Insteon_PLM on Hass.io, Anyone have it working?

Madelinot · March 24, 2018, 3:39pm

I did the following within my “config” directory (forget the “climate” component) with the raw contents of your files:

Rebooting now…

Madelinot · March 24, 2018, 3:54pm

Not good news. The components do not work. I get the following in my logs and none of the sensors work:

Error during setup of component insteon_plm
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/homeassistant/setup.py", line 142, in _async_setup_component
    result = await component.async_setup(hass, processed_config)
  File "/config/custom_components/insteon_plm.py", line 56, in async_setup
    ipdb = IPDB()
  File "/config/custom_components/insteon_plm.py", line 128, in __init__
    from insteonplm.states.sensor import (VariableSensor,
ImportError: cannot import name 'LeakSensorDryWet'

Plus this:

teharris1 · March 25, 2018, 3:51pm

The problem there is the insteonplm module cannot be installed like that. Unless you can get to your python library folder it looks like you will have to wait until I can get it into the main distro. I have started the release process but not completely sure when it will hit the master branch.

Madelinot · March 31, 2018, 1:07pm

Update: I reverted back the changes. I’ve had this running for a while, and still experiencing the same issues as before. However, there is one thing I noticed. Out of the five leak sensors that I have, two are almost new, three are about 4-5 years old. The new ones seem to work fine, they stay dry. The old ones, after a reset, they get wet within a day. They are all the same part number but could there be a difference there?

The issue related to them not being always detected in HASS remains and after a few reboots, they all show up.

Thanks!

teharris1 · March 31, 2018, 4:52pm

I posted an update in the 0.66.0 vesion of HA. Not sure how long it takes to go from HA to haas.io.

I took a good look at the log files and the config file. Next time you see missing sensors, can you try refreshing the browser and if that does not work, clear the browser cache? I have seen a couple of times were the browser cache seems to show duplicates or hide entities and groups. Based on your set up, I cannot see any reason why the devices would not load in HA. If the browser suggestion does not work, please send me the log files with the lines that look like this:
2018-03-17 08:34:56 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x57, 'controlFlags': 0xa2, 'group': 0xfb, 'address': 40.3F.FC, 'linkdata1': 0x10, 'linkdata2': 0x08, 'linkdata3': 0x44}
I don’t need the lines in between and there should be about 16 of them. When you don’t see all of the devices, do you see the same devices all the time and miss others or is it random?

As for three of the devices showing up wet and two showing up dry, all three devices report as the same model so there should not be a difference in how they act. However, three devices are sending a heartbeat and two devices are not. The three that show a heartbeat are:

28.4F.3D
28.57.BE
2D.60.AC

The two that are not are:

40.38.BB
40.3F.FC

The difference between them is the firmware version. The first three are firmware version 0x41 and the newer ones are firmware version 0x44. I cannot tell the difference yet between them other than that the newer ones don’t send a heartbeat. The only other possible issue could be the link tables. You have the following link table:

CTL Flag	Group	Address	Data 1	Data 2	Data 3
0xe2	0x01	28.4F.3D	0x10	0x08	0x41
0xa2	0xfb	28.4F.3D	0x10	0x08	0x41
0xe2	0x01	28.57.BE	0x10	0x08	0x41
0xa2	0x01	28.57.BE	0x10	0x08	0x41
0xa2	0xfb	28.57.BE	0x10	0x08	0x41
0xa2	0x01	2D.60.AC	0x10	0x08	0x41
0xe2	0x01	2D.60.AC	0x10	0x08	0x41
0xe2	0x01	40.38.BB	0x10	0x08	0x44
0xa2	0x01	40.38.BB	0x10	0x08	0x44
0xa2	0xfb	40.38.BB	0x10	0x08	0x44
0xa2	0x01	40.3F.FC	0x10	0x08	0x44

There is not a direct correlation between the issues you are describing and your link table so I cannot say that you need to ‘fix’ your links but this may start to explain the issues. I assume you set up all your links manually, correct? Based on how the device works, I would have expected to see links to groups 0x01, 0x02 and 0x04. One way to be sure your link tables is correct is to download HouseLinc to a PC, connect your PLM and relink your devices. Unfortunately this will mean you need to go to the apartment and bring a PC or a laptop.

Madelinot · April 1, 2018, 12:36am

Thanks for your response. Refreshing the page or clearing the cache does not do anything, I tried previously. I updated today to the latest HASSio version (0.66.0). Even after multiple reboots (30+), none of my leak sensors and the switch appear in the front-end. None! Not sure what to do now.

I did link them all manually, both ways. Here is my latest log showing the messages you are looking for:

	Line 1: 2018-03-31 20:21:46 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x60, 'address': 49.F8.EE, 'category': 0x03, 'subcategory': 0x15, 'firmware': 0x9e, 'acknak': 0x06}
	Line 2: 2018-03-31 20:21:47 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x69, 'acknak': 0x06}
	Line 4: 2018-03-31 20:21:47 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x57, 'controlFlags': 0xa2, 'group': 0xfb, 'address': 40.3F.FC, 'linkdata1': 0x10, 'linkdata2': 0x08, 'linkdata3': 0x44}
	Line 26: 2018-03-31 20:21:48 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x6a, 'acknak': 0x06}
	Line 28: 2018-03-31 20:21:48 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x57, 'controlFlags': 0xa2, 'group': 0x01, 'address': 2D.60.AC, 'linkdata1': 0x10, 'linkdata2': 0x08, 'linkdata3': 0x41}
	Line 50: 2018-03-31 20:21:49 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x6a, 'acknak': 0x06}
	Line 52: 2018-03-31 20:21:49 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x57, 'controlFlags': 0xe2, 'group': 0x01, 'address': 28.57.BE, 'linkdata1': 0x10, 'linkdata2': 0x08, 'linkdata3': 0x41}
	Line 75: 2018-03-31 20:21:50 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x6a, 'acknak': 0x06}
	Line 77: 2018-03-31 20:21:50 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x57, 'controlFlags': 0xa2, 'group': 0xfb, 'address': 28.57.BE, 'linkdata1': 0x10, 'linkdata2': 0x08, 'linkdata3': 0x41}
	Line 97: 2018-03-31 20:21:51 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x6a, 'acknak': 0x06}
	Line 99: 2018-03-31 20:21:51 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x57, 'controlFlags': 0xe2, 'group': 0x01, 'address': 40.38.BB, 'linkdata1': 0x10, 'linkdata2': 0x08, 'linkdata3': 0x44}
	Line 123: 2018-03-31 20:21:52 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x6a, 'acknak': 0x06}
	Line 125: 2018-03-31 20:21:52 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x57, 'controlFlags': 0xa2, 'group': 0xfb, 'address': 40.38.BB, 'linkdata1': 0x10, 'linkdata2': 0x08, 'linkdata3': 0x44}
	Line 144: 2018-03-31 20:21:54 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x6a, 'acknak': 0x06}
	Line 146: 2018-03-31 20:21:54 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x57, 'controlFlags': 0xe2, 'group': 0x01, 'address': 28.4F.3D, 'linkdata1': 0x10, 'linkdata2': 0x08, 'linkdata3': 0x41}
	Line 168: 2018-03-31 20:21:55 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x6a, 'acknak': 0x06}
	Line 170: 2018-03-31 20:21:55 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x57, 'controlFlags': 0xa2, 'group': 0xfb, 'address': 28.4F.3D, 'linkdata1': 0x10, 'linkdata2': 0x08, 'linkdata3': 0x41}
	Line 187: 2018-03-31 20:21:56 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x6a, 'acknak': 0x06}
	Line 189: 2018-03-31 20:21:56 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x57, 'controlFlags': 0xe2, 'group': 0x01, 'address': 23.7D.6E, 'linkdata1': 0x09, 'linkdata2': 0x0b, 'linkdata3': 0x3a}
	Line 212: 2018-03-31 20:21:57 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x6a, 'acknak': 0x06}
	Line 214: 2018-03-31 20:21:57 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x57, 'controlFlags': 0xa2, 'group': 0xfb, 'address': 23.7D.6E, 'linkdata1': 0x09, 'linkdata2': 0x0b, 'linkdata3': 0x3a}
	Line 231: 2018-03-31 20:21:58 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x6a, 'acknak': 0x06}
	Line 233: 2018-03-31 20:21:58 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x57, 'controlFlags': 0xa2, 'group': 0x01, 'address': 23.7D.6E, 'linkdata1': 0x09, 'linkdata2': 0x0b, 'linkdata3': 0x3a}
	Line 250: 2018-03-31 20:21:59 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x6a, 'acknak': 0x06}
	Line 252: 2018-03-31 20:21:59 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x57, 'controlFlags': 0xa2, 'group': 0x01, 'address': 40.3F.FC, 'linkdata1': 0x10, 'linkdata2': 0x08, 'linkdata3': 0x44}
	Line 269: 2018-03-31 20:22:00 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x6a, 'acknak': 0x15}
	Line 291: 2018-03-31 20:22:01 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x62, 'address': 23.7D.6E, 'flags': 0x00, 'cmd1': 0x19, 'cmd2': 0x00, 'acknak': 0x06}
	Line 292: 2018-03-31 20:22:01 DEBUG (MainThread) [insteonplm.plm] Processing message {'code': 0x50, 'address': 23.7D.6E, 'target': 49.F8.EE, 'flags': 0x20, 'cmd1': 0x13, 'cmd2': 0x00}

Is there any way to upgrade the firmware of these devices? I don’t think so…

I can try to completely erase the PLM, reset everything to factory (including the sensors), and relink everything. But I tried that already. I can run HouseLinc next time I go there.

Thanks again,

teharris1 · April 1, 2018, 1:18am

From the data you just posted, all of your devices should be showing up. I can be 100% sure the underlying library found your switch with address 23.7D.6E. Do you see any error messages in the log at all? I am on 0.66.0 and all 30 of my devices show up as expected.

Madelinot · April 1, 2018, 1:38pm

The switch finally showed up. It shows up once every other reboots or so. But none of the leak sensors are showing up. No error messages in the logs.

Madelinot · April 2, 2018, 2:56am

I don’t understand why this is so flaky and unreliable. I will probably ditch it all soon…

teharris1 · April 2, 2018, 3:37pm

I am very sorry you have having these issues and really want to help. Based on the log files I can be sure the insteonplm module is finding the devices and they can be communicated to. The issue must be on the hass.io side. When devices are missing do you see anything in the log that looks like this:
2018-03-31 21:54:16 DEBUG (MainThread) [insteonplm.plm] Found all link record for device 14627a
2018-03-31 21:54:16 DEBUG (MainThread) [insteonplm.plm] Product data: address 14627a cat: 10 subcat: 08 product_key: 44
2018-03-31 21:54:16 DEBUG (MainThread) [insteonplm.linkedDevices] New INSTEON Device ‘14627a’: Leak Sensor (10:08)
2018-03-31 21:54:16 INFO (MainThread) [homeassistant.components.insteon_plm] New INSTEON PLM device: 14627a (wetLeakSensor) binary_sensor
2018-03-31 21:54:16 INFO (MainThread) [insteonplm.plm] Device with id 14627a added to device list from ALDB data.`
You should see one of these for each of the devices.

tbandzul · April 2, 2018, 6:16pm

@teharris1 I was using hassio version 0.65.0 and everything “seemed to be working”. I updated this morning to 0.66.1 and some things are not working for me anymore. I am not sure if it is a hassio issue as you indicate may be the problem for others, as I am definitely seeing problems in the front end display.

a) A bunch of my switches (about 9 of 32) do not show up on every restart

seems to be same ones
there are duplicate groups in the front end right now for my configuration, so there may be issue with hassio
b) the door sensors show up but stay in an “unknown” state now (they worked in my version 065.0 automations) using “on” and “off” states - as binary_sensors vice just sensors
do I need to add something to configuration for this change?
c) the water sensor shows up but no longer works
d) the motion sensor shows up, but stays “on”

teharris1 · April 2, 2018, 7:21pm

Some of the things you describe can be associated with the upgrade but others not that I can see.
a) This is the biggest concern I have. I cannot find any thing that explains why this is happening. It will be helpful to get logs from you as well to figure out where the breakdown is.
b) The door sensor moving from sensor to binary_sensor has to do with the addition of many additional products into the Insteon Product Database in the underlying library. This should mean the sensor works better than in 0.65.x. I cannot explain why they would show up in the ‘unknown’ state because the default state is ‘off’ or ‘closed’. The device should always have a state and that did not change from 0.65.x to 0.66.0.
c) Can I assume the water sensor is not the leak sensor? What is the cat and subcat of the water sensor?
d) Unless your motion sensor is cat 0x10 subcat 0x16 Motion Sensor II, there should not be any change.

tbandzul · April 2, 2018, 8:09pm

a) I will read above on how to get the logs. Every time I restart now it is random how many items show up in the insteon device file; range from 16 max (same ones each time) to one. I did not have this issue in 0.65.0, - only change I made was to switch to appdaemon3 for dashboard
b) it went from binary_sensor to sensor if that makes a difference. cat: 0x10 subcat: 0x02
c) It is a leak sensor: 2852-222 cat: 0x10 subcat: 0x08. As a note it appears that hassio started adding the group id to the leak sensor; ie; binary_sensor.2df922_2 Why would that be?
d) 2420M Motion Sensor - can’t find the user guide, but it is old version I believe

Note: while reading above I see you say “I hope you are not deleting the insteon_plm_device_info file each time you restart” - I have NOT set such a setting and mine appears to be written new every time.

I captured a log, but it is 1800 lines long and way over the allowed limit. What part of the logfile is the most important to you?

Madelinot · April 2, 2018, 8:50pm

I found this error message in my logs:

2018-04-02 15:30:49 ERROR (MainThread) [homeassistant.core] Error doing job: Exception in callback <bound method PLM._handle_assign_to_all_link_group of <insteonplm.plm.PLM object at 0x73409990>>
Traceback (most recent call last):
  File "uvloop/cbhandles.pyx", line 49, in uvloop.loop.Handle._run
  File "/usr/lib/python3.6/site-packages/insteonplm/plm.py", line 306, in _handle_assign_to_all_link_group
    device.address.human)
AttributeError: 'NoneType' object has no attribute 'address'

It shows up a few times, and seems to always be the same.

tbandzul · April 2, 2018, 10:04pm

Here is the data (hopefully all) for a door sensor and the leak detector pulled out of the file. I trigger each sensor to get a report. The reports show up on an Insteon hub I also have, showing the detection from the door and leak sensors.

2018-04-02 15:06:59 DEBUG (MainThread) [insteonplm.plm] Starting: _get_next_all_link_recor
2018-04-02 15:06:59 INFO (MainThread) [insteonplm.plm] Requesting Next All-Link Record
2018-04-02 15:06:59 DEBUG (MainThread) [insteonplm.plm] Starting: send_msg
2018-04-02 15:06:59 DEBUG (MainThread) [insteonplm.plm] Ending: send_msg
2018-04-02 15:06:59 DEBUG (MainThread) [insteonplm.plm] Ending: _get_next_all_link_recor
2018-04-02 15:06:59 DEBUG (MainThread) [insteonplm.plm] True
2018-04-02 15:06:59 DEBUG (MainThread) [insteonplm.plm] Writing message: {‘code’: 0x6a, ‘acknak’: 0xNone}
2018-04-02 15:06:59 DEBUG (MainThread) [homeassistant.components.switch.insteon_plm] Adding device 15c716 entity lightOnOff to Switch platform
2018-04-02 15:07:00 DEBUG (MainThread) [insteonplm.plm] Starting: data_received
2018-04-02 15:07:00 DEBUG (MainThread) [insteonplm.plm] Received 13 bytes from PLM: b’026a060257e20113e3ed100228’
2018-04-02 15:07:00 DEBUG (MainThread) [insteonplm.plm] Total buffer: b’026a060257e20113e3ed100228’
2018-04-02 15:07:00 DEBUG (MainThread) [insteonplm.plm] Starting: _peel_messages_from_buffer
2018-04-02 15:07:00 DEBUG (MainThread) [insteonplm.plm] Finishing: _peel_messages_from_buffer
2018-04-02 15:07:00 DEBUG (MainThread) [insteonplm.plm] Messages in queue: 2
2018-04-02 15:07:00 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x6a, ‘acknak’: 0x06}
2018-04-02 15:07:00 DEBUG (MainThread) [insteonplm.plm] No callback found for message {‘code’: 0x6a, ‘acknak’: 0x06}
2018-04-02 15:07:00 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x57, ‘controlFlags’: 0xe2, ‘group’: 0x01, ‘address’: 13.E3.ED, ‘linkdata1’: 0x10, ‘linkdata2’: 0x02, ‘linkdata3’: 0x28}
2018-04-02 15:07:00 DEBUG (MainThread) [insteonplm.plm] Last item in self._recv_queue reached.
2018-04-02 15:07:00 DEBUG (MainThread) [insteonplm.plm] Finishing: data_received
2018-04-02 15:07:00 DEBUG (MainThread) [insteonplm.plm] Found all link record for device 13e3ed
2018-04-02 15:07:00 DEBUG (MainThread) [insteonplm.plm] Product data: address 13e3ed cat: 10 subcat: 02 product_key: 28
2018-04-02 15:07:00 DEBUG (MainThread) [insteonplm.aldb] New INSTEON Device ‘13e3ed’: Open/Close Sensor (10:02)
2018-04-02 15:07:00 INFO (MainThread) [homeassistant.components.insteon_plm] New INSTEON PLM device: 13e3ed (generalSensor) sensor
2018-04-02 15:07:00 INFO (MainThread) [insteonplm.plm] Device with id 13e3ed added to device list from ALDB data.

2018-04-02 15:07:02 DEBUG (MainThread) [insteonplm.plm] Starting: _get_next_all_link_recor
2018-04-02 15:07:02 INFO (MainThread) [insteonplm.plm] Requesting Next All-Link Record
2018-04-02 15:07:02 DEBUG (MainThread) [insteonplm.plm] Starting: send_msg
2018-04-02 15:07:02 DEBUG (MainThread) [insteonplm.plm] Ending: send_msg
2018-04-02 15:07:02 DEBUG (MainThread) [insteonplm.plm] Ending: _get_next_all_link_recor
2018-04-02 15:07:02 DEBUG (MainThread) [insteonplm.plm] True
2018-04-02 15:07:02 DEBUG (MainThread) [insteonplm.plm] Writing message: {‘code’: 0x6a, ‘acknak’: 0xNone}
2018-04-02 15:07:03 DEBUG (MainThread) [insteonplm.plm] Starting: data_received
2018-04-02 15:07:03 DEBUG (MainThread) [insteonplm.plm] Received 13 bytes from PLM: b’026a060257e2012df922100841’
2018-04-02 15:07:03 DEBUG (MainThread) [insteonplm.plm] Total buffer: b’026a060257e2012df922100841’
2018-04-02 15:07:03 DEBUG (MainThread) [insteonplm.plm] Starting: _peel_messages_from_buffer
2018-04-02 15:07:03 DEBUG (MainThread) [insteonplm.plm] Finishing: _peel_messages_from_buffer
2018-04-02 15:07:03 DEBUG (MainThread) [insteonplm.plm] Messages in queue: 2
2018-04-02 15:07:03 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x6a, ‘acknak’: 0x06}
2018-04-02 15:07:03 DEBUG (MainThread) [insteonplm.plm] No callback found for message {‘code’: 0x6a, ‘acknak’: 0x06}
2018-04-02 15:07:03 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x57, ‘controlFlags’: 0xe2, ‘group’: 0x01, ‘address’: 2D.F9.22, ‘linkdata1’: 0x10, ‘linkdata2’: 0x08, ‘linkdata3’: 0x41}
2018-04-02 15:07:03 DEBUG (MainThread) [insteonplm.plm] Last item in self._recv_queue reached.
2018-04-02 15:07:03 DEBUG (MainThread) [insteonplm.plm] Finishing: data_received
2018-04-02 15:07:03 WARNING (MainThread) [homeassistant.components.light] Setup of platform flux_led is taking over 10 seconds.
2018-04-02 15:07:03 DEBUG (MainThread) [insteonplm.plm] Found all link record for device 2df922
2018-04-02 15:07:03 DEBUG (MainThread) [insteonplm.plm] Product data: address 2df922 cat: 10 subcat: 08 product_key: 41
2018-04-02 15:07:03 DEBUG (MainThread) [insteonplm.aldb] New INSTEON Device ‘2df922’: Leak Sensor (10:08)
2018-04-02 15:07:03 INFO (MainThread) [homeassistant.components.insteon_plm] New INSTEON PLM device: 2df922 (dryLeakSensor) binary_sensor
2018-04-02 15:07:03 INFO (MainThread) [homeassistant.components.insteon_plm] New INSTEON PLM device: 2df922 (wetLeakSensor) binary_sensor
2018-04-02 15:07:03 INFO (MainThread) [insteonplm.plm] Device with id 2df922 added to device list from ALDB data.

2018-04-02 15:07:03 DEBUG (MainThread) [homeassistant.components.sensor.insteon_plm] Adding device 13e3ed entity generalSensor to Sensor platform

2018-04-02 15:07:06 DEBUG (MainThread) [insteonplm.plm] Starting: _get_next_all_link_recor
2018-04-02 15:07:06 INFO (MainThread) [insteonplm.plm] Requesting Next All-Link Record
2018-04-02 15:07:06 DEBUG (MainThread) [insteonplm.plm] Starting: send_msg
2018-04-02 15:07:06 DEBUG (MainThread) [insteonplm.plm] Ending: send_msg
2018-04-02 15:07:06 DEBUG (MainThread) [insteonplm.plm] Ending: _get_next_all_link_recor
2018-04-02 15:07:06 DEBUG (MainThread) [insteonplm.plm] True
2018-04-02 15:07:06 DEBUG (MainThread) [insteonplm.plm] Writing message: {‘code’: 0x6a, ‘acknak’: 0xNone}
2018-04-02 15:07:06 DEBUG (MainThread) [insteonplm.states] Registered callback for state: generalSensor
2018-04-02 15:07:07 DEBUG (MainThread) [insteonplm.plm] Starting: data_received
2018-04-02 15:07:07 DEBUG (MainThread) [insteonplm.plm] Received 13 bytes from PLM: b’026a060257a20113e3ed000000’
2018-04-02 15:07:07 DEBUG (MainThread) [insteonplm.plm] Total buffer: b’026a060257a20113e3ed000000’
2018-04-02 15:07:07 DEBUG (MainThread) [insteonplm.plm] Starting: _peel_messages_from_buffer
2018-04-02 15:07:07 DEBUG (MainThread) [insteonplm.plm] Finishing: _peel_messages_from_buffer
2018-04-02 15:07:07 DEBUG (MainThread) [insteonplm.plm] Messages in queue: 2
2018-04-02 15:07:07 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x6a, ‘acknak’: 0x06}
2018-04-02 15:07:07 DEBUG (MainThread) [insteonplm.plm] No callback found for message {‘code’: 0x6a, ‘acknak’: 0x06}
2018-04-02 15:07:07 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x57, ‘controlFlags’: 0xa2, ‘group’: 0x01, ‘address’: 13.E3.ED, ‘linkdata1’: 0x00, ‘linkdata2’: 0x00, ‘linkdata3’: 0x00}
2018-04-02 15:07:07 DEBUG (MainThread) [insteonplm.plm] Last item in self._recv_queue reached.
2018-04-02 15:07:07 DEBUG (MainThread) [insteonplm.plm] Finishing: data_received
2018-04-02 15:07:07 DEBUG (MainThread) [insteonplm.plm] Found all link record for device 13e3ed

2018-04-02 15:07:07 DEBUG (MainThread) [homeassistant.components.binary_sensor.insteon_plm] Adding device 2df922 entity wetLeakSensor to Binary Sensor platform

2018-04-02 15:07:34 INFO (MainThread) [insteonplm.plm] Requesting Next All-Link Record
2018-04-02 15:07:34 DEBUG (MainThread) [insteonplm.plm] Starting: send_msg
2018-04-02 15:07:34 DEBUG (MainThread) [insteonplm.plm] Ending: send_msg
2018-04-02 15:07:34 DEBUG (MainThread) [insteonplm.plm] Ending: _get_next_all_link_recor
2018-04-02 15:07:34 DEBUG (MainThread) [insteonplm.plm] True
2018-04-02 15:07:34 DEBUG (MainThread) [insteonplm.plm] Writing message: {‘code’: 0x6a, ‘acknak’: 0xNone}
2018-04-02 15:07:35 DEBUG (MainThread) [insteonplm.plm] Starting: data_received
2018-04-02 15:07:35 DEBUG (MainThread) [insteonplm.plm] Received 13 bytes from PLM: b’026a060257a2022df922000000’
2018-04-02 15:07:35 DEBUG (MainThread) [insteonplm.plm] Total buffer: b’026a060257a2022df922000000’
2018-04-02 15:07:35 DEBUG (MainThread) [insteonplm.plm] Starting: _peel_messages_from_buffer
2018-04-02 15:07:35 DEBUG (MainThread) [insteonplm.plm] Finishing: _peel_messages_from_buffer
2018-04-02 15:07:35 DEBUG (MainThread) [insteonplm.plm] Messages in queue: 2
2018-04-02 15:07:35 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x6a, ‘acknak’: 0x06}
2018-04-02 15:07:35 DEBUG (MainThread) [insteonplm.plm] No callback found for message {‘code’: 0x6a, ‘acknak’: 0x06}
2018-04-02 15:07:35 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x57, ‘controlFlags’: 0xa2, ‘group’: 0x02, ‘address’: 2D.F9.22, ‘linkdata1’: 0x00, ‘linkdata2’: 0x00, ‘linkdata3’: 0x00}
2018-04-02 15:07:35 DEBUG (MainThread) [insteonplm.plm] Last item in self._recv_queue reached.
2018-04-02 15:07:35 DEBUG (MainThread) [insteonplm.plm] Finishing: data_received
2018-04-02 15:07:35 DEBUG (MainThread) [insteonplm.plm] Found all link record for device 2df922

2018-04-02 15:09:28 DEBUG (MainThread) [insteonplm.plm] Starting: data_received
2018-04-02 15:09:28 DEBUG (MainThread) [insteonplm.plm] Received 33 bytes from PLM: b’025013e3ed000001cf1101025013e3ed000001cf1101025013e3ed4483a1451101’
2018-04-02 15:09:28 DEBUG (MainThread) [insteonplm.plm] Total buffer: b’025013e3ed000001cf1101025013e3ed000001cf1101025013e3ed4483a1451101’
2018-04-02 15:09:28 DEBUG (MainThread) [insteonplm.plm] Starting: _peel_messages_from_buffer
2018-04-02 15:09:28 DEBUG (MainThread) [insteonplm.plm] Finishing: _peel_messages_from_buffer
2018-04-02 15:09:28 DEBUG (MainThread) [insteonplm.plm] Messages in queue: 3
2018-04-02 15:09:28 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x50, ‘address’: 13.E3.ED, ‘target’: 00.00.01, ‘flags’: 0xcf, ‘cmd1’: 0x11, ‘cmd2’: 0x01}
2018-04-02 15:09:28 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x50, ‘address’: 13.E3.ED, ‘target’: 00.00.01, ‘flags’: 0xcf, ‘cmd1’: 0x11, ‘cmd2’: 0x01}
2018-04-02 15:09:28 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x50, ‘address’: 13.E3.ED, ‘target’: 44.83.A1, ‘flags’: 0x45, ‘cmd1’: 0x11, ‘cmd2’: 0x01}
2018-04-02 15:09:28 DEBUG (MainThread) [insteonplm.plm] Last item in self._recv_queue reached.
2018-04-02 15:09:28 DEBUG (MainThread) [insteonplm.plm] Finishing: data_received

2018-04-02 15:09:31 DEBUG (MainThread) [insteonplm.plm] Starting: data_received
2018-04-02 15:09:31 DEBUG (MainThread) [insteonplm.plm] Received 22 bytes from PLM: b’025013e3ed000001cf1301025013e3ed000001cf1301’
2018-04-02 15:09:31 DEBUG (MainThread) [insteonplm.plm] Total buffer: b’025013e3ed000001cf1301025013e3ed000001cf1301’
2018-04-02 15:09:31 DEBUG (MainThread) [insteonplm.plm] Starting: _peel_messages_from_buffer
2018-04-02 15:09:31 DEBUG (MainThread) [insteonplm.plm] Finishing: _peel_messages_from_buffer
2018-04-02 15:09:31 DEBUG (MainThread) [insteonplm.plm] Messages in queue: 2
2018-04-02 15:09:31 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x50, ‘address’: 13.E3.ED, ‘target’: 00.00.01, ‘flags’: 0xcf, ‘cmd1’: 0x13, ‘cmd2’: 0x01}
2018-04-02 15:09:31 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x50, ‘address’: 13.E3.ED, ‘target’: 00.00.01, ‘flags’: 0xcf, ‘cmd1’: 0x13, ‘cmd2’: 0x01}
2018-04-02 15:09:31 DEBUG (MainThread) [insteonplm.plm] Last item in self._recv_queue reached.
2018-04-02 15:09:31 DEBUG (MainThread) [insteonplm.plm] Finishing: data_received
2018-04-02 15:09:31 DEBUG (MainThread) [insteonplm.devices] Starting Device._receive_message
2018-04-02 15:09:31 DEBUG (MainThread) [insteonplm.devices] Ending Device._receive_message
2018-04-02 15:09:31 DEBUG (MainThread) [insteonplm.devices] Starting Device._receive_message
2018-04-02 15:09:31 DEBUG (MainThread) [insteonplm.devices] Ending Device._receive_message
2018-04-02 15:09:32 DEBUG (MainThread) [insteonplm.plm] Starting: data_received
2018-04-02 15:09:32 DEBUG (MainThread) [insteonplm.plm] Received 11 bytes from PLM: b’025013e3ed4483a14513ff’
2018-04-02 15:09:32 DEBUG (MainThread) [insteonplm.plm] Total buffer: b’025013e3ed4483a14513ff’
2018-04-02 15:09:32 DEBUG (MainThread) [insteonplm.plm] Starting: _peel_messages_from_buffer
2018-04-02 15:09:32 DEBUG (MainThread) [insteonplm.plm] Finishing: _peel_messages_from_buffer
2018-04-02 15:09:32 DEBUG (MainThread) [insteonplm.plm] Messages in queue: 1
2018-04-02 15:09:32 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x50, ‘address’: 13.E3.ED, ‘target’: 44.83.A1, ‘flags’: 0x45, ‘cmd1’: 0x13, ‘cmd2’: 0xff}
2018-04-02 15:09:32 DEBUG (MainThread) [insteonplm.plm] Last item in self._recv_queue reached.
2018-04-02 15:09:32 DEBUG (MainThread) [insteonplm.plm] Finishing: data_received

2018-04-02 15:57:38 DEBUG (MainThread) [insteonplm.plm] Starting: data_received
2018-04-02 15:57:38 DEBUG (MainThread) [insteonplm.plm] Received 44 bytes from PLM: b’02502df922000002cf110202502df922000002cf110202502df9224483a145110202502df922110202cf0600’
2018-04-02 15:57:38 DEBUG (MainThread) [insteonplm.plm] Total buffer: b’02502df922000002cf110202502df922000002cf110202502df9224483a145110202502df922110202cf0600’
2018-04-02 15:57:38 DEBUG (MainThread) [insteonplm.plm] Starting: _peel_messages_from_buffer
2018-04-02 15:57:38 DEBUG (MainThread) [insteonplm.plm] Finishing: _peel_messages_from_buffer
2018-04-02 15:57:38 DEBUG (MainThread) [insteonplm.plm] Messages in queue: 4
2018-04-02 15:57:38 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x50, ‘address’: 2D.F9.22, ‘target’: 00.00.02, ‘flags’: 0xcf, ‘cmd1’: 0x11, ‘cmd2’: 0x02}
2018-04-02 15:57:38 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x50, ‘address’: 2D.F9.22, ‘target’: 00.00.02, ‘flags’: 0xcf, ‘cmd1’: 0x11, ‘cmd2’: 0x02}
2018-04-02 15:57:38 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x50, ‘address’: 2D.F9.22, ‘target’: 44.83.A1, ‘flags’: 0x45, ‘cmd1’: 0x11, ‘cmd2’: 0x02}
2018-04-02 15:57:38 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x50, ‘address’: 2D.F9.22, ‘target’: 11.02.02, ‘flags’: 0xcf, ‘cmd1’: 0x06, ‘cmd2’: 0x00}
2018-04-02 15:57:38 DEBUG (MainThread) [insteonplm.plm] Last item in self._recv_queue reached.
2018-04-02 15:57:38 DEBUG (MainThread) [insteonplm.plm] Finishing: data_received

2018-04-02 15:57:40 DEBUG (MainThread) [insteonplm.plm] Starting: data_received
2018-04-02 15:57:40 DEBUG (MainThread) [insteonplm.plm] Received 11 bytes from PLM: b’02502df922110202cb0600’
2018-04-02 15:57:40 DEBUG (MainThread) [insteonplm.plm] Total buffer: b’02502df922110202cb0600’
2018-04-02 15:57:40 DEBUG (MainThread) [insteonplm.plm] Starting: _peel_messages_from_buffer
2018-04-02 15:57:40 DEBUG (MainThread) [insteonplm.plm] Finishing: _peel_messages_from_buffer
2018-04-02 15:57:40 DEBUG (MainThread) [insteonplm.plm] Messages in queue: 1
2018-04-02 15:57:40 DEBUG (MainThread) [insteonplm.plm] Processing message {‘code’: 0x50, ‘address’: 2D.F9.22, ‘target’: 11.02.02, ‘flags’: 0xcb, ‘cmd1’: 0x06, ‘cmd2’: 0x00}
2018-04-02 15:57:40 DEBUG (MainThread) [insteonplm.plm] Last item in self._recv_queue reached.
2018-04-02 15:57:40 DEBUG (MainThread) [insteonplm.plm] Finishing: data_received
2018-04-02 15:57:40 DEBUG (MainThread) [insteonplm.devices] Starting Device._receive_message
2018-04-02 15:57:40 DEBUG (MainThread) [insteonplm.devices] Ending Device._receive_message

Obviously didn’t paste it in correctly.

Madelinot · April 2, 2018, 10:43pm

Are your devices linked to both a hub and a PLM at the same time?

tbandzul · April 3, 2018, 12:14am

I have 32 insteon devices which are all connected to a hub (original version) that I have been using for many years. Of those 32 items, I think that I have 24 of them connected to the PLM that I bought just to work with Home Assistant. The hub and the PLM were both getting the messages and triggering events… everything except the voice control worked after the 0.65.0 release (the emulated hue device stopped working) , but now the leak detectors and door sensors are not working in Home assistant. The devices all appear to be showing up again, and the motion detector I have linked seems to be working again.

I do NOT have the version of the hub that works with Home Assistant. I am using the Insteon iPhone App.

teharris1 · April 3, 2018, 1:23am

a) OK, I thing I know the issue but it is very difficult to say with certainty. I am working on a solution now but not 100% sure it will solve the problem.
b) OK, cat 10 subcat 02 is an open/close sensor. Should I be treating that as a door sensor? I see why this happened and can easily put it back to a binary sensor if that is where it belongs.
c) Yes that is expected. The leak sensor is a weird device under the hood. It actually sends a dry message and a wet message as if they are separate states rather than binary opposites. The wet sensor is the 0x02 group which is why the sensor has the _2 postscript.
d) I would really like to see the messages associated with this device. I am looking for any lines in the log that contain “Processing Message” with the device address in them.

tbandzul · April 3, 2018, 2:50am

I created a github account and put the files there so that you get everything. This one appears to have all the linked devices in it. Motion sensor working, leak and door sensors not working.

The insteon_plm_device__info.dat file seems to get cleared every time I restart Home Assistant, it does not appear to be saved between restarts if that is the expected behavior.

Have been trying to get the devices to not show up by restarting, and it is working every time now… lol.

teharris1 · April 4, 2018, 8:06pm

I am reasonably convinced this is a hassio issue given that the problems you are talking about seem to only be reported by hassio users. I just posted an update that will change the device loading process to use the saved devices and the device_override config. This will ensure loads are much more consistent. It will at least eliminate the known issue were the all-link database does not fully load.