-
Notifications
You must be signed in to change notification settings - Fork 638
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
Add support for LYT8266 Bulb #213
Comments
I think a better option would be to use them as normal switches (ON/OFF):
Probably a nice add on would be to be able to rename the switches on the webUI, so intead of "switch 1", "switch 2",... you could have "Red", "Green", ... |
Original comment by Joe Biellik (Bitbucket: JoeBiellik, GitHub: JoeBiellik): Thanks for the reply, but that's not helped the issue. I could add the LED enable pin as a normal relay but if I don't use |
Wouldn't it be simpler to use a RELAY_PROVIDER_LIGHT and add the option to define a LIGHT_ENABLE_PIN than would be sync'd with the status? Something like this: 8bad421 |
I have released the code with 1.9.6, can anyone test the proposed solution? |
Original comment by Joe Biellik (Bitbucket: JoeBiellik, GitHub: JoeBiellik): Sorry for the slow reply and thanks for addressing this. I'll give your changes a try ASAP. |
Original comment by Joe Biellik (Bitbucket: JoeBiellik, GitHub: JoeBiellik): I can confirm the latest version works, setting the enable pin was exactly what was needed. Thanks again for adding support. |
Originally reported by: Joe Biellik (Bitbucket: JoeBiellik, GitHub: JoeBiellik)
I've been running ESPurna on a Sonoff S20 and wanted to port it to a LYT8266 LED bulb.
The bulb is a basic ESP8266 with 1Mb flash, RGBW LEDs.
The bulb has a pin which turns on and off all the LEDs. I've got it running but had to make a couple of changes as I couldn't see a way to do it built in.
I added a new relay type and code to switch the pin and set the light state:
Is there an easier way to achieve this? If not would you accept a pull request?
Thanks for the great firmware.
The text was updated successfully, but these errors were encountered: