-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MQTT? #7
Comments
To resolve the issue of missing MQTT support in the "Sound Reactive WLED" firmware, a solution is to switch to the official WLED version, which includes MQTT support by default. First, download the official WLED firmware from the GitHub repository at [(https://github.com/Aircoookie/WLED)]. Then, upload the firmware to your ESP8266 or ESP32 device using the Arduino IDE or PlatformIO. Once installed, configure MQTT in the WLED configuration file. To enable it, go to wled00\config\WLED_esp8266_esp32.h and make sure the line #define WLED_MQTT is not commented out. After that, configure your MQTT credentials in the WLED user interface under the "Wi-Fi" -> "MQTT" section by entering your broker, port, and credentials. Once done, you can control WLED via MQTT using commands like: As alternatives to WLED, you can consider other firmwares like ESPHome, Tasmota, or FastLED. ESPHome is very easy to configure and integrates well with platforms like Home Assistant. To control LEDs with ESPHome, here's an example configuration:
Tasmota is also a valid option if you're looking for MQTT support from the start. Here’s an example of how to configure it to control RGB LEDs in Tasmota:
FastLED is a more advanced option, offering a lot of flexibility for programming custom effects and patterns on your lights. If you choose to use FastLED, you will need more programming work, but it allows for full control over light effects. |
Describe the solution you'd like
MQTT support please
Describe alternatives you've considered
I tested with stock WLED and it seems to work fine.
Additional context
The text was updated successfully, but these errors were encountered: