Help to get better integration for Viessmann Valve

Hey all,

I integrated the new Viessmann Thermostat Valve. I have some questions for the received data.

The piHeatingDemand data should be between 0-255. and z2m use some math to get percent value. Well the Thermostat seems to just send a payload between 0-5. have you any ideas how to debug that for more details?! i have a pcap with wireshark if its helpful. The Payload what z2m published to mqtt is always “received data” / 255 *100. if i received the data with 1. the mqtt payload is = 0.

Then i have attributes names 16384 with payload between 0 -3. it seems to be a manufactur specific attribute. the attributID is 0x4000. that i have sniffed with wireshark. But i need some help to come deeper in debuging and understanding the zigbee data what i can see in wireshark 😃 Is there a possibilty to get to know what this attribute means?

how can i get the Firmware URL for OTA updates? can it be sniffed? or should i ask the manufacturer?

here the database.db entry:

{"id":4,"type":"EndDevice","ieeeAddr":"0x90fd9ffffe4a620e","nwkAddr":15806,"manufId":4641,"manufName":"Viessmann","powerSource":"Battery","modelId":"7637434","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":769,"inClusterList":[0,1,3,10,32,513,516,2821],"outClusterList":[0,25],"clusters":{"genBasic":{"attributes":{"modelId":"7637434","manufacturerName":"Viessmann","powerSource":3,"zclVersion":3,"appVersion":0,"stackVersion":8,"hwVersion":69,"dateCode":"20190705","swBuildId":"01.12.0008 02.00"}},"hvacThermostat":{"attributes":{"16384":1,"16391":0,"16392":0,"localTemp":2216,"occupiedHeatingSetpoint":2100,"pIHeatingDemand":2,"systemMode":4,"ctrlSeqeOfOper":2}},"genPowerCfg":{"attributes":{"batteryPercentageRemaining":158}}},"binds":[{"cluster":0,"type":"endpoint","deviceIeeeAddress":"0x00124b0018e1ea90","endpointID":1},{"cluster":1,"type":"endpoint","deviceIeeeAddress":"0x00124b0018e1ea90","endpointID":1},{"cluster":3,"type":"endpoint","deviceIeeeAddress":"0x00124b0018e1ea90","endpointID":1},{"cluster":10,"type":"endpoint","deviceIeeeAddress":"0x00124b0018e1ea90","endpointID":1},{"cluster":32,"type":"endpoint","deviceIeeeAddress":"0x00124b0018e1ea90","endpointID":1},{"cluster":513,"type":"endpoint","deviceIeeeAddress":"0x00124b0018e1ea90","endpointID":1},{"cluster":516,"type":"endpoint","deviceIeeeAddress":"0x00124b0018e1ea90","endpointID":1}]}},"appVersion":0,"stackVersion":8,"hwVersion":69,"dateCode":"20190705","swBuildId":"01.12.0008 02.00","zclVersion":3,"interviewCompleted":true,"meta":{"configured":1},"lastSeen":1588708734905}

i would be happy if we could discuss this points and when i could learn more about zigbee and get deeper knowing 😃

i could provide a pcap from my sniffing. But i just sniffed the zigbee2mqtt network. not with the original bridge.

best regards Chris

[ChrisChoke]

zigbee_20201215.zip

here it is 😃

[ChrisChoke]

okay, hey hey. wish you all a pretty sunday.

i am sitting in the cellar and look for the TRV. so please look in the pcap and in the txt file which is include in the zip. you will find all key you need to decrypt the pcap. i notice some line hinds in the txt file what happend at this points. viessmann_pcap.zip