Search the Community
Showing results for tags 'dead'.
Does anyone else have this same issue with the fibaro motion sensor? Did you resolve it, if so how? you add the motion sensor to home center and it works for a month then all of a sudden it will not detect motion and becomes a dead. it will not wakeup or respond to any commands in HC2. checked the sensor and has full battery so its not a battery issue. this has happened twice already. supposedly it is "up to date" in terms of software updates. Fibaro please fix this issue!!! *yes I have re-added it to HC2 but that does not resolve the issue permanently.
2,683 downloadsThis scene monitors and catches Z-wave commands traffic between controller and devices. The data displayed to user as a table which includes total commands and their properties per device, in addition same data displayed at graphical chart and shows system activities over the time. Since Z-wave protocol is not a fastest one (in many case it's just freeze) this code helps to analyze the data and to take necessary actions to reduce overall Z-wave traffic and system load. Scene functionality 1. This is not an auto started scene. You need to start it manually. While the scene is running
I have four Danfoss thermostats connected to HC2. I have noticed that they are marked as dead from time to time. It is probably pointless. If they wake up every 15 minutes (wake up interval set to 900 sec.) and then communicate with HC2 to set up the temperature, report battery level etc. so is there a need of checking them by HC2 every 125 sec. (standard polling time)? I think this could be the reason why they are marked as dead. So shouldn't I just set "Mark if dead" to 'No'? If I will do this the HC2 will stop to polling them every 125 sec.? What is your opinion - maybe I don't understand t