Closed kaihen closed 4 years ago
Generally, the device can be supported but I think, you'll not get happy with it. Based on the screenshots showing the available clusters, there is no therostat cluster available. This kinda fits into what I've previously read about the devices not having a local temperature sensor for valve adjustments. That means they'd always rely on an external sensor...
I'd assume this is where the manufacturer specific cluster FC00 comes into play. Unfortunately, we don't know which attributes it has and what they are for. This means they need to be reverse engineered by sniffing and analyzing the zigbee traffic, preferably with the vendor gateway available.
Sorry for not having better news.
Would it help if you got the firmware/update file for the Universal Gateway (UGE600)?
Not really. It's communication what's important.
Would it help if you got the firmware/update file for the Universal Gateway (UGE600)?
I have this device too, and we try to add them to Zigate.
Main probleme is cluster specific, Salus (computime) use is how language on Zigbee. even on connection Salus made thing very difficulte.
Closing this due to incomplete information. Please re-open if required.
Maybe this two links could help, where some guys sniffed the communication between SALUS devices: https://github.com/zigpy/zha-device-handlers/issues/571 https://github.com/Koenkk/zigbee-herdsman-converters/issues/1524
@benkuly Thanks for sharing this information. However: As Swoop mentioned we are missing some info from deCONZ which is needed to add this device.
I got some stuff from the vendor SALUS (see at the bottom). It would be great if you could support the TRV10RFM.
Cluster Info - Basic
Cluster Info - Identify
Cluster Info - OTAU
Node Info
The Log shows: log.txt
I don't know if it helps but I also found following file at my research for the TRV: SAL2EM1.txt
The following products counts also to my inventory: