-
Notifications
You must be signed in to change notification settings - Fork 1
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
One Light returns to previous state #1
Comments
Hi @mdeweerd can you tell me which device you're using? |
@mdeweerd unfortunately the MOES buttons only "kind of" work with my blueprint, you have to time your button presses long enough to avoid the "double press" action of MOES being triggered internally. Are you still using my blueprint or did you give up? |
I am not using the blueprint as I found another solution that works - I do not "give up" as such, I might try the blueprint for more presses in a future time. What is important to me is that you apparently know about this and I am on the same wavelength for the analysis. I conclude hat the blueprint is not usable for double presses for this device. |
@mdeweerd what I could do is add an option to only use the 1 and 2 press actions of the MOES button, which might work better for you |
Don't do it for me, bu tit may be useful for others - I can test it. |
Hi
I tested the moes_scene_switch_multi_press.yaml blueprint with zigbee light and I get an on command followed by a off command immediately (or vice versa) - so the light returns to the initial state.
I guess you're more familiar with the blueprint so you might spot the reason immediately. This does not happen with a simple on/off command.
trace automation.exterieur_3_button 2023-10-16T20_20_57.606094+00_00.json
This is the trace for the configuration further below.
Configuration:
The text was updated successfully, but these errors were encountered: