core: Home Assistant 2022.2.2 Insteon Keypad Buttons Broken

The problem

After upgrading to Home Assistant 2022.2.2, I noticed the following issues with my Insteon Keypad (2334-222) button controls:

When I press the “Main” button on the Keypad, Home Assistant turns all buttons on, both when looking at the keypad device in Home Assistant, as well as on the keypad itself.
When I try to turn a keypad button on using Home Assistant, I see the keypad button light up, but in Home Assistant, the toggle turns off a few seconds later - Home Assistant does not appear to think that that the button was actually turned on. This behavior is inconsistent - sometimes the button stays enabled, sometimes it does not.

The previous version of Home Assistant (2021.12.10) exhibits the following (correct) behavior when doing the above:

Pressing the “Main” button only turns on that button, and nothing else.
When turning on a keypad button from Home Assistant, the keypad button turns on, and Home Assistant always recognizes and keeps the toggle enabled.

It appears that the latest version of Home Assistant has, at the very least, broken something with the Insteon keypad buttons. Also, just to note, I have a Hub V2.

What version of Home Assistant Core has the issue?

2022.2.2

What was the last working version of Home Assistant Core?

2021.12.10

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Insteon

Link to integration documentation on our website

https://www.home-assistant.io/integrations/insteon/

Diagnostics information

No diagnostics available

Example YAML snippet

Issue is observable by interacting directly with the device

Anything in the logs that might be useful for us?

No specific errors were observed in the logs

Additional information

This problem is reproducible by doing the following:

Go to Devices -> Keypad Device
Turn on Keypad Main button
Observe other buttons also turn on

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 64 (20 by maintainers)

Most upvoted comments

It should show up in 2022.3.4 or 2022.3.5 so you just need to upgrade to the new version when it comes out.

teharris1 on Mar 10, 2022

Thanks. Also, what is the device type of 37.43.85 (cat and subcat)? Or model number?

Apologies for lack of info. The ID 37.43.85 aligns with an Insteon device model 2635-222 on/off module: https://www.smarthome.com/products/insteon-2635-222-on-off-module

miles267 on Mar 8, 2022

I should have time to look at this issue in the next couple of days. @srolomc and @miles267 can you put the insteon module into debug mode. This is done by putting the following in your configuration.yaml file:


logger:
  default: info
  logs:
    pyinsteon.topics: debug
    pyinsteon.messages: debug

Once you put these entries in the config file, you need to restart HA and let it sit for 15 min or so for the system to start up. This will put a lot of data into the home-assistant.log file, which you can see when you go to Configuration -> Settings -> Logs and press the “Load Full Home Assistant Log” button. Go through a cycle of events that demonstrate the issue then send me the lines from the log file from the timestamp when you started the testing. I don’t need the startup information most likely.

After you have finished sending me the logs you can remove those lines from the config file and restart HA so you don’t overload the log file with data.

teharris1 on Mar 7, 2022

@shoeboo - Yeah I’m really not sure what to say here, in it’s current state things are just unusable for me. Something has clearly changed since the older version is working fine for me, so I’m really at a loss here. I’d much prefer to not stay on an old version of Home Assistant for much longer, but I just don’t have of a choice right now. Is there anything else I can try here? The only thing that I have not done is completely remove and reinstall the integration, which seems like a pain since I will have to rename everything again and make sure the names match up with my automations still, but if anyone things this could fix the problem, I suppose I could try it…

One other thing that I did try is to update to the latest version of Home Assistant, but install pyinsteon version 1.0.13 following the instructions laid out earlier in this post. Everything works fine when I do this, so it seems like a bug was introduced between versions 1.0.13 and 1.0.16.

srolomc on Mar 5, 2022

So reporting back - I just updated to version 2022.3.1, and things overall seem worse now. The issue with states not being correctly reflected in Home Assistant is causing a lot of issues. Here are some of my observations:

I turn a light on that triggers the main keypad button backlight to turn on.
I observe the physical main keypad button light up.
I observe the main keypad button state transition to “On”
I turn on another light that triggers a non-main keypad button to light up.
I observe the physical non-main keypad button light up. I also observe that the physical main keypad button is still lit.
In Home Assistant, the state of the non-main keypad button transitions to “On”
Unexpectedly, in Home Assistant, the state of the main keypad button transitions to “Off”

The last item in the bulleted list above is a big problem - Home Assistant thinks that the main button was shut off for some reason, even though it wasn’t, which ends up triggering another automation that I have. I also notice that the non-main keypad button backlight does not register a transition to the “off” state when it should have been turned off by an automation. This is definitely not correct behavior.

@teharris1 - Any thoughts here? There does still seem to be an issue with registering keypad states in Home Assistant. I do want to stress that this all works perfectly fine in version 2021.12.10.

srolomc on Mar 5, 2022

I appreciate you getting back, and I do understand that all of this is being done on everyone’s own time, so help is always appreciated. I just reworked a bunch of my automations - I will take some time to test them, first with 2021.12.10, and then I’ll try them with the latest version. I do want to point out, though, that I do believe there is still a bug. I do feel like Home Assistant should be able to register button state changes as it did in version 2021.12.10, and that capability not working does seem like a real issue, at least in my mind.

I do not think I am ready to close out this issue until we at least have some more discussion about the expected behavior here, as I do think a problem still exists.

srolomc on Mar 4, 2022