Re: [weewx-user] Re: GW2000 driver and additional sensors

[Stephen Hocking]

Hi Gary,

Thank you for you clear and complete explanation, I now have the plots
being generated as I like in Seasons (haven't dared venture into
Belchertown), and am quite happy.

On Mon, 6 Jun 2022 at 14:07, gjr80  wrote:

> The first requirement for plotting observation data from a driver/station
> is that the data to be plotted must be saved to database, simply put if
> it's not in the database you cannot plot it. Following on from this
> requirement is that WeeWX will only save a field to database if (1) the
> field exists in the current archive table schema (aka 'the database
> schema') and (2) the field exists in the archive record generated by WeeWX
> (software record generation) or the driver (hardware record generation). If
> these two conditions are met the field will be automatically saved to
> database by WeeWX.
>
> As you say, all of the required data is present in loop packets. The WH41
> PM2.5 data appears in WeeWX loop packet field pm2_5 and the WH45 PM2.5
> and PM10 data appears in WeeWX loop packet fields pm2_55 and pm10 (refer
> to the Field Map page
> 
> in the Ecowitt Gateway driver wiki). If you are using the default
> wview_extended schema your archive table will contain the pm2_5 and pm10
> fields but not pm2_55. To get the WH45 PM2.5 data saved to database you
> will either need to add field pm2_55 to your database schema or you will
> need to re-purpose an existing unused database field in which to store the
> pm2_55 data. I would suggest the former, just follow the instructions
> under in Adding a new type to an existing database
>  in the
> Customization Guide. Once you have added the new field to the database you
> will need to tell WeeWX what units the new field uses, this is covered
> under Assigning a unit group
>  in the
> Customization Guide, but in your case the code required is:
>
> import weewx.units
> weewx.units.obs_group_dict['pm2_55'] = 'group_concentration'
>
> and you should add this code to /usr/share/weewx/user/extensions.py or
> /home/weewx/bin/user/extensions.py (as applicable).
>
> If you want to save the WH45 PM2.5 data in a (new) database field of your
> own choosing, for example say indoor_pm2_5, then you will need to add a
> field map extensions entry under [GW1000] in weewx.conf to map the WH45
> PM2.5 data to WeeWX field indoor_pm2_5, something like:
>
> [GW1000]
> 
> [[field_map_extensions]]
> indoor_pm2_5 = pm2_55
>
> you would then need to follow the earlier instructions for adding a field
> to the database but use indoor_pm2_5 as the field name instead of pm2_55.
>
> Once you restart WeeWX you should have WH41 PM2.5, WH45 PM2.5 and WH45
> PM10 data being saved to database. You can now make the necessary changes
> to the Season skin to create/display the desired plots.
>
> I'm not quite sure what you mean by "I'd like to map the indoor pm2.5 (and
> pm10) separately from the outdoor pm2.5". These three fields are already
> mapped separately, do you mean plotted instead of mapped?
>
> Assuming you are using the 'new' parameterised Season skin introduced in
> WeeWX v4.6.0 you will need to make a few changes to skin.conf to generate
> and display the plots you desire. There is already a plot that displays
> PM2.5 and PM10, you can add the WH45 PM2.5 data to the plot by adding
> pm2_55 to [[[daypm]]] under [ImageGenerator] [[day_images]], ie:
>
> [ImageGenerator]
> 
> [[day_plots]]
> 
> [[[daypm]]]
> pm1_0
> pm2_5
> pm10
> pm2_55
>
> You will need to make similar changes to [[[weekpm]]], [[[monthpm]]] and
> [[[yearpm]]]. This will result in the plots being likely being labelled
> 'pm2_5 pm10 pm2_55', you can change this to something more appealing by
> using the label option for each series, eg:
>
> [[[daypm]]]
> pm1_0
> pm2_5
> label = Outdoor PM2.5
> pm10
> label = Indoor PM10
> pm2_55
> label = Indoor PM2.5
>
> Note that this needs to be applied to each plot ie [[[daypm]]],
> [[[weekpm]]], [[[monthpm]]] and [[[yearpm]]]. Or you could add some
> suitable labels under [StdReport] [[Defaults]] [[[Labels]]]
> Generic in weewx.conf, eg:
>
>
> [StdReport]
> 
> [[Defaults]]
> 
> [[[Labels]]]
> 
> Generic
> 
> pm2_5 = Outdoor PM2.5
> pm10 = Indoor PM10
> pm2_55 = Indoor PM2.5
>
> If you want to have separate indoor and outdoor plots for PM2.5/PM10 then
> you would need to:
> 1. modify [[[daypm]]] and friends under [ImageGenerator] to plot either
> indoor or outdoor only
> 2. create a new plot, say [[[dayoutdoorpm]

[weewx-user] Re: Installing WS 6in1 for Bresser 5-in1

[gjr80]

You might want to re-think your approach here and use the latest WeeWX 
version under python3, you are already tying yourself in knots trying to 
find the right python 2 packages and it's only going to get worse as time 
progresses and python 2 falls further by the wayside. You cite the CRT and 
WeatherCloud extensions lack of support for python3 /WeeWX 4 as your reason 
for reverting to python 2, but both of those extensions were ported to 
WeeWX 4/python 3 over two years ago - this wiki link 
 and this wiki link 
 refer (green ticks mean 
tested with WeeWX 4/python 3). The two error traces you provided earlier 
for the CRT service and WeatherCloud uploader are certainly due to python 
2/3 code compatibility issues, but the line numbers/code in each trace do 
not match with the current GitHub versions of each so I strongly suspect 
you are tying to run old versions of CRT and WeatherCloud.

Gary

On Thursday, 16 June 2022 at 09:32:25 UTC+10 Ξ wrote:

> ...
> Like I said I decided to go back to Python2/WeeWX 3.7.1 because the CRT 
> and WeatherCloud extensions work with this combination.
> ...
>

-- 
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/f9f24c3b-dbcc-42de-b924-0112589e4c9dn%40googlegroups.com.

[weewx-user] Re: Installing WS 6in1 for Bresser 5-in1

[Ξ]

or rather Python3 can't find it, since it works with Python2 and weewx 
v3.7.1, either way I've decided to try that make work (because weewx 4.8 
doesn't work with two of the extensions for whatever reason) and I solved 
the crcmod issue, but when I try to run it it fails because 'No module 
named core'

[image: unknown.png]

I looked at ws6in1.py and on row 370 it's specified as 'import usb.core', 
pyusb is installed but it seems its sub-module 'core' isn't found by 
ws6in1.py 
# python2 -m site
sys.path = [
'/root',
'/usr/lib/python27.zip',
'/usr/lib/python2.7',
'/usr/lib/python2.7/plat-linux2',
'/usr/lib/python2.7/lib-tk',
'/usr/lib/python2.7/lib-old',
'/usr/lib/python2.7/lib-dynload',
'/usr/lib/python2.7/site-packages',
'/usr/lib/python2.7/site-packages/pyusb-1.0.2-py2.7.egg',
]
USER_BASE: '/root/.local' (exists)
USER_SITE: '/root/.local/lib/python2.7/site-packages' (doesn't exist)
ENABLE_USER_SITE: True

Like I said I decided to go back to Python2/WeeWX 3.7.1 because the CRT and 
WeatherCloud extensions work with this combination.

- Ivo

On Tuesday, June 14, 2022 at 7:34:56 PM UTC+3 Bob Atchley wrote:

> Looks like the 'Cheetah' module is not installed (or Python can't find it)
> Have a look at the install page:
> https://weewx.com/docs/setup.htm
> And look at the different OS tabs (Arch is not included).
> Some seem to use 'pip3' others the equivalent of 'pacman install'
> I would try a combination to find out what works with Arch
>
> Hope this helps
>
> Bob
>
>

-- 
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/621a5f34-36dc-4b27-80ca-38f90a70fb7fn%40googlegroups.com.

Re: [weewx-user] Re: Help with forecast

['John Kline' via weewx-user]

Our emails crossed.  I’m glad you got it working.

> On Jun 15, 2022, at 7:53 AM, John Kline  wrote:
> 
> 
> It sure looks like your forecast.sdb archive table got created as a weewx 
> archive table.  If so, it wasn’t the forecast extension that did it.  Perhaps 
> the binding were misconfigured when forecast.sdb was created.
> 
> Before we delete it, let’s have a look at it.
> 
> Please paste the output of (adjusting the path of forecast.sdb as necessary):
> 
> $ sqlite3 /home/weewx/archive/forecast.sdb 
> SQLite version 3.34.1 2021-01-20 14:10:07
> Enter ".help" for usage hints.
> sqlite> PRAGMA table_info(archive);
> 
> 
> If so, delete your forecast.sdb file and restart weewx.
> 
>>> On Jun 15, 2022, at 7:09 AM, Timothy Reaves  
>>> wrote:
>>> 
>> 
>> I'm going to start looking more at the python code now.
>> 
>> [DataBindings]
>> 
>>   [[wx_binding]]
>> # The database must match one of the sections in [Databases].
>> # This is likely to be the only option you would want to change.
>> database = archive_sqlite
>> # The name of the table within the database
>> table_name = archive
>> # The manager handles aggregation of data for historical summaries
>> manager = weewx.manager.DaySummaryManager
>> # The schema defines the structure of the database.
>> # It is *only* used when the database is created.
>> schema = schemas.wview_extended.schema
>> 
>>   [[forecast_binding]]
>> manager = weewx.manager.Manager
>> schema = user.forecast.schema
>> table_name = archive
>> database = forecast_sqlite
>> 
>> ##
>> 
>> #   This section defines various databases.
>> 
>> [Databases]
>> 
>>   # A SQLite database is simply a single file
>>   [[archive_sqlite]]
>> database_name = weewx.sdb
>> database_type = SQLite
>>   
>>   [[forecast_sqlite]]
>> database_type = SQLite
>> database_name = forecast.sdb
>> 
>> 
>>> On Wednesday, June 15, 2022 at 8:22:37 AM UTC-4 jo...@johnkline.com wrote:
>>> This looks like a clear case of forecast being pointed to the wrong 
>>> database.
>>> 
>>> Please send the data_binding line in the [forecast[ section of weewx.conf.
>>> Also send the [DataBindings] section of weewx.conf.
>>> 
> On Jun 13, 2022, at 6:49 AM, Timothy Reaves  
> wrote:
> 
 Thank you both for the responses.
>>> 
 
 Doug, that is the extension I wrote this post about.  I have followed the 
 instructions, and receive the error I'd posted. So I have all of the 
 configuration that the plugin lists.  When I enable the archive_service, I 
 get the error.  So for some reason it doesn't seem to be connecting to the 
 correct database.  Here is the snippet from my configuration regarding the 
 databases:
 
 [Databases]
 
 # A SQLite database is simply a single file
 [[archive_sqlite]]
 database_name = weewx.sdb
 database_type = SQLite
 
 # MySQL
 [[archive_mysql]]
 database_name = weewx
 database_type = MySQL
 
 [[forecast_sqlite]]
 database_type = SQLite
 database_name = forecast.sdb
 
 [[forecast_mysql]]
 database_type = MySql
 database_name = forecast
 
>> On Friday, June 10, 2022 at 11:22:26 AM UTC-4 do...@dougjenkins.com 
>> wrote:
>> Tim:
>> 
>> The forecast module uses a completely different schema and database. 
>> What you need to do is configure the module to a separate database and 
>> in your skin, bring in the data to be presented.
>> 
>> I personally use John Kline's weewx forecast driver ( GitHub - 
>> chaunceygardiner/weewx-forecast: forecasting extension for weewx) as it 
>> is being maintained and it works with the latest version of WeeWX 
>> (v4.8). You will need to look at the sample pages that accompany the 
>> driver and integrate the cheetah template code into your skin. 
>> 
>> Best practice is to copy your existing skin folder (eg seasons) to a 
>> separate folder (seasons-forecast) and make the modifications there. I 
>> usually use the wee_reports utility to generate the html when I make 
>> changes to the skin.
>> 
>> Please let us know if you have any questions.
>> 
>> Doug
>> www.largoweather.com
>> 
>> 
>>> On Friday, June 10, 2022 at 10:22:59 AM UTC-4 RobbH wrote:
>>> This is certainly not what you are looking for, but it is what I use to 
>>> get NWS forecasts.
>>> 
>>> Here is a url for a forecast for a randomly selected location:
>>> 
>>> https://forecast.weather.gov/MapClick.php?lat=41.177010&lon=-73.141963&unit=0&lg=english&FcstType=text&TextType=2
>>> 
>>> Note where latitude and longitude are inserted. "TextType=2" at the end 
>>> tells the server to include forecast graphics

Re: [weewx-user] Re: Help with forecast

['John Kline' via weewx-user]

It sure looks like your forecast.sdb archive table got created as a weewx 
archive table.  If so, it wasn’t the forecast extension that did it.  Perhaps 
the binding were misconfigured when forecast.sdb was created.

Before we delete it, let’s have a look at it.

Please paste the output of (adjusting the path of forecast.sdb as necessary):

$ sqlite3 /home/weewx/archive/forecast.sdb 
SQLite version 3.34.1 2021-01-20 14:10:07
Enter ".help" for usage hints.
sqlite> PRAGMA table_info(archive);


If so, delete your forecast.sdb file and restart weewx.

> On Jun 15, 2022, at 7:09 AM, Timothy Reaves  
> wrote:
> 
> 
> I'm going to start looking more at the python code now.
> 
> [DataBindings]
> 
>   [[wx_binding]]
> # The database must match one of the sections in [Databases].
> # This is likely to be the only option you would want to change.
> database = archive_sqlite
> # The name of the table within the database
> table_name = archive
> # The manager handles aggregation of data for historical summaries
> manager = weewx.manager.DaySummaryManager
> # The schema defines the structure of the database.
> # It is *only* used when the database is created.
> schema = schemas.wview_extended.schema
> 
>   [[forecast_binding]]
> manager = weewx.manager.Manager
> schema = user.forecast.schema
> table_name = archive
> database = forecast_sqlite
> 
> ##
> 
> #   This section defines various databases.
> 
> [Databases]
> 
>   # A SQLite database is simply a single file
>   [[archive_sqlite]]
> database_name = weewx.sdb
> database_type = SQLite
>   
>   [[forecast_sqlite]]
> database_type = SQLite
> database_name = forecast.sdb
> 
> 
>> On Wednesday, June 15, 2022 at 8:22:37 AM UTC-4 jo...@johnkline.com wrote:
>> This looks like a clear case of forecast being pointed to the wrong database.
>> 
>> Please send the data_binding line in the [forecast[ section of weewx.conf.
>> Also send the [DataBindings] section of weewx.conf.
>> 
 On Jun 13, 2022, at 6:49 AM, Timothy Reaves  
 wrote:
 
>>> Thank you both for the responses.
>> 
>>> 
>>> Doug, that is the extension I wrote this post about.  I have followed the 
>>> instructions, and receive the error I'd posted. So I have all of the 
>>> configuration that the plugin lists.  When I enable the archive_service, I 
>>> get the error.  So for some reason it doesn't seem to be connecting to the 
>>> correct database.  Here is the snippet from my configuration regarding the 
>>> databases:
>>> 
>>> [Databases]
>>> 
>>> # A SQLite database is simply a single file
>>> [[archive_sqlite]]
>>> database_name = weewx.sdb
>>> database_type = SQLite
>>> 
>>> # MySQL
>>> [[archive_mysql]]
>>> database_name = weewx
>>> database_type = MySQL
>>> 
>>> [[forecast_sqlite]]
>>> database_type = SQLite
>>> database_name = forecast.sdb
>>> 
>>> [[forecast_mysql]]
>>> database_type = MySql
>>> database_name = forecast
>>> 
> On Friday, June 10, 2022 at 11:22:26 AM UTC-4 do...@dougjenkins.com wrote:
> Tim:
> 
> The forecast module uses a completely different schema and database. What 
> you need to do is configure the module to a separate database and in your 
> skin, bring in the data to be presented.
> 
> I personally use John Kline's weewx forecast driver ( GitHub - 
> chaunceygardiner/weewx-forecast: forecasting extension for weewx) as it 
> is being maintained and it works with the latest version of WeeWX (v4.8). 
> You will need to look at the sample pages that accompany the driver and 
> integrate the cheetah template code into your skin. 
> 
> Best practice is to copy your existing skin folder (eg seasons) to a 
> separate folder (seasons-forecast) and make the modifications there. I 
> usually use the wee_reports utility to generate the html when I make 
> changes to the skin.
> 
> Please let us know if you have any questions.
> 
> Doug
> www.largoweather.com
> 
> 
>> On Friday, June 10, 2022 at 10:22:59 AM UTC-4 RobbH wrote:
>> This is certainly not what you are looking for, but it is what I use to 
>> get NWS forecasts.
>> 
>> Here is a url for a forecast for a randomly selected location:
>> 
>> https://forecast.weather.gov/MapClick.php?lat=41.177010&lon=-73.141963&unit=0&lg=english&FcstType=text&TextType=2
>> 
>> Note where latitude and longitude are inserted. "TextType=2" at the end 
>> tells the server to include forecast graphics.
>> 
>> Several times a day, a cron job uses PhantomJS to retrieve that page and 
>> create an jpeg of the forecast graphics, which is then displayed on my 
>> weewx home page.
>> 
>> It usually works well enough for my purposes, but there are ti

Re: [weewx-user] [resolved] Re: Help with forecast

[Timothy Reaves]

I ended up having to manually create the sqlite database, and the archive 
table in it.  Once that was done, I had a misconfiguration in my forecast 
section of the config file.  So now it is creating the data.  I'll now work 
on incorporating it into a template.

Thanks all for your responses.

On Wednesday, June 15, 2022 at 10:09:34 AM UTC-4 Timothy Reaves wrote:

> I'm going to start looking more at the python code now.
>
> [DataBindings]
> 
>   [[wx_binding]]
> # The database must match one of the sections in [Databases].
> # This is likely to be the only option you would want to change.
> database = archive_sqlite
> # The name of the table within the database
> table_name = archive
> # The manager handles aggregation of data for historical summaries
> manager = weewx.manager.DaySummaryManager
> # The schema defines the structure of the database.
> # It is *only* used when the database is created.
> schema = schemas.wview_extended.schema
>
>   [[forecast_binding]]
> manager = weewx.manager.Manager
> schema = user.forecast.schema
> table_name = archive
> database = forecast_sqlite
>
>
> ##
>
> #   This section defines various databases.
>
> [Databases]
> 
>   # A SQLite database is simply a single file
>   [[archive_sqlite]]
> database_name = weewx.sdb
> database_type = SQLite
>   
>   [[forecast_sqlite]]
> database_type = SQLite
> database_name = forecast.sdb
>
>
> On Wednesday, June 15, 2022 at 8:22:37 AM UTC-4 jo...@johnkline.com wrote:
>
>> This looks like a clear case of forecast being pointed to the wrong 
>> database.
>>
>> Please send the data_binding line in the [forecast[ section of weewx.conf.
>> Also send the [DataBindings] section of weewx.conf.
>>
>> On Jun 13, 2022, at 6:49 AM, Timothy Reaves  
>> wrote:
>>
>> Thank you both for the responses.
>>
>>
>> Doug, that is the extension I wrote this post about.  I have followed the 
>> instructions, and receive the error I'd posted. So I have all of the 
>> configuration that the plugin lists.  When I enable the archive_service, I 
>> get the error.  So for some reason it doesn't seem to be connecting to the 
>> correct database.  Here is the snippet from my configuration regarding the 
>> databases:
>>
>> [Databases]
>> 
>> # A SQLite database is simply a single file
>> [[archive_sqlite]]
>> database_name = weewx.sdb
>> database_type = SQLite
>> 
>> # MySQL
>> [[archive_mysql]]
>> database_name = weewx
>> database_type = MySQL
>>
>> [[forecast_sqlite]]
>> database_type = SQLite
>> database_name = forecast.sdb
>>
>> [[forecast_mysql]]
>> database_type = MySql
>> database_name = forecast
>>
>> On Friday, June 10, 2022 at 11:22:26 AM UTC-4 do...@dougjenkins.com 
>> wrote:
>>
>>> Tim:
>>>
>>> The forecast module uses a completely different schema and database. 
>>> What you need to do is configure the module to a separate database and in 
>>> your skin, bring in the data to be presented.
>>>
>>> I personally use John Kline's weewx forecast driver ( GitHub - 
>>> chaunceygardiner/weewx-forecast: forecasting extension for weewx 
>>> ) as it is being 
>>> maintained and it works with the latest version of WeeWX (v4.8). You will 
>>> need to look at the sample pages that accompany the driver and integrate 
>>> the cheetah template code into your skin. 
>>>
>>> Best practice is to copy your existing skin folder (eg seasons) to a 
>>> separate folder (seasons-forecast) and make the modifications there. I 
>>> usually use the wee_reports utility to generate the html when I make 
>>> changes to the skin.
>>>
>>> Please let us know if you have any questions.
>>>
>>> Doug
>>> www.largoweather.com
>>>
>>>
>>> On Friday, June 10, 2022 at 10:22:59 AM UTC-4 RobbH wrote:
>>>
 This is certainly not what you are looking for, but it is what I use to 
 get NWS forecasts.

 Here is a url for a forecast for a randomly selected location:


 https://forecast.weather.gov/MapClick.php?lat=41.177010&lon=-73.141963&unit=0&lg=english&FcstType=text&TextType=2

 Note where latitude and longitude are inserted. "TextType=2" at the end 
 tells the server to include forecast graphics.

 Several times a day, a cron job uses PhantomJS  to 
 retrieve that page and create an jpeg of the forecast graphics, which is 
 then displayed on my weewx home page.

 It usually works well enough for my purposes, but there are times when 
 the forecast page is down, so I end up with a blank rectangle on the weewx 
 page.



 On Wednesday, June 8, 2022 at 12:16:33 PM UTC-4 Timothy Reaves wrote:

> Hello all.  I'm using the latest version running on a Pi 4, with a 
> Davis Vantage

Re: [weewx-user] Re: Help with forecast

[Timothy Reaves]

I'm going to start looking more at the python code now.

[DataBindings]

  [[wx_binding]]
# The database must match one of the sections in [Databases].
# This is likely to be the only option you would want to change.
database = archive_sqlite
# The name of the table within the database
table_name = archive
# The manager handles aggregation of data for historical summaries
manager = weewx.manager.DaySummaryManager
# The schema defines the structure of the database.
# It is *only* used when the database is created.
schema = schemas.wview_extended.schema

  [[forecast_binding]]
manager = weewx.manager.Manager
schema = user.forecast.schema
table_name = archive
database = forecast_sqlite

##

#   This section defines various databases.

[Databases]

  # A SQLite database is simply a single file
  [[archive_sqlite]]
database_name = weewx.sdb
database_type = SQLite
  
  [[forecast_sqlite]]
database_type = SQLite
database_name = forecast.sdb


On Wednesday, June 15, 2022 at 8:22:37 AM UTC-4 jo...@johnkline.com wrote:

> This looks like a clear case of forecast being pointed to the wrong 
> database.
>
> Please send the data_binding line in the [forecast[ section of weewx.conf.
> Also send the [DataBindings] section of weewx.conf.
>
> On Jun 13, 2022, at 6:49 AM, Timothy Reaves  
> wrote:
>
> Thank you both for the responses.
>
>
> Doug, that is the extension I wrote this post about.  I have followed the 
> instructions, and receive the error I'd posted. So I have all of the 
> configuration that the plugin lists.  When I enable the archive_service, I 
> get the error.  So for some reason it doesn't seem to be connecting to the 
> correct database.  Here is the snippet from my configuration regarding the 
> databases:
>
> [Databases]
> 
> # A SQLite database is simply a single file
> [[archive_sqlite]]
> database_name = weewx.sdb
> database_type = SQLite
> 
> # MySQL
> [[archive_mysql]]
> database_name = weewx
> database_type = MySQL
>
> [[forecast_sqlite]]
> database_type = SQLite
> database_name = forecast.sdb
>
> [[forecast_mysql]]
> database_type = MySql
> database_name = forecast
>
> On Friday, June 10, 2022 at 11:22:26 AM UTC-4 do...@dougjenkins.com wrote:
>
>> Tim:
>>
>> The forecast module uses a completely different schema and database. What 
>> you need to do is configure the module to a separate database and in your 
>> skin, bring in the data to be presented.
>>
>> I personally use John Kline's weewx forecast driver ( GitHub - 
>> chaunceygardiner/weewx-forecast: forecasting extension for weewx 
>> ) as it is being 
>> maintained and it works with the latest version of WeeWX (v4.8). You will 
>> need to look at the sample pages that accompany the driver and integrate 
>> the cheetah template code into your skin. 
>>
>> Best practice is to copy your existing skin folder (eg seasons) to a 
>> separate folder (seasons-forecast) and make the modifications there. I 
>> usually use the wee_reports utility to generate the html when I make 
>> changes to the skin.
>>
>> Please let us know if you have any questions.
>>
>> Doug
>> www.largoweather.com
>>
>>
>> On Friday, June 10, 2022 at 10:22:59 AM UTC-4 RobbH wrote:
>>
>>> This is certainly not what you are looking for, but it is what I use to 
>>> get NWS forecasts.
>>>
>>> Here is a url for a forecast for a randomly selected location:
>>>
>>>
>>> https://forecast.weather.gov/MapClick.php?lat=41.177010&lon=-73.141963&unit=0&lg=english&FcstType=text&TextType=2
>>>
>>> Note where latitude and longitude are inserted. "TextType=2" at the end 
>>> tells the server to include forecast graphics.
>>>
>>> Several times a day, a cron job uses PhantomJS  to 
>>> retrieve that page and create an jpeg of the forecast graphics, which is 
>>> then displayed on my weewx home page.
>>>
>>> It usually works well enough for my purposes, but there are times when 
>>> the forecast page is down, so I end up with a blank rectangle on the weewx 
>>> page.
>>>
>>>
>>>
>>> On Wednesday, June 8, 2022 at 12:16:33 PM UTC-4 Timothy Reaves wrote:
>>>
 Hello all.  I'm using the latest version running on a Pi 4, with a 
 Davis Vantage Pro.  I've had my site configured to use Aeris for 
 forecasting, and have never really liked it.  It just isn't as accurate as 
 the NWS.  But I stuck with it.  Then last week, the Aeris forecast for my 
 sight started diverging significantly not only from the NWS, but also from 
 the actual Aeris site (which following the forecast link).  I don't know 
 what's going on, so I thought I'd jut stop using it.

 So I installed the Forecast user module.  When I start weewx now, it 
 fails to load with the

Re: [weewx-user] Re: Help with forecast

['John Kline' via weewx-user]

This looks like a clear case of forecast being pointed to the wrong database.

Please send the data_binding line in the [forecast[ section of weewx.conf.
Also send the [DataBindings] section of weewx.conf.

> On Jun 13, 2022, at 6:49 AM, Timothy Reaves  
> wrote:
> 
> Thank you both for the responses.
> 
> Doug, that is the extension I wrote this post about.  I have followed the 
> instructions, and receive the error I'd posted. So I have all of the 
> configuration that the plugin lists.  When I enable the archive_service, I 
> get the error.  So for some reason it doesn't seem to be connecting to the 
> correct database.  Here is the snippet from my configuration regarding the 
> databases:
> 
> [Databases]
> 
> # A SQLite database is simply a single file
> [[archive_sqlite]]
> database_name = weewx.sdb
> database_type = SQLite
> 
> # MySQL
> [[archive_mysql]]
> database_name = weewx
> database_type = MySQL
> 
> [[forecast_sqlite]]
> database_type = SQLite
> database_name = forecast.sdb
> 
> [[forecast_mysql]]
> database_type = MySql
> database_name = forecast
> 
>> On Friday, June 10, 2022 at 11:22:26 AM UTC-4 do...@dougjenkins.com wrote:
>> Tim:
>> 
>> The forecast module uses a completely different schema and database. What 
>> you need to do is configure the module to a separate database and in your 
>> skin, bring in the data to be presented.
>> 
>> I personally use John Kline's weewx forecast driver ( GitHub - 
>> chaunceygardiner/weewx-forecast: forecasting extension for weewx) as it is 
>> being maintained and it works with the latest version of WeeWX (v4.8). You 
>> will need to look at the sample pages that accompany the driver and 
>> integrate the cheetah template code into your skin. 
>> 
>> Best practice is to copy your existing skin folder (eg seasons) to a 
>> separate folder (seasons-forecast) and make the modifications there. I 
>> usually use the wee_reports utility to generate the html when I make changes 
>> to the skin.
>> 
>> Please let us know if you have any questions.
>> 
>> Doug
>> www.largoweather.com
>> 
>> 
>>> On Friday, June 10, 2022 at 10:22:59 AM UTC-4 RobbH wrote:
>>> This is certainly not what you are looking for, but it is what I use to get 
>>> NWS forecasts.
>>> 
>>> Here is a url for a forecast for a randomly selected location:
>>> 
>>> https://forecast.weather.gov/MapClick.php?lat=41.177010&lon=-73.141963&unit=0&lg=english&FcstType=text&TextType=2
>>> 
>>> Note where latitude and longitude are inserted. "TextType=2" at the end 
>>> tells the server to include forecast graphics.
>>> 
>>> Several times a day, a cron job uses PhantomJS to retrieve that page and 
>>> create an jpeg of the forecast graphics, which is then displayed on my 
>>> weewx home page.
>>> 
>>> It usually works well enough for my purposes, but there are times when the 
>>> forecast page is down, so I end up with a blank rectangle on the weewx page.
>>> 
>>> 
>>> 
 On Wednesday, June 8, 2022 at 12:16:33 PM UTC-4 Timothy Reaves wrote:
 Hello all.  I'm using the latest version running on a Pi 4, with a Davis 
 Vantage Pro.  I've had my site configured to use Aeris for forecasting, 
 and have never really liked it.  It just isn't as accurate as the NWS.  
 But I stuck with it.  Then last week, the Aeris forecast for my sight 
 started diverging significantly not only from the NWS, but also from the 
 actual Aeris site (which following the forecast link).  I don't know 
 what's going on, so I thought I'd jut stop using it.
 
 So I installed the Forecast user module.  When I start weewx now, it fails 
 to load with the error below.  In looking at the code, the database schema 
 isn't matching the extensions in-memory schema.  Don't know why.
 
 Has anyone an example of using NWS forecasts instead of Aeris?  Or can 
 provide any other ideas to troubleshoot?
 
 Thanks.
 
 Jun  8 10:12:34 pi4home weewx[12748] CRITICAL __main__:   
 Exception: NWS: schema mismatch: ['dateTime', 'usUnits', 'interval', 
 'altimeter', 'appTemp', 'appTemp1', 'barometer', 'batteryStatus1', 
 'batteryStatus2', 'batteryStatus3', 'batteryStatus4', 'batteryStatus5', 
 'batteryStatus6', 'batteryStatus7', 'batteryStatus8', 'cloudbase', 'co', 
 'co2', 'consBatteryVoltage', 'dewpoint', 'dewpoint1', 'ET', 'extraHumid1', 
 'extraHumid2', 'extraHumid3', 'extraHumid4', 'extraHumid5', 'extraHumid6', 
 'extraHumid7', 'extraHumid8', 'extraTemp1', 'extraTemp2', 'extraTemp3', 
 'extraTemp4', 'extraTemp5', 'extraTemp6', 'extraTemp7', 'extraTemp8', 
 'forecast', 'hail', 'hailBatteryStatus', 'hailRate', 'heatindex', 
 'heatindex1', 'heatingTemp', 'heatingVoltage', 'humidex', 'humidex1', 
 'inDewpoint', 'inHumidity', 'inTemp', 'inTempBatteryStatus', 'leafTemp1', 
 'leafTemp2', 'leafWet1', 'leafWet2', 'lightning_distance', 

[weewx-user] Re: GW1000 causing critical errors

[gjr80]

Hi Chris,

What version of the GW1000 (now Ecowitt Gateway) driver are you using? It 
appears from the code in error trace you provided that you have v0.3.1, the 
last release was v0.4.2 and we are testing v0.5.0b5 now. There have been 
substantial changes by Ecowitt to battery state handling since v0.3.1 was 
released. I suggest you upgrade to v0.5.0b5 which can be found on GitHub 
here .

Gary.

On Wednesday, 15 June 2022 at 11:38:06 UTC+10 cei...@gmail.com wrote:

> Hello all,
>
> I noticed that my web pages have stopped working and I've looked into the 
> logs and I see this:
>
> Jun 14 19:58:46 rocky1 journal[42479]: weewx[42479] CRITICAL user.gw1000: 
>   Traceback (most recent call last):
> Jun 14 19:58:47 rocky1 journal[42479]: weewx[42479] CRITICAL user.gw1000: 
> File "/usr/share/weewx/user/gw1000.py", line 2827, in run
> Jun 14 19:58:47 rocky1 journal[42479]: weewx[42479] CRITICAL user.gw1000: 
>   self.client.collect_sensor_data()
> Jun 14 19:58:47 rocky1 journal[42479]: weewx[42479] CRITICAL user.gw1000: 
> File "/usr/share/weewx/user/gw1000.py", line 2282, in 
> collect_sensor_data
> Jun 14 19:58:47 rocky1 journal[42479]: weewx[42479] CRITICAL user.gw1000: 
>   queue_data = self.get_live_sensor_data()
> Jun 14 19:58:47 rocky1 journal[42479]: weewx[42479] CRITICAL user.gw1000: 
> File "/usr/share/weewx/user/gw1000.py", line 2329, in 
> get_live_sensor_data
> Jun 14 19:58:47 rocky1 journal[42479]: weewx[42479] CRITICAL user.gw1000: 
>   self.update_sensor_id_data()
> Jun 14 19:58:47 rocky1 journal[42479]: weewx[42479] CRITICAL user.gw1000: 
> File "/usr/share/weewx/user/gw1000.py", line 2344, in 
> update_sensor_id_data
> Jun 14 19:58:47 rocky1 journal[42479]: weewx[42479] CRITICAL user.gw1000: 
>   self.sensors_obj.set_sensor_id_data(sensor_id_data)
> Jun 14 19:58:47 rocky1 journal[42479]: weewx[42479] CRITICAL user.gw1000: 
> File "/usr/share/weewx/user/gw1000.py", line 4108, in 
> set_sensor_id_data
> Jun 14 19:58:47 rocky1 journal[42479]: weewx[42479] CRITICAL user.gw1000: 
>   batt_fn = Gw1000Collector.sensor_ids[data[index:index + 
> 1]]['batt_fn']
> Jun 14 19:58:47 rocky1 journal[42479]: weewx[42479] CRITICAL user.gw1000: 
>   KeyError: b'0'
>
> I recently upgraded the firmware, so I wonder if that is what is causing 
> this error. The firmware version is GW1000B_V1.7.3 connected to an Ambient 
> Weather WS-5000. 
>
> I've found this error mentioned in web searches, but I'm not sure of what 
> I can do. I did a wee_config --reconfigure --driver=user.gw1000, but I 
> still get the error on startup (starting from a command line: sudo weewxd 
> /etc/weewx/weewx.conf).
>
> I'm happy to provide any information requested and thank you for your kind 
> attention.
>
>  - chris
>

-- 
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/2716d810-4d82-42c7-b5f9-7c2e3be57b3en%40googlegroups.com.