[weewx-user] Re: 2.6 going to 3.8 and wee_extension

[vigilancewx]

Hi

Yes its a little drastic

But several hours worth of customizing something else may be problematic

Originally i had installed the latest weewx 3.8 using the new automated 
installation package but i was unfamiliar with the new directory structure 
so i un-installed it and used to older setup method

something maybe crossed linked

upon reinstalling everything is working ok (so far) :-)

thanks for your help



On Sunday, February 4, 2018 at 3:56:02 PM UTC, vigilancewx wrote:
>
> Hello I have been using weewx for a few years version 2.6 on a PI and it 
> works fine (changing in and out of GMT causes the pi to play up but thats 
> all)  no problems with the SD cards etc
> However i  decided to install the latest version 3.8 on a machine running 
> Ubuntu 17
>
> I have modified my 2.6 quite extensively so doing a clean install and 
> trying to migrate my mods over if possible
>
> i am unable to get wee_extension to install i have tried on the forecast 
> extension and cmon
>
> i cant remember how to install the extensions from a few years ago  and 
> using wee_extension i get the following errors
>
> Thanks for any help
>
> pi@picomp:/home/myideas$ dir
> abcweewx.tgz  home   weewx-forecast-3.2.19.tgz
> abweewx.tgz   weewx-cmon-0.16.tgz  weewx-owfs-0.21.tgz
> pi@picomp:/home/myideas$ sudo /home/weewx/bin/wee_extension 
> /home/myideas/weewx-cmon-0.16.tgz
> Traceback (most recent call last):
>   File "/home/weewx/bin/wee_extension", line 83, in 
> main()
>   File "/home/weewx/bin/wee_extension", line 62, in main
> config_path, config_dict = weecfg.read_config(options.config, _args)
>   File "/home/weewx/bin/weecfg/__init__.py", line 223, in read_config
> config_dict = configobj.ConfigObj(config_path, file_error=True)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
> __init__
> self._load(infile, configspec)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in _load
> raise error
> configobj.ConfigObjError: Parsing failed with several errors.
> First error at line 1.
> pi@picomp:/home/myideas$ sudo /home/weewx/bin/wee_extension 
> /home/myideas/weewx-forecast-3.2.19.tgz
> Traceback (most recent call last):
>   File "/home/weewx/bin/wee_extension", line 83, in 
> main()
>   File "/home/weewx/bin/wee_extension", line 62, in main
> config_path, config_dict = weecfg.read_config(options.config, _args)
>   File "/home/weewx/bin/weecfg/__init__.py", line 223, in read_config
> config_dict = configobj.ConfigObj(config_path, file_error=True)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
> __init__
> self._load(infile, configspec)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in _load
> raise error
> configobj.ConfigObjError: Parsing failed with several errors.
> First error at line 3.
> pi@picomp:/home/myideas$ 
>

-- 
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] Problema cuando reinicio Raspberry Pi +wmr300

[Andrew Milner]

And you are 100% certain there the data for 2nd and 3rd and 4th is in the 
logger??  

seems very strange!!!  

I can think of no way that weewx could miss just one day of data but get 
the data for the days each side

I am sorry, but I have no more ideas - you will have to wait for matthew or 
someone else to give their opinions and advice or make comments




On Monday, 5 February 2018 08:12:57 UTC+2, Juan Antonio Mosquera wrote:

> Exactly

-- 
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] Problema cuando reinicio Raspberry Pi +wmr300

[Juan Antonio Mosquera]

Exactly

-- 
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] Problema cuando reinicio Raspberry Pi +wmr300

[Andrew Milner]

So are you saying that if you delete data for 2,3,4 feb, delete daily and 
rebuild daily, restart weewx you recover data for 2 and 4 feb but not 3 
feb??



On Sunday, 4 February 2018 21:30:40 UTC+2, Juan Antonio Mosquera wrote:

> Ok,
>
> i deleted all data from 2 Feb (delete data in archive table) and drop  - 
> rebuild and not add data from 3 feb...
>
> thanks.
>
> El domingo, 4 de febrero de 2018, 19:34:15 (UTC+1), Andrew Milner escribió:
>>
>> So what is your problem??  It successfully recovered data records from 
>> after 1830 on 4 feb until (I assume) 1910 when the main packet loop started.
>>
>> The recovery is only from the last entry in database up to current time - 
>> it will not fill any missing holes - so if there is data in the database 
>> for 1830 on 4 feb that is when recovery will start
>>
>> If you want to get the records for 03 feb you need to delete all data in 
>> database from 02 feb - 04 feb and force weewx to read data from 02 feb to 
>> current time, as i suggested in previous post.
>>
>>
>>
>>
>>
>> On Sunday, 4 February 2018 20:13:11 UTC+2, Juan Antonio Mosquera wrote:
>>
>>> Done.
>>>
>>> No veo errores al iniciar, pero veo esto:
>>>
>>>
>>> eb 04 19:08:18 meteomontaos systemd[1]: Starting LSB: weewx weather 
>>> system...
>>> Feb 04 19:08:20 meteomontaos weewx[17140]: engine: Initializing weewx 
>>> version 3.8.0
>>> Feb 04 19:08:20 meteomontaos weewx[17140]: engine: Using Python 2.7.9 
>>> (default, Sep 17 2016, 20:26:04) 
>>>[GCC 4.9.2]
>>> Feb 04 19:08:20 meteomontaos weewx[17140]: engine: Platform 
>>> Linux-4.4.48+-armv6l-with-debian-8.0
>>> Feb 04 19:08:20 meteomontaos weewx[17140]: engine: Locale is 
>>> 'en_US.UTF-8'
>>> Feb 04 19:08:20 meteomontaos weewx[17140]: engine: pid file is 
>>> /var/run/weewx.pid
>>> Feb 04 19:08:20 meteomontaos weewx[17130]: Starting weewx weather 
>>> system: weewx.
>>> Feb 04 19:08:20 meteomontaos systemd[1]: Started LSB: weewx weather 
>>> system.
>>> Feb 04 19:08:20 meteomontaos sudo[17109]: pam_unix(sudo:session): 
>>> session closed for user root
>>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Using configuration 
>>> file /etc/weewx/weewx.conf
>>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: debug is 1
>>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Initializing engine
>>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Loading station type 
>>> WMR300 (weewx.drivers.wmr300)
>>> Feb 04 19:08:20 meteomontaos weewx[17144]: wmr300: driver version is 0.18
>>> Feb 04 19:08:20 meteomontaos weewx[17144]: wmr300: usb info: 
>>> pyusb_version=0.4.x
>>> Feb 04 19:08:20 meteomontaos weewx[17144]: wmr300: sensor map is 
>>> {'outHumidity': 'humidity_1', 'extraDewpoint6': 'dewpoint_7', 'windchill': 
>>> 'windchill', 'extraDewpoint4': 'dewpoint_5', 'rainRate': 'rain_rate', 
>>> 'heatindex': 'heatindex_1', 'inTemp': 'temperature_0', 'windGustDir': 
>>> 'wind_gust_dir', 'extraDewpoint2': 'dewpoint_3', 'extraDewpoint3': 
>>> 'dewpoint_4', 'extraDewpoint1': 'dewpoint_2', 'barometer': 'barometer', 
>>> 'extraDewpoint7': 'dewpoint_8', 'dewpoint': 'dewpoint_1', 'extraDewpoint5': 
>>> 'dewpoint_6', 'extraHumid6': 'humidity_7', 'pressure': 'pressure', 
>>> 'extraHumid4': 'humidity_5', 'extraHumid5': 'humidity_6', 'extraHumid2': 
>>> 'humidity_3', 'extraHumid3': 'humidity_4', 'extraHumid1': 'humidity_2', 
>>> 'extraTemp6': 'temperature_7', 'extraTemp7': 'temperature_8', 'extraTemp4': 
>>> 'temperature_5', 'extraTemp5': 'temperature_6', 'extraTemp2': 
>>> 'temperature_3', 'extraTemp3': 'temperature_4', 'extraTemp1': 
>>> 'temperature_2', 'extraHeatindex3': 'heatindex_4', 'extraHeatindex2': 
>>> 'heatindex_3', 'extraHeatindex1': 'heatindex_2', 'extraHeatindex7': 
>>> 'heatindex_8', 'extraHeatindex6': 'heatindex_7', 'extraHeatindex5': 
>>> 'heatindex_6', 'extraHumid7': 'humidity_8', 'extraHeatindex4': 
>>> 'heatindex_5', 'windDir': 'wind_dir', 'outTemp': 'temperature_1', 
>>> 'windSpeed': 'wind_avg', 'inHumidity': 'humidity_0', 'windGust': 
>>> 'wind_gust'}
>>> Feb 04 19:08:20 meteomontaos weewx[17144]: wmr300: Found station at 
>>> bus=001 device=004
>>> Feb 04 19:08:20 meteomontaos kernel: usb 1-1.5: reset full-speed USB 
>>> device number 4 using dwc_otg
>>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Loading service 
>>> weewx.engine.StdTimeSynch
>>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Finished loading 
>>> service weewx.engine.StdTimeSynch
>>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Loading service 
>>> weewx.engine.StdConvert
>>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: StdConvert target 
>>> unit is 0x10
>>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Finished loading 
>>> service weewx.engine.StdConvert
>>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Loading service 
>>> weewx.engine.StdCalibrate
>>> Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Finished loading 
>>> service weewx.engine.StdCalibrate
>>> Feb 04 19:08:21 

[weewx-user] Re: NoneType error setting up WEEWX for WMR200 on Rasberry Pi3

[mwall]

On Sunday, February 4, 2018 at 5:05:03 PM UTC-5, JustJane wrote:
>
> Thanks. I edited the weewx.conf file and restarted weewx. It seems to loop 
> through old records then falls over once it gets to live data. The log file 
> when it falls over has the following entries
>

jane,

at line 1797 in the file weewx/drivers/wmr200.py, change this:

mapped = self._sensors_to_fields(pkt.packet_record(),

 self._sensor_map)

yield mapped

to this:

mapped = self._sensors_to_fields(pkt.packet_record(),

 self._sensor_map)

if mapped:

yield mapped

then start weewx.

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.

[weewx-user] Re: NoneType error setting up WEEWX for WMR200 on Rasberry Pi3

[JustJane]

Thanks. I edited the weewx.conf file and restarted weewx. It seems to loop 
through old records then falls over once it gets to live data. The log file 
when it falls over has the following entries

Feb  4 22:34:33 JanesPi weewx[2691]: wmr200: MainThread: D genLoop() 
Yielding live queued packet id:823
Feb  4 22:34:34 JanesPi weewx[2691]: wmr200: MainThread: D   Queuing live 
packet rx:382 live_queue_len:1
Feb  4 22:34:35 JanesPi weewx[2691]: wmr200: MainThread: D genLoop() 
Yielding live queued packet id:824
Feb  4 22:34:37 JanesPi weewx[2691]: wmr200: MainThread: D   Queuing live 
packet rx:383 live_queue_len:1
Feb  4 22:34:38 JanesPi weewx[2691]: wmr200: MainThread: D genLoop() 
Yielding live queued packet id:825
Feb  4 22:34:44 JanesPi weewx[2691]: wmr200: MainThread: D   Queuing live 
packet rx:384 live_queue_len:1
Feb  4 22:34:45 JanesPi weewx[2691]: wmr200: MainThread: D genLoop() 
Yielding live queued packet id:826
Feb  4 22:34:50 JanesPi weewx[2691]: wmr200: MainThread: D   Queuing live 
packet rx:385 live_queue_len:1
Feb  4 22:34:51 JanesPi weewx[2691]: wmr200: MainThread: D genLoop() 
Yielding live queued packet id:827
Feb  4 22:34:51 JanesPi weewx[2691]: engine: Main loop exiting. Shutting 
engine down.
Feb  4 22:34:51 JanesPi weewx[2691]: wmr200: Thread-2: I USB polling device 
thread exiting
Feb  4 22:34:51 JanesPi weewx[2691]: wmr200: MainThread: I USB polling 
thread expired
Feb  4 22:34:51 JanesPi weewx[2691]: wmr200: Thread-1: I Watchdog received 
shutdown
Feb  4 22:34:51 JanesPi weewx[2691]: wmr200: Thread-1: I Watchdog thread 
exiting
Feb  4 22:34:51 JanesPi weewx[2691]: wmr200: MainThread: I Watchdog thread 
expired
Feb  4 22:34:51 JanesPi weewx[2691]: wmr200: MainThread: I Received packet 
count live:385 archive:412 control:30
Feb  4 22:34:51 JanesPi weewx[2691]: wmr200: MainThread: I Received 
bytes:371464 sent bytes:3992
Feb  4 22:34:51 JanesPi weewx[2691]: wmr200: MainThread: I Packet archive 
queue len:0 live queue len:0
Feb  4 22:34:51 JanesPi weewx[2691]: wmr200: MainThread: I Driver 
gracefully exiting
Feb  4 22:34:51 JanesPi weewx[2691]: engine: Caught unrecoverable exception 
in engine:
Feb  4 22:34:51 JanesPi weewx[2691]:   'NoneType' object has no 
attribute '__getitem__'
Feb  4 22:34:51 JanesPi weewx[2691]:   Traceback (most recent call 
last):
Feb  4 22:34:51 JanesPi weewx[2691]: File 
"/usr/share/weewx/weewx/engine.py", line 871, in main
Feb  4 22:34:51 JanesPi weewx[2691]:   engine.run()
Feb  4 22:34:51 JanesPi weewx[2691]: File 
"/usr/share/weewx/weewx/engine.py", line 190, in run
Feb  4 22:34:51 JanesPi weewx[2691]:  
 self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
Feb  4 22:34:51 JanesPi weewx[2691]: File 
"/usr/share/weewx/weewx/engine.py", line 223, in dispatchEvent
Feb  4 22:34:51 JanesPi weewx[2691]:   callback(event)
Feb  4 22:34:51 JanesPi weewx[2691]: File 
"/usr/share/weewx/weewx/engine.py", line 318, in new_loop_packet
Feb  4 22:34:51 JanesPi weewx[2691]:   if 
event.packet['usUnits'] == self.target_unit:
Feb  4 22:34:51 JanesPi weewx[2691]:   TypeError: 'NoneType' object 
has no attribute '__getitem__'
Feb  4 22:34:51 JanesPi weewx[2691]:   Exiting.
 

Please also find attached the debug file

Thanks
Jane

-- 
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.


weewx.debug
Description: Binary data

Re: [weewx-user] 2.6 going to 3.8 and wee_extension

[Glenn McKechnie]

You're missing the "-- install" directive in both of those commands.

sudo /home/weewx/bin/wee_extension /home/myideas/weewx-cmon-0.16.tgz

should be...

sudo /home/weewx/bin/wee_extension --install /home/myideas/weewx-cmon-0.16.tgz

Ditto for weewx-forecast-3.2.19.tgz


http://www.weewx.com/docs/utilities.htm#wee_extension_utility


Cheers
 Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie


On 5 February 2018 at 02:56, vigilancewx  wrote:
> Hello I have been using weewx for a few years version 2.6 on a PI and it
> works fine (changing in and out of GMT causes the pi to play up but thats
> all)  no problems with the SD cards etc
> However i  decided to install the latest version 3.8 on a machine running
> Ubuntu 17
>
> I have modified my 2.6 quite extensively so doing a clean install and trying
> to migrate my mods over if possible
>
> i am unable to get wee_extension to install i have tried on the forecast
> extension and cmon
>
> i cant remember how to install the extensions from a few years ago  and
> using wee_extension i get the following errors
>
> Thanks for any help
>
> pi@picomp:/home/myideas$ dir
> abcweewx.tgz  home   weewx-forecast-3.2.19.tgz
> abweewx.tgz   weewx-cmon-0.16.tgz  weewx-owfs-0.21.tgz
> pi@picomp:/home/myideas$ sudo /home/weewx/bin/wee_extension
> /home/myideas/weewx-cmon-0.16.tgz
> Traceback (most recent call last):
>   File "/home/weewx/bin/wee_extension", line 83, in 
> main()
>   File "/home/weewx/bin/wee_extension", line 62, in main
> config_path, config_dict = weecfg.read_config(options.config, _args)
>   File "/home/weewx/bin/weecfg/__init__.py", line 223, in read_config
> config_dict = configobj.ConfigObj(config_path, file_error=True)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in
> __init__
> self._load(infile, configspec)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in _load
> raise error
> configobj.ConfigObjError: Parsing failed with several errors.
> First error at line 1.
> pi@picomp:/home/myideas$ sudo /home/weewx/bin/wee_extension
> /home/myideas/weewx-forecast-3.2.19.tgz
> Traceback (most recent call last):
>   File "/home/weewx/bin/wee_extension", line 83, in 
> main()
>   File "/home/weewx/bin/wee_extension", line 62, in main
> config_path, config_dict = weecfg.read_config(options.config, _args)
>   File "/home/weewx/bin/weecfg/__init__.py", line 223, in read_config
> config_dict = configobj.ConfigObj(config_path, file_error=True)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in
> __init__
> self._load(infile, configspec)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in _load
> raise error
> configobj.ConfigObjError: Parsing failed with several errors.
> First error at line 3.
> pi@picomp:/home/myideas$
>
> --
> 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.

-- 
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] Problema cuando reinicio Raspberry Pi +wmr300

[Juan Antonio Mosquera]

Ok,

i deleted all data from 2 Feb (delete data in archive table) and drop  - 
rebuild and not add data from 3 feb...

thanks.

El domingo, 4 de febrero de 2018, 19:34:15 (UTC+1), Andrew Milner escribió:
>
> So what is your problem??  It successfully recovered data records from 
> after 1830 on 4 feb until (I assume) 1910 when the main packet loop started.
>
> The recovery is only from the last entry in database up to current time - 
> it will not fill any missing holes - so if there is data in the database 
> for 1830 on 4 feb that is when recovery will start
>
> If you want to get the records for 03 feb you need to delete all data in 
> database from 02 feb - 04 feb and force weewx to read data from 02 feb to 
> current time, as i suggested in previous post.
>
>
>
>
>
> On Sunday, 4 February 2018 20:13:11 UTC+2, Juan Antonio Mosquera wrote:
>
>> Done.
>>
>> No veo errores al iniciar, pero veo esto:
>>
>>
>> eb 04 19:08:18 meteomontaos systemd[1]: Starting LSB: weewx weather 
>> system...
>> Feb 04 19:08:20 meteomontaos weewx[17140]: engine: Initializing weewx 
>> version 3.8.0
>> Feb 04 19:08:20 meteomontaos weewx[17140]: engine: Using Python 2.7.9 
>> (default, Sep 17 2016, 20:26:04) 
>>[GCC 4.9.2]
>> Feb 04 19:08:20 meteomontaos weewx[17140]: engine: Platform 
>> Linux-4.4.48+-armv6l-with-debian-8.0
>> Feb 04 19:08:20 meteomontaos weewx[17140]: engine: Locale is 'en_US.UTF-8'
>> Feb 04 19:08:20 meteomontaos weewx[17140]: engine: pid file is 
>> /var/run/weewx.pid
>> Feb 04 19:08:20 meteomontaos weewx[17130]: Starting weewx weather system: 
>> weewx.
>> Feb 04 19:08:20 meteomontaos systemd[1]: Started LSB: weewx weather 
>> system.
>> Feb 04 19:08:20 meteomontaos sudo[17109]: pam_unix(sudo:session): session 
>> closed for user root
>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Using configuration 
>> file /etc/weewx/weewx.conf
>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: debug is 1
>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Initializing engine
>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Loading station type 
>> WMR300 (weewx.drivers.wmr300)
>> Feb 04 19:08:20 meteomontaos weewx[17144]: wmr300: driver version is 0.18
>> Feb 04 19:08:20 meteomontaos weewx[17144]: wmr300: usb info: 
>> pyusb_version=0.4.x
>> Feb 04 19:08:20 meteomontaos weewx[17144]: wmr300: sensor map is 
>> {'outHumidity': 'humidity_1', 'extraDewpoint6': 'dewpoint_7', 'windchill': 
>> 'windchill', 'extraDewpoint4': 'dewpoint_5', 'rainRate': 'rain_rate', 
>> 'heatindex': 'heatindex_1', 'inTemp': 'temperature_0', 'windGustDir': 
>> 'wind_gust_dir', 'extraDewpoint2': 'dewpoint_3', 'extraDewpoint3': 
>> 'dewpoint_4', 'extraDewpoint1': 'dewpoint_2', 'barometer': 'barometer', 
>> 'extraDewpoint7': 'dewpoint_8', 'dewpoint': 'dewpoint_1', 'extraDewpoint5': 
>> 'dewpoint_6', 'extraHumid6': 'humidity_7', 'pressure': 'pressure', 
>> 'extraHumid4': 'humidity_5', 'extraHumid5': 'humidity_6', 'extraHumid2': 
>> 'humidity_3', 'extraHumid3': 'humidity_4', 'extraHumid1': 'humidity_2', 
>> 'extraTemp6': 'temperature_7', 'extraTemp7': 'temperature_8', 'extraTemp4': 
>> 'temperature_5', 'extraTemp5': 'temperature_6', 'extraTemp2': 
>> 'temperature_3', 'extraTemp3': 'temperature_4', 'extraTemp1': 
>> 'temperature_2', 'extraHeatindex3': 'heatindex_4', 'extraHeatindex2': 
>> 'heatindex_3', 'extraHeatindex1': 'heatindex_2', 'extraHeatindex7': 
>> 'heatindex_8', 'extraHeatindex6': 'heatindex_7', 'extraHeatindex5': 
>> 'heatindex_6', 'extraHumid7': 'humidity_8', 'extraHeatindex4': 
>> 'heatindex_5', 'windDir': 'wind_dir', 'outTemp': 'temperature_1', 
>> 'windSpeed': 'wind_avg', 'inHumidity': 'humidity_0', 'windGust': 
>> 'wind_gust'}
>> Feb 04 19:08:20 meteomontaos weewx[17144]: wmr300: Found station at 
>> bus=001 device=004
>> Feb 04 19:08:20 meteomontaos kernel: usb 1-1.5: reset full-speed USB 
>> device number 4 using dwc_otg
>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Loading service 
>> weewx.engine.StdTimeSynch
>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Finished loading 
>> service weewx.engine.StdTimeSynch
>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Loading service 
>> weewx.engine.StdConvert
>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: StdConvert target unit 
>> is 0x10
>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Finished loading 
>> service weewx.engine.StdConvert
>> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Loading service 
>> weewx.engine.StdCalibrate
>> Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Finished loading 
>> service weewx.engine.StdCalibrate
>> Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Loading service 
>> weewx.engine.StdQC
>> Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Finished loading 
>> service weewx.engine.StdQC
>> Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Loading service 
>> weewx.wxservices.StdWXCalculate
>> Feb 04 19:08:21 meteomontaos weewx[17144]: wxcalculate: 

[weewx-user] Re: 2.6 going to 3.8 and wee_extension

[gjr80]

Shouldn't be any need to reinstall Linux, that's a bit drastic. If you do 
reinstall weeWX make sure you remove all the remnants, if the issue is old 
remnants still being on the system it is possible that an uninstall will not 
remove them. You might want to go through all of the locations mentioned in the 
User's Guide (http://weewx.com/docs/usersguide.htm#Where_to_find_things).

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.

[weewx-user] Re: 2.6 going to 3.8 and wee_extension

[vigilancewx]

Hi

I will reinstall the Ubuntu
and reinstall weewx 

all fresh clean installations and try again 

thanks



On Sunday, February 4, 2018 at 3:56:02 PM UTC, vigilancewx wrote:
>
> Hello I have been using weewx for a few years version 2.6 on a PI and it 
> works fine (changing in and out of GMT causes the pi to play up but thats 
> all)  no problems with the SD cards etc
> However i  decided to install the latest version 3.8 on a machine running 
> Ubuntu 17
>
> I have modified my 2.6 quite extensively so doing a clean install and 
> trying to migrate my mods over if possible
>
> i am unable to get wee_extension to install i have tried on the forecast 
> extension and cmon
>
> i cant remember how to install the extensions from a few years ago  and 
> using wee_extension i get the following errors
>
> Thanks for any help
>
> pi@picomp:/home/myideas$ dir
> abcweewx.tgz  home   weewx-forecast-3.2.19.tgz
> abweewx.tgz   weewx-cmon-0.16.tgz  weewx-owfs-0.21.tgz
> pi@picomp:/home/myideas$ sudo /home/weewx/bin/wee_extension 
> /home/myideas/weewx-cmon-0.16.tgz
> Traceback (most recent call last):
>   File "/home/weewx/bin/wee_extension", line 83, in 
> main()
>   File "/home/weewx/bin/wee_extension", line 62, in main
> config_path, config_dict = weecfg.read_config(options.config, _args)
>   File "/home/weewx/bin/weecfg/__init__.py", line 223, in read_config
> config_dict = configobj.ConfigObj(config_path, file_error=True)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
> __init__
> self._load(infile, configspec)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in _load
> raise error
> configobj.ConfigObjError: Parsing failed with several errors.
> First error at line 1.
> pi@picomp:/home/myideas$ sudo /home/weewx/bin/wee_extension 
> /home/myideas/weewx-forecast-3.2.19.tgz
> Traceback (most recent call last):
>   File "/home/weewx/bin/wee_extension", line 83, in 
> main()
>   File "/home/weewx/bin/wee_extension", line 62, in main
> config_path, config_dict = weecfg.read_config(options.config, _args)
>   File "/home/weewx/bin/weecfg/__init__.py", line 223, in read_config
> config_dict = configobj.ConfigObj(config_path, file_error=True)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
> __init__
> self._load(infile, configspec)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in _load
> raise error
> configobj.ConfigObjError: Parsing failed with several errors.
> First error at line 3.
> pi@picomp:/home/myideas$ 
>

-- 
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] Problema cuando reinicio Raspberry Pi +wmr300

[Andrew Milner]

So what is your problem??  It successfully recovered data records from 
after 1830 on 4 feb until (I assume) 1910 when the main packet loop started.

The recovery is only from the last entry in database up to current time - 
it will not fill any missing holes - so if there is data in the database 
for 1830 on 4 feb that is when recovery will start

If you want to get the records for 03 feb you need to delete all data in 
database from 02 feb - 04 feb and force weewx to read data from 02 feb to 
current time, as i suggested in previous post.





On Sunday, 4 February 2018 20:13:11 UTC+2, Juan Antonio Mosquera wrote:

> Done.
>
> No veo errores al iniciar, pero veo esto:
>
>
> eb 04 19:08:18 meteomontaos systemd[1]: Starting LSB: weewx weather 
> system...
> Feb 04 19:08:20 meteomontaos weewx[17140]: engine: Initializing weewx 
> version 3.8.0
> Feb 04 19:08:20 meteomontaos weewx[17140]: engine: Using Python 2.7.9 
> (default, Sep 17 2016, 20:26:04) 
>[GCC 4.9.2]
> Feb 04 19:08:20 meteomontaos weewx[17140]: engine: Platform 
> Linux-4.4.48+-armv6l-with-debian-8.0
> Feb 04 19:08:20 meteomontaos weewx[17140]: engine: Locale is 'en_US.UTF-8'
> Feb 04 19:08:20 meteomontaos weewx[17140]: engine: pid file is 
> /var/run/weewx.pid
> Feb 04 19:08:20 meteomontaos weewx[17130]: Starting weewx weather system: 
> weewx.
> Feb 04 19:08:20 meteomontaos systemd[1]: Started LSB: weewx weather system.
> Feb 04 19:08:20 meteomontaos sudo[17109]: pam_unix(sudo:session): session 
> closed for user root
> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Using configuration 
> file /etc/weewx/weewx.conf
> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: debug is 1
> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Initializing engine
> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Loading station type 
> WMR300 (weewx.drivers.wmr300)
> Feb 04 19:08:20 meteomontaos weewx[17144]: wmr300: driver version is 0.18
> Feb 04 19:08:20 meteomontaos weewx[17144]: wmr300: usb info: 
> pyusb_version=0.4.x
> Feb 04 19:08:20 meteomontaos weewx[17144]: wmr300: sensor map is 
> {'outHumidity': 'humidity_1', 'extraDewpoint6': 'dewpoint_7', 'windchill': 
> 'windchill', 'extraDewpoint4': 'dewpoint_5', 'rainRate': 'rain_rate', 
> 'heatindex': 'heatindex_1', 'inTemp': 'temperature_0', 'windGustDir': 
> 'wind_gust_dir', 'extraDewpoint2': 'dewpoint_3', 'extraDewpoint3': 
> 'dewpoint_4', 'extraDewpoint1': 'dewpoint_2', 'barometer': 'barometer', 
> 'extraDewpoint7': 'dewpoint_8', 'dewpoint': 'dewpoint_1', 'extraDewpoint5': 
> 'dewpoint_6', 'extraHumid6': 'humidity_7', 'pressure': 'pressure', 
> 'extraHumid4': 'humidity_5', 'extraHumid5': 'humidity_6', 'extraHumid2': 
> 'humidity_3', 'extraHumid3': 'humidity_4', 'extraHumid1': 'humidity_2', 
> 'extraTemp6': 'temperature_7', 'extraTemp7': 'temperature_8', 'extraTemp4': 
> 'temperature_5', 'extraTemp5': 'temperature_6', 'extraTemp2': 
> 'temperature_3', 'extraTemp3': 'temperature_4', 'extraTemp1': 
> 'temperature_2', 'extraHeatindex3': 'heatindex_4', 'extraHeatindex2': 
> 'heatindex_3', 'extraHeatindex1': 'heatindex_2', 'extraHeatindex7': 
> 'heatindex_8', 'extraHeatindex6': 'heatindex_7', 'extraHeatindex5': 
> 'heatindex_6', 'extraHumid7': 'humidity_8', 'extraHeatindex4': 
> 'heatindex_5', 'windDir': 'wind_dir', 'outTemp': 'temperature_1', 
> 'windSpeed': 'wind_avg', 'inHumidity': 'humidity_0', 'windGust': 
> 'wind_gust'}
> Feb 04 19:08:20 meteomontaos weewx[17144]: wmr300: Found station at 
> bus=001 device=004
> Feb 04 19:08:20 meteomontaos kernel: usb 1-1.5: reset full-speed USB 
> device number 4 using dwc_otg
> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Loading service 
> weewx.engine.StdTimeSynch
> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Finished loading 
> service weewx.engine.StdTimeSynch
> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Loading service 
> weewx.engine.StdConvert
> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: StdConvert target unit 
> is 0x10
> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Finished loading 
> service weewx.engine.StdConvert
> Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Loading service 
> weewx.engine.StdCalibrate
> Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Finished loading 
> service weewx.engine.StdCalibrate
> Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Loading service 
> weewx.engine.StdQC
> Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Finished loading 
> service weewx.engine.StdQC
> Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Loading service 
> weewx.wxservices.StdWXCalculate
> Feb 04 19:08:21 meteomontaos weewx[17144]: wxcalculate: The following 
> values will be calculated: barometer=prefer_hardware, 
> windchill=prefer_hardware, dewpoint=prefer_hardware, 
> appTemp=prefer_hardware, rainRate=prefer_hardware, windrun=prefer_hardware, 
> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
> humidex=prefer_hardware, 

[weewx-user] 2.6 going to 3.8 and wee_extension

[gjr80]

Hi,

One of the first things wee_extension does is find weewx.conf and read it's 
contents with configobj (a config file parser). wee_extension has found a 
config file but configobj is finding errors in the file. Odd that it is finding 
errors in different places for (you would expect) the same file. I assume you 
have 3.8.0 running without error? The normal approach is to get weeWX running 
without error before adding extensions/further customising. A couple of things 
you can try if weeWX is otherwise running without error:

- Check weewx.conf, is there anything obviously wrong in the first few lines. 
You upgraded from 2.6 but did you do a clean install or an upgrade, assume a 
clean install if a different machine/OS.  If you did a clean 3.8.0 install 
weewx.conf should be good. You didn't copy weewx.conf from your old system did 
you? That could cause problems.

- Try explicitly specifying weewx.conf when running wee_extension using the 
--config option. Specify the full path to weewx.conf (take note of what weeWX 
says in its startup log to ensure you and weeWX agree on where weewx.conf is. 
If you don't use the --config option wee_extension looks for weewx.conf in the 
usual places, perhaps it has picked up an old or invalid file that is not your 
current weewx.cnf, could happen if if multiple installs have occurred on the 
machine using different install methods.

If you have no luck do a wee_debug run 
(http://weewx.com/docs/utilities.htm#wee_debug_utility) and post the output 
checking for any sensitive info first, wee_does a good job at removing 
sensitive info but it's not perfect. There is a chance wee_debug will have the 
same problem as wee_extension, in which case just post a copy of weewx.conf but 
you will need to manually remove sensitive info. Finally, what type of 3.8.0 
install did you do on the new machine?

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] Problema cuando reinicio Raspberry Pi +wmr300

[Juan Antonio Mosquera]

Done.

No veo errores al iniciar, pero veo esto:


eb 04 19:08:18 meteomontaos systemd[1]: Starting LSB: weewx weather 
system...
Feb 04 19:08:20 meteomontaos weewx[17140]: engine: Initializing weewx 
version 3.8.0
Feb 04 19:08:20 meteomontaos weewx[17140]: engine: Using Python 2.7.9 
(default, Sep 17 2016, 20:26:04) 
   [GCC 4.9.2]
Feb 04 19:08:20 meteomontaos weewx[17140]: engine: Platform 
Linux-4.4.48+-armv6l-with-debian-8.0
Feb 04 19:08:20 meteomontaos weewx[17140]: engine: Locale is 'en_US.UTF-8'
Feb 04 19:08:20 meteomontaos weewx[17140]: engine: pid file is 
/var/run/weewx.pid
Feb 04 19:08:20 meteomontaos weewx[17130]: Starting weewx weather system: 
weewx.
Feb 04 19:08:20 meteomontaos systemd[1]: Started LSB: weewx weather system.
Feb 04 19:08:20 meteomontaos sudo[17109]: pam_unix(sudo:session): session 
closed for user root
Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Using configuration file 
/etc/weewx/weewx.conf
Feb 04 19:08:20 meteomontaos weewx[17144]: engine: debug is 1
Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Initializing engine
Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Loading station type 
WMR300 (weewx.drivers.wmr300)
Feb 04 19:08:20 meteomontaos weewx[17144]: wmr300: driver version is 0.18
Feb 04 19:08:20 meteomontaos weewx[17144]: wmr300: usb info: 
pyusb_version=0.4.x
Feb 04 19:08:20 meteomontaos weewx[17144]: wmr300: sensor map is 
{'outHumidity': 'humidity_1', 'extraDewpoint6': 'dewpoint_7', 'windchill': 
'windchill', 'extraDewpoint4': 'dewpoint_5', 'rainRate': 'rain_rate', 
'heatindex': 'heatindex_1', 'inTemp': 'temperature_0', 'windGustDir': 
'wind_gust_dir', 'extraDewpoint2': 'dewpoint_3', 'extraDewpoint3': 
'dewpoint_4', 'extraDewpoint1': 'dewpoint_2', 'barometer': 'barometer', 
'extraDewpoint7': 'dewpoint_8', 'dewpoint': 'dewpoint_1', 'extraDewpoint5': 
'dewpoint_6', 'extraHumid6': 'humidity_7', 'pressure': 'pressure', 
'extraHumid4': 'humidity_5', 'extraHumid5': 'humidity_6', 'extraHumid2': 
'humidity_3', 'extraHumid3': 'humidity_4', 'extraHumid1': 'humidity_2', 
'extraTemp6': 'temperature_7', 'extraTemp7': 'temperature_8', 'extraTemp4': 
'temperature_5', 'extraTemp5': 'temperature_6', 'extraTemp2': 
'temperature_3', 'extraTemp3': 'temperature_4', 'extraTemp1': 
'temperature_2', 'extraHeatindex3': 'heatindex_4', 'extraHeatindex2': 
'heatindex_3', 'extraHeatindex1': 'heatindex_2', 'extraHeatindex7': 
'heatindex_8', 'extraHeatindex6': 'heatindex_7', 'extraHeatindex5': 
'heatindex_6', 'extraHumid7': 'humidity_8', 'extraHeatindex4': 
'heatindex_5', 'windDir': 'wind_dir', 'outTemp': 'temperature_1', 
'windSpeed': 'wind_avg', 'inHumidity': 'humidity_0', 'windGust': 
'wind_gust'}
Feb 04 19:08:20 meteomontaos weewx[17144]: wmr300: Found station at bus=001 
device=004
Feb 04 19:08:20 meteomontaos kernel: usb 1-1.5: reset full-speed USB device 
number 4 using dwc_otg
Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Loading service 
weewx.engine.StdTimeSynch
Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Loading service 
weewx.engine.StdConvert
Feb 04 19:08:20 meteomontaos weewx[17144]: engine: StdConvert target unit 
is 0x10
Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Finished loading service 
weewx.engine.StdConvert
Feb 04 19:08:20 meteomontaos weewx[17144]: engine: Loading service 
weewx.engine.StdCalibrate
Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Finished loading service 
weewx.engine.StdCalibrate
Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Loading service 
weewx.engine.StdQC
Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Finished loading service 
weewx.engine.StdQC
Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Feb 04 19:08:21 meteomontaos weewx[17144]: wxcalculate: The following 
values will be calculated: barometer=prefer_hardware, 
windchill=prefer_hardware, dewpoint=prefer_hardware, 
appTemp=prefer_hardware, rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Feb 04 19:08:21 meteomontaos weewx[17144]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Loading service 
user.csv.CSV
Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Finished loading service 
user.csv.CSV
Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Loading service 
weewx.engine.StdArchive
Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Archive will use data 
binding wx_binding
Feb 04 19:08:21 meteomontaos weewx[17144]: engine: Record 

Re: [weewx-user] Problema cuando reinicio Raspberry Pi +wmr300

[Juan Antonio Mosquera]

More info...

No hay errores en el log cuando se inicia.

En la documentación: http://www.weewx.com/docs/hardware.htm#wmr300_notes

dice:

When weeWX starts up it will attempt to download all records from the 
console since the last record in the archive database. This can take as 
much as couple of hours, depending on the number of records in the logger 
and the speed of the computer and disk.


Pero... no veo que lea los datos que faltan.

El domingo, 4 de febrero de 2018, 18:27:47 (UTC+1), Juan Antonio Mosquera 
escribió:
>
> Los datos no están en la base de datos.
>
> Con la estación anterior (watson) y versiones anteriores de weewx, al 
> reiniciar weewx, el sistema recuperaba los datos que no habían sido 
> registrados por alguna caída de weewx o de la raspberry.
>
> Yo quiero que weewx revise los datos de la WMR300 y guarde en BBDD los 
> datos que no ha registrado. Es posible?
>
> Gracias.
>
> El domingo, 4 de febrero de 2018, 17:19:43 (UTC+1), Andrew Milner escribió:
>>
>> Is it the NOAA report that has no data for 03 feb - or does the database 
>> have no data for 03 feb??
>>
>> To regenerate the noaa report just delete it and it will be generated 
>> again on the next report cycle - if the data is in the database.
>>
>> If weewx did not restart/recover correctly then you need to give us the 
>> logs for the restart to be able to help.
>>
>>
>>
>> On Sunday, 4 February 2018 18:10:13 UTC+2, Juan Antonio Mosquera wrote:
>>
>>> Ya había leído eso, pero antes con la estación Watson esto no pasaba.
>>>
>>> Ahora si la estación queda sin internet o se apaga, al reiniciar no 
>>> recupera de la estación WMR300 los datos que no se subieron, no sincroniza, 
>>> ejemplo:
>>>
>>> http://www.meteomontaos.gal/NOAA/NOAA-2018-02.txt
>>>
>>> day 3 Feb no se sincroniza con los datos de la estación.
>>>
>>> Saludos y gracias.
>>>
>>> El viernes, 2 de febrero de 2018, 6:03:25 (UTC+1), Andrew Milner 
>>> escribió:

 Have you read this:
 https://github.com/weewx/weewx/wiki/Raspberry-Pi



 On Thursday, 1 February 2018 23:04:33 UTC+2, Juan Antonio Mosquera 
 wrote:

> Ok Tom, en cuanto pueda se lo envio, muchas gracias
>
> El jueves, 1 de febrero de 2018, 22:03:01 (UTC+1), Tom Keffer escribió:
>>
>> necesitaríamos ver el registro del sistema.
>>
>> -tk
>>
>> 2018-02-01 13:57 GMT-07:00 Juan Antonio Mosquera <
>> juananton...@juanantoniomosquera.com>:
>>
>>> Buenas noches,
>>>
>>> Voy a permitirme hablar en espanhol para explicarme bien.
>>>
>>> Tengo un problema, cuando reinicio raspberry pi b+ weewx + wmr300 
>>> las graficas que crea weewx muestran un intervalo de tiempo sin medida, 
>>> parece como si hubiera un problema de hora, y al reiniciar se setee una 
>>> hora distinta a la actual, aunqeu al revisar la hora ( con date) parece 
>>> correcta.
>>>
>>> alguna idea?
>>>
>>> Saludos y gracias
>>>
>>> -- 
>>> 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.

Re: [weewx-user] Problema cuando reinicio Raspberry Pi +wmr300

[Andrew Milner]

if the data is still in the logger then you should be able to do something 
like:

(NOT TESTED, NOT GUARANTEED TO WORK - TRY AT YOUR OWN RISK)
 
a) stop weewx
b) make a copy of the database
c) make sure rpi has the correct date and time and timezone
d) delete all data in the database from say 01 feb
e) drop daily and rebuild daily summaries
f) restart weewx and it should download data records from after last record 
in database from the station.  It may take a long time to read the 
records.  The log should say what is happening if there are errors

If you have problems attach the log to your post





On Sunday, 4 February 2018 19:27:47 UTC+2, Juan Antonio Mosquera wrote:

> Los datos no están en la base de datos.
>
> Con la estación anterior (watson) y versiones anteriores de weewx, al 
> reiniciar weewx, el sistema recuperaba los datos que no habían sido 
> registrados por alguna caída de weewx o de la raspberry.
>
> Yo quiero que weewx revise los datos de la WMR300 y guarde en BBDD los 
> datos que no ha registrado. Es posible?
>
> Gracias.
>
> El domingo, 4 de febrero de 2018, 17:19:43 (UTC+1), Andrew Milner escribió:
>>
>> Is it the NOAA report that has no data for 03 feb - or does the database 
>> have no data for 03 feb??
>>
>> To regenerate the noaa report just delete it and it will be generated 
>> again on the next report cycle - if the data is in the database.
>>
>> If weewx did not restart/recover correctly then you need to give us the 
>> logs for the restart to be able to help.
>>
>>
>>
>> On Sunday, 4 February 2018 18:10:13 UTC+2, Juan Antonio Mosquera wrote:
>>
>>> Ya había leído eso, pero antes con la estación Watson esto no pasaba.
>>>
>>> Ahora si la estación queda sin internet o se apaga, al reiniciar no 
>>> recupera de la estación WMR300 los datos que no se subieron, no sincroniza, 
>>> ejemplo:
>>>
>>> http://www.meteomontaos.gal/NOAA/NOAA-2018-02.txt
>>>
>>> day 3 Feb no se sincroniza con los datos de la estación.
>>>
>>> Saludos y gracias.
>>>
>>> El viernes, 2 de febrero de 2018, 6:03:25 (UTC+1), Andrew Milner 
>>> escribió:

 Have you read this:
 https://github.com/weewx/weewx/wiki/Raspberry-Pi



 On Thursday, 1 February 2018 23:04:33 UTC+2, Juan Antonio Mosquera 
 wrote:

> Ok Tom, en cuanto pueda se lo envio, muchas gracias
>
> El jueves, 1 de febrero de 2018, 22:03:01 (UTC+1), Tom Keffer escribió:
>>
>> necesitaríamos ver el registro del sistema.
>>
>> -tk
>>
>> 2018-02-01 13:57 GMT-07:00 Juan Antonio Mosquera <
>> juananton...@juanantoniomosquera.com>:
>>
>>> Buenas noches,
>>>
>>> Voy a permitirme hablar en espanhol para explicarme bien.
>>>
>>> Tengo un problema, cuando reinicio raspberry pi b+ weewx + wmr300 
>>> las graficas que crea weewx muestran un intervalo de tiempo sin medida, 
>>> parece como si hubiera un problema de hora, y al reiniciar se setee una 
>>> hora distinta a la actual, aunqeu al revisar la hora ( con date) parece 
>>> correcta.
>>>
>>> alguna idea?
>>>
>>> Saludos y gracias
>>>
>>> -- 
>>> 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.

Re: [weewx-user] Problema cuando reinicio Raspberry Pi +wmr300

[Juan Antonio Mosquera]

Los datos no están en la base de datos.

Con la estación anterior (watson) y versiones anteriores de weewx, al 
reiniciar weewx, el sistema recuperaba los datos que no habían sido 
registrados por alguna caída de weewx o de la raspberry.

Yo quiero que weewx revise los datos de la WMR300 y guarde en BBDD los 
datos que no ha registrado. Es posible?

Gracias.

El domingo, 4 de febrero de 2018, 17:19:43 (UTC+1), Andrew Milner escribió:
>
> Is it the NOAA report that has no data for 03 feb - or does the database 
> have no data for 03 feb??
>
> To regenerate the noaa report just delete it and it will be generated 
> again on the next report cycle - if the data is in the database.
>
> If weewx did not restart/recover correctly then you need to give us the 
> logs for the restart to be able to help.
>
>
>
> On Sunday, 4 February 2018 18:10:13 UTC+2, Juan Antonio Mosquera wrote:
>
>> Ya había leído eso, pero antes con la estación Watson esto no pasaba.
>>
>> Ahora si la estación queda sin internet o se apaga, al reiniciar no 
>> recupera de la estación WMR300 los datos que no se subieron, no sincroniza, 
>> ejemplo:
>>
>> http://www.meteomontaos.gal/NOAA/NOAA-2018-02.txt
>>
>> day 3 Feb no se sincroniza con los datos de la estación.
>>
>> Saludos y gracias.
>>
>> El viernes, 2 de febrero de 2018, 6:03:25 (UTC+1), Andrew Milner escribió:
>>>
>>> Have you read this:
>>> https://github.com/weewx/weewx/wiki/Raspberry-Pi
>>>
>>>
>>>
>>> On Thursday, 1 February 2018 23:04:33 UTC+2, Juan Antonio Mosquera wrote:
>>>
 Ok Tom, en cuanto pueda se lo envio, muchas gracias

 El jueves, 1 de febrero de 2018, 22:03:01 (UTC+1), Tom Keffer escribió:
>
> necesitaríamos ver el registro del sistema.
>
> -tk
>
> 2018-02-01 13:57 GMT-07:00 Juan Antonio Mosquera <
> juananton...@juanantoniomosquera.com>:
>
>> Buenas noches,
>>
>> Voy a permitirme hablar en espanhol para explicarme bien.
>>
>> Tengo un problema, cuando reinicio raspberry pi b+ weewx + wmr300 las 
>> graficas que crea weewx muestran un intervalo de tiempo sin medida, 
>> parece 
>> como si hubiera un problema de hora, y al reiniciar se setee una hora 
>> distinta a la actual, aunqeu al revisar la hora ( con date) parece 
>> correcta.
>>
>> alguna idea?
>>
>> Saludos y gracias
>>
>> -- 
>> 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.

Re: [weewx-user] Problema cuando reinicio Raspberry Pi +wmr300

[Andrew Milner]

Is it the NOAA report that has no data for 03 feb - or does the database 
have no data for 03 feb??

To regenerate the noaa report just delete it and it will be generated again 
on the next report cycle - if the data is in the database.

If weewx did not restart/recover correctly then you need to give us the 
logs for the restart to be able to help.



On Sunday, 4 February 2018 18:10:13 UTC+2, Juan Antonio Mosquera wrote:

> Ya había leído eso, pero antes con la estación Watson esto no pasaba.
>
> Ahora si la estación queda sin internet o se apaga, al reiniciar no 
> recupera de la estación WMR300 los datos que no se subieron, no sincroniza, 
> ejemplo:
>
> http://www.meteomontaos.gal/NOAA/NOAA-2018-02.txt
>
> day 3 Feb no se sincroniza con los datos de la estación.
>
> Saludos y gracias.
>
> El viernes, 2 de febrero de 2018, 6:03:25 (UTC+1), Andrew Milner escribió:
>>
>> Have you read this:
>> https://github.com/weewx/weewx/wiki/Raspberry-Pi
>>
>>
>>
>> On Thursday, 1 February 2018 23:04:33 UTC+2, Juan Antonio Mosquera wrote:
>>
>>> Ok Tom, en cuanto pueda se lo envio, muchas gracias
>>>
>>> El jueves, 1 de febrero de 2018, 22:03:01 (UTC+1), Tom Keffer escribió:

 necesitaríamos ver el registro del sistema.

 -tk

 2018-02-01 13:57 GMT-07:00 Juan Antonio Mosquera <
 juananton...@juanantoniomosquera.com>:

> Buenas noches,
>
> Voy a permitirme hablar en espanhol para explicarme bien.
>
> Tengo un problema, cuando reinicio raspberry pi b+ weewx + wmr300 las 
> graficas que crea weewx muestran un intervalo de tiempo sin medida, 
> parece 
> como si hubiera un problema de hora, y al reiniciar se setee una hora 
> distinta a la actual, aunqeu al revisar la hora ( con date) parece 
> correcta.
>
> alguna idea?
>
> Saludos y gracias
>
> -- 
> 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.

Re: [weewx-user] Problema cuando reinicio Raspberry Pi +wmr300

[Juan Antonio Mosquera]

Ya había leído eso, pero antes con la estación Watson esto no pasaba.

Ahora si la estación queda sin internet o se apaga, al reiniciar no 
recupera de la estación WMR300 los datos que no se subieron, no sincroniza, 
ejemplo:

http://www.meteomontaos.gal/NOAA/NOAA-2018-02.txt

day 3 Feb no se sincroniza con los datos de la estación.

Saludos y gracias.

El viernes, 2 de febrero de 2018, 6:03:25 (UTC+1), Andrew Milner escribió:
>
> Have you read this:
> https://github.com/weewx/weewx/wiki/Raspberry-Pi
>
>
>
> On Thursday, 1 February 2018 23:04:33 UTC+2, Juan Antonio Mosquera wrote:
>
>> Ok Tom, en cuanto pueda se lo envio, muchas gracias
>>
>> El jueves, 1 de febrero de 2018, 22:03:01 (UTC+1), Tom Keffer escribió:
>>>
>>> necesitaríamos ver el registro del sistema.
>>>
>>> -tk
>>>
>>> 2018-02-01 13:57 GMT-07:00 Juan Antonio Mosquera <
>>> juananton...@juanantoniomosquera.com>:
>>>
 Buenas noches,

 Voy a permitirme hablar en espanhol para explicarme bien.

 Tengo un problema, cuando reinicio raspberry pi b+ weewx + wmr300 las 
 graficas que crea weewx muestran un intervalo de tiempo sin medida, parece 
 como si hubiera un problema de hora, y al reiniciar se setee una hora 
 distinta a la actual, aunqeu al revisar la hora ( con date) parece 
 correcta.

 alguna idea?

 Saludos y gracias

 -- 
 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.

[weewx-user] 2.6 going to 3.8 and wee_extension

[vigilancewx]

Hello I have been using weewx for a few years version 2.6 on a PI and it 
works fine (changing in and out of GMT causes the pi to play up but thats 
all)  no problems with the SD cards etc
However i  decided to install the latest version 3.8 on a machine running 
Ubuntu 17

I have modified my 2.6 quite extensively so doing a clean install and 
trying to migrate my mods over if possible

i am unable to get wee_extension to install i have tried on the forecast 
extension and cmon

i cant remember how to install the extensions from a few years ago  and 
using wee_extension i get the following errors

Thanks for any help

pi@picomp:/home/myideas$ dir
abcweewx.tgz  home   weewx-forecast-3.2.19.tgz
abweewx.tgz   weewx-cmon-0.16.tgz  weewx-owfs-0.21.tgz
pi@picomp:/home/myideas$ sudo /home/weewx/bin/wee_extension 
/home/myideas/weewx-cmon-0.16.tgz
Traceback (most recent call last):
  File "/home/weewx/bin/wee_extension", line 83, in 
main()
  File "/home/weewx/bin/wee_extension", line 62, in main
config_path, config_dict = weecfg.read_config(options.config, _args)
  File "/home/weewx/bin/weecfg/__init__.py", line 223, in read_config
config_dict = configobj.ConfigObj(config_path, file_error=True)
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
__init__
self._load(infile, configspec)
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in _load
raise error
configobj.ConfigObjError: Parsing failed with several errors.
First error at line 1.
pi@picomp:/home/myideas$ sudo /home/weewx/bin/wee_extension 
/home/myideas/weewx-forecast-3.2.19.tgz
Traceback (most recent call last):
  File "/home/weewx/bin/wee_extension", line 83, in 
main()
  File "/home/weewx/bin/wee_extension", line 62, in main
config_path, config_dict = weecfg.read_config(options.config, _args)
  File "/home/weewx/bin/weecfg/__init__.py", line 223, in read_config
config_dict = configobj.ConfigObj(config_path, file_error=True)
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
__init__
self._load(infile, configspec)
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in _load
raise error
configobj.ConfigObjError: Parsing failed with several errors.
First error at line 3.
pi@picomp:/home/myideas$ 

-- 
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] weewx raspi - only life data

[Andrew Milner]

pages are generated every archive interval.  check the log at the startup 
of weewx to make sure the archive interval from weewx.conf is being used.  
If the weather station has a different archive interval then the weather 
station's interval will be being used.



On Sunday, 4 February 2018 12:42:28 UTC+2, h...@shipdesign.de wrote:

> Dear All,
>
> found the time to install weewx and it runs fine.
> I will use just the index.html to pick out the data I want to have. That's 
> simple and easy for me.
>
> Just an other question:
> The standard is 30min update time.
> I could not find the setting to reduce this to e.g. 5min, same as archive 
> interval, which is 300sec.
>
> Thanks
>
> Harald
>
>
> Am Samstag, 20. Januar 2018 03:37:57 UTC+1 schrieb Andrew Milner:
>>
>> Just create a template called for example textdata.txt.tmpl, put inside 
>> the template the data fields you want in the .txt file for example:
>> $current.inTemp
>> $current.outTemp
>> $current.outHumidity
>>
>> set the archive interval to 60 and let cheetah create and populate your 
>> .txt file every 60 seconds
>>
>>
>>
>> On Saturday, 20 January 2018 02:00:59 UTC+2, h...@shipdesign.de wrote:
>>
>>> Hi Tom,
>>> I just need a text file every 60 seconds with the actual data.
>>> The rest is done by own code.
>>>
>>> I had a look at the customization guide - seems to give answers.
>>> Anyhow, I understand, it is necessary to run some database (LQlite) 
>>> always.
>>>
>>> Thanks for the hint.
>>>
>>> Harald
>>>
>>> Am Samstag, 20. Januar 2018 00:11:54 UTC+1 schrieb Tom Keffer:

 Hello, Harald

 I am not completely understanding your question.

 Do you want to write to an RDD database (which one?) instead of sqlite 
 or MySQL? If that is the case, then that would probably be a major 
 project. 

 Do you want instructions on how to write data to an HTML or XML file? 
 If so, there is lots of information in the Customizing Guide 
  on using templates to create 
 files.

 Or, did you want to do something else?

 -tk



 On Fri, Jan 19, 2018 at 3:09 PM,  wrote:

> Hi out there,
> I want to 'miss use' weewx on a raspi just for reading life data e.g. 
> every 60 sec and write it to an ASCII file, may be an html or xml file.
> This will be displayed and written to a RDD database together with a 
> bulk of data from the solar panel, battery and different consumption data.
> Tried to find out in the users manual e.g. to switch of the whole 
> archiving/database ...
> Any idea is of help.
> Thanks
> Harald
>
> -- 
> 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.

[weewx-user] Re: Weewx failing again

[Rune Lægreid]

Hi,

the weather station is in a very remote location and I just lost 
communication to the RPi.
I will visit the location (cabin) earliest on February 21 and by then I 
will set up a new RPi to take over for the one I have up in the mountains 
currently.

Do you have any recommendations when it comes to setup and configuration 
for an RPi with a Davis Vantage Pro2?

Rune.

lørdag 3. februar 2018 02.15.26 UTC+1 skrev gjr80 følgende:
>
> Hi Rune,
>
> Yes I did, seems we had our wires crossed, I was waiting for the debug=1 
> log from startup? wee_debug tells me what should happen, debug=1 startup 
> log tells me what did happen. A couple more questions/requests; do these 
> two errors occur on every report cycle or just now and then? If all the 
> time could you run weeWX directly 
>  and post the 
> screen output, only need to see the REC: line and a few LOOP: lines before 
> the REC:.
>
> Gary
>
> On Friday, 2 February 2018 23:50:58 UTC+10, Rune Laegreid wrote:
>>
>> look not lokk :-)
>>
>> fredag 2. februar 2018 14.49.35 UTC+1 skrev Rune Laegreid følgende:
>>>
>>> Gary,
>>>
>>> Did you have a chance to lokk at my debug report?
>>>
>>> Rune.
>>>
>>> lørdag 27. januar 2018 23.28.29 UTC+1 skrev gjr80 følgende:

 Hi,

 You have errors from at last 2 extensions in the log extract you 
 provided so I am thinking there may be a wider issue here. So we can get a 
 clear picture of what your are running can you please post a wee_debug (
 http://weewx.com/docs/utilities.htm#wee_debug_utility) report, make 
 sure you check the report for any sensitive info before posting. Can you 
 also set debug=1 in weewx.conf then restart weeWX and post the log from 
 startup until a couple of archive records have been processed.

 One other thing, I have found these sorts of errors frequently occur 
 when some observations are missing ie None. I see part of you log extract 
 (22:02:03-22:02:07) seems to indicate this, apart from the log errors is 
 your station functioning as it should and displaying all observations?

 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] weewx raspi - only life data

[hjm]

Dear All,

found the time to install weewx and it runs fine.
I will use just the index.html to pick out the data I want to have. That's 
simple and easy for me.

Just an other question:
The standard is 30min update time.
I could not find the setting to reduce this to e.g. 5min, same as archive 
interval, which is 300sec.

Thanks

Harald


Am Samstag, 20. Januar 2018 03:37:57 UTC+1 schrieb Andrew Milner:
>
> Just create a template called for example textdata.txt.tmpl, put inside 
> the template the data fields you want in the .txt file for example:
> $current.inTemp
> $current.outTemp
> $current.outHumidity
>
> set the archive interval to 60 and let cheetah create and populate your 
> .txt file every 60 seconds
>
>
>
> On Saturday, 20 January 2018 02:00:59 UTC+2, h...@shipdesign.de wrote:
>
>> Hi Tom,
>> I just need a text file every 60 seconds with the actual data.
>> The rest is done by own code.
>>
>> I had a look at the customization guide - seems to give answers.
>> Anyhow, I understand, it is necessary to run some database (LQlite) 
>> always.
>>
>> Thanks for the hint.
>>
>> Harald
>>
>> Am Samstag, 20. Januar 2018 00:11:54 UTC+1 schrieb Tom Keffer:
>>>
>>> Hello, Harald
>>>
>>> I am not completely understanding your question.
>>>
>>> Do you want to write to an RDD database (which one?) instead of sqlite 
>>> or MySQL? If that is the case, then that would probably be a major project. 
>>>
>>> Do you want instructions on how to write data to an HTML or XML file? If 
>>> so, there is lots of information in the Customizing Guide 
>>>  on using templates to create 
>>> files.
>>>
>>> Or, did you want to do something else?
>>>
>>> -tk
>>>
>>>
>>>
>>> On Fri, Jan 19, 2018 at 3:09 PM,  wrote:
>>>
 Hi out there,
 I want to 'miss use' weewx on a raspi just for reading life data e.g. 
 every 60 sec and write it to an ASCII file, may be an html or xml file.
 This will be displayed and written to a RDD database together with a 
 bulk of data from the solar panel, battery and different consumption data.
 Tried to find out in the users manual e.g. to switch of the whole 
 archiving/database ...
 Any idea is of help.
 Thanks
 Harald

 -- 
 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.

[weewx-user] Re: Just an other Problem with ftp upload

[St Bl]

Yes ... sure. This Directory exist

Am Samstag, 3. Februar 2018 20:28:06 UTC+1 schrieb vince:
>
>  
>
>> Failed uploading /pages/wetter/daytempchill.png to www.myurl.de. Reason: 
>> 550 /pages/wetter/daytempchill.png: No such file or directory
>>
>
> Does the /pages/wetter directory exist on your destination computer of 
> www.myurl.de ?
>
>
>  
>

-- 
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.