Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ntpserver2 is locked to nl.pool.ntp.org #3392

Closed
2 tasks done
jcheger opened this issue Aug 2, 2018 · 4 comments
Closed
2 tasks done

ntpserver2 is locked to nl.pool.ntp.org #3392

jcheger opened this issue Aug 2, 2018 · 4 comments
Labels
bug Type - Confirmated Bug fixed Result - The work on the issue has ended workaround Result - The work on the issue has ended with an alternative solution

Comments

@jcheger
Copy link

jcheger commented Aug 2, 2018

ntpserver2 cannot be changed, it is locked to nl.pool.ntp.org

NtpServer(1) and NtpServer3 let change the settings, but not NtpServer2

  • Searched the problem in issues and in the wiki
  • Hardware used : Sonoff POW
  • FW versions: 6.1.0, 6.1.1
ntpserver1 0.ch.pool.ntp.org
.../stat/RESULT = {"NtpServer1":"0.ch.pool.ntp.org"}
ntpserver2 1.ch.pool.ntp.org
.../stat/RESULT = {"NtpServer2":"nl.pool.ntp.org"}
ntpserver3 2.ch.pool.ntp.org
.../stat/RESULT = {"NtpServer3":"2.ch.pool.ntp.org"}```

To Reproduce

 ntpserver2 1.ch.pool.ntp.org
@arendst
Copy link
Owner

arendst commented Aug 2, 2018

Ah, that's not a bug but a feature....

If the ntp server starts with a "1" the software detects it as using the default ntp server from user_config.h

I guess a valid ntp server in Switzerland is also "ch.pool.ntp.org" so without the "1".

@arendst arendst added the workaround Result - The work on the issue has ended with an alternative solution label Aug 2, 2018
@jcheger
Copy link
Author

jcheger commented Aug 2, 2018

Ok, you are right. Without starting with « 1 », the server is set.

npserver2 ch.pool.ntp.org
.../stat/RESULT = {"NtpServer2":"ch.pool.ntp.org"}

Thanks for your answer

@jcheger jcheger closed this as completed Aug 2, 2018
arendst added a commit that referenced this issue Aug 27, 2018
Fix handling use of default names when using names starting with shortcut character (#3392, #3600)
@arendst
Copy link
Owner

arendst commented Aug 27, 2018

v6.1.1.12 allows the use of a 1 as start of server name.

@arendst arendst added bug Type - Confirmated Bug fixed Result - The work on the issue has ended labels Aug 27, 2018
@jcheger
Copy link
Author

jcheger commented Aug 27, 2018

oh, nice ! Thank you.

curzon01 pushed a commit to curzon01/Tasmota that referenced this issue Sep 7, 2018
Fix handling use of default names when using names starting with shortcut character (arendst#3392, arendst#3600)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Type - Confirmated Bug fixed Result - The work on the issue has ended workaround Result - The work on the issue has ended with an alternative solution
Projects
None yet
Development

No branches or pull requests

2 participants