Re: [weewx-user] Pi Stops Reporting to Wunderground

[Andy Harrold]

Hi, added the change from Hardware to Software, and I've also updated Weewx 
to 3.6.1. Thanks for your help :-)


On Thursday, 3 November 2016 23:24:14 UTC, gjr80 wrote:
>
> I will preface this up front that I am not a TE923 user but I think the 
> use of hardware record generation may be contributing to the problem... 
> reading the TE923  
> section in the Hardware Guide  I see 
> that it says 
>
> The TE923 driver will read history records from the station when weewx 
>> starts up, but it does not support hardware record generation.
>
>
> But in the weewx.conf you posted you have told weewx to use hardware 
> record generation:
>
> [StdArchive]
>> 
>> # If the station hardware supports data logging then the archive 
>> interval
>> # will be downloaded from the station. Otherwise, specify it (in 
>> seconds).
>> archive_interval = 300
>> 
>> # How long to wait (in seconds) before processing new archive data. 
>> Must
>> # be greater than zero.
>> archive_delay = 15
>> 
>> # If possible, new archive records are downloaded from the station
>> # hardware. If the hardware does not support this, then new archive
>> # records will be generated in software.
>> # Set the following to "software" to force software record generation.
>> record_generation = hardware
>> 
>> # Whether to include LOOP data in hi/low statistics
>> loop_hilo = True
>> 
>> # The data binding used to save archive records
>> data_binding = wx_binding
>>
>
> I am not sure of the exact impact this would have on weewx. But I suspect 
> it would have some difficulty in producing an archive record and the 
> archive record is what is stored in your archive and the WU updater will be 
> looking at the archive record for updating WU. I could certainly see this 
> causing problems for updating WU. If you have a look at a log extract you 
> posted early on there are long periods of time when no actual archive 
> record is produced and saved to the database.
>
> My suggestion is to:
>
>1. stop weewx
>2. set record_generation = software in weewx.conf [StdArchive]
>3. set debug = 1 in weewx.conf
>4. clear the TE923 memory using wee_device (refer to the TE923 
> section in the Hardware 
>Guide )
>5. start weewx
>6. monitor the logs/WU and see how that goes. If posts to WU fail 
>again, post the log from weewx startup until the failure.
>
> To make reading the logs a bit easier you might want to consider setting 
> your system to use a separate log file for weewx. The steps are quite 
> simple and are described in the weewx wiki here 
>  (if you do implement this 
> make sure you setup the logrotate part as well).
>
>
> Gary
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Pi Stops Reporting to Wunderground

[Andy Harrold]

Now updated to latest version, though I had updated the TE923 driver 
previously. Lets see what happens. Thanks for your help :-)

On Friday, 4 November 2016 00:19:07 UTC, mwall wrote:
>
> On Thursday, November 3, 2016 at 5:41:30 AM UTC-4, Andy Harrold wrote:
>>
>> Ive now purchase a new USB Hub with a 2A power supply. Unfortunately it 
>> hasn't fixed the problem. 
>>
>
> andy,
>
> please update to weewx 3.6.1, or replace your te923.py driver with the 
> te923.py driver from weewx 3.6.1
>
> there were significant changes to the te923 driver between weewx 3.5.0 and 
> weewx 3.6
>
> m 
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Pi Stops Reporting to Wunderground

[mwall]

On Thursday, November 3, 2016 at 5:41:30 AM UTC-4, Andy Harrold wrote:
>
> Ive now purchase a new USB Hub with a 2A power supply. Unfortunately it 
> hasn't fixed the problem. 
>

andy,

please update to weewx 3.6.1, or replace your te923.py driver with the 
te923.py driver from weewx 3.6.1

there were significant changes to the te923 driver between weewx 3.5.0 and 
weewx 3.6

m 

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Pi Stops Reporting to Wunderground

[gjr80]

weewx.conf will do for now. Just for the record its included in your 
/usr/share/weewx or /home/weewx/bin directory (depending on your install 
type) since weewx 3.3.0/3.4.0 and it's use is detailed here 
 in the Utilities 
Guide .

Gary

On Friday, 4 November 2016 08:13:35 UTC+10, Andy Harrold wrote:
>
> Where do I find the wee_debug report?
>
> On Thursday, 3 November 2016 10:50:21 UTC, gjr80 wrote:
>>
>> It's also hard to see exactly what your (weewx) config is. When posting 
>> the log Andrew asked for could you please post asanitised weewx.conf or a 
>> wee_debug report.
>>
>> Gary
>>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Pi Stops Reporting to Wunderground

[gjr80]

It's also hard to see exactly what your (weewx) config is. When posting the log 
Andrew asked for could you please post asanitised weewx.conf or a wee_debug 
report.

Gary

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Pi Stops Reporting to Wunderground

[Andrew Milner]

Is the 2A supply powering the hub or the pi?

since it is some time since your original post - can you post a section of 
log which highlights the problem now.

I had a problem with debian wheezy and an rpi2 B which after running \ok 
for a few years suddenly started to just stop and no errors in logs or 
anything - it just ceased processing altogether and the first I knew was an 
email from wunderground!!  Have replaced it with an rpi3 and debian Jessie 
and so far, touch wood, all is ok again.  I have not yet started really 
investigating what actually was going wrong - I had several theories which 
were disproved one by one until swapping the pi seemed the only option.  I 
don't know if it was debian, weewx, my hdd or what - but I think it was not 
weewx (since Jessie seems to be running fine)





On Thursday, 3 November 2016 11:41:30 UTC+2, Andy Harrold wrote:

> Ive now purchase a new USB Hub with a 2A power supply. Unfortunately it 
> hasn't fixed the problem. 
>
> On Sunday, 2 October 2016 01:41:04 UTC+1, Andrew Milner wrote:
>>
>> 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 0x4c
> 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 0x4c
> 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 0x4c
> 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-2098.usb-1.2.1.2/input0
> Sep 28 19:07:33 raspberrypi mtp-probe: checking bus 1, device 9: 
> "/sys/devices/platform/soc/2098.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 

Re: [weewx-user] Pi Stops Reporting to Wunderground

[Andy Harrold]

Ive now purchase a new USB Hub with a 2A power supply. Unfortunately it 
hasn't fixed the problem. 

On Sunday, 2 October 2016 01:41:04 UTC+1, Andrew Milner wrote:
>
> 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 0x4c
 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 0x4c
 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 0x4c
 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-2098.usb-1.2.1.2/input0
 Sep 28 19:07:33 raspberrypi mtp-probe: checking bus 1, device 9: 
 "/sys/devices/platform/soc/2098.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 
 

Re: [weewx-user] Pi Stops Reporting to Wunderground

[Andrew Milner]

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 0x4c
>>> 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 0x4c
>>> 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 0x4c
>>> 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-2098.usb-1.2.1.2/input0
>>> Sep 28 19:07:33 raspberrypi mtp-probe: checking bus 1, device 9: 
>>> "/sys/devices/platform/soc/2098.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 

Re: [weewx-user] Pi Stops Reporting to Wunderground

[Andy Harrold]

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 0x4c
>> 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 0x4c
>> 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 0x4c
>> 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-2098.usb-1.2.1.2/input0
>> Sep 28 19:07:33 raspberrypi mtp-probe: checking bus 1, device 9: 
>> "/sys/devices/platform/soc/2098.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]:   

Re: [weewx-user] Pi Stops Reporting to Wunderground

[Andrew Milner]

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 0x4c
> 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 0x4c
> 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 0x4c
> 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-2098.usb-1.2.1.2/input0
> Sep 28 19:07:33 raspberrypi mtp-probe: checking bus 1, device 9: 
> "/sys/devices/platform/soc/2098.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 

Re: [weewx-user] Pi Stops Reporting to Wunderground

[Andy Harrold]

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 0x4c
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 0x4c
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 0x4c
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-2098.usb-1.2.1.2/input0
Sep 28 19:07:33 raspberrypi mtp-probe: checking bus 1, device 9: 
"/sys/devices/platform/soc/2098.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', 

Re: [weewx-user] Pi Stops Reporting to Wunderground

[Andrew Milner]

There are plenty of threads on clocks and the rpi, as well as notes in the 
user guide!!

On Sunday, 25 September 2016 13:35:53 UTC+3, Andy Harrold 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 
>>> .
>>>
>>> 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 <
>>> aberdeengarden...@gmail.com> 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 weewx-user+...@googlegroups.com.
 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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.