Closed jsuanet closed 1 year ago
Hey there, ran into the same issue you described above. I was able to work around this by switching from FastLED light to NeoPixelBus Light.
Here's a sample of my code
esphome:
name: esp-office
esp8266:
board: nodemcuv2
framework:
version: recommended #2.7.4
wifi:
ssid: !secret ssid
password: !secret wifi
fast_connect: true
power_save_mode: none
logger:
api:
encryption:
key: !secret key
ota:
i2c:
sda: D2
scl: D1
scan: False
sensor:
- platform: dht
pin: D6
model: dht22
temperature:
name: "esp_office_temp"
id: temp
humidity:
name: "esp_office_humidity"
update_interval: 30s
- platform: bh1750
name: "esp_office_lux"
address: 0x23
update_interval: 30s
binary_sensor:
- platform: gpio
pin: D0
name: "esp_office_motion"
device_class: motion
id: motion
filters:
- delayed_off: 60s
on_state:
then:
- if:
condition:
binary_sensor.is_on: motion
then:
- light.turn_on:
id: led1
red: 100%
green: 100%
blue: 0%
brightness: 35%
- delay: 5s
else:
- light.turn_on:
id: led1
red: 0%
green: 100%
blue: 0%
brightness: 35%
light:
- platform: neopixelbus
variant: WS2812
pin: D3
num_leds: 1
type: RGB
name: "esp_office_led"
id: led1
Yes, I know that switching to Neopixelbus solves the problem, however for me that's a work around. If the fastled component is not longer working anymore, it should be declared deprecated and a "breaking change" item in the release notes, otherwise it is just a bug in the new 2023.3.0 version 😄
Same here - was planning to move to Neopixelbus but this should be reported nevertheless.
I created a PR that should fix the issue, i belief. https://github.com/esphome/esphome/pull/4257 love to know of this will help fixing your issues.
Hi everyone, just to add one more issue with EspHome 2023.3.0, it also affected my pi pico w. Then I restored and EspHome to an earlier version and would not start. just FYI.
lol, didnt see it until now, buit I am pretty sure this is the fix
Swapped {}
for ()
--- a/esphome/core/helpers.h
+++ b/esphome/core/helpers.h
@@ -550,7 +550,7 @@ class Mutex {
*/
class LockGuard {
public:
- LockGuard(Mutex &mutex) : mutex_{mutex} { mutex_.lock(); }
+ LockGuard(Mutex &mutex) : mutex_(mutex) { mutex_.lock(); }
~LockGuard() { mutex_.unlock(); }
private:
Yes I got the update after the post. Thanks
On Tue, Mar 21, 2023, 8:55 PM Jesse Hills @.***> wrote:
lol, didnt see it until now, buit I am pretty sure this is the fix
index a4f64171f..05a7eaa4c 100644--- a/esphome/core/helpers.h+++ b/esphome/core/helpers.h@@ -550,7 +550,7 @@ class Mutex { */ class LockGuard { public:- LockGuard(Mutex &mutex) : mutex{mutex} { mutex.lock(); }+ LockGuard(Mutex &mutex) : mutex(mutex) { mutex.lock(); } ~LockGuard() { mutex_.unlock(); }
private:
— Reply to this email directly, view it on GitHub https://github.com/esphome/issues/issues/4324#issuecomment-1478884647, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEGPBGMJGL5TBJZYDJO7I63W5JZ4TANCNFSM6AAAAAAV7MDOF4 . You are receiving this because you commented.Message ID: @.***>
I installed 2023.3.1 update but it didn 't make any change regarding this issue. The compile error still remained.
The PR is already merged in the dev branch and has label 2023.3.2, so you have to wait till that version is released. I tested with the dev version and with that version the problem is solved.
The problem
After upgrading ESPHome to version 2023.3 you get compile errors when using Fastled component and Arduino framework 2.7.4.
Which version of ESPHome has the issue?
2023.3.0
What type of installation are you using?
Docker
Which version of Home Assistant has the issue?
n.a.
What platform are you using?
ESP8266
Board
Wemos D1-mini
Component causing the issue
Fastled
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response