Eisy disappeared off network...

[tracknut]

This morning we had some random lights go on and off, so I checked to see if anything looked funny on the ISY, using the local IoX Admin Console. No unusual activity from programs at that time of day, so I guessed some random fluke. I rebooted the Eisy by pulling the power plug (probably not the right way to do it, sorry). Now, I bring up the IoX Finder and it can't find the Eisy on the network. Looking at my router tables, sure enough I don't see it there. I swapped out the Serial PLM to my spare, with no change. I've cleared my JAVA Cache.

Any thoughts?

THanks

[larryllix]

This appears to be the same problem I had with my ISY994s, my polisys and possibly with eISY.

From what I can gather:

The power goes out and ISY products beat the router in powering up. 
ISY asks the router for an IP address from the router's DHCP server.
Router is not prepared to be asked, and ghosts ISY, with no response.
ISY tries again (x times?) and then gives up.
Router boots up and sends out broadcast "Hello, everybody, I'm home"
ISY doesn't hear it, or does not respond to it, due to being busy, or low level drivers still have some deficiencies with retries.
ISY never tries again, and ISY never gets connected to router due to not obtaining an IP address.

Years ago I had another WiFi based receptacle that could power cycle my ISY, as well as some detection software written inside my ISY that could automatically power cycle the router again with successive increasing time delays on  retries. That seemed to rid my system of that problem. MY ISY counters did show some counts a few times over the years.

Since polISY came to me, this happens occasionally but very seldom.  It would seem possible that the O/Ses of both may be using the same C++ drivers.
 

[tracknut]

Thanks for the post, Larry. I don't think that's the situation though. I have fiddled quite rebooting the router, changing the physical ethernet port the Eisy is plugged into, rebooting the Eisy, etc. I have given the router plenty of time (e.g. over an hour) to be stable, then rebooted the Eisy. Still no MAC address is visible at the router, let alone the static IP it's been given.

Dave

[Geddy]

20 minutes ago, tracknut said:

Still no MAC address is visible at the router, let alone the static IP it's been given.

@tracknut, even though you probably didn't initiate an update it's possible that by pulling power it caused a corrupt process that isn't allowing the eisy to fully boot and initialize the ISY side. 

I would suggest you open a support ticket with UD to have them help troubleshoot with steps they know and know what results they're looking for. This has happened a few other times with various issues causing it and support has been able to get them running quickly. Hopefully your issue is easy to resolve as well. Going into the weekend though you might have limited help until Monday. But rest assured UD will be the best bet of how to resolve.

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

 

[tracknut]

Good idea, thanks, I will do that.

Dave

[Techman]

@tracknut

The eisy doesn't support a static address, only reserved addresses.

Make sure DHCP is enabled on your router

The PLM would be a non issue, so don't focus on it.

 

Edited August 15 by Techman

[tracknut]

Interesting. It's been on a static address for about 18 months now. DHCP is enabled on my router, but I have static addresses for a few key things. I'll pull out the static address for the eisy and see if that helps, thanks. It may just be my terminology, I don't know the difference between static and reserved.

[larryllix]

20 hours ago, tracknut said:

Thanks for the post, Larry. I don't think that's the situation though. I have fiddled quite rebooting the router, changing the physical ethernet port the Eisy is plugged into, rebooting the Eisy, etc. I have given the router plenty of time (e.g. over an hour) to be stable, then rebooted the Eisy. Still no MAC address is visible at the router, let alone the static IP it's been given.

Dave

One more. I found ASUS routers didn't completely get a fresh start by rebooting them (I have owned four model now). When things got tough I always had to power cycle them.

Reserved in the DHCP table makes the IP address static by the router enforcement.. Also defining it in a device makes it static.

Edited Saturday at 05:55 PM by larryllix

[tracknut]

A brief update for closure on this thread.

Michel sent me a sequence of commands to type directly to the eisy, which fixed the issue.

Thanks to all for your suggestions as well.

Dave