poudenes
(Poudenes)
December 27, 2023, 2:14pm
1
Hi all,
I updated my Esphome to 2023.12.5 and updated all my esp modules (wall switches). After I restart HA suddenly all esp went offline. Connect them to serial and checked the log.
All modules had problems to connect the wifi connection.
Downgraded ESPhome to 2023.12.3 and cleared the esp builds and reinstalled them all via serial. They are connected again and working correct.
Does anybody else have same issues?
Mats789
December 27, 2023, 5:23pm
2
No help but works fine here …
zoogara
(Daryl)
December 27, 2023, 7:38pm
3
No. Collect your yaml, the logs and full hardware specs and log an issue on GitHub. There may be one already logged for your device.
issue tracker .
1 Like
nickrout
(Nick Rout)
December 27, 2023, 7:48pm
4
Same here. All fine so far.
Edwin_D
(Edwin D.)
December 27, 2023, 8:06pm
5
Just tried both an arduino based and an esp-idf based one, not problems.
poudenes
(Poudenes)
December 27, 2023, 8:14pm
6
Ok. Will update esphome and update one of the devices and see what happen. If goes wrong will start a issue. Thanks for the feedback
zoogara
(Daryl)
December 28, 2023, 4:56am
7
Not sure if it’s related to this issue with Sonoff devices:
opened 11:10AM - 23 Dec 23 UTC
### The problem
I have several Sonoff Mini devices which worked quite well unti… l 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
```yaml
substitutions:
plug_name: "wzlichtwandlinks"
friendly_name: "Wand Links"
esphome:
name: ${plug_name}
platform: ESP8266
board: esp8285
wifi:
ssid: !secret wifi50_name
password: !secret wifi50_pwd
domain: .tondorf
use_address: 192.168.90.207
# manual IP
manual_ip:
static_ip: 192.168.90.207
gateway: 192.168.90.1
subnet: 255.255.255.0
dns1: 1.1.1.1
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "${friendly_name}"
password: !secret esp_fallback_hs_pwd
# Enable logging
logger:
# level: VERBOSE
# Enable Home Assistant API
api:
encryption:
key: !secret esp_api_key
ota:
safe_mode: True
password: !secret esp_ota_pwd
time:
- platform: homeassistant
id: homeassistant_time
status_led:
pin:
number: GPIO13
inverted: true
binary_sensor:
- platform: gpio
pin: GPIO00
id: reset
internal: true
filters:
- invert:
- delayed_off: 10ms
on_press:
- light.toggle:
id: ${plug_name}_light
- platform: gpio
name: "${friendly_name} Switch"
pin: GPIO04
id: ${plug_name}_switch
on_press:
then:
- light.turn_on:
id: ${plug_name}_light
on_release:
then:
- light.turn_off:
id: ${plug_name}_light
output:
- platform: gpio
pin: GPIO12
id: ${plug_name}_relay
light:
- platform: binary
name: "${friendly_name} Licht"
id: ${plug_name}_light
output: ${plug_name}_relay
```
### Anything in the logs that might be useful for us?
```txt
No
```
### Additional information
_No response_
I had the same issue with my Wi-Fi plug so I downloaded the bin file the and connected to the failback wifi network of the plug. Then I flashed the ota update and it started working again.
poudenes
(Poudenes)
December 28, 2023, 6:01am
9
Even that was not possible… The fallback wifi didn’t came up also.
poudenes
(Poudenes)
December 28, 2023, 12:13pm
10
This error I get now when I update 1 of the ESP:
[I][app:029]: Running through setup()...
[I][wifi:300]: WiFi Connecting to 'MY_WIFI_NAME'...
[W][wifi_esp8266:496]: Event: Disconnected ssid='MY_WIFI_NAME' bssid=D4:00:00:00:00:50[redacted] reason='Auth Expired'
[W][wifi:618]: Error while connecting to network.
[W][wifi:654]: Restarting WiFi adapter...
[W][wifi_esp8266:496]: Event: Disconnected ssid='MY_WIFI_NAME' bssid=D4:00:00:00:00:50[redacted] reason='Authentication Failed'
It seems then it is connected all other ESP’s in the house are unstable. Take very long time before they react.
#########################################################
# Below all fixed settings for doorbell PCB
#########################################################
substitutions:
devicename: meek-doorbell
friendly: Doorbell
ip: 192.168.100.211
neopixel: GPIO02 # (D4)
gpio_relay4: GPIO13 # (D7)
#########################################################
# Everything below can be copy/paste without problem
#########################################################
esphome:
name: ${devicename}
on_boot:
priority: 600
then:
- lambda: WiFi.setPhyMode(WIFI_PHY_MODE_11G);
esp8266:
board: esp01_1m
restore_from_flash: true
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
reboot_timeout: 0s
fast_connect: true
manual_ip:
static_ip: ${ip}
gateway: 192.168.100.1
subnet: 255.255.255.0
dns1: 192.168.100.1
ap:
ssid: ${devicename}
password: !secret password
channel: 4
api:
encryption:
key: !secret api_key
reboot_timeout: 15min
time:
- platform: homeassistant
id: homeassistant_time
captive_portal:
web_server:
port: 80
preferences:
flash_write_interval: 1min
logger:
level: INFO
ota:
safe_mode: true
password: !secret password
button:
- platform: factory_reset
name: "${friendly} - Reset"
light:
- platform: neopixelbus
default_transition_length: 0s
type: GRB
variant: 800KBPS
pin: ${neopixel}
num_leds: 1
name: "${friendly} - Neopixel"
restore_mode: RESTORE_DEFAULT_OFF
id: neopixel
binary_sensor:
- platform: gpio
pin:
number: ${gpio_relay4}
inverted: true
name: "${friendly} - Doorbell"
switch:
- platform: safe_mode
name: "${friendly} - Safe Mode"
text_sensor:
- platform: wifi_info
ip_address:
name: "${friendly} - ip"
icon: mdi:lan
ssid:
name: "${friendly} - ssid"
icon: mdi:lan
bssid:
name: "${friendly} - bssid"
icon: mdi:lan
mac_address:
name: "${friendly} - Mac"
icon: mdi:lan
- platform: version
name: "${friendly} - Version"
hide_timestamp: true
sensor:
- platform: wifi_signal
name: "${friendly} - wifi Signal"
update_interval: 5min
- platform: uptime
name: "${friendly} - Uptime"
update_interval: 5min
poudenes
(Poudenes)
January 1, 2024, 1:29pm
11
Tried it again with ESPhome 2023.12.5. There are Wifi issues.
Stupid as I am. The HA Backups goes every day with a keep of 3 days…
Now I lost my backup with ESPhome 2023.12.3 or less.
Does someone have a backup of this ESPhome 2023.12.3 or less and want send me this zip?
zoogara
(Daryl)
January 2, 2024, 1:12am
12
Can you install via the command line on a PC or Mac?
https://esphome.io/guides/installing_esphome
If so, when you get to the bit when you install ESPHome:
pip install esphome
install instead a specific version:
pip install esphome==2023.12.0
or whatever version you require.
Once you have done that - create a config directory on your PC, fire up the dashboard pointing to that directory, create a new device with the same name as the one you want to roll back , then copy and paste your yaml into that dashboard and do an OTA or USB install.
1 Like
zoogara
(Daryl)
January 2, 2024, 1:18am
13
poudenes:
web_server:
port: 80
Or you could try removing web_server:
- it may solve all your problems.
1 Like
poudenes
(Poudenes)
January 2, 2024, 7:30am
14
Installed now ESPhome 2023.12.0 and build the BIN files now.
Then update all devices and see if my problems are gone again.
Thanks for this idea!!
poudenes
(Poudenes)
January 2, 2024, 9:13am
15
All devices are downgraded now to 2023.12.0. What a difference.
Wifi connects very fast again. The Wifi module on the device is less warm now.
With 2023.12.5 the steel plate was hot. Now it’s low again.
Wifi signal -72 dBm a -78 dBm now back to -50 dBm a -67 dBm
On reset of modules there are no delay in beginning with the touch to turn on bulbs.
Response time is extreme faster with 2023.12.0
For me, all issues are solved. Have backups of all BIN files for 2023.12.0
So when I’m upgrade ESPhome to a newer version of 2023.12.5 and still have issues I can revert back.
@zoogara thanks for the advice of installing ESPhome on PC/Mac
1 Like
gaz99
(Gaz)
January 2, 2024, 10:40am
16
There is also the ESPHome Legacy add-on which allows you to run old versions.
5 Likes
nickrout
(Nick Rout)
January 2, 2024, 10:49am
17
Man I wish I heard of that before!! Thanks.
gaz99
(Gaz)
January 2, 2024, 10:30pm
18
Yes, it has proved to be quite useful for troubleshooting.
poudenes
(Poudenes)
January 16, 2024, 1:15pm
19
It seems that ESPhome 2023.12.6 is ok. Also the “generate unique” errors are gone