John Chen

@IndyMike To update the latest status for deleting and adding home profile on the Google Home, then linking Universal Device to the home. Google Home is now able to control each device accordingly but not for the scene, which was indicated offline on the Google Home dashboard. Restarting Google Home APP only worked for a single control for the scene, afterward the scene became offline again. At that time, there was NO error log on the admin console, where the scene was still alive and act accordingly for the request. Overall status is Devices == (good) == PLM == (good) == ISY994 == (good) == ISY potal == (???) == Google Home I will update the phenomenon to UDI team despite It seems the issue goes to Google Home though. Hopefully we get to dig and capture something informative on the ISY portal, which is the bridge between ISY994 and Google. Thanks for all the help John

@IndyMike Many thanks for the help !! Before submitting ticket to UDI team, I am planning to have one more shot by moving the google home profile and start over from scratch to see if it is able to recover the good state. And in case, if ISY really has problem working with google home and cannot resolve before long, I might move to alternative like Home Assistance. Any better suggestion from you for the automation control that is compatible with the PLM module ? Thanks, John

@IndyMike Much appreciate for the deep diving for the link table. I did another check step by step in my deployment below Devices === PLM === ISY994 === ISY potal === Google Home 1. linked all devices to PLM successfully 2. able to control each device via admin console, and device act promptly 3. able to control each device via ISY WEB portal (my.isy.io) 4. link connectivity to google home, some devices lost link to PLM ... So you probably right about it that the request from google home to UD somehow broke the link of the device, which is not always to be the same one from trial to trial... I don't understand given there is no problem with the the PLM and ISY994, then how come the out of band request from google could possibly jeopardize the link table of the device ? Is it possible anything went wrong in the ISY portal (my.isy.io) when handling the request from google ? any suggestion to debug on the ISY portal along with google ? for which I confirmed no problem with directly control on the WEB portal. At last, sorry that I am not sure about the UDI that you are referring to. Are you saying it's could be an UD (Univseral Device) issue ? If that's the case, could you shed some light on how to file the case for UDI problem ? Thanks for your time, John

@IndyMike I've moved the PLM and ISY994 to the other outlet and doing physical push button join for some dead devices for quick trial. The good news is that they get back to live and being able to prompt action when I control via admin console. Looks like there was indeed some unknown constant noise interference near where the PLM was. Thanks for the suggestion !!! I went a bit further by linking the device to Google Home via the ISY portal (my.isy.io), and the bad news is that I still cannot control the device via google home, meanwhile the admin console prompt me same error, "Unable to communicate to the device" but with different logs from ones before, where the device responded to PLM with NACK, and never get to recover until I pushed button join it once again. The event logs below showed the device was good after initially join, and respond NACK to the request and stayed in bad state .... I notice the hops is different between good and bad, does it has anything to do with the issue ? /* control a single device via admin console successfully, device ack to PLM */ 06/04/2024 21:23:58 : [50.CA.E7 00] Device already added, ignored 06/04/2024 21:34:12 : [INST-TX-I1 ] 02 62 50 CA E7 0F 13 00 06/04/2024 21:34:12 : [INST-ACK ] 02 62 50.CA.E7 0F 13 00 06 LTOFFRR(00) 06/04/2024 21:34:13 : [INST-SRX ] 02 50 50.CA.E7 52.65.0D 2B 13 00 LTOFFRR(00) 06/04/2024 21:34:13 : [Std-Direct Ack] 50.CA.E7-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 06/04/2024 21:34:13 : [D2D EVENT ] Event [50 CA E7 1] [ERR] [0] uom=0 prec=-1 06/04/2024 21:34:13 : [ 50 CA E7 1] ERR 0 06/04/2024 21:34:14 : [INST-TX-I1 ] 02 62 50 CA E7 0F 11 FF 06/04/2024 21:34:14 : [INST-ACK ] 02 62 50.CA.E7 0F 11 FF 06 LTONRR (FF) 06/04/2024 21:34:14 : [INST-SRX ] 02 50 50.CA.E7 52.65.0D 2B 11 FF LTONRR (FF) 06/04/2024 21:34:14 : [Std-Direct Ack] 50.CA.E7-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 06/04/2024 21:34:14 : [D2D EVENT ] Event [50 CA E7 1] [ST] [255] uom=10 /* control the same device through Google home */ 06/04/2024 22:09:15 : [INST-TX-I1 ] 02 62 50 CA E7 0F 13 00 06/04/2024 22:09:15 : [INST-ACK ] 02 62 50.CA.E7 0F 13 00 06 LTOFFRR(00) 06/04/2024 22:09:15 : [INST-SRX ] 02 50 50.CA.E7 52.65.0D AF 13 FF LTOFFRR(FF) 06/04/2024 22:09:15 : [Std-Direct Nack] 50.CA.E7-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 06/04/2024 22:09:15 : [D2D EVENT ] Event [50 CA E7 1] [ERR] [1] uom=0 prec=-1 06/04/2024 22:09:15 : [ 50 CA E7 1] ERR 1 /* control via admin console again, which edned up error with not able to communicate, the device send NACK to PLM */ 06/04/2024 22:11:32 : [INST-TX-I1 ] 02 62 50 CA E7 0F 13 00 06/04/2024 22:11:32 : [INST-ACK ] 02 62 50.CA.E7 0F 13 00 06 LTOFFRR(00) 06/04/2024 22:11:32 : [INST-SRX ] 02 50 50.CA.E7 52.65.0D AF 13 FF LTOFFRR(FF) 06/04/2024 22:11:32 : [Std-Direct Nack] 50.CA.E7-->ISY/PLM Group=0, Max Hops=3, Hops Left=3

With no lock, restoring device did not worked for me. I have to physically push the set button on the device to recover the link to PLM in between .......

@IndyMike@Techman many thanks for the comment. Sure, I will give it a shot by moving PLM to other outlet in my house. Before that, a quick question, for those being unable communicated devices, do I need to manually add them to the PLM by physically push the set button each time I switch the PLM from one place to another ? Or there is an efficient way to add them on the admin console, like restoring the device ? It will be costy to walk around the house for reaching each device for the test. Many thanks John

@IndyMike Hi Mike, Thanks for Reading my log and showing me what it is supposed to be in the good state. Some questions 1) Given the scene worked without ack, and like you said the controller (device) of the scene shall be able to receive the command from PLM and act accordingly. So the missing ack from a stand alone device might just cause not sync with the actual status it was ? But it turned out the stand alone did not act to the command on / off ? 2) I manually turn on a device that was indicated NOT communicated on the admin console, but I was able to fetch the correct status on the console. I can see the same correct status on the Google Home Dashboard. Does the device respond to the status fetch request from PLM ? If that's case, does it imply the PLM somehow is able to hear the device ? 06/04/2024 01:05:35 : [ 50 D3 E9 1] ERR 1 /* fail to communicated */ 06/04/2024 01:06:03 : [ 50 D3 E9 1] DON 0 /* the status is still correct after I manually turn it on */ 06/04/2024 01:06:03 : [ 50 D3 E9 1] ERR 0 3) the device and the PLM shall be dual band capable, as far as my understanding, PLM is just one way of the communication between the device, is there an alternative wireless communication for insteon device ? Please correct me if I get it wrong. Anyway, I will move the PLM to some other outlet for a shot. Thanks again for your time and the analysis. Thanks, John

Hi Jason, Thanks for the experience sharing, but that seems not my case here, which have lasted for weeks and never get to recover. >.< Thanks, John

Hi Brain, Observations for the questions 1) it did not work even I only power cycle PLM module 2) The PLM module revision is 2.5 1119. It has been running for more than 2 year since installation. 3) I am sure the linked device is dual band capable. But not sure the PLM module .. And some new observations, where I got two devices (50.CA.A5 and 54.25.B0) in a scene (00.00.11), I was testing on / off to each device individually, and both ended up fail, but system prompt error of "unable to communicated" for the second one. Strange thing is that when I was testing the scene that the two failure devices were grouped, it worked. I cannot figure out the phenomenon. Sometimes even it worked but with huge delay (couple minutes) for the switch turning on / off. Event Logs are as below. I can tell the command for LTONRR and LTOFFRR are for on and off respectively but the ERR 1, is it informative or just generic error code for unknown case? 06/02/2024 00:38:28 : [INST-TX-I1 ] 02 62 50 CA A5 0F 11 FF 06/02/2024 00:38:28 : [INST-ACK ] 02 62 50.CA.A5 0F 11 FF 06 LTONRR (FF) 06/02/2024 00:39:13 : [INST-TX-I1 ] 02 62 50 CA A5 0F 13 00 06/02/2024 00:39:13 : [INST-ACK ] 02 62 50.CA.A5 0F 13 00 06 LTOFFRR(00) 06/02/2024 00:40:13 : [INST-TX-I1 ] 02 62 54 25 B0 0F 11 FF 06/02/2024 00:40:13 : [INST-ACK ] 02 62 54.25.B0 0F 11 FF 06 LTONRR (FF) 06/02/2024 00:40:17 : [D2D EVENT ] Event [54 25 B0 1] [ERR] [1] uom=0 prec=-1 06/02/2024 00:40:17 : [ 54 25 B0 1] ERR 1 06/02/2024 00:41:16 : [INST-TX-I1 ] 02 62 00 00 11 CF 11 00 06/02/2024 00:41:16 : [INST-ACK ] 02 62 00.00.11 CF 11 00 06 LTONRR (00) 06/02/2024 00:41:30 : [INST-TX-I1 ] 02 62 00 00 11 CF 13 00 06/02/2024 00:41:30 : [INST-ACK ] 02 62 00.00.11 CF 13 00 06 LTOFFRR(00) any suggestion for the next debug action ? Many thanks, John

Recently, I cannot control any device via Google Home. When I login to admin console, it prompt me bunch of errors like, "Cannot Communicate with XXXX. Please check connections". Then I did some checks as below but none of them worked for me * power cycle ISY994 and PLM2413 * restore PLM2413 * re-adding link for devices I cannot control any device via the admin console on ISY994, and diagnose PLM status show my PLM still connected, and there were links showed in PLM link table. Given that, I am not sure which component in my system broken, is it ISY994 problem ? Any comment / advice will be much appreciated. Thanks, John