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 2023.12.3 killed my Sonoff Mini devices #5280
Comments
Same here with Sonmoff basic (HW: TH_V1.1). After several years running without problems, 2023.12.3 version kills all Sonoff devices in my home. Conected vía USB serial, the device is in Wifi conection loop:
The config:
|
I was able to recover one of the devices. It seems that not latest firmware was uploaded. A few weeks ago I rearranged my network and moved esphome devices from WIFI50 (VLAN 50) to WIFI90 (VLAN90) and disabled WIFI50 (VLAN 50). No problems until ESPHome 12.x. |
Reverted back all devices to 2023.12.1 via serial, and all are working again (I have had to unwire all of them, because to upgrade serially they have to be removed from live cables). There is definitely a problem in this version (2023.12.3) with the sonoff wifi. |
https://community.home-assistant.io/t/esphome-2023-12-5-bricked-my-esp-s/661901/19?u=participant |
I was staying on version 2023.12.1 until there was an explicit solution to the problem, but after seeing your post I decided to give it a try. I just upgraded one of the devices to version 2023.12.8 and it died again. I can confirm that the problem is still unresolved. For now I will downgrade to version 2023.12.1 again, while waiting for an explicit solution in the Changelog, as each failed test takes me more than half an hour between unwire, flash and mount. If no solution is given, I will consider placing some zigbee, but I feel bad for it because it has been working for years and the problem is some change introduced in version 2023.12.2. |
Thanks for trying. Sorry it didn't work out. All my Sonoff devices are installed in inaccessible areas, and I've never successfully flashed a single one of them via TTL adapter, so they'd have to go in the bin if I had tried it and they got knocked offline. Thanks. |
FWIW, I had 2 sonoff basics and a handful of S31s upgrade to 2023.12.9 just fine. 🤷 |
Thanks for info. I have tried with my two Sonoff basics, and they died with 2023.12.9. One of them have conected to Wifi after trying several minutes, but after a reboot, It didn't connect anymore. Reverted back to 2023.12.1, and working again. Looking for Zigbee switches as I only have 2... |
The problem
I have several Sonoff Mini devices which worked quite well until I upgraded from 2023.11.6 to 2023.12.3.
After update they don't appear in my wifi (and HomeAssistant) anymore and they started recovery AP.
When I connect to recovery AP I can reach them by ping 192.168.4.1, but when try to update them from windows commandline I get an error.
esphome run --device 192.168.4.1 C:\Users\marku\Downloads\wzlichtwandlinks.yaml
...
RAM: [==== ] 39.0% (used 31932 bytes from 81920 bytes)
Flash: [==== ] 42.6% (used 436403 bytes from 1023984 bytes)
============================================= [SUCCESS] Took 5.64 seconds =============================================
INFO Successfully compiled program.
INFO Connecting to 192.168.4.1
ERROR Connecting to 192.168.4.1:8266 failed: [WinError 10061] Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte (sorry for german, connection is refused, wrong port?).
First I thought that maybe I have some wifi issues, but after the third device shows the same issue, I suppose it might be related to ESPHome version. Other Sonoff devices or Gosund sockets updated without any issues.
Which version of ESPHome has the issue?
2023.12.3
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2023.12
What platform are you using?
ESP8266
Board
sonoff mini
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: