HC2 Stuck with flashing z-wave led

[dhanjel 7]

I removed a device that did not exist (inclurrectly included) and after that, the interface hang.

After a restart, the system still does not respond and the z-wave light keeps blinking with the following page instead of the login page.

 

Any ideas?

 

Please login or register to see this attachment.

 

Trying to access the api, for example:

http://<ip>/api/panels/event

 

Gives me this:

Quote

Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

---

Apache/2.2.16 (Debian) Server at 192.168.1.10 Port 80

 

Edited August 8, 2017 by dhanjel

[barend121 13]

Hard reboot? Power of/on

[dhanjel 7]

Yeah, did that. Same result 

[tinman 1,070]

before you call fibaro support or try recovery, you can just take the HC2 with you somewhere far from your z-wave network. There might be broken/short z-wave device sending the whole time. If that didn't work, you can always try full recovery and restore from backup (if you have recent one) or ask Fibaro support for help.

[dhanjel 7]

Did a recovery with "keep devices", that worked.

Then I tried to load the lastest backup (unfortunately from 2 months ago) and the system got stuck again.

 

Don´t have the energy or time to re-include 50 devices yet again

[tinman 1,070]

no, you don't have to, if HC2 is broken, it will not help. Z-Wave LED on means - transmission, but there can be as well problem with zwave service (if locked or crashing) which prevents the other services from start (the HC service is waiting for zwave service). As i said above, when broken device is flooding the zwave network, the zwave service might got locked (then one have to powerdown the broken device, or try to take the HC2 far from all the devices, to allow the service to start - if that didn't help the reason might be on HC2 side and not device side).  On the HC2 side it might be lack of space, e.g. when for some reason backups or updates crashed and files remained on file system, or broken files (both can be fixed by Fibaro support, us, or by doing recovery - which you did), or hardware problem. Typical hardware problem can be broken zwave eeprom data (due to wrong data coming from broken zwave device), this can be only fixed by fibaro support or us. There can be as well connection problem, e.g. when the zwave PCB (only on HC2) is not mounted properly to mainboard, and of course broken zwave chip (overvoltage due to whatsoever), which can't be fixed remotely, but at least confirmed (again, by fibaro support or us).

 

My proposal, take your HC2 somewhere far from your home and test if the boot process stops again, if that's the case you will have to get remote support, if not the problem is one of the 50 zwave devices. 

[dhanjel 7]

Thanks for a detailed response?

 

I´m about to try a recovery + upgrade to 4.130 and see if I can include one device again, or if it hanga again.

Stay tuned...