Jump to content

ISY not communicating, gone bad?


GQuack

Recommended Posts

Greetings, I have a new issue I have not seen. All has been running smoothly until it wasn't. The ISY programs stopped running, I cannot connect to the ISY using the admin console or a browser (Chrome: This site can't be reached, Edge: Hmmm, can't reach this page). I can see the ISY on the network via the network map and I can ping it and it replies. The ISY finder does not find the ISY, if I manually try to add with the URL address and get not found. 

I've had a couple of different LED light patterns, 1) Power LED on, TX, RX, and Memory all come on, Memory LED flashes very quickly, then TX, RX, and Memory all turn off, Power LED stays on. 2) Right now, Power, TX, RX all on and steady. None of the patterns I see are listed in the Wiki.

Tried to factory reset, same result. Tried a new PLM, same result. Help please, what else should I try?

image.thumb.png.ff49a58bc310853abe82c5faf2297c7a.png

Link to comment
Share on other sites

Yes. There have been no changes to the network. Everything was working just fine and then stopped. I’ll take a look again this morning.  The iSY is connected to the router via a network switch.  I also rebooted the switch during troubleshooting to make sure there was nothing going on with that connection.

Link to comment
Share on other sites

Just now, unplugged the switch and rebooted, unplugged the PLM, unplugged the ISY, verified connections. Plugged in the PLM, plugged in the ISY. Now I have just the Power light on, no others. When I fire up the ISY finder, I see the message: Searching and then nothing..doesn't say can't find but also doesn't come back with the address of the ISY.

Link to comment
Share on other sites

Does anyone have any comments, suggestions? I need to get this system back up and running, I have a lot of dependencies on this system (security cameras, main water valve, etc.) that I really don't want to be down for long. Any help would be appreciated.

Link to comment
Share on other sites

4 hours ago, GQuack said:

Does anyone have any comments, suggestions? I need to get this system back up and running, I have a lot of dependencies on this system (security cameras, main water valve, etc.) that I really don't want to be down for long. Any help would be appreciated.

Have you tried to type the Isy address in manually

Link to comment
Share on other sites

Programs have stopped and do not work, launcher does not find. I have not tried to re-seat the sd card, why would take come un-seated just sitting but I can try.

Here's something more to add. Swapped out the cables to the ISY and PLM just touching all the bases, restarted the ISY, tried to ping the ISY, results below. Unreachable twice, then reachable twice with vastly different times.

Reply from 192.168.1.145: Destination host unreachable.
Reply from 192.168.1.145: Destination host unreachable.
Reply from 192.168.1.200: bytes=32 time=2300ms TTL=60
Reply from 192.168.1.200: bytes=32 time=3ms TTL=60

Link to comment
Share on other sites

This is just bizarre. lilyoyo1 I did re-seat the SD card to touch that base, fired back up. Three successive ping attempts.

Pinging 192.168.1.200 with 32 bytes of data:
Reply from 192.168.1.200: bytes=32 time=284ms TTL=60
Reply from 192.168.1.200: bytes=32 time=2ms TTL=60
Reply from 192.168.1.200: bytes=32 time=1ms TTL=60
Reply from 192.168.1.200: bytes=32 time=2ms TTL=60

Ping statistics for 192.168.1.200:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 284ms, Average = 72ms

C:>ping 192.168.1.200

Pinging 192.168.1.200 with 32 bytes of data:
Reply from 192.168.1.200: bytes=32 time=1ms TTL=60
Reply from 192.168.1.200: bytes=32 time=2ms TTL=60
Reply from 192.168.1.200: bytes=32 time=1ms TTL=60
Reply from 192.168.1.200: bytes=32 time=2ms TTL=60

Ping statistics for 192.168.1.200:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:>ping 192.168.1.200

Pinging 192.168.1.200 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.200:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

Link to comment
Share on other sites

54 minutes ago, GQuack said:

Can I get someone from UDI to weigh in, Michel Kohanim are you out there? It looks to me like the network chip / board / ? in the ISY has failed, yes? Or other possible causes?

The proper channel for direct support from UDI is to submit a ticket. While they do chime in on the forums from time to time, a ticket assured you of service.

https://www.universal-devices.com/my-tickets

If you have a backup of your ISY, you can factory reset your isy and restore your backup to see if that helps

Link to comment
Share on other sites

  • 4 weeks later...

I have no idea whether our issues are related but two days ago my ISY stopped working off and on, and  the Administrative Console (when I succeed access......) does not show the status of any of my devices. I also had the issue of my ISY not showing in ISY Launcher but that changed when unplugged Poilyglot. Sometimes my existing programs run as before, but I am unable to access or change these programs. In ISY Portal it says that my ISY is off-line. Very frustrating.

Link to comment
Share on other sites

Just now, asbril said:

I have no idea whether our issues are related but two days ago my ISY stopped working off and on, and  the Administrative Console (when I succeed access......) does not show the status of any of my devices. Sometimes my existing programs run as before, but I am unable to access or change these programs. In ISY Portal it says that my ISY is off-line. Very frustrating.

Do you have a backup of stuff prior to your changes? You can try restoring that

Link to comment
Share on other sites

28 minutes ago, lilyoyo1 said:

Do you have a backup of stuff prior to your changes? You can try restoring that

I have backups and did a restore (several times in fact) and even reformatted the sd card etc. But no luck. Later today I will try to remove nodeservers oone-by-one if necessary as Michel believes that the issue may be linked to one of my nodeservers.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...