date:20240201

Re: [weewx-user] RS485 Pyranometer and Weewx

2024-02-01 Thread weather list

Jon,

Did you make any progress with either of those units? I'd be glad to hear any 
details.

> On 6 Jan, 2024, at 09:48, 'Jon Fear' via weewx-user 
> mailto:weewx-user@googlegroups.com>> wrote:
> 
> Hi Folks
> 
> Just been gifted a Vaisala WTX536 which will now become my goto device for my 
> weather station. I have a WS90 Wittboy with a separate rain gauge and 
> Temperature sensor. I also have a Davis Vue which seems to be missing the 
> rain side of things
> 
> So to the min part of the post, a Pyranometer.
> 
> Has anyone yet tried the Pyranometers that are now coming out of China such 
> as this one:
> 
> https://www.aliexpress.com/item/1005004417770153.html?spm=a2g0o.productlist.main.13.315e3767OTDN8D_pvid=0999474d-38f9-4262-a5b1-84e578e95f28_exp_id=0999474d-38f9-4262-a5b1-84e578e95f28-6_npi=4%40dis%21GBP%2156.04%2144.83%21%21%2169.07%21%21%40211b617a17044856686191647e24c7%211229113037964%21sea%21UK%21137599046%21=Qxj6jXEgUCne=scene%3Asearch%7Cquery_from%3A
>  
> 
> 
> Which is good for solar radiation or this  one:
> 
> https://www.aliexpress.com/item/1005005609001227.html?spm=a2g0o.productlist.main.25.315e3767OTDN8D_pvid=0999474d-38f9-4262-a5b1-84e578e95f28_exp_id=0999474d-38f9-4262-a5b1-84e578e95f28-12_npi=4%40dis%21GBP%2146.66%2137.33%21%21%2157.50%21%21%40211b617a17044856686191647e24c7%211233737748177%21sea%21UK%21137599046%21=AMTQ2u7rL6Ql
>  
> 
> 
> Which appears to cover UV.
> 
> Obviously there is  the calibration element of this but has anyone:
> 
> 1. Tried either?
> 2. if so interfaced it with Weewx?
> 3. Got Weewx to take data from multiple sources.
> 
> I am thinking of selling the WS90 but keeping the rain gauge and the soil 
> sensors, keeping the Davis, keeping the Vaisala and adding at least the solar 
> radiation sensor.
> 
> Any sensible thoughts, comments and suggestions would be welcome. 
> Unfortunately I am another of those people that do not do code. I am a 
> hardware man...If you need it made, easy, simple PTH electronics no problem! 
> Code, I'll get my hat!
> 
> Thank you folks
> 
> Jon
> 
> -- 
> 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/92786cbb-4211-4124-9417-cf3ec82a9bcen%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/6EADC8E5-FBA0-4428-9EC1-1BDB2C67290F%40gmail.com.

[weewx-user] Re: weewx.service fails at reboot

2024-02-01 Thread 'michael.k...@gmx.at' via weewx-user

The "cosmetic curiosity" is because the date in seasons skin's output is 
formatted using to the locale set for weewx, which is the OS' default 
locale, if not explicitly set otherwise.

en_GB is the default default (yes, 2x default) locale on RasperryPI OS. 
Install your desired locale using raspi-config and set it as the OS default 
locale, or start weewx with this locale.

By now, you cannot set an other locale, than the the one you run weewx 
with, for report generation, see https://github.com/weewx/weewx/issues/867

Vetti52 schrieb am Donnerstag, 1. Februar 2024 um 22:27:26 UTC+1:

> After upgrading to version 5.0.0, I can regularily observe, that starting 
> Weewx  sudo sdystemctl status weewx.service fails because of network 
> error.
>
> My setup is a Rasperry Pi4 under a freshly installed bookworm. I installed 
> the apt package as described in the guide, immediately stopped Weewx and 
> edited weewx.conf to adopt my previous settings. That is to change to 
> GW1000. I also changed from US to metric.
> As the Raspi has no display nor keyboard, I log in via ssd. Usually it 
> runs without interaction for many months. However, up to date rebooting was 
> not a problem. No, I have to log in and do a sudo systemctl start weewx, 
> which I would like to avoid, as I tend to forget this, when doing it once 
> per year or so.
> Why does this happen since version 5.0.0?  And, if there are new 
> conditions for starting, is  there a way to tell weewx, to wait for an 
> established network?
>
> BTW, I found a more of cosmetic curiosity: The date in the seasons skin is 
> now displayed in form of dd/mm/yy. Ok, I can read it , but it is very 
> unusual. As I did not touch this part in the seasons files, I have now 
> idea, where this format comes from.
>
> Thanks for any suggestions
> Peter
>

-- 
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/20df6174-153c-4b53-b0a5-8c6c2c136a9bn%40googlegroups.com.

[weewx-user] Re: Zambretti forecast in StellSeries

2024-02-01 Thread gjr80

If you want to use the Zambretti forecast text in the gauge-data.txt
template you will need to install the WeeWX forecast extension
. This extension has some
issues, mostly with weather services such as WU (changed API) and
DarkSky(now defunct) etc, but as far as I know the Zambretti forecast still
works. If it doesn't work under WeeWX v4 or v5 you should try one of the
forks. This one should
work.

Once installed you need to set the Zambretti forecast to work, there is
little on Zambretti in the extension documentation, but if you read the
comments
in forecast.py

it tells you what needs to go into the [Forecast] [[Zambretti]] stanza
(from memory you can get by with just telling it you hemisphere). You then
need to make the forecast variable available in your gauge-data.txt
template by adding search_list_extensions = user.forecast.ForecastVariables
to your SteelSeries skin config file, again this is covered in the comments
in forecast.py

You will need to restart WeeWX after installing and configuring the
forecast extension.

I do not use the gauge-data.txt template or the forecast extension, but if
they above do not work they should get you close. If you need to
troubleshoot first confirm the Zambretti forecast is working and the
forecast database is being populated, then look at whether the
gauge-data.txt template is obtaining the Zambretti forecast text.

Gary

--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/8a64f4c5-373f-4ead-bf92-1ec8de8a77f7n%40googlegroups.com.

Re: [weewx-user] Re: Trouble installing WeeWX-MQTTSubscribe

2024-02-01 Thread Frank Gruhlke

Hey Rich, thanks again... I managed to get my out-door temp to read F with 
this in my weewx.conf:

temperature_C
ignore = false
name = outTemp
units = degree_C

I have tried every "units" option for Weewx  Barometer unit ( inHg, mbar, 
hPa and kpa)
for the "pa" field in my mqtt topic.

 [[[pa
  ignore = false # opt back in for this field
   name = barometer
   units = hPa

I just get  N/A (N/A) for the Barometer Reading in my reports.
I don't see any errors restarting weewx.

Here is what I am subscribed to in the driver.
"pa" is the pressure reading I am trying to bring into Weewx

{
"tempc": 20.59,
"tempf": 69.062,
"hum": 38.88184,
"pa": 98790.06,
"altim": 213.1839,
"altift": 699.4224
}


*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/f7fd60e2-6b3a-4eb8-a187-3dbc1fdd6f98n%40googlegroups.com.

[weewx-user] Re: weewx.service fails at reboot

2024-02-01 Thread vince

Without seeing your logs and the gw1000 section of weewx.conf, we can't 
help too much.

As always start with setting debug=1, restart weewx, let it run through at 
least 'two' archive periods, and post the log.

WeeWX isn't going to start nor run reliably if the driver can't find your 
ecowitt gateway, which happens if your network is unstable and especially 
if the pi is on wifi.  We'd need to see the gw1000 section of weewx.conf to 
suggest much there.   And what ip is your pi and what ip is the ecowitt 
gateway ?

Also does this happen on 'reboot' or on 'power down and up' ?   The pi has 
no battery backed realtime clock so weewx might be waiting for your pi to 
get accurate network time.

On Thursday, February 1, 2024 at 1:27:26 PM UTC-8 Vetti52 wrote:

> After upgrading to version 5.0.0, I can regularily observe, that starting 
> Weewx  sudo sdystemctl status weewx.service fails because of network 
> error.
>
> My setup is a Rasperry Pi4 under a freshly installed bookworm. I installed 
> the apt package as described in the guide, immediately stopped Weewx and 
> edited weewx.conf to adopt my previous settings. That is to change to 
> GW1000. I also changed from US to metric.
> As the Raspi has no display nor keyboard, I log in via ssd. Usually it 
> runs without interaction for many months. However, up to date rebooting was 
> not a problem. No, I have to log in and do a sudo systemctl start weewx, 
> which I would like to avoid, as I tend to forget this, when doing it once 
> per year or so.
> Why does this happen since version 5.0.0?  And, if there are new 
> conditions for starting, is  there a way to tell weewx, to wait for an 
> established network?
>
> BTW, I found a more of cosmetic curiosity: The date in the seasons skin is 
> now displayed in form of dd/mm/yy. Ok, I can read it , but it is very 
> unusual. As I did not touch this part in the seasons files, I have now 
> idea, where this format comes from.
>
> Thanks for any suggestions
> Peter
>

-- 
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/a8b56d1b-ac98-409b-b65d-52addb742565n%40googlegroups.com.

[weewx-user] weewx.service fails at reboot

2024-02-01 Thread Vetti52

After upgrading to version 5.0.0, I can regularily observe, that starting
Weewx sudo sdystemctl status weewx.service fails because of network error.

My setup is a Rasperry Pi4 under a freshly installed bookworm. I installed
the apt package as described in the guide, immediately stopped Weewx and
edited weewx.conf to adopt my previous settings. That is to change to
GW1000. I also changed from US to metric.
As the Raspi has no display nor keyboard, I log in via ssd. Usually it runs
without interaction for many months. However, up to date rebooting was not
a problem. No, I have to log in and do a sudo systemctl start weewx, which
I would like to avoid, as I tend to forget this, when doing it once per
year or so.
Why does this happen since version 5.0.0? And, if there are new conditions
for starting, is there a way to tell weewx, to wait for an established
network?

BTW, I found a more of cosmetic curiosity: The date in the seasons skin is
now displayed in form of dd/mm/yy. Ok, I can read it , but it is very
unusual. As I did not touch this part in the seasons files, I have now
idea, where this format comes from.

Thanks for any suggestions
Peter

--
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/a600110f-25c6-41a7-85d2-ba590a25ccf1n%40googlegroups.com.

[weewx-user] Re: v5 git 'install' and logging

2024-02-01 Thread Tom Keffer

You are not missing anything at all! It's a bug --- and a pretty obvious 
one that I should have caught a long time ago.

Thanks for pointing it out!

Fixed in commit 218085 

.

On Thursday, February 1, 2024 at 9:00:27 AM UTC-8 bell...@gmail.com wrote:

> I am using a v5 git 'install'. I have checked out 'tags/v5.0.0'. I am not 
> using venv, I use pyenv so that I can easily change the python version I am 
> using. I set debug = 1 in weewx.conf, but I don't seem to be getting any 
> 'debug' logging.
>
> Looking at the code, I see a default of 'False' is set in 
> ~/weewx/src/weewx/__init__.py
>
> In ~/weewx/src/weewxd.py there is a call to 
> weeutil.logger.setup(namespace.log_label, config_dict) which does the 
> following
> log_level = 'DEBUG' if weewx.debug else 'INFO'
> .
> .
> .
> logging.config.dictConfig(log_dict)
>
> Later in ~/weewx/src/weewxd.py this is called, weewx_root, user_module = 
> weeutil.startup.initialize(config_dict)
> And it sets weewx.debug = to_int(config_dict.get('debug', 0))
>
> Here the log I am seeing at startup
>weewxd[44781]: INFO __main__: Initializing weewxd version 5.0.0
>weewxd[44781]: INFO __main__: Command line: ~/weewx/src/weewxd.py
>weewxd[44781]: INFO __main__: Using Python 3.10.13 (main, Oct 23 2023, 
> 11:48:50) [GCC 11.4.0]
>weewxd[44781]: INFO __main__: Located at 
> ~/.pyenv/versions/3.10.13/bin/python3
>weewxd[44781]: INFO __main__: Platform 
> Linux-5.15.0-92-generic-x86_64-with-glibc2.35
>weewxd[44781]: INFO __main__: Locale: 'en_US.UTF-8'
>weewxd[44781]: INFO __main__: Entry path: ~/weewx/src/weewxd.py
>weewxd[44781]: INFO __main__: WEEWX_ROOT: ~/weewx-data
>weewxd[44781]: INFO __main__: Configuration file: 
> ~/weewx-data/weewx.conf
>weewxd[44781]: INFO __main__: User module: ~/weewx-data/bin/user
>weewxd[44781]: INFO __main__: Debug: 1
>weewxd[44781]: INFO weewx.engine: Loading station type Simulator 
> (weewx.drivers.simulator)
>weewxd[44781]: INFO weewx.engine: StdConvert target unit is 0x1
>weewxd[44781]: INFO weewx.wxservices: StdWXCalculate will use data 
> binding wx_binding
>weewxd[44781]: INFO weewx.engine: Archive will use data binding 
> wx_binding
>weewxd[44781]: INFO weewx.engine: Record generation will be attempted 
> in 'hardware'
>weewxd[44781]: INFO weewx.engine: Using archive interval of 300 seconds 
> (specified in weewx configuration)
>weewxd[44781]: INFO weewx.restx: StationRegistry: Registration not 
> requested.
>weewxd[44781]: INFO weewx.restx: Wunderground: Posting not enabled.
>weewxd[44781]: INFO weewx.restx: PWSweather: Posting not enabled.
>weewxd[44781]: INFO weewx.restx: CWOP: Posting not enabled.
>weewxd[44781]: INFO weewx.restx: WOW: Posting not enabled.
>weewxd[44781]: INFO weewx.restx: AWEKAS: Posting not enabled.
>weewxd[44781]: INFO weewx.engine: 'pyephem' detected, extended almanac 
> data is available
>weewxd[44781]: INFO __main__: Starting up weewx version 5.0.0
>weewxd[44781]: INFO weewx.engine: Clock error is -0.03 seconds 
> (positive is fast)
>weewxd[44781]: INFO weewx.engine: Using binding 'wx_binding' to 
> database 'weewx.sdb'
>weewxd[44781]: INFO weewx.manager: Starting backfill of daily summaries
>weewxd[44781]: INFO weewx.manager: Empty database
>weewxd[44781]: INFO weewx.engine: Starting main packet loop.
>
>
> If I set debug = True in ~/weewx/src/weewx/__init__.py, I get this log
>
>weewxd[45469]: INFO __main__: Initializing weewxd version 5.0.0
>weewxd[45469]: INFO __main__: Command line: ~/weewx/src/weewxd.py
>weewxd[45469]: INFO __main__: Using Python 3.10.13 (main, Oct 23 2023, 
> 11:48:50) [GCC 11.4.0]
>weewxd[45469]: INFO __main__: Located at 
> ~/.pyenv/versions/3.10.13/bin/python3
>weewxd[45469]: INFO __main__: Platform 
> Linux-5.15.0-92-generic-x86_64-with-glibc2.35
>weewxd[45469]: INFO __main__: Locale: 'en_US.UTF-8'
>weewxd[45469]: INFO __main__: Entry path: ~/weewx/src/weewxd.py
>weewxd[45469]: INFO __main__: WEEWX_ROOT: ~/weewx-data
>weewxd[45469]: INFO __main__: Configuration file: 
> ~/weewx-data/weewx.conf
>weewxd[45469]: INFO __main__: User module: ~/weewx-data/bin/user
>weewxd[45469]: INFO __main__: Debug: 1
>weewxd[45469]: DEBUG __main__: Initializing engine
>weewxd[45469]: INFO weewx.engine: Loading station type Simulator 
> (weewx.drivers.simulator)
>weewxd[45469]: DEBUG weewx.engine: Loading service 
> weewx.engine.StdTimeSynch
>weewxd[45469]: DEBUG weewx.engine: Finished loading service 
> weewx.engine.StdTimeSynch
>weewxd[45469]: DEBUG weewx.engine: Loading service 
> weewx.engine.StdConvert
>weewxd[45469]: INFO weewx.engine: StdConvert target unit is 0x1
>weewxd[45469]: DEBUG weewx.engine: Finished loading service 
> weewx.engine.StdConvert
>weewxd[45469]: DEBUG weewx.engine: Loading

[weewx-user] v5 git 'install' and logging

2024-02-01 Thread bell...@gmail.com

I am using a v5 git 'install'. I have checked out 'tags/v5.0.0'. I am not 
using venv, I use pyenv so that I can easily change the python version I am 
using. I set debug = 1 in weewx.conf, but I don't seem to be getting any 
'debug' logging.

Looking at the code, I see a default of 'False' is set in 
~/weewx/src/weewx/__init__.py

In ~/weewx/src/weewxd.py there is a call to 
weeutil.logger.setup(namespace.log_label, config_dict) which does the 
following
log_level = 'DEBUG' if weewx.debug else 'INFO'
.
.
.
logging.config.dictConfig(log_dict)

Later in ~/weewx/src/weewxd.py this is called, weewx_root, user_module = 
weeutil.startup.initialize(config_dict)
And it sets weewx.debug = to_int(config_dict.get('debug', 0))

Here the log I am seeing at startup
   weewxd[44781]: INFO __main__: Initializing weewxd version 5.0.0
   weewxd[44781]: INFO __main__: Command line: ~/weewx/src/weewxd.py
   weewxd[44781]: INFO __main__: Using Python 3.10.13 (main, Oct 23 2023, 
11:48:50) [GCC 11.4.0]
   weewxd[44781]: INFO __main__: Located at 
~/.pyenv/versions/3.10.13/bin/python3
   weewxd[44781]: INFO __main__: Platform 
Linux-5.15.0-92-generic-x86_64-with-glibc2.35
   weewxd[44781]: INFO __main__: Locale: 'en_US.UTF-8'
   weewxd[44781]: INFO __main__: Entry path: ~/weewx/src/weewxd.py
   weewxd[44781]: INFO __main__: WEEWX_ROOT: ~/weewx-data
   weewxd[44781]: INFO __main__: Configuration file: ~/weewx-data/weewx.conf
   weewxd[44781]: INFO __main__: User module: ~/weewx-data/bin/user
   weewxd[44781]: INFO __main__: Debug: 1
   weewxd[44781]: INFO weewx.engine: Loading station type Simulator 
(weewx.drivers.simulator)
   weewxd[44781]: INFO weewx.engine: StdConvert target unit is 0x1
   weewxd[44781]: INFO weewx.wxservices: StdWXCalculate will use data 
binding wx_binding
   weewxd[44781]: INFO weewx.engine: Archive will use data binding 
wx_binding
   weewxd[44781]: INFO weewx.engine: Record generation will be attempted in 
'hardware'
   weewxd[44781]: INFO weewx.engine: Using archive interval of 300 seconds 
(specified in weewx configuration)
   weewxd[44781]: INFO weewx.restx: StationRegistry: Registration not 
requested.
   weewxd[44781]: INFO weewx.restx: Wunderground: Posting not enabled.
   weewxd[44781]: INFO weewx.restx: PWSweather: Posting not enabled.
   weewxd[44781]: INFO weewx.restx: CWOP: Posting not enabled.
   weewxd[44781]: INFO weewx.restx: WOW: Posting not enabled.
   weewxd[44781]: INFO weewx.restx: AWEKAS: Posting not enabled.
   weewxd[44781]: INFO weewx.engine: 'pyephem' detected, extended almanac 
data is available
   weewxd[44781]: INFO __main__: Starting up weewx version 5.0.0
   weewxd[44781]: INFO weewx.engine: Clock error is -0.03 seconds (positive 
is fast)
   weewxd[44781]: INFO weewx.engine: Using binding 'wx_binding' to database 
'weewx.sdb'
   weewxd[44781]: INFO weewx.manager: Starting backfill of daily summaries
   weewxd[44781]: INFO weewx.manager: Empty database
   weewxd[44781]: INFO weewx.engine: Starting main packet loop.


If I set debug = True in ~/weewx/src/weewx/__init__.py, I get this log

   weewxd[45469]: INFO __main__: Initializing weewxd version 5.0.0
   weewxd[45469]: INFO __main__: Command line: ~/weewx/src/weewxd.py
   weewxd[45469]: INFO __main__: Using Python 3.10.13 (main, Oct 23 2023, 
11:48:50) [GCC 11.4.0]
   weewxd[45469]: INFO __main__: Located at 
~/.pyenv/versions/3.10.13/bin/python3
   weewxd[45469]: INFO __main__: Platform 
Linux-5.15.0-92-generic-x86_64-with-glibc2.35
   weewxd[45469]: INFO __main__: Locale: 'en_US.UTF-8'
   weewxd[45469]: INFO __main__: Entry path: ~/weewx/src/weewxd.py
   weewxd[45469]: INFO __main__: WEEWX_ROOT: ~/weewx-data
   weewxd[45469]: INFO __main__: Configuration file: ~/weewx-data/weewx.conf
   weewxd[45469]: INFO __main__: User module: ~/weewx-data/bin/user
   weewxd[45469]: INFO __main__: Debug: 1
   weewxd[45469]: DEBUG __main__: Initializing engine
   weewxd[45469]: INFO weewx.engine: Loading station type Simulator 
(weewx.drivers.simulator)
   weewxd[45469]: DEBUG weewx.engine: Loading service 
weewx.engine.StdTimeSynch
   weewxd[45469]: DEBUG weewx.engine: Finished loading service 
weewx.engine.StdTimeSynch
   weewxd[45469]: DEBUG weewx.engine: Loading service 
weewx.engine.StdConvert
   weewxd[45469]: INFO weewx.engine: StdConvert target unit is 0x1
   weewxd[45469]: DEBUG weewx.engine: Finished loading service 
weewx.engine.StdConvert
   weewxd[45469]: DEBUG weewx.engine: Loading service 
weewx.engine.StdCalibrate
   weewxd[45469]: DEBUG weewx.engine: Finished loading service 
weewx.engine.StdCalibrate
   weewxd[45469]: DEBUG weewx.engine: Loading service weewx.engine.StdQC
   weewxd[45469]: DEBUG weewx.engine: Finished loading service 
weewx.engine.StdQC
   weewxd[45469]: DEBUG weewx.engine: Loading service 
weewx.wxservices.StdWXCalculate
   weewxd[45469]: INFO weewx.wxservices: StdWXCalculate will use data 
binding wx_binding
   weewxd[45469]: DEBUG weewx.manager: Daily summary version is 4.0

Re: [weewx-user] Timeout errors with WMR88

2024-02-01 Thread Tom Keffer

These are often caused by an inadequate power supply through the USB
connection. Try using a powered USB hub if you have one. Or, a bigger power
supply for the ASUS board. See if that helps.

On Thu, Feb 1, 2024 at 2:59 AM Scott Picton  wrote:

> I've recently got my WRM88 running with WeeWX. I'm running it off a ASUS
> Tinkerboard, loaded with DietPi and a few other services. I installed via
> apt (having to use the old gpg keys).
>
> For the most part it appeared to be running well, however I have been
> getting random timeout errors. Sometimes after hours, sometimes after
> almost a full 24 hours. After the timeout message I then get pipe errors
> each time it tries to read the station. If I unplug and replug the usb,
> then restart weewx then all works again for a while.
>
> I had the same weather station running fine on a RPi with wview and didn't
> appear to have any issues.
>
> I've got debugging on, but really it didn't seem to show much more
> information than without?
>
> Here's the log:
>
> ```
> Jan 29 22:25:38 tinkerboard1 weewxd[433]: INFO weewx.reportengine: Copied
> 0 files to /var/www/html/weewx
> Jan 29 22:30:36 tinkerboard1 weewxd[433]: INFO weewx.manager: Added record
> 2024-01-29 22:30:00 AEDT (1706527800) to database 'weewx.sdb'
> Jan 29 22:30:36 tinkerboard1 weewxd[433]: INFO weewx.manager: Added record
> 2024-01-29 22:30:00 AEDT (1706527800) to daily summary in 'weewx.sdb'
> Jan 29 22:30:37 tinkerboard1 weewxd[433]: ERROR weewx.drivers.wmr100:
> Unable to send USB control message: [Errno 110] Operation timed out
> Jan 29 22:30:37 tinkerboard1 weewxd[433]: INFO weewx.engine: Main loop
> exiting. Shutting engine down.
> Jan 29 22:30:37 tinkerboard1 weewxd[433]: INFO weewx.engine: Shutting down
> StdReport thread
> Jan 29 22:30:37 tinkerboard1 weewxd[433]: INFO weewx.cheetahgenerator:
> Generated 8 files for report SeasonsReport in 1.20 seconds
> Jan 29 22:30:38 tinkerboard1 weewxd[433]: INFO weewx.imagegenerator:
> Generated 12 images for report SeasonsReport in 0.55 seconds
> Jan 29 22:30:38 tinkerboard1 weewxd[433]: INFO weewx.reportengine: Copied
> 0 files to /var/www/html/weewx
> Jan 29 22:30:38 tinkerboard1 weewxd[433]: CRITICAL __main__: Caught
> WeeWxIOError: [Errno 110] Operation timed out
> Jan 29 22:30:38 tinkerboard1 weewxd[433]: CRITICAL __main__: 
>  Waiting 60.0 seconds then retrying...
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO __main__: retrying...
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: Loading
> station type WMR100 (weewx.drivers.wmr100)
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.drivers.wmr100:
> Driver version is 3.5.0
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.drivers.wmr100:
> Sensor map is {'pressure': 'pressure', 'windSpeed': 'wind_speed',
> 'windDir': 'wind_dir', 'windGust': 'wind_gust', 'windBatteryStatus':
> 'battery_status_wind', 'inTemp':>
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: StdConvert
> target unit is 0x1
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.wxservices:
> StdWXCalculate will use data binding wx_binding
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: Archive will
> use data binding wx_binding
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: Record
> generation will be attempted in 'hardware'
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: Using archive
> interval of 300 seconds (specified in weewx configuration)
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.restx:
> StationRegistry: Registration not requested.
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.restx: Wunderground:
> Posting not enabled.
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.restx: PWSweather:
> Posting not enabled.
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.restx: CWOP: Posting
> not enabled.
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.restx: WOW: Posting
> not enabled.
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.restx: AWEKAS:
> Posting not enabled.
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: 'pyephem'
> detected, extended almanac data is available
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO __main__: Starting up weewx
> version 5.0.0
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: Using binding
> 'wx_binding' to database 'weewx.sdb'
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.manager: Starting
> backfill of daily summaries
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.manager: Daily
> summaries up to date
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: Starting main
> packet loop.
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: ERROR weewx.drivers.wmr100:
> Unable to send USB control message: [Errno 32] Pipe error
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: Main loop
> exiting. Shutting engine down.
> Jan 29 22:31:38 tinkerboard1 weewxd[433]: CRITICAL __main__: Caught
> WeeWxIOError:

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

2024-02-01 Thread Chris McLeod

Tomasz, 

Thank you very much for the steps on how to manually install the driver!
Chris 

On Thursday, February 1, 2024 at 1:15:20 AM UTC-7 Tomasz Lewicki wrote:

> That's strange message. When you manualy decompress ZIP (I suppose 
> downloaded from GitHub) and look into install.py, last line says:
>
> *files=[('bin/user', ['bin/user/interceptor.py'])]*
>
> I don't know why in your case there is / (slash) in error message:
>
> *FileNotFoundError: [Errno 2] No such file or directory: 
> '/bin/user/interceptor.py'*
>
> But I think you can manually copy just one file - *interceptor.py*  - to 
> */etc/weewx/bin/user* directory and make changes in *weewx.conf,* then 
> restart weewx, it should work. There are additiional files in *util* 
> directory but install.py omits them so they are not necessary. 
> czwartek, 1 lutego 2024 o 08:35:01 UTC+1 Chris McLeod napisał(a):
>
>> @Tomasz, you stated above that ' I installed both interceptor and HP1000 
>> drivers by weectl. " Can you provide some insight into how you did this? I 
>> have a fresh install of 5.0.1 and when I run 'weectl extension install 
>> weewx-interceptor.zip (fresh download) I get an error stack below. I am 
>> posting here just in case I am missing something obvious, if not I will 
>> start a new thread. 
>>
>> Thanks, 
>> Chris 
>>
>> :~$ weectl extension install weewx-interceptor.zip
>> Using configuration file /etc/weewx/weewx.conf
>> Install extension 'weewx-interceptor.zip' (y/n)? y
>> Extracting from zip archive weewx-interceptor.zip
>>
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/weectl.py", line 74, in 
>> main()
>>   File "/usr/share/weewx/weectl.py", line 66, in main
>> namespace.func(namespace)
>>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
>> namespace.action_func(config_dict, namespace)
>>   File "/usr/share/weewx/weectllib/extension_cmd.py", line 116, in 
>> install_extension
>> ext.install_extension(namespace.source, no_confirm=namespace.yes)
>>   File "/usr/share/weewx/weecfg/extension.py", line 138, in 
>> install_extension
>> extension_name = self._install_from_file(extension_path, filetype)
>>   File "/usr/share/weewx/weecfg/extension.py", line 168, in 
>> _install_from_file
>> extension_name = self.install_from_dir(extension_dir)
>>   File "/usr/share/weewx/weecfg/extension.py", line 185, in 
>> install_from_dir
>> self._install_files(installer['files'], extension_dir)
>>   File "/usr/share/weewx/weecfg/extension.py", line 269, in _install_files
>> shutil.copy(source_path, destination_path)
>>   File "/usr/lib/python3.8/shutil.py", line 418, in copy
>> copyfile(src, dst, follow_symlinks=follow_symlinks)
>>   File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
>> with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
>> FileNotFoundError: [Errno 2] No such file or directory: 
>> '/bin/user/interceptor.py'
>>
>> On Thursday, January 25, 2024 at 1:27:34 AM UTC-7 Tomasz Lewicki wrote:
>>
>>> Mystery solved. 
>>>
>>> But answering to vince question, my system is rather typical - Raspbian 
>>> on Raspberry Pi, only WLAN interface is active. Weewx was unwillingly 
>>> updated from 4.10.2 to 5.0.0. I checked all point of failure: Python 
>>> version, permissions (thank you Gary!), network traffic. As I wrote before, 
>>> rtupdate.wunderground.com was hijacked - local DNS redirected it to 
>>> Weewx. So I deleted this bypass, allowing console to send data to real WU 
>>> server. But still I couldn't see any traffic on my router. Total silence. 
>>> It was abnormal (and it explains why PCAP file captured by Tshark was empty 
>>> on port 80). But I didn't check WU settings in WiFi console. Station ID was 
>>> empty, password was obfuscated by asterisks. I don't use WU website at all, 
>>> I just needed credentials for conversation between console and Weewx. I 
>>> entered ID and password - and then console started send data to real WU. So 
>>> I redirected  network traffic on my DNS again, and Weewx started to receive 
>>> data from WiFi console via interceptor driver :)
>>>
>>> Thank you to everyone who patiently read my writings and tried to help.
>>>
>>> środa, 24 stycznia 2024 o 22:54:46 UTC+1 vince napisał(a):
>>>
 Difficult to answer with no info from you on exactly 'what' command you 
 ran for wireshark and whether your listening computer is wifi, ethernet, 
 or 
 both.  What kind of computer are you running on ?  What os ?  What version 
 ?  Which interfaces ?  What was your 'exact' wireshark command ?

 But I see nothing basically in that 6-second pcap.  If running a 
 sniffer on your computer sees no traffic being redirected from the 
 station, 
 then there is nothing for interceptor to intercept on the weewx computer.

 Again, when you say "*But I hijacked DNS on my router*" that (to me) 
 does not cause any traffic from your station to wunderground to be 
 redirected to your

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

2024-02-01 Thread Chris McLeod

Gary, 

Thank you very much for the quick reply. I will stand by for the new 
release. 

Thanks,
Chris

On Thursday, February 1, 2024 at 1:52:59 AM UTC-7 gjr80 wrote:

> You have almost certainly encountered the bug mentioned in this post 
> . 
> The bug does not bite (ie potentially delete system files) unless you 
> uninstall the extension using weectl extension - so my strong advice to 
> you is do not attempt to uninstall the extension. A manual uninstall (or 
> install) will be fine. But I would further suggest waiting a few days for 
> v5.0.1 which fixes this bug, its release should not be too far off.
>
> Gary
>
> On Thursday 1 February 2024 at 17:35:01 UTC+10 csm...@gmail.com wrote:
>
>> @Tomasz, you stated above that ' I installed both interceptor and HP1000 
>> drivers by weectl. " Can you provide some insight into how you did this? I 
>> have a fresh install of 5.0.1 and when I run 'weectl extension install 
>> weewx-interceptor.zip (fresh download) I get an error stack below. I am 
>> posting here just in case I am missing something obvious, if not I will 
>> start a new thread. 
>>
>> Thanks, 
>> Chris 
>>
>> :~$ weectl extension install weewx-interceptor.zip
>> Using configuration file /etc/weewx/weewx.conf
>> Install extension 'weewx-interceptor.zip' (y/n)? y
>> Extracting from zip archive weewx-interceptor.zip
>>
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/weectl.py", line 74, in 
>> main()
>>   File "/usr/share/weewx/weectl.py", line 66, in main
>> namespace.func(namespace)
>>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
>> namespace.action_func(config_dict, namespace)
>>   File "/usr/share/weewx/weectllib/extension_cmd.py", line 116, in 
>> install_extension
>> ext.install_extension(namespace.source, no_confirm=namespace.yes)
>>   File "/usr/share/weewx/weecfg/extension.py", line 138, in 
>> install_extension
>> extension_name = self._install_from_file(extension_path, filetype)
>>   File "/usr/share/weewx/weecfg/extension.py", line 168, in 
>> _install_from_file
>> extension_name = self.install_from_dir(extension_dir)
>>   File "/usr/share/weewx/weecfg/extension.py", line 185, in 
>> install_from_dir
>> self._install_files(installer['files'], extension_dir)
>>   File "/usr/share/weewx/weecfg/extension.py", line 269, in _install_files
>> shutil.copy(source_path, destination_path)
>>   File "/usr/lib/python3.8/shutil.py", line 418, in copy
>> copyfile(src, dst, follow_symlinks=follow_symlinks)
>>   File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
>> with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
>> FileNotFoundError: [Errno 2] No such file or directory: 
>> '/bin/user/interceptor.py'
>>
>> On Thursday, January 25, 2024 at 1:27:34 AM UTC-7 Tomasz Lewicki wrote:
>>
>>> Mystery solved. 
>>>
>>> But answering to vince question, my system is rather typical - Raspbian 
>>> on Raspberry Pi, only WLAN interface is active. Weewx was unwillingly 
>>> updated from 4.10.2 to 5.0.0. I checked all point of failure: Python 
>>> version, permissions (thank you Gary!), network traffic. As I wrote before, 
>>> rtupdate.wunderground.com was hijacked - local DNS redirected it to 
>>> Weewx. So I deleted this bypass, allowing console to send data to real WU 
>>> server. But still I couldn't see any traffic on my router. Total silence. 
>>> It was abnormal (and it explains why PCAP file captured by Tshark was empty 
>>> on port 80). But I didn't check WU settings in WiFi console. Station ID was 
>>> empty, password was obfuscated by asterisks. I don't use WU website at all, 
>>> I just needed credentials for conversation between console and Weewx. I 
>>> entered ID and password - and then console started send data to real WU. So 
>>> I redirected  network traffic on my DNS again, and Weewx started to receive 
>>> data from WiFi console via interceptor driver :)
>>>
>>> Thank you to everyone who patiently read my writings and tried to help.
>>>
>>> środa, 24 stycznia 2024 o 22:54:46 UTC+1 vince napisał(a):
>>>
 Difficult to answer with no info from you on exactly 'what' command you 
 ran for wireshark and whether your listening computer is wifi, ethernet, 
 or 
 both.  What kind of computer are you running on ?  What os ?  What version 
 ?  Which interfaces ?  What was your 'exact' wireshark command ?

 But I see nothing basically in that 6-second pcap.  If running a 
 sniffer on your computer sees no traffic being redirected from the 
 station, 
 then there is nothing for interceptor to intercept on the weewx computer.

 Again, when you say "*But I hijacked DNS on my router*" that (to me) 
 does not cause any traffic from your station to wunderground to be 
 redirected to your weewx system unless I'm not understanding what you're 
 saying.  Perhaps you should tell everybody what

[weewx-user] Timeout errors with WMR88

2024-02-01 Thread Scott Picton

I've recently got my WRM88 running with WeeWX. I'm running it off a ASUS 
Tinkerboard, loaded with DietPi and a few other services. I installed via 
apt (having to use the old gpg keys).

For the most part it appeared to be running well, however I have been 
getting random timeout errors. Sometimes after hours, sometimes after 
almost a full 24 hours. After the timeout message I then get pipe errors 
each time it tries to read the station. If I unplug and replug the usb, 
then restart weewx then all works again for a while.

I had the same weather station running fine on a RPi with wview and didn't 
appear to have any issues.

I've got debugging on, but really it didn't seem to show much more 
information than without?

Here's the log:

```
Jan 29 22:25:38 tinkerboard1 weewxd[433]: INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx
Jan 29 22:30:36 tinkerboard1 weewxd[433]: INFO weewx.manager: Added record 
2024-01-29 22:30:00 AEDT (1706527800) to database 'weewx.sdb'
Jan 29 22:30:36 tinkerboard1 weewxd[433]: INFO weewx.manager: Added record 
2024-01-29 22:30:00 AEDT (1706527800) to daily summary in 'weewx.sdb'
Jan 29 22:30:37 tinkerboard1 weewxd[433]: ERROR weewx.drivers.wmr100: 
Unable to send USB control message: [Errno 110] Operation timed out
Jan 29 22:30:37 tinkerboard1 weewxd[433]: INFO weewx.engine: Main loop 
exiting. Shutting engine down.
Jan 29 22:30:37 tinkerboard1 weewxd[433]: INFO weewx.engine: Shutting down 
StdReport thread
Jan 29 22:30:37 tinkerboard1 weewxd[433]: INFO weewx.cheetahgenerator: 
Generated 8 files for report SeasonsReport in 1.20 seconds
Jan 29 22:30:38 tinkerboard1 weewxd[433]: INFO weewx.imagegenerator: 
Generated 12 images for report SeasonsReport in 0.55 seconds
Jan 29 22:30:38 tinkerboard1 weewxd[433]: INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx
Jan 29 22:30:38 tinkerboard1 weewxd[433]: CRITICAL __main__: Caught 
WeeWxIOError: [Errno 110] Operation timed out
Jan 29 22:30:38 tinkerboard1 weewxd[433]: CRITICAL __main__:  
 Waiting 60.0 seconds then retrying...
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO __main__: retrying...
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: Loading 
station type WMR100 (weewx.drivers.wmr100)
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.drivers.wmr100: Driver 
version is 3.5.0
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.drivers.wmr100: Sensor 
map is {'pressure': 'pressure', 'windSpeed': 'wind_speed', 'windDir': 
'wind_dir', 'windGust': 'wind_gust', 'windBatteryStatus': 
'battery_status_wind', 'inTemp':>
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: StdConvert 
target unit is 0x1
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.wxservices: 
StdWXCalculate will use data binding wx_binding
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: Archive will 
use data binding wx_binding
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: Record 
generation will be attempted in 'hardware'
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: Using archive 
interval of 300 seconds (specified in weewx configuration)
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.restx: 
StationRegistry: Registration not requested.
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.restx: Wunderground: 
Posting not enabled.
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.restx: PWSweather: 
Posting not enabled.
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.restx: CWOP: Posting 
not enabled.
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.restx: WOW: Posting 
not enabled.
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.restx: AWEKAS: Posting 
not enabled.
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: 'pyephem' 
detected, extended almanac data is available
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO __main__: Starting up weewx 
version 5.0.0
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.manager: Starting 
backfill of daily summaries
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.manager: Daily 
summaries up to date
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: Starting main 
packet loop.
Jan 29 22:31:38 tinkerboard1 weewxd[433]: ERROR weewx.drivers.wmr100: 
Unable to send USB control message: [Errno 32] Pipe error
Jan 29 22:31:38 tinkerboard1 weewxd[433]: INFO weewx.engine: Main loop 
exiting. Shutting engine down.
Jan 29 22:31:38 tinkerboard1 weewxd[433]: CRITICAL __main__: Caught 
WeeWxIOError: [Errno 32] Pipe error
Jan 29 22:31:38 tinkerboard1 weewxd[433]: CRITICAL __main__:  
 Waiting 60.0 seconds then retrying...
Jan 29 22:32:38 tinkerboard1 weewxd[433]: INFO __main__: retrying...
Jan 29 22:32:38 tinkerboard1 weewxd[433]: INFO weewx.engine: Loading 
station type WMR100 (weewx.drivers.wmr100)
```

-- 
You received this message because you are subscribed to

[weewx-user] Re: Rescaling of SteelSeries Gauges

2024-02-01 Thread 'Rory Gillies' via weewx-user

Thanks Gary, I have raised an issue on his repository.

On Thursday, February 1, 2024 at 9:15:39 AM UTC gjr80 wrote:

> Correct, not a RTGD or WeeWX issue. Something perhaps to take up with the 
> SteelSeries Weather Gauges author 
> https://github.com/mcrossley/SteelSeries-Weather-Gauges
>
> Gary
>
>
> On Thursday 1 February 2024 at 19:02:03 UTC+10 rory.g...@googlemail.com 
> wrote:
>
> I am using the SteelSeries gauges with RTGD on a 3 second update as a 
> stand-alone weather display on an old iPad. It looks great, however the 
> constant rescaling of the gauges for no apparent reason is a real problem. 
> Glancing at the display it should be possible to determine the temperature 
> and other readings by looking at the needle position without looking at the 
> numbers. Unfortunately this is not the case due to rescaling.
>
> The lowest temperature my station has recorded is -4.6ºC and the highest 
> (which was a very rare one-off) was 25.7ºC, so the scale of -10ºC to +30ºC 
> is perfect, and I have that set in the script, however it keeps rescaling 
> to -20ºC to +20ºC for no apparent reason.
>
> I can cope with the wind speed gauge rescaling, but even there I would 
> like it to remain 0 - 60mph and only rescale when it goes over 60mph. 
> Pressure, UV and solar radiation seem to stay at the values I have set.
>
> Is there any way to prevent the rescaling? I understand this really isn't 
> a Weewx or RTGD issue but there's maybe a hack out there that I haven't 
> found.
>
> Thanks,
>
> Rory
>
> You can see the page I use for the iPad here: ttps://
> www.360shetland.co.uk/weather/ss
>
>

-- 
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/317459eb-0b32-41f8-b47a-cd38e8ad0995n%40googlegroups.com.

[weewx-user] Re: Rescaling of SteelSeries Gauges

2024-02-01 Thread gjr80

Correct, not a RTGD or WeeWX issue. Something perhaps to take up with the
SteelSeries Weather Gauges
author https://github.com/mcrossley/SteelSeries-Weather-Gauges

Gary

On Thursday 1 February 2024 at 19:02:03 UTC+10 rory.g...@googlemail.com
wrote:

I am using the SteelSeries gauges with RTGD on a 3 second update as a
stand-alone weather display on an old iPad. It looks great, however the
constant rescaling of the gauges for no apparent reason is a real problem.
Glancing at the display it should be possible to determine the temperature
and other readings by looking at the needle position without looking at the
numbers. Unfortunately this is not the case due to rescaling.

The lowest temperature my station has recorded is -4.6ºC and the highest
(which was a very rare one-off) was 25.7ºC, so the scale of -10ºC to +30ºC
is perfect, and I have that set in the script, however it keeps rescaling
to -20ºC to +20ºC for no apparent reason.

I can cope with the wind speed gauge rescaling, but even there I would like
it to remain 0 - 60mph and only rescale when it goes over 60mph. Pressure,
UV and solar radiation seem to stay at the values I have set.

Is there any way to prevent the rescaling? I understand this really isn't a
Weewx or RTGD issue but there's maybe a hack out there that I haven't found.

Thanks,

Rory

You can see the page I use for the iPad here: ttps://
www.360shetland.co.uk/weather/ss

--
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/bfd4960d-68eb-45a0-a5f2-7182b9bbd327n%40googlegroups.com.

[weewx-user] Rescaling of SteelSeries Gauges

2024-02-01 Thread 'Rory Gillies' via weewx-user

Is there any way to prevent the rescaling? I understand this really isn't a
Weewx or RTGD issue but there's maybe a hack out there that I haven't found.

Thanks,

Rory

You can see the page I use for the iPad here:
ttps://www.360shetland.co.uk/weather/ss

--
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/0bcb0244-c61a-4226-884b-02d5532b5387n%40googlegroups.com.

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

2024-02-01 Thread gjr80

You have almost certainly encountered the bug mentioned in this post 
. The 
bug does not bite (ie potentially delete system files) unless you uninstall 
the extension using weectl extension - so my strong advice to you is do not 
attempt to uninstall the extension. A manual uninstall (or install) will be 
fine. But I would further suggest waiting a few days for v5.0.1 which fixes 
this bug, its release should not be too far off.

Gary

On Thursday 1 February 2024 at 17:35:01 UTC+10 csm...@gmail.com wrote:

> @Tomasz, you stated above that ' I installed both interceptor and HP1000 
> drivers by weectl. " Can you provide some insight into how you did this? I 
> have a fresh install of 5.0.1 and when I run 'weectl extension install 
> weewx-interceptor.zip (fresh download) I get an error stack below. I am 
> posting here just in case I am missing something obvious, if not I will 
> start a new thread. 
>
> Thanks, 
> Chris 
>
> :~$ weectl extension install weewx-interceptor.zip
> Using configuration file /etc/weewx/weewx.conf
> Install extension 'weewx-interceptor.zip' (y/n)? y
> Extracting from zip archive weewx-interceptor.zip
>
> Traceback (most recent call last):
>   File "/usr/share/weewx/weectl.py", line 74, in 
> main()
>   File "/usr/share/weewx/weectl.py", line 66, in main
> namespace.func(namespace)
>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
> namespace.action_func(config_dict, namespace)
>   File "/usr/share/weewx/weectllib/extension_cmd.py", line 116, in 
> install_extension
> ext.install_extension(namespace.source, no_confirm=namespace.yes)
>   File "/usr/share/weewx/weecfg/extension.py", line 138, in 
> install_extension
> extension_name = self._install_from_file(extension_path, filetype)
>   File "/usr/share/weewx/weecfg/extension.py", line 168, in 
> _install_from_file
> extension_name = self.install_from_dir(extension_dir)
>   File "/usr/share/weewx/weecfg/extension.py", line 185, in 
> install_from_dir
> self._install_files(installer['files'], extension_dir)
>   File "/usr/share/weewx/weecfg/extension.py", line 269, in _install_files
> shutil.copy(source_path, destination_path)
>   File "/usr/lib/python3.8/shutil.py", line 418, in copy
> copyfile(src, dst, follow_symlinks=follow_symlinks)
>   File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
> with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/bin/user/interceptor.py'
>
> On Thursday, January 25, 2024 at 1:27:34 AM UTC-7 Tomasz Lewicki wrote:
>
>> Mystery solved. 
>>
>> But answering to vince question, my system is rather typical - Raspbian 
>> on Raspberry Pi, only WLAN interface is active. Weewx was unwillingly 
>> updated from 4.10.2 to 5.0.0. I checked all point of failure: Python 
>> version, permissions (thank you Gary!), network traffic. As I wrote before, 
>> rtupdate.wunderground.com was hijacked - local DNS redirected it to 
>> Weewx. So I deleted this bypass, allowing console to send data to real WU 
>> server. But still I couldn't see any traffic on my router. Total silence. 
>> It was abnormal (and it explains why PCAP file captured by Tshark was empty 
>> on port 80). But I didn't check WU settings in WiFi console. Station ID was 
>> empty, password was obfuscated by asterisks. I don't use WU website at all, 
>> I just needed credentials for conversation between console and Weewx. I 
>> entered ID and password - and then console started send data to real WU. So 
>> I redirected  network traffic on my DNS again, and Weewx started to receive 
>> data from WiFi console via interceptor driver :)
>>
>> Thank you to everyone who patiently read my writings and tried to help.
>>
>> środa, 24 stycznia 2024 o 22:54:46 UTC+1 vince napisał(a):
>>
>>> Difficult to answer with no info from you on exactly 'what' command you 
>>> ran for wireshark and whether your listening computer is wifi, ethernet, or 
>>> both.  What kind of computer are you running on ?  What os ?  What version 
>>> ?  Which interfaces ?  What was your 'exact' wireshark command ?
>>>
>>> But I see nothing basically in that 6-second pcap.  If running a sniffer 
>>> on your computer sees no traffic being redirected from the station, then 
>>> there is nothing for interceptor to intercept on the weewx computer.
>>>
>>> Again, when you say "*But I hijacked DNS on my router*" that (to me) 
>>> does not cause any traffic from your station to wunderground to be 
>>> redirected to your weewx system unless I'm not understanding what you're 
>>> saying.  Perhaps you should tell everybody what your system config is so 
>>> those who do interceptor can try to help more. 
>>>
>>> On Wednesday, January 24, 2024 at 1:38:25 PM UTC-8 Tomasz Lewicki wrote:
>>>
 I attach PCAP file with packets captured for 120 seconds. TCP/80 only. 
 Weewx was shut down. No traffic on

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

2024-02-01 Thread 'Tomasz Lewicki' via weewx-user

That's strange message. When you manualy decompress ZIP (I suppose 
downloaded from GitHub) and look into install.py, last line says:

*files=[('bin/user', ['bin/user/interceptor.py'])]*

I don't know why in your case there is / (slash) in error message:

*FileNotFoundError: [Errno 2] No such file or directory: 
'/bin/user/interceptor.py'*

But I think you can manually copy just one file - *interceptor.py*  - to 
*/etc/weewx/bin/user* directory and make changes in *weewx.conf,* then 
restart weewx, it should work. There are additiional files in *util* 
directory but install.py omits them so they are not necessary. 
czwartek, 1 lutego 2024 o 08:35:01 UTC+1 Chris McLeod napisał(a):

> @Tomasz, you stated above that ' I installed both interceptor and HP1000 
> drivers by weectl. " Can you provide some insight into how you did this? I 
> have a fresh install of 5.0.1 and when I run 'weectl extension install 
> weewx-interceptor.zip (fresh download) I get an error stack below. I am 
> posting here just in case I am missing something obvious, if not I will 
> start a new thread. 
>
> Thanks, 
> Chris 
>
> :~$ weectl extension install weewx-interceptor.zip
> Using configuration file /etc/weewx/weewx.conf
> Install extension 'weewx-interceptor.zip' (y/n)? y
> Extracting from zip archive weewx-interceptor.zip
>
> Traceback (most recent call last):
>   File "/usr/share/weewx/weectl.py", line 74, in 
> main()
>   File "/usr/share/weewx/weectl.py", line 66, in main
> namespace.func(namespace)
>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
> namespace.action_func(config_dict, namespace)
>   File "/usr/share/weewx/weectllib/extension_cmd.py", line 116, in 
> install_extension
> ext.install_extension(namespace.source, no_confirm=namespace.yes)
>   File "/usr/share/weewx/weecfg/extension.py", line 138, in 
> install_extension
> extension_name = self._install_from_file(extension_path, filetype)
>   File "/usr/share/weewx/weecfg/extension.py", line 168, in 
> _install_from_file
> extension_name = self.install_from_dir(extension_dir)
>   File "/usr/share/weewx/weecfg/extension.py", line 185, in 
> install_from_dir
> self._install_files(installer['files'], extension_dir)
>   File "/usr/share/weewx/weecfg/extension.py", line 269, in _install_files
> shutil.copy(source_path, destination_path)
>   File "/usr/lib/python3.8/shutil.py", line 418, in copy
> copyfile(src, dst, follow_symlinks=follow_symlinks)
>   File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
> with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/bin/user/interceptor.py'
>
> On Thursday, January 25, 2024 at 1:27:34 AM UTC-7 Tomasz Lewicki wrote:
>
>> Mystery solved. 
>>
>> But answering to vince question, my system is rather typical - Raspbian 
>> on Raspberry Pi, only WLAN interface is active. Weewx was unwillingly 
>> updated from 4.10.2 to 5.0.0. I checked all point of failure: Python 
>> version, permissions (thank you Gary!), network traffic. As I wrote before, 
>> rtupdate.wunderground.com was hijacked - local DNS redirected it to 
>> Weewx. So I deleted this bypass, allowing console to send data to real WU 
>> server. But still I couldn't see any traffic on my router. Total silence. 
>> It was abnormal (and it explains why PCAP file captured by Tshark was empty 
>> on port 80). But I didn't check WU settings in WiFi console. Station ID was 
>> empty, password was obfuscated by asterisks. I don't use WU website at all, 
>> I just needed credentials for conversation between console and Weewx. I 
>> entered ID and password - and then console started send data to real WU. So 
>> I redirected  network traffic on my DNS again, and Weewx started to receive 
>> data from WiFi console via interceptor driver :)
>>
>> Thank you to everyone who patiently read my writings and tried to help.
>>
>> środa, 24 stycznia 2024 o 22:54:46 UTC+1 vince napisał(a):
>>
>>> Difficult to answer with no info from you on exactly 'what' command you 
>>> ran for wireshark and whether your listening computer is wifi, ethernet, or 
>>> both.  What kind of computer are you running on ?  What os ?  What version 
>>> ?  Which interfaces ?  What was your 'exact' wireshark command ?
>>>
>>> But I see nothing basically in that 6-second pcap.  If running a sniffer 
>>> on your computer sees no traffic being redirected from the station, then 
>>> there is nothing for interceptor to intercept on the weewx computer.
>>>
>>> Again, when you say "*But I hijacked DNS on my router*" that (to me) 
>>> does not cause any traffic from your station to wunderground to be 
>>> redirected to your weewx system unless I'm not understanding what you're 
>>> saying.  Perhaps you should tell everybody what your system config is so 
>>> those who do interceptor can try to help more. 
>>>
>>> On Wednesday, January 24, 2024 at 1:38:25 PM UTC-8 Tomasz Lewicki wrote:
>>>
 I

Re: [weewx-user] RS485 Pyranometer and Weewx

[weewx-user] Re: weewx.service fails at reboot

[weewx-user] Re: Zambretti forecast in StellSeries

Re: [weewx-user] Re: Trouble installing WeeWX-MQTTSubscribe

[weewx-user] Re: weewx.service fails at reboot

[weewx-user] weewx.service fails at reboot

[weewx-user] Re: v5 git 'install' and logging

[weewx-user] v5 git 'install' and logging

Re: [weewx-user] Timeout errors with WMR88

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

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

[weewx-user] Timeout errors with WMR88

[weewx-user] Re: Rescaling of SteelSeries Gauges

[weewx-user] Re: Rescaling of SteelSeries Gauges

[weewx-user] Rescaling of SteelSeries Gauges

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

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

17 matches

Site Navigation

Mail list logo

Footer information