This object is in archive!
How to configure poll interval of a device
Answered
Hi.
I recently bought a Danalock BT/z-wave door lock (125 BTZE). However, I'm having an issue with the batteries being drained within a few weeks :-(
I talked with the manufacturer and they suggest that it could be because the Zipato Controller polls the lock at some interval, which makes sense as in the events log, I can see a state reported about every hour or so..
So the question is how to configure the Ziapto Controller as to how often (if at all) it should poll a device, in this case on z-wave? E.g. I think this would be relevant for most battery powered devices, thus I have not specified the Danalock lock in the title.
Thanks in advance, Thomas.
The same question
No connection
Real-time notifications may not work
To lessen battery draining on battery powered devices you should change it's wake up interval to something less frequent.
Battery powered devices needs to be wake to be polled. It should be a setting in the device to control waking up at set intervals and reporting its status. And of course when it's status change it should make the controller know something has changed so controller can poll while it is still awake. If it does not do this it self it will be difficult for any controller.
Then you have the question about polling. I have not seen it confirmed anywhere if Zipato does polling, how often or if it is configurable.
To lessen battery draining on battery powered devices you should change it's wake up interval to something less frequent.
Battery powered devices needs to be wake to be polled. It should be a setting in the device to control waking up at set intervals and reporting its status. And of course when it's status change it should make the controller know something has changed so controller can poll while it is still awake. If it does not do this it self it will be difficult for any controller.
Then you have the question about polling. I have not seen it confirmed anywhere if Zipato does polling, how often or if it is configurable.
I've the same problem with my "Danalock" dorr lock. Two weeks after I got the lock and joined it on the Z-wave network, the batteries were almost empty! On the same day, the battery level change from 100% to 70% - 52% - 48% - 21%, then they hold for 2 more days and then they died! I can still contact the lock, but it doesn't have the power to move the deadbolt.
I've some friends using the Danalock with Fibaro HC2, and they don't have the same issue with the batteries, at least not yet.
On the template Zipato uses for the lock, there is no option to set the Weakup intervall, but it seems Danalock doesn't provide access to that paremeter even if you wantto change that manually (using the parameter Id).
I'm using the beta firmware on the Zipabox, but I don't think that's the issue.
Don't know what to do with the lock, to buy new batteries every 2-3 weeks is not an option :-(
I've the same problem with my "Danalock" dorr lock. Two weeks after I got the lock and joined it on the Z-wave network, the batteries were almost empty! On the same day, the battery level change from 100% to 70% - 52% - 48% - 21%, then they hold for 2 more days and then they died! I can still contact the lock, but it doesn't have the power to move the deadbolt.
I've some friends using the Danalock with Fibaro HC2, and they don't have the same issue with the batteries, at least not yet.
On the template Zipato uses for the lock, there is no option to set the Weakup intervall, but it seems Danalock doesn't provide access to that paremeter even if you wantto change that manually (using the parameter Id).
I'm using the beta firmware on the Zipabox, but I don't think that's the issue.
Don't know what to do with the lock, to buy new batteries every 2-3 weeks is not an option :-(
Please help!!!
Battery is very expensive (4 x CR-123A for Danalock v.2)
Please help!!!
Battery is very expensive (4 x CR-123A for Danalock v.2)
This seems be an annoying problem with many other battery powered devices too. There is something wrong the way, how Zipabox handles device configuration. Or for some other reason the box keeps devices awake long periods.
This seems be an annoying problem with many other battery powered devices too. There is something wrong the way, how Zipabox handles device configuration. Or for some other reason the box keeps devices awake long periods.
i'm very dissapointet about the support from Zipato! No ansver about this simple question, It seems there is no interest in providing support.
I do not want to spend 20-30 euros monthly on the batterys!
I have started to look into buying some other controls....
i'm very dissapointet about the support from Zipato! No ansver about this simple question, It seems there is no interest in providing support.
I do not want to spend 20-30 euros monthly on the batterys!
I have started to look into buying some other controls....
Dear Milan
Is it possible to at least see what polling interval is set?
Just to verify all went well during inclusion for example.
Or even to set manually?
Thank you
Tino
Dear Milan
Is it possible to at least see what polling interval is set?
Just to verify all went well during inclusion for example.
Or even to set manually?
Thank you
Tino
It appears to me that my batteries are not draining like you guys, I use Yale Door Looks, but seems there is no configuration parameter for wake up interval either. Also the documentation provided in manuals from Yale is very poor regarding Z-wave, I even tried to contact the manufacturer but I got a negative answer saying that since I wasn't a z-wave product/controller developer they couldn't provide any more information. How do I know if my inclusion process was succesfull or I need to re include the device if I dont know which parameters I should have in my interface???
It appears to me that my batteries are not draining like you guys, I use Yale Door Looks, but seems there is no configuration parameter for wake up interval either. Also the documentation provided in manuals from Yale is very poor regarding Z-wave, I even tried to contact the manufacturer but I got a negative answer saying that since I wasn't a z-wave product/controller developer they couldn't provide any more information. How do I know if my inclusion process was succesfull or I need to re include the device if I dont know which parameters I should have in my interface???
Replies have been locked on this page!