zha-device-handlers: [Device Support Request] TS0601 _TZE204_pcdmj88b TRV not showing any entities
Problem description
I bought some Zigbee TRVs, they show up in home assistant as TS0601_TZE204_pcdmj88b but although they are pairing, no entity for control or sensor reading is showing up.
I tried some custom quirks I found (for Moes or Zonnsmart TRVs) but obviously nothing good came out of it.
Solution description
I never used or debugged custom quirks before, but I’m willing to provide help if someone needs more information to create a custom quirks for this model. Thanks a lot!
Screenshots/Video
No response
Device signature
Device signature
{
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": "0x0104",
"device_type": "0x0051",
"input_clusters": [
"0x0000",
"0x0004",
"0x0005",
"0xef00"
],
"output_clusters": [
"0x000a",
"0x0019"
]
}
},
"manufacturer": "_TZE204_pcdmj88b",
"model": "TS0601",
"class": "zigpy.device.Device"
}
Diagnostic information
No response
Logs
No response
Custom quirk
No response
Additional information
No response
About this issue
- Original URL
- State: open
- Created 8 months ago
- Reactions: 5
- Comments: 48
Now reading is in better shape but i’m unable to find why i can’t change mode or temperature 😦
Code is available at : https://github.com/Teka101/zha-device-handlers/blob/support_tze204_pcdmj88b/zhaquirks/tuya/ts0601_trv_tze204.py
@Teka101 well it seems it did the trick, I have access to the calibration value now! it doesn’t appear as an entity yet though, it only works through zha interface “write attribute”, but it works! I tried to limit the range of value you cane use from -12 to +12
calibration = -12 if value < -12 else 12 if value > 12 else valuebut it doens’t seem to work, I don’t understand why.Here is the converter I’m testing:
I’m still wondering how to make it show up as an entity, but there is progress!
@elf0heart yes there is more to do 😃
@T0ytoy preset can be change with group
PcdmThermostatAt this time, you can only change:
And in read only, we have :
I’m still working on it
PS: je vois des français partout ^_^
@elf0heart yes it’s only work for reading… i’m working on it 💪
@royduin i’m trying to check if all features implemented works and after i will submit a PR 😃
@T0yto great ! i’ll check code asap (i only work 1 or 2 hours by week on this project, so sorry for delay in response) In term of Home-Assistant integration the new version 2023.12 try new things in order to improve integration of ZIGBEE devices… maybe in the futur, we don’t have to bring patch to have full features on HA.
Really good job for your blueprint !
@Teka101 I was finally able to test you update, it seems to work thank you! In the home assistant zha UI, boost mode and window detection mode are both switches without a name, so it isn’t clear which does what at first glance, but it’s not a big problem.
If I have some time this week-end, I’ll try to implement the right class so that temprature calibration gets it’s own numeric entity in home assistant, so that it can be used easily.
I use the calibration feature (it has an entity on the z2m integration) to correct the device internal temperature to the temperature of an external zigbee thermometer: that way when the radiator heats up, the TVR temperature does not increase just because it’s too close to the radiator. It is done home assistant side, that is why I’m deseperately trying to get that entity 😄
I’ll let you know if I’m getting anything done. Thank you!
PR: https://github.com/zigpy/zha-device-handlers/pull/2873
@ed-wright Good news! It kinda make sense: the issue was probably on the zigbee association side, I’m glad there is no intricated technical issue with the python code, as I’m really not comfortable debugging advanced issues in this context 😄
To give credit to where it’s due: 890% of the work was done by @Teka101, I mostly just worked on the calibration feature. Many thanks to him 😃
As a side note, I’m currently experimenting with using an average value over ~5-10 minutes instead of the raw “0.5 °C resolution shit data” locale temperature data from the TVR to feed the blueprint I made, I think it might be working a bit better since the raw temperature is jumping ±1°C all the time and the automation blueprint reacts a lot to try to compensate. I’m hoping it will generate less spikes above and below target temperature.
@ed-wright I just checked, the quirk I have running on my HA and the one I linked above are exactly the same, and it’s working fine for me, so I don’t really know what to think. Could you maybe have a different version of the TRV? Mine came in a blue box, the user manuel front page says “Model: BAB-1413Pro-E”.
I guess since the quirk is loaded and would only do so with
"_TZE204_pcdmj88b", "TS0601", the signature is right. Does it work if you change the calibration value in the “manage Zigbee device” menu?EDIT: alternatively you can try and put some
_LOGGER.error("line xxx : value is %s", value)at key lines of the code (%s or %d depending on the line I think, also ‘value’ or ‘intValue’): I’m thinking lines 456, 460, 464, 472 are good places to investigate. This way you would have information in home assistant logs on what is going on.@T0ytoy ok thank you for your code.
I just publish a new version with: window detection mode and temperature calibration
Hello,
Very experimental patch (and very ugly), just add these lines at the end of file ts0601_trv.py: