This happened at regular z-wave devices but indeed not connected or connected device not used (yet). Silence the warning would be a good idea to prevent future concerns.

Grtz, Mark

I analyzed/tested things last night and this morning: I get (got) the log messages at every poll with the actual value being 0. As soon as the accumulted value is non-zero, the message no longer appears.
So I made sure that the 'faulty' devices had a non-zero kWh value and I have a clean log now ...

Sorry for the late answer but I've been hospitalized so couldn't try things out. I'm getting better now but not this problem.

I checked for retained values: there are none. To be sure I deleted all value messages using MQTT Explorer, log messages keep coming.

I excluded/included one of the error ...

Updated from version 2025.2 (build 16922) to version 2025.2 (build 16954) and found next status in the log:
Status: ZWave-AD: Counter Looped detected on first received value for: PN1 (PN1_electric_kwh_value)/zwavejs2mqtt_0xfe88fc1e_8-50-0-value-65537, could be an old retained value?

This status ...

This morning all looks ok, battery level is populated for almost all (sub-)devices. I tested with updating the Hardware in order to check the generation of battery_level devices as it was the case in the faulty situation. Every thing is ok now and my battery check is working again.
Thanks for ...

No, I have no low batteries, all Low Battery devices are false. Hereby the configs for battery_islow ( state_topic: IsLow ) and battery_level ( state_topic: level ) {
"payload_on": true,
"payload_off": false,
"value_template": "{{ value_json.value }}",
"device_class": "battery",
"state_topic ...

Updated my live system to Trixy and applied the Domoticz update, Z-wave batterylevel problem remains the same. And yes, I did a wake-up on sensors and updated hardware (in case you wondered).

Doler wrote: Tuesday 12 August 2025 14:58 I'll try to switch to Trixy on my test system and see if it works.

Ok, Domoticz updated fine. Going to do the same on my live system (backup first) and see if the Z-wave problem is solved. Thanks sofar.

I'm running the virtual machine on Proxmox that is still running on Debian bookworm. There is a Proxmox upgrade 8 to 9 that is based on Trixy but other than running a script checking if Proxmox is ok for an upgrade. I did nothing else since I wanted the problem with Domoticz be solved first. So I ...

Never had problems before. My bookworm version number is:

No, I'm running Debian Bookworm on a virtual machine (AMD64).

Hmm,

After updating Domoticz won't start anymore. Status message: What to do?

zwave/FMS1/128/0/isLow
{
"time": 1753016911001,
"value": false,
"nodeName": "FMS1",
"nodeLocation": "Living"
}
zwave/FMS1/128/0/level
{
"time": 1754261342547,
"value": 100,
"nodeName": "FMS1",
"nodeLocation": "Living"
}

The not truncated configs for FMS1: zwave-ad/sensor/FMS1/temperature_air/config
{
"value_template": "{{ value_json.value }}",
"unit_of_measurement": "°C",
"state_class": "measurement",
"device_class": "temperature",
"state_topic": "zwave/FMS1/49/0/Air_temperature",
"availability ...

All latest version (see my signature).

I forgot to mention that the newly created devices (Battery_level) are NOT updated.

Sinds some time I'm missing the battery level report on Z-wave devices. It concerns motion sensors from Fibar/Neo and doorsensors from Neo. I am checking battery levels with a Lua script using:
local function getDevices()
local url = dz.settings['Domoticz url'] .. "/json.htm?type=command&param ...

[/quote]

Thanks for your answer. Do you mean that Domoticz would combine if there was only temp and humidity, but as there is also battery and signal strength Domoticz has no combined device and decides not to combine temp + humidity on one side and let battery and signal strength single?

By the ...

I probably had a combined temperature/humidity device but in the mean time I hacked these meters to use the Zigbee protocol as that is an interface I already used.
I do have some DIY temperature meters based on ESP32 that I programmed for auto discovery in Domoticz. From that I learned that Domoticz ...

@JanJaap

I recently bought a Tesla Model Y and thought I should try the integration with Domoticz. All did go well until the start of the new hardware were I met the following error:
2024-07-16 10:13:47.938 Status: Tesla: Started.
2024-07-16 10:13:48.387 Status: Tesla: Initialized version 0.8.1 ...

The way I solved this is to capture the status as changed by the script in dzVents data (data = { savedState = { initial = 'Off' }}). Whenever the script changes the state, change the savedState accordingly. So when you use a physical button this savedState remains unchanged. Then in your script you ...