Domoticz

I have implemented ZwaveJSUI with MQTT Auto Discovery, and almost everything works ok.
Except one thing i cant figure out..

All of the sub devices from my sensors are added as devices (illuminance, temperature, motion) inside domticz.
Also the batterylevel for the sensors is auto discovered.
'2023-02-16 18:01:05.194 Status: MQTT-Discovery: discovered: Sensor huiskamer/Sensor huiskamer_battery_level (unique_id: zwavejs2mqtt_.._7-128-0-level)'

But there is no device added for the batterylevel...
Anyone has a clue why this is and/or a solution?

thnx.

Battery level is in Domoticz an attribute of the device. You can see the battery level in the device list (menu setup - devices).

Further you can set Battery Low Level settings notifications in menu setup - settings - others.

Here you can set the level at which you get a notification that the battery level of the device is low. 0 = no notification.

A device widget will become yellow to indicate it is below set battery level.

It is that the batterylevel atribute is not showing in the device list (setup > devices)
Only the 4 other atributes of the device (illumination, temperature, motion, low battery) are in the device list.
And that while there are 5 attributes of the device discovered by MQTT Auto Discover. (this is showing in the logs)

Are you already on 2023.1 as I believe battery level was fixed in this version.

Yep, already on 2023.1

To be sure we understand each other, you do not see the indicated battery status as shown on the screenshot below.
It could be that it is not sending the level value that Domoticz is expecting.
Perhaps make a GitHub issue with the discovery, config and state topic names and payloads so that the developer easily reproduce your situation and hopefully fix it.

Nope, the battery level is also not showing in domoticz, on any zwave device at setup > devices (1).
(like i said, in the domoticz log the batterylevel attribute is discovered)

In the ZwaveJSUI (2) the battery level is shown, and also the discovery for the attributes are enabled..



But the main thing is, why the batterylevel is not added under setup > devices and the other 5 attributes do...

With OZW i had a seperate dzvents script to check daily the battery levels, updated a dummy battery device, and send me a sms warning if this was going low.
This is also possible with the battery low attribute, but i liked it to also see if a device is not low, but at 50%.
But over all it is a minor (but strange) problem... and i will make a github issue..

thnx for the reply

Hi,
I noticed that the battery levels are not corresponding with the battery levels in the Zwavejsui
Is there any news regarding this issue?

What kind of mismatch do you have?

It was with an Aeotec ZW130 Wallmote quad switch and only the last used switch updates the battery symbol in the devices page, the other battery symbols of this Wallmote are only updated after pressing the buttons.

So this was a mistake on my part.

I also did some searching on the internet and I came across this: https://theawesomegarage.com/blog/updat ... js-devices
Is it possible to implement something like this in Domoticz?

That should already be implemented in Zwave-JS-UI https://github.com/zwave-js/node-zwave-js/pull/5560
Perhaps update Zwave-JS-UI?

So I updated to latest Zwave-JS-UI and now there are two battery nodes that do not have battery symbols anymore, in the domoticz log the batterylevel attribute is discovered but the batterylevel attribute is not showing in the device list (setup > devices)

Now I am over asked as I do not use MQTT AD and Zwavejsui

RPi 3b: Bullseye
Domoticz: latest beta
Zwave-JS-UI: latest

Hi, I did some more digging and it is even worse, only nodes with the "Battery_level_status" attribute in their discovery create a device in the devices menu.
The nodes with only "Battery_level" attribute in their discovery are not creating a device in the menu.

Can you transfer this issue to github?

I will not do that. It seems something local on your setup as else everybody using Zwavejsui has the same issue and that does not seems to be the case.

Same here