Plugwise core and custom_component

Correct (my PLugs from Plugwise are not a zigbee but the very old variant which makes a network between themselves or did you mean this too?)

What I did notice is that it sometimes takes when you switch the plug on or off in Homeassistant, this is not always immediate and sometimes it takes a minute before it switches off, is this correct?

The old plugs are zigbee based too (same architecture, frequency, highlevel behavior, etc), but unfortunately it is still a custom flavor that is not compatible or compliant to the official zigbee standards.

About the switching: Do you experience a delay between flipping the switch at the home assistant web console and the physical switch of the plug?
Or is it about slow updating of the HA console representing the correct state? I.e the switch is flipping back to the original state and eventually gets updated to the new state after a delay of less than a minute?

When I flip the switch it sometimes takes more than a minute before the plug switches and sometimes nothing happens at all.
And indeed if you convert the switch to HA, it goes back to where it was in and then it switches off a bit, sometimes sometimes not.

It is very strange that they switch very quickly and immediately and sometimes not.

PS When my son is on his Nintendo switch, she didn’t switch at all at first, thought coincidence but every time it is.

That’s a bit strange behavior. To get some more insights to what actually happens, could collect som logging?

  1. Turn on informational logging in the developer menu:
    image
  2. Do the switching of a plug in Home Assistant and wait for the final result
  3. Turn off logging back to warning (or restart HA):
    image
  4. Collect the full log at the …/config/logs page
1 Like

i will do this tomorrow.
some plugs have suddenly become unavailable even after 6 hours still unavailable.
have already switched this off and in the socket but after hours still no connection. it is also a plug close to the circle + which is suddenly unavailable what can I do?

@brefa I think you mean setting the logger to: plugwise: debug?
Setting the level to info will not result in showing the debug-messages.

I don,t have this option
image

@mennog, Apparently you don’t have the logger integration active yet. Please, add the required logger: to the yml config file first.
@bouwew, the info log level logs the communication flow, which I suspect to be enough to get details about missing communication requests. Just to keep te log as small as possible :grinning:

Ho do i get the log file? (it’s new for me)

Also some plugs are not available this happened out of the blue
image

Instellingen --> Logboek --> LAAD VOLLEDIGE HOME ASSISTANT LOGBOEK

Plugs are marked as unavailable when it is not responding to 3 subsequently submitted powerusage requests. It will continue to ping the plug and make it as available again when a ping response is received.
In most cases this is an indication of weak signal strength or something like an oversaturated connection.
The requested logging should give some info about this :wink:

Log file is very big :frowning:

000D6F000278B66C is also not available but is max 5 meter from the circle+

021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Lookup message footer (b’\r\n’) in (b’\x05\x05\x03\x030000F88A00C14D43\r\n\x83’)

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Valid message footer found at index 20

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.controller] Received success NodeAckSmallResponse for request with seq_id b’F88A’

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Reset parser : b’\x83’

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Feed data: b’\x05\x05\x03\x030019F88A000D6F000278D3BF000D6F000278B24F091B8E\r\n’

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Parse data: b’\x05\x05\x03\x030019F88A000D6F000278D3BF000D6F000278B24F091B8E\r\n’

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Lookup message header (b’\x05\x05\x03\x03’) in (b’\x05\x05\x03\x030019F88A000D6F000278D3BF000D6F000278B24F091B8E\r\n’)

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Valid message header found at index 0

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Lookup message footer (b’\r\n’) in (b’\x05\x05\x03\x030019F88A000D6F000278D3BF000D6F000278B24F091B8E\r\n’)

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Valid message footer found at index 50

2021-01-27 19:23:10 INFO (serial_reader_thread) [plugwise.controller] Received CirclePlusScanResponse from 000D6F000278D3BF with sequence id b’F88A’

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.nodes] Previous update 2021-01-27 19:23:09.898452 of node 000D6F000278D3BF, last message 2021-01-27 19:23:10.059468

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.nodes.circle_plus] Process scan response for address 9

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.nodes.circle_plus] Linked plugwise node with mac 000D6F000278B24F found

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Reset parser : b’’

2021-01-27 19:23:10 INFO (send_messages_thread) [plugwise.controller] Send CirclePlusScanRequest to b’000D6F000278D3BF’ using seq_id b’F88B’

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.parser] Valid message header found at index 0

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.parser] Lookup message footer (b’\r\n’) in (b’\x05\x05\x03\x030000F88800C1F8B9\r\n’)

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.parser] Valid message footer found at index 20

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.controller] Received success NodeAckSmallResponse for request with seq_id b’F888’

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.parser] Reset parser : b’’

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.parser] Feed data: b’\x83\x05\x05\x03\x030019F888000D6F000278D3BF000D6F000278B66C0761C2\r\n’

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.parser] Parse data: b’\x83\x05\x05\x03\x030019F888000D6F000278D3BF000D6F000278B66C0761C2\r\n’

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.parser] Lookup message header (b’\x05\x05\x03\x03’) in (b’\x83\x05\x05\x03\x030019F888000D6F000278D3BF000D6F000278B66C0761C2\r\n’)

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.parser] Valid message header found at index 1

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.parser] Lookup message footer (b’\r\n’) in (b’\x05\x05\x03\x030019F888000D6F000278D3BF000D6F000278B66C0761C2\r\n’)

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.parser] Valid message footer found at index 50

2021-01-27 19:23:09 INFO (serial_reader_thread) [plugwise.controller] Received CirclePlusScanResponse from 000D6F000278D3BF with sequence id b’F888’

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.nodes] Previous update 2021-01-27 19:23:09.581667 of node 000D6F000278D3BF, last message 2021-01-27 19:23:09.735286

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.nodes.circle_plus] Process scan response for address 7

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.nodes.circle_plus] Linked plugwise node with mac 000D6F000278B66C found

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.parser] Reset parser : b’’

2021-01-27 19:23:09 INFO (send_messages_thread) [plugwise.controller] Send CirclePlusScanRequest to b’000D6F000278D3BF’ using seq_id b’F889’

2021-01-27 19:23:09 DEBUG (serial_writer_thread) [plugwise.connections] Sending CirclePlusScanRequest to plugwise stick (b’\x05\x05\x03\x030018000D6F000278D3BF080A77\r\n’)

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.parser] Feed data: b’\x05\x05\x03\x030000F88900C152E8\r\n\x83’

2021-01-27 19:23:09 DEBUG (serial_reader_thread) [plugwise.parser] Parse data: b’\x05\x05\x03\x030000F88900C152E8\r\n\x83’

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Lookup message footer (b’\r\n’) in (b’\x05\x05\x03\x030000F88A00C14D43\r\n\x83’)

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Valid message footer found at index 20

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.controller] Received success NodeAckSmallResponse for request with seq_id b’F88A’

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Reset parser : b’\x83’

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Feed data: b’\x05\x05\x03\x030019F88A000D6F000278D3BF000D6F000278B24F091B8E\r\n’

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Parse data: b’\x05\x05\x03\x030019F88A000D6F000278D3BF000D6F000278B24F091B8E\r\n’

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Lookup message header (b’\x05\x05\x03\x03’) in (b’\x05\x05\x03\x030019F88A000D6F000278D3BF000D6F000278B24F091B8E\r\n’)

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Valid message header found at index 0

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Lookup message footer (b’\r\n’) in (b’\x05\x05\x03\x030019F88A000D6F000278D3BF000D6F000278B24F091B8E\r\n’)

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Valid message footer found at index 50

2021-01-27 19:23:10 INFO (serial_reader_thread) [plugwise.controller] Received CirclePlusScanResponse from 000D6F000278D3BF with sequence id b’F88A’

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.nodes] Previous update 2021-01-27 19:23:09.898452 of node 000D6F000278D3BF, last message 2021-01-27 19:23:10.059468

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.nodes.circle_plus] Process scan response for address 9

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.nodes.circle_plus] Linked plugwise node with mac 000D6F000278B24F found

2021-01-27 19:23:10 DEBUG (serial_reader_thread) [plugwise.parser] Reset parser : b’’

2021-01-27 19:23:10 INFO (send_messages_thread) [plugwise.controller] Send CirclePlusScanRequest to b’000D6F000278D3BF’ using seq_id b’F88B’

dank je wel maar die is groot zeg om te laden :frowning:

Change/add this to your configuration.yaml fle and restart HA:

logger:
  default: warn
  logs:
    custom_components.plugwise: debug
    plugwise: info

That should result in less messages from plugwise.
@brefa please correct where necessary.

I now have an extensive log file from plugwise, but how can I attach a txt to it?

Please create an Issue here: https://github.com/plugwise/plugwise-beta/issues
And attach the txt-file to the issue-message .

Update: v0.14.3 has been released fixing the errors introduced in v0.14.1 and 0.14.2.

FYI, I had released Plugwise-beta v0.14.1 (adding a Domestic Hot Water Comfort Mode switch) but I have retracted the release due to a problem. I’m trying to fix the issue and hope to have a working release available soon.

RELEASE 0.14.5

1 Like

To attract the plug do I have to have the plugwise USB stick in my strech? my plugwise usb stick is in my Pi directly but cannot find the options to lock in it