Does the time need to be set after every startup?


 
T

TomGerhard

New member
Hi,

Every time I start up my HM the time is wrong. When I go to Configuration > System > System and click "Sync with browser" and then "Save & Apply" the time is correct.

Under NTP server candidates I have the default 0.openwrt.pool.ntp.org through 3.openwrt.pool.ntp.org.

I have tried with "Enable NTP client" checked and also with "Provide NTP server" checked but get the same result. Is this expected or should the time be set from some time server automatically when starting up and I am doing something wrong?

Thanks,
Tom
 
The time zone isn't important, but what is important is that your HeaterMeter can get to the internet so it can update its clock. If you go to Network -> Diagnostics and enter "0.openwrt.pool.ntp.org" into the ping field and hit the button, it should come back like this:
Code: 
PING 0.openwrt.pool.ntp.org (199.7.177.206): 56 data bytes
64 bytes from 199.7.177.206: seq=0 ttl=58 time=43.499 ms
64 bytes from 199.7.177.206: seq=1 ttl=58 time=43.180 ms
64 bytes from 199.7.177.206: seq=2 ttl=58 time=42.828 ms
64 bytes from 199.7.177.206: seq=3 ttl=58 time=42.771 ms
64 bytes from 199.7.177.206: seq=4 ttl=58 time=42.359 ms

--- 0.openwrt.pool.ntp.org ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 42.359/42.927/43.499 ms

If it fails, check your network configuration. I've never tried the "provide NTP server" option, but "Enable NTP client" should definitely be checked.
 
Bryan Mayland said:
The time zone isn't important, but what is important is that your HeaterMeter can get to the internet so it can update its clock. If you go to Network -> Diagnostics and enter "0.openwrt.pool.ntp.org" into the ping field and hit the button, it should come back like this:
Code: 
PING 0.openwrt.pool.ntp.org (199.7.177.206): 56 data bytes
64 bytes from 199.7.177.206: seq=0 ttl=58 time=43.499 ms
64 bytes from 199.7.177.206: seq=1 ttl=58 time=43.180 ms
64 bytes from 199.7.177.206: seq=2 ttl=58 time=42.828 ms
64 bytes from 199.7.177.206: seq=3 ttl=58 time=42.771 ms
64 bytes from 199.7.177.206: seq=4 ttl=58 time=42.359 ms

--- 0.openwrt.pool.ntp.org ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 42.359/42.927/43.499 ms

If it fails, check your network configuration. I've never tried the "provide NTP server" option, but "Enable NTP client" should definitely be checked.
Click to expand...

This doesn't work. I can get to my HM from outside my network though (tried from my phone while not on wi-fi as well as from work), doesn't that mean that it has access to the internet? When clicking the ping button it returns "ping: bad address '0.openwrt.pool.ntp.org'" .

Any idea on how I can fix this? I am using a static IP address on my HM, have changed the listening port to 8095 and have that port forwarded to the HM's IP address in my router.
 
If it says "bad address" that means you need to configure your DNS on the HeaterMeter to point to (most likely) your router.
 
You must log in or register to reply here.

 

Back
Top