This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Observation about the Z-Wave blog
DaneeDeKruyff
Member
Athom has posted a blog about Z-Wave with some general information and how Athom integrated Z-Wave into homey, an interresting read: https://blog.athom.com/2017/01/22/homey-z-wave-background-story/
I do have a remark though, as I don't think this is explained right:
This seems like a more acurate description:For example, most battery-powered devices have a ‘Wake Up Interval’, which is the amount of seconds it’ll take for them to be reachable to receive commands, e.g. new settings or a GET command. Upon pairing, Homey reads this value, and optionally set a new value if the app developer provided a new value.
Battery powered Z-Wave devices such as sensors or remote controllers are sleepy – they turn off their receivers to save energy, so you can’t send them commands at any time. Instead, they wake up at a regular interval and send a WakeUpNotification to alert other devices that they will be listening for incoming commands for the next few seconds. The WakeUpIntervalSet command is used to configure both how often the device will wake up and which controller it will send its WakeUpNotification to. When the controller gets the WakeUpNotification and has no commands to send to the device, it can send WakeUpNoMoreInformation to tell the device that it can go back to sleep.