As suggested I also corrected the 'DeviceStatus' sValue.
The 'comparing usage' graph is now back to normal.

The KWh value for today however showed one large negative peak (the correction).
So I also corrected that wrong value in Meter_Calendar.
Now everything looks OK again.

Thank you for your ...

I use an incremental counter to log my electricity use.
Every 5 min the actual consumed KWh value in this period is sent to the counter via a MQTT message.
This was working fine for more than a year now.

Due to a power outage on 7 dec a wrong KWh value (more than 1000x than normal value) was sent ...

Thanks for the tip about why the comma's are being removed ! This put me on the road to a solution.

As a workaround I now set the second argument as 1_2_3 (no comma's but underscores).
This argument is passed by Blockly to the bash script as 1_2_3 as expected (and not secretly removing characters ...

Some further testing resulted in :

When I run the bash script from the command line with as second argument :
1,2,3 -> no problem, the MQTT message is sent out as 1,2,3
"1,2,3" -> no problem, the MQTT message is sent out as 1,2,3

When the script is called from Blockly with as second argument :
1 ...

I use a simple bash script to send out an MQTT message :


#!/bin/bash
# Generic MQTT send script
# $1 = topic
# $2 = message
mosquitto_pub -h 192.168.1.xxx -t $1 -m $2


I call this script with the Blockly element Start script ... with parameter(s) ... where the parameters are the MQTT's topic ...

My hall sensor generates a pulse after every rotation of the last digit on my gas meter (i.e. one pulse per 0.01 m3)
So the logging is done with 2 decimals.
If I check the logged values, the 3rd decimal is always 0.

Setup:
Domoticz 2022.1 running on a RPi 3
I have a gas counter (Type General, Counter Incremental) that counts pulses from a hall sensor on the gas meter.

I noticed that sometimes the values in the log graphs are not consistent.

The values in Domoticz "per hour" graph match perfectly with the ...

Indeed solved.
Thanks again FireWizard.

@FireWizard

Publishing via MQTT does indeed give me the 'real time' values of the sensor.
Thanks !

Can I publish the value of just one device to MQTT ? I don't want to flood my MQTT broker with all updates of all devices.

After inclusion in Z-wave the Heiman created device #1282 in Domoticz and it appears under the 'Temperature' tab.

I use the following flow :

flow1.jpg

The 'inject' node triggers every minute
The 'exec' node request the values of #1282 using curl -s 'http://192.168.1.xxx:8080/json.htm?type ...

I have a Z-wave temperature-humidity sensor (Heiman).
The sensor works fine and in Node-Red I can query the device every minute, but the values change only after 5 min.

I know the Heiman sends out values at shorter intervals.

How can I capture the Temp/Hum values in 'real time' and send them to ...

I think I found the answer :

The ozwcache*.xml is for open Z-wave 1.5+
If you have Z-wave 1.4 (like me), you would have a ozwcfg*.xml file

I am running Domoticz 4.10717 with Z-wave 1.4-3335 on a RPi 3 (Jessie).
I think my z-wave experience is similar to many others : z-wave devices will run smoothly for weeks even months, but suddenly they become unresponsive or are not recognized any more. Usually an exclude/include of the failed ...

I found the error.

The MQTT broadcast was triggered by an on/off type dummy switch with an automatic 'off ' after 3 sec.
So it triggered the script again again when it went to 'off '' .

I changed it to a 'push on' switch, and now is OK.

I fine tuned the MQTT broadcast by using the MQTTSyncTrigger label in the description field of the devices I want to sync.
This works fine, however about 1 second after all the messages arrived, they are being send again so I receive them twice.

It's not a big issue but is there a way to avoid this ...

Success !

I removed the script call from the dummy switch definition and renamed the switch to MQTT-Broadcast, the exact name in that is in the script.
I did not realize that : was referring to the triggering switch name .

Thanks waaren !

I tried triggering the script with a dummy switch using
script:///home/pi/domoticz/scripts/dzVents/generated_scripts/BroadcastAllDevices.lua
This generates a script command error 32256, so I changed the permissions for the script to 755.
Now it gives me error 512. I am new to dzvents so I'm not ...

Triggering the dzvents script via MQTT results in "Unknown command received: customevent".
Could it be that I need dzevents 3.0.0 to use customvents?
I am still on Domoticz 4.10717 which uses dzvents 2.4.19 .

If I send this call in a browser window /json.htm?type=devices&used=true Domoticz replies with the status of all my devices. This is exactly what I need.
However I would like to achieve the same thing using a MQTT call in Node Red en also receive the answer via MQTT.
In Node Red I tried sending a ...