Overview of the Issue
Anthias v0.18.6 image has no way to see the host's current time. As such, there is no way to know what time/date assets need to activate them.
Setting assets to display for "1 day" etc. seems to only use the local time of the guest computer to set the asset start/end times.
There seems to be an assumption that the anthias host will have direct unfiltered internet access constantly and can track the time via NTP using whatever NTP server is added by default, in whatever timezone is set by default.
Requesting the following fixes:
- Display the host's current time in the web interface
- Use the host's local time to calculate asset schedules when using the premade "1 day" etc. instead of the time from the guest machine, as an immediate workaround for systems without the correct time set
- Add the ability to change the host's current time directly in the web interface
- And if possible, add the ability to configure an alternate NTP server (and set the correct timezone) for networks with one locally available
Reproduction Steps
- Apply v0.18.6 image from releases to microSD
- Boot Raspberry pi and leave on anthias splash screen until Anthias WiFi Connect AP is available on another device
- Connect to the AP, manually go to 192.168.42.1 in a browser.
Environment
- Raspberry Pi Hardware Version: 4B
- Raspberry Pi Network Setup: No network connection (wifi connection desired)
- Anthias Version: 0.18.6 pre-release image
Overview of the Issue
Anthias v0.18.6 image has no way to see the host's current time. As such, there is no way to know what time/date assets need to activate them.
Setting assets to display for "1 day" etc. seems to only use the local time of the guest computer to set the asset start/end times.
There seems to be an assumption that the anthias host will have direct unfiltered internet access constantly and can track the time via NTP using whatever NTP server is added by default, in whatever timezone is set by default.
Requesting the following fixes:
Reproduction Steps
Environment