paulw Posted Thursday at 03:38 PM Posted Thursday at 03:38 PM Admin Console keeps giving me a "Failed Communication With" for a insteon device. When I OK it, I get it a second time. After that I can control (manually or via program), and restore it with no issues. Happens for same device every time I start the console. Any thoughts? Quote
apostolakisl Posted Thursday at 05:52 PM Posted Thursday at 05:52 PM I have a similar situation. I believe the one device has communication issues that come and go because of some unknown interference source. So the error message is in ISY from a failure prior to opening the admin console. Quote
paulw Posted Friday at 02:13 PM Author Posted Friday at 02:13 PM Looking back I am thinking it started when I had the device unplugged when starting the console. Now it keep coming up every time I start the console but never when being used. Quote
Solution apostolakisl Posted Friday at 03:47 PM Solution Posted Friday at 03:47 PM 1 hour ago, paulw said: Looking back I am thinking it started when I had the device unplugged when starting the console. Now it keep coming up every time I start the console but never when being used. Did you try rebooting eisy/polisy? I had issues with other pop-up notifications presenting with every instance of opening the admin console after adding a new insteon device. Every time, it would tell me I had successfully added that device. Rebooting got rid of it. Though for all I know, if I add another insteon device it will happen again. Don't know, haven't added any since then. Quote
larryllix Posted Friday at 07:15 PM Posted Friday at 07:15 PM 5 hours ago, paulw said: Looking back I am thinking it started when I had the device unplugged when starting the console. Now it keep coming up every time I start the console but never when being used. Right click on the device in the device tree and select "Restore". There is likely a link missing yet. Devices have a link to the PLM for every function, sometimes 10 or 12 links. They can all work properly except one at times. Quote
paulw Posted Friday at 09:02 PM Author Posted Friday at 09:02 PM Thanks to you both. The reboot resolved it! Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.