Closed freakyjoe8 closed 1 year ago
Can you send a screenshot of the reconfiguration dialog? It looks like the device doesn't send attribute reports properly and ZHA would need to poll it.
I've also written to Ubisys support and asked them if this is maybe a firmware bug. They replied no and they stated that they are following Zigbee standards here and sent me this screenshot:
Not sure what this means as I'm no Zigbee expert. But I'd also suspect this error to occur on their whole switch product line (S1, S1-R, S2, S2-R).
Screenshot of the reconfigure dialog
I've worked around this now by polling the attribute manually every 5 minutes via ZHA toolkit and creating an automation. This is the service call if someone else also has this problem.
service: zha_toolkit.attr_read
data:
ieee: 00:1f:ee:00:00:00:xx:xx
endpoint: 3
cluster: 1794
attribute: 0
use_cache: false
state_attr: sensor.steckdose_quooker_summation_delivered
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug The power summation in kWh is not update for the Ubisys S1 switch (https://www.ubisys.de/en/products/light-and-consumers/power-switch-s1/). It is only updated on reboot. Firmware is the newest one available (ubisys S1 Firmware Version 2.1.2, ubisys Zigbee Stack 4.0.4 (Hardware Revision >= 2).
To Reproduce Steps to reproduce the behavior:
Expected behavior The summation should constantly increase based on the current summation of kWh used.
Screenshots
Additional logs
``` Paste any additional debug logs here. Don't remove the extra line breaks outside the ``` marks. ```Additional context Add any other context about the problem here.