-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SP24x Latest Firmware 1.9.28 Decimal Problem #691
Comments
Run OTA again, there's another firmware (1.9.30) which fixes that bug. See here -> Koenkk/zigbee-herdsman-converters#6747 |
Thanks for this. I've upgraded a plug to 1.9.30, however the CurrentSummationDelivered still seems too high. Anyone else experiencing this? A 120W device has used over 1 Kilowatt in an hour... |
Did you reconfigure the device after the FW upgrade? As it needs to now re-apply some settings. (Yellow/orange) arrows on the main device screen. Koenkk/zigbee-herdsman-converters#8715 (comment) edit: Note this will potentially change any custom reporting values on the reporting tab also. |
I'm not on z2m but i'm facing the same issue (ZHA) The energy consumption is far too high, tried to update to 1.9.30, removed the device, add it back to HA, but it didn't help. It was working perfectly before the update |
Re-paired the device, including the above re-interview step, the decimals are definitely off by a factor of 10 still. Luckily downgrading to 1.7 is possible. |
Is it possble to downgrade ? |
I downgraded using the documentation in Zigbee2Mqtt. Not sure if you can do it in ZHA. Made the switch to Zigbee2Mqtt from ZHA a while ago, I haven't regretted it, would recommend. |
Hi there,
I'm assuming the issue is related to the patch notes "CurrentSummationDelivered from 2 to 3 decimals: every Wh can now be tracked." - even after re-pairing the device, z2m & Home Assistant only show to 2 decimal places but seem to accept as if the 3rd was the 2nd, resulting in the value being multiplied by 10. As an example previous incremental device usage stats would be .02 w/H every 5 minutes the device was on, is now reporting as .11w/h every 5 minutes the same device is on. I think my understanding of the issue is right but maybe I'm wrong, either way the CurrentSummationDelivered is wrong now, as far as I can tell being 10 times what the value should be. (Device using 3.5Kw/H a day now reports using 35 Kw/H a day).
Thanks,
epd5
The text was updated successfully, but these errors were encountered: