Hi. Using Z-Wave JS, which as far as I can gather does not have the possibility to set the wake up interval on my Fibaro multisensor (FGMS-001).
I’m therefore trying to set it using an action call, but doesn’t seem to do much:
data:
command_class: "132"
property: wakeUpInterval
value: 300
target:
device_id: 1bceb2ccd0eec994a6bc5311891883f6
action: zwave_js.set_value
Am I doing this correctly, or is there some other way of doing this?
No simple way with zwave-js.
Very easy to set all ZWave parameters with zwave-js-ui. Search this forum how to migrate from zwave-js to the ui version.
I know I can do it with ZWave-JS-UI. I’m not currently in the mood to start the transition process for this little thing.
I’m assuming that the wake up interval anyway is going to be sent to the multisensor via a standard Z-Wave call, hence thinking it should be possible to do it not using the GUI, but just performing an action call.
I’m going to ask why? 
Increasing the wake-up interval will only drain the battery faster, and ISTR it isn’t related to the sensor (e.g. temperature) reporting interval.
For pairing, etc, just trigger the vibration sensor to wake the Z-Wave radio up.
The temperature reporting interval and measuring interval are both set at 300 seconds. The temperature threshold is set at 0.1C.
Still, it does not update the temperature more often than every few hours.
I bought a used HomeCenter 2 and set the sensor up there, in which case it happily reports the temperature every 5 minutes.
Might be that the wake up interval is not the issue, but figured it’s worth a shot, as I’ve run out of other things to try.
It is a long time since I gave up setting parameters on a FGMS-001 with openHAB as they didn’t reliably change behaviour regardless of what the Fibaro docs said.
This suggests HC2 has Z-Wave binding has a different definition from HA & openHAB (although the latter now uses ZHA apparently - it didn’t back then).
I can say battery life on FGMS-001 increased a lot moving from old openHAB to HA which might fit with less time awake.
Before a quick check, I was going to say mine only update every 4h-ish, but the Temperature Report Interval parameter seems to be working somewhat here:
Problem is I know it is able to work.
The same sensor was working fine on my previous Z-Stick. Unfortunately, this died and I moved over to Z-Stick 10. Have not been able to get the sensor to work properly after the move.
I have two sensors on firmware 2.8 which are not working properly. The one on FW 3.4 works fine. And 2.8 is the latest available for those two.
Did you manually wake up the device so it can receive the updated setting?
Yes, woke it up, it received the new settings. No change.
