You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: