plugwise / plugwise_usb-beta

Custom-component / development version of the USB Plugwise Home Assistant platform
MIT License
4 stars 4 forks source link

[BUG]: Energy Consumption stats stop working #11

Open infernix opened 1 year ago

infernix commented 1 year ago

Describe the bug.

On all my Circles and Circle+ the Energy Consumption Today stats stop working. They worked the first time i set it up, and maybe after a HASS restart, but then they stop updating. The Power Usage sensors work perfectly fine.

What version of Home Assistant Core has the issue?

2012.22

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

How did you install plugwise-beta?

HACS

What kind of Plugwise device is having issues?

USB: Stick

What firmware version is your Plugwise product at?

Not sure about stick but most circles are on 2011-06-27 10:52:18 and some on 2015-09-18 10:53:15

Logging

Here's the current logs without additional debugging enabled:

2022-12-19 04:45:48.684 WARNING (serial_reader_thread) [plugwise.controller] Drop NodePingRequest to 000D6F00004BE237 because max retries 3 reached
2022-12-19 04:46:08.703 WARNING (serial_reader_thread) [plugwise.controller] Drop NodePingRequest to 000D6F00004BE237 because max retries 3 reached
2022-12-19 04:46:28.719 WARNING (serial_reader_thread) [plugwise.controller] Drop NodePingRequest to 000D6F00004BE237 because max retries 3 reached
2022-12-19 04:46:48.734 WARNING (serial_reader_thread) [plugwise.controller] Drop NodePingRequest to 000D6F00004BE237 because max retries 3 reached
2022-12-19 04:47:08.756 WARNING (serial_reader_thread) [plugwise.controller] Drop NodePingRequest to 000D6F00004BE237 because max retries 3 reached
2022-12-19 04:47:28.766 WARNING (serial_reader_thread) [plugwise.controller] Drop NodePingRequest to 000D6F00004BE237 because max retries 3 reached
2022-12-19 04:47:48.782 WARNING (serial_reader_thread) [plugwise.controller] Drop NodePingRequest to 000D6F00004BE237 because max retries 3 reached
2022-12-19 04:48:08.810 WARNING (serial_reader_thread) [plugwise.controller] Drop NodePingRequest to 000D6F00004BE237 because max retries 3 reached
2022-12-19 04:48:28.817 WARNING (serial_reader_thread) [plugwise.controller] Drop NodePingRequest to 000D6F00004BE237 because max retries 3 reached
2022-12-19 04:48:48.837 WARNING (serial_reader_thread) [plugwise.controller] Drop NodePingRequest to 000D6F00004BE237 because max retries 3 reached
2022-12-19 04:49:08.851 WARNING (serial_reader_thread) [plugwise.controller] Drop NodePingRequest to 000D6F00004BE237 because max retries 3 reached
2022-12-19 04:49:28.864 WARNING (serial_reader_thread) [plugwise.controller] Drop NodePingRequest to 000D6F00004BE237 because max retries 3 reached
2022-12-19 08:06:16.389 WARNING (send_messages_thread) [plugwise.controller] Cannot resend unknown request b'3614'
2022-12-19 13:51:20.337 WARNING (SyncWorker_44) [homeassistant.loader] We found a custom integration plugwise which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-12-20 05:40:47.026 WARNING (send_messages_thread) [plugwise.controller] Cannot resend unknown request b'0011'
2022-12-20 05:40:58.544 WARNING (send_messages_thread) [plugwise.controller] Drop CirclePowerUsageRequest to 000D6F0000AF50EB because max retries 3 reached
2022-12-20 10:53:39.797 WARNING (serial_reader_thread) [plugwise.parser] Invalid message length received for NodeSwitchGroupResponse, expected 38 bytes got 22
2022-12-20 14:51:38.813 WARNING (serial_reader_thread) [plugwise.parser] Invalid message length received for NodeSwitchGroupResponse, expected 38 bytes got 22
2022-12-20 18:50:18.049 WARNING (serial_reader_thread) [plugwise.parser] Invalid message length received for NodeSwitchGroupResponse, expected 38 bytes got 22
2022-12-20 20:04:55.468 WARNING (serial_reader_thread) [plugwise.parser] Invalid message length received for NodeSwitchGroupResponse, expected 38 bytes got 22
2022-12-21 03:37:47.880 WARNING (send_messages_thread) [plugwise.controller] Cannot resend unknown request b'5A9A'
2022-12-21 07:25:42.336 WARNING (serial_reader_thread) [plugwise.parser] Invalid message length received for NodeSwitchGroupResponse, expected 38 bytes got 22
2022-12-21 07:49:45.883 WARNING (send_messages_thread) [plugwise.controller] Cannot resend unknown request b'0001'
2022-12-21 08:48:41.773 WARNING (serial_reader_thread) [plugwise.parser] Invalid message length received for NodeSwitchGroupResponse, expected 38 bytes got 22
2022-12-21 09:06:22.282 WARNING (serial_reader_thread) [plugwise.parser] Invalid message length received for NodeSwitchGroupResponse, expected 38 bytes got 22

This is only a snippet, there's many more lines lole like this.

Diagnostics information

Applies to all of them so not sure how useful

Additional information

I used Plugwise2Py before, which seems as if it kept track internally on the energy usage over time. But i do recall that back when I used the Windows software with these plugs, it worked fine. So doesn't seem like a hw issue.

ArnoutD commented 1 year ago

If have a identical issue, and have a 23:55 script to reboot HA for it to capture the latest values, Watt recording works fine

Screenshot-1

infernix commented 1 year ago

Not sure if related, but it also frequently doesn't find my circle+ after a homeassistant restart. It wil then never collect any stats at all, until i restart again and by chance it does find the circle+.

I'm inclined to switch back to Plugwise2Py given the unreliability at the moment. Is there anything i can do to speed up debugging?

CoMPaTech commented 1 year ago

@brefra can you provide @infernix with an update?

ksya commented 11 months ago

Same problem here. It was also with the last plugwise (not usb) version that worked with the Stick. After restarting the plugwise integration, it works again for an amount of time.

dirixmjm commented 6 months ago

Hi @infernix @ksya can you test with version 0.40.5a1 ? (You need to enable beta testing).