It will take a while for it to show up. Give it 20 minutes then let me know. Removing those two files removed all known device information from the underlying library. It can talk 1 minute per device and it has to review each device one at a time. So if the KeyPadLinc is the last device it may be 15 or 20 minutes before it appears in HA.
Here what i found:
- i can control all the buttons of the keypadlinc from the HA frontend.
- if a change the state of a button from the HA frontend and toggle it on the pad, HA can’t notice it.
- If a change the state of a button ON THE KEYPAD, HA notice it and can toggle it from HA or KEYPAD.
pastebin did not let me paste all the log.
I am confused because I see it working as I would expect:
2020-05-21 13:45:28 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x50, address: 50a331, target: 000003, flags: 0xc3, cmd1: 0x13, cmd2: 0x00
2020-05-21 13:45:28 DEBUG (MainThread) [pyinsteon.topics] Topic: 50a331.3.off.all_link_broadcast data: {'cmd1': 19, 'cmd2': 0, 'target': 000003, 'user_data': None, 'hops_left': 0}
2020-05-21 13:45:28 DEBUG (MainThread) [pyinsteon.topics] Topic: handler.50a331.3.off.all_link_broadcast data: {'on_level': 0}
2020-05-21 13:45:28 DEBUG (MainThread) [pyinsteon.topics] Topic: subscriber_50a331_off_3_broadcast data: {'on_level': 0}
2020-05-21 13:45:28 DEBUG (MainThread) [pyinsteon.topics] Topic: state_50a331_on_off_switch_a_3 data: {'name': 'on_off_switch_a', 'address': '50a331', 'value': 0, 'group': 3}
2020-05-21 13:45:28 DEBUG (MainThread) [custom_components.insteon2.insteon_entity] Received update for device 50a331 group 3 value 0
2020-05-21 13:45:28 DEBUG (MainThread) [pyinsteon.topics] Topic: event_50a331_3_off_event data: {'name': 'off_event', 'address': '50a331', 'group': 3, 'button': 'on_off_switch_a'}
2020-05-21 13:45:28 DEBUG (MainThread) [custom_components.insteon2.utils] Firing event insteon.button_off with {'address': '50a331', 'button': 'a'}
This says that you pressed button A on the KeyPadLinc and Home Assistant saw the update as expected. However, in your logs I see a lot of error messages that look like this:
2020-05-21 13:45:14 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 275, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
File "aiohttp\_http_parser.pyx", line 523, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: invalid HTTP method
2020-05-21 13:45:16 ERROR (MainThread) [root] Uncaught exception
Traceback (most recent call last):
File "av/container/output.pyx", line 22, in av.container.output.close_output
File "av/container/core.pyx", line 267, in av.container.core.Container.err_check
File "av/error.pyx", line 328, in av.error.err_check
File "av/container/pyio.pyx", line 39, in av.container.pyio.pyio_write_gil
TypeError: 'NoneType' object is not callable
I do not know what could be causing these errors but I am sure it is not Insteon related. Is it possible that your frontend configuration has a problem?
By the way, am I correct in believing this is a 6 button KeyPadLinc Switch?
This is new on 110, i remember this issue was on 109 when those errors wasn’t there.
I doubt is a front end issue i don’t have many tweaks but i will check it disabling my customs.
yes 6 buttons,
Based on this line in the logs, Home Assistant received the update from button A when it was turned off. If the front end did not respond to that change it is not due to the insteon2 component.
i’ll try a couples tricks and i let you know if i fix it.
Keep in mind, in 0.109 the device was likely configured as a cat: 0x00 subcat: 0x00 rather than the correct device. So it may not be correct to say the issue in 109 is the same as it is now in 110.
yes i know. in 109 the device didn’t updates on HA either in 110 completely disappears because the cat issue.