Z-Wave JS and Node Battery Level

redwngsrul · February 8, 2021, 4:39pm

Previous to the new Z-Wave JS integration, I was using the legacy Z-wave system. Through this system, home assistant was able to gather some hardware info from each node, particularly one of the attributes was the battery level of the node. I used this attribute of the node for automations, specifically to let me know when one node had a low battery level. This new Z-wave JS server system though doesn’t seem to poll for hardware info, and I’m currently unable to tell the battery level of my nodes. Does anyone have any suggestions? This might be a better question for the guy who made the Z-WaveJSMQTT system, but I thought I’d start here.

Thanks.

freshcoast · February 8, 2021, 4:48pm

Battery levels have been their own sensors in zwave for a long time now, as well as in ozw and now zwave-js. There shouldn’t be any need to use the zwave battery attribute even now.

For all integrations you should see some sensor (percentage) and for zwave-js there may be an additional binary_sensor (battery low).

redwngsrul · February 8, 2021, 4:59pm

Well for some reason, the new Z-WaveJS system isn’t receiving any data on battery levels or PIR status. These are the only sensors I receive from my Aeon Labs ZW100 multisensor.

using the old legacy integration, I was getting all of these sensors.

Any idea why the other values aren’t being registered?

freshcoast · February 8, 2021, 5:01pm

You need to wake up the battery devices so they are discovered. I can barely read your zwavejs2mqtt screenshot, but the device is in ProtocolInfo state, it needs to be Complete. (See docs).

eBoon · February 8, 2021, 5:49pm

I’m seeing the same thing with my Kwikset 916 locks. Without the zwave domain, I no longer have things like alarm_level and alarm_type. Did see sensors for battery level etc - but nothing for the alarm types and level.

freshcoast · February 8, 2021, 6:02pm

Those are hidden by default, you need to enable them. There’s also an issue that’s fixed in next patch release to show the correct values.

redwngsrul · February 8, 2021, 6:03pm

My nodes have been in ProtocolInfo for several days. I ended up performing “Re-Interview Node” on one of them (node 6) and it finished the interview process (Complete) and now I see all my values. I just have to figure out which ones to send to HASS now. Still can’t get node 10 to complete, same thing it’s been in ProtocolInfo for days, even though the wake interval is 1800 secs.

eBoon · February 8, 2021, 6:29pm

Thanks! - I’ll have to give it another go then. Do you know where they can be un-hidden?

decairn · February 8, 2021, 6:33pm

I can confirm the HANK door sensors create both a battery % level sensor and a low battery binary sensor. No need for template.

Northerner · February 9, 2021, 4:44am

I have a Schlage Connect door lock and the battery sensors are now showing as unavailable. The other sensors are working. Before the switch to JS the battery sensors were all functioning properly.

mightybosstone · February 9, 2021, 6:06am

Under Configuration - Integrations - Z-Wave JS

Click on the “xx devices” link
Click on the entity in question
Under the “Entities” section you’ll see any that are disabled

Untitled408×737 43.3 KB

Northerner · February 9, 2021, 8:23pm

Solved. Z-Wave JS update 0.1.5 fixed the battery sensor issue I was having. BE469ZP lock is now working as it should and reporting on all sensors.

Giel538 · February 11, 2021, 6:52pm

I switched from zwave2mqtt to zwavejs2mqtt. I use the websocket now to integrate.

I updated the zwavejs docker to version 1.1.1 and l lost all the battery connected devices. I have to re-interview them again. I never had this problem with zwave2mqtt. IS anyone else having the same issues ?

ericp · February 16, 2021, 9:41pm

I updated to zwavejs docker just now and just like you, i lost all the battery connected devices. I had to exclude and re-include them.

Soccs · February 22, 2021, 12:44pm

Hello,
I am very noob, if someone could help me revert to version 1.1.1 please?

Dolores · March 22, 2021, 1:54am

I am having a similar issue, except that my multisensor 6 is showing no entities whatsoever. I’ve woken the multsensor, but that hasn’t changed anything. Is there anything I need to do on the home assistant side to get it to re-interview the node?

quizzical · April 2, 2021, 5:28pm

I have factory reset my aeotec Zstick Gen5+, removed the z-wave integration and all z-wave devices in home assistant, etc to try to solve the issue that I didn’t get all sensors of the aeotec multisensor 6:

What finally sees to have solved it for me was to add it in secure mode. Now I have everything.

tung256 · April 6, 2021, 3:14pm

how do i wake up the device’s battery?
using the Zooz 4in1 sensor and the battery level is incorrect at 0%. it is the 3v battery and volt meter shows 3.4v so i know the battery is still good.

petro · April 6, 2021, 3:25pm

check the manual on the device, waking up hardware is hardware dependent. Also, I’ve noticed that most devices don’t report battery levels properly when dealing with normal disposable batteries like AA or AAA.