Automatic sending of changed configuration parameters when the status changes from "asleep" to "alive" (battery-operated units)

[KlausStoertebeker]

Automatic sending of changed configuration parameters when the status changes from "asleep" to "alive" (battery-operated units)

[AlCalzone]

This already happens if you don't restart ioBroker or the adapter between setting the config params and the device waking up.

[KlausStoertebeker]

Ok. My system is restarted every night at 2 o'clock by a cron job...
So if I'm getting you right, changed configuration parameters will be send automatically after a system restart if a Z-Wave device wakes up?

[AlCalzone]

No. When you change any value for a sleeping device, that change gets queued in memory. When a device wakes up, all queued commands get handled.

But when you restart the queue is cleared. So if the device hasn't woken up by that point, your changes are lost.

[tehmilcho]

Hope it's okay if I ask a question here, I also have Fibaro Multi sensors and am currently testing the adapter before I switch from the "stupid" original control center.

Normally you can set a value in seconds for the WakeUp to determine at what intervals the device should wake up for config changes etc. I can't find anything in the objects where I can set this. Is that not possible with this adapter?

Default set Value in Fibaro HC3 Lite and Openhub is 3600 seconds

[AlCalzone]

There should be, under "Wake up". Maybe your device hasn't been interviewed completely. Is it marked as "ready"?

[tehmilcho]

Ready is true and wakeup is an empty folder. The device seems to otherwise working normally. Also changed a parameter and just waited and the change was ack after round about 1 hour

[AlCalzone]

Empty folder seems like the object browser doesn't show what is there. Try reloading the page. If the adapter creates the wakeup folder it meant to put something there.

Otherwise you can try a re-interview. Maybe there was a timeout last time.

[tehmilcho]

I removed it and readded the Device still the same... Ready, Empty Folder

Update: Worked now after 3x Times "Refrash Node Info" and watching the Logs .. alwasys timeouts...