Re: [weewx-user] Bootstrap skin update preview

2021-02-23 Thread Michael 
The installation of fuzzy-archer-liveCharts.zip works without error message.
But when generating the reports, the following appears:

Feb 24 08:22:21 weewx-test weewx[4262] DEBUG weewx.reportengine: Found 
configuration file /home/weewx/skins/Images/skin.conf for report 
'SmallImages'
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: Unable to 
instantiate generator 'user.translategenerator.ImageGeneratorTranslated'
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  No module named 'user.jsonengine'
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  Traceback (most recent call last):
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
File "/home/weewx/bin/weewx/reportengine.py", line 179, in run
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  obj = weeutil.weeutil.get_object(generator)(
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
File "/home/weewx/bin/weeutil/weeutil.py", line 1093, in get_object
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  mod = __import__(module)
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
File "/home/weewx/bin/user/translategenerator.py", line 43, in 

Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  from user.jsonengine import JSONGenerator
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  ModuleNotFoundError: No module named 'user.jsonengine'
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  Generator ignored
Feb 24 08:22:21 weewx-test weewx[4262] DEBUG weewx.reportengine: Running 
report 'BigImages'
Feb 24 08:22:21 weewx-test weewx[4262] DEBUG weewx.reportengine: Found 
configuration file /home/weewx/skins/Images/skin.conf for report 'BigImages'
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: Unable to 
instantiate generator 'user.translategenerator.ImageGeneratorTranslated'
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  No module named 'user.jsonengine'
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  Traceback (most recent call last):
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
File "/home/weewx/bin/weewx/reportengine.py", line 179, in run
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  obj = weeutil.weeutil.get_object(generator)(
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
File "/home/weewx/bin/weeutil/weeutil.py", line 1093, in get_object
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  mod = __import__(module)
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
File "/home/weewx/bin/user/translategenerator.py", line 43, in 

Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  from user.jsonengine import JSONGenerator
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  ModuleNotFoundError: No module named 'user.jsonengine'
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  Generator ignored
Feb 24 08:22:21 weewx-test weewx[4262] DEBUG weewx.reportengine: Running 
report 'HTMLPages'
Feb 24 08:22:21 weewx-test weewx[4262] DEBUG weewx.reportengine: Found 
configuration file /home/weewx/skins/Bootstrap/skin.conf for report 
'HTMLPages'
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: Unable to 
instantiate generator 'user.translategenerator.JSONGeneratorTranslated'
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  No module named 'user.jsonengine'
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  Traceback (most recent call last):
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
File "/home/weewx/bin/weewx/reportengine.py", line 179, in run
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  obj = weeutil.weeutil.get_object(generator)(
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
File "/home/weewx/bin/weeutil/weeutil.py", line 1093, in get_object
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  mod = __import__(module)
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
File "/home/weewx/bin/user/translategenerator.py", line 43, in 

Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  from user.jsonengine import JSONGenerator
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine: 
  ModuleNotFoundError: No module named 'user.jsonengine'
Feb 24 08:22:21 weewx-test weewx[4262] ERROR weewx.reportengine:

[weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

2021-02-23 Thread monmul 
No change in USB port.

pi@WeatherPi:~ $ 
pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
minicom: cannot open /dev/ttyUSB0: Device or resource busy
pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
minicom: cannot open /dev/ttyUSB0: Device or resource busy
pi@WeatherPi:~ $ 
pi@WeatherPi:~ $ 
pi@WeatherPi:~ $ 
pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200

[screen is terminating]
pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200






















[screen is terminating]
pi@WeatherPi:~ $ TEST
bash: TEST: command not found
pi@WeatherPi:~ $ 


On Monday, 22 February 2021 at 23:15:28 UTC+13 gjr80 wrote:

> OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert but I am 
> told they behave just like a console. First thing I would do is test 
> connectivity from your RPi to the Envoy. Any chance the Envoy is now on a 
> different USB port? Not sure if you remember the Establishing connectivity 
> 
>  
> testing Tom got you to work through a couple of years back, but that is a 
> good place to start. The instructions are now in the wiki rather than the 
> User Guide but the link I have provided should work.
>
> Gary
> On Monday, 22 February 2021 at 19:43:26 UTC+10 monmul wrote:
>
>> Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather 
>> system...
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing weewx 
>> version 4.4.0
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python 2.7.13 
>> (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Platform 
>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Locale is 
>> 'en_NZ.UTF-8'
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> Feb 22 22:39:03 WeatherPi weewx[24948]: Starting weewx weather system: 
>> weewx.
>> Feb 22 22:39:03 WeatherPi systemd[1]: Started LSB: weewx weather system.
>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Using configuration 
>> file /etc/weewx/weewx.conf
>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Debug is 1
>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG __main__: Initializing engine
>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO weewx.engine: Loading station 
>> type Vantage (weewx.drivers.vantage)
>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
>> Driver version is 3.2.1
>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
>> Option loop_request=1
>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
>> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
>> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>> Feb 22 22:39:07 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
>> #0 failed
>> Feb 22 22:39:11 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
>> #1 failed
>> Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>> Feb 22 22:39:15 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
>> #2 failed
>> Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>> Feb 22 22:39:19 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
>> #3 failed
>> Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.drivers.vantage: 
>> Unable to wake up console
>> Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.engine: Import of 
>> driver failed: Unable to wake up Vantage console (> 'weewx.WakeupError'>)
>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
>> Traceback (most recent call last):
>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>>   self.console = loader_function(config_dict, self)
>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>>   return VantageService(engine, config_dict)
>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__
>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
>> Feb 22 22:39:19 WeatherPi

[weewx-user] Belchertown Australian forecast

2021-02-23 Thread Neville Davis 
I have updated my post in the weewx Wiki 
https://github.com/weewx/weewx/wiki/Raspberry-Pi-weather-station-with-i2C-sensors
 with 
a link to the mods done to include The Australian localised weather 
forecast, and also a colour history chart
I don't think I left anything out :)

Neville

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f3b98bcb-a10d-4590-8033-bc469c7a9403n%40googlegroups.com.

[weewx-user] Re: MQTTSubscribe units conversion failed

2021-02-23 Thread Tarmo 
Ofcourse. My mistake.
Thank you!

On Tuesday, February 23, 2021 at 7:42:18 PM UTC+2 bell...@gmail.com wrote:

> Rain is an ‘incremental’ observation in WeeWX. Meaning that, it is the 
> amount that has fallen since the previous reading. So, expected units are 
> inch, cm, and mm. mm_per_hour is ‘rate’ measurement and cannot be converted 
> to the expected unit of cm. Perhaps you want name = rainRate?
> For additional information see, 
> http://www.weewx.com/docs/customizing.htm#units
> rich
>
> On Tuesday, 23 February 2021 at 10:52:06 UTC-5 Tarmo wrote:
>
>> Hi!
>>
>> I'm getting the following error:
>> Feb 23 17:25:58 pi3 weewx[1803] DEBUG user.MQTTSubscribe: (Driver) 
>> MessageCallbackProvider data-> incoming topic: emhi/26038/precipitations, 
>> QOS: 0, retain: 1, payload: b'0.1'
>> Feb 23 17:25:58 pi3 weewx[1803] DEBUG weewx.units: Unable to convert from 
>> mm_per_hour to cm
>> Feb 23 17:25:58 pi3 weewx[1803] ERROR user.MQTTSubscribe: (Driver) 
>> MessageCallbackProvider on_message_individual failed with: 'cm'
>> Feb 23 17:25:58 pi3 weewx[1803] ERROR user.MQTTSubscribe: (Driver)  
>> MessageCallbackProvider Ignoring topic=emhi/26038/precipitations and 
>> payload=b'0.1'
>>
>> weewx.conf snippet:
>> [MQTTSubscribeDriver]
>> # This section is for the MQTTSubscribe driver.
>> 
>> # The driver to use:
>> driver = user.MQTTSubscribe
>> 
>> # The MQTT server.
>> # Default is localhost.
>> host = localhost
>> 
>> # The port to connect to.
>> # Default is 1883.
>> port = 1883
>> 
>> # Maximum period in seconds allowed between communications with the 
>> broker.
>> # Default is 60.
>> keepalive = 60
>> 
>> # username for broker authentication.
>> # Default is None.
>> username = 
>> 
>> # password for broker authentication.
>> # Default is None.
>> password = 
>> 
>> # Configuration for the message callback.
>> [[message_callback]]
>> type = individual
>> 
>> # The topics to subscribe to.
>> [[topics]]
>> unit_system = METRIC
>> use_topic_as_fieldname = true
>> use_server_datetime = true
>> 
>> [[[rtl_433/lab/devices/Solight-TE44/1/4/temperature_C]]]
>> name = outTemp
>> [[[emhi/26038/uvindex]]]
>> name = UV
>> [[[emhi/26038/airpressure]]]
>> name = pressure
>> [[[emhi/26038/precipitations]]]
>> name = rain
>> units = mm_per_hour
>> [[[emhi/26038/relativehumidity]]]
>> name = outHumidity
>> [[[emhi/26038/winddirection]]]
>> name = windDir
>> [[[emhi/26038/windspeed]]]
>> name = windSpeed
>> units = meter_per_second
>> [[[emhi/26038/windspeedmax]]]
>> name = windGust
>> units = meter_per_second
>> [[[emhi/26038/phenomenon]]]
>> name = phenomenon
>> conversion_type = None
>> [[[emhi/26038/visibility]]]
>> name = visibility
>> conversion_type = None
>>
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5d952b51-a53e-4cf2-9ef6-55adefafe54fn%40googlegroups.com.

[weewx-user] Re: MQTTSubscribe units conversion failed

2021-02-23 Thread bell...@gmail.com 
Rain is an ‘incremental’ observation in WeeWX. Meaning that, it is the 
amount that has fallen since the previous reading. So, expected units are 
inch, cm, and mm. mm_per_hour is ‘rate’ measurement and cannot be converted 
to the expected unit of cm. Perhaps you want name = rainRate?
For additional information see, 
http://www.weewx.com/docs/customizing.htm#units
rich

On Tuesday, 23 February 2021 at 10:52:06 UTC-5 Tarmo wrote:

> Hi!
>
> I'm getting the following error:
> Feb 23 17:25:58 pi3 weewx[1803] DEBUG user.MQTTSubscribe: (Driver) 
> MessageCallbackProvider data-> incoming topic: emhi/26038/precipitations, 
> QOS: 0, retain: 1, payload: b'0.1'
> Feb 23 17:25:58 pi3 weewx[1803] DEBUG weewx.units: Unable to convert from 
> mm_per_hour to cm
> Feb 23 17:25:58 pi3 weewx[1803] ERROR user.MQTTSubscribe: (Driver) 
> MessageCallbackProvider on_message_individual failed with: 'cm'
> Feb 23 17:25:58 pi3 weewx[1803] ERROR user.MQTTSubscribe: (Driver)  
> MessageCallbackProvider Ignoring topic=emhi/26038/precipitations and 
> payload=b'0.1'
>
> weewx.conf snippet:
> [MQTTSubscribeDriver]
> # This section is for the MQTTSubscribe driver.
> 
> # The driver to use:
> driver = user.MQTTSubscribe
> 
> # The MQTT server.
> # Default is localhost.
> host = localhost
> 
> # The port to connect to.
> # Default is 1883.
> port = 1883
> 
> # Maximum period in seconds allowed between communications with the 
> broker.
> # Default is 60.
> keepalive = 60
> 
> # username for broker authentication.
> # Default is None.
> username = 
> 
> # password for broker authentication.
> # Default is None.
> password = 
> 
> # Configuration for the message callback.
> [[message_callback]]
> type = individual
> 
> # The topics to subscribe to.
> [[topics]]
> unit_system = METRIC
> use_topic_as_fieldname = true
> use_server_datetime = true
> 
> [[[rtl_433/lab/devices/Solight-TE44/1/4/temperature_C]]]
> name = outTemp
> [[[emhi/26038/uvindex]]]
> name = UV
> [[[emhi/26038/airpressure]]]
> name = pressure
> [[[emhi/26038/precipitations]]]
> name = rain
> units = mm_per_hour
> [[[emhi/26038/relativehumidity]]]
> name = outHumidity
> [[[emhi/26038/winddirection]]]
> name = windDir
> [[[emhi/26038/windspeed]]]
> name = windSpeed
> units = meter_per_second
> [[[emhi/26038/windspeedmax]]]
> name = windGust
> units = meter_per_second
> [[[emhi/26038/phenomenon]]]
> name = phenomenon
> conversion_type = None
> [[[emhi/26038/visibility]]]
> name = visibility
> conversion_type = None
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/913b81e9-d4ad-4c6d-9c5a-abf0318dfd45n%40googlegroups.com.

[weewx-user] MQTTSubscribe units conversion failed

2021-02-23 Thread Tarmo 
Hi!

I'm getting the following error:
Feb 23 17:25:58 pi3 weewx[1803] DEBUG user.MQTTSubscribe: (Driver) 
MessageCallbackProvider data-> incoming topic: emhi/26038/precipitations, 
QOS: 0, retain: 1, payload: b'0.1'
Feb 23 17:25:58 pi3 weewx[1803] DEBUG weewx.units: Unable to convert from 
mm_per_hour to cm
Feb 23 17:25:58 pi3 weewx[1803] ERROR user.MQTTSubscribe: (Driver) 
MessageCallbackProvider on_message_individual failed with: 'cm'
Feb 23 17:25:58 pi3 weewx[1803] ERROR user.MQTTSubscribe: (Driver)  
MessageCallbackProvider Ignoring topic=emhi/26038/precipitations and 
payload=b'0.1'

weewx.conf snippet:
[MQTTSubscribeDriver]
# This section is for the MQTTSubscribe driver.

# The driver to use:
driver = user.MQTTSubscribe

# The MQTT server.
# Default is localhost.
host = localhost

# The port to connect to.
# Default is 1883.
port = 1883

# Maximum period in seconds allowed between communications with the 
broker.
# Default is 60.
keepalive = 60

# username for broker authentication.
# Default is None.
username = 

# password for broker authentication.
# Default is None.
password = 

# Configuration for the message callback.
[[message_callback]]
type = individual

# The topics to subscribe to.
[[topics]]
unit_system = METRIC
use_topic_as_fieldname = true
use_server_datetime = true

[[[rtl_433/lab/devices/Solight-TE44/1/4/temperature_C]]]
name = outTemp
[[[emhi/26038/uvindex]]]
name = UV
[[[emhi/26038/airpressure]]]
name = pressure
[[[emhi/26038/precipitations]]]
name = rain
units = mm_per_hour
[[[emhi/26038/relativehumidity]]]
name = outHumidity
[[[emhi/26038/winddirection]]]
name = windDir
[[[emhi/26038/windspeed]]]
name = windSpeed
units = meter_per_second
[[[emhi/26038/windspeedmax]]]
name = windGust
units = meter_per_second
[[[emhi/26038/phenomenon]]]
name = phenomenon
conversion_type = None
[[[emhi/26038/visibility]]]
name = visibility
conversion_type = None


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7c16bc7e-3bb5-4ac8-a712-c445576d51f2n%40googlegroups.com.

[weewx-user] Re: Importing Weatherflow data

2021-02-23 Thread mbat...@gmail.com 
Please keep "us" in the loop... I'm sure I'm going to want to duplicate 
these efforts for my station...
Thanks!

Paul

On Tuesday, February 23, 2021 at 4:06:39 AM UTC-6 gjr80 wrote:

> Hi,
>
> You more or less have it. CSV imports require a header row so that 
> wee_import can identify the source data fields and map them to WeeWX 
> field as per the field map. If the data you intend to import has no header 
> row then you can add one, the field names are not important, the important 
> part is making sure you use the correct field name in the field map.
>
> There is no --test, I think you mean --dry-run instead. Best thing is to 
> work through the CSV import step-by-step instructions 
>  in the 
> Utilities Guide, but I would also revise all of the CSV related sections as 
> well.
>
> In terms of checking the import results, that really comes down to you and 
> how much confirmation you require. In order of increasing complexity you 
> might consider the following:
>
> 1. did the import executed without error?
> 2. did the reported number of records processed and imported match your 
> expectations?
> 3. were there any errors in the log?
> 4. were there any unexplained failures to save a record to database in the 
> log? (a record may not be saved to database because a record for that 
> timestamp already exists)
> 5. do the NOAA month and year reports for the period imported have 
> sensible/expected values?
> 6. did the number of records saved to database match your expectation? 
> (the only way to confirm the number of records saved to database is to 
> count the success 'record added' messga ein the log, unfortunately 
> wee_import is unable to determine how many records are actually saved to 
> database, it can only tell how many records it processed and attempted to 
> save to database)
> 7. does each field of the imported data in the database match the 
> corresponding field/record in the source? (this one is for hardcore users, 
> there are no tools for doing this it is a manual process)
>
> I would do 1-5 but 6 and 7, well that depends on how hard core you are :)
>
> Gary
>
>
> On Tuesday, 23 February 2021 at 16:37:29 UTC+10 david.a@gmail.com 
> wrote:
>
>> sorry, my touchpad has caused early posting!
>> To continue, 
>> 5. Edit the import file to include the field names.
>> 6. run wee-import --test only
>> 7. evaluate results, make corrections
>> 8. run final import
>> 9. restart weewx
>>
>> any way to verify success?
>>
>>
>> On Monday, February 22, 2021 at 10:27:44 PM UTC-8 David Prellwitz wrote:
>>
>>> I'm trying to import (wee_import) two weeks of data from my tempest 
>>> repository held at Weatherflow. The API page example of my data shows no 
>>> header in the csv file. How should i handle this import? should i edit the 
>>> file by adding the first reacord and inserting the proper field names?
>>> i assume the normal approach is to:
>>> 1. create the import config file.
>>> 2. extract the WeatherFlow data use their API.
>>> 3. stop weewx, 
>>> 4. copy current db as backup, 
>>> 5. edit 
>>> 6. 
>>>
>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f24eae16-ed16-49d1-9156-f85c6ef8b3a2n%40googlegroups.com.

Re: [weewx-user] Problem with extension install (SyntaxError: Non-ASCII character)

2021-02-23 Thread Michael Schantl 
Yes, a new db needs to be created. You could also configure a second db 
manually, let WeeWX populate the schema and then transfer all data using 
wee_database 
--transfer
But the effort is mostly the same either way, so it's easier to just follow 
the documentation.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/51e4d4d3-c9f1-4773-a489-fbaaf289f7d0n%40googlegroups.com.

Re: [weewx-user] Belchertown skin with Australian BOM forecasts

2021-02-23 Thread Neville Davis 
I will include it in the weewx wiki post of mine soon... 

Neville
On Tuesday, February 23, 2021 at 7:58:16 PM UTC+10 ti...@skybase.net wrote:

> Hi Neville,
>
> Can you share your mods to get BoM forecasts into Belchertown ?
>
> I'd like to be able to do that too :)
>
> thanks
>
> Tim
>
> On 23/2/21 10:30 am, Neville Davis wrote:
> > I have updated my weather station link in the weewx Wiki ( i2C weather 
> > station) to include the local Australian weather 
> > forecast. https://bit.ly/2A8BbOx
> > I have also included the colourful history chart by Nick Dajda.
> > The forecast data is gathered by the script by Darryn Capes-Davis.
> >
> > Neville
> >
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d6a1c2ba-4358-40db-864d-88b09e565f72n%40googlegroups.com.

Re: [weewx-user] Customising NOAATable

2021-02-23 Thread Auchtermuchty Weather 

Got around to looking at this, and it was easy thanks to your help.  
Instead of 'return cellText' I used 'return cellText.replace(".txt", "")'

My Python is almost non-existent, but my moderate C# was handy.  :)


On Tuesday, 16 February 2021 at 13:58:59 UTC gjr80 wrote:

> If I understand your question correctly the $NOAATable tag is produced in 
> the MyXSearch search list in user/historygenerator.py. The actual HTML 
> for the links to the month and year NOAA format reports is produced in the 
> _NoaaCell() 
> 
>  
> and _NoaaYear() 
> 
>  
> methods. I hope your python is good!
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d99ffa95-1cf2-46a5-a3af-4920ffc4bc53n%40googlegroups.com.

[weewx-user] Re: Importing Weatherflow data

2021-02-23 Thread gjr80 
Hi,

You more or less have it. CSV imports require a header row so that 
wee_import can identify the source data fields and map them to WeeWX field 
as per the field map. If the data you intend to import has no header row 
then you can add one, the field names are not important, the important part 
is making sure you use the correct field name in the field map.

There is no --test, I think you mean --dry-run instead. Best thing is to 
work through the CSV import step-by-step instructions 
 in the 
Utilities Guide, but I would also revise all of the CSV related sections as 
well.

In terms of checking the import results, that really comes down to you and 
how much confirmation you require. In order of increasing complexity you 
might consider the following:

1. did the import executed without error?
2. did the reported number of records processed and imported match your 
expectations?
3. were there any errors in the log?
4. were there any unexplained failures to save a record to database in the 
log? (a record may not be saved to database because a record for that 
timestamp already exists)
5. do the NOAA month and year reports for the period imported have 
sensible/expected values?
6. did the number of records saved to database match your expectation? (the 
only way to confirm the number of records saved to database is to count the 
success 'record added' messga ein the log, unfortunately wee_import is 
unable to determine how many records are actually saved to database, it can 
only tell how many records it processed and attempted to save to database)
7. does each field of the imported data in the database match the 
corresponding field/record in the source? (this one is for hardcore users, 
there are no tools for doing this it is a manual process)

I would do 1-5 but 6 and 7, well that depends on how hard core you are :)

Gary


On Tuesday, 23 February 2021 at 16:37:29 UTC+10 david.a@gmail.com wrote:

> sorry, my touchpad has caused early posting!
> To continue, 
> 5. Edit the import file to include the field names.
> 6. run wee-import --test only
> 7. evaluate results, make corrections
> 8. run final import
> 9. restart weewx
>
> any way to verify success?
>
>
> On Monday, February 22, 2021 at 10:27:44 PM UTC-8 David Prellwitz wrote:
>
>> I'm trying to import (wee_import) two weeks of data from my tempest 
>> repository held at Weatherflow. The API page example of my data shows no 
>> header in the csv file. How should i handle this import? should i edit the 
>> file by adding the first reacord and inserting the proper field names?
>> i assume the normal approach is to:
>> 1. create the import config file.
>> 2. extract the WeatherFlow data use their API.
>> 3. stop weewx, 
>> 4. copy current db as backup, 
>> 5. edit 
>> 6. 
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d0833664-b6f5-49d4-a3b6-7c7020b65965n%40googlegroups.com.

Re: [weewx-user] Problem with extension install (SyntaxError: Non-ASCII character)

2021-02-23 Thread Christian Gruber 
hello,

put my RPI now to the same subnet, and i get data.

i also switched schema in weewx.conf to user.weatherlink_live.schema and 
restarted the service

do i have to create a new database then, like its written 
here http://www.weewx.com/docs/customizing.htm#archive_database 
or is this not necessary?

regards,
chris

Christian Gruber schrieb am Sonntag, 21. Februar 2021 um 08:46:12 UTC+1:

> hello,
>
> thank you for this information about schema and UDP.
>
> i use a mikrotik rb4011igs, so i think this should be possible, i will 
> look for a solution and post it here.
>
> regards,
> chris
>
> mbat...@gmail.com schrieb am Sonntag, 21. Februar 2021 um 03:39:09 UTC+1:
>
>> UDP broadcasts are not routed between subnets, so unless your weewx host 
>> has a presence on the weatherlink hub's net, it won't "hear" the hub.
>>
>> There are a couple of ways (besides "multi-homing" the weewx box) to deal 
>> with the problem. Ass u me ing your home firewall / router is a Linux box, 
>> and that you have administrative control of it, one solution is to install 
>> a UDP replicator (such as this one 
>> ) on your home router.  
>> Another method (same assumptions) is to use port forwarding, which is 
>> described here 
>> 
>> .
>>
>> On Saturday, February 20, 2021 at 12:55:10 PM UTC-6 
>> michael.s...@gmail.com wrote:
>>
>>> should the pi and weatherlink live be on the same subnetwork, because i 
 dont get data

>>>
>>> Yes, to receive the live 2.5 second push updates (wind, rain) both 
>>> devices must be on the same subnet. They work using UDP broadcasts. The 
>>> "complete" data set (HTTP) doesn't technically require it, though I haven't 
>>> tested whether the driver works fine if it never receives a push update (it 
>>> should).
>>>
>>>
>>> why should i switch to WLL schema, i loose specific data, when i dont do 
 it?

>>>  
>>> The following columns are added in the WLL schema:
>>>
>>>- dewpoint and heatindex for up to 9 sensors (default only for 2)
>>>- wetbulb temperature
>>>- THW and THSW index ("feels like" temperature)
>>>- indoor heatindex 
>>>- "rainCount": how often your rain sensor's spoon got tripped since 
>>>the last update
>>>- "rainCountRate": the current rate of spoon tripping
>>>- "rainSize": the size of the rain sensor spoon *in inches *(as 
>>>configured in the WLL app or the WeatherLink.com website)
>>>
>>> Additionally, daily summaries and units are configured for all new 
>>> columns (except the last one).
>>>
>>>
>>> regards, Michael
>>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8cf02db6-eb61-47d5-9d88-455e9b83470bn%40googlegroups.com.

Re: [weewx-user] Belchertown skin with Australian BOM forecasts

2021-02-23 Thread Tim Tuck 

Hi Neville,

Can you share your mods to get BoM forecasts into Belchertown ?

I'd like to be able to do that too :)

thanks

Tim

On 23/2/21 10:30 am, Neville Davis wrote:
I have updated my weather station link in the weewx Wiki ( i2C weather 
station) to include the local Australian weather 
forecast. https://bit.ly/2A8BbOx

I have also included the colourful history chart by Nick Dajda.
The forecast data is gathered by the script by Darryn Capes-Davis.

Neville



--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/602e9753-2490-3e65-aae2-d6d5f5e8a273%40skybase.net.

[weewx-user] Belchertown skin with Australian BOM forecasts

2021-02-23 Thread Neville Davis 
I have updated my weather station link in the weewx Wiki ( i2C weather 
station) to include the local Australian weather 
forecast. https://bit.ly/2A8BbOx 
I have also included the colourful history chart by Nick Dajda.
The forecast data is gathered by the script by Darryn Capes-Davis.

Neville

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9d111241-914e-43e4-bbe8-0dfb33709d2cn%40googlegroups.com.

[weewx-user] Belchertown skin with colour history chart and local Australian weather forecast

2021-02-23 Thread Neville Davis 
I have updated my link in my information on the weewx Wiki (i2C weather 
station) to my latest weather page. https://bit.ly/2A8BbOx
I have edited and incorporated scripts by Darryn Capes-Davis and Nick Dajda 
into the Belchertown skin.
Still been quite slack in getting my installation files and scripts 
updatedmaybe this year..  :)

Neville


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6ffe7d3f-e9cf-4d72-8719-e0716421af9fn%40googlegroups.com.

[weewx-user] Belchertown skin with local Australian weather forecast

2021-02-23 Thread Neville Davis 
I have updated my weather station link in my weewx Wiki entry (pi weather 
station with i2C sensors).
The link https://bit.ly/2A8BbOx now is able to display the local forecast 
data from our Gov website using the script developed by Darryn Capes-Davis 
for his responsive skin, also the history chart using a script by Nick 
Dajda used in his Bootstrap skin.
I have been meaning to update the Wiki for sometime, thought maybe I should 
get started.
Running on weewx 4.4.0 Belchertown 1.2 and python 3.

Neville

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0f844c6e-35f7-4db7-a72b-ea8ec2f8bc63n%40googlegroups.com.