Just thinking about it I wonder if this option needs an internet connection to function or if there is a built in table used?
@skywatch IIRC, there is no service required internet in MyController V1.
sunrise sunset too calculated locally based on the latitude and longitude.
In MyController, we are using https://github.com/mikereedell/sunrisesunsetlib-java
@jkandasa Thank you!
@jkandasa I was thinking more on this, I suppose that without a RTC then it all depends on the accuracy of the 'fake clock' on the pi? I also assume that the pi needs NTP to update the clock at regular intervals to remain accurate.
Maybe in version 2.0 we could add in an option for RTC module (they are cheap) and a menu for users to add regular NTP updates as per their own schedule?
@skywatch I think it is better to add RTC on your RPI and ask RPI to update the clock from the RTC. This could be a universal solution.
If you have more than one RPI, you can configure an NTP server on an RPI (an RPI that has RTC) and ask other RPI to get update from that RPI via NTP.
@jkandasa Thanks, I understand but was thinking that to make it simple for users in 2.0 an entry in settings with a checkbox for RTC attached and then a 'timer style' option for frequency of update and then say 2 boxes to enter the NTP wervers to try and update from.
This way user only need to get RTC connected and recognised by pi and all the rest is taken care of in MyController....
I also see that GPS time servers are getting cheaper so another option if 'off grid' accurate time is required.
@skywatch Sure, I will think of a possible option with MC.
@jkandasa Great stuff - another amazing new feature for V2.0!