LED constantly on since updating

[klaasnicolaas]

LED constantly on since updating

[Userofhomeassistant]

Hi Everyone,

The above-mentioned problem of my ghost readings has been solved (almost). As suggested in another post, the ghost readings might due to “noise” and the use of a 100 nF capacitor in the hardware setup was suggested......

When I applied a 10 uF capacitor / 25V, the hardware started to work fine, apart from two misreadings overnight. Maybe, I need a capacitor with a slightly higher capacitance, or somebody has another suggestion.

For those who encounter the same problem, I installed the capacitor between the 3V3 and GND pin of the photodiode. Note that the negative side of the capacitor should be connected to the GND pin.

[Userofhomeassistant]

I have also most of the time continuously a red led without flash, but sometimes, it is correctly flashing. It looks to happen rather ad random. As RamblingGeekUK, I have also noticed that there are 4 cables visible in the picture. The AO is likely the analog output and DO is the digital one. The use of both outputs looks not logical, isn't it? Maybe Klaasnicolaas can explain the use of the fourth cable, if any.....

[Userofhomeassistant]

In general, I use the newest versions. I have played around with the flash time, changed it to 150ms. Presently, the LED works fine. However, I did not test it extensively, so no guarantee. Indeed, a little later, it was again continuously lighting. After uploading the same program without any changes, the LED worked again fine, including blue flashing during uploading. The present conclusion is that is destabilizes after a while. But why?

Another (additional?) reason for a continuous light might be that I have sometimes a misreading, a value far too high. This seems to be related to the sensitivity of the photodiode. If I make it a little less sensible, it does not pick up de flash of the E-meter. If I make it a bit too sensitive, it gives a continuous signal, which you can see from the green LED on the photodiode. Finding the correct sensitivity is not easy. In between, the LED on the photodiode may start to flash very rapidly while there is no flash from the E-meter. There seems to be a solution for misreadings related to electronic noise by placing a 100nF capacitor, as written in at another (closed) issue about instability of the reading. However, I have no clue where to add it. Unfortunately, that issue has been closed, but the applied solution with the capacitor has not been documented, the electronic scheme is missing......

[Sysoev86]

A similar problem. The red LED is always on

[Mincka]

It happens when there are two quick flashes (but it could be imperceptible noise, or require tweaking of internal_filter). The duration of the flash is higher than the duration between the two flashes. The LED should go back to it "previous state" but the previous state is still "on", that's why the LED stays permanently "on".

Either it could be improved by using turn_on / turn_off with a short delay, or use a reset loop to force turn_off the LED every few seconds. It would not change the sensor results since this LED is just there for control.

[aptonline]

Thanks @Mincka , this sounds like a solution. @klaasnicolaas can this be implemented? My esphome yaml skills aren’t the best 🤣.

Edit: actually would this work?

on_value:
      then:
        - light.turn_on:
            id: led_red
            flash_length: 400ms
        - delay: 1s
        - light.turn_off:
            id: led_red

Edit: the above does work but doesn’t feel as elegant as it should do. I could potentially remove the flash_length and reduce the delay.

Edit: this seems better.

on_value:
      then:
        - light.turn_on:
            id: led_red
        - delay: 0.5s
        - light.turn_off:
            id: led_red

[klaasnicolaas]

That's right, everything works fine for me with version 1.2 and ESPHome 2021.8 🤔 I'll create a PR to fix a few things.

[klaasnicolaas]

@RamblingGeekUK Could you create a separate issue for this? To prevent situations from getting mixed up in an issue 😉

[klaasnicolaas]

That way of entering the imp/kWh rate has changed in version glow yaml version 1.2.

[aptonline]

Yes I know, I’m using the default 1000 as this is what’s displayed on my meter.

  # imp/kWh rate ⬇ #
  pulse_rate: '1000'

[aptonline]

Is this something to do with the pulse_pin changing from a number to the actual GPIO pin?

[RamblingGeekUK]

Mine does seem to flash at all...

I'm also confused by this

It says A0 isn't connected or not using on the ESP32, in the image it looks connected as four cables in use, but to what ?

[aptonline]

@Userofhomeassistant did you upgrade from the earlier version of the glow yaml (1.0)? It all worked fine for me (flashed on the pulse reading) but since updating to 1.2 it's constantly on. I've set the pulse to 1000 as per my meter (photo above).

[aptonline]

BTW I followed the guide as opposed to referring to the photo and I only used the 3 pins that were referenced.

[Userofhomeassistant]

Answer to Aptonline, I use the newest version, i.e. 1.2.0.

[aptonline]

Answer to Aptonline, I use the newest version, i.e. 1.2.0.

But did you use the version prior to that? For me the led flashed correctly with the version prior. Also out of interest what version of esphome are you using? I’m trying to determine if this new behaviour is a change in the yaml for glow or a change that was introduced in the latest esphome.

[RamblingGeekUK]

appears to be working, intermittently, it has started reading, after I confirm the sensor was working after holding my phones led to it. I'm not getting anything plotting on the Energy chart. I'm using the 3 cables and I agree the AO if for analogue and shouldn't be needed. 

[aptonline]

@RamblingGeekUK i’m assuming you are waiting a while to check the energy dashboard in HA? It does take a while to get the data in.

[RamblingGeekUK]

It's been 11 hours... the animation was animating but that has now stopped... not sure.. was going to leave it alone today as I only installed yesterday and see what happens if anything tomorrow.

[aptonline]

That seems a long time. Hopefully @klaasnicolaas will be able to assist. Maybe worth posting another issues so my LED issue doesn’t get lost 😉.

[aptonline]

@Userofhomeassistant I attempted to change the dial on the photodiode yesterday but didn’t see any changes (to the led at least). I’ll attempt to do it again today (it is a Sunday after all) and reboot the glow at each stage. As an observation the LED seems to be staying on after the first pulse is received for me, it’s almost like the led is not being reset correctly after it’s turned on or the delay is not being read correctly and therefore constant.

[aptonline]

Adjusted photodiode sensitivity and issue still remains. There is a small led on the photodiode itself which you can use to calibrate it, too high and the led is on too low and it doesn’t fire. Adjusting this doesn’t seem to alter the LED connected to glow however.

[klaasnicolaas]

@RamblingGeekUK A0 is not used, the photo shows it because this is from a test set-up. But you can just omit the 4th cable 😉

[klaasnicolaas]

My Glow uses the 1.2 version and runs on ESPHome 2021.8, but I am not experiencing any problems in the measurements at the moment. As for the LED, that I'm not visually checking right now, so I'll get to that later.

@aptonline I find it strange that this has arisen after updating, what if you use an old version of the YAML config again?

[aptonline]

@klaasnicolaas ok I’ve just rolled back to v1 of the yaml and it initially started working as expected (the led flashed) then after a few mins the LED stayed on like before, this seems to be different from when I use v 1.2 as it stays on after the first pulse.

I’m starting to think it’s a change in EPShome but looking at the change log I can’t see anything that would impact it.

[Userofhomeassistant]

Thanks Mincka,

Your suggestion works fine for me. The LED is functioning now flawless.

[klaasnicolaas]

I think it's fine to modify the code that calls the led flash, I tested it at home and it makes no difference for me.

[aptonline]

@klaasnicolaas so on your setup on the flash interval is working as expected?

[RamblingGeekUK]

I just can't get mine to get consistent readings

I think I may solder the cables, just to be sure. 🤔

[aptonline]

I amended the code as per my post here: #28 (comment) but I believe @klaasnicolaas is going to update the main code via a PR in the future to hopefully improve this for all.