Help: All my *actors* suddenly stopped working!!
Posted: 06 Mar 2013 00:23
I have a serious problem in my RaZberry setup.
All of a sudden, all (!!!) of my actors stopped working without any of my intervention.
Some hours ago, everything worked fine.
Then, I wanted to switch on a light using the Web interface but nothing happened...
Next, I've tried all other wall switches (Everspring AN157), Fibaro FGS211 and roller shutters Fibaro FGR221...
NONE of them works, anymore!!
The strange thing is, ALL of my sensors (motion detectors, windows sensors) still work completely normally!!
I have tried including a NEW actor to my network - this operation works and the strange thing is, this newly included device completely works without problems. At the same time, all other actors are still dead!
After rebooting the RaZberry, the newly added actor is dead, as well.
=> I have completely reset the RaZberry and re-built my whole network again. For some hours, the system runs properly, then, all of a sudden, the same behaviour shows up again!!!!
((((
I really hope that this is a known issue or that there is some debugging info possible...
All of a sudden, all (!!!) of my actors stopped working without any of my intervention.
Some hours ago, everything worked fine.
Then, I wanted to switch on a light using the Web interface but nothing happened...
Next, I've tried all other wall switches (Everspring AN157), Fibaro FGS211 and roller shutters Fibaro FGR221...
NONE of them works, anymore!!
The strange thing is, ALL of my sensors (motion detectors, windows sensors) still work completely normally!!
I have tried including a NEW actor to my network - this operation works and the strange thing is, this newly included device completely works without problems. At the same time, all other actors are still dead!
After rebooting the RaZberry, the newly added actor is dead, as well.
=> I have completely reset the RaZberry and re-built my whole network again. For some hours, the system runs properly, then, all of a sudden, the same behaviour shows up again!!!!
((((
I really hope that this is a known issue or that there is some debugging info possible...