Almost. 53 is the property, and 2147418112 (0x7fff0000) is the property_key. The property key denotes the partial part in this case. You can also nearly find these fields by looking at the network dump. Search for the parameter and you’ll find the same fields.
and then the sensor value will use the trigger.current_value data to get the battery voltage?
That sounds right.
Configuration parameters also have their own special trigger type that isn’t documented, but it’s available in the UI. I’m not sure if this works in a trigger-based template or not (I would think it would?), but you could try it. You just go to the Automation Editor UI, create a new automation (temporary, no need to save) and select a configuration value trigger, then just convert it to YAML and copy and paste into the trigger of the sensor.
You can delete the null value since it doesn’t apply. Again, I haven’t tried this particular trigger before, so it may or may not work as a template trigger.
I will say, there is a downside to trigger-based sensors based on this value updated event. When you restart HA, the sensor value will be unknown until the config parameter actually changes. There needs to be a real event (a config param value change) while HA is listening for the trigger to occur and update the sensor. If the parameter does not change often, it won’t be that useful.
I think it’s likely too much work for only a little payoff.
the trigger wasn’t available for those parameters in the UI drop down. Likely because they are read-only (?).
Hopefully the “power management replace battery soon” entity works and I can use that for battery status.
Still don’t know why I only have one of those if I have two button while @tmjpugh seems to have 3.
But it’s still better than zwave1.4 that didn’t have any battery status and I just relied on the flashing light
on the doorbell itself for low battery notifications.
But I’m always glad to learn more stuff so thanks anyway.
EDIT: interestingly again…
I just looked back at a previous post of mine above from Apr 9th and in that screenshot there actually was a battery class section there. So it was there at some point and now it’s not.
I too have had a doorbell 6 since the first month they were available and very quickly gave up trying to do any sort of automation (i use node-red). If you want to slay the Doorbell 6, move to Z-Wave JS to MQTT, which I did last week. The interface let’s you change sounds, duration, all of it. Then use node-red for automation. [Here is a shout out for node-red. I moved all of my automations over to node-red about two years ago. No lookin’ back once you make the change.] Once you move toZ-Wave JS to MQTT, it is simply turn on siren #n and turn it off when you want. Super simple. BTW. if you haven’t seen them, aeotec is now selling the buttons on amazon for about $16.
Yes, I know, it is a journey to move to Z-Wave JS to MQTT. I elected to go the scorched-earth route with my z-stick. I removed all of the devices from the z-stick, factory reset all the devices, then went through the process of adding them all back using Z-Wave JS to MQTT. I have 34 devices. It took about 6 hours. While Z-Wave JS to MQTT is a big improvement, it is not without its defects so be prepared to be patient.
I also spent a couple of hours getting this to work: Remove a Failed Node using Zensys Tool / PC Controller 4 : Aeotec Help Desk The utility that aeotec offers is down a major version, has an unsigned driver for pre-win10, which requires some work to install on pre-win 10 machines. The driver for the z-stick is native in Win10. It is very useful for managing dead nodes.
