-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESPHome 2024.5.0 + D1 Mini + LD2410 = The connection dropped immediately after encrypted hello #5790
Comments
disable encryption. This work with esphome 2024.5.0 |
@vasyna I don't see any changes related to encryption in esphome 2024.5.0. |
I can’t say, but the problem is only on devices paired with ESP8266 + LD |
Exact same fault here. I have multiple PIR sensors still functioning as intended, but every LD2410 on my network is failing with the same error. Also, seem to be unable to re-flash any of them. |
Disabling encryption doesn't help much.
It seems also that ESP itself crashes every few seconds:
|
yes, I had to go and reflash it one by one with the cable to the previous fw. |
Does everything seem to work as intended after the reflash? Did you have to make any other adjustments? Sorry for the questions, I'm just getting more and more frustrated with it 😂 |
@CEZ15 I did a rollback to ESPHome 2024.4.2 addon from HA backup and installed the firmware on top of the newer one. |
ESP8266 + LD2410 : same issue, router shows ip up and running, as I disabled webui for the performance issues, I cannot access via Web server to confirm. I will wait a fix and will not revert esphome version. |
I don't think it is specific to the LD2410, as others are seeing it without this, but still D1 Minis |
I had the same log messages and an unresponsive device after upgrading to 2024.5.0 on an m5Stack Atom Lite ESP32. To troubleshoot I used https://web.esphome.io/ to view the log. This revealed repeated reboots due to #esp32_improv:
# authorizer: none |
I had similar behavior with LD1125H and ESP32. No encryption used. |
Same issue with different board:
|
Maybe but same board with cc1101 works fine and did not brake after update. |
maybe interesting. This is not the first time that a new update brick the connection/wifi etc. In 2023 I revert 2 or 3 times back to the version I used before the update. (To bad I don't remember the versions anymore) |
Same problem here with Wemos D1 Mini. |
Not sure how to revert the devices since I can't even connect to them. It just keep saying connecting when I try to flash the older version. Grounding d3 doesn't get them into flash mode. Seems I may have to unsolder all connections. What a royal PITA. |
I found desoldering the RX / TX pins would then allow them to be flashed. Not sure why these pins being connected to sensors stop the device from allowing flashing, but at least you don't need to desolder the entire board |
The ESP8266 only have one UART with TX and RX and it is use for flashing. If you have any device attached on those pins it will prevent the flashing. It is also good practice to add on the Logger: section the command baud_rate: 0. This command disable the log mensagens on the serial port. |
I just tried that and nothing, then I also unsoldered the 5v, still nothing... |
Yes logger was already at 0. |
Do you use GPIO0, GPIO2, GPIO12 and GPIO15 pins? Those pins could have influence on flashing processe. |
Don't feel alone here i have the same issue on only the LD2410 sensors connected to an esp8266 just about identical to yours, restored to a version before re flashed them and they working again |
will wait for a new version to see if that fixes it |
Not only with LD sensors. I seeing same behavior with bme680 and not with the board using the LD |
Just come to say I'm experiencing the exact same issue but with a Wemos D1 mini and LD2410c
Logger baud rate set to 0:
|
Yes also broke my D1 Mini presence sensors no idea how to revert back to an older version of esp home :( |
Neither do I, but at least I was just testing |
Thanks @vazquezjm |
I have the same thing with Sonoff 4ch ESPHome 2024.5.2
but sometimes it will connect |
Idea ... Something in 2024.5.0 was introduced that corrupted memory maintenance or similar? Or bloated some component? I was able to "capture out of memory" errors, on device with yaml compiled with 2024.5.2. Example is one at my greenhouse. Device is working ok, with really simple yaml, compiled at 2024.5.0. But I am not able to do OTA via website. Rebooting is not helping. I will downgrade this to 2024.4.2 just directly.
|
Same issue for me with a Localbytes Tasmota uk plug flashed OTA with ESPHOME. ``Working fine until latest ESPHOME version, Message: WARNING localbytes-plug-11 @ 192.168.0.80: Connection error occurred: localbytes-plug-11 @ 192.168.0.80: The connection dropped immediately after encrypted hello; Try enabling encryption on the device or turning off encryption on the client (ESPHome Logs 2024.5.2).
|
still the same problem in 5.3. Here is a video how to back up the firmware before upgrading the v5 or if you already upgraded, how to get back any version of esphome. You can even have the oficial updated and use a legacy for the devices that fail. |
Hi, |
That sounds good. Will wait for others who have positive news about the 5.4 version. Then I will try it here also. |
same here. seems to work again wirg 2024.5.4 - weird |
It seams issue has been fixed. 5.4 |
Fixed also on my end. |
Just a side note for this issue...... I have a few ESP01's in places I can not remove and just flash when I feel like it (One example is the front gate). As for the 2024.5.4, I eventually managed to get it to take the flash (after hours of pushing the flash over OTA), however, it still had the same issues where it would drop off from time to time, was not taking the firmware as it always used to, and just seemed to be completely unreliable and unstable (I am referring to the EPS01's, I can not recall if the ESP8266's were behaving or not after the 2024.5.4, as by this point I had completely Lost My S#!t). I did however notice that the 4 nodes that were most problematic, were the nodes that contained INA219 modules in them (2 x ESP01's and a further 2 x ESP8266 D1 Mini's, both with 2 x INA219 Modules connected to them) Thankfully I managed to revert back to a previous version (2024.3) as described elsewhere in this thread, and after Many hours of pushing the firmware to the ESP01 node, it eventually took, and is now back to its previously "Well Behaved" disposition. I could obviously not remove the gate node as it is one that has been soldered in place due to space constraints, and therefore could only be updated via OTA. (And no, my laptop with win7 on it bombed out recently, so that was not an option with the ftd adapter either). On a side note, I did notice that all nodes bin files seemed around 30% larger (Even with no additional code, and with just the bare minimum of code it was 517KB+/-) which seemed a bit odd. I can not recall the exact size, however, the one nodes bin file I have on backup with just the bare minimum is 455KB, so I landed up removing virtually everything from the gates code to give it every possible chance of success. I can only surmise this issue is not resolved as I was still having issues with all the ESP01 nodes that had INA219 modules connected to them, after the supposed fix was released. In conclusion, with all the frustration that has led me up to this thread, I will not be updating ESPHome again soon, as this is now the second time I have had my fingers burnt to a crisp, and I do not enjoy the bitter taste it leaves in my mouth weeks after the ordeal has passed! |
Esphome 5.4 didn't resolve anything. Same error, encryption yada yada..
Esp8266 with LD1410.
Time to stop paying for nabu casa, it's been too long and no reply from
devs.
…On Tue, 28 May 2024, 19:35 Gadget43, ***@***.***> wrote:
Just a side note for this issue......
I have a few ESP01's in places I can not remove and just flash when I feel
like it (One example is the front gate).
As for the 2024.5, I eventually managed to get it to take the flash (after
hours of pushing the flash over OTA), however, it still had the same issues
where it would drop off from time to time, was not taking the firmware as
it always used to, and just seemed to be completely unreliable and unstable
(I am referring to the he EPS01's, I can not recall if the ESP8266's were
behaving or not after the 2024.5, as by this point I had completely Lost My
S#!t).
I did however notice that the 4 nodes that were most problematic, were the
nodes that contained INA219 modules in them (2 x ESP01's and a further 2 x
ESP8266 D1 Mini's, both with 2 x INA219 Modules connected to them)
Thankfully I managed to revert back to a previous version (2024.3) as
described elsewhere in this thread, and after Many hours of pushing the
firmware to the ESP01 node, it eventually took, and is now back to its
previously "Well Behaved" disposition.
I could obviously not remove the gate node as it is one that has been
soldered in place due to space constraints, and therefore could only be
updated via OTA. (And no, my laptop with win7 on it bombed out recently, so
that was not an option with the ftd adapter either.
On a side note, I did notice that all nodes bin files seemed around 30%
larger (Even with no additional code, and with just the bare minimum of
code it was 517KB+/-) which seemed a bit odd. I can not recall the exact
size, however, the one nodes bin file I have on backup with just the bare
minimum is 455KB, so I landed up removing virtually everything from the
gates code to give it every possible chance of success.
I can only surmise this issue is not resolved as I was still having issues
with all the ESP01 nodes that had INA219 modules connected to them, after
the supposed fix was released.
In conclusion, with all the frustration that has led me up to this thread,
I will not be updating ESPHome again soon, as this is now the second time I
have had my fingers burnt to a crisp, and I do not enjoy the bitter taste
it leaves in my mouth weeks after the ordeal has passed!
—
Reply to this email directly, view it on GitHub
<#5790 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMNLFK2ICDLZOZUAHC2WAZ3ZETE7DAVCNFSM6AAAAABHXYYO4GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZVHA4DEMRWGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Confirmed working for my three d1 minis. Thanks for the fix to all involved. I guess smart alec ain't so smart after all, lol. EDIT: I've disabled encryption, which may be why it's working for me. |
All is working for me again with the newest update, but my BME680 still says IAQ accuracy is uncertain (this didn’t happen under 2024.4.2). We forge on! |
I feel hashing out 95% of your code just to get the node to operate "Sort of" again is kind of counter productive, don't you think? I actually did remove nearly All the code from the one node before it took on OTA, but in my opinion, removing code that actually served a purpose before this update, just means someone screwed something up. Eventually, bloat will take over and you will be told that you can't use ESP01's and D1 Mini's, because they don't meet the minimum requirements of Esphome, what then? I suppose if you earn thousands a month, and can afford to throw out all the 1MB devices, good for you, but all I do with an ESP01 is send battery voltages from my gate, so I don't need a million io pins, or updates every 5 seconds, but I guess that's just my use case scenario 🤷🏼♂️ The only thing I am currently trying to wrap my head around is how this issue has been marked as "Closed" or "Resolved" |
Thanks for the side splitting laugh, I enjoyed that after what I was put through! I really do have to admit, that as funny as that was, myself, not being a coder/programmer, would not want to be the person responsible for having to repair all these errors. I take a look at some of the code and code fixes on GitHub and my mind boggles at the shear "mass of knowledge" of some of these guys/gals keeping HA afloat, and I very quickly, re-appreciated how much work has gone in to it, and my frustrations and anger subside... Slightly! It IS extremely annoying landing up with non working nodes after an update, however, lesson learned, and I will be doing the updates after I have done my due diligence, and not just "Assuming All Is Good". As the saying goes, fool me once, shame on you, fool me twice, shame on Me! |
It would be a lot better if more people tested the beta. The developers can't test on the huge variety of hardware people have. Also, you should first test on something serial flashable if possible. |
As much as I like running beta software, doing it with ESPHome on a house scale isn't really feasible. Also, out of the 50+ devices I have on ESPHome, only a single one of them had this issue so it'll be hard to find on a small scale install (disabling encryption didn't fix it for me, I just ended up reverting to the latest 2024.4 release). |
I certainly don't mean to run beta on everything, but a couple of tests of some representative hardware would be helpful. |
Well, I also have 25 productive nodes and one had the problem. |
The one I had issues with only had an IR transmitter with a few template switches/buttons to transmit IR codes |
2024.5.4 did solve the issue for me too |
Just out of curiosity, what type of node did this cause issues on? Mainly i just wanted to see if there was any relevance to my situation where it mainly affected the ESP01-1M and Esp8266's that are most likely clones. |
It was a WeMos D1 Mini (ESP8266). |
2024.5.4, I'm just now encountering this very issue. Same setup, Wemos D1 Mini (ESP8266), LD2410. Encryption enabled -> problem seems to persist |
I don't want to upgrade my home assistant esphome for 2024.4.2 but it seems the devices initialized from esphome-web are now on 2024.5.4 and don't get detected/appear for 2024.4.2? Edit: Actually, probably user error - I had a second device connected to my PC that I was flashing instead of the one I intended to. And that was already in esphome/home assistant. Sadly, esphome let me add the device manually and quite happily overwrote the original yaml file for that device when I used the same esphome-web- format so I'll have to set it back up from scratch. |
no, it also happened with a esp8285, a 01S (8266 compatible), haven't tried the 2024.5.4 yet, i'm in no horry to cause more work than i want for myself as i have a lot of esp devices, so for now i stick the 4.2 |
2024.5.4 fixed it for me |
The problem
The issue starts to happen after upgrading to ESPHome 2024.5.0.
My LD2410 presence sensors are working fine with version 2024.4.2.
The firmware compilation log is attached: logs_bedroom-presence-sensor_run.txt
I will try to rollback now and see if i will be able to recover the sensors.
Which version of ESPHome has the issue?
2024.5.0
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2024.5.3
What platform are you using?
ESP8266
Board
D1 Mini (https://www.amazon.de/-/en/gp/product/B0754W6Z2F/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1)
Component causing the issue
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: