No reading
dean-ElisGroup opened this issue · comments
Anyone experienced no reading since the ESPHome updates recently?
My Glow does not read anything now and shows just a ZERO for usage. i've tried resetting etc but nothing is working.
Which version are you using and is your sensor still on the correct GPIO pin?
Yes, all hardware hasn't been altered in anyway.
Version: 2023.9.3
Glow Version: 4.0.0
I too have noticed recently, that once in a while its stopping metering. Was thinking it had something to do with my wifi network.
I updated the position of a wifi repeater that is now used by the ESP and had to recalibrate the sensor.
Not sure but maybe it has to do with some kind of change in the amount of power going through the module?
This might relate to the ESPHome updates causing some optimisations to mess with the power levels and thus causing the sensor to become less reliable.
I updated the position of a wifi repeater that is now used by the ESP and had to recalibrate the sensor.
Not sure but maybe it has to do with some kind of change in the amount of power going through the module?
This might relate to the ESPHome updates causing some optimisations to mess with the power levels and thus causing the sensor to become less reliable.
I've changed nothing, other than the software update. How do you recalibrate the sensor?
I updated the position of a wifi repeater that is now used by the ESP and had to recalibrate the sensor.
Not sure but maybe it has to do with some kind of change in the amount of power going through the module?
This might relate to the ESPHome updates causing some optimisations to mess with the power levels and thus causing the sensor to become less reliable.I've changed nothing, other than the software update. How do you recalibrate the sensor?
The sensor has a blue potentiometer that, when turned, changes the sensitivity of the sensor.
I get sporadic readings now, a few minutes ago it was over 11,000,000W, not sure that's correct!
Yes, if you look at the log then this happens because the sensitivity is such that it reports the same red flash as multiple flashes.
There are two ways to correct this:
- Turn the potentiometer so that it only provides one input per red flash
- Use the internal filter inside YAML by uncommenting it.
#internal_filter: 100ms
The internal filter will only register input once every 100ms and will eliminate the wrong reading.
Hi guys. In ESPHome 2023.8.0, there was a pulse_meter refactoring. The default mode is now EDGE instead of PULSE as before.
To use the PULSE mode, you need to add the internal_filter_mode option to the pulse_meter configuration, like this:
- platform: pulse_meter
name: '${friendly_name} - Power Consumption'
id: sensor_energy_pulse_meter
internal_filter_mode: PULSE
unit_of_measurement: 'W'
state_class: measurement
...
I use the EDGE mode with an internal_filter of 100ms, with a pulse rate of 1000 and have not noticed any difference 🤔
Do you have any strange values?
Nope, it is always spot on with measuring
hm, In EDGE mode, an internal_filter of 100ms and a pulse rate of 10000 i have right values too 🤔I didn't use the internal_filter before
Mine is still dead. Reports a 0w all day every day. I've tried to fix it but with no luck
A pulse rate of 10000 is actually too high to make correct measurements. But if I understand correctly, you get good measurements when you set the interval_filter_mode to PULSE?
Yes, but it's better with EDGE mode, an internal_filter of 100ms
Show the difference:
Pulse rate of 10000, EDGE mode, an internal_filter of 100ms:
Pulse rate of 10000, PULSE mode, an internal_filter is disabled
Perhaps it would be better to set the internal_filter with 100ms default and not the mode back to PULSE as in your PR.
I did close it
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!