I've had this module for almost 3 years now but unfortunately seem to have lost connection to the Envisalink Server a few days ago - 06/02/17 with a Network Supervision Fault message. I have tried the following:
1. Switched off my alarm system(DSC PC1864) and disconnected battery, restarted the alarm after 10 minutes
2. Rebooted and changed switches & routers
I can see the device from my LAN with no issue (screenshot below), but it looks as if its not subscribed on the server. I have removed the MAC address from the screenshot, is there a way I can verify that this is still registered on the Envisalink server before I try registering the device again? It was previously registered under a dealer account, so my account view does not have " Add Devices " devices option on the myconnect2go.com interface.
You can see a couple of problems here. First is that the device is firewalled, most likely by your router, and that is what the "OFFLINE" means when the IP address is valid, which it is. The other issue is that your DNS server is no longer responding to the Envisalink, that is what the (E) at the end of the IP address tells you. This means the Envisalink is using a cached DNS value that it got sometime before.
I am 90% sure your problem is with your static IP settings. You probably did this a long time ago and now the gateway and DNS settings have changed or the router no longer will route "unknown" traffic. Try switching back to DHCP and see if your connection returns. If it does and you still want a Static IP, use your router's MAC reservation service to create a static IP, not the local Envisalink option.
For those following along at home, in Eyezon tech-support we see the "Static IP not being recognised by the router" issue more and more. It looks like whatever version of Linux the router companies are using these days is starting to have stricter and stricter firewall rules including a rule that will block traffic from the LAN if the IP is not in its DHCP table. So by using the Envisalink's "static IP" settings, the router never sees the device in the DHCP table so it will refuse to route its traffic to the WAN side.
Many thanks for the quick reply, I didn't see your comment, but you were correct. I actually ended up first doing the hard reset (jumping pins 2 & 5) which ended up pointing out the DHCP issue. I think I'm going to leave out using a static ip for now, until I get my new router next month and will configure the static on the router and see how that goes. Thank you again!
Rather than setting a static IP on the EVL, set a "DHCP reservation" (sometimes called static ARP) on the router, associated with the MAC on the EVL. For all intents and purposes it is the same, except that the router sets the IP rather than the EVL.
I have the same problem that started about the same day. Ive changed nothing. it just quit. the ev3 is showing it has a connection with the lights, but I don't see it on my list of wired devices on my router. what can i check? How do i find my MAC to put it on the list
Were you set to Static IP? If you were then you most likely have a DNS issue as the new firmware reset the cache for available servers and that can only be found through DNS.
Turn off static and use a MAC reservation instead as one of our fine users already mentioned in this thread.
Same thing happened to me. I was using this with my vera for years. Suddenly it wasn't working. Then I noticed eyez-on website couldn't communicate with my EVL-3. Then I factory defaulted it, let it grab DHCP IP. I can ping my EVL-3's IP; MAC registered to eyez-on. But when I go to http://192.168.1.100 (current EVL-3 IP), I get error connection timed out.
Can anyone please help me understand what changed and why I suddenly can't get to the webpage of my EVL-3 locally?
Why would you think the IP was 192.168.1.100? If it is on DHCP it could be anything. You need to check your DHCP table to see what IP your router as assigned to the module.
GrandWizard wrote:Why would you think the IP was 192.168.1.100? If it is on DHCP it could be anything. You need to check your DHCP table to see what IP your router as assigned to the module.
Thank you for your reply. I verified the MAC against the mac I see when I go to envisalink website and select my partition which also matches the sticker on my evl-3
I am a network engineer by trade. I have an enterprise "lab" setup here that I test things on. It is way overkill for a normal home but I test all scenarios in it. That said, I have a windows 2012R2 server handling my DHCP for Vlan1 which I have in the 192.168.1.0/24 range. The switch port for my EVL-3 is an access port on Vlan1. I can see my DHCP server hand out the first address in that range 192.168.1.100, and I see the corresponding mac address. I'm sure its the right address for the right device. I can ping it fine, but the local webpage won't load since this update.
I'm trying to understand if my evl-3 malfunctioned or is there something silly I'm missing.
I even considered my asa firewall blocking port 80; but I can telnet to the IP of my EVL-3 fine. Also, in this setup my main network runs in Vlan 3 (192.168.3.0/24) network, and my Cisco3825 handles my internal routing so it never leaves out to the firewall.
