Domoticz

I have a counter that counts water usage (type counter incremental) called Watermeter2. Whenever a GPIO pin changes, I want to add 1 ltr to the counter. Domoticz measures in 1000's of litres. I tried domoticz.devices('Watermeter2').updateCounter(2) and (2/1000) but the Watermeter total doesn't update even though dzvents says it did:

2017-08-25 14:01:47.864 dzVents: Debug: Dumping domoticz data to /home/pi/domoticz/scripts/dzVents//domoticzData.lua
2017-08-25 14:01:47.878 dzVents: Debug: Event trigger type: device
2017-08-25 14:01:47.895 dzVents: Debug: Found module in /home/pi/domoticz/scripts/dzVents/scripts folder: water
2017-08-25 14:01:47.941 dzVents: Debug: Device-adapter found for GPIO 22: Switch device adapter
2017-08-25 14:01:47.952 dzVents: Debug: Processing device-adapter for GPIO 22: Switch device adapter
2017-08-25 14:01:47.953 dzVents: Debug: Device-event for: GPIO 22 value: Closed
2017-08-25 14:01:47.953 dzVents: Debug: Searching for scripts for changed item: GPIO 22
2017-08-25 14:01:47.953 dzVents: Info: Handling events for: "GPIO 22", value: "Closed"
2017-08-25 14:01:47.953 dzVents: Info: ------ Start external script: water.lua: Device: "GPIO 22 (GPIO)", Index: 14
2017-08-25 14:01:47.953 dzVents: GPIO Triggered Closed
2017-08-25 14:01:47.953 dzVents: Increase watermeter count by 1 LTR Closed
2017-08-25 14:01:47.954 dzVents: Debug: Device-adapter found for Watermeter2: Counter device adapter
2017-08-25 14:01:47.955 dzVents: Debug: Processing device-adapter for Watermeter2: Counter device adapter
2017-08-25 14:01:47.955 dzVents: Info: ------ Finished water.lua
2017-08-25 14:01:47.955 dzVents: Debug: [1] = UpdateDevice: 15|0|0.002

Any ideas?

H

Yeah, I noticed that too when testing. I suspect the counters aren't updated instantly somehow. Have you tried it with the json api?

Yes and that too works really weird. I reinstated my ESP which works fine: both daily and total counters are updated, i tried JSON and then the total gets updated but the daily only on/off which looks similar to updateCounter().
I looked at the espeasy firmware to see how it calls domoticz (http interface which stills work correct) but could not figure it out just yet. Downside of the ESP approach is that it randomly generates hundreds of litres of water at weird intervals. Swapped tcrt5000, swapped esp module, soldered leads directly, used different gpio ports to no avail. Hence connecting the tcrt straight to the pi's gpio and now I have this other issue.

Never a dull moment if it wasn't for being the laughing stock with 3 women around the house...

Which version of ESP easy are you using?
I've had better success with the mega beta versions over the R120 release.

Both unfortunately.

Meanwhile I found that updating with an external python script (on the forum) needs a counter divider of 3000 (triggers on gpio fall where every fall is 1 ltr). Python gpio and domoticz CAN both read the gpio port, right? I do see the gpio updates fine in domoticz but it's as if through dzvents, i need a divider of 1000.

Did you ever find a solution for this? This is driving me insane. I'm trying to build a script to put charged current from a solar panel array into one meter and consumption from the batteries into another one. But using dZvent and updateCounter() fails and I never get the sum for the the day, just the instant one. Sending the signal directly from ESPEasy works and Json doesn't work. Whats going on!?

olleman wrote: ↑Thursday 28 June 2018 21:29 Did you ever find a solution for this? This is driving me insane. I'm trying to build a script to put charged current from a solar panel array into one meter and consumption from the batteries into another one. But using dZvent and updateCounter() fails and I never get the sum for the the day, just the instant one. Sending the signal directly from ESPEasy works and Json doesn't work. Whats going on!?

You should not use a counter device, but a Electric (Actual + counter) (in Dutch: Elektra (Aktueel + teller). That way, Domoticz adds up all fed actual values to a sum of the day.

But en incremental counter set to energy should do the same, right? I have real instabillity issues right now and have had to revert to an older database several times. I'm wondering if feeding domoticz counter OR Actual+counter a value like 0.0045786 gives it headache? To many decimals perhaps?

EDIT: Seems like ESPEasy is updatering the energy meter incorrectly and that's what's crashing the database. IT works with json.

Edit2: How does the Electric + counter actually calculate the used power? If I send data from domoticz every 10 seconds and I want the energy i KwH then the value would need to be divided by 60*6=360. So if domoticz is reporting 1000watts usage "right now" then it would set 1000/360 as the "counted value" since a new value will come in the next 10 seconds?

Somethings off because this is my data table to the last couple of hours. The aggregated consumption is always a little low.
Sorry, this explanation sucks but with my english this is the best I can do

I found, that for all counters ( incremental too ), function :

domoticz.devices('Counter').updateCounter(value)

do not add ( increment ) value, but set counter state to value.

To increment counter by DZvents you must write something like this:
( add value in pom_spotreba in liters to water counter )

local aktual = domoticz.devices('Counter_spotreba').counter * 1000 + pom_spotreba
domoticz.devices('Counter_spotreba').updateCounter(aktual)

kimot wrote: ↑Thursday 20 June 2019 21:56 I found, that for all counters ( incremental too ), function :
domoticz.devices('Counter').updateCounter(value)
do not add ( increment ) value, but set counter state to value.

That is why in dzvents version 2.4.23 the method incrementCounter was implemented for incremental counters

Oh, very nice.
And thumb up that this information is already in the wiki now.