I have trouble getting battery level for my Aeotec Door/Window sensor 6 ZW112. From the log it seems that the controller sends a request for status. I have got one update of the battery level when doing a parameter change (changed wake up time to 4 minutes for test).
Logfile showing the one time only battery update for Node 4 at 20:41:09.908. My other ZW112 (Node 15) have newer been updating the battery status. Both have the same settings.
Battery update is only performed every few hours (ie the binding polls every hour or so). The device then needs to wake up to actually receive the message and respond.
I’m not really sure what you want me to look at? The log looks fine so clearly it’s working.
So the battery update is a request from the binding to the device about battery status?
For a device that wakes up once a day how will this work. Is the request buffered and sent to the device when awake or does the device have to be awake when the request is sent?
Since I have had none updates for the battery status for the last 5 months I guess the device has to be awake when the request is sent.
The message requesting battery status is placed in a send/transmit queue. When the device wakes up (it “announces” that it is awake by sending a message to the controller), the binding sends the messages that are in the queue. Note that the queue is memory-based, so those queued messages won’t survive an OH restart.
With the binding in debug mode, you should be able to see the battery request being placed in the queue. And, some time later, you also should to see the wakeup notification being received by the binding, along with the queued messages being sent.
That’s great information. The strange thing is that I have two identical devices with the same parameters set but one updates the battery status every 2nd hour and the other one aprox every 12th hour.
As earlier stated about never having battery status update: After setting the wake up time to 240s yesterday I started to get updates with the sequence mentioned above.
@vegarroe The two things you want to check in the configuration of those devices – the polling period and the wakeup interval. Those two parameters will determine the frequency with which you will receive updates from a device.
Edit: I should note that changes to the polling period will take effect immediately, because that is controlled by the binding. Changes to the wakeup interval will take effect the next time the device wakes up (as it is a message that is queued for transmission to the device).
I have the same device and only get battery level 100% or 0%.
Is this how it works? Somehow a Lowbat-Level? Or do others see the “real” level like 68%?
There should not be any problem with battery reporting - other than typically on these kind of devices, the measurement is pretty poor as they tend to use voltage rather than integrating energy. Voltage remains flat, so battery percent stays at 100% for a long time and then quickly drops.
@vegarroe
I come back to these old post. I run into the same problem. All other z-wave devices report battery state minimum every 6h. Only this device not. How ofter does your device update battery status?
Can you give me your parameter for:
parameter 19:
parameter 101:
parameter 111:
wakeup interval:
I think a combination of this 4 parameters controll the time interval to send battery status updates.
Tried these intervals without success.
The node is operating correctly but no battery status.
Any other suggestions?
And anyone else with a knowledge of how often it does report battery status? (I have seen it I know it can ;-))
I changed parameter 111 and wakeup interval to 240. Every 6 hours an update to the battery state is send now. Very strange because 240 means 240sec. But It is working even if the battery value is not changed, an update is send.
I did some log filtering and parameter changes last night and changed the parameter 111 to 720s and polling periode to 1 hour after reading this post: https://www.domoticz.com/forum/viewtopic.php?f=24&t=12136&sid=1a8380757f1c602355627e667314100e&start=20#p128293
and another forum where it was stated that there were trouble with battery updates if the parameter 111 was set below 10min (600s) (can’t find back to the forum where this was mentioned). Now I have had battery and status updates every hour!
For the reference here are the other settings:
1: Value that will be sent on open/close events
On for opened, Off for closed
39: Low battery threshold (10% to 50%)
20
101: Low battery voltage check
Enable
111: Low battery voltage check time
720
121: Reporting mode on open/close event
Send Basic Set CC
252: Lock/Unlock all configuration parameters
Unlock
255: Reset sensor to factory default and remove from network
0
From my testing it seems that the parameter that at the end defines when to get update for battery (and a status update for the switch) is the polling parameter, see screen shot. In addition the status of the switch of course are sent on change.
To get this working the parameter 111 has to be shorter than the polling parameter, e.g. 111 < 3600s for 1 hour polling. Mine is set to 111 = 720s.
What the difference parameters do (the ones valid for the node and the ones valid for the binding side) and how they interact and influence each other.
How to filter the logs (keywords) to easier post the correct parts of logs for faster forum response and understanding
