schinckel
commented
1 year ago Are you using an i2c bus? I needed to increase the bus speed after connecting a display using i2c.
Open leodrivera opened 1 year ago
schinckel
commented
1 year ago Are you using an i2c bus? I needed to increase the bus speed after connecting a display using i2c.
Loatan
commented
1 year ago Similar problem. I'm struggling with this problem to no avail. All advice from similar topics has been done, there is no significant difference. At first, removing the "ota", "ap", "logging" sections when adding components helped, but with a certain number of added component parameters, this no longer works. NODEMCU v3 and WEMOS d1 mini
wifi_apply_hostname_(lothost-ir): lwIP error -16 on interface st (index 0)
Event: Disconnected ssid='LOTHOST2' bssid=3C:7C:3F:AB:38:78 reason='Association Leave'ap_probe_send over, rest wifi status to disassoc
leodrivera
commented
1 year ago Are you using an i2c bus? I needed to increase the bus speed after connecting a display using i2c.
I've tested it with different components, including a component that made use of the i2c bus. In all cases where I used a component, I had the problem I described above.
leodrivera
commented
1 year ago Similar problem. I'm struggling with this problem to no avail. All advice from similar topics has been done, there is no significant difference. At first, removing the "ota", "ap", "logging" sections when adding components helped, but with a certain number of added component parameters, this no longer works. NODEMCU v3 and WEMOS d1 mini
wifi_apply_hostname_(lothost-ir): lwIP error -16 on interface st (index 0) Event: Disconnected ssid='LOTHOST2' bssid=3C:7C:3F:AB:38:78 reason='Association Leave'
ap_probe_send over, rest wifi status to disassoc
I've got this same error when trying one of the possible solutions (to use board: d1_mini ):
[W][wifi_esp8266:482]: Event: Disconnected ssid='Leo Wi-Fi' bssid=[redacted] reason='Beacon Timeout'
[W][wifi:125]: WiFi Connection lost... Reconnecting...
[W][wifi:585]: Restarting WiFi adapter...
[I][wifi:257]: WiFi Connecting to 'Leo Wi-Fi'...
[W][wifi_esp8266:212]: wifi_apply_hostname_(wemos-test): lwIP error -16 on interface st (index 0)
[D][text_sensor:067]: 'Wemos Test IP': Sending state '0.0.0.0'
[I][wifi:518]: WiFi Connected!
[C][wifi:362]: Local MAC: [redacted]
[C][wifi:363]: SSID: [redacted]
[C][wifi:364]: IP Address: 192.168.1.203
[C][wifi:365]: BSSID: [redacted]
[C][wifi:367]: Hostname: 'wemos-test'
[C][wifi:369]: Signal strength: -38 dB ▂▄▆█
[C][wifi:373]: Channel: 6
[C][wifi:374]: Subnet: 255.255.255.0
[C][wifi:375]: Gateway: 192.168.1.1
[C][wifi:376]: DNS1: 192.168.1.1
[C][wifi:377]: DNS2: 192.168.1.1
[D][text_sensor:067]: 'Wemos Test IP': Sending state '192.168.1.203'
[W][wifi_esp8266:482]: Event: Disconnected ssid='Leo Wi-Fi' bssid=[redacted] reason='Beacon Timeout'
[W][wifi:125]: WiFi Connection lost... Reconnecting...
[W][wifi:585]: Restarting WiFi adapter...
[I][wifi:257]: WiFi Connecting to 'Leo Wi-Fi'...
[W][wifi_esp8266:212]: wifi_apply_hostname_(wemos-test): lwIP error -16 on interface st (index 0)
[D][text_sensor:067]: 'Wemos Test IP': Sending state '0.0.0.0'
[I][wifi:518]: WiFi Connected!
[C][wifi:362]: Local MAC: [redacted]
[C][wifi:363]: SSID: [redacted]
[C][wifi:364]: IP Address: 192.168.1.203
[C][wifi:365]: BSSID: [redacted]
[C][wifi:367]: Hostname: 'wemos-test'
[C][wifi:369]: Signal strength: -33 dB ▂▄▆█
[C][wifi:373]: Channel: 6
[C][wifi:374]: Subnet: 255.255.255.0
[C][wifi:375]: Gateway: 192.168.1.1
[C][wifi:376]: DNS1: 192.168.1.1
[C][wifi:377]: DNS2: 192.168.1.1
[D][text_sensor:067]: 'Wemos Test IP': Sending state '192.168.1.203'
[W][wifi_esp8266:482]: Event: Disconnected ssid='Leo Wi-Fi' bssid=[redacted] reason='Beacon Timeout'
[W][wifi:125]: WiFi Connection lost... Reconnecting...
[W][wifi:585]: Restarting WiFi adapter...
[I][wifi:257]: WiFi Connecting to 'Leo Wi-Fi'...
[W][wifi_esp8266:212]: wifi_apply_hostname_(wemos-test): lwIP error -16 on interface st (index 0)
[D][text_sensor:067]: 'Wemos Test IP': Sending state '0.0.0.0'
[I][wifi:518]: WiFi Connected!
[C][wifi:362]: Local MAC: [redacted]
[C][wifi:363]: SSID: [redacted]
[C][wifi:364]: IP Address: 192.168.1.203
[C][wifi:365]: BSSID: [redacted]
[C][wifi:367]: Hostname: 'wemos-test'
[C][wifi:369]: Signal strength: -34 dB ▂▄▆█
[C][wifi:373]: Channel: 6
[C][wifi:374]: Subnet: 255.255.255.0
[C][wifi:375]: Gateway: 192.168.1.1
[C][wifi:376]: DNS1: 192.168.1.1
[C][wifi:377]: DNS2: 192.168.1.1
[D][text_sensor:067]: 'Wemos Test IP': Sending state '192.168.1.203'
[D][sensor:126]: 'Wemos Test Wi-Fi Signal': Sending state -34.00000 dBm with 0 decimals of accuracy
[W][wifi_esp8266:482]: Event: Disconnected ssid='Leo Wi-Fi' bssid=[redacted] reason='Beacon Timeout'
[W][wifi:125]: WiFi Connection lost... Reconnecting...
[W][wifi:585]: Restarting WiFi adapter...
[I][wifi:257]: WiFi Connecting to 'Leo Wi-Fi'...
[W][wifi_esp8266:212]: wifi_apply_hostname_(wemos-test): lwIP error -16 on interface st (index 0)
[D][text_sensor:067]: 'Wemos Test IP': Sending state '0.0.0.0'
[I][wifi:518]: WiFi Connected!
[C][wifi:362]: Local MAC: [redacted]
[C][wifi:363]: SSID: [redacted]
[C][wifi:364]: IP Address: 192.168.1.203
[C][wifi:365]: BSSID: [redacted]
[C][wifi:367]: Hostname: 'wemos-test'
[C][wifi:369]: Signal strength: -35 dB ▂▄▆█
[C][wifi:373]: Channel: 6
[C][wifi:374]: Subnet: 255.255.255.0
[C][wifi:375]: Gateway: 192.168.1.1
[C][wifi:376]: DNS1: 192.168.1.1
[C][wifi:377]: DNS2: 192.168.1.1
[D][text_sensor:067]: 'Wemos Test IP': Sending state '192.168.1.203'
[D][sensor:126]: 'Wemos Test Uptime': Sending state 55.83400 s with 0 decimals of accuracy
[D][sensor:126]: 'Wemos Test Wi-Fi Signal': Sending state -35.00000 dBm with 0 decimals of accuracy
[D][sensor:126]: 'Wemos Test Uptime': Sending state 115.83400 s with 0 decimals of accuracy
38decibel
commented
1 year ago Hi,
I have similar problem with an AzDelivery D1 mini based on esp8266ex ; reason='Probe Request Unsuccessful'. I solved this with an aluminum foil around the card, avoiding the antenna.
FGOD1983
commented
7 months ago apart from the joke, is there any update on a solution? because this is really frustrating
ssieb
commented
7 months ago That's not a joke. I expect that at least in that case, there's interference between the antenna and the rest of the board. You could try reducing the tx power. This has been a known issue with some 8266 boards.
FGOD1983
commented
7 months ago @ssieb the most strange thing about this is that I ordered 3 boards recently (my mistake that I selected these EX ones), and out of 3 1 has no issues at all and 2 have. All with the same config being loaded onto them.
So I just tossed those 2 in the bin and kept the one working now, but it kinda starts to feel more like a bad wifi chip on those board that sometimes is of better quality, then it actually being a design flaw like it is suggested
mevst
commented
4 months ago I had this problem on my 2 Sonoff basic R1 devices bought in 2016. I didn't use them until now. I tried all the advices from the issues listed in the original problem description. None of them actually solve the issue while some of them have a temporary impact, like removing some particular component from the code helps but adding some other brings the issie back. However the same code works OK on other ESP8266 devices. Code size is not the root of the issue After many experiments with FW and HW I figured out that this is a HW issue related to the crystal on the board. The crystal on my Sonoff Basic R1 units is very tiny, has no clear marking and as I suspect is faulty. I replaced it with little bit bigger crystal desoldered from perfectly working ESP01s module and now the previously faulty Sonoff Basic R1 works perfectly. I think that these small chrystal starts slowly at power up and at moment when boot code measures the CLK frequency and configures PLL the chrystal oscillation is not stable yet. Changes in code probably cause change in the boot timing. I see Sonoff uses similar chrystal in other devices (I see it on my Sonoff 4CH R3) and they works without problems. So the problim looks to be specific for a particular manyfacturing batches. The chrystal replacement isn't easy, I used hot air rework station and soltering paste to do it, so it isn't a solution for everyone. However I hope it explains the root reason of the issue.
The problem
I have a Wemos NodeMCU ESP8266 v3 - CH340 (https://botland.store/img/art/inne/10908_3.jpg) and I noticed that after installing esphome on it, the device wasn't able to connect to wi-fi).
The flashing process proceeds normally without any errors.
I performed the troubleshooting, seeking to isolate the problem. In this process, I did the following:
None of the previous attempts worked. Finally, as a last attempt, I compiled the code without any components, as shown below, and performed the flashing process:
Worked perfectly.
To confirm my suspicion, I added a simple remote_receiver component and flashed it again, as shown below, and the problem happened again.
PS: I have other esps running in my HA (ESP-12f and ESP-01) and never had problems like that. PS2: I've changed the board type to generic esp8266 (
esp01_1m) and the number pin to the corresponding GPIO (GPIO12) and the result was the same.Which version of ESPHome has the issue?
2022.11.4
What type of installation are you using?
Docker
Which version of Home Assistant has the issue?
2022.11.5
What platform are you using?
ESP8266
Board
Wemos NodeMCU ESP8266 v3 - CH340
Component causing the issue
any component
Example YAML snippet
No response
Anything in the logs that might be useful for us?
The log from the code without components (that is working):
The log from the code with components (that is not working):
And it keeps in a loop...
Additional information
No response