Hi,
well I must say that I also had some extra pulses, so I am playing a bit with the position of the proximity sensor. Now it did run 1 day without ghost pulses, let’s see how it continues 
With the TCRT5000 sensor I also had them, but I changed the position with 90°, as I think that when the rotary dial with mirror passes too slowly or stops, it could get some of these extra pulses. So I hope that having it now in a different set up, it will be better! Will keep you posted
UPDATE ON ORIGINAL POST
After having a bit of a play about over the Christmas holidays and thinking about the best way to get this working I changed the YAML code from that previously posted, or more accurately, changed the C++ code in the Lambda function within the YAML code
I’ve now had this running for over 48 hours and it seems to be logging the needle as it passes under the IR sensor quite accurately now, as can be seen from the screenshots below.
IR Sensor ADC Values
This screen grab shows the values being logged from the ESP32’s ADC using the analog output from the IR sensor. The red vertical sketch line is the last time the ESP32 was reset. The spikes on the graph are the needle passing below the IR sensors emitter and receiver. For clarity, the narrow spikes are when the burner is turned on (needle rotating fast) and the wider spikes are when the burner is off and just the pilot light running (needle running slowly). The darker blue numbers scribbled near the spikes are the number of rotations of the meter dial which equate to 1 ft3 of gas since the last reset (red vertical line). This screenshot shows 11 ft3 used since the last reset of the ESP32.
Actual Logged Consumption
This is a screen grab from HA itself, and the gas consumption figure correlates to the spikes shown on the previous graph, 11 ft3
YAML Code
name: gas-meter-monitor
esp32:
board: nodemcu-32s
# Enable logging
logger:
# Enable Home Assistant API
api:
encryption:
key: "HNNVUMR69RNNJBK9q+LCtVwenVKZpL1en2+jzl0VaHE="
ota:
password: "a306ebc5fe5e8fb5c286227999570932"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Gas-Meter-Monitor"
password: "kCTrfHhD3FcG"
captive_portal:
globals:
- id: total_pulses
type: float
restore_value: false
initial_value: '0.0'
- id: max_pulse_value
type: float
restore_value: false
initial_value: '0.1730'
# This sensor exposes the 'total_pulses' variable to Home Assistant and
# tells HA it is to ft³
sensor:
- platform: template
name: "Gas used"
device_class: gas
unit_of_measurement: "ft³"
state_class: "total_increasing"
icon: "mdi:fire"
accuracy_decimals: 0
lambda: |-
return id(total_pulses);
# This is the reading of the voltage on the analog input pin Take a measurement every 50ms but only report the average
# every 2 seconds. This is to overcome the noisy ADC on the ESP32, and also to see if the sensor is 'seeing' the rotating needle
- platform: adc
id: adc_value
pin: GPIO32
accuracy_decimals: 4
name: "Gas Meter Sensor Analog Value"
update_interval: 50ms
attenuation: 11dB
filters:
- throttle_average: 2sec
# When a new voltage measurement is received, calculate the
# difference with the previous voltage. If it's larger than
# a certain threshold, increase the pulse counter and also reset the maximum value
# to the current value for the next needle rotation
on_value:
then:
- lambda: |-
float current_pulse_value = id(adc_value).state;
float last_pulse_value = current_pulse_value;
float diff = id(max_pulse_value) - current_pulse_value;
if(current_pulse_value > id(max_pulse_value)){
id(max_pulse_value) = current_pulse_value;
}
if(diff > 0.008){
id(total_pulses) += 1;
}
if(diff > 0.008){
id(max_pulse_value) = current_pulse_value;
}
# Uptime sensor
- platform: uptime
name: Gas Meter Uptime
# WiFi Signal sensor
- platform: wifi_signal
name: Gas Meter WiFi Signal
update_interval: 60s
# Switch to restart
switch:
- platform: restart
name: gas meter monitor restart
Brief Explanation of How It Works
When there is no needle under the sensor the ESP 32 reports back a pretty steady voltage level. The ADC is quite noisy but the voltage is read every 50ms and averaged before reporting this every two seconds - smooths it out a bit.
As the needle starts to pass under the IR sensor, the voltage output on the sensor rises and reaches a maximum (in my case) of 0.183 V and after this peak starts to fall back to around 0.172 to 0.174 V - these are the peaks and troughs on the above graph.
As the needle starts to pass under the sensor, the ESP32 checks the current value of the IR sensor and compares it to the max_pulse_value of the IR sensor since the last rotation, and if it is higher, it will log that newer value as max_pulse_value. This means that we can obtain a maximum value from the IR sensor as the needle rotates under it, and we then know that the needle has passed under the sensor.
There is a variable named ‘diff’ which is the difference between the max_pulse_value and the current_pulse_value - this number is changing all the time as the needle rotates and passes under the IR sensor; it will increase and decrease in size as the needle rotates.
What we want to know is this “When has the needle definitely passed the IR sensor”. (and also when it has passed the IR Sensor, then increment the gas consumption figure by 1 ft3). This is done in the Lambda function which is C++ code, not YAML. The IF statements within the Lambda function are used to determine the difference in voltage between high and steady state, that ‘difference’ being 0.008V in my case. If this difference is exceeded, then the needle has passed the IR head as the difference between the peak sensor value and the lower ‘steady state’ value is at it’s maximum level. When this large difference occurs, the total_consumption variable is increased by 1, and max_pulse_value variable is reset to the current level, to enable the next rotation of the dial to be ascertained - and the process starts again.
I hope the above explanation is clear. If anybody wants to use this method the ‘0.008’ figure within the Lambda function will need to be changed to suit your own purposes. It would be best to set up a dashboard where you can monitor the value of the ESP32’s ADC value from the sensor, or you could sit and watch the ESPHome Log scroll past to monitor voltages/ADC values. You will need to find the maximum values and “steady-state” values of your own installation. When the dial passes under the IR Sensor this will provide the maximum value, and when the dial is away from the sensor (180 degrees opposite, it will be the lowest value). It is these ‘max’ & ‘current’ values which determine the ‘diff’ threshold in the Lambda function - and thus the success of the total_consumption variable being increased every time the needle passes the IR Sensor.
I do hope this helps somebody, and please do feel free to respond if you feel I can be of any help at all.
Thanks to all who contributed, and offered suggestions. Your input was much appreciated and valued.
Cheers,
Mike.
Just a further update.
Gas monitoring is working well, and I have created an ‘at a glance’ type dashboard. This contains cards such as ‘Daily Consumption’, ‘Weekly Consumption’, ‘Monthly Consumption’ etc.
In order to do this I first created a “Gas Meter” using the Meter preset in the Helpers section and used the sensor ‘gas_used’ (which is based on the total_pulses variable from the IR sensing head). This Helper is the gas meter, and can be added on a card to the dashboard.
This is from my gas meter and it reads in hundred’s of ft3 - the actual reading on the dials of my meter is 1994.90x (x= whatever fraction of ft3 the small dial is pointing to)
The problem here is the readings off this meter in the dashboard and the physical gas meter in your house will be different, as the HA Dashboard Meter will only start recording gas used from the time you create it. This is when it should be calibrated to match the existing meter reading.
If you go to Developer Tools > Services and add this yaml (below) to the box, it should replace the current gas meter value with 30208. You would click the ‘Call Service’ button to calibrate with this value you have entered. The value has to be whatever is on your gas meter reading - try and do it when the dials on the meter are static for the best accuracy.
service: utility_meter.calibrate
target:
entity_id: sensor.gas_meter
data:
value: '30208'
After doing the calibration is it a simple procedure to then create other Helper Meters to cover Daily, Weekly, and Monthly gas consumption. These Meters can go on separate cards on the Dashboard for ‘at a glance’ reading.
Cheers,
Mike.
Now Added a "at a glance dashboard"
The Gas Meter monitor is now seemingly to be working well and is accurately logging the dial rotations. This is feeding into the standard Energy Dashboard and calculating a cost. As noted above, I decided to create a Dashboard with all the relevant gas consumption figures on it… and here it is.
The next stage for me is to add kWh conversions to each card on the dashboard, and also a cost to each card on the dashboard… that is beyond my experience yet on HA. I will do an update when I manage to get something working though.
Cheers,
Mike.
Now added costs and kWh conversion to ‘Gas’ Dashboard
As noted in my previous post, I was looking to add a kWh figure and a cost figure to my dashboard. I have done this by creating several new ‘sensors’ in my configuration.yaml file, and also by using the Meters Helper to log the information.
‘Gas Dashboard’ as it currently stands…
The additional sensors I created are noted below:-
template:
- sensor:
- name: "Daily Gas Consumption kWh"
unique_id: daily_gas_usage_kwh
state: "{{ ((((states('sensor.gas_consumption_daily_v2')|float * 0.0283) * 1.02264) * 39.9) / 3.6)|round(2) }}"
availability: "{{ states('sensor.gas_consumption_daily_v2')|is_number }}"
unit_of_measurement: "kWh"
device_class: energy
state_class: total
- name: "Daily Gas Cost"
unique_id: daily_gas_cost
state: "{{ (((((states('sensor.gas_consumption_daily_v2')|float * 0.0283) * 1.02264) * 39.9) / 3.6) * 0.09835)|round(2) }}"
availability: "{{ states('sensor.gas_consumption_daily_v2')|is_number }}"
unit_of_measurement: "£"
device_class: monetary
state_class: total
- name: "Weekly Gas Consumption kWh"
unique_id: weekly_gas_usage_kwh
state: "{{ ((((states('sensor.gas_consumption_weekly_v2')|float * 0.0283) * 1.02264) * 39.9) / 3.6)|round(2) }}"
availability: "{{ states('sensor.gas_consumption_weekly_v2')|is_number }}"
unit_of_measurement: "kWh"
device_class: energy
state_class: total
- name: "Weekly Gas Cost"
unique_id: weekly_gas_cost
state: "{{ (((((states('sensor.gas_consumption_weekly_v2')|float * 0.0283) * 1.02264) * 39.9) / 3.6) * 0.09835)|round(2) }}"
availability: "{{ states('sensor.gas_consumption_weekly_v2')|is_number }}"
unit_of_measurement: "£"
device_class: monetary
state_class: total
- name: "Monthly Gas Consumption kWh"
unique_id: monthly_gas_usage_kwh
state: "{{ ((((states('sensor.gas_consumption_monthly_v2')|float * 0.0283) * 1.02264) * 39.9) / 3.6)|round(2) }}"
availability: "{{ states('sensor.gas_consumption_monthly_v2')|is_number }}"
unit_of_measurement: "kWh"
device_class: energy
state_class: total
- name: "Monthly Gas Cost"
unique_id: monthly_gas_cost
state: "{{ (((((states('sensor.gas_meter_monthly_v2')|float * 0.0283) * 1.02264) * 39.9) / 3.6) * 0.09835)|round(2) }}"
availability: "{{ states('sensor.gas_meter_monthly_v2')|is_number }}"
unit_of_measurement: "£"
device_class: monetary
state_class: total
The new sensors take the totals from various Meter type Helpers I created i.e. ‘sensor.gas_consumption_daily_V2’, or ‘sensor.gas_consumption_weekly_V2’, and then undertake either a kWh conversion or a cost conversion on the figures created by the Helpers… and as these costs or kWh ‘sensors’ have unique names, they can be quite readily added to Entity cards in a dashboard for review.
Obviously, if my gas unit rate (we get billed in £/kWh here in the UK) changes, I will have to change the figures in the yaml code, but this isn’t difficult to do.
The next step for me is to add a “Standing Charge” cost… (here in the UK we get billed a fixed amount per day from the gas company, irrespective of how much gas we use - this is £0.2712 with my current gas supplier)… and I could add this into the daily, weekly monthly calculations in order to get a more accurate reflection of what my next bill will look like and also add the 5% VAT (tax) onto the bill too, for even greater accuracy.
I hope this helps somebody, and if anybody does have any questions do feel free to ask, and I’d be more than happy to help out where I can.
Cheers, 
Mike.
1 Like
This is very intriguing. I have a very crude meter (see below), so this won’t work for me.
Did you set up a normal HA integration, a HACS integration, or some other way to import the data?
Hi Will,
I used the ESPHome add-on for HA. I don’t know if you are familiar with ESPHome, but it is a fantastic way to create custom sensors for your Home Assistant setup. I bought some ESP32 WiFi/Bluetooth-enabled microcontrollers from Amazon and used these with other sensors to feed back into HA. You upload code etc to the ESP32 module using the ESPHome add-on. Sounds complicated, but it isn’t really in practice. If I can do it, anybody can! 
BTW I added a few more thoughts to your initial post on the thread you created earlier.
Cheers,
Mike.
1 Like
I currently have a couple of Kauf bulbs, a couple of Kauf plugs, and a couple of Athom plugs, so have an exposure to ESPHome (and have updated .yaml files, etc), so that’s one very interesting option. Thanks for the tip!
1 Like
I have the exact same gas meter as you, except mine is from 1986
I am probably going to try to reproduce your set up, except I will use C++ and a RPi Pico because I prefer to work with that.
Your problem of turning the analog signal into a series of events is a standard signal processing task. Typically you would simply low pass filter the signal and look for maximums (peaks). This is pretty much identical to the solution you found.
Do you have any advice on sensor positioning and mounting? And approximately how fast does the dial turn at maximum? (Thinking about how often I need to sample in order to never miss rotations.)
edit: I’ve been reading up about gas meters and the one we have is called “U6 UGI Black Spot”. Apparently these are known for over-reporting.
Hi Alistair,
Congrats on your “choice” of gas meter!!! 
In answer to your questions on positioning, see attached photo of where the sensor is located on mine. The red circles I have drawn on are the IR Tx & Rx LED’s… I tried to get them at the 3 O’clock position as this would still enable me to read the meter in order to check the reliability of the logging. (so far, it’s not missed a beat!) and also, on the clear plastic faceplate there is a small, raised perimeter upstand which prevented the 3D-printed sensor housing from moving further over to the right.
Regarding the speed of dial turning… here is a screen grab of the voltage peaks when the burner is on full. You should be able to work out the peak to trough time from the timings logged at the bottom of the graph. I get it to be about 5 or 6 seconds, assuming each step is about two seconds.
I hope that helps, and do feel free to shout up if you need further info - more than happy to help where I can!
Cheers,
Mike.
1 Like
Are you not using the built in energy dash on HA? I’m trying to work out how to add costs for my meter but need to convert it to kWh first from ft3.
Hi,
Yes, I use the HA Energy Dashboard in addition to my own custom, “at a glance” dashboard.
If using the HA Energy Dashboard it will automatically convert from ft3 into m3, but when you add costs you have to calculate the cost per m3 of gas for it to accurately reflect your usage, although here in UK we get charged by the kWh (this is also another reason why I designed my own dashboard).
In order to get kWh and Cost I put some additional yaml ‘sensors’ in my configuration file to calculate these. If you want me to post the yaml for these, let me know.
Cheers,
Mike
Hi Mike,
Yes please, if you wouldn’t mind!
Morning…
I created a number of 'Helper ’ Meters to track various elements of gas usage and cost, so their results could be shown in my custom dashboard… some of these I did after putting the new yaml code into the configuration file.
Note: The one which says just “Gas Meter” tracks the actual meter reading, and is easy to calibrate by pasting the following into the Developer Tools > Services section of HA and then hitting the ‘Call Service’ button.
service: utility_meter.calibrate
target:
entity_id: sensor.gas_meter #Change this to your Gas Meter Reading helper sensor
data:
value: '199870' #Change this to your meter reading
The yaml code for the various other sensors is noted below…
- name: "Daily Gas Consumption kWh"
unique_id: daily_gas_usage_kwh
state: "{{ ((((states('sensor.gas_consumption_daily_v2')|float * 0.0283) * 1.02264) * 39.9) / 3.6)|round(2) }}"
availability: "{{ states('sensor.gas_consumption_daily_v2')|is_number }}"
unit_of_measurement: "kWh"
device_class: energy
state_class: total
- name: "Daily Gas Cost"
unique_id: daily_gas_cost
state: "{{ (((((states('sensor.gas_consumption_daily_v2')|float * 0.0283) * 1.02264) * 39.9) / 3.6) * 0.09835)|round(2) }}"
availability: "{{ states('sensor.gas_consumption_daily_v2')|is_number }}"
unit_of_measurement: "£"
device_class: monetary
state_class: total
- name: "Weekly Gas Consumption kWh"
unique_id: weekly_gas_usage_kwh
state: "{{ ((((states('sensor.gas_consumption_weekly_v2')|float * 0.0283) * 1.02264) * 39.9) / 3.6)|round(2) }}"
availability: "{{ states('sensor.gas_consumption_weekly_v2')|is_number }}"
unit_of_measurement: "kWh"
device_class: energy
state_class: total
- name: "Weekly Gas Cost"
unique_id: weekly_gas_cost
state: "{{ (((((states('sensor.gas_consumption_weekly_v2')|float * 0.0283) * 1.02264) * 39.9) / 3.6) * 0.09835)|round(2) }}"
availability: "{{ states('sensor.gas_consumption_weekly_v2')|is_number }}"
unit_of_measurement: "£"
device_class: monetary
state_class: total
- name: "Monthly Gas Consumption kWh"
unique_id: monthly_gas_usage_kwh
state: "{{ ((((states('sensor.gas_consumption_monthly_v2')|float * 0.0283) * 1.02264) * 39.9) / 3.6)|round(2) }}"
availability: "{{ states('sensor.gas_consumption_monthly_v2')|is_number }}"
unit_of_measurement: "kWh"
device_class: energy
state_class: total
- name: "Monthly Gas Cost"
unique_id: monthly_gas_cost
state: "{{ (((((states('sensor.gas_meter_monthly_v2')|float * 0.0283) * 1.02264) * 39.9) / 3.6) * 0.09835)|round(2) }}"
availability: "{{ states('sensor.gas_meter_monthly_v2')|is_number }}"
unit_of_measurement: "£"
device_class: monetary
state_class: total
Obviously, you will need to change the sensor names to match your existing sensor names, or it won’t work!!
As you can see above the kWh conversion use the ‘standard’ conversion from ft3 to kWh as is printed on UK gas bills… the only items which are liable to change are the calorific value of the gas, the 39.9 figure. This is an average of the calorific values from my last 12 months’ gas bills, so will give a very close approximation to the amount used, but it won’t be to the penny.
Also on the costs… the last number in the ‘state’ line of yaml (0.09835 in my case) is the cost per kWh of gas from your gas Co in pence, and you will need to change it to match your cost per kWh from your recent gas bill… additionally, do bear in mind that this would also need to change when they increase their kWh costs too (very unlikely it will ever reduce - but we’ll not get into that bone of contention eh?)
The other thing I haven’t got around to doing is adding the Daily Standing Rip-Off Charge, and then tax at 5%… it’s an easy amendment to the yaml code to achieve this.
I hope this helps and is useful in creating your own custom dashboard
Cheers,
Mike.
1 Like
That’s great, thank you.
I have followed this, and your other thread, and have built and installed it, but am unsure about the pin connections / GPIO between the TCRT5000 and ESP32. Can you advise please?
Hi,
Apologies for the delay, I’ve been on holiday for a few days!
I’m using GPIO32 on the ESP32 (you will see this noted in the yaml code at the beginning of this thread) this pin uses a built-in ADC on the ESP32 and has the name “Gas Meter Analog Value”. It reports back the voltage that the IR sensor is sending out. This voltage will vary according to what is under the IR LED’s.
There could be either three or four pins on your TCRT5000, there are 4 on mine. They should be positive and negative power feeds to power the IR sensor, both of these are taken from “+3.3V” on the ESP32 and the “Gnd” connection on the ESP32. The other remaining outputs on the TCRT5000 are a digital output and an analogue output and are marked accordingly, AO for analogue output and DO for digital output. Just ignore the digital output as it is of no use to us, and connect the Analogue Output (AO) pin to GPIO32 of the ESP32 - this will feed the varying voltage output from TCRT5000 into the ESP32.
That is pretty much all there is to connect, just three pins +ve, -ve and AO
Just shout if you need any more assistance.
Cheers,
Mike
Hi Folks,
I have used this example and ‘improved’ on it - specifically I have:
- increased ADC sampling to 2ms and averaging to 1 second to achieve a more stable ADC reading (500 samples)
- implemented a stateful sensor for tracking the needle position
- tracking the level of the sensor when the needle is not present by averaging over time to track the figure for the off state.
- Setting a figure of 50% (adjustable) of the peak to peak swing to move to the needle present state
- tracking the level of the sensor when the needle is present, tracking the number up to a maximum and setting a threshold which is must fall below.
- ability to set the meter reading (via home assistant developer tools → actions → sensorname_set_gas_usage, which is stored in the esp in flash and updated every hour (with esp32 flash 100,000 write cycles should last 11 years). This is reloaded on boot, and saved on shutdown so other than being turned off the sensor will continue to track with the meter.
- adjust the needle resolution to 1/100 of a cubic foot
- removed the attenuation (which you may need to put back, depending on your board and settings - just look out for getting more than 1 volt back on the ADC value and then set to 6 or 12 dB as needed
All you need to do is
- enter the various 3x passwords which will be generated if you create an ESPHome Sensor,
- enter your rise value - which was only 0.0025 volts for my setup.
- adjust the 0.03 ‘averager’ figure if your gas meter rotates faster than 30 seconds at the needle off position. the figure needs to be 1/(number seconds without needle) when rotating at maximum speed. You can read this off the graph that the sensor creates in home assistant for the analog value figure.
- note that i found i got a maximum peak-to-peak response off the sensor when placing the black (transmit) IR LED under the needle dial centre and placing the IR receiver (blue color) under where the needle sweeps.
esphome:
name: gasgaugev2
friendly_name: GasGaugeV2
on_boot:
priority: 600
then:
- globals.set:
id: total_pulses
value: !lambda 'return id(total_pulses_flash);'
on_shutdown:
then:
- globals.set:
id: total_pulses_flash
value: !lambda 'return id(total_pulses);'
esp32:
board: pico32
framework:
type: arduino
# Enable logging
logger:
# Enable Home Assistant API
api:
encryption:
key: "INSERTYOURKEYHERE"
services:
- service: set_total_gas_usage
variables:
gas_meter_reading: float
then:
- globals.set:
id: total_pulses
value: !lambda 'return gas_meter_reading;'
ota:
- platform: esphome
password: "INSERTYOURPASSWORDHERE"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Gasgaugev1 Fallback Hotspot"
password: "SETFALLBACKHOTSPOTHERE"
captive_portal:
globals:
- id: total_pulses
type: float
restore_value: false
initial_value: '0.0'
- id: total_pulses_flash
type: float
restore_value: true
initial_value: '0.0'
- id: rise
type: float
restore_value: false
initial_value: '0.0025'
- id: recent_average
type: float
restore_value: false
initial_value: '0.0'
- id: this_peak
type: float
restore_value: false
initial_value: '0.0'
- id: needle_state
type: int
restore_value: false
initial_value: '0'
# This sensor exposes the 'total_pulses' variable to Home Assistant and
# tells HA it is to ft³
sensor:
- platform: template
name: "Gas used"
device_class: gas
unit_of_measurement: "ft³"
state_class: "total_increasing"
icon: "mdi:fire"
accuracy_decimals: 2
update_interval: 10s
lambda: |-
return id(total_pulses);
# This is the reading of the voltage on the analog input pin Take a measurement every 2ms but only report the average
# every 1 second. This is to overcome the noisy ADC on the ESP32, and also to see if the sensor is 'seeing' the rotating needle
- platform: adc
id: adc_value
pin: GPIO32
accuracy_decimals: 4
name: "Gas Meter Sensor Analog Value"
update_interval: 2ms
attenuation: 0dB
filters:
- throttle_average: 1sec
#calculate the running average to work out a noise floor for the zero state
#this is based on a minimum zero state lasting 30 seconds which is the fastest rate the boiler can run between pulses in measurement data
#this means an iterative averager using 97% the previous value and 3% the new value
#this achieves a low value with typical rotations of about 1/6th of the peak value
# we also test if it is zero when starting as that is the initilsation value
# start in state 0 (assumes low state, which we will get to eventually)
# look for a figure of at least half the rise value to move into state 1 (high)
# the rise value is teh peak to peak difference that you need to measure using the voltage graph
# set an initial peak value at the transition point
# once in state 1 look for continuing rising edge and update peak value to track this increase to it's maximum for this high state
# continue to look for at least half the peak to peak value as a fall to transition back to the zero state
# once seen, return to the zero state
on_value:
then:
- lambda: |-
float current_pulse_value = id(adc_value).state;
float averager = 0.03;
float rise_factor = 0.5;
if(id(recent_average) == 0)
{
id(recent_average) = current_pulse_value;
}
id(recent_average) = current_pulse_value*averager + id(recent_average)*(1-averager);
switch (id(needle_state)) {
case 0:
if(current_pulse_value > (id(recent_average) + id(rise)*rise_factor)){
id(needle_state) = 1;
id(total_pulses) += 0.01;
id(this_peak) = current_pulse_value;
}
break;
case 1:
if(current_pulse_value > id(this_peak))
{
id(this_peak) = current_pulse_value;
}
if(current_pulse_value < (id(this_peak) - (id(rise)*rise_factor))){
id(needle_state) = 0;
}
break;
default:
id(needle_state) = 0;
break;
}
# Uptime sensor
- platform: uptime
name: Gas Meter Uptime
# WiFi Signal sensor
- platform: wifi_signal
name: Gas Meter WiFi Signal
update_interval: 60s
# Switch to restart
switch:
- platform: restart
name: gas meter monitor restart
interval:
- interval: 3600s
then:
- lambda: |-
id(total_pulses_flash) = id(total_pulses);
1 Like
Wow! That’s a fair bit of work you’ve done on this simple, but useful little sensor.
I’m glad that it was of some use to you. I’ve been using it since I originally created the thread and it hasn’t missed a beat on the logging of the moving needle. I still need to fit it into a box though, so it looks a bit better, but it is currently languishing in a room we don’t use too much and is a case of “out of sight, out of mind.”
Just out of interest, are you monitoring the same gas meter, or another manufacturer with a moving dial setup?
Cheers,
Mike.
It’s nearly the same meter - it just has a slightly different display for the digits. I found this article looking for a way to measure it, and the idea of using the IR meter was novel and seemed to work so i went for it. I was a bit disappointed that my setup has such a small rise in voltage under the needle so optimised the code to fix this.
PS i 3d printed this case which may be useful for others:
And i used an ESP32 Pico Kit v4.1 (Pico D4) board:
https://www.aliexpress.com/item/1005005710873439.html