Values reported by Glow much higher #33
Comments
|
The piece of logs looks fine, I think there was some hypersensitivity of the sensor at that moment. So that causes a high kWh value in your energy dashboard. Maybe make the sensor less sensitive and/or make sure that the sensor is in a dark room. |
klaasnicolaas
added
the
help-wanted
|
Hey @klaasnicolaas , |
|
Maybe it was a one-time thing after all and is it okay now? |
|
Hey Klaas,
I think there must have been an issue with the code.
I recreated the config using the current yaml on github and reflashed.
It works better now but still not 100% correct.
I'll need to look in to why the usage on the energy dashboard is still
higher then what I see on my energy account, maybe the calculation is still
a bit off
…On Mon, 30 Aug 2021, 02:18 Klaas Schoute, ***@***.***> wrote:
Maybe it was a one-time thing after all and is it okay now?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6SOLXWTTJQN7MS454JB4TT7LL6LANCNFSM5C65JMXQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Looks like I have the same or similar issue. I've added a service to reset the energy total and wrote down my electricity meter data to compare it with the glow. In 12 hours electricity meter reported 12 kWh consumed while the glow reported 48kWh. I'll continue observation to find out is it always 4 times differences or the dependence is nonlinear. My electricity meter blinks at 3200 imp / kWh. @Joeboyc2 , please, let me know if you found a reason of your issue. Thanks. |
|
Hi Yegor,
I'm still having issue with the totals as they are much higher than my
energy account reports and I even tried to change the pulse count to a much
higher value 8000 (where as my meter reports 4000) but still no luck.
I could just be that meter I have is misscalculating as I moved provider a
while ago.
I need to revisit this to be honest as it throws me off when I see ive used
£100+ electricity (in ha dashboard) in an afternoon lol
I should have some time to reassess soon, will get back to you
…On Sun, 24 Oct 2021, 10:09 Yegor Vialov, ***@***.***> wrote:
Looks like I have the same or similar issue. I've added a service to reset
the energy total and wrote down my electricity meter data to compare it
with the glow.
api:
password: ********
services:
- service: reset_total
then:
- pulse_meter.set_total_pulses:
id: electricity_pulse_meter
value: 0
In 12 hours electricity meter reported 12 kWh consumed while the glow
reported 48kWh. I'll continue observation to find out is it always 4 times
differences or the dependence is nonlinear.
My electricity meter blinks at 3200 imp / kWh.
@Joeboyc2 <https://github.com/Joeboyc2> , please, let me know if you
found a reason of your issue. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6SOLVQN7XJVROM5CPJZVLUIPELPANCNFSM5C65JMXQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Hi, One other thing - I was getting values of around 150000W earlier (now i filtered out everything > 100000 with a lambda), depending on the position of the LED it would vary between 140000-150000... might be related but not sure how to diagnose it, suggestions are welcome :) |
|
Hi @sillymoi . That's called noise. Those photodiode boards are very noisy when switching their state. This electromagnetic noise is counted as pulses and you are getting the wrong measurements. The only way to ditch it is to not accept any pulses after one was detected. Try to uncomment this line: I'm done with this type of electricity consumption monitoring as my meter can blink too fast to filter out any noise. |
|
Hi @estevez-dev - of course, should've thought it through.. I cut off the high frequency noise with the My meter pulses a bit slower, hopefully the 100ms filter will help. |
This code fragment is great, @estevez-dev. May I ask you how I will be able to set the "Total Energy" to a value I enter in the web page? I would like the counter to reflect the value being displayed at the electricity meter. |
|
That is currently not possible, you can only reset the value. Also, the service name in the default yaml file has been changed. I wonder how useful it is to enter the value of your electricity meter, it's a nice idea, but at the moment that value will always reset when you update the firmware or interrupt the power. That would have to be solved first if you really want to benefit from it 🤔 |
|
Resetting the value after rebooting / firmware update to the value it had before is more in sync with the understanding of a meter as a monotonically increasing value. Therefore I think it might be a good idea to reset the counter. |
|
I also have an issue with energy spikes (nearly 1.000.000W 😂) i have uncommented internal_filter: 100ms and I will see if that helps. When it comes to applying total meter reading to total energy value, you can either update that adding meter reading to the total value lambda, when you flash the ESP (see below), but you have to be quick with that. (1 on the photo). Or create text input field in home assistant and input energy total energy value from energy monitor, then simply add this value to total energy value from ESP (2 on the photo). Its a work around, but seems to work. |
|
I still face a similar issue. The readings seem to be going crazy even if the sensor itself isn't showing much activity. The LED doesn't blink almost at all, is there a way to filter out noise? |
|
Sounds like the photodiode is set too sensitive 😉 |
|
It's strange I've lowered it as much as it goes, the LED doesn't blink at all and yet readings are off the charts. |
|
@niemtec |
|
@cholek3 I have tried this with two photodiodes and had the same results. I checked them against the photo in README and appears to be soldered on correctly. It doesn't seem to react to the energy meters blinks at all and yet measurements are off the charts. I'm getting daily readings of about 255.273 kWh which sounds completely wrong. ---
# Home Assistant Glow
#
# Read your electricity meter by means of the pulse LED on your
# meter, useful if you do not have a serial port (P1).
#
substitutions:
device_name: home-assistant-glow
friendly_name: House
project_version: "3.1.0"
device_description: "Measure your energy consumption with the pulse LED on your smart meter"
pulse_pin: GPIO12
status_led: GPIO5
# imp/kWh rate ⬇ #
pulse_rate: '1000'
# Webserver credentials ⬇ #
web_username: 'glow'
web_password: 'esphome'
dashboard_import:
package_import_url: github://klaasnicolaas/home-assistant-glow/home_assistant_glow.yaml
esphome:
name: '${device_name}'
comment: '${device_description}'
project:
name: "klaasnicolaas.home-assistant-glow"
version: "${project_version}"
compile_process_limit: 1
# Choose the right Platform
# esp32: https://esphome.io/components/esp32.html
# esp8266: https://esphome.io/components/esp8266.html
esp32:
board: esp32dev
# WiFi credentials #
wifi:
ssid: 'name' # Enter your WiFi SSID here. Example: `ssid: 'your_network_name'`
password: 'blablablabla' # Enter your wifi password here. Example: `password: 'abcde123456'`
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: '${device_name}'
captive_portal:
# Enable logging
logger:
# Enable improv over serial
improv_serial:
# Enable Home Assistant API
api:
services:
- service: reset_total_energy
then:
- button.press:
id: button_reset_total
ota:
safe_mode: false
reboot_timeout: 5min
num_attempts: 5
web_server:
port: 80
auth:
username: '${web_username}'
password: '${web_password}'
output:
# - platform: gpio
# pin: GPIO5
# id: output_blue
- platform: gpio
pin: GPIO2
id: output_red
- platform: gpio
pin: GPIO4
id: output_green
light:
- platform: binary
internal: true
id: led_red
name: Red
output: output_red
# Status LED for connection
status_led:
pin:
# Blue LED
number: ${status_led}
button:
- platform: restart
name: "Restart - Glow"
- platform: template
name: "Reset - Total Energy"
id: button_reset_total
on_press:
- pulse_meter.set_total_pulses:
id: sensor_energy_pulse_meter
value: 0
# Sensors for ESP version and WIFI information
text_sensor:
# Installed version
- platform: template
name: "Glow - Installed version"
id: glow_version
icon: "mdi:label-outline"
entity_category: diagnostic
lambda: |-
return {"${project_version}"};
update_interval: 6h
- platform: version
hide_timestamp: true
name: '${friendly_name} - ESPHome Version'
- platform: wifi_info
ip_address:
name: '${friendly_name} - IP Address'
icon: mdi:wifi
ssid:
name: '${friendly_name} - Connected SSID'
icon: mdi:wifi-strength-2
sensor:
# WiFi signal
- platform: wifi_signal
name: "${friendly_name} - WiFi Signal"
update_interval: 120s
# Pulse meter
- platform: pulse_meter
name: '${friendly_name} - Power Consumption in kW'
id: sensor_energy_pulse_meter
unit_of_measurement: 'kW'
state_class: measurement
device_class: power
icon: mdi:flash-outline
accuracy_decimals: 0
pin: ${pulse_pin}
internal_filter: 100ms
internal_filter_mode: 'PULSE'
on_value:
then:
- light.turn_on:
id: led_red
- delay: 0.5s
- light.turn_off:
id: led_red
filters:
# multiply value = (60 / imp value) * 1000
# - multiply: 60
- lambda: return x * (60.0 / ${pulse_rate});
total:
name: '${friendly_name} - Total Energy'
id: sensor_total_energy
unit_of_measurement: 'kWh'
icon: mdi:circle-slice-3
state_class: total_increasing
device_class: energy
accuracy_decimals: 2
filters:
# multiply value = 1 / imp value
# - multiply: 0.001
- lambda: return x * (1.0 / ${pulse_rate});
# Total day useage
- platform: total_daily_energy
name: '${friendly_name} - Daily Energy'
id: sensor_total_daily_energy
power_id: sensor_energy_pulse_meter
unit_of_measurement: 'kWh'
icon: mdi:circle-slice-3
state_class: total_increasing
device_class: energy
accuracy_decimals: 2
filters:
# Multiplication factor from W to kW is 0.001
- multiply: 0.001
# Enable time component to reset energy at midnight
# https://esphome.io/components/time.html#home-assistant-time-source
time:
- platform: homeassistant
id: homeassistant_time |
|
I have project_version: "4.0.0" and I keep getting |
Change to GPIO26 and see if that fixes the issue https://github.com/klaasnicolaas/home-assistant-glow/issues/300 |
|
Same issue here. anyone had any luck? |
|
I'm having this issue too...
The 'W' power consumption value seems correct. |
There are no instructions yet, but it could certainly be added to the website. This also applies to the use of the ./Klaas |
|
Where after installing and setting up ESPHOME GLOW can I fing config yamls? My ESP Home dashboard doesn't see my GLOW instance, HA sees it, but I have crazy Power values, and want to enable internal filter, so again, where can I find config to change the internal filter. It could be enabled on the Glow web server. I'm using ver. 4.1.1 |
|
@Footz355 You can change the YAML config after adopting in ESPHome Dashboard. If it's not shown there you could try removing the glow from Home Assistant, then reboot to see if both HA and ESPHome see the device. Have you already tried adjusting the sensitivity of the sensor using the small potentiometer? Related doc: https://glow-energy.io/docs/advanced/firmware_customization ./Klaas |
|
Greetings Klass. No, I have not played with the potentiometer because I am currently using Glow 3.0.0 and it is working fine with internal filter set to 200. I just got lost in new config style with separate sub configs. Probably will have to download it, edit in internal_filter, copy/paste it to a single yaml and deploy in my ESPHome, at least that seems the easiest way for me. Or I will just stay with 3.0.0 until some ESPHome update will brake it. My I recommend adding internal_filter setting to web_server? It seems judging by my experience and browsing in forums that this feature is more often used then changing pulse rate settings from the glow web_server. Thank you very much for this project. |
Hi All,
I've recently setup the glow on my electricity meter and all seemed to be working well.
However, I have noticed that the power consumption readings are going up much quicker than I would expect.
My meter runs at a rate of 4000 blinks per kWh, and i have adjusted my config to that, but when looking in the logs i can see it is tracking each of these blinks and pushing the number up pretty quickly, rather then small increments.
Here is some output from my logs:
so when looking at my energy usage via the energy dashboard it reports really high usage over each half hour, where as my energy company dashboard shows a much lower readings (when looking at yesterday)
I will need to wait until tomorrow to get the true usage data from my energy provider for todays usage but i will update this ticket then, to give a good example.
I think the issue here must be due to the pulses but im not 100% sure how the calculation is being done
The text was updated successfully, but these errors were encountered: