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

[Remy Lavabre]

Hello Gary and thank you for your response.

I have put all the fields in my database below :

[image: WX1.png]

[image: WX2.png]

[image: WX3.png]

[image: WX4.png]

Indeed the error perhaps comes from this side because I deleted fields 
which were useless to me and added others...*However I do not think I 
deleted "basic" fields such as those which are used in the skin...?*

As for the WeeWX driver, this is also a driver that I created myself since 
it directly retrieves the data from AWEKAS after my Bresser 7in1 weather 
station sent it to their site (no USB output unfortunately) .
But I don't think this driver is to blame since all the data entered into 
the database is consistent!
For information: -> https://meteomillau.go.yo.fr/index.html

Concerning the configuration of Weewx, nothing more classic it seems to 
me...:

 [[SteelSeries]]
 skin = ss
 enable = False
 HTML_ROOT = /var/www/html/weewx/ss
 [[[Units]]]
 Groups
 group_altitude = meter
 group_pressure = hPa
 group_rain = mm
 group_rainRate = mm_per_hour
 group_speed = km_per_hour
 group_temperature = degree_C
 StringFormats
 degree_C = %.1f
 degree_F = %.1f
 degree_compass = %.0f
 foot = %.0f
 hPa = %.1f
 inHg = %.3f
 inch = %.2f
 inch_per_hour = %.2f
 km = %.1f
 km_per_hour = %.0f
 knot = %.0f
 mbar = %.1f
 meter = %.0f
 meter_per_second = %.1f
 mile = %.1f
 mile_per_hour = %.0f
 mm = %.1f
 mmHg = %.1f
 mm_per_hour = %.1f
 percent = %.0f
 uv_index = %.1f
 watt_per_meter_squared = %.0f

Le dimanche 21 janvier 2024 à 05:52:36 UTC+1, gjr80 a écrit :

> 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 '> 'TypeError'>'
>> 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/Cheet

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

[Tom Keffer]

Make sure that appTemp appears in the [StdWXCalculate] section of
your weewx.conf:

[StdWXCalculate]
[[Calculations]]
...
appTemp = prefer_hardware

Also, try running weewxd from the command line and see if appTemp is
printed in the LOOP packets and archive records.


On Sat, Jan 20, 2024 at 6:36 PM Richard Whitcombe 
wrote:

> Just woke up so delayed reply but yep thats exactly the case.
>
> From index.html.tmpl:
>
>  
> #if $current.appTemp.has_data
>  class="feelslike">$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 us

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

[Tomasz Lewicki]

Thank you, this is exactly what I was looking for :)

sobota, 20 stycznia 2024 o 21:48:57 UTC+1 bell...@gmail.com napisał(a):

> 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/77a6118f-a69f-4265-8cde-1500218a75cfn%40googlegroups.com.

[weewx-user] StdCalibrate math question

[Steve2Q]

I have a calibration curve for my outdoor humidity sensor that includes 
division and an exponent. The formula is : OutHumidity = 
92.2/(1+(1/(OutHumididty/64.6)^3.47))  Can this be handled by StdCalibrate?

-- 
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/9e1d1a9b-faa3-48f9-8ca1-5cfeb712def9n%40googlegroups.com.

[weewx-user] weewx and void linux

[Δημήτρης Βήχος]

tried to run weewx  5.0 in void linux with runit .
with git instalation.
instalation its very easy and fast, but weewx never start .running at the 
end "python3 ~/weewx/src/weewxd.py"  tells me "unknown file system" in 
terminal. 

-- 
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/9aa69194-d0d6-490e-a46a-b99ca67def13n%40googlegroups.com.

Re: [weewx-user] StdCalibrate math question

[Tom Keffer]

Yes, of course. Just substitute "**" for "^" so it's a Python expression.
Or, use the math function pow().

On Sun, Jan 21, 2024 at 8:14 AM Steve2Q  wrote:

> I have a calibration curve for my outdoor humidity sensor that includes
> division and an exponent. The formula is : OutHumidity =
> 92.2/(1+(1/(OutHumididty/64.6)^3.47))  Can this be handled by StdCalibrate?
>
> --
> 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/9e1d1a9b-faa3-48f9-8ca1-5cfeb712def9n%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/CAPq0zEC1L-%3DKXyMTS9oKA%2Bs92%3DpVh2PDrMGAxKsNVp%2BUFHCY0A%40mail.gmail.com.

[weewx-user] Driver permission error when starting Weewx

[Tomasz Lewicki]

I got problem with running Weewx with old/new station. Recently I bought 
new station and moved it to previous remote location. Old station will be 
installed in my home. It is clone of FineOffset HP1000 so both HP1000 
driver from AussieSusan (https://github.com/AussieSusan/HP1000) and 
Interceptor from Matthew Wall 
(https://github.com/matthewwall/weewx-interceptor) should work.

I installed both interceptor and HP1000 drivers by weectl. But after 
starting Weewx I got critical errors in my log (see below). I suppose it is 
something easy to fix, some permissions to file and/or directory but I 
don't know where. 

Jan 21 18:14:17 FR24 weewxd[14285]: INFO __main__: Initializing weewxd 
version 5.0.0
Jan 21 18:14:17 FR24 weewxd[14285]: INFO __main__: Command line: 
/usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
Jan 21 18:14:17 FR24 weewxd[14285]: INFO __main__: Using Python 3.7.3 
(default, Oct 11 2023, 09:51:27) #012[GCC 8.3.0]
Jan 21 18:14:17 FR24 weewxd[14285]: INFO __main__: Located at 
/usr/bin/python3
Jan 21 18:14:17 FR24 weewxd[14285]: INFO __main__: Platform 
Linux-5.10.103-v7+-armv7l-with-debian-10.13
Jan 21 18:14:17 FR24 weewxd[14285]: INFO __main__: Locale: 'pl_PL.UTF-8'
Jan 21 18:14:17 FR24 weewxd[14285]: INFO __main__: Entry path: 
/usr/share/weewx/weewxd.py
Jan 21 18:14:17 FR24 weewxd[14285]: INFO __main__: WEEWX_ROOT: /etc/weewx
Jan 21 18:14:17 FR24 weewxd[14285]: INFO __main__: Configuration file: 
/etc/weewx/weewx.conf
Jan 21 18:14:17 FR24 weewxd[14285]: INFO __main__: User module: 
/etc/weewx/bin/user

Jan 21 18:14:17 FR24 weewxd[14285]: INFO __main__: Debug: 1
Jan 21 18:14:17 FR24 weewxd[14285]: DEBUG __main__: Initializing engine
Jan 21 18:14:17 FR24 weewxd[14285]: INFO weewx.engine: Loading station type 
Interceptor (user.interceptor)
Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: driver version 
is 0.60
Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: device type: 
observer
Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: hardware name: 
weatherstation via interceptor
Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: mode is listen
Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: listen on :80
Jan 21 18:14:17 FR24 weewxd[14285]: ERROR weewx.engine: Import of driver 
failed: [Errno 13] Brak dostępu ()
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine:  
 Traceback (most recent call last):
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/engine.py", line 115, in setupStation
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine:  
 self.console = loader_function(config_dict, self)
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine: File 
"/etc/weewx/bin/user/interceptor.py", line 316, in loader
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine:  
 return InterceptorDriver(**config_dict[DRIVER_NAME])
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine: File 
"/etc/weewx/bin/user/interceptor.py", line 2529, in __init__
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine:  
 self._device = self.DEVICE_TYPES.get(self._device_type)(**stn_dict)
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine: File 
"/etc/weewx/bin/user/interceptor.py", line 1286, in __init__
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine:  
 Observer.Parser(), handler=Observer.Handler, **stn_dict)
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine: File 
"/etc/weewx/bin/user/interceptor.py", line 430, in __init__
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine:  
 self._server = Consumer.TCPServer(address, port, handler)
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine: File 
"/etc/weewx/bin/user/interceptor.py", line 585, in __init__
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine:  
 TCPServer.__init__(self, (address, int(port)), handler)
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine: File 
"/usr/lib/python3.7/socketserver.py", line 452, in __init__
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine:  
 self.server_bind()
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine: File 
"/usr/lib/python3.7/socketserver.py", line 466, in server_bind
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine:  
 self.socket.bind(self.server_address)
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL weewx.engine:  
 PermissionError: [Errno 13] Brak dostępu
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL __main__: Unable to load 
driver: [Errno 13] Brak dostępu
Jan 21 18:14:17 FR24 weewxd[14285]: CRITICAL __main__:   Exiting...

-- 
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+un

Re: [weewx-user] weewx and void linux

[Tom Keffer]

That's not much information, but sounds like an operating system issue.
Unless you're a void Linux expert, perhaps you should use a more standard
OS?

On Sun, Jan 21, 2024 at 8:52 AM Δημήτρης Βήχος 
wrote:

> tried to run weewx  5.0 in void linux with runit .
> with git instalation.
> instalation its very easy and fast, but weewx never start .running at the
> end "python3 ~/weewx/src/weewxd.py"  tells me "unknown file system" in
> terminal.
>
> --
> 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/9aa69194-d0d6-490e-a46a-b99ca67def13n%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/CAPq0zEB-ZYNmm9FdAfZSscb%2B2TdqjiQWggV3Gnhfv43gzL1p1A%40mail.gmail.com.

[weewx-user] Re: Driver permission error when starting Weewx

[matthew wall]

On Sunday, January 21, 2024 at 12:23:34 PM UTC-5 Tomasz Lewicki wrote:


Jan 21 18:14:17 FR24 weewxd[14285]: INFO weewx.engine: Loading station type 
Interceptor (user.interceptor)
Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: driver version 
is 0.60
Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: device type: 
observer
Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: hardware name: 
weatherstation via interceptor
Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: mode is listen
Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: listen on :80


if you listen on port 80, then the process must run as root (only root can 
listen on lower ports).

so either run weewxd as root, or configure interceptor (and the station) to 
communicate on a higher port.
 

-- 
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/be30410a-dbe2-4cec-b261-f6187aa5b1f1n%40googlegroups.com.

[weewx-user] Re: weewx and void linux

[matthew wall]

On Sunday, January 21, 2024 at 11:52:44 AM UTC-5 hobbyl...@gmail.com wrote:

tried to run weewx  5.0 in void linux with runit .
with git instalation.
instalation its very easy and fast, but weewx never start .running at the 
end "python3 ~/weewx/src/weewxd.py"  tells me "unknown file system" in 
terminal. 


we'll need a bit more than "unknown file system" to figure this one out.  
post the whole session - what you typed and what you got in response.
 it would also help to know whether you provisioned a station (and was that 
successful?), whether you are using a virtual environment or the system's 
python, ...

-- 
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/10b317e8-44f4-4740-b791-e07f96da4aabn%40googlegroups.com.

[weewx-user] Interceptor - Parse failed for ... Dictionary update sequence element #0...

[Cory Verellen]

This is a new one I've not seen. 
Just updated (accidentally) to 5.0.0 via automatic update script. Oops, 
forgot I shouldn't do that with weewx. OK, let's see if I can fix this 
Running Belchertown, and got the DB issue sorted. Now this

Jan 21 10:00:26 weather weewxd[2883]: ERROR user.interceptor: parse failed 
for 
&PASSKEY=xxx&stationtype=AMBWeatherPro_V5.1.4&dateutc=2024-01-21+18:00:26&tempf=43.9&humidity=99&windspeedmph=0.00&windgustmph=0.00&maxdailygust=5.82&winddir=61&uv=0&solarradiation=20.31&hourlyrainin=0.000&eventrainin=0.409&dailyrainin=0.150&weeklyrainin=0.150&monthlyrainin=4.201&yearlyrainin=4.201&totalrainin=26.929&battout=1&tempinf=65.8&humidityin=41&baromrelin=29.297&baromabsin=29.220&temp1f=52.9&humidity1=66&batt1=1:
 
dictionary update sequence element #0 has length 1; 2 is required

There are some mentions of this out there but I've not found a solution 
yet. 

This is a Ambient WS-2902 that was working fine on 4.10.2 Any Ideas?

-- 
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/579c0a97-cb42-41a6-ae02-448213c54b73n%40googlegroups.com.

[weewx-user] Re: Interceptor - Parse failed for ... Dictionary update sequence element #0...

[Cory Verellen]

Fixed though I'm not sure why/how/what changed to break interceptor. Here's 
the fix:

in interceptor.py you need to strip out the leading '&' in the url being 
parsed. Add s=s.lstrip('&') 

def _cgi_to_dict(s):
s=s.lstrip('&')
if '=' in s:
return dict([y.strip() for y in x.split('=')] for x in s.split('&'))
return dict()

On Sunday, January 21, 2024 at 10:18:51 AM UTC-8 Cory Verellen wrote:

> This is a new one I've not seen. 
> Just updated (accidentally) to 5.0.0 via automatic update script. Oops, 
> forgot I shouldn't do that with weewx. OK, let's see if I can fix this 
> Running Belchertown, and got the DB issue sorted. Now this
>
> Jan 21 10:00:26 weather weewxd[2883]: ERROR user.interceptor: parse failed 
> for 
> &PASSKEY=xxx&stationtype=AMBWeatherPro_V5.1.4&dateutc=2024-01-21+18:00:26&tempf=43.9&humidity=99&windspeedmph=0.00&windgustmph=0.00&maxdailygust=5.82&winddir=61&uv=0&solarradiation=20.31&hourlyrainin=0.000&eventrainin=0.409&dailyrainin=0.150&weeklyrainin=0.150&monthlyrainin=4.201&yearlyrainin=4.201&totalrainin=26.929&battout=1&tempinf=65.8&humidityin=41&baromrelin=29.297&baromabsin=29.220&temp1f=52.9&humidity1=66&batt1=1:
>  
> dictionary update sequence element #0 has length 1; 2 is required
>
> There are some mentions of this out there but I've not found a solution 
> yet. 
>
> This is a Ambient WS-2902 that was working fine on 4.10.2 Any Ideas?
>

-- 
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/817a0e3b-b1fc-42e9-93d7-b5eb17d839ban%40googlegroups.com.

[weewx-user] weewx.drivers.vantage: Socket error while opening port 22222

[Ed Surowiec]

I am having trouble getting weewx to connect to my WeatherLink Live 
ethernet box.  I am able to connect to the WeatherLink Live using a browser 
and also using netcat to port 2 from the raspberry pi I have weewx 
installed on.  Here is the error.  Any help would be appreciated.



Jan 21 13:51:26 rpi-blue weewxd[12964]: INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage)

Jan 21 13:51:26 rpi-blue weewxd[12964]: ERROR weewx.drivers.vantage: Socket 
error while opening port 2 to ethernet host 10.0.1.180.

Jan 21 13:51:26 rpi-blue weewxd[12964]: ERROR weewx.engine: Import of 
driver failed: [Errno 111] Connection refused ()


I am able to connect to weatherlink live box using the link 
http://10.0.1.180:80/v1/current_conditions

and see data in my browser.


I can also connect to the weatherlink live with netcat from the raspberry 
pi that I have weewx installed on.

*pi@rpi-blue*:*~ $* nc -nvulp 2

Bound on 0.0.0.0 2

Connection received on 10.0.1.180 43539

{"did":"001D0A712868","ts":1705869635,"conditions":[{"lsid":326721,"data_structure_type":1,"txid":1,"wind_speed_last":4.00,"wind_dir_last":207,"rain_size":1,"rain_rate_last":0,"rain_15_min":0,"rain_60_min":0,"rain_24_hr":28,"rain_storm":28,"rain_storm_start_at":1705832820,"rainfall_daily":28,"rainfall_monthly":54,"rainfall_year":54,"wind_speed_hi_last_10_min":10.00,"wind_dir_at_hi_speed_last_10_min":244}]}^C


My weewx.config contains the following:

##

[Vantage]
# This section is for the Davis Vantage series of weather stations.

# Connection type: serial or ethernet 
#  serial (the classic VantagePro)
#  ethernet (the WeatherLinkIP or Serial-Ethernet bridge)
   type = ethernet

# If the connection type is serial, a port must be specified:
#   Debian, Ubuntu, Redhat, Fedora, and SuSE:
# /dev/ttyUSB0 is a common USB port name
# /dev/ttyS0   is a common serial port name
#   BSD:
# /dev/cuaU0   is a common serial port name
port = /dev/ttyUSB0

# If the connection type is ethernet, an IP Address/hostname is 
required:
   host = 10.0.1.180

##
# The rest of this section rarely needs any attention. 
# You can safely leave it "as is."
##

# Serial baud rate (usually 19200)
baudrate = 19200

# TCP port (when using the WeatherLinkIP)
tcp_port = 2

# TCP send delay (when using the WeatherLinkIP):
tcp_send_delay = 0.5

# The type of LOOP packet to request: 1 = LOOP1; 2 = LOOP2; 3 = both
loop_request = 1

# The id of your ISS station (usually 1). If you use a wind meter 
connected
# to a anemometer transmitter kit, use its id
iss_id = 1

# How long to wait for a response from the station before giving up (in
# seconds; must be greater than 2)
timeout = 4

# How long to wait before trying again (in seconds)
wait_before_retry = 1.2

# How many times to try before giving up:
max_tries = 4

# Vantage model Type: 1 = Vantage Pro; 2 = Vantage Pro2
model_type = 2

# The driver to use:
driver = weewx.drivers.vantage

##


-- 
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/be1b9b26-1de2-467c-91a6-0d11911bc97dn%40googlegroups.com.

Re: [weewx-user] StdCalibrate math question

[Graham Eddy]

it is worth noting and perhaps documenting that python builtin functions can be 
used in StdCalibrate expressions
⊣GE⊢

> On 22 Jan 2024, at 4:19 am, Tom Keffer  wrote:
> 
> Yes, of course. Just substitute "**" for "^" so it's a Python expression. Or, 
> use the math function pow().
> 
> On Sun, Jan 21, 2024 at 8:14 AM Steve2Q  > wrote:
>> I have a calibration curve for my outdoor humidity sensor that includes 
>> division and an exponent. The formula is : OutHumidity = 
>> 92.2/(1+(1/(OutHumididty/64.6)^3.47))  Can this be handled by StdCalibrate?
>> 
>> -- 
>> 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/9e1d1a9b-faa3-48f9-8ca1-5cfeb712def9n%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/CAPq0zEC1L-%3DKXyMTS9oKA%2Bs92%3DpVh2PDrMGAxKsNVp%2BUFHCY0A%40mail.gmail.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/9E0668B3-0B83-408A-8C16-2C01863E3287%40geddy.au.

Re: [weewx-user] StdCalibrate math question

[Tom Keffer]

It is documented.

*expression* is a valid Python expression involving any observation types
> in the same record, or functions in the math module
> .


https://www.weewx.com/docs/5.0/reference/weewx-options/stdcalibrate/#corrections

On Sun, Jan 21, 2024 at 2:07 PM Graham Eddy  wrote:

> it is worth noting and perhaps documenting that python builtin functions
> can be used in StdCalibrate expressions
> *⊣GE⊢*
>
> On 22 Jan 2024, at 4:19 am, Tom Keffer  wrote:
>
> Yes, of course. Just substitute "**" for "^" so it's a Python expression.
> Or, use the math function pow().
>
> On Sun, Jan 21, 2024 at 8:14 AM Steve2Q  wrote:
>
>> I have a calibration curve for my outdoor humidity sensor that includes
>> division and an exponent. The formula is : OutHumidity =
>> 92.2/(1+(1/(OutHumididty/64.6)^3.47))  Can this be handled by StdCalibrate?
>>
>> --
>> 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/9e1d1a9b-faa3-48f9-8ca1-5cfeb712def9n%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/CAPq0zEC1L-%3DKXyMTS9oKA%2Bs92%3DpVh2PDrMGAxKsNVp%2BUFHCY0A%40mail.gmail.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/9E0668B3-0B83-408A-8C16-2C01863E3287%40geddy.au
> 
> .
>

-- 
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/CAPq0zECtc9v_beuBz573V4XFSCpB%2BdzDbKDf1Jq6jp-6C6XyNQ%40mail.gmail.com.

[weewx-user] Re: HP1000 Driver Problems discovered

[Susan Mackay]

I'm not sure what happened but I did reply to this topic a few days ago 
with an explanation of what was happening. So here I go again

Firstly - please DON'T delete the historical records from the console. 
While that does get WeeWx to again read the current data, it is not 
necessary given the faults I've found. As long as the console is powered on 
and working, it will be storing the historical records that can be 
retrieved by the fixed driver. True, you won't get the data into WeeWx 
right now but you will soon.

The issue seems to stem from the HP1000 console firmware showing 0 
historical records for 2024 - there are valid record counts for previous 
years (at least on my console back to 2017). 

Of course these are only used when WeeWx tries to 'catch up' any historical 
records it has missed since the last time it was connected to the console. 
(Normal, on-going data is not affected.)

When the driver saw the '0' record count, it was not expecting this and 
mishandled the requests for historical record. Basically it sent a request 
that was never responded to the console but it also never timed out while 
waiting for that response. The historical are actually there but just not 
reported by the console when asked for the year-by-year historical record 
count.

I now detect when that situation arises and use the current date to 'guess' 
at the number of records. I also allow for a timeout if there is not 
response from the console. All this seems to work OK (at least for me).

I'm now looking at the code changes needed to make the driver V5 compatible 
and I'm hoping the new driver will be available in the next few days.

Susan

On Wednesday 17 January 2024 at 8:32:59 am UTC+11 Susan Mackay wrote:

> A problem has recently been found with the HP1000 (WS1001, XC0422) driver.
> While the driver will continue to work correctly, if it is restarted then 
> it will hand trying to retrieve the 'historical' records from the console..
> (A 'solution' has been mentioned by some that involves deleting the 
> historical records form the console and relying on the data held in the 
> WeeWx database. I don't recommend this approach.)
> I am looking into the issue and I will post an updated version of the 
> driver as soon as I can.
> I also will bring the driver into compliance with the WeeWx V5 driver 
> requirements. I've heard that it does work under V5 but that it is missing 
> something for a new installation.
> Susan
>

-- 
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/e4975658-9a4c-4240-b37b-4a06c4cc5988n%40googlegroups.com.

Re: [weewx-user] weewx.drivers.vantage: Socket error while opening port 22222

[John Smith]

On Mon, 22 Jan 2024 at 08:13, Ed Surowiec  wrote:

> I am having trouble getting weewx to connect to my WeatherLink Live
> ethernet box.  I am able to connect to the WeatherLink Live using a browser
> and also using netcat to port 2 from the raspberry pi I have weewx
> installed on.  Here is the error.  Any help would be appreciated.
>
>
>
> Jan 21 13:51:26 rpi-blue weewxd[12964]: INFO weewx.engine: Loading station
> type Vantage (weewx.drivers.vantage)
>
> Jan 21 13:51:26 rpi-blue weewxd[12964]: ERROR weewx.drivers.vantage:
> Socket error while opening port 2 to ethernet host 10.0.1.180.
>
> Jan 21 13:51:26 rpi-blue weewxd[12964]: ERROR weewx.engine: Import of
> driver failed: [Errno 111] Connection refused ()
>

It looks like you are connecting to the wrong IP or it's not reachable on
the LAN

-- 
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/CAGTinV6daa-0aSGtrAi%2BhThvY9oHwXUuVmi1ToUnNoK2S30p6g%40mail.gmail.com.

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

['michael.k...@gmx.at' via weewx-user]

Here is what I've observed, I can't tell if everything is an issue or if it 
is working as designed. (What I am trying to achieve, I will post in 
another reply)

I've configured an instance which reads from one GW2000 device (receiving 
from a WS68 sensor array) configured as driver, and another GW2000 
device (receiving from a WS90 sensor array) as service. I've configured 
both with the same poll_interval:

[GW1000] #WS68
# This section is for the Ecowitt Gateway driver.

# How often to poll the API, default is every 20 seconds:
poll_interval = 10
ip_address = 10.0.1.85
max_tries = 360

# The driver to use:
driver = user.gw1000

[GW1000Service] #WS90
# This section is for the Ecowitt Gateway driver.

# How often to poll the API, default is every 20 seconds:
poll_interval = 10
ip_address = 10.0.1.86
max_tries = 360

# The driver to use:
driver = user.gw1000

[[field_map]]
ws90_windDir = winddir
ws90_windSpeed = windspeed
ws90_windGust = gustspeed
ws90_daymaxwind = daymaxwind
ws90_uvradiation = uv
ws90_UV = uvi
ws90_luminosity = light
p_rain = p_rain
p_stormRain = p_rainevent
p_rainRate = p_rainrate
p_dayRain = p_rainday
p_weekRain = p_rainweek
p_monthRain = p_rainmonth
p_yearRain = p_rainyear

Starting weewxd, there is one LOOP every 10 Seconds, it seems it is 
containing values from the device configured in [GW1000Service] including 
the values from [[field_map]], which I didn't expect from skimming through 
the driver's code.  In my understanding  [[field_map]]  replaces the 
default field map, leading to a LOOP packet only containing the configured  
[[field_map]], but obviously I was wrong :) :

LOOP:   2024-01-22 06:16:03 CET (1705900563) 'altimeter': 
'1025.4477187548832', 'appTemp': '-6.253423533619011', 'barometer': 
'1028.5013923390995', 'cloudbase': '1041.4809012741189', 'dateTime': 
'1705900563', 'daymaxwind': '6.6', 'dayRain': '0.0', 'dewpoint': 
'-6.533418604408247', 'ET': 'None', 'extraHumid6': '59', 'extraHumid7': 
'61', 'extraHumid8': '57', 'extraTemp6': '14.7', 'extraTemp7': '20.5', 
'extraTemp8': '21.3', 'heatindex': '-1.5994', 'humidex': 
'-1.6', 'inDewpoint': '9.08853654596964', 'inHumidity': '51', 'inTemp': 
'19.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': '69', 'outTemp': '-1.6', 'p_dayRain': '0.0', 'p_monthRain': 
'26.5', 'p_rain': '0.0', 'p_rainRate': '0.0', 'p_stormRain': '0.0', 
'p_weekRain': '0.0', 'p_yearRain': '26.5', 'pressure': '973.1', 
'radiation': '0.0', 'rain': '0.0', 'rainRate': '0.0', 'relbarometer': 
'1025.9', 'stormRain': '0.0', 'usUnits': '17', 'UV': '0', 'uvradiation': 
'0.0', 'weekRain': '0.0', '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.44', 'wh40_sig': '4', 'wh57_batt': '5', 'wh57_sig': '4', 'windchill': 
'-5.128915747986651', 'windDir': '206', 'windGust': '4.2', 'windrun': 
'None', 'windSpeed': '2.7', '*ws90_batt*': '3.28', 'ws90_daymaxwind': 
'7.7', 'ws90_luminosity': '0.0', 'ws90_sig': '4', 'ws90_UV': '0', 
'ws90_uvradiation': '0.0', '*ws90_windDir*': '206', 'ws90_windGust': '2.6', 
'ws90_windSpeed': '2.1', 'yearRain': '50.4'

But On RPi4, polling the devices seems to drift apart quite quickly, 
producing individual LOOP packets, containing the individual values (I 
haven't observed that happening on my Desktop, so this might be connected 
to CPU power, maybe it happens after a longer period of time) 
These LOOP packets contain values from the device configured in 
[GW1000Service] and from the device configured in [ GW1000 ] in that order, 
but *without values from the configured*  [[field_map]] in [GW1000Service] - 
I didn't expect that.  
*(Maybe also worth noting is that the batt/sig values from my WS68 are 
tagged as wh68, which I consider an undesired typo in the driver's map)*

LOOP:   2024-01-22 06:16:14 CET (1705900574) 'altimeter': 
'1025.4477187548832', 'appTemp': '-6.463423533619011', 'barometer': 
'1028.5013923390995', 'cloudbase': '1041.4809012741189', 'dateTime': 
'1705900574', 'daymaxwind': '6.6', 'dayRain': '0.0', 'dewpoint': 
'-6.533418604408247', 'ET': 'None', 'extraHumid6': '59', 'extraHumid7': 
'61', 'extraHumid8': '57', 'extraTemp6': '14.7', 'extraTemp7': '20.5', 
'extraTemp8': '21.3', 'heatindex': '-1.5994', 'humidex': 
'-1.6', 'inDewpoint': '9.08853654596964', 'inHumidity': '51', 'inTemp': 
'19.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': '69', 'outTemp': '-1.6', 'p

[weewx-user] Aucrite sensor stopped working - does it need re-registration?

[ken.r...@gmail.com]

I setup Weewx 3.9.1 about 6yrs ago when Acurite dropped support for their 
SmartHub, and haven't upgraded since.

Recently I moved home and lost a sensor in one of the packing boxes and 
then found it again after the battery had been flat for almost 6 months. It 
displays temperature and humidity and the repeater flickers when it 
transmits, but weewx is not recording any data for that sensor ID#.

Acurite gave instructions on how to register a sensor, but as the turned 
off the server that support SmartHubs I can't do that
https://support.acurite.com/hc/en-us/articles/360021588913-Add-a-Sensor-to-the-My-AcuRite-Dashboard-

I found these instructions for weewx but I'm getting errors when I try to 
sniff
https://github.com/matthewwall/weewx-interceptor

[root]# PYTHONPATH=bin python /usr/share/weewx/user/interceptor.py 
--conf=/etc/weewx/weewx.conf --device=acurite-bridge --mode=sniff 
--iface=ens3 --filter="src XXX.XXX.XXX.XXX and dst port 80"
Traceback (most recent call last):
  File "/usr/share/weewx/user/interceptor.py", line 212, in 
import weewx.drivers
ImportError: No module named weewx.drivers

Could the sensor have lost it's ID? The reset button on the sensor doesn't 
help. What else can I try?

-- 
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/766727b3-a72f-49b1-afd0-2fe7d9592343n%40googlegroups.com.