Anyone else having issues with the upgrade to ESPhome 2023.8.1? #301
Comments
|
Installation went OK and device started OK. But now i get weird results: [09:35:52][D][light:047]: State: ON |
Exactly the same thing happened at my end. I think the update broke the current configuration... |
That doesn't work correctly. If you have low consumption seems that it works but if I raise consumption eg. 4 kWh, the meter shows only ~half of that. |
|
I have exact same problem. |
|
I also updated my Glow to the latest version, but it works fine for me 🤷🏻♂️ |
|
@sillami1 What I see in your log is that it actually measures 1 pulse as 2 pulses because you see 2 times a watt log with the same timestamp 🤔 |
|
@klaasnicolaas Think the timestamp is not same, but fits inside same second. Here's other example... [14:31:31][D][sensor:094]: 'House - Power Consumption': Sending state 309.58020 W with 0 decimals of accuracy I'm not sure but seems it sends pulse of both, rising edge and falling edge. If so, the pulse of falling edge is incorrect. |
|
Here is my log... [14:59:34] [D] [sensor: 094]: 'House - Power Consumption': Sending state 3559.57739 W with 0 decimals of accuracy |
Tried with dishwasher and kettle on. The power went up to 4.5kw. Looks quite accurate. Maybe our setup is different. |
|
In my case it seemed that min value show right value. |
|
Seems that there's a few issues going on with the upgrade. The one that I had that I logged this issue for was [web_server:116]: Setting up web server... abort() was called at PC 0x4020ce8b on core 0 Backtrace:0x40083985:0x3ffd80500x40093ec5:0x3ffd8070 0x40099489:0x3ffd8090 0x4020ce8b:0x3ffd8110 0x4020ced2:0x3ffd8130 0x4020cfcb:0x3ffd8150 0x4020cf2a:0x3ffd8170 0x400dcc89:0x3ffd8190 0x4012e555:0x3ffd81b0 0x401576d9:0x3ffd81d0 0x40159533:0x3ffd81f0 |
|
Please add a full configuration file you are using with the secrets redacted and which board you are using. |
This look's like fix my problem also. |
|
@JuMaPa What's your IMP value? |
Not sure what u mean, but 1000imp/kwh |
|
And just check power consumption history graph...it's not right even now. |
|
Yes, just that what I meant. I have 10000 so I have 10 times more pulses. And that's why the mentioned solution don't work for me. There are also reported this issue in ESPhome GitHub esphome/issues#4807 |
|
@sillami1 10.000 pulses is actually too much to use the pulse_meter component properly, which may also explain why your measurements are not going well. @ABredhauer Have you already been able to solve your problem? Given your issue is bit hijacked by others 😄 |
|
I've just updated to 2018.8.1 today and have been facing the same issues. Multiple reportings at the same time and creating values well over 200,000,000 at some points. Changing the internal filter to 100ms did work in getting the values to be more realistic and removed the jumpy results from the multiple pulses at the same time. I'm not sure however why the sensitivity of the sensor took a leap after the update. |
|
@klaasnicolaas thanks for following up. I have not made any progress but I've also come down with the flu so haven't done much of anything It seems to always die after MQTT so I'm wondering if thats the issue For now I rolled back my ESPHome to the previous release and reflashed the firmware. |
|
Your pastebins are private, the glow does not use MQTT so I find that strange |
|
Sorry should be fixed now |
|
Would start by disabling the MQTT (why are you using that?) and the BLE proxy, see if that makes a difference. Did you upload that firmware via a cable before using bluetooth proxy? Because the first time that would not work via OTA. |
|
Actually I’m not using the mqtt anymore. It was a workaround when I was having connectivity issues with my wifi and for some reason the connection was much more stable with mqtt enabled. I’ll disable and check it in the morning. And yes the proxy upgrade was done via cable initially. It’s been stable for months with no issues until this update |
|
I am having this same issue as well. Has been working fine for a year. Changing the internal filter to 100ms did work for me too. I am using esp32-C3 and using ble proxy |
|
@klaasnicolaas I removed the MQTT setting from my config and reflashed while staying on 2023.7 and my glow and connection were stable for an hour so I bit the bullet and upgraded ESPHome to 2023.8.2 and reflashed with updated config. It still seems to be stable after 4 hours so I guess it was the MQTT after all. Thanks for your help |
|
Any advice, what to do? I haven't do any change's before that update and it works like charm. And now it just shows that 117,600w consumption all the time. At same second show also that right value....or that's what i think it's happening |
|
@JuMaPa Are you seeing multiple inputs when the red light flashes? In this case uncommenting Very high readings usually pop up for me when the sensitivity of the sensor changes for some reason. I then usually manually calibrate the sensor. This is the first time i´ve used the filter and it seems to be a good combination to get the readings clear. |
That's my log when my problem occured. I try to change after that above log 200ms, it is closer. But history log looks like pillar graph after that. Hope undersstand what i try to explain. |
|
@JuMaPa Yeah you have to use the blue potentiometer on the sensor so that you get as few readings when the red light flashes as possible. Then the filter should work on fine tuning the results. Just to clarify further. Step 2: Fine tune with the filter if the manual calibration is not sensitive enough and you have 2-3 readings per red flash. Hope this made sense. |
|
Uuuh, yes. That's look's like fix my problem. Just little adjustment and problem solved👍 Thanks for help for all you folks. I just need to check after few days what that data looks like and compare to my electricity seller log. |
|
same issue updated today to 2023.8.2, too high readings, been 100% stable for years, something changed |
|
So the issue I had with the upgrade was different and I didnt see the strange readings that others are seeing but I did have a similar issue much earlier in my journey and solved it with some of the info in this issue #57 Wondering if thats why I'm not seeing this issue now |
For clarity then if you have your issue solved then please mark the topic as anwsered and we can continue in #302 since the nature of the issues are actually different and you topic has been hijacked for a new cause. Thanks! |
|
Sounds good to me |
|
like i just said it have to do with the update, behaviour changed right
after, sensor is where it should be, i have upgraded every update without
ANY problems
Den man. 28. aug. 2023 kl. 03.43 skrev Mikk von Berg <
***@***.***>:
… same issue updated today to 2023.8.2, too high readings, been 100% stable
for years, something changed
Did you try recalibrating the sensor?
—
Reply to this email directly, view it on GitHub
<#301 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHDAOWQLMPHEEUHGKBMKHB3XXPZVBANCNFSM6AAAAAA3VBQKXA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I installed the update and reflashed my glow but then it dropped off my network. Connected via USB and saw that it continually rebooted and died. For the moment I've rolled back to ESPHome 2023.7.1 and reflashed to get it working again
The text was updated successfully, but these errors were encountered: