.... or you could just have it routed badly now near some form of 
interference ..

slow down

1.  connect all your hardware
2. stop weewx
3. set debug = 1 in weewx.conf
3. start weewx
4. wait for weewx to get 'missing' archive records from console if there 
are any to retrieve
5.wait for first archive interval to pass (5 or 10 minutes??)

6. post log from start to first interval if you still have problems.

If all is well
edit weewx.conf to turn debug off and restart weewx






On Friday, 16 December 2016 16:40:53 UTC+2, Auchtermuchty Weather wrote:

> I shut down weewx and rebooted the Pi as it occurred to me hot plugging 
> the weather station might be a problem, and then restarted Pi again with 
> 'debug=1'.  It's not finding the weather station:
>
> Dec 16 14:23:02 weather2 systemd[1]: Stopping LSB: weewx weather system...
> Dec 16 14:23:02 weather2 weewx[9448]: Stopping weewx weather system: weewx 
> not running....
> Dec 16 14:23:02 weather2 systemd[1]: Starting LSB: weewx weather system...
> Dec 16 14:23:03 weather2 weewx[9472]: engine: Initializing weewx version 
> 3.6.2
> Dec 16 14:23:03 weather2 weewx[9472]: engine: Using Python 2.7.9 (default, 
> Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
> Dec 16 14:23:03 weather2 weewx[9472]: engine: Platform 
> Linux-4.4.34+-armv6l-with-debian-8.0
> Dec 16 14:23:04 weather2 weewx[9472]: engine: pid file is 
> /var/run/weewx.pid
> Dec 16 14:23:04 weather2 weewx[9462]: Starting weewx weather system: weewx.
> Dec 16 14:23:04 weather2 systemd[1]: Started LSB: weewx weather system.
> Dec 16 14:23:04 weather2 weewx[9476]: engine: Using configuration file 
> /home/weewx/weewx.conf
> Dec 16 14:23:04 weather2 weewx[9476]: engine: Initializing engine
> Dec 16 14:23:04 weather2 weewx[9476]: engine: Loading station type 
> FineOffsetUSB (weewx.drivers.fousb)
> Dec 16 14:23:04 weather2 weewx[9476]: fousb: driver version is 1.9
> Dec 16 14:23:04 weather2 weewx[9476]: fousb: polling mode is PERIODIC
> Dec 16 14:23:04 weather2 weewx[9476]: fousb: polling interval is 60
> Dec 16 14:23:04 weather2 weewx[9476]: fousb: Cannot find USB device with 
> Vendor=0x1941 ProdID=0x8021 Device=None
> Dec 16 14:23:04 weather2 weewx[9476]: import of driver failed: Unable to 
> find USB device (<class 'weewx.WeeWxIOError'>)
> Dec 16 14:23:04 weather2 weewx[9476]: engine: Unable to load driver: 
> Unable to find USB device
> Dec 16 14:23:04 weather2 weewx[9476]:     ****  Exiting...
>
> FineOffset is correct.
>
>
> Fiddling with the cable produced several of these:
> Dec 16 14:27:50 weather2 kernel: [ 1703.009271] usb 1-1.2: new low-speed 
> USB device number 5 using dwc_otg
> Dec 16 14:27:50 weather2 kernel: [ 1703.155425] usb 1-1.2: New USB device 
> found, idVendor=1941, idProduct=8021
> Dec 16 14:27:50 weather2 kernel: [ 1703.155465] usb 1-1.2: New USB device 
> strings: Mfr=0, Product=0, SerialNumber=0
> Dec 16 14:27:50 weather2 kernel: [ 1703.213542] hid-generic 
> 0003:1941:8021.0001: hiddev0,hidraw0: USB HID v1.00 Device [HID 1941:8021] 
> on usb-20980000.usb-1.2/input0
>
> And I have this:
> pi@weather2:/home/weewx $ sudo lsusb
> Bus 001 Device 004: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless 
> Adapter
> Bus 001 Device 008: ID 1941:8021 Dream Link WH1080 Weather Station / USB 
> Missile Launcher
> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
> Fast Ethernet Adapter
> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> Restarted weewx, the tail of syslog:
> 021] on usb-20980000.usb-1.2/input0
> Dec 16 14:30:38 weather2 systemd[1]: Started LSB: weewx weather system.
> pi@weather2:/home/weewx $ date
> Fri 16 Dec 14:39:06 GMT 2016
> pi@weather2:/home/weewx $
>
>
> Connection problem, having disturbed a cable that was left to it's own 
> devices for 4 years?  New USB cable maybe?
>
>
> On Friday, 16 December 2016 14:15:44 UTC, Tom Keffer wrote:
>
>> Take a look at the "driver" option in weewx.conf and make sure it's 
>> correct. 
>>
>> If that's not the problem, then set debug=1, restart weewx, then follow 
>> Andrew's suggestion of posting more of the log.
>>
>> -tk
>>
>> On Fri, Dec 16, 2016 at 5:57 AM, Auchtermuchty Weather <
>> shunr...@gmail.com> wrote:
>>
>>> I was going to say this should be painless after some experimentation 
>>> and realising I just needed (in outline) to copy over /home/weewx, and 
>>> upgrade with setup.py - that was how I originally installed it, and I 
>>> prefer having everything in one directory.
>>>
>>> However...  Am getting these errors in syslog:
>>>
>>> Dec 16 13:32:12 weather2 weewx[625]: import of driver failed: 'module' 
>>> object has no attribute 'getAltitudeM' (<type exceptions.AttributeError'>)
>>> Dec 16 13:32:12 weather2 weewx[625]: engine: Unable to load driver: 
>>> 'module' object has no attribute 'getAltitudeM'
>>> Dec 16 13:32:12 weather2 weewx[625]:     ****  Exiting...
>>> Dec 16 13:35:34 weather2 rsyslogd-2007: action 'action 17' suspended, 
>>> next retry is Fri Dec 16 13:36:34 2016 [try 
>>> http://www.rsyslog.com/e/2007 ]
>>>
>>> There is no output to /home/weewx/public_html being created - the most 
>>> recent time is before I stopped the old Pi.
>>>
>>> On Friday, 9 December 2016 10:41:37 UTC, Auchtermuchty Weather wrote:
>>>
>>>> I realised that not only am I running an old (2.7) version of Weewx, 
>>>> the RPi it's on is short of room on the SD card - it's an old B model with 
>>>> an SD card.
>>>>
>>>> I had a B+ Pi doing nothing (Micro SD card, 4 USB ports) so I put the 
>>>> latest Raspberrian on an 8GB card and then installed Weewx and it's 
>>>> working 
>>>> fine with the simulator - the HTML files are being produced with correct 
>>>> units & layout.
>>>>
>>>> Not quite sure what the process of changing the two over is though.  I 
>>>> know I will have to copy some stuff across (not a problem as both are on 
>>>> my 
>>>> network), not sure what stuff though.
>>>>
>>>> Nor am I sure if there are any 'gotchas' I need to be aware of.
>>>>
>>>> -- 
>>> 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.

Reply via email to