Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[BUG] Problems with Plugwise beta #5

Closed
mgiebels opened this issue Jan 28, 2021 · 24 comments
Closed

[BUG] Problems with Plugwise beta #5

mgiebels opened this issue Jan 28, 2021 · 24 comments
Assignees
@brefra
Labels
bug Something isn't working

Comments

@mgiebels
Copy link

plugwise.txt

I regularly have that some circles are not available such as Circle type F (000D6F000278B66C) or 8b25a all the way, the B66C is close to the Circle + at most 5 to 6 meters away.

I also have problems with some circles when I press the switch it jumps back 15:19 just done see the log below
Circle is : 000D6F000278B257

2021-01-28 15:19:33 INFO (send_messages_thread) [plugwise.controller] Send NodePingRequest to b'000D6F000278B257' using seq_id b'799C'
2021-01-28 15:19:33 WARNING (serial_reader_thread) [plugwise.controller] Drop NodePingRequest to 000D6F000278B257 because max retries 3 reached
2021-01-28 15:19:33 INFO (send_messages_thread) [plugwise.controller] Send NodePingRequest to b'000D6F000278B24F' using seq_id b'799D'
2021-01-28 15:19:33 WARNING (serial_reader_thread) [plugwise.controller] Drop NodePingRequest to 000D6F000278B24F because max retries 3 reached
2021-01-28 15:19:33 INFO (send_messages_thread) [plugwise.controller] Resend NodePingRequest to b'000D6F000278B257' using seq_id b'799E', retry 2
2021-01-28 15:19:33 INFO (send_messages_thread) [plugwise.controller] Resend NodePingRequest to b'000D6F000278B24F' using seq_id b'799F', retry 2
2021-01-28 15:19:34 INFO (serial_reader_thread) [plugwise.controller] Received NodePingResponse from 000D6F00005528C5 with sequence id b'799A'
2021-01-28 15:19:34 INFO (serial_reader_thread) [plugwise.controller] Received NodePingResponse from 000D6F00005528C5 with sequence id b'799A'
2021-01-28 15:19:34 INFO (serial_reader_thread) [plugwise.controller] Drop unexpected NodePingResponse using seq_id b'799A'
2021-01-28 15:19:34 INFO (serial_reader_thread) [plugwise.controller] Received CirclePowerUsageResponse from 000D6F00005528C5 with sequence id b'799B'
2021-01-28 15:19:34 INFO (serial_reader_thread) [plugwise.controller] Received CirclePowerUsageResponse from 000D6F00005528C5 with sequence id b'799B'
2021-01-28 15:19:34 INFO (serial_reader_thread) [plugwise.controller] Drop unexpected CirclePowerUsageResponse using seq_id b'799B'
@mgiebels mgiebels added the bug Something isn't working label Jan 28, 2021
@brefra brefra self-assigned this Jan 28, 2021
@brefra
Copy link
Contributor

brefra commented Jan 28, 2021

Thanks for reporting and the log. A quick look into the log shows a lot of missing responses. So there is definitely something wrong here.
I need some more time to get a to an conclusion.

@brefra
Copy link
Contributor

brefra commented Feb 3, 2021

A small update: For the 4 responding plugs (....28C5, ...B24F, ....B257, ....B2CA) I see multiple times the same response getting back. On average about 6~7% of the received messages is a replay. Still have to do some more research...

@mgiebels
Copy link
Author

Ok i will wait for it i saw today an update but doesnt solve it

@brefra
Copy link
Contributor

brefra commented Feb 14, 2021

The update of today doesn't update anything in relation to the legacy USB-stick setups.
After some additional investigation I strongly suspect some kind of network congestion or node processing overload is preventing communication to some nodes further down the zigbee network. Which explains the high number of repeated/duplicated messages and some high delayed messages too.
So I'm currently writing/testing updated code with improved message priority together with a variable update polling frequency based on the amount of repeated/duplicated messages received.

@mgiebels
Copy link
Author

mgiebels commented May 1, 2021

Is there already a solution? problem does still excists

@bouwew
Copy link
Contributor

bouwew commented May 3, 2021 •
edited
Loading

@brefra unfortunately doesn't have time at the moment.

As you can see in other issues, @CoHoAppel is experiencing similar issues: #6 and #7.
Knowing a bit more about CoHoAppel's system, his Stick used to be a part of a Stretch running the newest (beta?) firmware known to me, I wonder whether CoHoAppel's and your issues are related to the firmware-version of your Stick and/or Circle's, etc.?

Can you provide the firmware versions of your Stick and the connected devices that have issues? If you see differences in firmware versions between the same connected devices, please let us know as well.

My Circles firmware is: 2011-06-27 10:52:18, all 9 have the same version on board, my Stealth M+ firmware is 2011-06-27 10:47:37. I couldn't find the firmware version of my Stick.
As far as I can see, my system is working well.

@CoHoAppel
Copy link

You are correct bouwew I do see "Drop NodePingRequest to 000xxxxxxxxxx because max retries 3 reached" from time to time as well. I also experience Circles randomly disappearing from the network. Not sure if this is Plugwise related or if it is because of a not functioning recovery procedure in "plugwise-beta" once it detected the 3 retries limit. It could take weeks, then a plug may show up or another may disappear. In all cases, when I remove the stick from the Raspberry Pi to a PC (Windows) where I can run the plugwise application "Source", all plug are recognized in minutes and also all the values recorded in the plugwise network , (history of many weeks) are retrieved and displayed in the reporting module of "The Source". This makes me believe that plugwise beta recovery is suspected. The 6 Circles have Firmware dated 2011-06-27 10:52:18 The Circle+ is dated 2011-06-27 10:47:37 . No idea where to find the Stick firmware level. I have been testing various external conditions. See a list of questions in the attached doc.
Plugwise beta project losing circles from the network.docx

@bouwew
Copy link
Contributor

bouwew commented May 4, 2021

I also see that message now and then but that is expected because some of my Circles are not plugged at certain times. After unplugging a Circle, this message shows up.

Which version of Source are you using?

@mgiebels
Copy link
Author

mgiebels commented May 4, 2021

My circles are all with the same firmware as below.
Circle type F.
by Plugwise
Firmware: 2011-06-27 10:52:18

And the circle +

Circle + type F.
by Plugwise
Firmware: 2011-06-27 10:47:37

I can't read the firmware of my stick in Homeassistant

@CoHoAppel
Copy link

The version of The Source is 2.40 (20180404.555). I consulted the Plugwise Helpdesk back in feb and they advised we to download it from there: https://securedata.plugwise.net/source/pwsetup.exe

@bouwew
Copy link
Contributor

bouwew commented May 4, 2021 •
edited
Loading

The Source version I'm using is v2.25. I had read about a newer version but hadn't been able to find it, thanks!

And, you're right, the issue is likely in the plugwise-beta / python-plugwise code. But, we only have limited information available on the communication protocol, also @brefra most likely does not have a Stick with newer or the newest (beta) firmware.
We should probably show the Stick as a device in HA Core, including the firmware. In order to get clear if the difference in firmware is the root-cause of the issues. @brefra is there maybe another way to find the firmware version of the Stick?

@brefra
Copy link
Contributor

brefra commented May 4, 2021

Sorry, unfortunately I don't have much time at the moment. A quick answer: From reverse engineering of the Source software I know the stick has firmware installed (over 25 different versions just for the stick !) . I haven't found any way to retrieve the actual version out of the Stick (yet)
I do have some ideas in mind to improve the communication and (debug)logging to get this issue sorted. Still haven't got the time to write and test this out.

@CoHoAppel
Copy link

Don't know if there is much competition between communities, but notices that Plugwise-2-py , https://github.com/SevenW/Plugwise-2-py , also has an interface to HA using MQTT. Talking to those guys may shorten your learning curve :-) and as more and more HA users start working with MQTT one way or another (would be another challenge for me, but if it works.....I'm fine ) this may save you time and efforts. Just a thought.

@bouwew
Copy link
Contributor

bouwew commented Aug 8, 2021 •
edited
Loading

@mgiebels
Please try plugwise-beta v0.17.0a7, do the changes have any effect on the bugs that you've reported?

@mgiebels
Copy link
Author

mgiebels commented Aug 8, 2021 via email

@CoMPaTech
Copy link
Member

It already is - check if you have 'include beta' on choose 'reinstall' from HACS and check if you have the toggle set - it's an unreleased version as things might not work (so handle with due care)
screenshot

@mgiebels
Copy link
Author

mgiebels commented Aug 8, 2021 via email

@mgiebels
Copy link
Author

mgiebels commented Aug 16, 2021 via email

@phaeton82
Copy link

Having the same issue i thought let’s see if I can provide some info. What information would you guys need? The issue is more ‘visible ‘ since the new energy dashboard. Sometimes devices seem to stop using energy ;)

I use plugwise with a stick, have approx 15 plugs and distance doesn’t seem to be an issue since the plug 15 cm from my circle+ also has issues. Network congestion sound logical to me. Can we set timings to lower the amount of updates?

Please let me know if I can hand over some useful information.

This was referenced Jan 20, 2022
Closed
Closed
Merged
@ArnoutD
Copy link

ArnoutD commented Feb 7, 2022 •
edited
Loading

I have a the same issue (Circle+ 8 Circles connected via Stick) Stick is almost next 2 the Circle+ so main connectivity is no issue

Difficult part is that average time between two issues is 2 hours

as a workaround I reload the integration on the error with an automation
`

  • id: '1625817083040'
    alias: Reload plugwise
    description: ''
    trigger:
    • platform: event
      event_type: system_log_event
      condition:
    • condition: template
      value_template: '{{ ''Drop NodePingRequest to'' in trigger.event.data.message[0]
      }}'
      action:
    • service: rest_command.reload_plugwise
      data: {}
      mode: single
      `
      If you need help I am willing to help to test for a solution. Haven't run a dev home assistant though

@CoMPaTech
Copy link
Member

@brefra can you check and/or do you want to resolve the plugwise/plugwise-beta#226 MC's or should we assist?

@CoMPaTech CoMPaTech changed the title Problems with PLugwise beta Problems with Plugwise beta [BUG] Feb 20, 2022
@CoMPaTech CoMPaTech changed the title Problems with Plugwise beta [BUG] [BUG] Problems with Plugwise beta Feb 20, 2022
@malosaa
Copy link

malosaa commented Apr 16, 2022

I must say the plugs are pretty stable to me right now.
I had before with homeassistant 2022.1 sometimes that my plugs turned on by itself when there was an connection error.
So the plugs where off at a specific time, but because of the connection issue by the usb it reconnected my plugs and put my off plugs to on.

So this caused my reptiles to wake up in the night hehe.

But now i have some drops in the logs but it gets resolved by itself, and i have a lot of plugs used for my reptiles and some other stuff like a fridge, freezer, induction etc...

Before i was thinking to switch over to zigbee/shelly but right now its running smooth.

What i also did is reconfigure all plugs with source software (as of now u cant get a code anymore) u need to email plugwise to get one.

And i used a different usb hub whats powered.

And it works great till today.

@CoMPaTech CoMPaTech transferred this issue from plugwise/plugwise-beta Apr 19, 2023
@dirixmjm
Copy link
Contributor

@mgiebels although a very old thread, please try with updated release 0.40.0.

@dirixmjm
Copy link
Contributor

dirixmjm commented Jan 7, 2024

Closing due to lack of response. Please open a new ticket if the problem persists with version 0.40.5a1 (enable beta testing).

@dirixmjm dirixmjm closed this as completed Jan 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@brefra brefra

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@dirixmjm @CoMPaTech @phaeton82 @brefra @bouwew @malosaa @ArnoutD @CoHoAppel @mgiebels