-
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
LED Updates #2170
LED Updates #2170
Conversation
Now it does. Changing any settings in WebUI or calling If there is any need in persistence, I think better option is to update |
I'm trying to understand what I need to
What do I define to make
Or just define the second LED2 and not have a Once configured, where do the pattern parameters get set? In the webUI? To make the 'buzzer' output the pattern, do I send an string e.g. |
The general idea is to use pattern instead of simply turning led ON. See debug panel to |
Please excuse my ignorance, so do I get rid of Once configured, I guess then in webUI I can then set |
LED pin should control the buzzer. Relay only controls the LED state, but if you keep RELAY2_PIN set it will turn it on briefly. You can add
Yep. When using manual mode, we need to use |
Perfect. All working, great work. I've added dummy relay and set LED1 in web to I'll do some more testing over the next few days but basically it meets my original request perfectly. 👍 |
Thanks! |
In my current configuration I do have a push button connected to
Setting
Could you have a final For my alarm system, the arming or trigged state could go something like: For reference |
Limit for amount of sets is actually the available RAM. Main issue is that kv settings storage can only store up to 255 chars. MQTT can accept more, ~1000 at least. |
includes & depends on #2162 , rebase will fix order
fix #2101
fix #2081
@davebuk 3rd try. if you can test this, clone the tree directly (as always)
This should work with any state that just turns LED either ON or OFF (relay follow, findme, always on, always off).
(space)
ledPatternN
setting, whereN
is LED ID, controls the pattern as500,500,10 100,100,0
. Rule is read left-to-right. Like the previous PR, only difference is that patterns are now separated byLED manual mode (
ledMode => 0
) via MQTT will use the setting too.Although, MQTT does not parse the pattern. Right now it checks for strings like
1
,on
,ON
,toggle
etc. I guess this can be changed and it could try to parse the pattern when it can't parse the status string