PulseCounter - GasMeter

---

Hey,

i have a Wemos D1 Mini 4MB, flashed with Espeasy. I count pulses with a reed sensor of my gasmeter. The transmission works very well. Every Count is sending by mqtt protocoll to pimatic. So i count the pulses and add every puls 0.01m3 to the var.

But now, thats all. How can i add a day/week/Month view Like This one:

Image by @OrTiN

Can i realize this with pimatic? Or is there a Plugin to use?

Thanks!

noone a idea?

@schmucke There are various plugins (emon/volkszähler/smartmeter, etc) which implement this kind of functionality (in most cases combined with a another building block to facilitate the data logging and accumulation into different registers). It is possible to implement such functionality as a generic building block into pimatic but it is a fair amount of work.

For the time being my suggestion is to have a look at Volkzähler. It should be possible to use it along with espeasy as far as I understand this.

http://wiki.volkszaehler.org/
http://wiki.volkszaehler.org/hardware/controllers/espeasy
https://pimatic.org/plugins/pimatic-volkszaehler/

I have 2 pulsreader with 2 arduinos and read the water and elektrometer in my home. The project is Kompf.de. The software read the serialports of 0/1 input and write this in a rrd.

@Jens perhaps this plugin

https://forum.pimatic.org/topic/3908/new-plugin-pimatic-charts

can also be an improvement to make the data visible in the pimatic gui. I haven’t tested it, but it seems to be quite nice.

@schmucke

You can display such statistics using variables.

I implemented it this way:
You can adapt this to your counter varable instead of $powermetercounter.

In your case the current consumption can also be calculated via a variable
and display the delta each minute for example. (it depends on how often a pulse is generated)

Variables:

$daycounter
$yesterdaycounter
$weekcounter
$powermetercounter <- your m³ var
$currentcounter

Rules:

when its 0:00 then $yesterdaycounter = $powermetercounter - $daycounter and after 1 second 
$daycounter = $powermetercounter
when its 0:00 and monday then $weekcounter = $powermetercounter
when every 1 minute then $currentcounter = $powermetercounter

VariableDevice for the GUI with

current consumption = $powermetercounter - $currentcounter
today = $powermetercounter - $daycounter
yesterday = $yesterdaycounter
week = $powermetercounter - $weekcounter

For month, year an total you can make it the same way.

The result is this:
The last device is the variable device.
The charts are generated with the charts-plugin.

The yesterdaycounter variable is also a good candidate for display in a chart,
because it changes once a day.

@kosta said in PulseCounter - GasMeter:

@schmucke

You can display such statistics using variables.

I implemented it this way:
You can adapt this to your counter varable instead of $powermetercounter.

In your case the current consumption can also be calculated via a variable
and display the delta each minute for example. (it depends on how often a pulse is generated)

Variables:

$daycounter
$yesterdaycounter
$weekcounter
$powermetercounter <- your m³ var
$currentcounter

Rules:

when its 0:00 then $yesterdaycounter = $powermetercounter - $daycounter and after 1 second 
$daycounter = $powermetercounter
when its 0:00 and monday then $weekcounter = $powermetercounter
when every 1 minute then $currentcounter = $powermetercounter

VariableDevice for the GUI with

current consumption = $powermetercounter - $currentcounter
today = $powermetercounter - $daycounter
yesterday = $yesterdaycounter
week = $powermetercounter - $weekcounter

For month, year an total you can make it the same way.

The result is this:
The last device is the variable device.
The charts are generated with the charts-plugin.

The yesterdaycounter variable is also a good candidate for display in a chart,
because it changes once a day.

And how dies the rule Look Like for month and year?

@kosta

Thank you for your rules! Nice - i give them a try today.

@temp

i think, i realise the month and year quick and dirty like this one:
I have create a shellsensor device which is get the 1st day of month like:

      "attributeName": "1stday",
      "attributeType": "string",
      "command": "sudo date +'%d'",
      "id": "1stday",
      "name": "1stday",
      "class": "ShellSensor",
      "interval": 60000
    }

and every day at 00:01 i check if it is a new month by this rule:

{
      "id": "1stday",
      "name": "1stday",
      "rule": "when its 00:01 and 1stday of 1stday is \"01\" then set $gasMonat to 0 + $gasStunde",
      "active": true,
      "logging": true
    }

and now i will create a var like $gasYear what i will fill with the $gasMonat var…

^^^thats all untestet yet…

this should also work

when its "first day of month 00:00" then $monthcounter = $powermetercounter
when its "Jan 01 00:00"  then $yearcounter = $powermetercounter

see cron first day of month

@schmucke said in PulseCounter - GasMeter:

@kosta

Thank you for your rules! Nice - i give them a try today.

@temp

i think, i realise the month and year quick and dirty like this one:
I have create a shellsensor device which is get the 1st day of month like:

      "attributeName": "1stday",
      "attributeType": "string",
      "command": "sudo date +'%d'",
      "id": "1stday",
      "name": "1stday",
      "class": "ShellSensor",
      "interval": 60000
    }

and every day at 00:01 i check if it is a new month by this rule:

{
      "id": "1stday",
      "name": "1stday",
      "rule": "when its 00:01 and 1stday of 1stday is \"01\" then set $gasMonat to 0 + $gasStunde",
      "active": true,
      "logging": true
    }

and now i will create a var like $gasYear what i will fill with the $gasMonat var…

^^^thats all untestet yet…

Can You Post your Tested Setup then?

Instead of doing all the twist with rules I think it is worth having a look at Volkszähler.

@mwittig said in PulseCounter - GasMeter:

Instead of doing all the twist with rules I think it is worth having a look at Volkszähler.

i give them a try too. but i dont want another plugin. i will try i on a testraspberry

@temp yes i can post my setup then. @OrTiN will post his setup too. i wait for it

@schmucke said in PulseCounter - GasMeter:

@mwittig said in PulseCounter - GasMeter:

Instead of doing all the twist with rules I think it is worth having a look at Volkszähler.

i give them a try too. but i dont want another plugin. i will try i on a testraspberry

@temp yes i can post my setup then. @OrTiN will post his setup too. i wait for it

I Need to do the statistics with rules due to the fact I want to generate it for my smart voltage plug

@kosta said in PulseCounter - GasMeter:

this should also work

when its "first day of month 00:00" then $monthcounter = $powermetercounter
when its "Jan 01 00:00"  then $yearcounter = $powermetercounter

see cron first day of month

this rule is not working. this rule reset my var tonight.

I did a little test around the rules.
These ones work:

When its "11th of month" and its 18:48 then
When its "1st of month" and its 00:00 then
When its "Jan 12 18:45" then
When its "Jan 01 00:00" then

i think you think i have no life - answer in 60 sec…

i try it - have u set the date the raps to test it?
Thanks!

The date must be in double quotation mark like above.

Hi,
i have a question to the decimal place. With a shell sensor-device read i my water and elektro counter.

In Pimatic show this with the units water–> m³ and elektro–> kW

But i read from rrdtool 3 decimal places for water and 2 decimal places for elektro consum. When i change the unit, then change the decimal place?

But i need 3 places for water. How can i make this?

THX.

@Jens
The frontend plugin has for some units special places. see here

The variable itself should has 3 places. Look at the variable manager.

Maybe this workaround helps:
Create a new variable device with this expression.

formatNumber(($shell-device.value) ,3 , " m³")

Hi kosta,
with this expression change the type from number to string. Can i change my scope.coffee file to the decimal places for m³, or are information over the number format in another files stored?