thank you. yes others have mentioned it before. and i have been resisting it. ![]()
its not whimsical resistance. let me explain … ST in its docs says:
Number of scheduled executions limit
The canSchedule() method returns false if four or more scheduled executions are created.
This currently does not actually impact the ability to create additional schedules, but such a limit may be imposed in the near future. A community post will be made in advance of any such change.
thats from this link:
the child apps already use 4 timers aka scheduled executions. adding time offset would require at least couple more timers. i am hesitant to build something knowing it might break suddenly if ST starts enforcing that limit. then users will be left with no easy solution to rooms that they have already setup with these rules that have time offsets. this is why i have been resisting it. ![]()
that said i use lux instead of time offset. it works really well and even better than time offset. give it a shot think you will like it better. ![]()
EDIT: there is no need to buy anything to get access to lux. its available from ST provided app already you just need to install it and start using it as the lux sensor.