Page 1 of 1
No live data after reboot **solved**
Posted: Thu Jan 23, 2014 11:15 pm
by Kanok
Just saw that 2.1 has come out. So I reboot the bridge. After rebooting I no longer have live data from Acurite 1525. Changing the USB port on USB hub or change to another WX station and change back doesn't help. The green check mark is correctly at the station list. Force to reboot with 2.0 give the same result.
meteobridge: MR3020
WX: AcuRite 1525
USB hub: Belkin
Thanks,
Kanok
Re: No live data after reboot
Posted: Fri Jan 24, 2014 1:19 am
by admin
Do you see correct data on "live data" tab?
Can you please provide the log data from "system" tab?
You need to narrow a bit what works and what does not,
and log files are displayed to be consulted when things
don't do as expected. So please share that with us too. Thanks.
Re: No live data after reboot
Posted: Fri Jan 24, 2014 2:53 am
by Kanok
Hi,
I didn't see any live data in the live data tab. This morning it seem to start feeding outdoor sensor while not the pressure sensor indoor. From the log it start logging after "usb hub resetted" system message while pressure sensor is off scale high. I reset the console and now there is not live data again.
I'm not sure what was trigged the "usb hub resetted" because I went to bed already.
Code: Select all
wnetd (24.01.2014 05:13:45): process started.
logger (24.01.2014 05:13:46): Historical data loaded (15 records).
logger (24.01.2014 05:13:46): data logger (version 4.9w, build 3148) started.
logger (24.01.2014 05:13:47): connect station 0 (Acurite 1025 via USB HID).
logger (24.01.2014 05:24:18): child process received timeout signal (14).
logger (24.01.2014 05:24:18): data logger stopped.
logger (24.01.2014 05:24:18): Historical data loaded (15 records).
logger (24.01.2014 05:24:18): data logger (version 4.9w, build 3148) started.
logger (24.01.2014 05:24:19): connect station 0 (Acurite 1025 via USB HID).
logger (24.01.2014 05:34:49): child process received timeout signal (14).
logger (24.01.2014 05:34:49): data logger stopped.
logger (24.01.2014 05:34:49): Historical data loaded (15 records).
logger (24.01.2014 05:34:49): data logger (version 4.9w, build 3148) started.
logger (24.01.2014 05:34:49): connect station 0 (Acurite 1025 via USB HID).
logger (24.01.2014 05:45:19): child process received timeout signal (14).
logger (24.01.2014 05:45:20): usb port resetted.
logger (24.01.2014 05:45:20): data logger stopped.
logger (24.01.2014 05:45:20): Historical data loaded (15 records).
logger (24.01.2014 05:45:20): data logger (version 4.9w, build 3148) started.
logger (24.01.2014 05:45:21): connect station 0 (Acurite 1025 via USB HID).
logger (24.01.2014 05:46:03): Bad thb0(0) sensor data, "pressure x10" (16211) out of range [4000:12000]
logger (24.01.2014 05:46:09): Bad thb0(0) sensor data, "pressure x10" (16211) out of range [4000:12000]
logger (24.01.2014 05:46:19): Bad thb0(0) sensor data, "pressure x10" (16211) out of range [4000:12000]
logger (24.01.2014 05:46:24): Bad thb0(0) sensor data, "pressure x10" (16211) out of range [4000:12000]
logger (24.01.2014 05:46:34): Bad thb0(0) sensor data, "pressure x10" (16211) out of range [4000:12000]
.
.
.
.
logger (24.01.2014 07:29:42): Bad thb0(0) sensor data, "pressure x10" (16785) out of range [4000:12000]
logger (24.01.2014 07:29:47): Bad thb0(0) sensor data, "pressure x10" (16785) out of range [4000:12000]
logger (24.01.2014 07:29:57): Bad thb0(0) sensor data, "pressure x10" (16785) out of range [4000:12000]
logger (24.01.2014 07:31:07): child process received update persist db signal (17).
logger (24.01.2014 07:31:07): parent process received update persist db signal (17).
logger (24.01.2014 07:31:07): update meteobridge configuration data
logger (24.01.2014 07:42:24): child process received timeout signal (14).
logger (24.01.2014 07:42:24): data logger stopped.
logger (24.01.2014 07:42:24): Historical data loaded (15 records).
logger (24.01.2014 07:42:24): data logger (version 4.9w, build 3148) started.
logger (24.01.2014 07:42:25): connect station 0 (Acurite 1025 via USB HID).
Re: No live data after reboot
Posted: Fri Jan 24, 2014 10:30 am
by admin
please send MAC of your Meteobridge to "info(at)meteobridge.com".
Re: No live data after reboot
Posted: Fri Jan 24, 2014 7:51 pm
by Kanok
MAC is emailed. Now I've got only data from 5in1 sensor. The indoor data is missing. Perhaps the console is defected. Strange the it works fine before the reboot.
Kanok
Re: No live data after reboot
Posted: Sat Jan 25, 2014 2:52 am
by admin
please reboot Meteobridge again. ssh tunnel did not show up.
Re: No live data after reboot
Posted: Sat Jan 25, 2014 5:46 am
by Kanok
Rebooted.
Re: No live data after reboot
Posted: Sat Jan 25, 2014 6:59 pm
by admin
Pressure reading on the Acurite goes completely wild... not idea right now why.
Re: No live data after reboot
Posted: Sun Jan 26, 2014 2:37 am
by admin
Looks like Acurite station is very picky with battery status. Did you try running it on AC?
Re: No live data after reboot
Posted: Tue Feb 18, 2014 12:50 am
by dchamberlain
My Acurite 01035 exhibited the same issue following a reboot today. It took me well over an hour to finally get it working again....which was basically unplugging and re-plugging, resetting usb settings on acurite, forcing datalogger resets by choosing other stations, rebooting the device. In the end, I have no idea what worked as it just decided to start gathering the data again.
logger (17.02.2014 16:06:46): Historical data loaded (15 records).
logger (17.02.2014 16:06:46): data logger (version 4.9w, build 3284) started.
logger (17.02.2014 16:06:47): connect station 0 (Acurite 1025 via USB HID).
logger (17.02.2014 16:18:46): child process received timeout signal (14).
logger (17.02.2014 16:18:46): data logger stopped.
logger (17.02.2014 16:18:46): Historical data loaded (15 records).
logger (17.02.2014 16:18:46): data logger (version 4.9w, build 3284) started.
logger (17.02.2014 16:18:47): connect station 0 (Acurite 1025 via USB HID).
logger (17.02.2014 16:29:17): child process received timeout signal (14).
logger (17.02.2014 16:29:17): disconnect station 0 (Acurite 1025): exit
logger (17.02.2014 16:29:17): data logger stopped.
logger (17.02.2014 16:29:17): Historical data loaded (15 records).
logger (17.02.2014 16:29:17): data logger (version 4.9w, build 3284) started.
logger (17.02.2014 16:29:18): connect station 0 (Acurite 1025 via USB HID).
logger (17.02.2014 16:39:48): child process received timeout signal (14).
logger (17.02.2014 16:39:49): usb port resetted.
logger (17.02.2014 16:39:49): data logger stopped.
logger (17.02.2014 16:39:49): Historical data loaded (15 records).
logger (17.02.2014 16:39:49): data logger (version 4.9w, build 3284) started.
logger (17.02.2014 16:39:51): connect station 0 (Acurite 1025 via USB HID).
logger (17.02.2014 16:50:21): child process received timeout signal (14).
logger (17.02.2014 16:50:21): data logger stopped.
logger (17.02.2014 16:50:21): Historical data loaded (15 records).
logger (17.02.2014 16:50:21): data logger (version 4.9w, build 3284) started.
logger (17.02.2014 16:50:22): connect station 0 (Acurite 1025 via USB HID).
Re: No live data after reboot
Posted: Sat Mar 01, 2014 5:34 pm
by Kanok
Yes, looks like meteobridge and AcuRite is very picky. It runs fine for 3 days and when I set the pressure offset and save which reload the data logger. I've go no realtime data. Unplug and replug usb and reboot several time make it works again.
But when I plug to my PC USB and use PC Connect SW, the VIS Reader get the data from the console fine.
Regards,
Kanok
Re: No live data after reboot
Posted: Tue May 06, 2014 3:05 pm
by Bushman
After 139 days of flawless operation, my MB is no longer getting data from the Nat Geo console. Did the reboot, version up/downgrade and still no luck. Powered on/off and nothing. Guess I will see if batteries in the console are the problem. I really have to get rid of that useless weather station!
Re: No live data after reboot
Posted: Tue May 06, 2014 7:49 pm
by Bushman
Full on power down and removal of batteries from console did the trick. No idea why...
Re: No live data after reboot
Posted: Tue May 06, 2014 8:46 pm
by wvdkuil
Bushman wrote:Full on power down and removal of batteries from console did the trick. No idea why...
Well the console is a computer. So if you leave it on long enough, with even a very minor memory leak, it will fail after a long enough period.
Rule 1: Remove all power, count slowly to ten, apply power again.
And most of the time those annying problems are gone.
For another 139 days?
Wim