I’ll explain a little bit about what you are noticing. There are two (actually three but I’ll keep it simple) types of Z-wave devices. Mains powered devices that act as repeaters and battery powered devices that do not. Mains powered devices are always awake and ready to receive configuration changes, respond to get commands, or apply association updates. These are devices such as switches, outlets, some sirens, etc. Battery devices are mostly asleep and do not respond to anything. They do this to conserve battery and it works very well. I have “sleepy” Z-Wave devices that have lasted over 4 years and are still going. These devices are Motion sensors, contact sensors, remotes, etc.
Because these devices will sometimes need to receive updates from the Z-Wave controller, they “wake up” and send the controller a “wake up” report. This wake up report is only sent to a single controller and the interval in which it wakes up is configurable. I don’t remember what the default is for this device, but the manufacturer has asked that it be set to 24 hrs. The shorter this interval, the more of an effect it has on battery life.
So this device, like all of my other Z-Wave handlers, tries to handle configuration how the Z-Wave developers intended it. It waits for a wake up report, sends the configuration changes, and then sends a wakeUpNoMoreInformation to tell the device to go back to sleep. If there are no changes to be made to the device, it immediately tells it to go back to sleep. This is optimal for battery life.
With this device you can either a) wait for the device changes to sync when the device wakes up on its own. It might not be optimal as the wake up interval is 24 hours. (although this is often optimal for motion or contact sensors that you have a lot of and might be in hard to reach places). Or b) you can manually “wake” the device up. Every Z-Wave sleepy device should have a way to do this. This one, if you hold the button down for a few seconds, will wake up (as I and others have mentioned above).
During this process you do not have to hit done on the preferences page or the sync button or do anything. The Wallmote will send a wake report to the controller and it will send the configuration changes. If you want to see what it is doing, you can watch in the logs with debug enabled.
I will make note of this in the first post and put it in the handler. It is something that has been in my handlers for so long I guess I just forget that everyone doesn’t know how it works.