I am using a 2342-2 8 button mini-remote. This worked perfectly on my ISY system. Current network is 2413u PLM, no hub, HA running in a virtualbox vm on Fedora 41 linux.
I can see the remote in my devices list. The remote shows the PLM as responder 0 in the ALDB and 8 controllers with group 1 - 8 in the ALDB for the remote.
Developer tools shows one listener to the insteon.button_on event (my test automation). When I enter insteon.button_on with address and button in the listen to events. I see the trigger happen every other time I push the button on the remote (it alternates from on to off with each button press).
My automation is created as a manual event with trigger using the same data as the developer tools listen entry, but no trigger actually happens.
I have verified that the remote is listed as 2342-222 with 0x00, 0x1a.
I have a second 2342-2 remote listed as 2444A2WH8 with 0x00, 0x12. It doesn’t work either.
I see how to change the ALDB to link insteon devices together, but I also need to use the remotes to trigger non-insteon devices (zigbee and z-wave) as well.
If you put it in the UI and clucked the run button to test it, this does not use the triggers at all.
You need to test it by causing the action that the trigger represents to test your automation.
I always click the button on the remote to trigger the event, and the event does trigger in the “listen” part of the developer tools, just not in my automation. The developer tools listen, however, only listens to the insteon.button_on/off event for any address or button.
New information:
I have discovered that if I leave out the address portion of the trigger definition in my automation that the automation does indeed run when I click the button on the remote. If I add in the address of the button (and I have verified it many times it is the correct address) No event is triggered.
Problem here is that I have two remotes and without the address part of the definition both remotes trigger the action when I push the button on either one.
Solved! I have discovered that the address is case sensitive and needs to be lower case. I changed my address field to use lower case letters and now it works as expected, also If there are no letters in the hex characters of the address then the address must be enclosed in quotes (").
address: 2EEDE4 => Bad
address: 2eede4 => Good
address: 357628 => Bad
address: “357628” => Good
To HA developers: I believe this is bad behavior. The address should match case insensitive. ie) both 2EEDE4 and 2eede4 should match on the address field, 357628 and “357628” both should also match.