Closed luke7101 closed 3 weeks ago
Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
zha documentation zha source (message by IssueLinks)
Enable debug logging for 20 minutes and attach the log please
Ok, tonight at 10PM the tariff switches from sensor.lixee_zlinky_tic_tier_2_summation_delivered (Cluster 0x702 Attribute 0x0102), which is working normally, to sensor.lixee_zlinky_tic_tier_1_summation_delivered (Cluster 0x702 Attribute 0x0100) which isn't working excepted with an automated periodic reading of the cluster/attribute made by ZHA toolkit attr_read service. I guess it'd be of more interest to send you the logs across this time instead of now ?
Thanks !
Hi @dmulcahey, here are 20 minutes of ZHA debug logs. From 21:50 to 22:00 tariff 2 (updating normally) From 22:00 to 22:05 tariff 1 (not updating) From 22:05 to 22:10 tariff 1 + ZHA toolkit attr_read service set to read Cluster 0x702 Attribute 0x0100 every 10 seconds (just read, not set to update any sensor, still, the read function triggers an update of the stuck sensor). home-assistant_zha_2024-02-07T21-10-03.002Z.log
Can I do anything to help ?
I'm now on core-2024.3.0 and it still doesn't work !
Hi @dmulcahey, here are 20 minutes of ZHA debug logs. From 21:50 to 22:00 tariff 2 (updating normally) From 22:00 to 22:05 tariff 1 (not updating) From 22:05 to 22:10 tariff 1 + ZHA toolkit attr_read service set to read Cluster 0x702 Attribute 0x0100 every 10 seconds (just read, not set to update any sensor, still, the read function triggers an update of the stuck sensor). home-assistant_zha_2024-02-07T21-10-03.002Z.log
Please do this again and don’t manually read anything and avoid using zha-toolkit during the test so that I have a clean log please. I need the full startup of ZHA in the log too.
Please do this again and don’t manually read anything and avoid using zha-toolkit during the test so that I have a clean log please. I need the full startup of ZHA in the log too.
David, I just missed the opportunity to do it yesterday with the right tariff (off peak blue day = tic_tier_1), I now have to wait for the next "blue" day.
I'll send you the logs starting just before the tariff change, is it ok for you ?
In order to send you the full startup of ZHA I guess I must restart HA. Which debug logs should I activate in configuration.yaml in order to make the logs as clean as possible for you ?
logger:
default: info
logs:
homeassistant.core: debug
homeassistant.components.zha: debug
zigpy: debug
zigpy_znp: debug
You can just reload the ZHA integration after enabling debug logging:
Please do this again and don’t manually read anything and avoid using zha-toolkit during the test so that I have a clean log please. I need the full startup of ZHA in the log too.
Here you are, 20 minutes of debug logs with ZHA startup and no manual reading with ZHA ! home-assistant_zha_2024-03-14T21-10-06.872Z.log
Now on core-2024.3.3, it still doesn't work. Please tell me if I can do anything to help!
core-2024.4.0 and still no luck 😕
Bonjour, Je suis dans le même cas depuis le 21/03/2024. J'utilisr un seul sensor pour les kW de la maison:
Mais je n'ai pas de remonter de toutes les entités depuis cette date.
Je ne sais pas si cela est vraiment une issue. Mais en débranchant du compteur le lixee et en le remettant cela fonctionne pour moi. J'ai également cliquer sur reconfigurer dans zha sur l'écran information de l'appareil. Bonne continuation.
I'm now on core-2024.5.1, and it still doesn't work. Please tell me if I can do anything to help!
Hi,
I'm experiencing the same issue. If anyone knows how to solve it, please let me know.
Initially, I thought it was a problem with Lixee or Zigbee2MQTT (Z2M) in my case.
I edited my message because I didn't read it correctly the first time. I noticed that you're having this issue with Zigbee Home Automation (ZhA), but I'm facing it with Z2M, not ZhA. I'm not sure what to think about that.
I've tried unplugging and plugging it back in, but I'm hoping the issue will be resolved with the next HCJB update.
Sadly, there's in no one here anymore apparently...
Updated HA to core-2024.8.0 and sensor started to update again! A chance, cause ZHA toolkit is broken since the 2024.8.0 update 😅
Will it last?! I prefer not to close the issue yet...
Updated to core-2024.8.1 and sensor still updates. I'll close the issue.
The problem
This issue is a follow up of the https://github.com/home-assistant/core/issues/106712 issue, apparently solved by https://github.com/home-assistant/core/pull/106738 but seemingly not for everyone.
In my case almost all the device sensors are still updating since 2024.1.1, excepted for one.
Here are the locations of the metering counters from the 6 tariffs of our subscription:
sensor.lixee_zlinky_tic_tier_1_summation_delivered Cluster 0x702 Attribute 0x0100
sensor.lixee_zlinky_tic_tier_2_summation_delivered Cluster 0x702 Attribute 0x0102
sensor.lixee_zlinky_tic_tier_3_summation_delivered Cluster 0x702 Attribute 0x0104
sensor.lixee_zlinky_tic_tier_4_summation_delivered Cluster 0x702 Attribute 0x0106
sensor.lixee_zlinky_tic_tier_5_summation_delivered Cluster 0x702 Attribute 0x0108
sensor.lixee_zlinky_tic_tier_6_summation_delivered Cluster 0x702 Attribute 0x010a
All sensors are updating excepted for sensor.lixee_zlinky_tic_tier_1_summation_delivered The first one is only updated after a restart or if manually read through the "Manage Zigbee device" window.
What version of Home Assistant Core has the issue?
core-2024.1.6
What was the last working version of Home Assistant Core?
core-2023.12
What type of installation are you running?
Home Assistant Container
Integration causing the issue
zha
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
Diagnostics information
zha-fab0e8aa14aa219d689ae9890c8770ef-LiXee ZLinky_TIC-954a1f87f8c96baa2aa849772a4eddb8.json.txt
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response