John Chen Posted June 1 Posted June 1 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
Brian H Posted June 1 Posted June 1 (edited) You did power cycle the ISY994i and 2413. Letting the PLM fully boot first? We have seen strange things if the wall wart supply for the ISY994i has issues but this doesn't exactly fit the problems we have seen. I would suspect the 2413S has a problem communicating. How old is it and can you find the revision number on the back? Can you do a test to one of the problem devices. Showing the communications in Event Viewer on Level 3 and see what it shows. Or you suddenly have a noise maker on the power lines strong enough for the 2413S to think there is a communications on the line. Oh one more thought. Are the modules in question new enough the be Dual Band or the older power line only modules? Edited June 1 by Brian H Fix spelling. 1 1
jason.russo.96 Posted June 1 Posted June 1 I had a problem a few weeks ago that was similar. The ISY was working. It was sending timed commands (like lights off at 10 pm), but I couldn't log in via the app or admin console. I swapped the power supply. Rebooted the network, tried different network cables etc. Nothing worked, the next day it was fine. When I was actually able to log into the ISY (the few days I was having problems), I did a backup which took about 45 minutes. It usually takes a minute or so.
John Chen Posted June 1 Author Posted June 1 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
John Chen Posted June 1 Author Posted June 1 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
IndyMike Posted June 3 Posted June 3 On 6/1/2024 at 1:08 PM, John Chen said: 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 Hello John, Your event logs are showing device timeout errors in response to a "DIRECT MESSAGE" from the admin console (On/Off). Direct messages require that the target device acknowledge the command. A normal ON command from the Admin Console would resemble the 1st log below. You are missing the "INST-SRX" entry which is the response from the device. The second example is after I removed the device. It shows the missing "INST-SRX" entry and the ERR1. Note that the ISY does not ALWAYS tag the no-response entries with the ERR1. Another important thing to note is that SCENES do not require a response from devices. The ISY sends scene commands and does not request a response from the target devices. It assumes that the devices responded properly and reflects that in the admin console status. From your desciption, your "Scenes" sometimes function, but you have problems with On/Off commands from the admin console (direct). That sounds like your devices can (sometimes) hear your PLM communication, but your PLM cannot hear your devices trying to respond. That could suggest a strong noise source/signal absorber near the PLM. Please inspect the electrical circuit where PLM is installed for possible offenders (PC's, UPS's, Chargers, Printers) and filter or move them to another circuit. Alternatively, you could temporarily move your PLM to another circuit to diagnose the issue (extension cord). Normal Direct ON command ISY Command to PLM Sun 06/02/2024 08:39:54 PM : [INST-TX-I1 ] 02 62 54 A1 F5 0F 11 FF PLM Acknowledge Sun 06/02/2024 08:39:54 PM : [INST-ACK ] 02 62 54.A1.F5 0F 11 FF 06 LTONRR (FF) Device Acknowledge Sun 06/02/2024 08:39:54 PM : [INST-SRX ] 02 50 54.A1.F5 53.BC.3A 2F 11 FF LTONRR (FF) Sun 06/02/2024 08:39:54 PM : [Std-Direct Ack] 54.A1.F5-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Direct ON command with No-response Timeout ISY Command to PLM Sun 06/02/2024 08:40:30 PM : [INST-TX-I1 ] 02 62 54 A1 F5 0F 11 FF PLM Acknowledge Sun 06/02/2024 08:40:30 PM : [INST-ACK ] 02 62 54.A1.F5 0F 11 FF 06 LTONRR (FF) No Device Acknowledge Sun 06/02/2024 08:40:34 PM : [D2D EVENT ] Event [54 A1 F5 1] [ERR] [1] uom=0 prec=-1 Timeout error Sun 06/02/2024 08:40:34 PM : [ 54 A1 F5 1] ERR 1 1
Techman Posted June 3 Posted June 3 @John Chen Adding to @IndyMike conclusion, I've attached a trouble shooting article. It was written for X10 but it's also applicable to Insteon. Powerline noise.pdf 1
Brian H Posted June 3 Posted June 3 (edited) Jeff at JV Digital also has a good set of tutorials. X10 primarily but many also effect Insteon power line issues. I found the cell phone charger. Real interesting and sad. https://jvde.us/x10-troubleshooting/ Edited June 3 by Brian H 1 1
John Chen Posted June 3 Author Posted June 3 15 hours ago, IndyMike said: Hello John, Your event logs are showing device timeout errors in response to a "DIRECT MESSAGE" from the admin console (On/Off). Direct messages require that the target device acknowledge the command. A normal ON command from the Admin Console would resemble the 1st log below. You are missing the "INST-SRX" entry which is the response from the device. The second example is after I removed the device. It shows the missing "INST-SRX" entry and the ERR1. Note that the ISY does not ALWAYS tag the no-response entries with the ERR1. Another important thing to note is that SCENES do not require a response from devices. The ISY sends scene commands and does not request a response from the target devices. It assumes that the devices responded properly and reflects that in the admin console status. From your desciption, your "Scenes" sometimes function, but you have problems with On/Off commands from the admin console (direct). That sounds like your devices can (sometimes) hear your PLM communication, but your PLM cannot hear your devices trying to respond. That could suggest a strong noise source/signal absorber near the PLM. Please inspect the electrical circuit where PLM is installed for possible offenders (PC's, UPS's, Chargers, Printers) and filter or move them to another circuit. Alternatively, you could temporarily move your PLM to another circuit to diagnose the issue (extension cord). Normal Direct ON command ISY Command to PLM Sun 06/02/2024 08:39:54 PM : [INST-TX-I1 ] 02 62 54 A1 F5 0F 11 FF PLM Acknowledge Sun 06/02/2024 08:39:54 PM : [INST-ACK ] 02 62 54.A1.F5 0F 11 FF 06 LTONRR (FF) Device Acknowledge Sun 06/02/2024 08:39:54 PM : [INST-SRX ] 02 50 54.A1.F5 53.BC.3A 2F 11 FF LTONRR (FF) Sun 06/02/2024 08:39:54 PM : [Std-Direct Ack] 54.A1.F5-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Direct ON command with No-response Timeout ISY Command to PLM Sun 06/02/2024 08:40:30 PM : [INST-TX-I1 ] 02 62 54 A1 F5 0F 11 FF PLM Acknowledge Sun 06/02/2024 08:40:30 PM : [INST-ACK ] 02 62 54.A1.F5 0F 11 FF 06 LTONRR (FF) No Device Acknowledge Sun 06/02/2024 08:40:34 PM : [D2D EVENT ] Event [54 A1 F5 1] [ERR] [1] uom=0 prec=-1 Timeout error Sun 06/02/2024 08:40:34 PM : [ 54 A1 F5 1] ERR 1 @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
IndyMike Posted June 3 Posted June 3 4 hours ago, John Chen said: 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 ? @John Chen I'm going to rephrase things a bit. If you send a direct command to a device from the ADMIN console and the device responds (turns on) but the PLM/ISY does not get and acknowledge - you will have a sync error between the device and the ISY. I believe that is what you were stating. In addition, you are stating that the device did not respond to the direct on/off command - Is this correct? I do not have a good explanation why a device would respond to a scene command and not a direct command from the admin console. The direct command should ALWAYS be more reliable because it requires the PLM to retry communications. 4 hours ago, John Chen said: 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 ? This does sound like the PLM received the manual on from the device. 4 hours ago, John Chen said: 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. Your device appear to be rather new (<5 years old). Both your switch and PLM should be dual band. They will communicate via powerline and RF - assuming there is another RF device in range. Please do try moving the PLM to another location. To test - Open the event viewer and set to level3. Right click on "My Lighting" on the admin console tree and select "query". Communication errors will result in POP UP windows showing the devices. If you can, post the contents of the even viewer.
Techman Posted June 3 Posted June 3 @John Chen Right click on the devices you're having issues with, then click on restore device. Did that correct the problem?
John Chen Posted June 4 Author Posted June 4 @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 Posted June 4 Posted June 4 (edited) 3 hours ago, John Chen said: @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 You do not need to reset your devices when you move the PLM. Keep in mind that this is a troubleshooting step to determine if there is noise on the circuit your PLM is currently plugged into. If you have Insteon plug-in devices (dimmers/on-off modules) you can also try plugging them into the same outlet as the PLM to see if you can communicate with them. Edited June 4 by IndyMike spelling
John Chen Posted June 4 Author Posted June 4 16 hours ago, Techman said: @John Chen Right click on the devices you're having issues with, then click on restore device. Did that correct the problem? 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 .......
John Chen Posted June 4 Author Posted June 4 @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
IndyMike Posted June 4 Posted June 4 @John Chen, the NACK is the device indicating that it is no longer linked correctly to the PLM. I am not well versed on the "Google home linking". It appears that this linking process "broke" the link table in your device. The following looks good with good communication (hops left 2 or greater) Quote /* 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 The following has good communication (good hops remaining), but the device is returning a NACK. That's an indication that the PLM is no longer a valid controller for group 0. Did you "link google home" prior to this? Quote /* 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 Same as previous. Good communication, but NACK indicating PLM isn't a valid controller. 5 hours ago, John Chen said: /* 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 Hopefully someone else can help with the Google Home Linking issue. It seems that it is corrupting your devices. I would also strongly suggest that you investigate the circuit where your PLM was originally installed. There is still a strong noise source or signal absorber on this circuit. Moving your PLM improved things, but the offending device is still degrading your system.
IndyMike Posted June 5 Posted June 5 @John Chen, the following is an example of what I believe is happening in your system. The link table shown is from one of my newer Switchlinc dimmers (similar vintage to your device). These are I2CS devices that must be "INITIALIZED" during the linking process. If they are not initialized, they will respond with the NACK that you are seeing. The highlighted row is the "GROUP 0" responder link back to my PLM. Without this link, the device will refuse to respond to "Device Direct" Commands from the Admin Console (On/OFF/Fast ON/Fast OFF etc). The remaining links are to scenes that the device is assigned to. I believe that your Group 0 link is being overwritten for some reason. That would produce the NACK that you are seeing and would prevent the device from responding to "Direct Commands" from the admin console. Re-linking with the "set button" could restore this link. Assuming the other link records are intact, your device would still be able to respond to scenes and communicate manual kepreses back to the PLM. This would explain why you could control the device through scenes, but not directly from the Admin Console. The device would not respond to a "Restore" since the Group 0 record is missing or corrupt. Unfortunately, I do not understand HOW this is happening. I am assuming that this is happening on multiple devices. That means it's not an isolated device failure. The communication in your current location also appears good, so a failing PLM does not fit. Do you have another Insteon controller in your system (houselinc or Insteon Hub) that might be writing to these devices? If you don't have a second controller in your system, I would suggest that you open a ticket with the UDI team. What you are seeing is not at all normal.
John Chen Posted June 5 Author Posted June 5 @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 1
IndyMike Posted June 5 Posted June 5 @John Chen, I do not use the web portal or google Home. I can't troubleshoot this from my end. Your description definitely points to a problem with the google home connectivity. I did not realize that affected links in hardware devices. I have been seeing an increase in the number of posts about devices that mysteriously become unavailable and require re-linking. You may have uncovered the cause. My apologies for the short hand. UDI = Universal Devices Inc. You can submit a support ticket here : https://www.universal-devices.com/contact-us/. Please do make sure to inform Universal Devices of this issue. It likely affects many others.
John Chen Posted June 7 Author Posted June 7 @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 Posted June 7 Posted June 7 (edited) 3 hours ago, John Chen said: 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 ? @John Chen, the simple answer is "NO". In my opinion, there is nothing better than the ISY for managing Insteon devices. Like you, I use the ISY994. When I get to the point where I need to replace it, I'll upgrade to the current Universal Devices product (likely the EISY). I use Home Assistant for managing my Z-Wave and Zigbee devices. I would not suggest using Home Assistant to replace the ISY for Insteon. From what I understand, you will loose a lot in terms of scene management. I have no doubt that Universal Devices will be able to solve your issue - they really are quite good. Edited June 7 by IndyMike 1
John Chen Posted June 8 Author Posted June 8 On 6/7/2024 at 3:22 PM, John Chen said: @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. @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
Recommended Posts