Fibaro HC 2 stops reacting completely - no error messages

[dakis 0]

I installed our HC 2 some two months ago. For the first month, everything worked fine. Then, 3 weeks, the system all of a sudden became unresponsive. I could still log in to the web app, no error messages whatsoever. In the app, everything looks completely fine. I can even control some of the devices, e.g. my lamps, but the system doesn't display any "transfer ok" messages. The mobile app connects to the HC fine but won't work at all - it's not possible to control any devices from there. Scenes don't work, either. 

 

I rebooted the HC 2 and everything worked again for anywhere bewteen a few minutes and a few hours at a time and then stopped again. I kept rebooting the system once in a while. After the update to 4.0.80, the system worked for an entire week, until it crapped out again today. Rebooted, worked for a few minutes, then crapped out again. Rebooted again, now it's been up and running for about 2 hours or so. 

 

Since I'm note getting any error messages and everything just looks perfectly fine in the system, I have absolutely no idea where to even start. RAM etc. seems fine as well. Does anyone have any ideas how to proceed? 

[Joacim 11]

Sounds like you may have a rouge device somewhere in the network clogging it with messages and halting all other communication. Fibaro support can look at logs or you can try and är what happens if you start disconnecting devices.

[dakis 0]

Sounds like you may have a rouge device somewhere in the network clogging it with messages and halting all other communication. Fibaro support can look at logs or you can try and är what happens if you start disconnecting devices.

 

thanks, I looked at some of the most obvious candidates and I hope I've now found the problem: one of the Nodon Octan remotes knocks out the entire system as soon as I click on any of the buttons. Removing the battery from the device doesn't do anything, however. The system won't run again until I have performed a reboot - I don't think it's great that a single device can knock out the entire system

Please login or register to see this image.

/emoticons/default_icon_curve.gif" alt=":-/" />

[j.nowacki 5]

What version do you run? Do you have any Lua scene that triggers on Octan remote?

[dakis 0]

What version do you run? Do you have any Lua scene that triggers on Octan remote?

4.0.80 - each button of the remote is assigned to a scene. I have now deleted the remote from the system and assigned the same scenes to another remote - no problems so far. But I guess it's too early to tell

[bjarne79 0]

I have a similar setup, with a NodOn Octan remote, where buttons trigger simple LUA scenes. This is causing issues idential to yours: Has worked well for some months, now hangs whole network while interface still seems fine.

I have removed the remote from the system (just a few hours ago, so maybe to soon to say if everything else is back to normal. But seems that way now.)

 

However - I have tried to add the remote again, but get a "learning mode error. Try again"

This is after deleting device from interface, removing it from the network, then resetting remote to factory defaults.

 

I am running version 4.0.80

The LUA scenes for the buttons are quite simple, and they can still be run from the web interface and mobile app.

[chaicka 195]

Check out 'hidden' device as there may be residue among the hidden device view.