Cannot pair Insteon 240V relay, also how to get and modify on hub schedules

hainhi · April 29, 2022, 2:11am

I recently switched over to HA after Insteon shut down and all my devices showed up except for one - my Insteon 2477SA1 INSTEON Dual-Band 220V / 240V 30-AMP Load Controller Normally Open Relay. Before Insteon shutdown, I had an interesting failure condition where the relay would never turn off according to schedule but always turn on, even if I moved the hub right next to it (and was within feet of another switch which may have bee relaying the RF signal for it). What is strange is that the relay ALWAYS turns on in the morning, but after some time it was less and less reliable at turning off in the evening until it just stopped altogether one day. My schedule was always on in the morning and off in the evening - never changed it.

I downloaded Insteon-terminal to see if I could at least see the “pairing” messages from the unit (after holding down the setup button). Here is the output with logging level DEBUG after modem.startWatch():

15:33:23.540 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x6A|ACK/NACK:0x06|
modem got msg: IN:Cmd:0x6A|ACK/NACK:0x06|
15:33:23.553 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x57|RecordFlags:0xEB|ALLLinkGroup:0x00|LinkAddr:33.51.AD|LinkData1:0x01|LinkData2:0x07|LinkData3:0x4A|
modem got msg: IN:Cmd:0x57|RecordFlags:0xEB|ALLLinkGroup:0x00|LinkAddr:33.51.AD|LinkData1:0x01|LinkData2:0x07|LinkData3:0x4A|
15:33:23.556 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x6A|ACK/NACK:0x06|
modem got msg: IN:Cmd:0x6A|ACK/NACK:0x06|
15:33:23.557 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:33.51.AD|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
modem got msg: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:33.51.AD|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
15:33:23.560 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x6A|ACK/NACK:0x06|
modem got msg: IN:Cmd:0x6A|ACK/NACK:0x06|
15:33:23.562 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:39.4C.12|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
modem got msg: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:39.4C.12|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
15:33:23.563 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x6A|ACK/NACK:0x06|
modem got msg: IN:Cmd:0x6A|ACK/NACK:0x06|
15:33:23.564 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x00|LinkAddr:32.2E.59|LinkData1:0x01|LinkData2:0x38|LinkData3:0x43|
modem got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x00|LinkAddr:32.2E.59|LinkData1:0x01|LinkData2:0x38|LinkData3:0x43|
15:33:23.564 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x6A|ACK/NACK:0x06|
modem got msg: IN:Cmd:0x6A|ACK/NACK:0x06|
15:33:23.565 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:32.2E.59|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
modem got msg: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:32.2E.59|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
15:33:23.565 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x6A|ACK/NACK:0x06|
modem got msg: IN:Cmd:0x6A|ACK/NACK:0x06|
15:33:23.565 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x00|LinkAddr:58.56.8F|LinkData1:0x01|LinkData2:0x2A|LinkData3:0x45|
modem got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x00|LinkAddr:58.56.8F|LinkData1:0x01|LinkData2:0x2A|LinkData3:0x45|
15:33:23.565 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x6A|ACK/NACK:0x06|
modem got msg: IN:Cmd:0x6A|ACK/NACK:0x06|
15:33:23.566 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:58.56.8F|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
modem got msg: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:58.56.8F|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
15:33:23.566 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x6A|ACK/NACK:0x15|
modem got msg: IN:Cmd:0x6A|ACK/NACK:0x15|
15:33:23.566 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x7F|Command2:0x02|ACK/NACK:0x06|
modem got msg: IN:Cmd:0x7F|Command2:0x02|ACK/NACK:0x06|

Since I’ve already had to replace my hub once and since Insteon is out of business, I thought I would post here with this info before I starting changing anything in the hub configuration. Is there a low risk way to add this to HA (and also if anyone knows to test communication using Insteon-terminal) sop I can schedule it to turn off in the evening?

I also had a question regarding the schedules in the hub. Is there a way I can see it with either HA or Insteon-terminal? Also, can I modify it? I just have two things it controls and at this point if I can’t modify it I’m happy just to add a schedule in HA to turn off the relay (assuming I can control and actually turn it off).

Thanks in advance for any insight you all can provide.

autocreations · June 16, 2022, 7:37pm

I ran in to this same problem and have not been able to get the device recognized by HASS. Have you managed to get it working since posting?

Thanks.

rfmcmanus · August 17, 2022, 11:27pm

Updated to HA 2022.8.5 today and voila my 2477SA load controller appeared. Working great in my automation. I had added it to HA last month and waited for this HA update to get to use it.