Zoogara
commented
4 years ago Same issue experienced, worked fine untill adding a timer and condition so maybe a memory issue?
Removed captive_portal:, all good
Open mguaylam opened 4 years ago
Zoogara
commented
4 years ago Same issue experienced, worked fine untill adding a timer and condition so maybe a memory issue?
Removed captive_portal:, all good
andordavoti
commented
4 years ago having the same issue, this bricked a lot of my sonoff devices. any news on how to fix this?
timelyfiasco
commented
4 years ago @andordavoti I experienced this also. But I cant reproduce the error. I am thinking maybe it was due to the dhcp server. Just start with a simple code then slowly add new modules and see if it works.
andordavoti
commented
4 years ago @timelyfiasco after swapping sonoffs, the new ones connected without issues. I have no idea why, it's the same code🙃
MaxWh1t3
commented
3 years ago https://github.com/esphome/issues/issues/952 worked for me on 3 boards!
BuildTheRobots
commented
3 years ago Had the same issue, but until I found this post I was convinced it was enabling/disabling a DHT sensor that was causing it. Now that I've disabled the captive_portal wifi and sensor are both working.
sielenk
commented
3 years ago EspHome Version 1.16.2
Changing the configuration for my device made this problem reappear for one of my devices. Adding or removing "captive_portal" has no effect, the same goes for "status_led".
It works when using "switch" with "gpio" platform for the relay and fails when replacing that with "output" and using that for the switch.
The files: atticfan.yaml (good) atticfan.yaml (bad)
andriej
commented
3 years ago Encountered this on one of my sonoffs. It was "down" since half of year (1.15), I've reflashed it and put newest 1.19.4 on - still "Probe request" and was not able to login to WiFi. I've found one of issues regarding removing "captive portal" - did that, removed one line, reflashed and it works like a charm.
DoctorOctagonapus
commented
3 years ago Welp, I'm stuck. Got a Sonoff Basic that's now totally unusable since updating to 2021.10.3.
Logs:
INFO Reading configuration /config/esphome/[name].yaml...
INFO Starting log output from /dev/ttyUSB0 with baud rate 115200
[15:21:24]scandone
[15:21:24][W][wifi_esp8266:479]: Event: Disconnected ssid='[name]' reason='Probe Request Unsuccessful'
[15:21:24]wifi evt: 1
[15:21:24]STA disconnect: 201
[15:21:24][W][wifi:535]: Error while connecting to network.
[15:21:24][W][wifi:570]: Restarting WiFi adapter...
[15:21:24][V][wifi_esp8266:060]: Disabling STA.
[15:21:24]del if0
[15:21:24]usl
[15:21:24]mode : null
[15:21:24][V][wifi_esp8266:535]: Event: Changed Mode old=STA new=OFF
[15:21:24]wifi evt: 8
[15:21:30][I][wifi:247]: WiFi Connecting to '[name]'...
[15:21:30][V][wifi:249]: Connection Params:
[15:21:30][V][wifi:250]: SSID: '[name]'
[15:21:30][V][wifi:255]: BSSID: Not Set
[15:21:30][V][wifi:273]: Password: [redacted]
[15:21:30][V][wifi:280]: Channel: Not Set
[15:21:30][V][wifi:287]: Using DHCP IP
[15:21:30][V][wifi:289]: Hidden: NO
[15:21:30][V][wifi_esp8266:058]: Enabling STA.
[15:21:30]mode : sta([Mac])
[15:21:30]add if0
[15:21:30][V][wifi_esp8266:535]: Event: Changed Mode old=OFF new=STA
[15:21:30]wifi evt: 8
[15:21:32]scandone
[15:21:32][W][wifi_esp8266:479]: Event: Disconnected ssid='[name]' reason='Probe Request Unsuccessful'
[15:21:32]wifi evt: 1
[15:21:32]STA disconnect: 201
[15:21:32][W][wifi:535]: Error while connecting to network.
[15:21:32][W][wifi:570]: Restarting WiFi adapter...
Eventually it starts up the fallback AP and continues on a loop of failed connection attempts.Config:
name: [redacted]
platform: ESP8266
board: esp01_1m
wifi:
# Hidden SSID
ssid: !secret wifi_ssid
password: !secret wifi_pw
fast_connect: true
output_power: 10db
ap:
ssid: [name]
password: [redacted]
#captive_portal:
# Enable logging
logger:
level: VERBOSE
# Enable Home Assistant API
api:
ota:
...I've already disabled captive_portal after this device broke with the same error once before. It was fine with previous versions of ESPHome, but the latest one has broken it completely now apparently. All my other ESP devices work, including another Sonoff Basic that still has captive_portal enabled. This one has apparently just decided it doesn't wanna live any more.
Any ideas?
tmarkson
commented
2 years ago Any ideas?
@DoctorOctagonapus I suggest simplifying your config to barebones, as others have before. Try removing the ap, output_power, and level items. Remove any other components below ota and try flashing -- if that works, then add those components individually, uploading firmware in between adds. I've found compatibility issues this way, especially when using ESP8266 devices that seem to choke on complex items. Some variants may be running at reduced clock or another handicap.
pironic
commented
2 years ago here is my config
substitutions:
id: bes02
ip: 10.1.50.121
class: door
version: 22.04.09.02
esphome:
name: ${id}
platform: esp8266
board: nodemcu
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_pass
fast_connect: true
manual_ip:
static_ip: "${ip}"
subnet: 255.255.255.0
gateway: 10.1.50.1
ap:
ssid: "${id} Fallback"
password: !secret wifi_pass
logger:
level: VERBOSE
baud_rate: 76800
hardware_uart: UART0And i'm getting the same problems on 2022.3.2. Did anyone ever figure out a true cause for this?
alnavasa
commented
2 years ago Robotdyn 2x relay board, ESP8266 same issue with wireless as soon as the code was a little bit interesting. managed to solve the issue by commenting the lines of captive portal and fallback ap
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# power_save_mode: none
# Enable fallback hotspot (captive portal) in case wifi connection fails
# ap:
# ssid: "$device_name Fallback Hotspot"
# password: "lghjfd5rfsU"
#captive_portal:
hcooper
commented
1 year ago +1, I found a fresh install of ESPHome on a Sonoff Basic R2 fails with
[W][wifi_esp8266:479]: Event: Disconnected ssid=... reason='Probe Request Unsuccessful'However I can confirm adding debug: to the config makes it work!
Also of note, a fresh install of Tasmota works fine (v12.3.1)
vks007
commented
1 year ago I am also getting the same error with many of my modules. Is there a solution to this? The other thread suggested to use framework version 1.8.0 but that's too old now, it doesnt even compile now. @hcooper are you sure adding debug helps because logger level debug is anyway the default?
johny-mnemonic
commented
1 year ago This must be some kind of conflict in the compilation. I just hit this exact issue after using two Sonoff basics with same configuration for a long time without any issue. What triggered it was adding the DHT sensor definition to one of them. After going through these threads I came to a conclusion it must be a combination of modules that results to either filling too much RAM or using too much of some other resource of this poor little bugger. And sure enough, removing some modules fixed it. So, my Sonoff basic modules were both running with captive portal, mqtt client, binary_sensor, switch and output defined. The one where I added the DHT sensor is now running just fine with captive portal and mqtt removed. Not sure which one was the culprit but after removing these and flashing it using serial link it works just fine 🤷♂️
myLens
commented
1 year ago I also ended up in a messed runtime. Adding and removing modules leads to unpredictable results - no matter it it is webserver, a simple sensor, the captive portal .... I suppose the wifi_esp8266 has memory issues or some combination of modules causes malfunction. Sometimes it works like a charm but even the slightest change can become a game changer - very disappointing.
aiexz
commented
1 year ago Removing captive_portal from config worked for HW-628 board (nodemcu clone)
kjake
commented
1 year ago However I can confirm adding
debug:to the config makes it work!
+1 this worked for me on two of my D1 boards and got them back online with the latest build of ESPhome (2023.9.3)
Operating environment/Installation (Hass.io/Docker/pip/etc.):
Docker raspbian ESP (ESP32/ESP8266, Board/Sonoff):
8266 Sonoff basic Affected component:
https://esphome.io/components/captive_portal.html
Description of problem: When enabling captiveportal: on the sonoff basic (8266), it cannot connect to the Wi-Fi showing this error in the console : reason='Probe Request Unsuccessful' while trying to connect to my AP. If I remove the captiveportal:, it works fine. Also, adding debug: seem's to fix the issue weirdly. I can confirm that the captive portal is working with (debug:) added to the config.
Problem-relevant YAML-configuration entries:
Logs (if applicable):
Additional information and things you've tried:
Working logs :