Jacek Kończewski

Blakadder identified it as below: https://zigbee.blakadder.com/Avatto_TRV06.html Above DPs from Z2M and @challs help should be sufficient. Will do the quirk probably tomorrow. Only question is: me167FrostGuard: 36, me167AntiScaling: 39, Are...

Enable debug logs - if you didn't that already: ``` logger: default: info logs: homeassistant.components.zha: debug zigpy: debug zhaquirks: debug ``` Place that file in zha_custom_quirks [ts0601_temperature.py.zip](https://github.com/zigpy/zha-device-handlers/files/7913051/ts0601_temperature.py.zip) Restart HA. Remove...

@toy3375 unk_model means that device wasn't properly initialized. You need to remove it and add again. Maybe after HA restart. Your device sends those attributes: ``` 2022-01-21 19:19:08 DEBUG (MainThread)...

Code was written with a new approach, but that should not be a problem here, since you have newest HA version. Nevertheless here's same code rewritten in the older approach....

> and now the Bonus-Level. Any Idea for the Clock ( Time ) ? :) You think you will ever wanna to get that from the device? Here's a list...

Try version below. Time offset wasn't set, but I see that your device is making a request for time update. Device MUST ask for time update - there's no possibility...

@jbmfg > could be possible to change the temperature units on the device itself to F Probably yes. You just need to tell me which attribute is responsible for the...

@jbmfg I mean Zigbee attribute from the DEBUG logs.

Not sure what you did, but there's an attribute that changes value. ``` 2022-01-28 07:45:39 DEBUG (MainThread) [zhaquirks.tuya] [0x7dd0:1:0xef00] Received value [1] for attribute 0x040f (command 0x0002) 2022-01-28 08:08:15 DEBUG...

@joaoasilva Yep. For start please put here a pairing log. And after pairing put here also Zigbee Device Signature