[weewx-user] Re: READ THIS!

[Owen]

As always.another good reminder to NOT run things as 'root', if you 
don't have to.

On Saturday 27 January 2024 at 5:26:01 pm UTC+11 gjr80 wrote:

> The problem is encountered when using the extension installer/uninstaller 
> weectl 
> extension. If you install WeeWX v5 via a package install and then use weectl 
> extension install to install an extension, some or all of the extension 
> files may be installed in an incorrect location. At this stage nothing 
> destructive has occurred to your system other than the extension files 
> perhaps being in the wrong location (and almost certainly the extension 
> itself will not work with WeeWX - though WeeWX functions normally). If you 
> then happen to uninstall the extension (perhaps because it seemingly does 
> not work) with weectl extension uninstall that is when the uninstaller 
> might delete system files.
>
> So in these circumstances we recommend against installing or uninstalling 
> extensions with weectl extension. Manual installs/uninstalls of 
> extensions will be fine, it is just weectl extension that experiences 
> problems. Also, if you have upgraded from an earlier WeeWX package install 
> and the extension concerned was already installed (ie it was not installed 
> using weectl extension) then you will be fine.
>
> This issue will be fixed in v5.0.1 which should be released real soon.
>
> Gary 
>
> On Saturday 27 January 2024 at 16:09:06 UTC+10 abcor...@gmail.com wrote:
>
>> I'm using weewx 5.0.0-1 (which I upgraded through Debian apt) and the 
>> GW1000 driver. Does that mean I should not install the driver via 
>> wee_extension until a new version comes out?
>>
>> Thanks...
>>
>> Andrew 
>> On Wednesday, January 17, 2024 at 11:30:24 AM UTC-7 Tom Keffer wrote:
>>
>>> We have discovered a potentially serious bug. The specific situation is 
>>> as follows:
>>>
>>>- A V4.x configuration file;
>>>- Package installer;
>>>- Install an extension;
>>>- Uninstall the extension.
>>>
>>> Under these circumstances, the extension uninstaller could remove system 
>>> files!
>>>
>>> If you are using a V4.x configuration file, please do not install any 
>>> extensions until we get a fix out.
>>>
>>> Apologies.
>>>
>>> -tk
>>>
>>

-- 
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/d21285cb-9342-44f5-af13-99b8d145e887n%40googlegroups.com.

[weewx-user] Re: python interceptor module not working after v5 upgrade

[Owen]

Apologies - if not already obvious I upgraded using the pip method, 
replacing the old 'setup.py'.

-- 
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/111de134-9779-4b7f-ac0d-de475506b59en%40googlegroups.com.

[weewx-user] python interceptor module not working after v5 upgrade

[Owen]

Just upgraded to v5 and everything works as it should except my interceptor 
module.

Long story shortmy barometer module is broken and returns ridiculous 
values that bork the normal weewx calculations, so I've been using an 
interceptor to check the database entry after every new archive record is 
written, and run a shell script that changes these crazy values to one that 
I suck down off the internet.
This has been working for a long time now.

"*weewx.conf*" relevant entry/lines:
[Engine]
[[Services]]
report_services = *user.barometerfudge.MungeBarometer*, 
weewx.engine.StdPrint, weewx.engine.StdReport, user.lowBattery.BatteryAlarm

Module name in ~/bin/user :
-rw-r--r-- 1 weewx weewx   1172 Jan 25 21:20 barometerfudge.py

Contents:
import subprocess
import weewx
from weewx.engine import StdService

class MungeBarometer(StdService):

def __init__(self, engine, config_dict):
super(MungeBarometer, self).__init__(engine, config_dict)
self.bind(weewx.NEW_ARCHIVE_RECORD, self.new_archive_record)

def new_archive_record(self, event):
subprocess.call(["/home/weewx/check_fix_pressure.sh"])

I have also tried using 'subprocess.run', but same result.

There are a couple of other python modules in ~/bin/user and they are being 
run fine, so there's not a permission issue.  Nothing else has changed.

No errors appear in the log even when debug=1, there is simply no output 
from that script at all meaning that it's not being run.  I updated it to 
create a 'logger' entry when it starts, and it works if I run it manually 
so I know that it's not being called by weewx.

The compiled python *is* being generated/updated in __pycache__ when weewx 
is restarted.

Does using a "virtual python environment' prevent the execution of shell 
scripts in discreet directories further up the directory structure?  I 
would have thought I'd see an error in the log if that were the case.

Any other clues/ideas appreciated.

Cheers...Owen

-- 
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/9beaeee5-787f-4d7d-81a7-7d0d4f964fefn%40googlegroups.com.

Re: [weewx-user] Re: Solid non-Raspbian platform for WeeWx + MariaDB?

[Owen]

I used to run Raspian on a Pi4, but my InfluxDB regularly crashed and 
sometimes even failed to restart cleanly at all due to corruption.
All sorts of random issues, including out of memory (when it wasn't).  No 
tuning of config file settings would fix it.  Drove me mental for months.  
I believe it to now be a limitation of the 32-bit OS.

Anyhooswitched to Ubuntu 20.04.4 LTS (64bit) and it's been flawless 
since.

I've basically ditched Raspian completely on all my Pi's - the Ubuntu 
release is extremely stable and robust.

On Saturday, 13 August 2022 at 2:32:24 pm UTC+10 vince wrote:

> I would be interested in hearing which version of ubuntu you went with, 
> considering the new 22.04.1 LTS just came out today, and whether you have 
> passwordless ssh working from all the client boxes you want to ssh from.
>
> Reason I'm asking is that when I upgraded my AWS Lightsail to 22.04.1 LTS 
> from 20.04 LTS today it broke passwordless ssh from the ancient long out of 
> patchability debian-7 ARM box that I run weewx on.   Symptoms are that ssh 
> with keys that 'used' to work does not work any more from the old debian 
> box, but it works fine from my mac mini.  I don't want to confuse this 
> thread with the gory details and the workaround I found unless others run 
> into similar misadventures.
>
> (my guess is that anything running current os will be fine, but I did want 
> to mention there 'are' changes in newest ubuntu that deprecate old setups 
> from working without workarounds).
>
> On Friday, August 12, 2022 at 4:31:59 PM UTC-7 saro...@optema.com wrote:
>
>> Thanks to all of you for the help.  Thanks to Vince idea, I now happily 
>> am running Ubuntu Desktop on my Pi 4, which so far is a lot more polished 
>> than Raspbian OS (which is toylike by comparison).  I have MariaDB 
>> successfully installed as well, which was a seamless process on Ubuntu -- 
>> this what I'm used to.
>>
>> Next step is to get passwordless SSH running at least in test mode from 
>> the Pi, as my understanding is that it is required for rsync.  When I can 
>> prove that out the path should be clear for rsync approach to pushing 
>> weather data to my cloud host.  I doubt that there will be any issues with 
>> WeeWx install on Ubuntu + Pi but we'll see!!!  This has been a rocky road.
>>
>> Doug I haven't had trouble with Win10 passwordless access to my Digital 
>> Ocean Ubuntu 20.04 webserver, just got stuck with Raspbian OS as the SSH 
>> client.  But your checklist looks useful and I am a novice at RSA key pair 
>> authentication so it will likely come in handy.  And I will take a look at 
>> Vince's recommendation for cygwin although the only problem I've had with 
>> Putty was puttygen key compatibility on Raspbian. 
>>
>> I will report back when I get through it all...
>>
>> On Friday, August 12, 2022 at 2:08:15 PM UTC-7 tke...@gmail.com wrote:
>>
>>> I have had this issue with newer versions of MariaDB as well. The 
>>> solution was to run as root. See this thread 
>>> 
>>>  
>>> on SO.
>>>
>>> Or, maybe you already knew that.
>>>
>>> On Fri, Aug 12, 2022 at 9:13 AM Stephen Rogers  
>>> wrote:
>>>
 Thanks Vince.  I didn't include error messages because my question was 
 (and is) whether there are other options for a small CPU I can use to 
 replace the Pi/Raspbian.  I appreciate your letting me know that you have 
 confirmed Ubuntu can work on the Pi 4, I may try that.

 I see the differences between Ubuntu (which I am getting pretty 
 familiar with) and Raspbian (which has some annoying differences in how 
 users are implemented for example, plus the various issues below) as 
 distracting from my main goals with WeeWx.  

 With regard to the SSH passwordless login issue, I have been running 
 into "Putty key format is too new" when using the keys created by Puttygen 
 in Putty to log into a remote server.  So this indicates to me that 
 Puttygen is downrev on the Pi/RaspbiOS.  I'm sure there is a way to make 
 this work but I haven't found it.  There are multiple options for 
 generating keys.  The ones I've tried don't work on Raspbian thus far.  I 
 have updated all the packages and gone through multiple reinstalls to make 
 sure I wasn't tripping on some small detail.

 I don't see how firewalls or sudo play into these problems.

 I'm hearing you that you haven't had these problems with Pi.  You are 
 clearly much more of an expert and are working from solid install/config 
 procedures that I don't have, since the (multiple) ones I've tried are not 
 getting me through to the result.

 As for MariaDB, I have used it for years and the problems I'm running 
 into with RaspiOS are ones I haven't seen on Ubuntu.  Where I am stuck on 
 that now is when running mysql_secure_installation

[weewx-user] Re: WeeWX on Debian 11 Bullseye

[Owen]

On Friday, 8 October 2021 at 12:02:55 am UTC+11 gldic...@gmail.com wrote:

> Has anyone encountered any problems upgrading and running 
> WeeWX/Belchertown/MQTT on Debian 11 Bullseye? 
>

Whoops - think I hit the wrong button on my previous reply!

As I said - any hurry to upgrade?  Bullseye was only officially released ~1 
month ago, and Buster is supported until mid-2024.
I'd wait for early kinks in Bullseye to be ironed out, but that's just me...

O

-- 
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/2a0527a5-6ac0-4a60-910f-9b0460e65d55n%40googlegroups.com.

[weewx-user] Re: Database and web pages no longer updating

[Owen]

On Tuesday, 28 September 2021 at 12:56:39 pm UTC+10 gjr80 wrote:

> My apologies but I missed your reply. For what it’s worth now you have all 
> the classic symptoms of corrupted memory in your logger. See the wiki 
> article WeeWX generates HTML pages, but it does not update them 
> 
> .
>
>
Must be the season for itmy VP2 just started playing up in exactly the 
same way.
Put weewx into debug mode - if it's like mine you'll see messages such as:

  weewx.drivers.vantage: LOOP try #1; error: Expected to read 99 chars; 
got 0 instead

Dumping/clearing the VP2 memory resolved the issue.

O.

-- 
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/f42d56e5-63d5-4b8e-988a-15b691009630n%40googlegroups.com.

[weewx-user] Re: Belchertown Skin Beaufort Category Missing

[Owen Edwards]

Umm...I'm not running master, but could it be that you've just got a typo 
in your config file?

beaufort_categoty   <=-- This?

Cheers.

On Thursday, 22 April 2021 at 3:38:43 am UTC+10 Alan Bryant wrote:

> I forgot to mention that I am running the master branch of Belchertown 
> from today (04/21/2021) & weewx 4.5.1 installed via apt on Ubuntu 20.10.
>
> On Wednesday, April 21, 2021 at 12:30:27 PM UTC-5 Alan Bryant wrote:
>
>>
>> I just did a fresh installation of the Belchertown skin, which I love, 
>> thank you Pat, and everything is working so far except for the 
>> beaufort_category.
>>
>> I had this working earlier today, but I was having other intermittent 
>> issues, so I did a fresh installation. This time, the intermittent issues 
>> are gone, but the beaufort category is not displaying.
>>
>> I have enabled debug in the Belchertown skin, but I am not seeing 
>> anything obvious. Any help would be greatly appreciated!
>>
>> My website is https://weather.bryantgeeks.com/.
>>
>> Here is the Belchertown config from weewx.conf:
>>
>> [[Belchertown]]
>> skin = Belchertown
>> HTML_ROOT = /var/www/html/weewx
>> enable = true
>> [[[Labels]]]
>>
>> Generic
>>
>> #--- Common Titles under Labels Section to Change ---
>> home_page_header = "Pocket Farm Road Weather Conditions"
>> # graphs_page_header = "Weather Observation Graphs"
>> # reports_page_header = "Weather Observation Reports"
>> # records_page_header = "Weather Observation Records"
>> # about_page_header = "About This Site"
>> powered_by = 'Observations are powered by an > href="/about" target="_blank">Ecowitt Personal Weather Station'
>> footer_copyright_text = "Pocket Farm Road Weather"
>> # footer_disclaimer_text = "Never make important 
>> decisions based on info from this website."
>>
>> [[[Extras]]]
>>
>> # For help refer to the docs at 
>> https://github.com/poblabs/weewx-belchertown
>>
>> #--- General Options ---
>> belchertown_debug = 1
>> belchertown_locale = "auto"
>> theme = auto
>> theme_toggle_enabled = 1
>> logo_image = "
>> https://weather.bryantgeeks.com/images/baysidelogo.png";
>> # logo_image_dark = ""
>> site_title = "Pocket Farm Road Weather"
>> station_observations = 
>> "barometer","dewpoint","outHumidity","rainWithRainRate","cloudbase","visibility","windrun"
>> beaufort_categoty = 1
>> manifest_name = "Pocket Farm Road Weather"
>> manifest_short_name = "PFRW"
>> # aeris_map = 0
>> radar_html = 'https://embed.windy.com/embed2.html?lat=28.04291&lon=-97.226451&detailLat=28.04291&detailLon=-97.226451&width=650&height=360&zoom=11&level=surface&overlay=radar&product=radar&menu=&message=true&marker=&calendar=now&pressure=&type=map&location=coordinates&detail=&metricWind=mph&metricTemp=%C2%B0F&radarRange=-1";
>>  
>> frameborder="0">'   #  (default seems to center on your lat/lon)
>> # radar_html_dark = None
>> # radar_zoom = 8
>> radar_marker = 1
>> # almanac_extras = 1
>> # highcharts_enabled = 1
>> # graph_page_show_all_button = 1
>> # graph_page_default_graphgroup = "day"
>> # highcharts_homepage_graphgroup = "day"
>> # highcharts_decimal = "auto"
>> # highcharts_thousands = "auto"
>> # googleAnalyticsId = ""
>> # pi_kiosk_bold = "false"
>> # pi_theme = "auto"
>> # webpage_autorefresh = 0
>> reload_hook_images = 1
>> # reload_images_radar = 300
>> # reload_images_hook_asi = -1
>> # reload_images_hook_af = -1
>> # reload_images_hook_as = -1
>> # reload_images_hook_ac = -1
>> # show_last_updated_alert = 0
>> # last_updated_alert_threshold = 1800
>>
>> #--- MQTT Websockets (for Real Time Streaming) Options ---
>> mqtt_websockets_enabled = 1
>> mqtt_websockets_host = "weather.bryantgeeks.com"
>> mqtt_websockets_port = 9001
>> mqtt_websockets_ssl = 1
>> mqtt_websockets_topic = "weather/loop"
>> # disconnect_live_website_visitor = 180
>>
>> #--- Forecast Options ---
>> forecast_enabled = 1
>> # forecast_provider = "aeris"
>> forecast_api_id = ""
>> forecast_api_secret = 
>> "x"
>> # forecast_units = "us"
>> # forecast_lang = "en"
>> # forecast_stale = 3540
>> # forecast_aeris_use_metar = 1
>> # forecast_interval_hours = 24