MGustin

I think I will just give my own answer on this topic. Now that eisy supports ZigBee and zwave its time to just start saying goodbye to Insteon. Obviously, we all know about the scare we had not that long ago with them, the devices are twice or three times the price what a decent ZigBee costs (honestly, I don't know why I replaced this failing unit with another Insteon - habit I guess). I am sure some of the Insteon die-hards will read this and light me up but oh well. I'm sick of the high prices, I am sick of being charged shipping, I am sick of the quality. I have nearly 100 Insteon devices, been on the platform for a decade or so - I think that gives me the right to say I'm done with Insteon. As these things die and trust me they will die, anyone that owns Insteon knows that, I will replace with something else.

I don't have any LED bulbs on it all are incandescent.

I just put 200 watts on it with not change. I would also note that this is replacing a very old 2474dwh that finally died.

Load is approximately 75W. Query Log: Wed 11/06/2024 05:20:43 PM : [INST-TX-I1 ] 02 62 70 D1 82 0F 19 00 Wed 11/06/2024 05:20:43 PM : [INST-ACK ] 02 62 70.D1.82 0F 19 00 06 LTSREQ (LIGHT) Wed 11/06/2024 05:20:44 PM : [INST-SRX ] 02 50 70.D1.82 43.A7.42 2B 03 00 (00) Wed 11/06/2024 05:20:44 PM : [Std-Direct Ack] 70.D1.82-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Wed 11/06/2024 05:20:44 PM : [D2D EVENT ] Event [70 D1 82 1] [ST] [0] uom=100 prec=0 Wed 11/06/2024 05:20:44 PM : [70 D1 82 1 ] ST 0 (uom=100 prec=0) Wed 11/06/2024 05:20:44 PM : [D2D EVENT ] Event [70 D1 82 1] [OL] [255] uom=100 prec=0 Wed 11/06/2024 05:20:44 PM : [70 D1 82 1 ] OL 255 (uom=100 prec=0) Wed 11/06/2024 05:20:44 PM : [D2D EVENT ] Event [70 D1 82 1] [RR] [31] uom=25 prec=0 Wed 11/06/2024 05:20:44 PM : [70 D1 82 1 ] RR 31 (uom=25 prec=0) Write: Wed 11/06/2024 05:21:51 PM : [70 D1 82 1 ] Link 1 : 0FF0 [E20143A742010001] Writing [E20143A742010001] Wed 11/06/2024 05:21:51 PM : [INST-TX-I2CS] 02 62 70 D1 82 1F 2F 00 00 02 0F F7 08 E2 01 43 A7 42 01 00 01 B0 Wed 11/06/2024 05:21:51 PM : [INST-ACK ] 02 62 70.D1.82 1F 2F 00 00 02 0F F7 08 E2 01 43 A7 42 01 00 01 B0 06 (00) Wed 11/06/2024 05:22:00 PM : [INST-TX-I2CS] 02 62 70 D1 82 1F 2F 00 00 02 0F F7 08 E2 01 43 A7 42 01 00 01 B0 Wed 11/06/2024 05:22:00 PM : [INST-ACK ] 02 62 70.D1.82 1F 2F 00 00 02 0F F7 08 E2 01 43 A7 42 01 00 01 B0 06 (00) Wed 11/06/2024 05:22:09 PM : [INST-TX-I2CS] 02 62 70 D1 82 1F 2F 00 00 02 0F F7 08 E2 01 43 A7 42 01 00 01 B0 Wed 11/06/2024 05:22:09 PM : [INST-ACK ] 02 62 70.D1.82 1F 2F 00 00 02 0F F7 08 E2 01 43 A7 42 01 00 01 B0 06 (00) Wed 11/06/2024 05:22:13 PM : [70 D1 82 1 ] Link 1 : 0FF0 [E20143A742010001] *Failed Writing [E20143A742010001] Wed 11/06/2024 05:22:13 PM : [70 D1 82 1 ] Memory : Write dbAddr=0x0032 [FF] cmd1=0x2E cmd2=0x00 Wed 11/06/2024 05:22:13 PM : [INST-TX-I2CS] 02 62 70 D1 82 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 CC Wed 11/06/2024 05:22:13 PM : [INST-ACK ] 02 62 70.D1.82 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 CC 06 (00) Wed 11/06/2024 05:22:21 PM : [INST-TX-I2CS] 02 62 70 D1 82 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 CC Wed 11/06/2024 05:22:22 PM : [INST-ACK ] 02 62 70.D1.82 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 CC 06 (00) Wed 11/06/2024 05:22:30 PM : [INST-TX-I2CS] 02 62 70 D1 82 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 CC Wed 11/06/2024 05:22:31 PM : [INST-ACK ] 02 62 70.D1.82 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 CC 06 (00) Wed 11/06/2024 05:22:34 PM : [70 D1 82 1 ] Memory : Write dbAddr=0x0032 [FF] cmd1=0x2E cmd2=0x00 - Failed Wed 11/06/2024 05:22:34 PM : [D2D EVENT ] Event [70 D1 82 1] [ERR] [1] uom=0 prec=-1 Wed 11/06/2024 05:22:35 PM : [70 D1 82 1 ] ERR 1 Wed 11/06/2024 05:22:36 PM : [D2D EVENT ] Event [n014_335688] [DISTANC] [6] uom=116 prec=1 Wed 11/06/2024 05:22:36 PM : [n014_335688 ] DISTANC 6 (uom=116 prec=1) Wed 11/06/2024 05:22:36 PM : [D2D EVENT ] Event [n014_335688] [CLIHUM] [8348] uom=22 prec=2 Wed 11/06/2024 05:22:36 PM : [n014_335688 ] CLIHUM 8348 (uom=22 prec=2) Wed 11/06/2024 05:22:36 PM : [D2D EVENT ] Event [n014_335688] [BATLVL] [2531] uom=72 prec=3 Wed 11/06/2024 05:22:36 PM : [n014_335688 ] BATLVL 2531 (uom=72 prec=3)

Brand new device, but yes - did to a factory reset.

It isn't a case of it not finding it - it has always done that and identified it as the correct model. It did toss the link table error when I posted this. I did enter manually and automatically. About 30 min after posting the first post I tried adding it again and it did add. Now if you try to put in any scene it does not write and fails. When you write the changes I get the bellow error but can turn it on and off from UDM without any issues.

I have seen other posts on this topic and the solution was having a range extender or Dual Band device nearby. This is a 2474DWH and I am getting the Cannot determine device link table address when I go to add the device. When I do automatic or manual add the device type is detected almost instantly. I have a 2477D Dual Band switch that is about 5 feet away in the same room and also put a range extender within 2 feet. At a loss...any suggestions on how to troubleshoot?

You will only need your API Key. Copy if just in case so you can drop it in the config but yes, you do not need port forwarding anymore once you upgrade. You also need to make sure you have remote access enabled: PG3 remote access must be configured and active. To configure this, login to My ISY, and under your ISY, use: Select tools | PG3 | Remote Connection

Upgraded without any issues.

Confirming 5.0.3 fixed that issue. Thank you.

Found a new issue. When you attempt to stop Rachio from watering it does not (via Programs / Admin). Let me know if you would like logs PM'd.

Just looked; the upgrade to 5.0.2 must have set it to 600. Thanks for making sure.

Will do.

I can confirm that the upgrade to 5.0.2 did the trick. Watering status is now working. Thank you @Jimbo.Automates!!!

Update not showing in the store: