How to check if Z-wave Battery Device setting is stored in device (Fibaro Smoke/motion)

Comments

• Phaeton Member

  October 2017

  That's awefully silent <span></span>
  Nobody?
• ingmar Member

  November 2017

  HarryBuurman said:

  I dont know if this is device specific, but I'll start more general. My current situation. I have a Fibaro Smoke Detector V1. It beeps periodically which is setting I should be able to change in the interface. 

  
  

  Steps I took:

  1) I have changed the setting in the interface and saved. 

  2) Got the message that the device will be updated when a wake up occurs. 

  3) I tapped the smoke detector button three times, see the following message in the log:

  
  

  [2017-10-20T19:49:34.236Z] Node[45]: Marked as online

  [2017-10-20T19:49:34.236Z] Node[45]: sendData to COMMAND_CLASS_SENSOR_ALARM, params 0x0104

  [2017-10-20T19:49:34.245Z] Node[45]: sendData to COMMAND_CLASS_SENSOR_ALARM, params 0x0100

  [2017-10-20T19:49:34.249Z] Node[45]: sendData to COMMAND_CLASS_SENSOR_MULTILEVEL, params 0x04

  [2017-10-20T19:49:34.254Z] Node[45]: sendData to COMMAND_CLASS_SENSOR_MULTILEVEL, params 0x04

  [2017-10-20T19:49:34.260Z] Node[45]: sendData to COMMAND_CLASS_SENSOR_MULTILEVEL, params 0x04

  [2017-10-20T19:49:34.265Z] Node[45]: Received application update: 0xa1029c31867270858e8b568480

  [2017-10-20T19:49:34.272Z] Node[45]: sendData to COMMAND_CLASS_SENSOR_ALARM, params 0x0101

  [2017-10-20T19:49:34.315Z] Node[45]: Received application command for COMMAND_CLASS_SENSOR_ALARM, data: 0x022d04000000

  [2017-10-20T19:49:34.318Z] Node[45]: sendData to COMMAND_CLASS_SENSOR_ALARM, params 0x0104

  [2017-10-20T19:49:34.341Z] Node[45]: Received application command for COMMAND_CLASS_SENSOR_ALARM, data: 0x022d00000000

  [2017-10-20T19:49:34.344Z] Node[45]: sendData to COMMAND_CLASS_SENSOR_ALARM, params 0x0100

  [2017-10-20T19:49:34.370Z] Node[45]: Received application command for COMMAND_CLASS_SENSOR_MULTILEVEL, data: 0x05012200eb

  [2017-10-20T19:49:34.373Z] Node[45]: sendData to COMMAND_CLASS_SENSOR_MULTILEVEL, params 0x04

  [2017-10-20T19:49:34.904Z] Node[45]: Received application command for COMMAND_CLASS_SENSOR_MULTILEVEL, data: 0x05012200eb

  [2017-10-20T19:49:34.909Z] Node[45]: sendData to COMMAND_CLASS_SENSOR_MULTILEVEL, params 0x04

  [2017-10-20T19:49:35.441Z] Node[45]: Received application command for COMMAND_CLASS_SENSOR_MULTILEVEL, data: 0x05012200eb

  [2017-10-20T19:49:35.444Z] Node[45]: sendData to COMMAND_CLASS_SENSOR_MULTILEVEL, params 0x04

  [2017-10-20T19:49:35.978Z] Node[45]: Received application command for COMMAND_CLASS_SENSOR_ALARM, data: 0x022d01000000

  [2017-10-20T19:49:36.013Z] Node[45]: Received application command for COMMAND_CLASS_SENSOR_ALARM, data: 0x022d04000000

  [2017-10-20T19:49:36.048Z] Node[45]: Received application command for COMMAND_CLASS_SENSOR_ALARM, data: 0x022d00000000

  [2017-10-20T19:49:36.083Z] Node[45]: Received application command for COMMAND_CLASS_SENSOR_MULTILEVEL, data: 0x05012200eb

  [2017-10-20T19:49:36.115Z] Node[45]: Received application command for COMMAND_CLASS_SENSOR_MULTILEVEL, data: 0x05012200eb

  [2017-10-20T19:49:36.254Z] Node[45]: Received application command for COMMAND_CLASS_SENSOR_MULTILEVEL, data: 0x05012200eb

  [2017-10-20T19:49:36.647Z] Node[45]: Received application command for COMMAND_CLASS_SENSOR_MULTILEVEL, data: 0x05012200eb

  [2017-10-20T19:49:36.678Z] Node[45]: Received application command for COMMAND_CLASS_SENSOR_MULTILEVEL, data: 0x05012200eb

  [2017-10-20T19:49:37.765Z] Node[45]: sendData to COMMAND_CLASS_WAKE_UP, params 0x08

  [2017-10-20T19:49:37.801Z] Node[45]: Marked as offline

  
  

  --

  I wonder, how can I check if the setting is stored?
  When I don't wake up the device (setting cannot have been send to the device) I still see the setting I set in the interface.
  
  I conclude that the settings I see are not recieved from the device but are stored somewhere in Homey. Is this true?
  
  

  In my previous software (Homeseer) I could ask the interface to retrieve settings in the device. Which is very handy. Can Homey do this?

  
  

  I have a Fibaro Motion Sensor which I set to not show the led when motion is detected. This device also doesnt seem to update. Could it be I do something wrong?

  
  I was wondering that myself as well, there is an wake up interval which should inquiry for updates, but I never got that working... I have a many devices from qubino, fibaro and aeotec, none of the battery devices will get updated just like that... So, I am really curious if someone could explain how we can keep track of wakeups and updates. Would also be nice to understand what the command classes and parameters do, is there a some kind of dictionary somewhere? :-)
• caseda Member

  November 2017

  @ingmar: full "dictionary" for zwave is public:
  http://zwavepublic.com/specifications
  Mind you, in total it is about 2000 pages.
  
  Currently there is no build in way to retrieve current state of parameters in homey settings, have been waiting for a button in settings to be able to implement it manually. 
  And are stored on homey itself.
  
  There is a way to get a (yes 1) parameter at a time and its current value from within the zwave settings but this way only works for non secure devices, how to do it is explained here:
  https://github.com/caseda/homey_zw-ccl/blob/master/Configuration.js
  
  If you want an easier way, you will have to add an issue on github as feature request.
  
  There is a way to always save the parameters to a battery device consistently:
  If a parameter is already a value your wanted, change it to something random and save, and change it back to the value you want, as only changed values will be send.
  Don't press save yet.
  Wake up the device near homey, and while it is awake press the save button.
  
  There can go a lot wrong when trying to do it on wakeup, homey is no power house, but does have to act like it with everything it can do, so empties the send queue to that device to save resources when the device woke up, even if the device does not send the "acknowledged" signal back (in time). 
  Doing it the above way you will make sure the parameters reach the device immediately.
  

  
  
• Phaeton Member

  November 2017

  Thanks, very helpful. I will try this. And I'll add a request on github and post it here.
• ingmar Member

  November 2017

  caseda said:

  @ingmar: full "dictionary" for zwave is public:
  http://zwavepublic.com/specifications
  Mind you, in total it is about 2000 pages.
  
  Currently there is no build in way to retrieve current state of parameters in homey settings, have been waiting for a button in settings to be able to implement it manually. 
  And are stored on homey itself.
  
  There is a way to get a (yes 1) parameter at a time and its current value from within the zwave settings but this way only works for non secure devices, how to do it is explained here:
  https://github.com/caseda/homey_zw-ccl/blob/master/Configuration.js
  
  If you want an easier way, you will have to add an issue on github as feature request.
  
  There is a way to always save the parameters to a battery device consistently:
  If a parameter is already a value your wanted, change it to something random and save, and change it back to the value you want, as only changed values will be send.
  Don't press save yet.
  Wake up the device near homey, and while it is awake press the save button.
  
  There can go a lot wrong when trying to do it on wakeup, homey is no power house, but does have to act like it with everything it can do, so empties the send queue to that device to save resources when the device woke up, even if the device does not send the "acknowledged" signal back (in time). 
  Doing it the above way you will make sure the parameters reach the device immediately.
  

  
  

  
  Hi thanks for the explanation.The trick with changing parameters, save it, change it back, wake up the device, and done! I know that and it works. Still, it would be cool to just leave your stuff hanging and remotely update the settings.
  
  Anyhow, just 2000 pages ;-) let's see if I can find something in it, once I am >65 years and have plenty of time :-)