Since I upgraded to 2.0 I have 2 issues.
1.) My TE923 is displaying 29.94 in for the barometric pressure. The dashboard within meteohub is showing 29 with no decimal points. BUT, it is sending 30.55 to Weather Underground.
2> The clock sync is showing to be stopped.
Time Synchonization: stopped
Any ideas???
THANKS!!!!!!!!!!!!
Version 2.0
Moderator: Mattk
Re:Version 2.0
1) WU needs sea level pressure. Meteohub takes the station pressure as reported by the te-923 and computes sea level pressure from this based on the height as told on the settings page.
2) The dashboard shows no 1/10 and 1/100 for pressure. This is ok for hPa but does not make sense for the non-metric units. I will change this in the next release.
3) Update 2.0 does nothing new to the NTPD. Please try a restart. When the problem is still there, please have a look at the NTP log file to get a clue what is going wrong.
2) The dashboard shows no 1/10 and 1/100 for pressure. This is ok for hPa but does not make sense for the non-metric units. I will change this in the next release.
3) Update 2.0 does nothing new to the NTPD. Please try a restart. When the problem is still there, please have a look at the NTP log file to get a clue what is going wrong.
Re:Version 2.0
It seems to think the time is off to much to adjust for sync. However the time is the exact as the atomic clock time.
after reboot:
16 Feb 18:48:46 ntpd[1555]: synchronized to 192.53.103.104, stratum 1
16 Feb 18:48:46 ntpd[1555]: time correction of 5433 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time.
Before 2.0 upgrade:
14 Feb 19:09:59 ntpd[1557]: synchronized to 192.53.103.104, stratum 1
14 Feb 19:15:15 ntpd[1557]: synchronized to 192.53.103.108, stratum 1
14 Feb 19:39:13 ntpd[1557]: synchronized to 192.53.103.104, stratum 1
14 Feb 20:47:35 ntpd[1557]: synchronized to 192.53.103.108, stratum 1
14 Feb 21:27:55 ntpd[1557]: synchronized to 192.53.103.104, stratum 1
14 Feb 22:13:11 ntpd[1557]: synchronized to 192.53.103.108, stratum 1
after reboot:
16 Feb 18:48:46 ntpd[1555]: synchronized to 192.53.103.104, stratum 1
16 Feb 18:48:46 ntpd[1555]: time correction of 5433 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time.
Before 2.0 upgrade:
14 Feb 19:09:59 ntpd[1557]: synchronized to 192.53.103.104, stratum 1
14 Feb 19:15:15 ntpd[1557]: synchronized to 192.53.103.108, stratum 1
14 Feb 19:39:13 ntpd[1557]: synchronized to 192.53.103.104, stratum 1
14 Feb 20:47:35 ntpd[1557]: synchronized to 192.53.103.108, stratum 1
14 Feb 21:27:55 ntpd[1557]: synchronized to 192.53.103.104, stratum 1
14 Feb 22:13:11 ntpd[1557]: synchronized to 192.53.103.108, stratum 1
Re:Version 2.0
strange...
Can you set the time manually on the \"settings\" page? Is it ok after pressing save and doing a reboot?
There is another user that also has trouble with setting the clock. Unfortunately, I don't have any symptoms like that on my machines...
Do I have a chance to logon on your system? If so, please send me details to \"info(at)meteohub.de\".
Can you set the time manually on the \"settings\" page? Is it ok after pressing save and doing a reboot?
There is another user that also has trouble with setting the clock. Unfortunately, I don't have any symptoms like that on my machines...
Do I have a chance to logon on your system? If so, please send me details to \"info(at)meteohub.de\".
Re:Version 2.0
Yes, I will change the password back to the default.
http://64.91.93.50
I have tried it with the use weather station time and without that ck'd, all seems to be the same.
You can manually change the time, as you have to reset it someimes when it reboots. It loses anywhere from no time to 20 or 30 minutes when you reboot it.
Also tried using time wervers in the US instead of the defaults, no change.
http://64.91.93.50
I have tried it with the use weather station time and without that ck'd, all seems to be the same.
You can manually change the time, as you have to reset it someimes when it reboots. It loses anywhere from no time to 20 or 30 minutes when you reboot it.
Also tried using time wervers in the US instead of the defaults, no change.
Re:Version 2.0
I do try to address this in the next update. Looks like the problem discussed here: http://www.meteohub.de/joomla/index.php ... id=336#336

