After updating to Core 0.114.0, Iām seeing this in Logs:
Log Details (ERROR)
Logger: root
Source: /usr/src/homeassistant/homeassistant/bootstrap.py:313
First occurred: 2:57:56 PM (1 occurrences)
Last logged: 2:57:56 PM
Uncaught thread exception
Traceback (most recent call last):
File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/usr/local/lib/python3.8/threading.py", line 870, in run
self._target(*self._args, **self._kwargs)
File "/usr/local/lib/python3.8/site-packages/plugwise/stick.py", line 701, in _watchdog_loop
if not self.connection.read_thread_alive():
File "/usr/local/lib/python3.8/site-packages/plugwise/connections/connection.py", line 103, in read_thread_alive
return self._reader_thread.isAlive() if run_reader_thread else False
NameError: name 'run_reader_thread' is not defined
@brefa, an observation and some feedback, if you donāt mind
I see you are showing as an attribute the ātoday_energy_kwhā value. When looking at the value: 0.002 at the moment, and looking at my own sensor for the same entity: 2.2, it looks like your value is a factor 1000 wrong.
Nice catch, the today_energy_kwh is definitely miscalculated. I have fixed it in the latest version 1.2.2.
I have assigned the āoutletā device_class according to this development page. Apparently the user documentation is kind of missing the switch entity.
Do you experience any negative behavior due to this device_class setting?
Just FYI, not to steal your thunder @brefa , initial support for the Plugwise Stretch with firmware 3.1 is available in Plugwise-beta. Please leave a message in the Plugwise Smile custom_component (BETA) topic if you are interested in helping us test.
@bouwew, sorry I cannot reproduce the problem you are reporting. Do you experience this for all plugs and do the values remain at 0 even after one day?
If possible could you collect some debug logging of the startup process (first few minutes should be enough) so Iām able to investigate this.
Hi, first off thank you for all your hard work. I was very excited to see that my plugs arenāt useless anymore. I do have a problem with configuring the USB stick. It gives me the following error: āInitialization of Plugwise USB-stick failedā when selecting the stick. I followed the 3 steps written in the first post, anything I overlooked? thanks.
Are you sure you have selected the correct USB serial device? The most obvious reason to bump into this error messages is when you selected/entered a wrong device path.
I have tried a few things, different usb port, a few restarts of the server but nothing works. I know for sure I have the right USB stick. This is the error I see in the logs when I attempt to configure it:
Skip message, received 54 bytes of expected 60 bytes
and:
Uncaught thread exception
Traceback (most recent call last):
File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/usr/local/lib/python3.8/threading.py", line 870, in run
self._target(*self._args, **self._kwargs)
File "/usr/local/lib/python3.8/site-packages/plugwise/stick.py", line 514, in _receive_timeout_loop
if self._cb_stick_initialized:
AttributeError: 'stick' object has no attribute '_cb_stick_initialized'
It seems that the first answer to the initialization request from the USB stick is different from what is expected: a message with 54 bytes instead of a message containing 60 bytes. I am curious about the contents of this 54 bytes message.
To investigate this could you collect some debug logging by setting the logging level like below? As it fails at the initialization phase the log will be small.
The crash (uncaught thread exception) happens while recovering from the unexpected response. I will fix that but it wonāt solve your problem as it shouldnāt get to that point.
0011000D6F00002363C501000D [Zigbee state missing] 6F00002366A934DA [Zigbee ID missing] FF5370
Iām guessing the Zigbee network information is missing, but Iām not 100% sure yet. From some reverse enginering of the plugwise source software I discovered there could be situations some information in this message is optional, but I have not seen this happen in real life before.
To be sure could you let me know some little more information?
Does the Circle+ module have ID 934DA ?
Is the Circle+ operational (powered) and within reach of the USB-Stick
Does the USB-Stick work using the Windows Source software?
Hi, I just noticed this: I have used my oven in the morning and evening, as can be seen in the power usage graph.
However, in the energy used graph the morning usage is not shown.
How can I/we debug this?
Also, how can I retrieve ātotal power usage to dateā?
Thanks for any help!
Iāve been running Plugwise-2-py fro a long time now and iāve made some small modifications to if for myself.
As home assistant only works with present values, Iāve modified the Plugwse-2-py to push straight to influxdb. So in case home assistant is crashing, or a circle is out of range for some time, the data will be recovered as soon as the connection is back. Maybe we can add something like that to this plugin at a later stage.
But first things first, stability.
I wanted to test this integration. But during testing i found that the polling is not consistent.
Using the Plugwise-2-py -> MQTT -> Influxdb I get consistent pols every 10 (+/-1) seconds:
My circle+ does NOT have the ID: 934DA
the Circle+ is powered and when plugging in I hear a āclickā
I have tried using the circle+ with the source software on windows but it gets stuck on linking it to the stick. Iāve waited around 1,5 hours and itās still not working.