I have 10 i3 KPLs already in the eisy. They all correctly show 5 nodes, 4 buttons 1, B, C, D and 1 Flags. These where added before I started using Eisy UI. But!!!, I think I added one on the eisy ui before the latest update and it was correct.

Current firmware:

Tonight I added another i3 4-button KPL and it keeps coming in with 6 nodes: 1, A, B, C, D, Flags. Nodes 1 and A respond the same as seen in the ui. It should show 1, B, C, D and Flags. I have not yet made scenes (groups) from the recently added KPL as it is not right.

I have deleted it, rebooted the eisy via menu, factory reset the KPL, yet it didn't fix it. I also unplugged eisy and let it come back up, factory reset the device again, still didn't fix it. The newly added KPL keeps coming up with one too many nodes.

Wrong:

The other 10 already in my system are fine, 1, B, C, D, Flags.

Correct:

Too see if I have a bad kpl, I added another i3 4 Button KPL, but the result is the same, 1 too many nodes.

All KPLs where bought at the same time (a year or so ago), so I think it's an isy issue not an Insteon issue. But I could be wrong. :/

Edited October 27Oct 27 by nowandthen

Not a bug, this is the new implementation. For i3 the load and the buttons can be detached or attached to any other button. so Load + Buttons + flags. delete and re-add the others to split the load out of A

I'm sorry but this is not working as before.

Here is my group (scene). As you can see, when button C is activated, button B and D are set to off, yet button B is still lit.

I didn't add the goofy button 1 that seems to be the same as button A in this new version of i3 programming code.

And when I go to check the setting for button B, or any button for that matter, it always shows "i_relay" whatever that means. Previously I changed it to Insteon so I have the option to set the button to On or Off, and set the number of retries (which historically has not mattered to me). But when I go back. it shows "i_relay" which does not allow any settings with respect to on of off.

Is anyone asking for the latest i3 firmaware? suggest to go back to the previous version until the bugs are worked out on this version. Something is not right with this firmware.

I have tried and tried and can't make the 13 KPL behave like the other 10 I already have up and running, added under prior version of eisy/Insteon firmware.

This is painful, as I have 12 of these keypads at $80 each.

I think Insteon has given you bad code or bad instructions.

I'll send you a KPL and my code if that helps.

Or... it's an Eisy Ui issue. I don' believe I have added and set up an i3 KPL using Eisy UI, only Console.

Edited Wednesday at 02:35 AM5 days by nowandthen

10 hours ago, nowandthen said:

I didn't add the goofy button 1 that seems to be the same as button A in this new version of i3 programming code.

It is not the same, the i3 the load (1) and Buttons are separate. The device itself has it's own "internal scene" which can link a button to the load. But this does not translate to an ISY scene. While this may have sort of worked when linked to button A, it completely broke when the load was set to another button. When creating an eisy scene both the load and the button must be included, even if they are linked in the "internal scene"

However there may be an issue with the version number. v0.56 appears to behave differently than v.0.58. Which version do you have?

Edit: I think I found an issue with scene links. Will be in staging soon, but still needs tests on my production controller.

Fix will require write changes from the Device Nodes to fix scene links

All are v .58.

More information:

I have been watching the LEDs on the face of the switch. Thinking they reflect the state of each button in the eisy, but they do not.

I started watching the state (ON or OFF) in the eisy browser window. In the browser window; as I clicked each button, one by one, the state of the buttons are behaving as programmed, the button that is pressed shows ON and all others show OFF, however, the LEDs on the face of the switch are not reflecting the state in the eisy, they are staying on (well most are not behaving, button C and D work between each other but not with button B as programeed). When I query any button that is ON but the eisy thinks is OFF, the eisy then changes that button to ON.

Am I missing a setting somewhere? There are a lot of settings for these switches, in a lot of places.

I compared the FLAGS settings of a switch that stays in sync between it and eisy to the switch I am trying to add, which does not stay in sync. The settings are the same.

I don't see a "write updates to device" or perhaps more importantly "restore device".

Edit: To make sure I didn't have a defective switch, I added and set up the other "new" i3 keypad. Same behavior, switch not responding to what eisy thinks it should be/do. And buttons C and D function correctly on both switches.

Edited Wednesday at 04:02 PM4 days by nowandthen

39 minutes ago, nowandthen said:

All are v .58.

More information:

I have been watching the LEDs on the face of the switch. Thinking they reflect the state of each button in the eisy, but they do not.

I started watching the state (ON or OFF) in the eisy browser window. In the browser window; as I clicked each button, one by one, the state of the buttons are behaving as programmed, the button that is pressed shows ON and all others show OFF, however, the LEDs on the face of the switch are not reflecting the state in the eisy, they are staying on (well most are not behaving, button C and D work between each other but not with button B as programeed). When I query any button that is ON but the eisy thinks is OFF, the eisy then changes that button to ON.

Am I missing a setting somewhere? There are a lot of settings for these switches, in a lot of places.

I compared the FLAGS settings of a switch that stays in sync between it and eisy to the switch I am trying to add, which does not stay in sync. The settings are the same.

I don't see a "write updates to device" or perhaps more importantly "restore device".

Edit: To make sure I didn't have a defective switch, I added and set up the other "new" i3 keypad. Same behavior, switch not responding to what eisy thinks it should be/do. And buttons C and D function correctly on both switches.

After the next release (likely staging today), Right click node > Configuration. > Write Updates. This should fix the scenes. Worst case remove from eisy + factory reset (air gap 10 sec + long press) then add back to eisy.

The status prediction is working (insteon does not send status back so it need to be predicted). The issue was the writing scenes and responding to scenes.

Hi Javi,

Is the next release posting soon?, Thanks.

In staging now

Working on Sunday!!! Unexpected dedication! Thanks!