I have a six button keypad switch in my ensuite that I am using to control the ensuite fan. The on and off buttons turn the fan on and off. The other four buttons are labelled as 15min, 30min, 1hour, 2hour. These are controllers in scenes with the on/off buttons set up to respond. So if any of the buttons are pressed the fan comes one. Also the hot water circulation pump is activated. And if the water closet door is open it turns that on as well. The water closet has a Lutron Z-wave switch that I bought when Insteon went out of business years ago. When any of these four buttons are pressed they activate a timing program in my EISY to turn off the fan scene that is running in the time listed on the button.

I was gifted a brand new Insteon On/Off switch in March. Tonight I finally decided what I wanted to do with it. Since my wife and I always select the 2 hour option I figured I would put this switch in the place of the six button keypad and then move the keypad to the powder room on the main floor to use the timer functions on that fan. I want to put a switch here because I have a Zooz 4 in 1 zwave sensor on the way that I plan to use the motion sensor to turn the hot water circulation on and the humidity sensor to turn the fans on. Just like the setup I have in the main bathroom.

I removed the keypad and installed the switch. I then added the device in the admin console. I was able to turn it on and off from the console. So I created a new scene to get it to control the circulation pump as well as the water closet fan. The first oddity was that the water closet fan would not update the command to "on" in the scene. I could do all the other commands (off, query, etc), but not on. This was minor. I plan to swap out all my Lutron devices with either Insteon or a device that follow proper z-wave protocols.

I ran into an issue when I tried to operate the switch manually. The status did not change in the admin console. So I tried to operate it with the console and it worked fine, but whenever I operated it manually it did not activate anything other device in the scene or update its status on the console. I tried a query and that worked. I opened the event viewer and when i sent commands or did a query I could see the traffic to device, but nothing if operated manually.

Is there something I should try to troubleshoot this? Or do I just have a bad device? I ended up putting the keypad back and restoring my IoX with a backup I made before swapping out the device.

Cheers,

K

Is this an i3 keypad?

No, the working keypad is from long before i3 ever became a thing. The switch that isn't working is also not an i3.

K

It likely needed a factory reset or it was defective. When including must use remove existing links.

I built a "test rig" with some spare parts. Its a power cable I cut and a plastic electrical box. I was then able to plug it in easily to test it. I did a factory reset with the air gap as per the instructions and then added it to my IoX again. Same issue. Responds to queries and sent instructions, but does not send a status change when operated manually.

Calling this one defective.

Thank you,

K

Well, I was wrong. I purchased a new on/off switch and put it into my test rig. It acts exactly the same way.

I added it to the admin console and that worked. I can once again control and query it from the EISY, but when I operate it manually it does not update its status. Since this is a brand new device I am sure that the problem is not the switch itself.

I now have two good, but not really working switches.

K

I'm starting to think it could be your PLM. Do you have a spare on hand?

Not a good one. I originally had a USB PLM that was connected to a Raspberry Pi. I then upgraded to an ISY994 and bought a Serial PLM to go with it. When I upgraded to the EISY I used the USB PLM, but a couple years ago it failed and I switched to the serial PLM.

K

@K-bert , please try performing a device link table read/compare (right click device on Console tree, select Diagnostics/Show device Links Table). Examples below. Bonus is you can have event viewer open on "Level 3" to record communications.

Please post the resulting table and the event viewer contents.

The Link table will show us whether you have the correct links in the device (Please provide current PLM address). The event viewer will show the communication progression, quality (hops remaining), and any errors encountered.

The PLM also requires a link in it's table, but that's a little harder to come by. Please post the above and we'll see if a PLM table read is necessary.

The examples below show a link table for a device that is linked ONLY to the PLM (53.BC.3A). It is the absolute minimum # of links for a device to function properly.

Link Table Read Selection

Link Table Contents

Event Viewer Communications

Tue 10/27/2026 09:47:12 AM : [INST-TX-I2  ] 02 62 18 93 83 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2
Tue 10/27/2026 09:47:12 AM : [INST-ACK    ] 02 62 18.93.83 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06        (00)
Tue 10/27/2026 09:47:12 AM : [INST-SRX    ] 02 50 18.93.83 53.BC.3A 2F 2F 00           (00)
Tue 10/27/2026 09:47:12 AM : [Std-Direct Ack] 18.93.83-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Tue 10/27/2026 09:47:12 AM : [INST-ERX    ] 02 51 18 93 83 53 BC 3A 15 2F 00 01 01 0F FF 01 A2 00 53 BC 3A FF 1F 01 C2 
Tue 10/27/2026 09:47:12 AM : [Ext-Direct  ] 18.93.83-->ISY/PLM Group=0, Max Hops=1, Hops Left=1
Tue 10/27/2026 09:47:12 AM : [INST-TX-I2  ] 02 62 18 93 83 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA
Tue 10/27/2026 09:47:12 AM : [INST-ACK    ] 02 62 18.93.83 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA 06        (00)
Tue 10/27/2026 09:47:13 AM : [INST-SRX    ] 02 50 18.93.83 53.BC.3A 2F 2F 00           (00)
Tue 10/27/2026 09:47:13 AM : [Std-Direct Ack] 18.93.83-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Tue 10/27/2026 09:47:13 AM : [INST-ERX    ] 02 51 18 93 83 53 BC 3A 15 2F 00 01 01 0F F7 01 E2 01 53 BC 3A 01 00 01 CA 
Tue 10/27/2026 09:47:13 AM : [Ext-Direct  ] 18.93.83-->ISY/PLM Group=0, Max Hops=1, Hops Left=1
Tue 10/27/2026 09:47:13 AM : [INST-TX-I2  ] 02 62 18 93 83 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2
Tue 10/27/2026 09:47:13 AM : [INST-ACK    ] 02 62 18.93.83 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06        (00)
Tue 10/27/2026 09:47:14 AM : [INST-SRX    ] 02 50 18.93.83 53.BC.3A 2F 2F 00           (00)
Tue 10/27/2026 09:47:14 AM : [Std-Direct Ack] 18.93.83-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Tue 10/27/2026 09:47:14 AM : [INST-ERX    ] 02 51 18 93 83 53 BC 3A 15 2F 00 01 01 0F EF 01 00 00 00 00 00 00 00 00 D2 
Tue 10/27/2026 09:47:14 AM : [Ext-Direct  ] 18.93.83-->ISY/PLM Group=0, Max Hops=1, Hops Left=1
Tue 10/27/2026 09:47:15 AM : [All         ] Writing 0 bytes to devices
Tue 10/27/2026 09:47:15 AM : [All         ] Writing 0 bytes to devices

With the first switch I did look at the event view, and there was no event shown when the switch was operated manually. I have not done this with the new switch. I am not home at the moment so I cannot do the event viewer as I cannot operate the switch.

I have opened a ticket with UD and have been walked through finding the device int he PLM links table. It was listed twice:

133 : 0085 : E2 00 71.FC.E9 02 2A 45

134 : 0086 : A2 01 71.FC.E9 02 2A 45

The PLM address is 45.80.E2 v9E

K

@K-bert , your link table read produced gibberish for that device. I'm guessing that if you try this again with the event viewer open you will see poor communications and the data will be different.

If you are still running your "test rig", try plugging it in close to the PLM.

Edit: The PLM links you posted look correct. If the PLM sees a valid communication from the device it should register it (134 : 0086 : A2 01 71.FC.E9 02 2A 45). My guess is that your communication is so corrupted the PLM is not recognizing it.

Edited Thursday at 03:36 PM5 days by IndyMike

I can try that tonight.

As I said I do have a ticket open. I sent the link table image to them as well and have been told that the link table looking like it does is a bug in AC. I will be shipping one of the switches to UD tomorrow so they can test it.

Provided this thread is still open at that point I will keep updating what happens.

K

25 minutes ago, K-bert said:

I can try that tonight.

As I said I do have a ticket open. I sent the link table image to them as well and have been told that the link table looking like it does is a bug in AC. I will be shipping one of the switches to UD tomorrow so they can test it.

Provided this thread is still open at that point I will keep updating what happens.

K

Curious - I have seen posts regarding issues with the EISY-UI, but nothing regarding IOX. I would think if there were a bug in IOX you would have a lot of company with issues.

Please do post back where this leads