In ZHA there is a last_seen value for each device but it is not set as a sensor. depending on your HA, each update for each devices is stored in the database sqlite or mysql. It is possible to setup a sensor that will scan the database to get the last updated timestamp for each device you want to follow. Normally a powered device will be updated every 10 minutes and a battery sensor at least every 25hrs.
I’m presently porting all Sinopé devices to quirks V2 and i will see if I can add a sensor for last seen timestamp. I see that you have a TH1400ZB and TH1300ZB. Is it possible for you to send me a device scan from zha toolkit. This will give me all cluster / attribute specific to those two devices. In quirks V2 all important / usefull attributes are added as a sensor or a number or a select entities so they are directly usable in automation.
For example your automation can be rewritten to send the temperature to an entity like number.your_thermostat_outdoor_temp. No need for ieee, cluster and attributes.
You can scan your devices in dev tools/actions:
action: zha_toolkit.scan_device
data:
ieee: 00:0d:6f:00:05:7d:2d:34 <--ieee of your thermostats
endpoint: 1
event_success: my_read_success_trigger_event
event_fail: my_read_fail_trigger_event
event_done: my_read_done_trigger_event
This will create a file in config/scans. Post the content or if you want send it by email.
I was going to pm you with the requested info but it seems that there is a number of character limitation that can be sent. I have instead emailed you the information so you can get going on your changes. Let me know if you need anything more.
I will try later to setup a sensor as you suggested. Also I am not sure what version of quirks I am on to run Sinopé V2… if or when it is available. I may have to get back to you on how to install all this. I am running HA core with mysql.
My quirks V2 is available for testing. It’s on my git:
Just copy the 4 files and replace the one you have in config/zhaquirks. Then restart HA. It won’t change your device name. Youe old automations will still work. But you will see many new sensor, number, select etc in the device card in ZHA. Each is a complete entitie that can be used for automations. No more need to create sensors to read attributes etc.
Tonight I’m doing a big update. to match the PR I’ve done to zha-device-handler.
Thanks for the two devices scans.
Unfortunately your scan are missing the sinopé manufacturer attributes. Sometime they don’t show up in the scan. If you install the V2 quirks try to re scan as with V2 sometime the devices are more verbose.
Thank for your help.
Normally this is fired by the HA event bus. Each time s device change his state an event is fired in the event bus and recorded in the history. This is generated when a service action is performed like change setpoint or change mode. On your graph the yellow light is the setpoint and the change should be registered in the logbook. The drop to 5oC is probably an error during device update or a confusion in message reception from the GT125. Normally, each request for device update is coded with a request number and wait for that number in the answer from the device via the GT125. It is possible that the answer was altered or two answer for different request came back at the same time. I need to improve request validation during device update to avoid this.
Thanks for reporting. What is your scan_interval for the GT125 ?
Even If I turn up and DOWN temperature inside HA nothing is showing in my logs.
Also the temperature really did get turned down. And I was using HA to see if I can figure out what triggered it.
I think I somehow triggered it by mistake but none of the climate changes for the GT125 or the Neviweb are showing in my logbook and i don’t know why even if make changes using HA.
