Skip to content
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

Blinds with STOP Button - plus - "lag" field to handle different blinds at the same time with same radio frequency #10

Open
frankmrbreads opened this issue May 18, 2018 · 1 comment

Comments

@frankmrbreads
Copy link

Hi,

I successfully installed and configured your homebridge-gpio-blinds plugin

Thank you so mach for that, it’s preatty useful

I was wondering if you could make a new version of the plugin with “a little change"
I’m new in raspberry and programming world and don0t know where to start unfortunately

In my blinds remotes (that I control via GPIO pins with your plug in) I have one more button, the STOP one.
The remote send 3 message, UP, DOWN and STOP and neither of the 3 need to be long pressed.
When I push the DOWN button the blind shut and automatically stop when is completely closed.
Same thing for the UP button.

So I would really like a version of the plugin where I can set the 3rd button to handle a midway stop of my blinds.

I think this could be done using the durationUp/Down time field and calculating the right moment to send the STOP message.

Another really appreciated feature would be a “lag” field to handle different blinds at the same time, because all the remotes
work with same frequency (different channels) and if UP/DOWN/STOP button is pressed at the same time in 2 or more remotes
none of the messages are sent to the blinds.
With a “lag” field I would be able to space slightly in time, different simultaneus messages without having problems.

I know it’s a big request
Feel free to decline

many thanks in advance

@chrisremie
Copy link

I would be very happy with a similar but different extra option: the 'second' click (after open or close) of the button would stop the blinds.
This could be an optional setting: enable stop: true
So if the blinds were closed, a sequence would be: 'click': blinds start opening (blinds still opening) 'click': blinds stop opening 'click': blinds start closing ..... etcetera

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants