Closed RomainD2 closed 3 years ago
Yes, yes. It is still broken https://github.com/esphome/issues/issues/1481 and it is affecting 1.15.x and dev branch.
Just add this and it will work again.
esphome:
platformio_options:
lib_deps: NeoPixelBus@2.6.0
Operating environment/Installation (Hass.io/Docker/pip/etc.):
Docker ESP (ESP32/ESP8266, Board/Sonoff):
ESP32 ESPHome version (latest production, beta, dev branch)
1.15.3 Affected component:
https://esphome.io/components/light/neopixelbus.html
Description of problem: Hi,
I have a problem with an ESPHome light which was working well for one year.
I tried to do a minor change and upload the code with OTA update, and my device wasn't working anymore, and couldn't connect to wifi.
I upload again the previous yaml code which was working fine for one year, and I had the same problem. After some investigations, I found that the problem appears when I add the Neopixelbus platform line. When I am trying to use it, all my device doens't work anymore, and I have no wifi.
I don't remember which was the ESPHome version when my device was working fine.
You can find attached the below yaml which works, and when I remove the # from these lines :
It doesn't work anymore
I tried to upload the bin file with ESPHome-Flasher in order to see the log with serial port, and I had that :
And nothing more happen...
Note : The device is not connected to my light, so it is normal that some stuff as I2C devices are not avalaible. But even when the ESP32 is connected to my light, it doesn't work.
Problem-relevant YAML-configuration entries:
Logs (if applicable):
Additional information and things you've tried: