My light bulbs flashed with ESPHome looses WiFi connection and is then unable to reconnect. When the bulbs are lit in about 5-10 minuets they loose wifi connection. Then they are unable to reconnect and they do not start the access point either. The only way to get connection again is to cut the power and restart them that way. Im am currently running ESPHome v1.16.0-dev since some other people have hade better luck with connection issues with this firmware, but without success for me. The bulbs I am using are Blitzwolf BW-LT27 RGBCCT.
esphome:
name: taklampa1
platform: ESP8266
board: esp8285
wifi:
ssid: "ssid"
password: "pass"
manual_ip:
static_ip: 10.0.1.201
gateway: 10.0.1.1
subnet: 255.255.255.0
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Taklampa1 Fallback Hotspot"
password: "pass"
captive_portal:
# Enable logging
logger:
# Enable Home Assistant API
api:
ota:
light:
- platform: rgbww
name: "Taklampa 1"
red: red
green: green
blue: blue
cold_white: cold_white
warm_white: warm_white
cold_white_color_temperature: 6500 K
warm_white_color_temperature: 2700 K
output:
- platform: esp8266_pwm
id: red
pin: 15
- platform: esp8266_pwm
id: green
pin: 5
- platform: esp8266_pwm
id: blue
pin: 12
- platform: esp8266_pwm
id: cold_white
pin: 14
- platform: esp8266_pwm
id: warm_white
pin: 4
They are not connected to wifi, can’t se them in my router interface nor in my wifi scanner app. I have tried set up the webserver but since the devices don’t connect to wifi I am unable to accesses the webserver or ping them.
They are connected to wifi and everything works well until I light the bulbs. Then after about 5-10 minuets they looses their connection and I have to cut the power to connect to them again.
[07:53:39][VV][api.service:220]: on_ping_request: PingRequest {}
[07:53:39][VV][api.service:032]: send_ping_response: PingResponse {}
[07:53:45][VV][api.service:220]: on_ping_request: PingRequest {}
[07:53:45][VV][api.service:032]: send_ping_response: PingResponse {}
[07:53:47][VV][api.service:220]: on_ping_request: PingRequest {}
[07:53:47][VV][api.service:032]: send_ping_response: PingResponse {}
[07:53:50][VV][api.service:220]: on_ping_request: PingRequest {}
[07:53:50][VV][api.service:032]: send_ping_response: PingResponse {}
[07:53:55][VV][api.service:220]: on_ping_request: PingRequest {}
[07:53:55][VV][api.service:032]: send_ping_response: PingResponse {}
[07:54:00][VV][api.service:220]: on_ping_request: PingRequest {}
[07:54:00][VV][api.service:032]: send_ping_response: PingResponse {}
[07:54:02][VV][api.service:220]: on_ping_request: PingRequest {}
[07:54:02][VV][api.service:032]: send_ping_response: PingResponse {}
[07:54:05][VV][api.service:220]: on_ping_request: PingRequest {}
[07:54:05][VV][api.service:032]: send_ping_response: PingResponse {}
[07:54:10][VV][api.service:220]: on_ping_request: PingRequest {}
[07:54:10][VV][api.service:032]: send_ping_response: PingResponse {}
WARNING Disconnected from API: Timeout while waiting for message response!
INFO Connecting to 10.0.1.201:6053 (10.0.1.201)
WARNING Couldn't connect to API (Error connecting to 10.0.1.201: timed out). Trying to reconnect in 1 seconds
INFO Connecting to 10.0.1.201:6053 (10.0.1.201)
WARNING Couldn't connect to API (Error connecting to 10.0.1.201: timed out). Trying to reconnect in 1 seconds
INFO Connecting to 10.0.1.201:6053 (10.0.1.201)
WARNING Couldn't connect to API (Error connecting to 10.0.1.201: timed out). Trying to reconnect in 2 seconds
INFO Connecting to 10.0.1.201:6053 (10.0.1.201)
WARNING Couldn't connect to API (Error connecting to 10.0.1.201: [Errno 113] No route to host). Trying to reconnect in 3 seconds
INFO Connecting to 10.0.1.201:6053 (10.0.1.201)
WARNING Couldn't connect to API (Error connecting to 10.0.1.201: [Errno 113] No route to host). Trying to reconnect in 5 seconds
INFO Connecting to 10.0.1.201:6053 (10.0.1.201)
WARNING Couldn't connect to API (Error connecting to 10.0.1.201: [Errno 113] No route to host). Trying to reconnect in 7 seconds
INFO Connecting to 10.0.1.201:6053 (10.0.1.201)
WARNING Couldn't connect to API (Error connecting to 10.0.1.201: [Errno 113] No route to host). Trying to reconnect in 11 seconds
INFO Connecting to 10.0.1.201:6053 (10.0.1.201)
WARNING Couldn't connect to API (Error connecting to 10.0.1.201: [Errno 113] No route to host). Trying to reconnect in 17 seconds
INFO Connecting to 10.0.1.201:6053 (10.0.1.201)
WARNING Couldn't connect to API (Error connecting to 10.0.1.201: [Errno 113] No route to host). Trying to reconnect in 25 seconds
INFO Connecting to 10.0.1.201:6053 (10.0.1.201)
WARNING Couldn't connect to API (Error connecting to 10.0.1.201: [Errno 113] No route to host). Trying to reconnect in 30 seconds
INFO Connecting to 10.0.1.201:6053 (10.0.1.201)
WARNING Couldn't connect to API (Error connecting to 10.0.1.201: [Errno 113] No route to host). Trying to reconnect in 30 seconds
INFO Connecting to 10.0.1.201:6053 (10.0.1.201)
WARNING Couldn't connect to API (Error connecting to 10.0.1.201: [Errno 113] No route to host). Trying to reconnect in 30 seconds
INFO Connecting to 10.0.1.201:6053 (10.0.1.201)
WARNING Couldn't connect to API (Error connecting to 10.0.1.201: [Errno 113] No route to host). Trying to reconnect in 30 seconds
INFO Connecting to 10.0.1.201:6053 (10.0.1.201)
WARNING Couldn't connect to API (Error connecting to 10.0.1.201: [Errno 113] No route to host). Trying to reconnect in 30 seconds
I have two Blitzwolf bulbs and both of them have this problem. I have ordered two new EXUP bulbs so have to wait for them to see if they have the same problem. There was no problem when I only had one bulb but as soon I setup the second both of them started to act like this.
Found the problem, the bulbs were overheating because the RGB led still were lit when the white led were lit. Fixed this by adding color_interlock: true to my yaml. I also added constant_brightness: true to prevent further overheating.