Re: [weewx-user] Re: Error with weewx-SteelSeries skin

2024-01-20 Thread gjr80 
The error message is very non-specific (as Cheetah errors often are), 
though the error is likely caused by a required field being None or 
non-existent. When asking for log extract I was not looking for errors in 
the log, but rather looking for details of your setup including station 
type, driver and WeeWX configuration that would hopefully give a clue as to 
the field causing the problem. Without any further information there is 
little else I can add.

Gary
On Saturday 20 January 2024 at 20:30:04 UTC+10 remy.l...@gmail.com wrote:

> Thank-you...
> Sorry but in the syslog, there is only that...
> And systematically same error at each packetsloop !
> if the option is disabled in weewx.conf obviously no problem. :-(
>
> Jan 16 13:56:19 localhost wee_reports[62658] INFO user.alarm_multi: Alarm 
> set for expression 18: "extraTemp3 is not None and extraTemp3 >= 80.6"
> Jan 16 13:56:19 localhost wee_reports[62658] INFO user.healthchecks: 
> healthchecks: Using url 
> https://hc-ping.com/---Spw/weewx-record
> Jan 16 13:56:20 localhost wee_reports[62658] INFO user.historygenerator: 
> historygenerator.py: Generated 6 tables in 0.42 seconds
> Jan 16 13:56:32 localhost wee_reports[62658] INFO weewx.cheetahgenerator: 
> Generated 13 files for report SeasonsReport2 in 12.56 seconds
> Jan 16 13:56:35 localhost wee_reports[62658] INFO weewx.imagegenerator: 
> Generated 28 images for report SeasonsReport2 in 2.95 seconds
> Jan 16 13:56:35 localhost wee_reports[62658] INFO weewx.reportengine: 
> Copied 5 files to /var/www/html/weewx
> Jan 16 13:56:35 localhost wee_reports[62658] INFO weewx.reportengine: 
> Copied 6 files to /var/www/html/weewx/ss
> Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator: 
> Evaluation of template /etc/weewx/skins/ss/gauge-data.txt.tmpl failed with 
> exception ''
> Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator: 
>  Ignoring template /etc/weewx/skins/ss/gauge-data.txt.tmpl
> Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator: 
>  Reason: 'UnknownType' object is not subscriptable
> Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator: 
>   Traceback (most recent call last):
> Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in 
> generate
> Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator: 
>   unicode_string = compiled_template.respond()
> Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator: 
> File "_etc_weewx_skins_ss_gauge_data_txt_tmpl.py", line 142, in 
> respond
> Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator: 
> File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
> 1446, in getVar
> Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator: 
>   return valueFromSearchList(
> Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator: 
> File "/usr/share/weewx/weewx/units.py", line 1094, in raw
> Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator: 
>   return self.value_t[0]
> Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator: 
>   TypeError: 'UnknownType' object is not subscriptable
> Jan 16 13:56:36 localhost wee_reports[62658] INFO weewx.cheetahgenerator: 
> Generated 1 files for report SteelSeries in 0.76 seconds
> Jan 16 13:56:37 localhost wee_reports[62658] INFO weewx.imagegenerator: 
> Generated 11 images for report SteelSeries in 0.91 seconds
> Jan 16 13:56:40 localhost wee_reports[62658] INFO weewx.cheetahgenerator: 
> Generated 2 files for report wxobs in 3.66 seconds
> Jan 16 13:56:40 localhost wee_reports[62658] INFO weewx.reportengine: 
> Copied 6 files to /var/www/html/weewx/wxobs
> Jan 16 13:56:54 localhost wee_reports[62658] INFO weewx.reportengine: 
> ftpgenerator: Ftp'd 54 files in 13.22 seconds
>
> *Rémy LAVABRE*
>
>
> Le sam. 20 janv. 2024 à 10:51, gjr80  a écrit :
>
>> Impossible to say with such a small log extract. Please refer to the 
>> section How to get a good, useful log 
>> 
>>  
>> on the Help! Posting to weewx user wiki page 
>> 
>> .
>>
>> Gary
>> On Saturday 20 January 2024 at 19:40:47 UTC+10 remy.l...@gmail.com wrote:
>>
>>> -> https://github.com/gjr80/weewx-steelseries
>>> Good morning,
>>>
>>> I don't understand the reason and why of the error that occurs with my 
>>> version 4.10.2 of weewx and the 'SteelSeries' Skin.
>>>
>>> Can anyone help me and tell me what's going on?
>>> THANKS
>>>
>>>
>>>
>>> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator: 
>>>  Ignoring template /etc/weewx/skins/ss/gauge-data

Re: [weewx-user] Slow Report Generation after Upgrade from 4.10.2 to 5..0

2024-01-20 Thread Richard Whitcombe 
Just woke up so delayed reply but yep thats exactly the case.

>From index.html.tmpl:

 
#if $current.appTemp.has_data
$obs.label.feels_like: $current.appTemp
#end if


Previously this would display the "feels like" temperature below the 
current temperature.  Now theres simply nothing shown which suggests no 
data.
I cant remember if it appeared on v5 but before i fixed the database by 
adding AppTemp and calc-missing though.

Can see how this could more be a skin problem than weewx related though so 
might not be applicable to this group.
On Sunday 21 January 2024 at 04:06:16 UTC+9 vince wrote:

> In index.html.tmpl..
>
> #if $current.appTemp.has_data
>  $obs.label.feels_like: 
> $current.appTemp
> #end if
>
> So he has no current appTemp value apparently.
>
> On Saturday, January 20, 2024 at 9:29:24 AM UTC-8 Colin Larsen wrote:
>
>> I guess he means this "feels like" which as far as I know is a 
>> derived/calculated field in the skin
>>
>> [image: image.png]
>>
>> On Sun, 21 Jan 2024 at 03:13, Tom Keffer  wrote:
>>
>>> Richard, you're going to have to give us more information than this. The 
>>> only reference to "feels like" that I can find in the Belchertown skin has 
>>> been commented out. Where are you seeing this?
>>>
>>> On Fri, Jan 19, 2024 at 7:25 PM Richard Whitcombe  
>>> wrote:
>>>
 Actually follow up that ive only just noticed.
 Since performing this fix ive lost the "Feels like" temperature display 
 on my skin on all pages.

 On Friday 19 January 2024 at 19:47:31 UTC+9 Richard Whitcombe wrote:

> I just did AppTemperature but its working for me.
> Although i dont think i use any of the other columns as my station 
> doesnt provide it.
>
> Missing data calculations took about 8 minutes for 7 years of data on 
> a Pi4.
>
> On Friday 19 January 2024 at 19:14:09 UTC+9 mh081...@gmail.com wrote:
>
>> Hi,
>>
>> as i read in the other posts about this Problem i doing now following.
>>
>> weectl database add-column appTemp
>> weectl database add-column cloudbase
>> weectl database add-column visibility
>> weectl database add-column windrun
>> weectl database add-column cloud_cover
>> weectl database add-column aqi
>>
>> weectl database calc-missing
>>
>> Answer all wit 'y'
>>
>> Now it seems that the Problem was solved. Belchertown Reports was 
>> generated in about 6 seconds. Thanks @vince for your right direction.
>> ##
>> Jan 19 11:09:50 wetter weewxd[293936]: INFO weewx.engine: Loading 
>> station type Vantage (weewx.drivers.vantage)
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: StdConvert 
>> target unit is 0x1
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.wxservices: 
>> StdWXCalculate will use data binding wx_binding
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Archive 
>> will use data binding wx_binding
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Record 
>> generation will be attempted in 'hardware'
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Using 
>> archive interval of 300 seconds (specified by hardware)
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: 
>> StationRegistry: Registration not requested.
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: 
>> Wunderground-PWS: Data for station IMECKLEN47 will be posted
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: PWSWeather: 
>> Data for station MHROSTOCK will be posted
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: CWOP: 
>> Posting not enabled.
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: WOW: Posting 
>> not enabled.
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: AWEKAS: 
>> Posting not enabled.
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: service 
>> version is 0.23
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: binding to 
>> ['archive', 'loop']
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: topic is 
>> weather
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: desired unit 
>> system is METRIC
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: data will be 
>> uploaded to mqtt://pi:x...@gw.martenhinrichs.de:8883/ 
>> 
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: network 
>> encryption/authentication will be attempted
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: 'pyephem' 
>> detected, extended almanac data is available
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO __main__: Starting up 
>> wee

[weewx-user] Re: Different time for report generation and sending to website via rsync?

2024-01-20 Thread bell...@gmail.com 
Checkout, http://www.weewx.com/docs/5.0/custom/report-scheduling/

On Saturday 20 January 2024 at 15:37:10 UTC-5 Tomasz Lewicki wrote:

> Hello Weewx users.
>
> I'd like to know if it is possible to set different time (interval) for 
> generating reports:
>
> [StdArchive]
> archive_interval = 300
>
> and for syncing the files to website by rsync? My station is installed in 
> a place where I have only cellular internet (LTE) with monthly transfer 
> limits so I send them every 10 minutes (archive-interval = 600). I'd like 
> to have database records every 5 minutes but sending data to website every 
> 10 minutes. I hope I explained it properly. 
>

-- 
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/7364022c-b7b1-412f-b14d-0155ae9b1321n%40googlegroups.com.

Re: [weewx-user] Slow Report Generation after Upgrade from 4.10.2 to 5..0

2024-01-20 Thread bell...@gmail.com 
Any’ skin is an over generalization. It depends what the skin is doing with 
calculated/synthetic observations. On a pi 3B+ and Blaine’s db (seems to be 
the defacto test data), WeeWX-JAS took approximately 24 minutes to generate 
charts with appTemp on its first run. On its second run, approximately 60 
seconds.

Without appTemp, run one took approximately 5 1/2 minutes and run two took 
approximately 50 seconds.

The first run is when WeeWX-JAS pulls historical data. After that it just 
pulls recent/changing data for the appropriate aggregate interval. So in 
both cases on a new day, a new aggregate interval starts and therefore more 
data/processing would occur. I think it would still complete in a typical 
300 second archive period.

For reference:
Run one with appTemp
~/small-schema.weewx-data $ date; python3 ~/weewx/src/weectl.py report run 
jas --config ~/small-schema.weewx-data/report.conf; date
Sat 20 Jan 2024 02:43:05 PM EST
Using configuration file /home/pi/small-schema.weewx-data/report.conf
The following reports will be run: jas
Generating as of last timestamp in the database.
Done.
Sat 20 Jan 2024 03:07:08 PM EST

Run two with appTemp
~/small-schema.weewx-data $ date; python3 ~/weewx/src/weectl.py report run 
jas --config ~/small-schema.weewx-data/report.conf; date
Sat 20 Jan 2024 03:07:27 PM EST
Using configuration file /home/pi/small-schema.weewx-data/report.conf
The following reports will be run: jas
Generating as of last timestamp in the database.
Done.
Sat 20 Jan 2024 03:08:27 PM EST

Run one without appTemp.
~/small-schema.weewx-data $ date; python3 ~/weewx/src/weectl.py report run 
jas --config ~/small-schema.weewx-data/report.conf; date
Sat 20 Jan 2024 03:12:57 PM EST
Using configuration file /home/pi/small-schema.weewx-data/report.conf
The following reports will be run: jas
Generating as of last timestamp in the database.
Done.
Sat 20 Jan 2024 03:18:29 PM EST

Run two without appTemp.
~/small-schema.weewx-data $ date; python3 ~/weewx/src/weectl.py report run 
jas --config ~/small-schema.weewx-data/report.conf; date
Sat 20 Jan 2024 03:18:41 PM EST
Using configuration file /home/pi/small-schema.weewx-data/report.conf
The following reports will be run: jas
Generating as of last timestamp in the database.
Done.
Sat 20 Jan 2024 03:19:30 PM EST

rich

On Friday 19 January 2024 at 10:34:33 UTC-5 Cameron D wrote:

> On Friday 19 January 2024 at 4:37:05 am UTC+10 vince wrote:
>
>
> The pattern so far seems to be (a) Belchertown and (b) certain drivers 
> that might not have complete measurement sets.   I see Acurite and 
> Interceptor in a couple reports if I remember correctly.
>
>
>  No, it is *any *skin that tries to plot the derived parameters - the 
> common factor is if they are not in the DB. I reported the same with the 
> default standard Seasons skin.
>

-- 
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/88d9ce96-b741-45d3-a301-2607cbefe54dn%40googlegroups.com.

[weewx-user] Different time for report generation and sending to website via rsync?

2024-01-20 Thread Tomasz Lewicki 
Hello Weewx users.

I'd like to know if it is possible to set different time (interval) for 
generating reports:

[StdArchive]
archive_interval = 300

and for syncing the files to website by rsync? My station is installed in a 
place where I have only cellular internet (LTE) with monthly transfer 
limits so I send them every 10 minutes (archive-interval = 600). I'd like 
to have database records every 5 minutes but sending data to website every 
10 minutes. I hope I explained it properly. 

-- 
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/8347de7a-4ea5-443a-9224-503804f5413an%40googlegroups.com.

Re: [weewx-user] APT upgrade to WeeWX 5.0: Belchertown skin no longer working

2024-01-20 Thread matthew wall 
On Saturday, January 20, 2024 at 11:21:51 AM UTC-5 kevinjc...@gmail.com 
wrote:

Very good to know as I plan on doing the upgrade myself. One question, how 
do you mean you upgrade the conf file? Did it not upgrade with the rest of 
the upgrade? 


the configuration file and the skins are explicitly *not* upgraded when you 
upgrade weewx

this is to reduce the chance of breaking anything, and to let you choose to 
upgrade them only if you want to

in the case of the config file, there is almost never a need to upgrade 
it.  when new features are added to weewx, they have sane defaults.

in the case of skins, you only need to upgrade if a specific skin has new 
features/functionality that you want, and then only when you are confident 
that upgrading the skin will not break your customizations (if any)

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3801a4d3-46ed-452d-b08f-978f3ff9c888n%40googlegroups.com.

Re: [weewx-user] Slow Report Generation after Upgrade from 4.10.2 to 5..0

2024-01-20 Thread vince 
In index.html.tmpl..

#if $current.appTemp.has_data
 $obs.label.feels_like: 
$current.appTemp
#end if

So he has no current appTemp value apparently.

On Saturday, January 20, 2024 at 9:29:24 AM UTC-8 Colin Larsen wrote:

> I guess he means this "feels like" which as far as I know is a 
> derived/calculated field in the skin
>
> [image: image.png]
>
> On Sun, 21 Jan 2024 at 03:13, Tom Keffer  wrote:
>
>> Richard, you're going to have to give us more information than this. The 
>> only reference to "feels like" that I can find in the Belchertown skin has 
>> been commented out. Where are you seeing this?
>>
>> On Fri, Jan 19, 2024 at 7:25 PM Richard Whitcombe  
>> wrote:
>>
>>> Actually follow up that ive only just noticed.
>>> Since performing this fix ive lost the "Feels like" temperature display 
>>> on my skin on all pages.
>>>
>>> On Friday 19 January 2024 at 19:47:31 UTC+9 Richard Whitcombe wrote:
>>>
 I just did AppTemperature but its working for me.
 Although i dont think i use any of the other columns as my station 
 doesnt provide it.

 Missing data calculations took about 8 minutes for 7 years of data on a 
 Pi4.

 On Friday 19 January 2024 at 19:14:09 UTC+9 mh081...@gmail.com wrote:

> Hi,
>
> as i read in the other posts about this Problem i doing now following.
>
> weectl database add-column appTemp
> weectl database add-column cloudbase
> weectl database add-column visibility
> weectl database add-column windrun
> weectl database add-column cloud_cover
> weectl database add-column aqi
>
> weectl database calc-missing
>
> Answer all wit 'y'
>
> Now it seems that the Problem was solved. Belchertown Reports was 
> generated in about 6 seconds. Thanks @vince for your right direction.
> ##
> Jan 19 11:09:50 wetter weewxd[293936]: INFO weewx.engine: Loading 
> station type Vantage (weewx.drivers.vantage)
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: StdConvert 
> target unit is 0x1
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.wxservices: 
> StdWXCalculate will use data binding wx_binding
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Archive will 
> use data binding wx_binding
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Record 
> generation will be attempted in 'hardware'
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Using 
> archive interval of 300 seconds (specified by hardware)
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: 
> StationRegistry: Registration not requested.
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: 
> Wunderground-PWS: Data for station IMECKLEN47 will be posted
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: PWSWeather: 
> Data for station MHROSTOCK will be posted
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: CWOP: Posting 
> not enabled.
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: WOW: Posting 
> not enabled.
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: AWEKAS: 
> Posting not enabled.
> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: service version 
> is 0.23
> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: binding to 
> ['archive', 'loop']
> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: topic is weather
> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: desired unit 
> system is METRIC
> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: data will be 
> uploaded to mqtt://pi:x...@gw.martenhinrichs.de:8883/ 
> 
> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: network 
> encryption/authentication will be attempted
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: 'pyephem' 
> detected, extended almanac data is available
> Jan 19 11:09:53 wetter weewxd[293936]: INFO __main__: Starting up 
> weewx version 5.0.0
> Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.engine: Clock error 
> is 2.69 seconds (positive is fast)
> Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.engine: Using 
> binding 'wx_binding' to database 'weewx.sdb'
> Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.manager: Starting 
> backfill of daily summaries
> Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.manager: Daily 
> summaries up to date
> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.wxxtypes: Type 
> beaufort has been deprecated. Use unit beaufort instead.
> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added 
> record 2024-01-19 10:50:00 CET (1705657800) to database 'weewx.sdb'
> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added 
> record 2024-01

Re: [weewx-user] Slow Report Generation after Upgrade from 4.10.2 to 5..0

2024-01-20 Thread Colin Larsen 
I guess he means this "feels like" which as far as I know is a
derived/calculated field in the skin

[image: image.png]

On Sun, 21 Jan 2024 at 03:13, Tom Keffer  wrote:

> Richard, you're going to have to give us more information than this. The
> only reference to "feels like" that I can find in the Belchertown skin has
> been commented out. Where are you seeing this?
>
> On Fri, Jan 19, 2024 at 7:25 PM Richard Whitcombe 
> wrote:
>
>> Actually follow up that ive only just noticed.
>> Since performing this fix ive lost the "Feels like" temperature display
>> on my skin on all pages.
>>
>> On Friday 19 January 2024 at 19:47:31 UTC+9 Richard Whitcombe wrote:
>>
>>> I just did AppTemperature but its working for me.
>>> Although i dont think i use any of the other columns as my station
>>> doesnt provide it.
>>>
>>> Missing data calculations took about 8 minutes for 7 years of data on a
>>> Pi4.
>>>
>>> On Friday 19 January 2024 at 19:14:09 UTC+9 mh081...@gmail.com wrote:
>>>
 Hi,

 as i read in the other posts about this Problem i doing now following.

 weectl database add-column appTemp
 weectl database add-column cloudbase
 weectl database add-column visibility
 weectl database add-column windrun
 weectl database add-column cloud_cover
 weectl database add-column aqi

 weectl database calc-missing

 Answer all wit 'y'

 Now it seems that the Problem was solved. Belchertown Reports was
 generated in about 6 seconds. Thanks @vince for your right direction.
 ##
 Jan 19 11:09:50 wetter weewxd[293936]: INFO weewx.engine: Loading
 station type Vantage (weewx.drivers.vantage)
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: StdConvert
 target unit is 0x1
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.wxservices:
 StdWXCalculate will use data binding wx_binding
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Archive will
 use data binding wx_binding
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Record
 generation will be attempted in 'hardware'
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Using archive
 interval of 300 seconds (specified by hardware)
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx:
 StationRegistry: Registration not requested.
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx:
 Wunderground-PWS: Data for station IMECKLEN47 will be posted
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: PWSWeather:
 Data for station MHROSTOCK will be posted
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: CWOP: Posting
 not enabled.
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: WOW: Posting
 not enabled.
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: AWEKAS:
 Posting not enabled.
 Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: service version
 is 0.23
 Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: binding to
 ['archive', 'loop']
 Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: topic is weather
 Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: desired unit
 system is METRIC
 Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: data will be
 uploaded to mqtt://pi:x...@gw.martenhinrichs.de:8883/
 
 Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: network
 encryption/authentication will be attempted
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: 'pyephem'
 detected, extended almanac data is available
 Jan 19 11:09:53 wetter weewxd[293936]: INFO __main__: Starting up weewx
 version 5.0.0
 Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.engine: Clock error
 is 2.69 seconds (positive is fast)
 Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.engine: Using binding
 'wx_binding' to database 'weewx.sdb'
 Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.manager: Starting
 backfill of daily summaries
 Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.manager: Daily
 summaries up to date
 Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.wxxtypes: Type
 beaufort has been deprecated. Use unit beaufort instead.
 Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record
 2024-01-19 10:50:00 CET (1705657800) to database 'weewx.sdb'
 Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record
 2024-01-19 10:50:00 CET (1705657800) to daily summary in 'weewx.sdb'
 Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record
 2024-01-19 10:55:00 CET (1705658100) to database 'weewx.sdb'
 Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record
 2024-01-19 10:55:00 CET (1705658100) to daily summary in 'weewx.sdb'
 Jan 19 11:09:56 wetter weewxd[293936]: IN

Re: [weewx-user] APT upgrade to WeeWX 5.0: Belchertown skin no longer working

2024-01-20 Thread Kevin Crivelli 
Very good to know as I plan on doing the upgrade myself. One question, how
do you mean you upgrade the conf file? Did it not upgrade with the rest of
the upgrade?

On Sat, Jan 20, 2024, 6:39 AM c bosshard  wrote:

> Just FYI
>
> APT upgraded my installation to WeeWx 5.0 and my Belchertown Skin 1.2
> stopped working.
> Everything else was still working and processing data...
>
> What I did to fix it:
> - Installed the latest Belchertown Skin 1.3.1 using weectl
> - Upgdated my weewx.conf file to V5.0
>
> Thank you to the WeeWx team for your hard work, happy user since 2016!
>
> --
> 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/6405f568-622e-4830-8eaf-7914358c8ee2n%40googlegroups.com
> 
> .
>

-- 
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/CAG3iCAwDc%3DE5uvHeembR%2B%3DP4BuEOh%3Du-8QecNBiv9N-VQ-U1BQ%40mail.gmail.com.

Re: [weewx-user] Slow Report Generation after Upgrade from 4.10.2 to 5..0

2024-01-20 Thread Tom Keffer 
Richard, you're going to have to give us more information than this. The
only reference to "feels like" that I can find in the Belchertown skin has
been commented out. Where are you seeing this?

On Fri, Jan 19, 2024 at 7:25 PM Richard Whitcombe 
wrote:

> Actually follow up that ive only just noticed.
> Since performing this fix ive lost the "Feels like" temperature display on
> my skin on all pages.
>
> On Friday 19 January 2024 at 19:47:31 UTC+9 Richard Whitcombe wrote:
>
>> I just did AppTemperature but its working for me.
>> Although i dont think i use any of the other columns as my station doesnt
>> provide it.
>>
>> Missing data calculations took about 8 minutes for 7 years of data on a
>> Pi4.
>>
>> On Friday 19 January 2024 at 19:14:09 UTC+9 mh081...@gmail.com wrote:
>>
>>> Hi,
>>>
>>> as i read in the other posts about this Problem i doing now following.
>>>
>>> weectl database add-column appTemp
>>> weectl database add-column cloudbase
>>> weectl database add-column visibility
>>> weectl database add-column windrun
>>> weectl database add-column cloud_cover
>>> weectl database add-column aqi
>>>
>>> weectl database calc-missing
>>>
>>> Answer all wit 'y'
>>>
>>> Now it seems that the Problem was solved. Belchertown Reports was
>>> generated in about 6 seconds. Thanks @vince for your right direction.
>>> ##
>>> Jan 19 11:09:50 wetter weewxd[293936]: INFO weewx.engine: Loading
>>> station type Vantage (weewx.drivers.vantage)
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: StdConvert
>>> target unit is 0x1
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.wxservices:
>>> StdWXCalculate will use data binding wx_binding
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Archive will
>>> use data binding wx_binding
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Record
>>> generation will be attempted in 'hardware'
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Using archive
>>> interval of 300 seconds (specified by hardware)
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx:
>>> StationRegistry: Registration not requested.
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx:
>>> Wunderground-PWS: Data for station IMECKLEN47 will be posted
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: PWSWeather:
>>> Data for station MHROSTOCK will be posted
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: CWOP: Posting
>>> not enabled.
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: WOW: Posting
>>> not enabled.
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: AWEKAS: Posting
>>> not enabled.
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: service version
>>> is 0.23
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: binding to
>>> ['archive', 'loop']
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: topic is weather
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: desired unit
>>> system is METRIC
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: data will be
>>> uploaded to mqtt://pi:x...@gw.martenhinrichs.de:8883/
>>> 
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: network
>>> encryption/authentication will be attempted
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: 'pyephem'
>>> detected, extended almanac data is available
>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO __main__: Starting up weewx
>>> version 5.0.0
>>> Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.engine: Clock error is
>>> 2.69 seconds (positive is fast)
>>> Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.engine: Using binding
>>> 'wx_binding' to database 'weewx.sdb'
>>> Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.manager: Starting
>>> backfill of daily summaries
>>> Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.manager: Daily
>>> summaries up to date
>>> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.wxxtypes: Type
>>> beaufort has been deprecated. Use unit beaufort instead.
>>> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record
>>> 2024-01-19 10:50:00 CET (1705657800) to database 'weewx.sdb'
>>> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record
>>> 2024-01-19 10:50:00 CET (1705657800) to daily summary in 'weewx.sdb'
>>> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record
>>> 2024-01-19 10:55:00 CET (1705658100) to database 'weewx.sdb'
>>> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record
>>> 2024-01-19 10:55:00 CET (1705658100) to daily summary in 'weewx.sdb'
>>> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record
>>> 2024-01-19 11:00:00 CET (1705658400) to database 'weewx.sdb'
>>> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record
>>> 2024-01-19 11:00:00 CET (1705658400) to daily summary in 'weewx.sdb'
>>> Jan 19 11:09:56 wetter wee

[weewx-user] Aeris Soil Data Import

2024-01-20 Thread 'Anthony B' via weewx-user 
Hi there! I am a fairly new user. I currently have my station reporting to 
multiple services, I have been able to add a few extra temp/humidity 
sensors, have configured the Belchertown skin and added a few extra graphs 
for different sensor data, and have imported previous station history from 
WU to fill the gaps from before running Weewx. I only share all this as a 
barometer (no pun intended) of what I've been able to work through 
technically. 

With the Belchertown skin setup, I have established an account with Aeris 
weather. As a result, I saw I have the ability to pull a custom API. I have 
an API from Aeris to provide soil temperature data at different depths that 
I would like to pull in to my station data and Belchertown reports. 

I am at a bit of a loss of what steps I need to take (and which files to 
add/edit) to make this happen. Is this a relatively easy thing to 
accomplish or am I in a bit over my head? The only python/coding experience 
I have is trial and error messing with things such as weewx. Thanks in 
advance for any help! 

-- 
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/d25ceeaf-4d42-4b89-86ad-48523eed1842n%40googlegroups.com.

Re: [weewx-user] I'm desperate to fix my NOAA reports. Can I please pay someone to help fix my database and recover this data?

2024-01-20 Thread WindnFog 
Rewording Tom's post to align with one of my professors decades ago, "That 
will work, but let's do it the right way." Using 'weectl database' 
(followed by the proper parameters) is the right way. Humidex is now stored 
in the database, and '$alltime.humidex.max' takes a split second to return 
the correct result. My Rube Goldberg software machine has been dismantled.

- Paul VE1DX

On Friday, January 19, 2024 at 10:55:50 AM UTC-4 Tom Keffer wrote:

> I mean this in the gentlest way, but this is basically what the SQLite 
> database is doing for you: saving various values in a file where they can 
> be retrieved via a general query statement.
>
> On Fri, Jan 19, 2024 at 6:16 AM WindnFog  wrote:
>
>> I encountered the same problem trying to calculate the all time humidex 
>> in the index.html.tmpl template.  This was taking about 3 minutes on a Pi 
>> 4. Rather than add humidex to the database (probably the best solution), I 
>> calculated all-time humidex once a day using a small program and invoking 
>> it with cron. I saved it in a text file that I could then use the Cheetah 
>> include statement to read it into index.the html.tmpl template.  This runs 
>> in 2 seconds on a Pi 4 and 1 second on a pi 5; if you have an algorithm for 
>> appTemp, a similar approach might work.  I was not comfortable with 
>> modifying the database because that's not my area of expertise:
>>
>> #!/usr/bin/env python3
>> # -*- coding: utf-8 -*-
>>
>> """
>> Program:WeeWX Humidex calculator
>> Author: Paul M Dunphy
>> Date:   12 December 2023
>> Version:1.0.0
>> Description:This script sweeps through the Weewx database and 
>> calculates the 
>> derived parameter humidex for each record.  It then 
>> returns the
>> maximum humidex and the date/time when it occured.  This 
>> takes
>> about 1.5 seconds on a 900,000 record database as opposed 
>> to 3.5
>> minutes by the WeeWX system if the recommended aggregate 
>> values
>> are implemented in the Standard/index.html.tmpl file:
>> 
>> $alltime.humidex.max ($alltime.humidex.max.degree_F) 
>> $alltime.humidex.maxtime.format($ALLTIMEFMT)
>>
>> It's not clear why the weeWX system takes so long.  
>> Possibly
>> because it's doing many other things at the same time.  
>>
>> This runs on a Raspberry Pi 4B (4 GB Ram) using Debian 12
>> """
>>
>> # Required Libraries
>>
>> import sqlite3
>> import math
>> from datetime import datetime
>> import pytz
>> from pytz import timezone
>>
>>
>> def calculate_humidex(temperature, dewpoint):
>> # Constants for the formula
>> k = 273.15  # Conversion factor for Celsius to Kelvin
>>
>> # Convert temperatures to Kelvin
>> temperature + k
>> dewpoint_k = dewpoint + k
>>
>> # Calculate vapor pressure in hPa
>> vapor_pressure = 6.112 * math.exp(5417.7530 * ((1 / 273.16) - (1 / 
>> dewpoint_k)))
>>
>> # Humidex calculation
>> humidex = temperature + ((vapor_pressure - 10) * 0.)
>> return humidex
>>
>>
>> def get_max_humidex(database_path):
>> # Connect to the WeeWX database
>> conn = sqlite3.connect(database_path)
>> cursor = conn.cursor()
>>
>> # Query for temperature, dewpoint, and dateTime for all records
>> query = "SELECT outTemp, dewpoint, dateTime FROM archive"
>> cursor.execute(query)
>>
>> # Variables to track the maximum humidex and its date
>> maximum_humidex = None
>> maximum_humidex_date = None
>>
>> for row in cursor:
>> temperature, dewpoint, date_time = row
>> if temperature is not None and dewpoint is not None:
>> humidex = calculate_humidex(temperature, dewpoint)
>> if maximum_humidex is None or humidex > maximum_humidex:
>> maximum_humidex = humidex
>> maximum_humidex_date = date_time
>>
>> conn.close()
>> return maximum_humidex, maximum_humidex_date
>>
>>
>> def convert_utc_to_ast_adt(utc_datetime):
>> """
>> Convert a UTC datetime to AST or ADT depending on the date.
>>
>> Parameters:
>> utc_datetime (datetime): UTC datetime object.
>>
>> Returns:
>> datetime: Datetime object in AST or ADT.
>> """
>> # Define the time zone for AST/ADT
>> ast_tz = timezone('America/Halifax')
>>
>> # Localize the UTC datetime to the AST/ADT timezone
>> local_datetime = ast_tz.normalize(utc_datetime.astimezone(ast_tz))
>>
>> return local_datetime
>>
>>
>> def format_date(unix_timestamp):
>> """
>> Format a UNIX timestamp into a human-readable string in AST or ADT.
>>
>> Parameters:
>> unix_timestamp (int): UNIX timestamp.
>>
>> Returns:
>> str: Formatted date string.
>> """
>> # Create a UTC datetime from the UNIX timestamp
>> utc_datetime = 
>> datetime.utcfromtimestamp(unix_timestamp).replace(tzin

[weewx-user] APT upgrade to WeeWX 5.0: Belchertown skin no longer working

2024-01-20 Thread c bosshard 
Just FYI

APT upgraded my installation to WeeWx 5.0 and my Belchertown Skin 1.2 
stopped working.
Everything else was still working and processing data...

What I did to fix it:
- Installed the latest Belchertown Skin 1.3.1 using weectl
- Upgdated my weewx.conf file to V5.0

Thank you to the WeeWx team for your hard work, happy user since 2016!

-- 
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/6405f568-622e-4830-8eaf-7914358c8ee2n%40googlegroups.com.

Re: [weewx-user] Re: Error with weewx-SteelSeries skin

2024-01-20 Thread Remy LAVABRE 
Thank-you...
Sorry but in the syslog, there is only that...
And systematically same error at each packetsloop !
if the option is disabled in weewx.conf obviously no problem. :-(

Jan 16 13:56:19 localhost wee_reports[62658] INFO user.alarm_multi: Alarm
set for expression 18: "extraTemp3 is not None and extraTemp3 >= 80.6"
Jan 16 13:56:19 localhost wee_reports[62658] INFO user.healthchecks:
healthchecks: Using url
https://hc-ping.com/---Spw/weewx-record
Jan 16 13:56:20 localhost wee_reports[62658] INFO user.historygenerator:
historygenerator.py: Generated 6 tables in 0.42 seconds
Jan 16 13:56:32 localhost wee_reports[62658] INFO weewx.cheetahgenerator:
Generated 13 files for report SeasonsReport2 in 12.56 seconds
Jan 16 13:56:35 localhost wee_reports[62658] INFO weewx.imagegenerator:
Generated 28 images for report SeasonsReport2 in 2.95 seconds
Jan 16 13:56:35 localhost wee_reports[62658] INFO weewx.reportengine:
Copied 5 files to /var/www/html/weewx
Jan 16 13:56:35 localhost wee_reports[62658] INFO weewx.reportengine:
Copied 6 files to /var/www/html/weewx/ss
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
Evaluation of template /etc/weewx/skins/ss/gauge-data.txt.tmpl failed with
exception ''
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
 Ignoring template /etc/weewx/skins/ss/gauge-data.txt.tmpl
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
 Reason: 'UnknownType' object is not subscriptable
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
  Traceback (most recent call last):
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
File "/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in
generate
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
  unicode_string = compiled_template.respond()
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
File "_etc_weewx_skins_ss_gauge_data_txt_tmpl.py", line 142, in
respond
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line
1446, in getVar
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
  return valueFromSearchList(
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
File "/usr/share/weewx/weewx/units.py", line 1094, in raw
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
  return self.value_t[0]
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
  TypeError: 'UnknownType' object is not subscriptable
Jan 16 13:56:36 localhost wee_reports[62658] INFO weewx.cheetahgenerator:
Generated 1 files for report SteelSeries in 0.76 seconds
Jan 16 13:56:37 localhost wee_reports[62658] INFO weewx.imagegenerator:
Generated 11 images for report SteelSeries in 0.91 seconds
Jan 16 13:56:40 localhost wee_reports[62658] INFO weewx.cheetahgenerator:
Generated 2 files for report wxobs in 3.66 seconds
Jan 16 13:56:40 localhost wee_reports[62658] INFO weewx.reportengine:
Copied 6 files to /var/www/html/weewx/wxobs
Jan 16 13:56:54 localhost wee_reports[62658] INFO weewx.reportengine:
ftpgenerator: Ftp'd 54 files in 13.22 seconds

*Rémy LAVABRE*


Le sam. 20 janv. 2024 à 10:51, gjr80  a écrit :

> Impossible to say with such a small log extract. Please refer to the
> section How to get a good, useful log
> 
> on the Help! Posting to weewx user wiki page
> 
> .
>
> Gary
> On Saturday 20 January 2024 at 19:40:47 UTC+10 remy.l...@gmail.com wrote:
>
>> -> https://github.com/gjr80/weewx-steelseries
>> Good morning,
>>
>> I don't understand the reason and why of the error that occurs with my
>> version 4.10.2 of weewx and the 'SteelSeries' Skin.
>>
>> Can anyone help me and tell me what's going on?
>> THANKS
>>
>>
>>
>> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator: 
>> Ignoring template /etc/weewx/skins/ss/gauge-data.txt.tmpl
>> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator: 
>> Reason: 'UnknownType' object is not subscriptable
>> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator: 
>>  Traceback (most recent call last):
>> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator: 
>>File "/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in generate
>> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator: 
>>  unicode_string = compiled_template.respond()
>> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator: 
>>File "_etc_weewx_skins_ss_gauge_data_txt_tmpl.py", line 142, in respond
>> Jan 20 10:31:21 localhost w

[weewx-user] Re: Running Ecowitt Gateway Driver bith as a driver and a service at the same time?

2024-01-20 Thread 'michael.k...@gmx.at' via weewx-user 
Thank you! I'll see how far I get and I'll consider the mentioned drawbacks.
gjr80 schrieb am Samstag, 20. Januar 2024 um 10:47:29 UTC+1:

> The Gateway driver has supported simultaneous driver/service operation 
> since v0.5.0b5. It is not a configuration I recommend due to the fragility 
> of the configuration (if the driver crashes or the device using the driver 
> fails/locks up data from the service device is also lost) and the ease of 
> running dual WeeWX instances on the same device (particularly under WeeWX 
> v5).
>
> Notwithstanding, if you wish to use simultaneous driver/service operation 
> the driver configuration is placed under the [GW1000] stanza as normal and 
> the service configuration is placed under the [GW1000Service] stanza. 
> Otherwise the driver and service are configured as per independent 
> operation.
>
> Finally, be aware this is not a configuration I routinely, in fact I 
> suspect it has not bee touched since it was added to v0.5.0b5 so there may 
> be issues.
>
> Gary
>
> On Saturday 20 January 2024 at 17:52:04 UTC+10 michael.k...@gmx.at wrote:
>
>> The empty queue is probably because of running it in WSL and being in a 
>> different IP range than the Console:
>> 2024-01-19 18:47:39 weewxd[13771] DEBUG user.interceptor: empty queue
>>
>> $ ip addr
>> 2: eth0:  mtu 1500 qdisc mq state UP 
>> group default qlen 1000
>> link/ether 00:15:5d:a1:b2:53 brd ff:ff:ff:ff:ff:ff
>> inet 172.19.239.191/20 brd 172.19.239.255 scope global eth0
>>valid_lft forever preferred_lft forever
>> inet6 fe80::215:5dff:fea1:b253/64 scope link 
>>valid_lft forever preferred_lft forever
>>
>> And the console has 10.0.1.106
>>
>> I need to set up WSL to be in the same network or try this on another 
>> machine.
>>
>> Anyway, @grj80: have you ever considered collecting data from more than 
>> one ecowitt console device with the driver? For me this would make perfect 
>> sense, but I can very well understand, if it doesn't to you :D
>> michael.k...@gmx.at schrieb am Freitag, 19. Januar 2024 um 18:48:05 
>> UTC+1:
>>
>>> Yes, it's possible. 
>>> 2024-01-19 18:27:35 weewxd[5855] DEBUG user.gw1000: Next update in 9 
>>> seconds
>>> 2024-01-19 18:27:35 weewxd[5855] DEBUG user.gw1000: Next update in 9 
>>> seconds
>>> LOOP:   2024-01-19 18:27:35 CET (1705685255) 'altimeter': 
>>> '1023.2565915245989', 'appTemp': '-4.6378894597484965', 'barometer': 
>>> '1026.3446847507096', 'cloudbase': '972.4294835518078', 'dateTime': 
>>> '1705685255', 'daymaxwind': '2.1', 'dayRain': '4.7', 'dewpoint': 
>>> '-6.267050581532717', 'ET': 'None', 'extraHumid6': '62', 'extraHumid7': 
>>> '61', 'extraHumid8': '58', 'extraTemp6': '14.8', 'extraTemp7': '19.9', 
>>> 'extraTemp8': '20.6', 'heatindex': '-1.9008', 'humidex': 
>>> '-1.9', 'inDewpoint': '12.462345522375951', 'inHumidity': '60', 'inTemp': 
>>> '20.5', 'lightning_distance': 'None', 'lightning_last_det_time': 
>>> '1705345360', 'lightning_strike_count': '0', 'lightningcount': '0', 
>>> 'luminosity': '0.0', 'maxSolarRad': '0.0', 'monthRain': '50.4', 
>>> 'outHumidity': '72', 'outTemp': '-1.9', 'p_dayRain': '0.0', 'p_monthRain': 
>>> '26.5', 'p_rain': '0.0', 'p_rainRate': '0.0', 'p_stormRain': '0.0', 
>>> 'p_weekRain': '11.8', 'p_yearRain': '26.5', 'pressure': '971.0', 
>>> 'radiation': '0.0', 'rain': '0.0', 'rainRate': '0.0', 'relbarometer': 
>>> '1023.8', 'stormRain': '0.0', 'usUnits': '17', 'UV': '0', 'uvradiation': 
>>> '0.0', 'weekRain': '15.2', 'wh31_ch6_batt': '0', 'wh31_ch6_sig': '4', 
>>> 'wh31_ch7_batt': '0', 'wh31_ch7_sig': '4', 'wh31_ch8_batt': '0', 
>>> 'wh31_ch8_sig': '4', 'wh32_batt': '0', 'wh32_sig': '4', 'wh40_batt': 
>>> '1.45', 'wh40_sig': '4', 'wh57_batt': '5', 'wh57_sig': '4', 'windchill': 
>>> '-1.9008', 'windDir': 'None', 'windGust': '1.3', 'windrun': 
>>> 'None', 'windSpeed': '0.0', 'ws90_batt': '3.28', 'ws90_sig': '4', 
>>> 'yearRain': '50.4'
>>>
>>> But why would anybody want to do this? I have two GW2000 devices and 
>>> want to store and show data of as many of my sensor possible in a single 
>>> weewx instance. Yet configuring the driver both, as driver and a service at 
>>> the same time, seems to work as I hoped at least foor LOOP: two device 
>>> queries, on LOOP data.
>>>
>>> The question now: is it possible to configure the driver/service in a 
>>> way, they uses their own ip_address and is it possible to map the 
>>> Wind/Dir/Gust of the WS90 bound to the one GW2000, to e.g. 
>>> us_windSpeed/us_windDir/us_windGust (us for ultrasonic) just like p_rain 
>>> for the haptic array?
>>>
>>> Or isn't this possible and do I have to combine the Interceptor driver 
>>> with the Ecowitt Gateway Driver, one as a service, the other as a Driver to 
>>> achieve this? If yes, how could this be possible, I tried it with 
>>> Interceptor as a driver and Ecowitt Gateway Driver as a Service and get not 
>>> device data:
>>> 2024-01-19 18:46:59 weewxd[13771] DEBUG user.interceptor: empty queue
>>> 2024-01-19

[weewx-user] Re: Error with weewx-SteelSeries skin

2024-01-20 Thread gjr80 
Impossible to say with such a small log extract. Please refer to the 
section How to get a good, useful log 

 
on the Help! Posting to weewx user wiki page 

.

Gary
On Saturday 20 January 2024 at 19:40:47 UTC+10 remy.l...@gmail.com wrote:

> -> https://github.com/gjr80/weewx-steelseries
> Good morning,
>
> I don't understand the reason and why of the error that occurs with my 
> version 4.10.2 of weewx and the 'SteelSeries' Skin.
>
> Can anyone help me and tell me what's going on?
> THANKS
>
>
>
> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
> Ignoring template /etc/weewx/skins/ss/gauge-data.txt.tmpl
> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
> Reason: 'UnknownType' object is not subscriptable
> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
>  Traceback (most recent call last):
> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
>File "/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in generate
> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
>  unicode_string = compiled_template.respond()
> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
>File "_etc_weewx_skins_ss_gauge_data_txt_tmpl.py", line 142, in respond
> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
>File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1446, in 
> getVar
> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
>  return valueFromSearchList(
> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
>File "/usr/share/weewx/weewx/units.py", line 1094, in raw
> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
>  return self.value_t[0]
> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
>  TypeError: 'UnknownType' object is not subscriptable
>

-- 
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/18ebb63d-7160-4411-8e3d-3ecab1cf3e86n%40googlegroups.com.

[weewx-user] Re: Running Ecowitt Gateway Driver bith as a driver and a service at the same time?

2024-01-20 Thread gjr80 
The Gateway driver has supported simultaneous driver/service operation 
since v0.5.0b5. It is not a configuration I recommend due to the fragility 
of the configuration (if the driver crashes or the device using the driver 
fails/locks up data from the service device is also lost) and the ease of 
running dual WeeWX instances on the same device (particularly under WeeWX 
v5).

Notwithstanding, if you wish to use simultaneous driver/service operation 
the driver configuration is placed under the [GW1000] stanza as normal and 
the service configuration is placed under the [GW1000Service] stanza. 
Otherwise the driver and service are configured as per independent 
operation.

Finally, be aware this is not a configuration I routinely, in fact I 
suspect it has not bee touched since it was added to v0.5.0b5 so there may 
be issues.

Gary

On Saturday 20 January 2024 at 17:52:04 UTC+10 michael.k...@gmx.at wrote:

> The empty queue is probably because of running it in WSL and being in a 
> different IP range than the Console:
> 2024-01-19 18:47:39 weewxd[13771] DEBUG user.interceptor: empty queue
>
> $ ip addr
> 2: eth0:  mtu 1500 qdisc mq state UP 
> group default qlen 1000
> link/ether 00:15:5d:a1:b2:53 brd ff:ff:ff:ff:ff:ff
> inet 172.19.239.191/20 brd 172.19.239.255 scope global eth0
>valid_lft forever preferred_lft forever
> inet6 fe80::215:5dff:fea1:b253/64 scope link 
>valid_lft forever preferred_lft forever
>
> And the console has 10.0.1.106
>
> I need to set up WSL to be in the same network or try this on another 
> machine.
>
> Anyway, @grj80: have you ever considered collecting data from more than 
> one ecowitt console device with the driver? For me this would make perfect 
> sense, but I can very well understand, if it doesn't to you :D
> michael.k...@gmx.at schrieb am Freitag, 19. Januar 2024 um 18:48:05 UTC+1:
>
>> Yes, it's possible. 
>> 2024-01-19 18:27:35 weewxd[5855] DEBUG user.gw1000: Next update in 9 
>> seconds
>> 2024-01-19 18:27:35 weewxd[5855] DEBUG user.gw1000: Next update in 9 
>> seconds
>> LOOP:   2024-01-19 18:27:35 CET (1705685255) 'altimeter': 
>> '1023.2565915245989', 'appTemp': '-4.6378894597484965', 'barometer': 
>> '1026.3446847507096', 'cloudbase': '972.4294835518078', 'dateTime': 
>> '1705685255', 'daymaxwind': '2.1', 'dayRain': '4.7', 'dewpoint': 
>> '-6.267050581532717', 'ET': 'None', 'extraHumid6': '62', 'extraHumid7': 
>> '61', 'extraHumid8': '58', 'extraTemp6': '14.8', 'extraTemp7': '19.9', 
>> 'extraTemp8': '20.6', 'heatindex': '-1.9008', 'humidex': 
>> '-1.9', 'inDewpoint': '12.462345522375951', 'inHumidity': '60', 'inTemp': 
>> '20.5', 'lightning_distance': 'None', 'lightning_last_det_time': 
>> '1705345360', 'lightning_strike_count': '0', 'lightningcount': '0', 
>> 'luminosity': '0.0', 'maxSolarRad': '0.0', 'monthRain': '50.4', 
>> 'outHumidity': '72', 'outTemp': '-1.9', 'p_dayRain': '0.0', 'p_monthRain': 
>> '26.5', 'p_rain': '0.0', 'p_rainRate': '0.0', 'p_stormRain': '0.0', 
>> 'p_weekRain': '11.8', 'p_yearRain': '26.5', 'pressure': '971.0', 
>> 'radiation': '0.0', 'rain': '0.0', 'rainRate': '0.0', 'relbarometer': 
>> '1023.8', 'stormRain': '0.0', 'usUnits': '17', 'UV': '0', 'uvradiation': 
>> '0.0', 'weekRain': '15.2', 'wh31_ch6_batt': '0', 'wh31_ch6_sig': '4', 
>> 'wh31_ch7_batt': '0', 'wh31_ch7_sig': '4', 'wh31_ch8_batt': '0', 
>> 'wh31_ch8_sig': '4', 'wh32_batt': '0', 'wh32_sig': '4', 'wh40_batt': 
>> '1.45', 'wh40_sig': '4', 'wh57_batt': '5', 'wh57_sig': '4', 'windchill': 
>> '-1.9008', 'windDir': 'None', 'windGust': '1.3', 'windrun': 
>> 'None', 'windSpeed': '0.0', 'ws90_batt': '3.28', 'ws90_sig': '4', 
>> 'yearRain': '50.4'
>>
>> But why would anybody want to do this? I have two GW2000 devices and want 
>> to store and show data of as many of my sensor possible in a single weewx 
>> instance. Yet configuring the driver both, as driver and a service at the 
>> same time, seems to work as I hoped at least foor LOOP: two device queries, 
>> on LOOP data.
>>
>> The question now: is it possible to configure the driver/service in a 
>> way, they uses their own ip_address and is it possible to map the 
>> Wind/Dir/Gust of the WS90 bound to the one GW2000, to e.g. 
>> us_windSpeed/us_windDir/us_windGust (us for ultrasonic) just like p_rain 
>> for the haptic array?
>>
>> Or isn't this possible and do I have to combine the Interceptor driver 
>> with the Ecowitt Gateway Driver, one as a service, the other as a Driver to 
>> achieve this? If yes, how could this be possible, I tried it with 
>> Interceptor as a driver and Ecowitt Gateway Driver as a Service and get not 
>> device data:
>> 2024-01-19 18:46:59 weewxd[13771] DEBUG user.interceptor: empty queue
>> 2024-01-19 18:47:07 weewxd[13771] DEBUG user.gw1000: Next update in 9 
>> seconds
>> 2024-01-19 18:47:09 weewxd[13771] DEBUG user.interceptor: empty queue
>> 2024-01-19 18:47:16 weewxd[13771] DEBUG user.gw1000: Next update in 9 
>> seconds
>> 2024-01-19 18:47:19

[weewx-user] Error with weewx-SteelSeries skin

2024-01-20 Thread Remy Lavabre 
-> https://github.com/gjr80/weewx-steelseries
Good morning,

I don't understand the reason and why of the error that occurs with my 
version 4.10.2 of weewx and the 'SteelSeries' Skin.

Can anyone help me and tell me what's going on?
THANKS



Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
Ignoring template /etc/weewx/skins/ss/gauge-data.txt.tmpl
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
Reason: 'UnknownType' object is not subscriptable
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
 Traceback (most recent call last):
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:    
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in generate
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:    
   unicode_string = compiled_template.respond()
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:    
 File "_etc_weewx_skins_ss_gauge_data_txt_tmpl.py", line 142, in respond
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:    
 File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1446, in 
getVar
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:    
   return valueFromSearchList(
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:    
 File "/usr/share/weewx/weewx/units.py", line 1094, in raw
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:    
   return self.value_t[0]
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
 TypeError: 'UnknownType' object is not subscriptable

-- 
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/16f5a162-11f1-4b5c-b12b-a4539aa7833en%40googlegroups.com.

[weewx-user] Re: Running Ecowitt Gateway Driver bith as a driver and a service at the same time?

2024-01-20 Thread 'michael.k...@gmx.at' via weewx-user 
Ignore that empty queue, I forgot that the console device actively reports 
to a certain IP...

michael.k...@gmx.at schrieb am Samstag, 20. Januar 2024 um 08:52:04 UTC+1:

> The empty queue is probably because of running it in WSL and being in a 
> different IP range than the Console:
> 2024-01-19 18:47:39 weewxd[13771] DEBUG user.interceptor: empty queue
>
> $ ip addr
> 2: eth0:  mtu 1500 qdisc mq state UP 
> group default qlen 1000
> link/ether 00:15:5d:a1:b2:53 brd ff:ff:ff:ff:ff:ff
> inet 172.19.239.191/20 brd 172.19.239.255 scope global eth0
>valid_lft forever preferred_lft forever
> inet6 fe80::215:5dff:fea1:b253/64 scope link 
>valid_lft forever preferred_lft forever
>
> And the console has 10.0.1.106
>
> I need to set up WSL to be in the same network or try this on another 
> machine.
>
> Anyway, @grj80: have you ever considered collecting data from more than 
> one ecowitt console device with the driver? For me this would make perfect 
> sense, but I can very well understand, if it doesn't to you :D
> michael.k...@gmx.at schrieb am Freitag, 19. Januar 2024 um 18:48:05 UTC+1:
>
>> Yes, it's possible. 
>> 2024-01-19 18:27:35 weewxd[5855] DEBUG user.gw1000: Next update in 9 
>> seconds
>> 2024-01-19 18:27:35 weewxd[5855] DEBUG user.gw1000: Next update in 9 
>> seconds
>> LOOP:   2024-01-19 18:27:35 CET (1705685255) 'altimeter': 
>> '1023.2565915245989', 'appTemp': '-4.6378894597484965', 'barometer': 
>> '1026.3446847507096', 'cloudbase': '972.4294835518078', 'dateTime': 
>> '1705685255', 'daymaxwind': '2.1', 'dayRain': '4.7', 'dewpoint': 
>> '-6.267050581532717', 'ET': 'None', 'extraHumid6': '62', 'extraHumid7': 
>> '61', 'extraHumid8': '58', 'extraTemp6': '14.8', 'extraTemp7': '19.9', 
>> 'extraTemp8': '20.6', 'heatindex': '-1.9008', 'humidex': 
>> '-1.9', 'inDewpoint': '12.462345522375951', 'inHumidity': '60', 'inTemp': 
>> '20.5', 'lightning_distance': 'None', 'lightning_last_det_time': 
>> '1705345360', 'lightning_strike_count': '0', 'lightningcount': '0', 
>> 'luminosity': '0.0', 'maxSolarRad': '0.0', 'monthRain': '50.4', 
>> 'outHumidity': '72', 'outTemp': '-1.9', 'p_dayRain': '0.0', 'p_monthRain': 
>> '26.5', 'p_rain': '0.0', 'p_rainRate': '0.0', 'p_stormRain': '0.0', 
>> 'p_weekRain': '11.8', 'p_yearRain': '26.5', 'pressure': '971.0', 
>> 'radiation': '0.0', 'rain': '0.0', 'rainRate': '0.0', 'relbarometer': 
>> '1023.8', 'stormRain': '0.0', 'usUnits': '17', 'UV': '0', 'uvradiation': 
>> '0.0', 'weekRain': '15.2', 'wh31_ch6_batt': '0', 'wh31_ch6_sig': '4', 
>> 'wh31_ch7_batt': '0', 'wh31_ch7_sig': '4', 'wh31_ch8_batt': '0', 
>> 'wh31_ch8_sig': '4', 'wh32_batt': '0', 'wh32_sig': '4', 'wh40_batt': 
>> '1.45', 'wh40_sig': '4', 'wh57_batt': '5', 'wh57_sig': '4', 'windchill': 
>> '-1.9008', 'windDir': 'None', 'windGust': '1.3', 'windrun': 
>> 'None', 'windSpeed': '0.0', 'ws90_batt': '3.28', 'ws90_sig': '4', 
>> 'yearRain': '50.4'
>>
>> But why would anybody want to do this? I have two GW2000 devices and want 
>> to store and show data of as many of my sensor possible in a single weewx 
>> instance. Yet configuring the driver both, as driver and a service at the 
>> same time, seems to work as I hoped at least foor LOOP: two device queries, 
>> on LOOP data.
>>
>> The question now: is it possible to configure the driver/service in a 
>> way, they uses their own ip_address and is it possible to map the 
>> Wind/Dir/Gust of the WS90 bound to the one GW2000, to e.g. 
>> us_windSpeed/us_windDir/us_windGust (us for ultrasonic) just like p_rain 
>> for the haptic array?
>>
>> Or isn't this possible and do I have to combine the Interceptor driver 
>> with the Ecowitt Gateway Driver, one as a service, the other as a Driver to 
>> achieve this? If yes, how could this be possible, I tried it with 
>> Interceptor as a driver and Ecowitt Gateway Driver as a Service and get not 
>> device data:
>> 2024-01-19 18:46:59 weewxd[13771] DEBUG user.interceptor: empty queue
>> 2024-01-19 18:47:07 weewxd[13771] DEBUG user.gw1000: Next update in 9 
>> seconds
>> 2024-01-19 18:47:09 weewxd[13771] DEBUG user.interceptor: empty queue
>> 2024-01-19 18:47:16 weewxd[13771] DEBUG user.gw1000: Next update in 9 
>> seconds
>> 2024-01-19 18:47:19 weewxd[13771] DEBUG user.interceptor: empty queue
>> 2024-01-19 18:47:25 weewxd[13771] DEBUG user.gw1000: Next update in 9 
>> seconds
>> 2024-01-19 18:47:29 weewxd[13771] DEBUG user.interceptor: empty queue
>> 2024-01-19 18:47:34 weewxd[13771] DEBUG user.gw1000: Next update in 9 
>> seconds
>> 2024-01-19 18:47:39 weewxd[13771] DEBUG user.interceptor: empty queue
>> 2024-01-19 18:47:43 weewxd[13771] DEBUG user.gw1000: Next update in 9 
>> seconds
>> 2024-01-19 18:47:49 weewxd[13771] DEBUG user.interceptor: empty queue
>>
>>
>>

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