Skip to content

UsageConfig - apply saved NTP/DVB time sync setting on startup#4346

Merged
WanWizard merged 1 commit into
OpenPLi:scarthgapfrom
ims21:scarthgap
Jun 27, 2026
Merged

UsageConfig - apply saved NTP/DVB time sync setting on startup#4346
WanWizard merged 1 commit into
OpenPLi:scarthgapfrom
ims21:scarthgap

Conversation

@ims21

@ims21 ims21 commented Jun 27, 2026

Copy link
Copy Markdown
Contributor

timesync notifier was registered with initial_call=False, so saved configuration was not applied after Enigma2 startup until the user changed the setting manually.

timesync notifier was registered with initial_call=False, so saved configuration was not applied after Enigma2 startup until the
user changed the setting manually.
@WanWizard WanWizard merged commit 115641d into OpenPLi:scarthgap Jun 27, 2026
1 check passed
@littlesat

littlesat commented Jun 28, 2026

Copy link
Copy Markdown
Member

I suggest this should be reverted as this is not a solution. See forum

When it is set to 'NTP' and there is no 'NTP' time known (yet) when enigma2 starts-up the time will be in 1970... so recordings/timers do not start. You need to 'fallback' to DVB time in these cases. When enigma2 does start-up and the 'system' already as an appropriate time I'm afraid adding the non initial check was a good idea.

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

Successfully merging this pull request may close these issues.

3 participants