Try a 1.5A or 2A supply and see if it helps.
On Saturday, 1 October 2016 23:06:05 UTC+3, Andy Harrold wrote: > Hi. > > 1. Using a powered USB Hub > 2. 5v 1.0amp > > On Saturday, 1 October 2016 12:45:38 UTC+1, Andrew Milner wrote: >> >> 1. Are you using a powered usb hub (recommended) or the usb ports on the >> RPi itself? >> 2. What size power supply are you using? >> >> RPis can be quite critical and finicky concerning both. >> >> Your problem would appear to be a basic usb issue though, and the >> wunderground loss etc are mere by-products of a device communication >> failure. >> >> >> >> >> >> On Saturday, 1 October 2016 14:40:00 UTC+3, Andy Harrold wrote: >> >>> Hi, >>> Managed to find a log of a failure. >>> >>> Sep 28 19:07:05 raspberrypi weewx[2083]: te923: read: address 0x020001 >>> Sep 28 19:07:05 raspberrypi weewx[2083]: te923: read: 5a 81 a1 70 aa 0a >>> aa aa 0a aa aa 0a aa 52 c1 08 aa 0a aa ff ff 9d 3d 03 ee ee ee ee ee ee 07 >>> ee 00 db >>> Sep 28 19:07:05 raspberrypi weewx[2083]: te923: read: address 0x00004c >>> Sep 28 19:07:05 raspberrypi weewx[2083]: te923: read: 5a 7f ff ff ff ff >>> ff ff ff ff ff ff ff ff 10 c6 00 07 33 ff ff 39 28 18 22 98 3d 98 3d c0 3d >>> d5 3d f9 >>> Sep 28 19:07:15 raspberrypi weewx[2083]: te923: read: address 0x020001 >>> Sep 28 19:07:16 raspberrypi weewx[2083]: te923: read: 5a 81 a1 70 aa 0a >>> aa aa 0a aa aa 0a aa 52 c1 08 aa 0a aa ff ff 9d 3d 03 ee ee ee ee ee ee 07 >>> ee 00 db >>> Sep 28 19:07:16 raspberrypi weewx[2083]: te923: read: address 0x00004c >>> Sep 28 19:07:16 raspberrypi weewx[2083]: te923: read: 5a 7f ff ff ff ff >>> ff ff ff ff ff ff ff ff 10 c6 00 07 33 ff ff 39 28 18 22 98 3d 98 3d c0 3d >>> d5 3d f9 >>> Sep 28 19:07:26 raspberrypi weewx[2083]: te923: read: address 0x020001 >>> Sep 28 19:07:26 raspberrypi weewx[2083]: te923: read: 5a 81 a1 70 aa 0a >>> aa aa 0a aa aa 0a aa 52 c1 08 aa 0a aa ff ff 9d 3d 03 ee ee ee ee ee ee 07 >>> ee 00 db >>> Sep 28 19:07:26 raspberrypi weewx[2083]: te923: read: address 0x00004c >>> Sep 28 19:07:26 raspberrypi weewx[2083]: te923: read: 5a 7f ff ff ff ff >>> ff ff ff ff ff ff ff ff 10 c6 00 07 33 ff ff 39 28 18 22 98 3d 98 3d c0 3d >>> d5 3d f9 >>> Sep 28 19:07:33 raspberrypi kernel: [87218.944317] usb 1-1.2.1.2: USB >>> disconnect, device number 8 >>> Sep 28 19:07:33 raspberrypi rsyslogd-2007: action 'action 17' suspended, >>> next retry is Wed Sep 28 19:09:03 2016 [try >>> http://www.rsyslog.com/e/2007 ] >>> Sep 28 19:07:33 raspberrypi kernel: [87219.193350] usb 1-1.2.1.2: new >>> low-speed USB device number 9 using dwc_otg >>> Sep 28 19:07:33 raspberrypi kernel: [87219.299415] usb 1-1.2.1.2: New >>> USB device found, idVendor=1130, idProduct=6801 >>> Sep 28 19:07:33 raspberrypi kernel: [87219.299456] usb 1-1.2.1.2: New >>> USB device strings: Mfr=0, Product=1, SerialNumber=0 >>> Sep 28 19:07:33 raspberrypi kernel: [87219.299479] usb 1-1.2.1.2: >>> Product: >>> Sep 28 19:07:33 raspberrypi kernel: [87219.318477] hid-generic >>> 0003:1130:6801.0002: hiddev0,hidraw0: USB HID v1.10 Device [ ] on >>> usb-20980000.usb-1.2.1.2/input0 >>> Sep 28 19:07:33 raspberrypi mtp-probe: checking bus 1, device 9: >>> "/sys/devices/platform/soc/20980000.usb/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1.2" >>> Sep 28 19:07:33 raspberrypi mtp-probe: bus: 1, device: 9 was not an MTP >>> device >>> Sep 28 19:07:36 raspberrypi weewx[2083]: te923: read: address 0x020001 >>> Sep 28 19:07:36 raspberrypi weewx[2083]: te923: Failed attempt 1 of 5 to >>> read data: error sending control message: No such device >>> Sep 28 19:07:36 raspberrypi weewx[2083]: te923: Waiting 3 seconds before >>> retry >>> Sep 28 19:07:39 raspberrypi weewx[2083]: te923: Failed attempt 2 of 5 to >>> read data: error sending control message: No such device >>> Sep 28 19:07:39 raspberrypi weewx[2083]: te923: Waiting 3 seconds before >>> retry >>> Sep 28 19:07:42 raspberrypi weewx[2083]: te923: Failed attempt 3 of 5 to >>> read data: error sending control message: No such device >>> Sep 28 19:07:42 raspberrypi weewx[2083]: te923: Waiting 3 seconds before >>> retry >>> Sep 28 19:07:45 raspberrypi weewx[2083]: te923: Failed attempt 4 of 5 to >>> read data: error sending control message: No such device >>> Sep 28 19:07:45 raspberrypi weewx[2083]: te923: Waiting 3 seconds before >>> retry >>> Sep 28 19:07:48 raspberrypi weewx[2083]: te923: Failed attempt 5 of 5 to >>> read data: error sending control message: No such device >>> Sep 28 19:07:48 raspberrypi weewx[2083]: te923: Waiting 3 seconds before >>> retry >>> Sep 28 19:07:51 raspberrypi weewx[2083]: engine: Main loop exiting. >>> Shutting engine down. >>> Sep 28 19:07:51 raspberrypi weewx[2083]: engine: Shutting down StdReport >>> thread >>> Sep 28 19:07:51 raspberrypi weewx[2083]: engine: StdReport thread has >>> been terminated >>> Sep 28 19:07:51 raspberrypi weewx[2083]: restx: Shut down >>> Wunderground-PWS thread. >>> Sep 28 19:07:51 raspberrypi weewx[2083]: te923: release interface >>> failed: could not release intf 0: No such device >>> Sep 28 19:07:51 raspberrypi weewx[2083]: engine: Caught WeeWxIOError: >>> Read failed after 5 tries >>> Sep 28 19:07:51 raspberrypi weewx[2083]: **** Waiting 60 seconds >>> then retrying... >>> Sep 28 19:08:52 raspberrypi weewx[2083]: engine: retrying... >>> Sep 28 19:08:52 raspberrypi weewx[2083]: engine: Using configuration >>> file /etc/weewx/weewx.conf >>> Sep 28 19:08:52 raspberrypi weewx[2083]: engine: Initializing engine >>> Sep 28 19:08:52 raspberrypi weewx[2083]: engine: Loading station type >>> TE923 (weewx.drivers.te923) >>> Sep 28 19:08:52 raspberrypi weewx[2083]: te923: driver version is 0.19 >>> Sep 28 19:08:52 raspberrypi weewx[2083]: te923: polling interval is 10 >>> Sep 28 19:08:52 raspberrypi weewx[2083]: te923: observation map is >>> {'bat_1': 'outBatteryStatus', 'bat_3': 'extraBatteryStatus2', 'bat_2': >>> 'extraBatteryStatus1', 'bat_5': 'extraBatteryStatus4', 'bat_4': >>> 'extraBatteryStatus3', 'bat_wind': 'windBatteryStatus', 't_in': 'inTemp', >>> 'link_rain': 'rainLinkStatus', 't_1': 'extraTemp4', 'h_in': 'inHumidity', >>> 'h_3': 'extraHumid3', 'h_1': 'extraHumid4', 'h_5': 'extraHumid1', 'h_2': >>> 'extraHumid3', 'h_4': 'outHumidity', 't_5': 'extraTemp1', 'link_2': >>> 'extraLinkStatus1', 'link_uv': 'uvLinkStatus', 'link_wind': >>> 'windLinkStatus', 'uv': 'UV', 'bat_uv': 'uvBatteryStatus', 'link_5': >>> 'extraLinkStatus4', 'bat_rain': 'rainBatteryStatus', 'link_3': >>> 'extraLinkStatus2', 't_2': 'extraTemp2', 'link_1': 'outLinkStatus', 't_4': >>> 'outTemp', 't_3': 'extraTemp3', 'link_4': 'extraLinkStatus3'} >>> Sep 28 19:08:52 raspberrypi weewx[2083]: te923: Found device on USB >>> bus=001 device=009 >>> Sep 28 19:08:52 raspberrypi weewx[2083]: te923: read: address 0x0000fc >>> Sep 28 19:08:53 raspberrypi weewx[2083]: engine: Unable to load driver: >>> could not release intf 0: No such device >>> Sep 28 19:08:53 raspberrypi weewx[2083]: **** Exiting... >>> Sep 28 19:09:27 raspberrypi systemd[1]: Starting Cleanup of Temporary >>> Directories... >>> Sep 28 19:09:27 raspberrypi rsyslogd-2007: action 'action 17' suspended, >>> next retry is Wed Sep 28 19:10:57 2016 [try >>> http://www.rsyslog.com/e/2007 ] >>> Sep 28 19:09:27 raspberrypi systemd[1]: Started Cleanup of Temporary >>> Directories. >>> Sep 28 19:17:01 raspberrypi rsyslogd-2007: action 'action 17' suspended, >>> next retry is Wed Sep 28 19:18:31 2016 [try >>> http://www.rsyslog.com/e/2007 ] >>> Sep 28 19:17:01 raspberrypi CRON[8801]: (root) CMD ( cd / && run-parts >>> --report /etc/cron.hourly) >>> Sep 28 19:50:38 raspberrypi dhcpcd[408]: wlan0: carrier lost >>> Sep 28 19:50:38 raspberrypi rsyslogd-2007: action 'action 17' suspended, >>> next retry is Wed Sep 28 19:52:08 2016 [try >>> http://www.rsyslog.com/e/2007 ] >>> Sep 28 19:50:38 raspberrypi wpa_supplicant[501]: wlan0: >>> CTRL-EVENT-DISCONNECTED bssid=74:da:38:1c:20:f4 reason=4 locally_generated=1 >>> Sep 28 19:50:38 raspberrypi kernel: [89804.507825] cfg80211: World >>> regulatory domain updated: >>> Sep 28 19:50:38 raspberrypi kernel: [89804.507870] cfg80211: DFS Master >>> region: unset >>> >>> >>> >>> >>> >>> On Sunday, 25 September 2016 14:03:43 UTC+1, Tom Keffer wrote: >>>> >>>> Weewx versions 3.4 and later have included a delay to wait until the >>>> system clock shows a time after 1 Jan 2000. >>>> >>>> If you are still having problems, a log snippet would be helpful. >>>> >>>> -tk >>>> >>>> On Sun, Sep 25, 2016 at 3:35 AM, Andy Harrold < >>>> [email protected]> wrote: >>>> >>>>> Ok, Weewx run for a lot longer this time around and appears to have >>>>> been an issue with Fake Clock. >>>>> Next time Wunderground reported losing connection to my weather >>>>> station I checked the logs. Seems something had caused a reboot of my Pi >>>>> and as advised above when it restarted the date/time reverted back to >>>>> 1970. >>>>> Not sure if weewx tried to start up during this system time but it still >>>>> failed to report to wunderground even after the date/time sorted itself. >>>>> Maybe I need the weewx to delay its startup until the date/time has fixed >>>>> itself after reboot. Whats your opinion? >>>>> >>>>> >>>>> On Wednesday, 21 September 2016 22:20:12 UTC+1, Andy Harrold wrote: >>>>>> >>>>>> Thanks. Have removed the Fake Clock and associated data. Will >>>>>> stop/Start Weewx and see what happens. >>>>>> >>>>>> On Wednesday, 21 September 2016 16:43:32 UTC+1, Tom Keffer wrote: >>>>>>> >>>>>>> Looks like your RPi decided to reboot itself for some reason. >>>>>>> >>>>>>> One problem is that weewx is starting up before the system clock is >>>>>>> being set by NTP. You should remove module fake-hwclock. See the Wiki >>>>>>> Running weewx on a Raspberry Pi >>>>>>> <https://github.com/weewx/weewx/wiki/Raspberry%20Pi>. >>>>>>> >>>>>>> In any case, for whatever reason, weewx was unable to load the >>>>>>> driver. This could be related to the clock problem, but I doubt it. Fix >>>>>>> the >>>>>>> clock problem and then see what happens. >>>>>>> >>>>>>> -tk >>>>>>> >>>>>>> On Wed, Sep 21, 2016 at 8:06 AM, Andy Harrold < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> After finally getting my system up and running I keep getting >>>>>>>> notifications from Wunderground that my system has stopped reporting. >>>>>>>> A quick stop and start of the Weewx service sorts that out until >>>>>>>> the next time, usually happens around 2-3 times a day. >>>>>>>> I set Debug on today and looking at the Syslog & Debug log >>>>>>>> everything seems to go haywire around 13:16. >>>>>>>> >>>>>>>> I've attached the Syslog & Debug file, if you want me to just cut & >>>>>>>> Paste in here I can, just ask. >>>>>>>> >>>>>>>> I think it might have something to do with my wireless, or maybe >>>>>>>> the USB interface. >>>>>>>> >>>>>>>> Thanks >>>>>>>> Andy >>>>>>>> >>>>>>>> -- >>>>>>>> You received this message because you are subscribed to the Google >>>>>>>> Groups "weewx-user" group. >>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>> send an email to [email protected]. >>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>> >>>>>>> >>>>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "weewx-user" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
