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

third action ("my") in schedules #100

Open
dfagnan opened this issue Jan 3, 2021 · 1 comment
Open

third action ("my") in schedules #100

dfagnan opened this issue Jan 3, 2021 · 1 comment

Comments

@dfagnan
Copy link

dfagnan commented Jan 3, 2021

This is a feature request but especially seeing that others are also having issues with "partial" schedules - I would advocate for adding the "my" action being supported in schedules which could be a good substitute for partial actions. Not sure if implementing this this was avoided given that the my action also functions as stop but for my use case right now it would be perfect. I could take a stab at this myself though it looks potentially incompatible with the position tracking.

@rbswift
Copy link
Contributor

rbswift commented Jan 3, 2021

I don't see a reason scheduling the My position should break position tracking if the ShutterIntermediatePositions are set correctly in the config. Scheduling a move the the My position could just calculate and sleep for the travel time between CurrentPosition and ShutterIntermediatePositions then update CurrentPosition to ShutterIntermediatePositions.

That said, more and more people are likely using mqtt with some independent home automation system for scheduling a range of household events rather than the inbuilt Pi-Somfy scheduler so that might be an option to consider instead.

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