Re: [weewx-user] How to set WeeWx to restart after local network returns from being offline

[vince]

You need to replace the weewxd.py file with the newer one for the 
loop_on_init switch to work.  There's a bug in the previous versions.

On Sunday, May 19, 2024 at 5:33:50 AM UTC-7 Ben W. wrote:

> Thanks! I have  loop_on_init = 1 right now per the documentation. I will 
> change it to "True" to give that a shot. I"m a bit lost with the rest of 
> your response, but I'll look into that more. Thank you!
>
> On Saturday, May 18, 2024 at 4:32:36 PM UTC-5 vince wrote:
>
>> At the top of weewx.conf add "loop_on_init = True" to have it try 
>> basically continually.   Until 5.1 comes out you'll need to grab an updated 
>> weewxd.py and overwrite your existing 5.x copy of that file so the option 
>> works.   The latest version is at 
>> https://raw.githubusercontent.com/weewx/weewx/master/src/weewxd.py if 
>> you want to grab it sooner rather than later.
>>
>> Worked for me here vs. the ecowitt driver under similar circumstances 
>> when I needed to take my network offline for a bit to update firmware on 
>> the network gear
>>
>> On Saturday, May 18, 2024 at 12:56:58 PM UTC-7 p q wrote:
>>
>>> Here's a dumb suggestion. I'm sure there will be smarter answers. 
>>> Restart weewx every day at 2am with a cron job whether it needs it or not.
>>>
>>> On Sat, May 18, 2024 at 12:45 PM Ben W.  wrote:
>>>
>>>> Hello!
>>>>
>>>> Every so often, my home network (through eero) will upgrade causing 
>>>> devices to go offline/lose connection for a few minutes.
>>>>
>>>> The last two times my eero/network was updated in the early morning, 
>>>> WeeWx stopped when the connection was lost (expected). I cannot find how 
>>>> to 
>>>> set WeeWx to restart once the network is available again.
>>>>
>>>> The log from the most recent upgrade around 02:41 on the 15th:
>>>>
>>>>
>>>>
>>>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.restx: PWSWeather: 
>>>> Published record 2024-05-15 02:40:00 CDT (1715758800)
>>>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
>>>> Generated 8 files for report SeasonsReport in 0.38 seconds
>>>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.imagegenerator: 
>>>> Generated 17 images for report SeasonsReport in 0.21 seconds
>>>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0 
>>>> files to /var/www/html/weewx
>>>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
>>>> Generated 6 files for report SmartphoneReport in 0.02 seconds
>>>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.imagegenerator: 
>>>> Generated 6 images for report SmartphoneReport in 0.05 seconds
>>>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0 
>>>> files to /var/www/html/weewx/smartphone
>>>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
>>>> Generated 1 files for report MobileReport in 0.01 seconds
>>>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.imagegenerator: 
>>>> Generated 4 images for report MobileReport in 0.03 seconds
>>>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0 
>>>> files to /var/www/html/weewx/mobile
>>>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
>>>> Generated 13 files for report StandardReport in 0.22 seconds
>>>> May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.imagegenerator: 
>>>> Generated 12 images for report StandardReport in 0.11 seconds
>>>> May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0 
>>>> files to /var/www/html/weewx
>>>> May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
>>>> Generated 12 files for report Belchertown in 0.38 seconds
>>>> May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 3 
>>>> files to /var/www/html/weewx/belchertown
>>>> May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Failed to 
>>>> obtain response to command 'CMD_GW1000_LIVEDATA' after 3 attempts
>>>> May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to 
>>>> obtain live sensor data
>>>> May 15 02:41:06 rpi5  weewxd[101529]: INFO weewx.engine: Main loop 
>>>> exiting. Shutting engine down.
>>>> May 15 02:41:06 rpi5  weewxd[101529]: INFO weewx.engine: Shutting down 
>>>> StdReport thread
>&g

Re: [weewx-user] How to set WeeWx to restart after local network returns from being offline

[vince]

At the top of weewx.conf add "loop_on_init = True" to have it try basically 
continually.   Until 5.1 comes out you'll need to grab an updated weewxd.py 
and overwrite your existing 5.x copy of that file so the option works.   
The latest version is at 
https://raw.githubusercontent.com/weewx/weewx/master/src/weewxd.py if you 
want to grab it sooner rather than later.

Worked for me here vs. the ecowitt driver under similar circumstances when 
I needed to take my network offline for a bit to update firmware on the 
network gear

On Saturday, May 18, 2024 at 12:56:58 PM UTC-7 p q wrote:

> Here's a dumb suggestion. I'm sure there will be smarter answers. Restart 
> weewx every day at 2am with a cron job whether it needs it or not.
>
> On Sat, May 18, 2024 at 12:45 PM Ben W.  wrote:
>
>> Hello!
>>
>> Every so often, my home network (through eero) will upgrade causing 
>> devices to go offline/lose connection for a few minutes.
>>
>> The last two times my eero/network was updated in the early morning, 
>> WeeWx stopped when the connection was lost (expected). I cannot find how to 
>> set WeeWx to restart once the network is available again.
>>
>> The log from the most recent upgrade around 02:41 on the 15th:
>>
>>
>>
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.restx: PWSWeather: 
>> Published record 2024-05-15 02:40:00 CDT (1715758800)
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
>> Generated 8 files for report SeasonsReport in 0.38 seconds
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.imagegenerator: 
>> Generated 17 images for report SeasonsReport in 0.21 seconds
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
>> Generated 6 files for report SmartphoneReport in 0.02 seconds
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.imagegenerator: 
>> Generated 6 images for report SmartphoneReport in 0.05 seconds
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx/smartphone
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
>> Generated 1 files for report MobileReport in 0.01 seconds
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.imagegenerator: 
>> Generated 4 images for report MobileReport in 0.03 seconds
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx/mobile
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
>> Generated 13 files for report StandardReport in 0.22 seconds
>> May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.imagegenerator: 
>> Generated 12 images for report StandardReport in 0.11 seconds
>> May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx
>> May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
>> Generated 12 files for report Belchertown in 0.38 seconds
>> May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 3 
>> files to /var/www/html/weewx/belchertown
>> May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Failed to obtain 
>> response to command 'CMD_GW1000_LIVEDATA' after 3 attempts
>> May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to obtain 
>> live sensor data
>> May 15 02:41:06 rpi5  weewxd[101529]: INFO weewx.engine: Main loop 
>> exiting. Shutting engine down.
>> May 15 02:41:06 rpi5  weewxd[101529]: INFO weewx.engine: Shutting down 
>> StdReport thread
>> May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Failed to obtain 
>> response to command 'CMD_GW1000_LIVEDATA' after 3 attempts
>> May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to obtain 
>> live sensor data
>> May 15 02:41:07 rpi5  weewxd[101529]: INFO user.gw1000: GatewayCollector 
>> thread has been terminated
>> May 15 02:41:17 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to shut 
>> down GatewayCollector thread
>> May 15 02:41:17 rpi5  weewxd[101529]: CRITICAL __main__: Caught 
>> WeeWxIOError: Failed to obtain response to command 'CMD_GW1000_LIVEDATA' 
>> after 3 attempts
>> May 15 02:41:17 rpi5  weewxd[101529]: CRITICAL __main__:  
>>  Waiting 60.0 seconds then retrying...
>> May 15 02:41:27 rpi5  weewxd[101529]: ERROR user.gw1000: Failed to obtain 
>> response to command 'CMD_GW1000_LIVEDATA' after 3 attempts
>> May 15 02:41:27 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to obtain 
>> live sensor data
>> May 15 02:42:17 rpi5  weewxd[101529]: INFO __main__: retrying...
>> May 15 02:42:17 rpi5  weewxd[101529]: INFO weewx.engine: Loading station 
>> type GW1000 (user.gw1000)
>> May 15 02:42:17 rpi5  weewxd[101529]: INFO user.gw1000: GatewayDriver: 
>> version is 0.6.1
>> May 15 02:42:17 rpi5  weewxd[101529]: INFO user.gw1000:  device 
>> address is 192.168.7.206:45000
>> May 15 02:42:17 rpi5  weewxd[101529]: INFO user.gw1000:  poll 
>> 

[weewx-user] Re: Can This Error Message Be fixed ?

[vince]

for (2) you have to install a webserver of your choice

for (1) if you do a google search of 'weewx.drivers.fousb:unrecognised 
magic number' you will find some hits suggesting you need to power cycle 
your weather station's console as one possible fix.

On Friday, May 17, 2024 at 11:38:14 PM UTC-7 Ee Bee51 wrote:

> Hi All
> A Newbie here.
> I have a weather station that lsusb indentifies as a "Dream Link WH1080".
> I have 2 compatible display units for it. One works quite happily with 
> weewx and the station is online with it both locally and through 
> wunderground.com
> The second one however crashes, despite seemingly being identical both in 
> appearance and according to lsusb. When using it however, "status weewx" 
> gives the error message...
> "weewx.drivers.fousb:unrecognised magic number fcb4"
> I'm using the FineOffsetUSB (option 2) driver...
> This isn't really an issue because the station is on air, but I'm curious 
> as to why one unit works and the other doesn't..
> Question 2
> How do I get weewx to display in a skin for a local display ?
> In the .conf file "Seasons" is marked as true, the program is running as 
> desired, but the only way I can get as local display is to look directly at 
> the index.html file. As yet, I've not been able to find anything on the web 
> site (and believe me I've looked).
>

-- 
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/26ffd531-5384-405d-bc5f-455f476159fbn%40googlegroups.com.

Re: [weewx-user] Error Reading GW1100

[vince]

Verify the ip address on your 'new' gateway is what is in weewx.conf

On Saturday, May 11, 2024 at 5:20:22 AM UTC-7 Ian Millard wrote:

> Following on, hers is my open gw1000 stanza in whew.conf: -
>
> [GW1000]
> # This section is for the Ecowitt Gateway driver.
> 
> # How often to poll the API, default is every 20 seconds:
> poll_interval = 4
> 
> # The driver to use:
> driver = user.gw1000
> # gateway device IP address:
> ip_address = 192.168.1.89
> port = 45000
> 
> [[field_map_extensions]]
> batteryStatus1 = wh65_batt
> barometer = relbarometer
>
>
> On 11 May 2024, at 11:21, 'steepleian' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
> weewx.conf
>
>
>

-- 
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/fb5674c2-cc69-473b-bca6-ff011493886en%40googlegroups.com.

Re: [weewx-user] Upgraded to V5 - will not run automaticly

[vince]

yup - overloaded terminology.  Sounds a little like running a process under 
cgroups isolation 15+ years ago.  Looking that up briefly I see the term 
'process container' which I guess is the same thing.  Thanks.

On Thursday, May 9, 2024 at 6:21:16 AM UTC-7 Paul R Anderson wrote:

> Vince,
> Your confusion is probably caused by the enormous popularity of Docker. At 
> this point most of us hear the word Container and only think of Docker. 
> This is also a huge reason why LXC Containers are nowhere near as popular 
> as Docker containers , no one knows they exist, let alone what they are.  
> *LXC Containers are system containers*
> *Docker Containers are Application containers*
> There are generally at least two types of containers: Application 
> containers, and System containers
> There's a good blog post from Ubuntu that explains it much better than I 
> can.
> What are Linux containers? 
> <https://ubuntu.com/blog/what-are-linux-containers>
>
> Brief excerpt from the blog post:
>
> " Application vs system containers
> Application containers (such as Docker) are containers running a single 
> process per container. They run stateless types of workloads so that you 
> can ramp up and down as needed – create new containers and delete them at 
> any time. Usually, you don’t need to care about the lifecycle of those 
> containers, as they are meant to be ephemeral.
>
> The other type of containers, system containers, are much closer to a 
> virtual or a physical machine. They run a full operating system inside 
> them, and you manage them exactly as you would a virtual or a physical 
> machine. That means you can install packages inside them, you can manage 
> services, define backup policies, monitoring, and all other aspects as you 
> usually would with a virtual machine. These containers are usually very 
> long-lasting. If you need to update them, you can do so with the normal 
> tooling of the Linux distribution you are using. It also means that you 
> will get normal security updates from distributions for those containers, 
> so you wouldn’t need to wait for any image to be published to get the 
> security fixes. "
>
>
>
> Paul
>
> On Wed, May 8, 2024 at 8:10 PM vince  wrote:
>
>> I have to admit being a little confused.  A container running multiple 
>> processes that you can ssh into isn't a container, it's a virtual machine.
>>
>> On Wednesday, May 8, 2024 at 4:42:00 AM UTC-7 Graham Eddy wrote:
>>
>>> i suggest testing before publishing..
>>> that won’t work without the permissions towards end of my lxc/105.conf 
>>> file
>>> *⊣GE⊢*
>>>
>>> On 8 May 2024, at 9:25 PM, G7LTT  wrote:
>>>
>>> Updated to add USB device to the container.
>>>
>>>
>>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/dd2f4126-94ec-4456-b7c1-fc0fce4a6d3an%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/dd2f4126-94ec-4456-b7c1-fc0fce4a6d3an%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/a3740533-b43c-4a87-a879-b50fb2f70aaan%40googlegroups.com.

Re: [weewx-user] Upgraded to V5 - will not run automaticly

[vince]

I have to admit being a little confused.  A container running multiple 
processes that you can ssh into isn't a container, it's a virtual machine.

On Wednesday, May 8, 2024 at 4:42:00 AM UTC-7 Graham Eddy wrote:

> i suggest testing before publishing..
> that won’t work without the permissions towards end of my lxc/105.conf file
> *⊣GE⊢*
>
> On 8 May 2024, at 9:25 PM, G7LTT  wrote:
>
> Updated to add USB device to the container.
>
>
>

-- 
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/dd2f4126-94ec-4456-b7c1-fc0fce4a6d3an%40googlegroups.com.

[weewx-user] Re: removed bad rainrate data but this did not reflect in totals

[vince]

You might want to consult the wiki.  That's why hundreds of hours have been 
spent creating it.

https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data

On Tuesday, May 7, 2024 at 9:19:04 AM UTC-7 Kevin Crivelli wrote:

> or perhaps there is a way to rebuild the raintotals fields from the 
> current rainrate data
>
> On Tuesday, May 7, 2024 at 12:17:20 PM UTC-4 Kevin Crivelli wrote:
>
>> I removed bad rainrate data but it did not effect the raintotals field. I 
>> was able to determine the epoch date-time for the bad rainrate data. Having 
>> those I was going to delete the rain_total values for those entries but how 
>> would I have that then reflect in the following rain_total fields?
>>
>> chatgpt gave me this which I feel is a start but I'm not quite there yet. 
>> anyone able to help me with this?
>>
>> -- Store the rain total of the specific datetime in a variable
>> SET @deleted_rain_total = (SELECT rain_total FROM your_table WHERE 
>> datetime = specific_datetime);
>>
>> -- Delete the rain total at the specific datetime
>> DELETE FROM your_table WHERE datetime = specific_datetime;
>>
>> -- Decrease the rain totals for the following datetimes
>> UPDATE your_table
>> SET rain_total = rain_total - @deleted_rain_total
>> WHERE datetime > specific_datetime;
>>
>> These are the date and times of the entries that need their raintotal 
>> nulled and then the proceeding raintotals to reflect the change
>>
>> 1699559700: 2024-05-10 01:55:00
>> 169956: 2024-05-10 01:56:40
>> 1709221800: 2024-05-26 06:50:00
>> 1709222100: 2024-05-26 06:55:00
>> 1713436800: 2024-06-16 10:00:00
>> 1713437100: 2024-06-16 10:05:00
>> 1713780900: 2024-06-20 03:35:00
>> 1713781200: 2024-06-20 03:40:00
>> 1714771200: 2024-06-25 18:40:00
>> 1714771500: 2024-06-25 18:45:00
>> 1699559400: 2024-05-10 01:50:00
>> 1699560300: 2024-05-10 01:51:40
>> 1709221500: 2024-05-26 06:45:00
>> 1713437400: 2024-06-16 10:10:00
>> 1713781500: 2024-06-20 03:05:00
>> 1714771800: 2024-06-25 18:10:00
>>
>>

-- 
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/b687da34-99af-42a8-a84b-490f6c902d91n%40googlegroups.com.

[weewx-user] Re: Upgraded to V5 - will not run automaticly

[vince]

No, I was referring to LXC in proxmox. Lots of folks do vanilla docker. 
Glad you got it working.

A start to finish writeup for building a LXC setup would be a nice thing if 
you have time. If you do it, just assume proxmox is already installled and 
ready to use, Thanks!

On Monday, May 6, 2024 at 3:41:42 PM UTC-7 G7LTT wrote:

> And that's one of the issues. No logs are being written. /var/log/syslog 
> has nothing and neither does/var/log/weewx/weexd.log. The debug=1 setting 
> is set.
>
> This was working just fine under V4 so I can't believe its to do with 
> things like perms.
>
> "running a somewhat unusual setup"? I assume you have no other users 
> runing weewx in a container? Makes total sense to do it that way when you 
> think about it. Even on an RPi. Why waste a whole machine on such a trivial 
> task?
>
> I'll take another swing at it. see if I can't get some logging going.
>
> Mark
>
> On Sunday, May 5, 2024 at 4:53:16 PM UTC-4 vince wrote:
>
>> We can't read minds.   Need to see actual logs with debug=1 set in 
>> weewx.conf and ideally your weewx.conf file as well.
>>
>> The usual error tends to be permissions accessing the hardware or the 
>> network itself.   Considering you're running a somewhat unusual setup you 
>> might want to provide a way for folks to try to look at what you might be 
>> missing within your container image.
>>
>>
>> On Sunday, May 5, 2024 at 12:39:03 PM UTC-7 G7LTT wrote:
>>
>>> So I upgraded to V5.0.4 from 4.whatever and it looked like everything 
>>> went ok. But then about an hour later I noticed that the web pages were not 
>>> being updated.  Off to the logs I go - nothing in the logs.
>>>
>>> Hmmnnn. OK, time to run it manually at the command line to see if it 
>>> spews anything out. Nope, works perfectly. I can leave "weewxd" running for 
>>> hours without any error. And the pages get updated/uploaded etc etc etc. 
>>> What gives?
>>>
>>> I am running Weewx in an LXC container on Proxmox in my homelab system. 
>>> I have the Ambient WS2000 API installed (rather than talk to the station it 
>>> collects the station data from Ambient themselves). 
>>>
>>> V4 was running as expected in daemon mode. It would survive a 
>>> reboot/restart of the machine and the container. V5? Not so much. But there 
>>> are no entries in the log files for it which is making me suspicious.
>>>
>>> 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/432b364a-bd24-4b1b-aac4-ea459cbcd6f8n%40googlegroups.com.

[weewx-user] Re: Upgraded to V5 - will not run automaticly

[vince]

We can't read minds.   Need to see actual logs with debug=1 set in 
weewx.conf and ideally your weewx.conf file as well.

The usual error tends to be permissions accessing the hardware or the 
network itself.   Considering you're running a somewhat unusual setup you 
might want to provide a way for folks to try to look at what you might be 
missing within your container image.


On Sunday, May 5, 2024 at 12:39:03 PM UTC-7 G7LTT wrote:

> So I upgraded to V5.0.4 from 4.whatever and it looked like everything went 
> ok. But then about an hour later I noticed that the web pages were not 
> being updated.  Off to the logs I go - nothing in the logs.
>
> Hmmnnn. OK, time to run it manually at the command line to see if it spews 
> anything out. Nope, works perfectly. I can leave "weewxd" running for hours 
> without any error. And the pages get updated/uploaded etc etc etc. What 
> gives?
>
> I am running Weewx in an LXC container on Proxmox in my homelab system. I 
> have the Ambient WS2000 API installed (rather than talk to the station it 
> collects the station data from Ambient themselves). 
>
> V4 was running as expected in daemon mode. It would survive a 
> reboot/restart of the machine and the container. V5? Not so much. But there 
> are no entries in the log files for it which is making me suspicious.
>
> 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/c584a01e-f82d-42b4-b5b2-dc63244bb975n%40googlegroups.com.

[weewx-user] Re: Preparing for v4 to v5 upgrade - Linux User and file permissions

[vince]

I'm sorry - that link is https://github.com/weewx/weewx/wiki/v5-upgrade 
above.  Typo on my part.

On Friday, May 3, 2024 at 11:49:01 AM UTC-7 vince wrote:

> Having a test pi is a good thing.  Definitely use that to walk through the 
> steps and verify you know what'll happen.
>
> I followed the https://github.com/weewx/weewx/wiki/v5-upgrade steps and 
> found what seems to be one error in it.  I 'did' need to do "sudo chown 
> -R pi:pi /home/weewx" before doing the pip installation step.   Remember 
> - v5 pip runs as whatever user you run the pip command from.
>
> so:
> i) nope - just install it as 'pi' without sudo
> ii) yup - see above.  I'll open an issue on github about that seeming 
> omission in the instructions
> iii) nope - just do the steps as written (with that one addition) as user 
> 'pi'
>
> On Friday, May 3, 2024 at 8:40:22 AM UTC-7 mike.t...@noworries.plus.com 
> wrote:
>
>> Hi,
>> I'm a little embarrassed to ask these most basic of questions but at 
>> least I'll get started on the right track so here goes;
>>
>> I have been running Weewx on a RPI since 2104 using setup.py
>> It's currently v4.10.2, python 3 and on rpi4
>> I have made several changes to graphs, reports etc and have a few 
>> extensions installed.
>> Everything is under /home/weewx
>> I never created a weewx user I just sudo from the pi user
>> root owns all the files
>> I have no experience of running a virtual environment
>> Yes I have read the upgrade guide and the v5 wiki
>> I have searched the google group but my moist basic of questions don't 
>> look to be covered.
>> I did do a test upgrade of my backup rpi but although it runs at v5 the 
>> upgrade couldn't have been clean as  it wouldn't upgrade from v5.0 to 
>> v5.0.2 so I must have done something wrong in the initial upgrade.
>>
>> My queries are;
>> i) should I create a weewx linux user and login as that use to execute 
>> the upgrade
>> ii) if yes, do I need to change the file ownership on all the files to 
>> weewx user
>> iii)  if I don't need a weewx user do I just sudo from the pi user?
>>
>> Thanks in Advance
>> Mike
>>
>>

-- 
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/fc82d512-9f85-4daa-b6ce-14b3ace8fb6an%40googlegroups.com.

[weewx-user] Re: Preparing for v4 to v5 upgrade - Linux User and file permissions

[vince]

Having a test pi is a good thing.  Definitely use that to walk through the 
steps and verify you know what'll happen.

I followed the https://github.com/weewx/weewx/wiki/v5-upgrade steps and 
found what seems to be one error in it.  I 'did' need to do "sudo chown -R 
pi:pi /home/weewx" before doing the pip installation step.   Remember - v5 
pip runs as whatever user you run the pip command from.

so:
i) nope - just install it as 'pi' without sudo
ii) yup - see above.  I'll open an issue on github about that seeming 
omission in the instructions
iii) nope - just do the steps as written (with that one addition) as user 
'pi'

On Friday, May 3, 2024 at 8:40:22 AM UTC-7 mike.t...@noworries.plus.com 
wrote:

> Hi,
> I'm a little embarrassed to ask these most basic of questions but at least 
> I'll get started on the right track so here goes;
>
> I have been running Weewx on a RPI since 2104 using setup.py
> It's currently v4.10.2, python 3 and on rpi4
> I have made several changes to graphs, reports etc and have a few 
> extensions installed.
> Everything is under /home/weewx
> I never created a weewx user I just sudo from the pi user
> root owns all the files
> I have no experience of running a virtual environment
> Yes I have read the upgrade guide and the v5 wiki
> I have searched the google group but my moist basic of questions don't 
> look to be covered.
> I did do a test upgrade of my backup rpi but although it runs at v5 the 
> upgrade couldn't have been clean as  it wouldn't upgrade from v5.0 to 
> v5.0.2 so I must have done something wrong in the initial upgrade.
>
> My queries are;
> i) should I create a weewx linux user and login as that use to execute the 
> upgrade
> ii) if yes, do I need to change the file ownership on all the files to 
> weewx user
> iii)  if I don't need a weewx user do I just sudo from the pi user?
>
> Thanks in Advance
> Mike
>
>

-- 
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/c5068660-3f0a-4ad9-8287-d5052345fb11n%40googlegroups.com.

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

[vince]

Marco - Would you provide more information to help us understand your 
system ?  See the new Problem Reporting Questionnaire (link) 
<https://github.com/weewx/weewx/wiki/WeeWX-Problem-Reporting-Questionnaire> for 
the kind of information we need in order to try to help much better.  Thank 
you.

On Wednesday, May 1, 2024 at 12:45:42 AM UTC-7 Marco Citossi wrote:

> Hi vince! sestatus gives disabled...
>
> Il giorno mercoledì 1 maggio 2024 alle 01:57:29 UTC+2 vince ha scritto:
>
>> Marco are you running with selinux in enforcing mode ? Can you check for 
>> selinux errors in your logs or perhaps temporarily run with selinux 
>> disabled to see if that helps ? 
>>
>> Sorry but I’m away from a computer so I can’t give you the precise 
>> commands, but selinux can rather quietly stop things from working in some 
>> configurations. It would be helpful to eliminate that possibility.
>>
>> Other possibility is that your weewx user isn’t in a group with network 
>> access. What does ‘groups weewx’ return ?
>> On Tuesday, April 30, 2024 at 11:39:51 AM UTC-7 Tom Keffer wrote:
>>
>>> I am not that familiar with the IP logger, but I assume you would obey 
>>> the same echo TEST as a regular logger. If it doesn't, then it sounds like 
>>> there is a connectivity problem.
>>>
>>> Yes, it worked under WeeWX V3.8, but you have also changed servers since 
>>> then.
>>>
>>> Double check any firewalls. For example, do you use iptables? Does your 
>>> router prevent indiscriminate traffic between ports? 
>>>
>>>
>>>
>>> On Tue, Apr 30, 2024 at 10:45 AM Marco Citossi  
>>> wrote:
>>>
>>>> I've tried to change weewx.service but without results.
>>>> Telent doesn't echo anything.
>>>> The network should work because the old weewx (3.8.xxx) on the other 
>>>> webserver is working.
>>>>
>>>> Il giorno martedì 30 aprile 2024 alle 19:03:43 UTC+2 Tom Keffer ha 
>>>> scritto:
>>>>
>>>>> I am wondering whether the network is up and running by the time 
>>>>> weewxd tries to access it. Try editing your weewx systemd service file 
>>>>> (normally located in /lib/systemd/system/weewx.service) so it looks 
>>>>> something like the following:
>>>>>
>>>>> [Unit]
>>>>> Description=WeeWX
>>>>> Documentation=https://weewx.com/docs
>>>>> Requires=time-sync.target
>>>>> After=time-sync.target
>>>>> After=network-online.target
>>>>> Requires=network-online.target
>>>>>
>>>>> Then
>>>>>
>>>>> *sudo systemctl daemon-reload*
>>>>> *sudo systemctl restart weewx*
>>>>>
>>>>> If that doesn't work, we can try putting a sleep command in the 
>>>>> startup.
>>>>>
>>>>> Also, can you telnet to the logger and perform the logger TEST 
>>>>> function? The IP address of your logger got cut off in the log, but it 
>>>>> would look something like this (replace 140.105.xxx.yyy with the IP 
>>>>> address):
>>>>>
>>>>> telnet 140.105.xxx.yyy 2
>>>>> press  a few times.
>>>>> Then type "TEST", all caps. It will not echo.
>>>>> then 
>>>>> The logger should respond with "TEST".
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Apr 30, 2024 at 9:21 AM Marco Citossi  
>>>>> wrote:
>>>>>
>>>>>> Yes it's ethernet.
>>>>>>
>>>>>> Here it is the log:
>>>>>>
>>>>>>
>>>>>> apr 30 18:07:10 web4.xxx systemd[1]: Started WeeWX.
>>>>>>
>>>>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Initializing 
>>>>>> weewxd version 5.0.2
>>>>>>
>>>>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Command line: 
>>>>>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>>>>>>
>>>>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Using Python 
>>>>>> 3.6.8 (default, Jan 16 2024, 02:08:59) 
>>>>>>
>>>>>>  [GCC 8.5.0 20210514 
>>>>>> (Red Hat 8.5.0-20.0.1)]
>>>>>>
>>>>>&g

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

[vince]

It should certainly permit ports over 1024 but if selinux blocks stuff due 
to an executable not being labelled correctly you can get quiet failures 
unless you notice it in the logs. It’s not always self-evident when he 
victim program logs what it thinks happened. I just can’t remember the file 
it logs into (away from computer for a few days).

Quick test would to ‘temporarily’ run setenforce 0 to disable enforcement, 
try it again, and see if magic happens. Then of course reenable selinux via 
setenforce 1 and work the actual issue.  Basically test to be sure you can 
eliminate selinux as a possible cause.  But if selinux is blocking 
something it will log that someplace in /var/log
On Tuesday, April 30, 2024 at 5:12:37 PM UTC-7 Tom Keffer wrote:

> Vince, Redhat doesn't necessarily allow socket access for ports over 1024?
>
> On Tue, Apr 30, 2024 at 4:57 PM vince  wrote:
>
>> Marco are you running with selinux in enforcing mode ? Can you check for 
>> selinux errors in your logs or perhaps temporarily run with selinux 
>> disabled to see if that helps ? 
>>
>> Sorry but I’m away from a computer so I can’t give you the precise 
>> commands, but selinux can rather quietly stop things from working in some 
>> configurations. It would be helpful to eliminate that possibility.
>>
>> Other possibility is that your weewx user isn’t in a group with network 
>> access. What does ‘groups weewx’ return ?
>> On Tuesday, April 30, 2024 at 11:39:51 AM UTC-7 Tom Keffer wrote:
>>
>>> I am not that familiar with the IP logger, but I assume you would obey 
>>> the same echo TEST as a regular logger. If it doesn't, then it sounds like 
>>> there is a connectivity problem.
>>>
>>> Yes, it worked under WeeWX V3.8, but you have also changed servers since 
>>> then.
>>>
>>> Double check any firewalls. For example, do you use iptables? Does your 
>>> router prevent indiscriminate traffic between ports? 
>>>
>>>
>>>
>>> On Tue, Apr 30, 2024 at 10:45 AM Marco Citossi  
>>> wrote:
>>>
>>>> I've tried to change weewx.service but without results.
>>>> Telent doesn't echo anything.
>>>> The network should work because the old weewx (3.8.xxx) on the other 
>>>> webserver is working.
>>>>
>>>> Il giorno martedì 30 aprile 2024 alle 19:03:43 UTC+2 Tom Keffer ha 
>>>> scritto:
>>>>
>>>>> I am wondering whether the network is up and running by the time 
>>>>> weewxd tries to access it. Try editing your weewx systemd service file 
>>>>> (normally located in /lib/systemd/system/weewx.service) so it looks 
>>>>> something like the following:
>>>>>
>>>>> [Unit]
>>>>> Description=WeeWX
>>>>> Documentation=https://weewx.com/docs
>>>>> Requires=time-sync.target
>>>>> After=time-sync.target
>>>>> After=network-online.target
>>>>> Requires=network-online.target
>>>>>
>>>>> Then
>>>>>
>>>>> *sudo systemctl daemon-reload*
>>>>> *sudo systemctl restart weewx*
>>>>>
>>>>> If that doesn't work, we can try putting a sleep command in the 
>>>>> startup.
>>>>>
>>>>> Also, can you telnet to the logger and perform the logger TEST 
>>>>> function? The IP address of your logger got cut off in the log, but it 
>>>>> would look something like this (replace 140.105.xxx.yyy with the IP 
>>>>> address):
>>>>>
>>>>> telnet 140.105.xxx.yyy 2
>>>>> press  a few times.
>>>>> Then type "TEST", all caps. It will not echo.
>>>>> then 
>>>>> The logger should respond with "TEST".
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Apr 30, 2024 at 9:21 AM Marco Citossi  
>>>>> wrote:
>>>>>
>>>>>> Yes it's ethernet.
>>>>>>
>>>>>> Here it is the log:
>>>>>>
>>>>>>
>>>>>> apr 30 18:07:10 web4.xxx systemd[1]: Started WeeWX.
>>>>>>
>>>>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Initializing 
>>>>>> weewxd version 5.0.2
>>>>>>
>>>>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Command line: 
>>>>>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

[vince]

Marco are you running with selinux in enforcing mode ? Can you check for 
selinux errors in your logs or perhaps temporarily run with selinux 
disabled to see if that helps ? 

Sorry but I’m away from a computer so I can’t give you the precise 
commands, but selinux can rather quietly stop things from working in some 
configurations. It would be helpful to eliminate that possibility.

Other possibility is that your weewx user isn’t in a group with network 
access. What does ‘groups weewx’ return ?
On Tuesday, April 30, 2024 at 11:39:51 AM UTC-7 Tom Keffer wrote:

> I am not that familiar with the IP logger, but I assume you would obey the 
> same echo TEST as a regular logger. If it doesn't, then it sounds like 
> there is a connectivity problem.
>
> Yes, it worked under WeeWX V3.8, but you have also changed servers since 
> then.
>
> Double check any firewalls. For example, do you use iptables? Does your 
> router prevent indiscriminate traffic between ports? 
>
>
>
> On Tue, Apr 30, 2024 at 10:45 AM Marco Citossi  wrote:
>
>> I've tried to change weewx.service but without results.
>> Telent doesn't echo anything.
>> The network should work because the old weewx (3.8.xxx) on the other 
>> webserver is working.
>>
>> Il giorno martedì 30 aprile 2024 alle 19:03:43 UTC+2 Tom Keffer ha 
>> scritto:
>>
>>> I am wondering whether the network is up and running by the time weewxd 
>>> tries to access it. Try editing your weewx systemd service file (normally 
>>> located in /lib/systemd/system/weewx.service) so it looks something like 
>>> the following:
>>>
>>> [Unit]
>>> Description=WeeWX
>>> Documentation=https://weewx.com/docs
>>> Requires=time-sync.target
>>> After=time-sync.target
>>> After=network-online.target
>>> Requires=network-online.target
>>>
>>> Then
>>>
>>> *sudo systemctl daemon-reload*
>>> *sudo systemctl restart weewx*
>>>
>>> If that doesn't work, we can try putting a sleep command in the startup.
>>>
>>> Also, can you telnet to the logger and perform the logger TEST function? 
>>> The IP address of your logger got cut off in the log, but it would look 
>>> something like this (replace 140.105.xxx.yyy with the IP address):
>>>
>>> telnet 140.105.xxx.yyy 2
>>> press  a few times.
>>> Then type "TEST", all caps. It will not echo.
>>> then 
>>> The logger should respond with "TEST".
>>>
>>>
>>>
>>>
>>> On Tue, Apr 30, 2024 at 9:21 AM Marco Citossi  wrote:
>>>
 Yes it's ethernet.

 Here it is the log:


 apr 30 18:07:10 web4.xxx systemd[1]: Started WeeWX.

 apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Initializing 
 weewxd version 5.0.2

 apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Command line: 
 /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf

 apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Using Python 
 3.6.8 (default, Jan 16 2024, 02:08:59) 

  [GCC 8.5.0 20210514 
 (Red Hat 8.5.0-20.0.1)]

 apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Located at 
 /usr/bin/python3

 apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Platform 
 Linux-5.4.17-2136.330.7.1.el8uek.x86_64-x86_64-with-oracle-8.9

 apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Locale: 
 'en_US.UTF-8'

 apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Entry path: 
 /usr/share/weewx/weewxd.py

 apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: WEEWX_ROOT: 
 /etc/weewx

 apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Configuration 
 file: /etc/weewx/weewx.conf

 apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: User module: 
 /etc/weewx/bin/user

 apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Debug: 1

 apr 30 18:07:10 web4.xxx weewxd[22596]: DEBUG __main__: Initializing 
 engine

 apr 30 18:07:10 web4.xxx weewxd[22596]: INFO weewx.engine: Loading 
 station type Vantage (weewx.drivers.vantage)

 apr 30 18:07:10 web4.xxx weewxd[22596]: DEBUG weewx.drivers.vantage: 
 Driver version is 3.6.2

 apr 30 18:07:10 web4.xxx weewxd[22596]: DEBUG weewx.drivers.vantage: 
 Option loop_request=1

 apr 30 18:07:14 web4.xxx weewxd[22596]: ERROR weewx.drivers.vantage: 
 Socket error while opening port 2 to ethernet host 140.105.>

 apr 30 18:07:14 web4.xxx weewxd[22596]: ERROR weewx.engine: Import of 
 driver failed: timed out ()

 apr 30 18:07:14 web4.xxx weewxd[22596]: CRITICAL weewx.engine: 
   Traceback (most recent call last):

 apr 30 18:07:14 web4.xxx weewxd[22596]: CRITICAL weewx.engine: 
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 35>

 apr 30 18:07:14 web4.xxx weewxd[22596]: CRITICAL weewx.engine: 
   self.socket.connect((self.host, self.port))

 apr 30 18:07:14 web4.xxx weewxd[22596]: 

[weewx-user] Re: New install of weewx 5 fails to claim USB

[vince]

 Found it. The bottom section of the understanding permissions page has the 
details of which group can do what.

On Monday, April 29, 2024 at 1:21:51 PM UTC-7 Mary Ann Horton wrote:

> Thank you! I added weewx to the weewx group and rebooted - that got it 
> working.
> The wiki page is also very helpful. It would be nice if the doc and the 
> faq pointed there.
>
> On Monday, April 29, 2024 at 1:17:42 PM UTC-7 vince wrote:
>
>> Sorry can’t find where I wrote it up. 
>> https://groups.google.com/g/weewx-user/c/xCQlL3XPXhg/m/bHPnFWVLAQAJ At 
>> the bottom might help
>> On Monday, April 29, 2024 at 1:14:38 PM UTC-7 vince wrote:
>>
>>> Try adding the weewx user to group plugdev if I recall correctly. 
>>> Basically the user weewx runs has to be in a group that is permitted to 
>>> access the hardware.
>>>
>>> On Monday, April 29, 2024 at 11:07:49 AM UTC-7 Mary Ann Horton wrote:
>>>
>>>> I'm having a similar problem to what I see others are having, but the 
>>>> solutions I see here don't seem to work for me.
>>>> I had weewx 4 running on xubuntu 20.04 for years with a Acurite USB 
>>>> weather station - it worked great. Then my PC died. I got a new PC, a 
>>>> fresh 
>>>> xubuntu 22.04 installation, and a fresh "apt install weewx". I'm getting 
>>>> the permission error:
>>>> CRITICAL weewx.drivers.acurite: Unable to claim USB interface 0: [Errno 
>>>> 13] Access denied (insufficient permissions)
>>>>
>>>> The documentation says a fresh install will create the rule in 
>>>> /etc/udev/rules.d. It did not.
>>>> I found the acurite line in /etc/weewx/udev, and copied it into 
>>>> /etc/udev/rules.d/71-weewx.rules. Ran udevadm control --reload. service 
>>>> weewx restart. Same error.
>>>> I also found by unplugging the USB cable that the associated device is 
>>>> /dev/hidraw0. I've chowned it to weewx:weewx and chmodded it to 660. No 
>>>> joy.
>>>>
>>>> What am I missing? How do I track this down?
>>>>
>>>>

-- 
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/b266f342-7292-4a58-8d93-2de7073d188fn%40googlegroups.com.

[weewx-user] Re: New install of weewx 5 fails to claim USB

[vince]

Sorry can’t find where I wrote it up. 
https://groups.google.com/g/weewx-user/c/xCQlL3XPXhg/m/bHPnFWVLAQAJ At the 
bottom might help
On Monday, April 29, 2024 at 1:14:38 PM UTC-7 vince wrote:

> Try adding the weewx user to group plugdev if I recall correctly. 
> Basically the user weewx runs has to be in a group that is permitted to 
> access the hardware.
>
> On Monday, April 29, 2024 at 11:07:49 AM UTC-7 Mary Ann Horton wrote:
>
>> I'm having a similar problem to what I see others are having, but the 
>> solutions I see here don't seem to work for me.
>> I had weewx 4 running on xubuntu 20.04 for years with a Acurite USB 
>> weather station - it worked great. Then my PC died. I got a new PC, a fresh 
>> xubuntu 22.04 installation, and a fresh "apt install weewx". I'm getting 
>> the permission error:
>> CRITICAL weewx.drivers.acurite: Unable to claim USB interface 0: [Errno 
>> 13] Access denied (insufficient permissions)
>>
>> The documentation says a fresh install will create the rule in 
>> /etc/udev/rules.d. It did not.
>> I found the acurite line in /etc/weewx/udev, and copied it into 
>> /etc/udev/rules.d/71-weewx.rules. Ran udevadm control --reload. service 
>> weewx restart. Same error.
>> I also found by unplugging the USB cable that the associated device is 
>> /dev/hidraw0. I've chowned it to weewx:weewx and chmodded it to 660. No joy.
>>
>> What am I missing? How do I track this down?
>>
>>

-- 
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/d7fc41d3-cb02-47bb-8543-b4412187f962n%40googlegroups.com.

[weewx-user] Re: New install of weewx 5 fails to claim USB

[vince]

Try adding the weewx user to group plugdev if I recall correctly. Basically 
the user weewx runs has to be in a group that is permitted to access the 
hardware.

On Monday, April 29, 2024 at 11:07:49 AM UTC-7 Mary Ann Horton wrote:

> I'm having a similar problem to what I see others are having, but the 
> solutions I see here don't seem to work for me.
> I had weewx 4 running on xubuntu 20.04 for years with a Acurite USB 
> weather station - it worked great. Then my PC died. I got a new PC, a fresh 
> xubuntu 22.04 installation, and a fresh "apt install weewx". I'm getting 
> the permission error:
> CRITICAL weewx.drivers.acurite: Unable to claim USB interface 0: [Errno 
> 13] Access denied (insufficient permissions)
>
> The documentation says a fresh install will create the rule in 
> /etc/udev/rules.d. It did not.
> I found the acurite line in /etc/weewx/udev, and copied it into 
> /etc/udev/rules.d/71-weewx.rules. Ran udevadm control --reload. service 
> weewx restart. Same error.
> I also found by unplugging the USB cable that the associated device is 
> /dev/hidraw0. I've chowned it to weewx:weewx and chmodded it to 660. No joy.
>
> What am I missing? How do I track this down?
>
>

-- 
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/73810eaf-4c57-4c67-8fe4-5eb8cd116256n%40googlegroups.com.

[weewx-user] Re: formatting MQTT message sensor lenght

[vince]

This works here with HA 2023.8 in a docker container:

  - name: "Outside"

device_class: "temperature"

state_topic: "vp2/loop"

unit_of_measurement: '°F'

value_template: "{{ value_json.outTemp | float | round(1) }}"



On Friday, April 26, 2024 at 10:38:22 AM UTC-7 miso k wrote:

> finally... the name should not be in "" and it needs to be without space I 
> hope. I am getting value updates now.
>
> Thanks everyone for pointing me the right direction!
>
> Dátum: piatok 26. apríla 2024, čas: 19:29:52 UTC+2, odosielateľ: miso k
>
>> I can read the MQTT message in HA built in MQTT plugin. So the server is 
>> correctly set up and MQTT client too. I can even read the messages in MQTT 
>> Explorer. 
>> The problem is, that the entity in HA is not updating and is "unknown". 
>>
>> Dátum: piatok 26. apríla 2024, čas: 19:27:21 UTC+2, odosielateľ: miso k
>>
>>> I have red on another forum, that the number is too big for HA to read 
>>> it. Maybe I am wrong, but the possibilities that my configuration.yaml is 
>>> wrong are limited already I hope
>>>
>>> Dátum: štvrtok 25. apríla 2024, čas: 5:22:28 UTC+2, odosielateľ: 
>>> michael.k...@gmx.at
>>>
 What's the problem with the number of digits? Are they displayed 
 correctly in HA? Or is there a problem for HA dealing with that number of 
 digits generally?

 miso k schrieb am Mittwoch, 24. April 2024 um 22:15:18 UTC+2:

> Hello Weather observers,
>
> since long time my weewx server is running - and  updated to latest 
> 5.0.2 version.
>
> I want to export MQTT messages to Home Assistant, but the numbers are 
> too long.
> How can I make them shorter?
> Example:
> outHumidity = 91.0
> inHumidity = 56.0
> outTemp_C = 3.776
> inTemp_C = 22.89
> windSpeed_kph = 9.0123264
> windGust_kph = 9.3341952
>
>
> I have tried to format it through format = %.1f , but it does not 
> seems to work
>
> My MQTT Configuration:
>
> [[MQTT]]
> server_url = mqtt://xxx:xxx@localhost:1883/
> topic = weather
> unit_system = METRIC
> binding = archive, loop
> aggregation = individual
> log_success = False
> log_failure = True
> [[[inputs]]]
> outTemp
> name = inside_temperature  # use a label other than 
> outTemp
> format = %.1f  # two decimal places of 
> precision
> unit = degree_F# convert outTemp to F, 
> others in C
> inTemp
> unit = degree_C # use F instead of C
> format = %.1f   # use two decimal 
> places of precision
> name = inside_temperature   # use label other than 
> inTemp
> windSpeed
> units = meter_per_second# use knots instead of 
> meter_per_second
> format = %.1f   # use two decimal 
> places of precision
> name = wind_speed   # use label other than 
> inTemp
>
> Thank you!
> Michal
>


-- 
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/a8036a1d-c6f7-4c4d-9121-29e1927bdac5n%40googlegroups.com.

Re: [weewx-user] Problem for public_html access with Weewx 5 and apache 2

[vince]

I do it in the opposite direction.   The /var/www/html/weewx path is a 
directory.  The /home//weewx-data/public_html path is a symlink 'to' 
the webserver directory.

For a pip installation:
sudo mkdir /var/www/html/weewx
sudo chown ${WEEWXUSER}:${WEEWXUSER} /var/www/html/weewx
ln -s /var/www/html/weewx /home/${WEEWXUSER}/weewx-data/public_html


On Friday, April 26, 2024 at 7:53:03 AM UTC-7 Remy Lavabre wrote:

> 1/ if I try xxx.xxx.xxx.xxx/index.html -> Work fine, I've got the Apache2 
> Debian Default Page (which is in /var/www/html/index.html).
> 2/ if i try xxx.xxx.xxx.xxx/weewx/index.html -> Forbidden - You don't have 
> permission to access this resource. (with my symbolic link)
>
> I've tried :
> A/ sudo chown www-data ~/weewx-data/public_html -Rf
> B/ sudo chmod 775 -R ~/weewx-data/public_html
> --> Same thing
>
> C/ sudo nano /etc/apache2/sites-available/000-default.conf and change 
> "DocumentRoot /var/www/html" to "DocumentRoot ~/weewx-data/public_html"
>  xxx.xxx.xxx.xxx/index.html *and* xxx.xxx.xxx.xxx/weewx/index.html does 
> not work...
>
> Any idear ??
> Le vendredi 26 avril 2024 à 15:46:48 UTC+2, p q a écrit :
>
>> Looks like a rights issue with Apache. Find the apache.conf file and you 
>> probably need to enable access to the right directories.
>>
>> On Fri, Apr 26, 2024 at 6:26 AM Remy Lavabre  wrote:
>>
>>> Hello,
>>>
>>> Good morning,
>>> I didn't find the answer to my problem in the various discussions on the 
>>> WeeWX forum...
>>>
>>> I installed Weewx 5 in a virtual environment.
>>> So I have my weewx-data and weewx-venv directories in /home/---/
>>>
>>> weewxd seems to "finally" work normally with the 
>>> ~/weewx-data/public_html directory refreshing.
>>>
>>> On version 4, the weewx public_html directory was /var/www/html/weewx 
>>> ROOT:ROOT and did not pose a problem with the Apache 2 server.
>>> Since the location of the web server changed in version 5, I put a 
>>> symbolic link "weewx" in /var/www/html/ pointing to 
>>> ~/weewx-data/public_html/weewx [sudo ln -s/ ~/ weewx-data/public_htmlweewx 
>>> /var/www/html/weewx].
>>>
>>> The rights of var/www/html remained ROOT:ROOT while the rights of 
>>> ~/weewx-data/public_html/weewx are those of the creator.
>>>
>>> Filezilla navigation works correctly. Clicking on the symbolic link 
>>> takes you to the new WeeWX 5 public_html directory.
>>>
>>> However, when trying to connect through a web browser (
>>> http://xxx.xxx.xxx.xxx/weewx/index.html), I get the response:
>>> :
>>>
>>>
>>>
>>>
>>> *ForbiddenYou don't have permission to access this 
>>> resource.Apache/2.4.59 (Debian) Server at xxx.xxx.xxx.xxx Port 80*
>>>
>>> I think it must just be a rights issue...?
>>>
>>> *What is the recommended solution in Weewx 5 with Apache 2 to redirect 
>>> Apache from /var/www/html to ~/weewx-data/public_html?*
>>>
>>> Thanks a lot for the help! ;-)
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/1deda7f3-fa1e-4ab8-8ef7-a7b561fa9ffen%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>
>>
>> -- 
>> Peter Quinn
>> (415)794-2264 <(415)%20794-2264>
>>
>

-- 
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/f25d43bb-628c-43a6-8f99-2c473c9cdee4n%40googlegroups.com.

[weewx-user] Re: FTPS and Windows server

[vince]

Cron is not a kludge.  It's been around for decades longer than weewx.  Add 
one line to one file. Done.

On Wednesday, April 24, 2024 at 10:01:24 AM UTC-7 m8rk...@gmail.com wrote:

> I know that the Weewx documentation mentions that the Phyton's ftplib 
> implementation of FTPS does not work well with Windows servers. But I am 
> curious if there is an workaround for this problem besides using rsnyc 
> instead. Weewx is executing on a Raspberry Pi and Curl has no issues 
> transmitting file to the Windows 2023 IIS server using either the implicit 
> or explicit FTPS  protocol.  
>
> I suppose a contab script could be setup to transmit the html file to the 
> server instead of using Weewx's ftp but that is more or less another kludge 
> to maintain.
>

-- 
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/614a37f4-d0cb-4045-939f-9bd9ec32f015n%40googlegroups.com.

Re: [weewx-user] Replacement for Vantage Pro 2

[vince]

Highly recommend Scaled. Use their contact link if you have questions.  The 
other vendor was Scientific Sales but they don’t seem to have many parts 
anymore.  Both had great customer service for me.

On Tuesday, April 23, 2024 at 1:47:22 PM UTC-7 Charlie Fortner wrote:

> On Tue, Apr 23, 2024, at 16:20, 'Daniel Rich' via weewx-user wrote:
>
> The panel prices have gone up — $86.57 with shipping. 
>
>
> That's very expensive. Have you looked at Scaled Instruments? Vince 
> included a link to their selection of Davis parts in an earlier message. 
> I've ordered many parts and at least one VP2 from them. They are very 
> helpful and their prices are good.
>
>
> Charlie
>
>

-- 
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/5fd8c67c-5f87-417c-b2ea-e97077aba139n%40googlegroups.com.

[weewx-user] Re: No DB or reports update

[vince]

This one is a FAQ.  You have to update the skins.   Look again at the 
upgrade guide and a lot of previous threads here about that.

On Monday, April 22, 2024 at 1:25:28 PM UTC-7 John Walker wrote:

> Thanks for this.
> So I changed owner to 'weewx' on /var/www/html/weewx folder and everything 
> is working again now. Appreciate the help.
>
> Only weird thing remaining is that on the webpage it has the below - with 
> a WeeWX v5 upgrade should the skins not be updated as well?
>
> WeeWX version
> 5.0.2
> Skin
> Seasons 4.9.1
>
> On Monday, April 22, 2024 at 12:03:13 PM UTC-4 vince wrote:
>
>> Another permission denied issue. I'm guessing you are mounting a NAS or 
>> other network drive ?
>>
>> The weewx user needs permission to write to wherever it's trying to write 
>> to.
>>
>>
>> Apr 22 08:45:47 sparta weewxd[465042]: DEBUG 
>> user.weatherlink_live.davis_broadcast: Stopped broadcast reception Apr 22 
>> 08:45:47 sparta weewxd[465042]: CRITICAL __main__: Caught OSError: [Errno 
>> 13] Permission denied: 
>> '/srv/samba/raid1/public_shares/weewx/data-2024-04.csv' Apr 22 08:45:47 
>> sparta weewxd[465042]: CRITICAL __main__:  Traceback (most recent call 
>> last): Apr 22 08:45:47 sparta weewxd[465042]: CRITICAL __main__:  File 
>> "/usr/share/weewx/weewxd.py", line 166, in main Apr 22 08:45:47 sparta 
>> weewxd[465042]: CRITICAL __main__:  engine.run() Apr 22 08:45:47 sparta 
>> weewxd[465042]: CRITICAL __main__:  File 
>> "/usr/share/weewx/weewx/engine.py", line 206, in run Apr 22 08:45:47 sparta 
>> weewxd[465042]: CRITICAL __main__:  
>> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet)) Apr 
>> 22 08:45:47 sparta weewxd[465042]: CRITICAL __main__:  File 
>> "/usr/share/weewx/weewx/engine.py", line 241, in dispatchEvent Apr 22 
>> 08:45:47 sparta weewxd[465042]: CRITICAL __main__:  callback(event) Apr 
>> 22 08:45:47 sparta weewxd[465042]: CRITICAL __main__:  File 
>> "/etc/weewx/bin/user/csv.py", line 63, in handle_new_loop Apr 22 08:45:47 
>> sparta weewxd[465042]: CRITICAL __main__:  
>> self.write_data(event.packet) Apr 22 08:45:47 sparta weewxd[465042]: 
>> CRITICAL __main__:  File "/etc/weewx/bin/user/csv.py", line 85, in 
>> write_data Apr 22 08:45:47 sparta weewxd[465042]: CRITICAL __main__:  
>> with open(filename, flag) as f: Apr 22 08:45:47 sparta weewxd[465042]: 
>> CRITICAL __main__:  PermissionError: [Errno 13] Permission denied: 
>> '/srv/samba/raid1/public_shares/weewx/data-2024-04.csv' Apr 22 08:45:47 
>> sparta weewxd[465042]: CRITICAL __main__:  Waiting 10 seconds then 
>> retrying...
>>
>>
>> On Monday, April 22, 2024 at 6:12:22 AM UTC-7 John Walker wrote:
>>
>>> Hi Gary - many thanks. I captured a log file from startup for 10+ mins - 
>>> see attached.
>>> Below is service status report after the log capture.
>>> I do have a reports copy to a network share that isn't working due to 
>>> some permissions error - that is in the log file too.
>>>
>>>
>>> ● weewx.service - WeeWX
>>>  Loaded: loaded (/etc/systemd/system/weewx.service; enabled; vendor 
>>> preset: enabled)
>>>  Active: active (running) since Mon 2024-04-22 08:44:05 EDT; 24min 
>>> ago
>>>Docs: https://weewx.com/docs
>>>Main PID: 465042 (python3)
>>>   Tasks: 3 (limit: 18955)
>>>  Memory: 66.9M
>>> CPU: 29.462s
>>>  CGroup: /system.slice/weewx.service
>>>  └─465042 python3 /usr/share/weewx/weewxd.py 
>>> /etc/weewx/weewx.conf
>>>
>>> On Sunday, April 21, 2024 at 4:05:33 PM UTC-4 gjr80 wrote:
>>>
>>>> Reinstalling is a bit drastic without first seeing what the problem is. 
>>>> Despite a lengthy log extract we did not see the full WeeWX startup 
>>>> (didn't 
>>>> see anything covering the driver being loaded) nor did we see anything 
>>>> after WeeWX startup. How about posting another log extract showing the 
>>>> full 
>>>> WeeWX startup and a good 10-15 minutes after WeeWX has started (ie after 
>>>> the 'Starting main packet loop' log entry).
>>>>
>>>> Gary
>>>>
>>>> On Monday 22 April 2024 at 01:54:50 UTC+10 jw1...@gmail.com wrote:
>>>>
>>>>> Hi,
>>>>> Amid some updates and other problem solving I now have no updates 
>>>>> happening to the database nor the /var/www/htm

[weewx-user] Re: Tempest WeatherFlow UV and Radiation

[vince]

Yes that's normal.   Look at any of the weatherflow-udp stations registered 
on the weewx map and you'll see the same thing.

-- 
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/656c3c3d-25b1-4b66-85d7-588e2f77dedfn%40googlegroups.com.

[weewx-user] Re: No DB or reports update

[vince]

Another permission denied issue. I'm guessing you are mounting a NAS or 
other network drive ?

The weewx user needs permission to write to wherever it's trying to write 
to.


Apr 22 08:45:47 sparta weewxd[465042]: DEBUG 
user.weatherlink_live.davis_broadcast: Stopped broadcast reception Apr 22 
08:45:47 sparta weewxd[465042]: CRITICAL __main__: Caught OSError: [Errno 
13] Permission denied: 
'/srv/samba/raid1/public_shares/weewx/data-2024-04.csv' Apr 22 08:45:47 
sparta weewxd[465042]: CRITICAL __main__:  Traceback (most recent call 
last): Apr 22 08:45:47 sparta weewxd[465042]: CRITICAL __main__:  File 
"/usr/share/weewx/weewxd.py", line 166, in main Apr 22 08:45:47 sparta 
weewxd[465042]: CRITICAL __main__:  engine.run() Apr 22 08:45:47 sparta 
weewxd[465042]: CRITICAL __main__:  File 
"/usr/share/weewx/weewx/engine.py", line 206, in run Apr 22 08:45:47 sparta 
weewxd[465042]: CRITICAL __main__:  
self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet)) Apr 
22 08:45:47 sparta weewxd[465042]: CRITICAL __main__:  File 
"/usr/share/weewx/weewx/engine.py", line 241, in dispatchEvent Apr 22 
08:45:47 sparta weewxd[465042]: CRITICAL __main__:  callback(event) Apr 
22 08:45:47 sparta weewxd[465042]: CRITICAL __main__:  File 
"/etc/weewx/bin/user/csv.py", line 63, in handle_new_loop Apr 22 08:45:47 
sparta weewxd[465042]: CRITICAL __main__:  
self.write_data(event.packet) Apr 22 08:45:47 sparta weewxd[465042]: 
CRITICAL __main__:  File "/etc/weewx/bin/user/csv.py", line 85, in 
write_data Apr 22 08:45:47 sparta weewxd[465042]: CRITICAL __main__:  
with open(filename, flag) as f: Apr 22 08:45:47 sparta weewxd[465042]: 
CRITICAL __main__:  PermissionError: [Errno 13] Permission denied: 
'/srv/samba/raid1/public_shares/weewx/data-2024-04.csv' Apr 22 08:45:47 
sparta weewxd[465042]: CRITICAL __main__:  Waiting 10 seconds then 
retrying...


On Monday, April 22, 2024 at 6:12:22 AM UTC-7 John Walker wrote:

> Hi Gary - many thanks. I captured a log file from startup for 10+ mins - 
> see attached.
> Below is service status report after the log capture.
> I do have a reports copy to a network share that isn't working due to some 
> permissions error - that is in the log file too.
>
>
> ● weewx.service - WeeWX
>  Loaded: loaded (/etc/systemd/system/weewx.service; enabled; vendor 
> preset: enabled)
>  Active: active (running) since Mon 2024-04-22 08:44:05 EDT; 24min ago
>Docs: https://weewx.com/docs
>Main PID: 465042 (python3)
>   Tasks: 3 (limit: 18955)
>  Memory: 66.9M
> CPU: 29.462s
>  CGroup: /system.slice/weewx.service
>  └─465042 python3 /usr/share/weewx/weewxd.py 
> /etc/weewx/weewx.conf
>
> On Sunday, April 21, 2024 at 4:05:33 PM UTC-4 gjr80 wrote:
>
>> Reinstalling is a bit drastic without first seeing what the problem is. 
>> Despite a lengthy log extract we did not see the full WeeWX startup (didn't 
>> see anything covering the driver being loaded) nor did we see anything 
>> after WeeWX startup. How about posting another log extract showing the full 
>> WeeWX startup and a good 10-15 minutes after WeeWX has started (ie after 
>> the 'Starting main packet loop' log entry).
>>
>> Gary
>>
>> On Monday 22 April 2024 at 01:54:50 UTC+10 jw1...@gmail.com wrote:
>>
>>> Hi,
>>> Amid some updates and other problem solving I now have no updates 
>>> happening to the database nor the /var/www/html/weewx reports.
>>> I could have butchered the config it a bit - is there a safe (retaining 
>>> database) way to reinstall? Weewx.conf and syslog excerpt below.
>>> Thanks,
>>> JW
>>>
>>>
>>> *WEEWX.CONF (first couple sections)*
>>>
>>> # WEEWX CONFIGURATION FILE
>>> #
>>> # Copyright (c) 2009-2021 Tom Keffer 
>>> # See the file LICENSE.txt for your rights.
>>>
>>>
>>> ##
>>>
>>> # This section is for general configuration information.
>>>
>>> # Set to 1 for extra debug info, otherwise comment it out or set to zero
>>> debug = 1
>>>
>>> # Root directory of the weewx data file hierarchy for this station
>>> WEEWX_ROOT = /
>>>
>>> # Whether to log successful operations
>>> log_success = True
>>>
>>> # Whether to log unsuccessful operations
>>> log_failure = True
>>>
>>> # How long to wait before timing out a socket (FTP, HTTP) connection
>>> socket_timeout = 20
>>>
>>> # Do not modify this. It is used when installing and updating weewx.
>>> version = 5.0.2
>>>
>>>
>>> ##
>>>
>>>
>>> *SYSLOG EXCERPT*
>>>
>>> Apr 21 11:46:10 sparta weewxd[429125]: DEBUG weewx.engine: Loading 
>>> service weewx.engine.StdTimeSynch
>>> Apr 21 11:46:10 sparta weewxd[429125]: DEBUG weewx.engine: Finished 
>>> loading service weewx.engine.StdTimeSynch
>>> Apr 21 11:46:10 sparta weewxd[429125]: DEBUG weewx.engine: Loading 
>>> service weewx.engine.StdConvert
>>> Apr 21 11:46:10 sparta 

[weewx-user] Re: Replacement for Vantage Pro 2

[vince]

Based on your description it sounds like a new battery (CR123 - $10) and 
perhaps a solar panel ($55) will handle the data problems, but I'd suggest 
doing just the battery first to see.

Adding UV/solar to a Davis is crazy expensive.  There seem to be a lot of 
different replacement rain gauge assemblies available in the $60-85 range 
if you poke around online at Scaled Instruments (link 
).
 
 Those guys are pretty responsive in my experience if you want to email 
questions.

You could probably sell your VP2 for more than the price of whatever you're 
thinking of replacing it with.

On Monday, April 22, 2024 at 8:34:33 AM UTC-7 wwwd...@gmail.com wrote:

> My Vantage Pro 2 is showing its age. The solar panel needs to be replaced, 
> as I'm losing the station connection once the sun goes down and regularly 
> having issues with the rain gauge not registering rainfall. I know that I 
> can send it into Davis for a tune up ($225 do buy the parts, $400+ if they 
> do it), but given the cost of that I'm wondering if it is just time to 
> replace it. It also doesn't give me warm fuzzies that I never heard back 
> from them when I tried to contact them about a repair.
>
> Does anyone have a recommendation for a replacement station that doesn't 
> break the bank like the Vantage Pro? Ideally I would like to have the same 
> basic sensors and be able to add UV and solar radiation, as I use that to 
> make sure my rooftop solar is producing appropriately. And of course, 
> continuing to work with weewx is a requirement! :-)
>
> Thanks!
>
> -- 
> Dan Rich  |   http://www.employees.org/~drich/
>|  "Step up to red alert!"  "Are you sure, 
> sir?
>|   It means changing the bulb in the 
> sign..."
>|  - Red Dwarf (BBC)
>

-- 
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/3e894801-4d03-4983-974d-15c6a65ad084n%40googlegroups.com.

[weewx-user] Re: No DB or reports update

[vince]

On Sunday, April 21, 2024 at 8:54:50 AM UTC-7 John Walker wrote:

I could have butchered the config it a bit - is there a safe (retaining 
database) way to reinstall? Weewx.conf and syslog excerpt below.


Simply stash a copy of your database and weewx.conf file and you can 
certainly delete everything else and start anew.  
 

-- 
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/41a452dd-d419-439e-8b2d-070c9361c2f3n%40googlegroups.com.

[weewx-user] Re: Lightning sensor from Ecowitt PWS problem

[vince]

One is since the last archive period, the other is the sum of all archive 
periods in that longer time period.

Check your db and see if the records add up.

On Saturday, April 20, 2024 at 11:40:57 AM UTC-7 Riccardo Rossi (RikyUnreal 
- IU4APB) wrote:

> Hi all,
> I'm running WeeWX 4.10.2 on a Raspberry PI3 and I'm getting data from 
> an Ecowitt PWS.
>
> To do this, I used this tutorial 
> https://www.cougar.eu.com/useful-guides/weewx-guides/rasberry-pi/add-ecowitt/index.html
>
> It works like a charm and recently I added a lightning sensor to the PWS: 
> today the sensor finally detected two lightnings.
>
> As you can see in the screenshot, the lightning strikes in the "Current 
> Conditions" section are correct, but in the "Statistics" section the number 
> is weird and it keeps increasing right now even though no more lightning 
> are occurring.  The bar graph is also anomalous.
>
> Any suggestions to fix the issue?
>
> Riky
>

-- 
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/20f8f299-8a4a-4f04-b226-d68e2fffc02dn%40googlegroups.com.

[weewx-user] Re: Belling the Cat — Was: Launching Weewx

[vince]

Wonderful 

On Tuesday, April 16, 2024 at 11:54:49 AM UTC-7 Marie-Laure TERRIENNE wrote:

> vince, avant toute chose, je voudrais vous remercier de m'avoir accompagné 
> pour résoudre un problème ... qui n'en était pas un, mais qui était, comme 
> vous l'avez deviné, un problème lié à ma mauvaise connaissance de 
> l'environnement Linux (Ubuntu dans mon cas).
>
> Je pensais aussi que weewx était une application autonome et qu'avoir un 
> serveur n'était qu'un petit plus.
>
> Vous m'aviez demandé d'installer un serveur (nginx) et allant voir dans 
> mon gestionnaire de paquets, ce serveur et ces dépendances étaient cochés. 
> Oui, coché, mais pas installé ! J'avais mal interprété les coches. Je viens 
> donc de l'installer et de relancer la commande que vous m'aviez dite : 
> http://192.168.0.7/weewx <http://your_ip_here/weewx> et Oh miracle, les 
> jolies courbes comme celles de la page weewx.com se sont affichées.
>
> Je pense donc que "mon" problème est résolu. Tout fonctionne très bien.
>
> Encore merci vince.
>
> Cordialement.
>
> Pierre.
>
>
>
>

-- 
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/fec6942e-0a5d-46c2-904b-9440bf746a20n%40googlegroups.com.

[weewx-user] Re: Belling the Cat — Was: Launching Weewx

[vince]

Pierre - I'm sorry but I have to ask some more general questions:

   - have you ever run weewx before, or is this a new installation ?
   - Are you a new unix/linux user ?
   - Did you install a webserver onto your weewx computer ?  If so, which 
   one ?
   
Your questions tell me that you do not quite understand the entire system 
end-to-end, unless GoogleTranslate is misleading me.

   - weewx connects to your weather station to query it for sensor data
   - weewx periodically saves that data to a sqlite3 database named 
   'weewx.sdb'
   - weewx also periodically generates web pages and images 'from' that 
   data and saves them to /var/www/html/weewx by default

And:

   - you 'also' need to install a webserver app of your choice.  I 
   recommend nginx as the webserver to use
   - if you have weewx and a webserver installed, you should not see any 
   permission errors at all
   - you should not need to write your own software to read the database 
   and write out your own web pages or images

We can fix your permission errors but I wanted to make sure you understand 
what a complete weewx system looks like.  You need weewx 'and' a webserver 
installed and both need to be configured so that they work together.  If 
you install weewx and nginx, you should not be seeing any errors at all, 
and you should be able to browser your web pages via any browser.


(last questions he asked via Google Translate for our mostly 
English-speaking readers here)

*Apparently, my station is recognized and information is saved in a 
file named "weewx.sdb". What is this type of database?*







*I think the error lines correspond to data not provided by my 
station.How do we get graphical presentations like those shown on the 
right of the page: https://weewx.com/?I understand that these are 
images of applications that some users were willing to show, but that this 
is not an "option" of weewx. Yes No ?Being an Object Pascal programmer 
with Lazarus, I could make a similar presentation as long as I could insert 
the data from my station. But to do this, I need to be able to retrieve 
this data, updated every "x" seconds via weewx. Where to get this? In which 
file?*

-- 
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/59859d5d-832f-44b9-b755-b4447db5ba98n%40googlegroups.com.

[weewx-user] Re: Belling the Cat — Was: Launching Weewx

[vince]

rt = 
> 2011-01-01T00:00# The driver to use.driver = 
> weewx.drivers.simulator##*
>
> Cela ne correspond plus à ma station, ça correspond au simulator et quand 
> je lance :"sudo weewxd /etc/weewx/weewx.conf-5.0.2, j'obtiens des 
> résultats dans le terminal, mais ils ne correspondent bien entendu pas à 
> ceux de ma station. C'est à peu près les mêmes valeurs que celles que vous 
> avez mises dans votre post.
>
> Faut-il modifier weewx.conf-5.0.2 et si oui, comment.
>
> Cordialement.
>
> Pierre.
> Le dimanche 14 avril 2024 à 20:45:52 UTC+2, vince a écrit :
>
>> Your English is ok.  Google Translate is not always so ok :-)
>>
>> You might want to check your /etc/weewx/weewx.conf to see if it looks 
>> correct.  Make sure that it is not zero length.   This example is running 
>> the simulator driver.
>>
>> /etc/weewx$ ls -lgd /etc/weewx/weewx.conf*
>> -rw-r--r-- 1 weewx 23713 Apr  2 12:04 /etc/weewx/weewx.conf
>> -rw-rw-r-- 1 weewx 19482 Apr  2 12:04 /etc/weewx/weewx.conf.20240402120403
>> -rw-rw-r-- 1 weewx 19463 Feb  9 23:03 /etc/weewx/weewx.conf-5.0.2
>>
>> Weewx v5 runs as user 'weewx' and group 'weewx', but the command to test 
>> from the shell is somewhat complicated.  This example is the simulator 
>> driver.
>>
>> $ sudo -u weewx bash -c 'python3 /usr/share/weewx/weewxd.py 
>> /etc/weewx/weewx.conf'
>>
>> LOOP:   2024-04-14 11:39:38 PDT (1713119978) 'altimeter': 
>> '31.10283290280814', 'appTemp': '28.46010918752483', 'barometer': 
>> '31.09998967093', 'cloudbase': '1244.323176426526', 
>> 'consBatteryVoltage': '12.718450749586843', 'dateTime': '1713119978', 
>> 'dewpoint': '27.203560993945757', 'ET': 'None', 'heatindex': 
>> '32.67858297022247', 'heatingVoltage': '12.0', 'humidex': 
>> '32.67858297022247', 'inDewpoint': '31.079533828013187', 'inHumidity': 
>> '29.99958683617', 'inTemp': '63.0002065819', 'inTempBatteryStatus': 
>> '0', 'maxSolarRad': '66.05216886122633', 'outHumidity': 
>> '79.9996901272', 'outTemp': '32.67858297022247', 
>> 'outTempBatteryStatus': '0', 'pressure': '31.09998967093', 'radiation': 
>> '992.1106767453836', 'rain': '0', 'rainBatteryStatus': '0', 'rainRate': 
>> '0.0', 'referenceVoltage': '12.0', 'rxCheckPercent': '82.52427564124497', 
>> 'supplyVoltage': '13.150462912118508', 'txBatteryStatus': '0', 'usUnits': 
>> '1', 'UV': '13.88954947443537', 'windBatteryStatus': '0', 'windchill': 
>> '32.67858297022247', 'windDir': '359.998140763', 'windGust': 
>> '6.197456769996279e-09', 'windGustDir': '359.998140763', 'windrun': 
>> 'None', 'windSpeed': '5.164547900449179e-09'
>>
>> ^C to stop it in the command above.   You should see LOOP messages every 
>> few seconds.
>>
>> To start and stop weewx, you would use systemctl 'with' sudo required:
>>
>> $ sudo systemctl start weewx
>> $ sudo systemctl stop weewx
>>
>> On Sunday, April 14, 2024 at 10:50:24 AM UTC-7 Marie-Laure TERRIENNE 
>> wrote:
>>
>>> Thank you very much "vince" for answering to my problem.
>>>
>>> First of all : I am French and not very good in English. I often use 
>>> Google's online translation.
>>> This was an opportunity for : Just a question : how do you simply 
>>> launch, usually "weewx". Here is the French formulation: Simple question: 
>>> Comment lance-ton normalement, habituellement "weewx"?
>>>
>>> Note : If I run the following commands :
>>>
>>> sudo weewxd
>>> sudo weewxd /etc/weewx/weewx.conf
>>>
>>> Nothing happens.
>>>
>>> if I run : sudo weewxd /etc/weewx/weewx.conf-5.0.2, I get in the shell 
>>> a lot of information about my weather station. This information is 
>>> updated every two seconds. Mais je n'ai toujours pas de présentation 
>>> graphique comme montrée dans le site weewx
>>>
>>> Now, reading your answers, I have the impression that you have not 
>>> understood my software and hardware configuration. I only have one computer 
>>> with Ubuntu operating system and I have "weewx" installed on it. My web 
>>> browser is Firefox.
>>>
>>> With Firefox, I can go to any external site ; that of this forum for 
>>> example.
>>>
>>> I haven't tried it with another browser yet.
>>>
>>> Sincerely.
>>>
>>> Pierre.
>>> Le dimanche 14 avril 2024 à 18:33:28 UTC+2, vince a écrit :
>>>
>>>

[weewx-user] Re: Belling the Cat — Was: Launching Weewx

[vince]

Your English is ok.  Google Translate is not always so ok :-)

You might want to check your /etc/weewx/weewx.conf to see if it looks 
correct.  Make sure that it is not zero length.   This example is running 
the simulator driver.

/etc/weewx$ ls -lgd /etc/weewx/weewx.conf*
-rw-r--r-- 1 weewx 23713 Apr  2 12:04 /etc/weewx/weewx.conf
-rw-rw-r-- 1 weewx 19482 Apr  2 12:04 /etc/weewx/weewx.conf.20240402120403
-rw-rw-r-- 1 weewx 19463 Feb  9 23:03 /etc/weewx/weewx.conf-5.0.2

Weewx v5 runs as user 'weewx' and group 'weewx', but the command to test 
from the shell is somewhat complicated.  This example is the simulator 
driver.

$ sudo -u weewx bash -c 'python3 /usr/share/weewx/weewxd.py 
/etc/weewx/weewx.conf'

LOOP:   2024-04-14 11:39:38 PDT (1713119978) 'altimeter': 
'31.10283290280814', 'appTemp': '28.46010918752483', 'barometer': 
'31.09998967093', 'cloudbase': '1244.323176426526', 
'consBatteryVoltage': '12.718450749586843', 'dateTime': '1713119978', 
'dewpoint': '27.203560993945757', 'ET': 'None', 'heatindex': 
'32.67858297022247', 'heatingVoltage': '12.0', 'humidex': 
'32.67858297022247', 'inDewpoint': '31.079533828013187', 'inHumidity': 
'29.99958683617', 'inTemp': '63.0002065819', 'inTempBatteryStatus': 
'0', 'maxSolarRad': '66.05216886122633', 'outHumidity': 
'79.9996901272', 'outTemp': '32.67858297022247', 
'outTempBatteryStatus': '0', 'pressure': '31.09998967093', 'radiation': 
'992.1106767453836', 'rain': '0', 'rainBatteryStatus': '0', 'rainRate': 
'0.0', 'referenceVoltage': '12.0', 'rxCheckPercent': '82.52427564124497', 
'supplyVoltage': '13.150462912118508', 'txBatteryStatus': '0', 'usUnits': 
'1', 'UV': '13.88954947443537', 'windBatteryStatus': '0', 'windchill': 
'32.67858297022247', 'windDir': '359.998140763', 'windGust': 
'6.197456769996279e-09', 'windGustDir': '359.998140763', 'windrun': 
'None', 'windSpeed': '5.164547900449179e-09'

^C to stop it in the command above.   You should see LOOP messages every 
few seconds.

To start and stop weewx, you would use systemctl 'with' sudo required:

$ sudo systemctl start weewx
$ sudo systemctl stop weewx

On Sunday, April 14, 2024 at 10:50:24 AM UTC-7 Marie-Laure TERRIENNE wrote:

> Thank you very much "vince" for answering to my problem.
>
> First of all : I am French and not very good in English. I often use 
> Google's online translation.
> This was an opportunity for : Just a question : how do you simply launch, 
> usually "weewx". Here is the French formulation: Simple question: Comment 
> lance-ton normalement, habituellement "weewx"?
>
> Note : If I run the following commands :
>
> sudo weewxd
> sudo weewxd /etc/weewx/weewx.conf
>
> Nothing happens.
>
> if I run : sudo weewxd /etc/weewx/weewx.conf-5.0.2, I get in the shell a 
> lot of information about my weather station. This information is updated 
> every two seconds. Mais je n'ai toujours pas de présentation graphique 
> comme montrée dans le site weewx
>
> Now, reading your answers, I have the impression that you have not 
> understood my software and hardware configuration. I only have one computer 
> with Ubuntu operating system and I have "weewx" installed on it. My web 
> browser is Firefox.
>
> With Firefox, I can go to any external site ; that of this forum for 
> example.
>
> I haven't tried it with another browser yet.
>
> Sincerely.
>
> Pierre.
> Le dimanche 14 avril 2024 à 18:33:28 UTC+2, vince a écrit :
>
>> On Sunday, April 14, 2024 at 1:04:35 AM UTC-7 Marie-Laure TERRIENNE wrote:
>>
>> vince : i tried what you said : http://192.168.0.7/weewx
>>
>> the answaer is :
>> The connection failed
>> An error occurred while connecting to 192.168.0.7.
>> The site may be temporarily unavailable or overloaded. Try again later;
>> If you cannot navigate to any site, check your computer's network 
>> connection;
>> If your computer or network is protected by a firewall or proxy, make 
>> sure Firefox is allowed to access the web.
>>
>>
>> Are you running Firefox on the weewx computer, or are you running it on a 
>> different computer (MS Windows?) ?
>>
>> Are you running a firewall on the computer you are running Firefox on ?   
>> Are you running a firewall on the weewx computer ?
>>
>>  
>>
>> Just a question : how do you simply launch, usually "weewx"
>>
>>  
>> I'm sorry, I do not understand the question.  If you are not a native 
>> English speaker, rephrase that in French (?) and perhaps Google Translate 
>> will generate a different wording in English.
>>
>> Your weewx log file seems to say that weewx is running.   Your error 
>> message seems to say the operating system on the computer you are running 
>> Firef

[weewx-user] Re: Belling the Cat — Was: Launching Weewx

[vince]

On Sunday, April 14, 2024 at 1:04:35 AM UTC-7 Marie-Laure TERRIENNE wrote:

vince : i tried what you said : http://192.168.0.7/weewx

the answaer is :
The connection failed
An error occurred while connecting to 192.168.0.7.
The site may be temporarily unavailable or overloaded. Try again later;
If you cannot navigate to any site, check your computer's network 
connection;
If your computer or network is protected by a firewall or proxy, make sure 
Firefox is allowed to access the web.


Are you running Firefox on the weewx computer, or are you running it on a 
different computer (MS Windows?) ?

Are you running a firewall on the computer you are running Firefox on ?   
Are you running a firewall on the weewx computer ?

 

Just a question : how do you simply launch, usually "weewx"

 
I'm sorry, I do not understand the question.  If you are not a native 
English speaker, rephrase that in French (?) and perhaps Google Translate 
will generate a different wording in English.

Your weewx log file seems to say that weewx is running.   Your error 
message seems to say the operating system on the computer you are running 
Firefox on is blocking Firefox from accessing your web site.   Can Firefox 
access other websites ?Can you try a different browser on your ubuntu 
computer ?

If you can run a command from a shell prompt on your weewx computer, log 
into the weewx computer and run "curl http://192.168.0.7; and then "curl 
http://192.168.0.7/weewx; and see if they respond with something looking 
like a web page.

-- 
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/150787a1-02de-4224-a67b-eaa57898c6fcn%40googlegroups.com.

[weewx-user] Re: Belling the Cat — Was: Launching Weewx

[vince]

I would suggest installing a webserver (I recommend nginx) and then just 
opening http://your_ip_here/weewx and seeing if that works.  Your log looks 
ok to me.

On Friday, April 12, 2024 at 11:51:31 AM UTC-7 Marie-Laure TERRIENNE wrote:

> I have followed what is said to get the log. Here is what i got :
>
>
> Le vendredi 12 avril 2024 à 19:21:23 UTC+2, Chuck Rhode a écrit :
>
>> -BEGIN PGP SIGNED MESSAGE- 
>> Hash: SHA1 
>>
>> On Fri, 12 Apr 2024 08:43:04 -0500 
>> DR  wrote: 
>>
>> > THE most often made comment from the developers is to turn on debug 
>> > and then furnish the log. 
>>
>> Humpf! If it's that easy, why not put it in a script like a 
>> client-side *bugzilla*? Seems like a good idea to me. All us mice could 
>> approve, wouldn't we? 
>>
>> Of course, it takes only one mouse to put a bell on this (apparently) 
>> sleepy cat. 
>>
>> What scope should the script have? 
>>
>> + NO PARAMETERS! 
>>
>> + NO *.ini*! 
>>
>> + Import *configobj*. 
>>
>> + Get write authority to ~/weewx-data/weewx.conf. Not so easy because 
>> it could be in any number of locations. 
>>
>> + Save *debug* option status. 
>>
>> + Set *debug* option. 
>>
>> + Ask real-time User of this script for *root* authority and escalate 
>> to it, telling User what we're doing and making doubly sure of his 
>> approval. Danger, Will Robinson! 
>>
>> + Do *systemctl restart weewx*. If this fails, throw up hands. 
>>
>> + Keep User on hold for an hour. 
>>
>> + Reset *debug* option. 
>>
>> + Do *systemctl restart weewx*. Expect success. 
>>
>> + Checkpoint current log file. Not so easy because it could be in any 
>> number of locations. Allow read-only access to User. 
>>
>> + Relinquish *root* authority. 
>>
>> + Checkpoint the output of *weectl debug*. 
>>
>> + Ask for the User's favorite code editor. Give Newbies *emacs*. 
>>
>> + Conjure authority to send eMail. 
>>
>> * What is your name? 
>>
>> * What is your eMail address? 
>>
>> * Which is your SMTP server? 
>>
>> * What port is allowed? 
>>
>> * What password is required? 
>>
>> * What is your quest? 
>>
>> * What's your favorite color? 
>>
>> + Present a template for a well-formed Bug report. 
>>
>> * What happened that prompted you to make this bug report? 
>>
>> * What did you expect to happen? 
>>
>> * What did you do to make it happen? 
>>
>> * What was the most recent change you made? 
>>
>> + Checkpoint the template and amendments. 
>>
>> + Compose eMail to weewx...@googlegroups.com. 
>>
>> + Show the User what we're going to send (with attachments) and ask 
>> for approval. 
>>
>> + Import *smtplib*. 
>>
>> + Import *email.message*. 
>>
>> + Do *SMTP.send_message()*. If this fails, throw up hands. 
>>
>>
>> - -- 
>> .. Be Seeing You, 
>> .. Chuck Rhode, Sheboygan, WI, USA 
>> .. Weather: http://LacusVeris.com/WX 
>> .. 53° — Wind NNW 25 mph 
>>
>> -BEGIN PGP SIGNATURE- 
>>
>> iF0EARECAB0WIQT+MY/5I/LMPSswTbVg2/xipKOWUgUCZhltfgAKCRBg2/xipKOW 
>> UuySAJ95fU4/3AMb+PFfbW90Zt+dPL9p/QCdHytzG+LsiviUTPGQJ+PQXd74aLI= 
>> =KydE 
>> -END PGP SIGNATURE- 
>>
>

-- 
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/b9b2b18e-937f-48e7-b6d3-b95263bd24ean%40googlegroups.com.

Re: [weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

[vince]

So is there a /home/weewx/bin/weewxd file ?
What is in your /home/weewx tree ?

Did you perhaps install as user 'pi' and everything is under there ?

On Wednesday, April 10, 2024 at 12:27:54 PM UTC-7 Juan Antonio Mosquera 
Casais wrote:

> pi@raspberrypi:/etc $ cat /etc/systemd/system/weewx.service
> # systemd unit configuration file for WeeWX
> #
> # For information about running WeeWX under systemd,
> # be sure to read https://github.com/weewx/weewx/wiki/systemd
> #
> [Unit]
> Description=WeeWX weather system
> Documentation=https://weewx.com/docs
>
> Requires=time-sync.target
> After=time-sync.target
> RequiresMountsFor=/home
>
> [Service]
> ExecStart=/home/weewx/bin/weewxd /home/weewx/weewx.conf
> StandardOutput=null
> # To run as a non-root user, uncomment and set username and group here:
> #User=weewx
> #Group=weewx
>
> [Install]
> WantedBy=multi-user.target
>
>
> El miércoles, 10 de abril de 2024 a las 19:46:01 UTC+2, vince escribió:
>
>> Check to see if you have multiple weewx.service files on your system. 
>>  It's possible you have one under /etc and a different one under /usr and 
>> systemd is using the old one.
>>
>> If that is not the case, post your /etc/systemd/system/weewx.service file 
>> please.
>>
>> On Wednesday, April 10, 2024 at 10:42:39 AM UTC-7 Juan Antonio Mosquera 
>> Casais wrote:
>>
>>> Thanks... but... step 4 done> 
>>>
>>> history
>>>
>>>  1323  sudo cp /home/weewx/util/systemd/weewx.service /etc/systemd/system
>>>  1324  sudo systemctl daemon-reload
>>>  1325  sudo systemctl enable weewx
>>>  1326  sudo systemctl start weewx
>>>
>>>
>>>
>>>
>>>
>>> El miércoles, 10 de abril de 2024 a las 13:16:55 UTC+2, Tom Keffer 
>>> escribió:
>>>
>>>> You did not update your weewx service file, 
>>>> /etc/systemd/system/weewx.service. This is step #4 in the instructions. 
>>>>
>>>>
>>>>
>>>> On Wed, Apr 10, 2024 at 1:05 AM Juan Antonio Mosquera Casais <
>>>> juan.antonio.m...@gmail.com> wrote:
>>>>
>>>>> Hello, I have weewx 4.10.2 installed via setup.py, and I followed the 
>>>>> instructions at https://github.com/weewx/weewx/wiki/v5-upgrade but 
>>>>> when trying to start the service I get this error:
>>>>>
>>>>> Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed to 
>>>>> locate executable /home/weewx/bin/weewxd: No such file or directory
>>>>> Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed at 
>>>>> step EXEC spawning /home/weewx/bin/weewxd: No such file or directory
>>>>> Apr 10 07:39:51 raspberrypi systemd[1]: Started WeeWX weather system.
>>>>> Apr 10 07:39:51 raspberrypi systemd[1]: weewx.service: Main process 
>>>>> exited, code=exited, status=203/EXEC
>>>>> Apr 10 07:39:51 raspberrypi systemd[1]: weewx.service: Failed with 
>>>>> result 'exit-code'.
>>>>>
>>>>> It is because in the instructions the bin has to be moved to bin.old, 
>>>>> if I put the bin back it works, but with version 4.10.2. How can I update 
>>>>> to version 5.0.2 and keep my old configuration? Thank you. 
>>>>>
>>>>> -- 
>>>>> 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+...@googlegroups.com.
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/weewx-user/689f6dd3-1de9-4d6b-90b2-1c7fc0b36fc7n%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/weewx-user/689f6dd3-1de9-4d6b-90b2-1c7fc0b36fc7n%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>>

-- 
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/9ac549b4-1f5e-4cfc-9f5c-afb7968316a6n%40googlegroups.com.

Re: [weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

[vince]

Check to see if you have multiple weewx.service files on your system.  It's 
possible you have one under /etc and a different one under /usr and systemd 
is using the old one.

If that is not the case, post your /etc/systemd/system/weewx.service file 
please.

On Wednesday, April 10, 2024 at 10:42:39 AM UTC-7 Juan Antonio Mosquera 
Casais wrote:

> Thanks... but... step 4 done> 
>
> history
>
>  1323  sudo cp /home/weewx/util/systemd/weewx.service /etc/systemd/system
>  1324  sudo systemctl daemon-reload
>  1325  sudo systemctl enable weewx
>  1326  sudo systemctl start weewx
>
>
>
>
>
> El miércoles, 10 de abril de 2024 a las 13:16:55 UTC+2, Tom Keffer 
> escribió:
>
>> You did not update your weewx service file, 
>> /etc/systemd/system/weewx.service. This is step #4 in the instructions. 
>>
>>
>>
>> On Wed, Apr 10, 2024 at 1:05 AM Juan Antonio Mosquera Casais <
>> juan.antonio.m...@gmail.com> wrote:
>>
>>> Hello, I have weewx 4.10.2 installed via setup.py, and I followed the 
>>> instructions at https://github.com/weewx/weewx/wiki/v5-upgrade but when 
>>> trying to start the service I get this error:
>>>
>>> Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed to 
>>> locate executable /home/weewx/bin/weewxd: No such file or directory
>>> Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed at step 
>>> EXEC spawning /home/weewx/bin/weewxd: No such file or directory
>>> Apr 10 07:39:51 raspberrypi systemd[1]: Started WeeWX weather system.
>>> Apr 10 07:39:51 raspberrypi systemd[1]: weewx.service: Main process 
>>> exited, code=exited, status=203/EXEC
>>> Apr 10 07:39:51 raspberrypi systemd[1]: weewx.service: Failed with 
>>> result 'exit-code'.
>>>
>>> It is because in the instructions the bin has to be moved to bin.old, if 
>>> I put the bin back it works, but with version 4.10.2. How can I update to 
>>> version 5.0.2 and keep my old configuration? Thank you. 
>>>
>>> -- 
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/689f6dd3-1de9-4d6b-90b2-1c7fc0b36fc7n%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/ba5a4d52-a21d-4820-ad13-01051f88df47n%40googlegroups.com.

Re: [weewx-user] Re: Unexpected weewx stop: ERROR weewx.engine: Import of driver failed

[vince]

Cool - thanks.   Would it be possible to add the log.info() to always log 
its settings ?  That might make some more "did you set this true" support 
threads a little quicker.

Also given Matthew is kinda out of pocket for personal/work reasons, would 
it be possible to get a 5.0.next out there for pip users ?  Or does the 
to-do list include code as well as packaging things ?

On Tuesday, April 9, 2024 at 4:58:52 PM UTC-7 Tom Keffer wrote:

> Yes, there was a bug, but it was fixed by Gary back in February. PR #935 
> <https://github.com/weewx/weewx/pull/935>. To appear whenever we get a 
> new version out.
>
> -tk
>
>
> On Tue, Apr 9, 2024 at 4:22 PM vince  wrote:
>
>> I was thinking systemd would be a more general purpose way, but maybe 
>> that's just frustration here with loop_on_init not working.
>>
>> In poking around more I think there's a bug in weewxd.py - I can't find 
>> an incantation that actually sets loop_on_init to what's set in the .conf 
>> file.  I added some log.info around the statements in weewxd.py and it 
>> always gets set False no matter what I do.
>>
>> This patch works though...
>>
>> #-
>> ###
>> #### If no command line --loop-on-init was specified, look in the 
>> config file.
>> ###if namespace.loop_on_init is None:
>> ###loop_on_init = to_bool(config_dict.get('loop_on_init', False))
>> ###else:
>> ###loop_on_init = namespace.loop_on_init
>> ###
>> #-
>>
>> # If command line --loop-on-init was specified use that
>> if namespace.loop_on_init is True:
>> loop_on_init = namespace.loop_on_init
>> else:
>> # look in the config file, failing safe to False
>>  loop_on_init = to_bool(config_dict.get('loop_on_init', False))
>>
>> # always log its setting
>> log.info("loop_on_init: %s", loop_on_init)
>>
>> #-
>>
>>
>> On Tuesday, April 9, 2024 at 2:55:32 PM UTC-7 gjr80 wrote:
>>
>>> The more I think of it the more I don't see the benefit of this approach 
>>> over using loop_on_init in weewx.conf in dealing with this type of 
>>> problem. Setting loop_on_init = True will cause WeeWX to reload the 
>>> driver after (the default) three consecutive attempts to contact the 
>>> gateway device fail; WeeWX continues running the entire time. Perhaps if 
>>> some sort of network or device initialisation sat in the WeeWX core there 
>>> might be a benefit, but all of that sits solely in the driver (as far as I 
>>> am aware this is the case with all drivers). If the network or the device 
>>> is in such a state that communication with the device via the API is not 
>>> possible then no amount of WeeWX restarts or driver reloads will correct 
>>> the situation.
>>>
>>> It seems to me that forcing a WeeWX restart via systemd is a somewhat 
>>> heavy handed approach.
>>>
>>> My opinion only and I expect others will have a different view.
>>>
>>> Gary 
>>>
>>> On Wednesday 10 April 2024 at 06:00:37 UTC+10 vince wrote:
>>>
>>>> update - my ecowitt instance crashed out on me during a several minute 
>>>> network outage while I was updating firmware on the router/switch/ap so 
>>>> I'm 
>>>> trying this solution to see how well that works.  Thanks.
>>>>
>>>> (not a bug in the gw1000 driver - it did exactly what it's configured 
>>>> to do.  It tried 3x with 2 sec in between.  An alternate workaround would 
>>>> be to try 1000x with a minute in between to basically get through any 
>>>> reasonable network outages for the LAN, but I want to try the systemd 
>>>> method as a more generic fix)
>>>>
>>>> On Tuesday, March 26, 2024 at 7:56:12 AM UTC-7 gary@gmail.com 
>>>> wrote:
>>>>
>>>>> I have added these lines to my weewx service file for just such an 
>>>>> instance.
>>>>> Add under StandardError=journal+console entry in the [Service] stanza
>>>>>
>>>>> Restart=on-failure
>>>>> RestartSec=30
>>>>>
>>>>> Restarts weewx after waiting for 30 seconds to allow whatever 
>>>>> interfered to (hopefully) clear.
>>>>>
>>>>> On Monday, March 25, 2024 at 6:26:44 PM UTC-4 vince wrote:
>>>>>
>>>>>> Perhaps this setting (link) 
>>>>>> <https://unix.stackexchange.com/questions/564443/what

[weewx-user] Re: Unexpected weewx stop: ERROR weewx.engine: Import of driver failed

[vince]

I was thinking systemd would be a more general purpose way, but maybe 
that's just frustration here with loop_on_init not working.

In poking around more I think there's a bug in weewxd.py - I can't find an 
incantation that actually sets loop_on_init to what's set in the .conf 
file.  I added some log.info around the statements in weewxd.py and it 
always gets set False no matter what I do.

This patch works though...

#-
###
#### If no command line --loop-on-init was specified, look in the 
config file.
###if namespace.loop_on_init is None:
###loop_on_init = to_bool(config_dict.get('loop_on_init', False))
###else:
###loop_on_init = namespace.loop_on_init
###
#-

# If command line --loop-on-init was specified use that
if namespace.loop_on_init is True:
loop_on_init = namespace.loop_on_init
else:
# look in the config file, failing safe to False
 loop_on_init = to_bool(config_dict.get('loop_on_init', False))

# always log its setting
log.info("loop_on_init: %s", loop_on_init)

#-


On Tuesday, April 9, 2024 at 2:55:32 PM UTC-7 gjr80 wrote:

> The more I think of it the more I don't see the benefit of this approach 
> over using loop_on_init in weewx.conf in dealing with this type of 
> problem. Setting loop_on_init = True will cause WeeWX to reload the 
> driver after (the default) three consecutive attempts to contact the 
> gateway device fail; WeeWX continues running the entire time. Perhaps if 
> some sort of network or device initialisation sat in the WeeWX core there 
> might be a benefit, but all of that sits solely in the driver (as far as I 
> am aware this is the case with all drivers). If the network or the device 
> is in such a state that communication with the device via the API is not 
> possible then no amount of WeeWX restarts or driver reloads will correct 
> the situation.
>
> It seems to me that forcing a WeeWX restart via systemd is a somewhat 
> heavy handed approach.
>
> My opinion only and I expect others will have a different view.
>
> Gary 
>
> On Wednesday 10 April 2024 at 06:00:37 UTC+10 vince wrote:
>
>> update - my ecowitt instance crashed out on me during a several minute 
>> network outage while I was updating firmware on the router/switch/ap so I'm 
>> trying this solution to see how well that works.  Thanks.
>>
>> (not a bug in the gw1000 driver - it did exactly what it's configured to 
>> do.  It tried 3x with 2 sec in between.  An alternate workaround would be 
>> to try 1000x with a minute in between to basically get through any 
>> reasonable network outages for the LAN, but I want to try the systemd 
>> method as a more generic fix)
>>
>> On Tuesday, March 26, 2024 at 7:56:12 AM UTC-7 gary@gmail.com wrote:
>>
>>> I have added these lines to my weewx service file for just such an 
>>> instance.
>>> Add under StandardError=journal+console entry in the [Service] stanza
>>>
>>> Restart=on-failure
>>> RestartSec=30
>>>
>>> Restarts weewx after waiting for 30 seconds to allow whatever interfered 
>>> to (hopefully) clear.
>>>
>>> On Monday, March 25, 2024 at 6:26:44 PM UTC-4 vince wrote:
>>>
>>>> Perhaps this setting (link) 
>>>> <https://unix.stackexchange.com/questions/564443/what-does-restart-on-abort-mean-in-a-systemd-service>
>>>>  is 
>>>> something to try if you want to experiment and let us know if it works…
>>>>
>>>> On Monday, March 25, 2024 at 3:11:41 PM UTC-7 Thomas Hackler wrote:
>>>>
>>>>> thank you for the answer, then it was maybe soemthing wrong with the 
>>>>> wifi
>>>>>
>>>>> does it make sense to increase the attempts before exit ?
>>>>>
>>>>> I try to find something to check if the process is running
>>>>> I have some experience with monit, so maybe I find an example or 
>>>>> anything else
>>>>>
>>>>>
>>>>> vince schrieb am Montag, 25. März 2024 um 22:09:58 UTC+1:
>>>>>
>>>>>> I have also seen my gw1000 weewx setup abort on the pi4 occasionally 
>>>>>> when the wifi network bounces for some reason.  Mine's been up for 6 
>>>>>> weeks 
>>>>>> now so it is definitely a transient kind of thing.
>>>>>>
>>>>>> Writing yourself a little cron job to look for the weewxd process and 
>>>>>> if it's not there restart it wouldn't be too tough to do.   Perhaps 
>>>>>> there 
>>>>>> is s

[weewx-user] Re: Unexpected weewx stop: ERROR weewx.engine: Import of driver failed

[vince]

update - my ecowitt instance crashed out on me during a several minute 
network outage while I was updating firmware on the router/switch/ap so I'm 
trying this solution to see how well that works.  Thanks.

(not a bug in the gw1000 driver - it did exactly what it's configured to 
do.  It tried 3x with 2 sec in between.  An alternate workaround would be 
to try 1000x with a minute in between to basically get through any 
reasonable network outages for the LAN, but I want to try the systemd 
method as a more generic fix)

On Tuesday, March 26, 2024 at 7:56:12 AM UTC-7 gary@gmail.com wrote:

> I have added these lines to my weewx service file for just such an 
> instance.
> Add under StandardError=journal+console entry in the [Service] stanza
>
> Restart=on-failure
> RestartSec=30
>
> Restarts weewx after waiting for 30 seconds to allow whatever interfered 
> to (hopefully) clear.
>
> On Monday, March 25, 2024 at 6:26:44 PM UTC-4 vince wrote:
>
>> Perhaps this setting (link) 
>> <https://unix.stackexchange.com/questions/564443/what-does-restart-on-abort-mean-in-a-systemd-service>
>>  is 
>> something to try if you want to experiment and let us know if it works…
>>
>> On Monday, March 25, 2024 at 3:11:41 PM UTC-7 Thomas Hackler wrote:
>>
>>> thank you for the answer, then it was maybe soemthing wrong with the wifi
>>>
>>> does it make sense to increase the attempts before exit ?
>>>
>>> I try to find something to check if the process is running
>>> I have some experience with monit, so maybe I find an example or 
>>> anything else
>>>
>>>
>>> vince schrieb am Montag, 25. März 2024 um 22:09:58 UTC+1:
>>>
>>>> I have also seen my gw1000 weewx setup abort on the pi4 occasionally 
>>>> when the wifi network bounces for some reason.  Mine's been up for 6 weeks 
>>>> now so it is definitely a transient kind of thing.
>>>>
>>>> Writing yourself a little cron job to look for the weewxd process and 
>>>> if it's not there restart it wouldn't be too tough to do.   Perhaps there 
>>>> is some systemd configuration magic that is possible, but I'm not sure 
>>>> there what a safe+effective way to leverage systemd would look like.  I 
>>>> know how cron works :-)
>>>>
>>>> On Monday, March 25, 2024 at 1:56:10 PM UTC-7 Thomas Hackler wrote:
>>>>
>>>>> Hello,
>>>>> my weewx stopped yesterday unexpected. The last logs are attached. It 
>>>>> ran stable for over 1 week. I have restarts of my raspberry pi with cron 
>>>>> every 1 or 2 days. What is the reason that the gw1000 driver has suddenly 
>>>>> a 
>>>>> problem? How can I avoid it in future? Should I increase the attemps if 
>>>>> there is a short problem with the wifi connection?
>>>>> It is a problem of my gw1000 device? I see no problems with the 
>>>>> ecowitt app.
>>>>> Thank you!
>>>>> Regards
>>>>> Thomas
>>>>>
>>>>

-- 
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/86de5170-efec-40a3-91ae-56b184117179n%40googlegroups.com.

[weewx-user] obligatory eclipse thread

[vince]

Having seen the 2017 total eclipse after a 4-hour drive south to below 
Portland OR, I highly recommend finding a way to see this one if you have 
the opportunity.  It is truly an amazing amazing experience you will 
absolutely never forget.  The diamond ring is sooo incredible.   
Temperatures dropped 20F at totality and everything turned the strangest 
colors as totality approached.  Beyond cool.

Lets see your solar sensor graphs too 

-- 
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/48463a5e-de3c-4ee3-b8bf-b91120ab4107n%40googlegroups.com.

[weewx-user] Re: After a power loss three days ago, graphs do not update but current data and day's statistic are valid.

[vince]

Standard answer applies.  Set debug=1, restart weewx, and provide logs 
through 'two' archive periods.

On Sunday, April 7, 2024 at 2:53:27 PM UTC-7 Sylvain Gagnon wrote:

> Hi, like the subject says, after a power loss three days ago, graphs do 
> not update but current data and day's statistics is valid. Is there a way 
> to force a refresh of the graphs? Running WeeWX 4.10.2.
>

-- 
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/8a195acc-ea16-48cb-9b5c-2c48ec06f18fn%40googlegroups.com.

Re: [weewx-user] Re: Exclude list or Overwrite behaviour for RSync Report

[vince]

Agree that one way to do it would be ideal, unless there are backward 
compatibility reasons to leave the current switches 'also' valid.  I guess 
it would be possible to tear apart a hypothetical rsync_options="whatever 
here" string to not break folks, but I didn't want to write the code this 
time, just suggest where it might be doable to at least think about as a 
feature addition.

On Tuesday, April 2, 2024 at 4:08:26 PM UTC-7 John Kline wrote:

> The problem with an rsync_options (similar to the existing ssh_options) is 
> that the code already has rsync options specified individually (e.g., 
> delete and compress).  It would be messy to have two ways to specify delete 
> and compress.
>
> It might be best to add an explicit exclude option.  BTW, exclude can be 
> specified multiple times, so the value should be an array.
>
> On Apr 2, 2024, at 11:56 AM, Chris Alemany  wrote:
>
> Hmm, both strategies have advantages. It'd be great if weewx had the 
> ability to add in rsync options so that if you just wanted to do a single 
> thing, exclude a directory, or maybe conform to a specific non-standard 
> setting on the remote host, then you can easily do that in weewx.
>
>
> The extension is nice to have to create a full suite of rsync options so 
> people can use it to backup stuff, move stuff, etc.
>
> I've created a GitHub issue/request
> https://github.com/weewx/weewx/issues/951
>
> Thanks to you both.
> Chris
> On Tuesday, April 2, 2024 at 8:30:30 AM UTC-7 vince wrote:
>
>> Seems complicated.  
>>
>> I was suggesting something like adding a general purpose 'rsync_options' 
>> variable in that section of weewx.conf, and adding the value  to the 
>> assembled rsync command in the run(self) routine in rsyncupload.py ? 
>> Then the user could add any combination of the rsync options to the command 
>> if needed.   Perhaps something like the following (untested):
>>
>> pi@pi4:/tmp$ diff rsyncupload.py.orig rsyncupload.py -u
>> --- rsyncupload.py.orig 2024-04-02 08:18:48.311469290 -0700
>> +++ rsyncupload.py 2024-04-02 08:19:57.970078706 -0700
>> @@ -46,6 +46,7 @@
>>  self.delete = delete
>>  self.port = port
>>  self.ssh_options = ssh_options
>> +self.rsync_options = rsync_options   # <== new
>>  self.compress = compress
>>  self.log_success = log_success
>>  self.log_failure = log_failure
>> @@ -96,6 +97,7 @@
>>  if self.timeout is not None:
>>  cmd.extend(["--timeout=%s" % self.timeout])
>>  cmd.extend(["-e"])
>> +cmd.extend([rsync_options])# <=== new
>>  cmd.extend([rsyncsshstring])
>>  cmd.extend([rsynclocalspec])
>>  cmd.extend([rsyncremotespec])
>>
>> And add a rsync_options = "whatever you want here" to the [[RSYNC]] 
>> section in weewx.conf ala:
>>
>>[[RSYNC]]
>> delete = 0
>> skin = Rsync
>> enable = true
>> server = x.x.x.x 
>> user = myremoteuser
>> path = /my/remote/path/here
>> log_success = true
>> log_failure = true
>> rsync_options = "-x -y -z whatever"   # <=== new
>>
>> Disclaimer - totally untested and no idea if there are security risks of 
>> doing it this way, but it would seem to be about as flexible as you can get 
>> toward supporting whatever rsync options the underlying os supports with a 
>> minimum of change to the existing uploader
>>
>> On Tuesday, April 2, 2024 at 1:17:58 AM UTC-7 Glenn McKechnie wrote:
>>
>>> On Tue, 2 Apr 2024 at 15:00, Chris Alemany  wrote:
>>>
>>>> Thanks for the hints Vince. I ended up looking through the old Wiki and 
>>>> came upon this page about backing up databases with the rsync report and 
>>>> how you can spit rsync into multiple skins.
>>>>
>>>>
>>>> https://github.com/weewx/weewx/wiki/Using-the-RSYNC-skin-as-a-backup-solution
>>>>
>>>
>>> That was a good solution for a while, until - like you - I wanted more.
>>>
>>> I eventually pulled the rsyncupload.py code from the main tree and 
>>> stuffed it into a skin.
>>> The following was written a while ago. I still use it as is, but it's 
>>> rough and untidy.  Really does need a clean up but I haven't and still 
>>> don't have the time do that, so you get it warts and all...
>>>
>>> https://github.com/glennmckechnie/weewx-rsynctransfer
>>>
>>> It shou

[weewx-user] Re: New 5.0.2 Installation - SystemCtl can't start it, invalid argument

[vince]

Try running this to see what's whereyou might have old versions sitting 
around...

This is from a clean dpkg deb12 installation with no previous versions 
there

$ sudo find / -name weewx.service  -exec ls -lgd {} \; 2>/dev/null | sort +7
lrwxrwxrwx 1 root   33 Apr  2 12:04 
/etc/systemd/system/multi-user.target.wants/weewx.service -> 
/lib/systemd/system/weewx.service
-rw-rw-r-- 1 weewx 424 Feb  9 23:03 /etc/weewx/systemd/weewx.service
drwxr-xr-x 2 root0 Apr  2 15:07 
/sys/fs/cgroup/system.slice/weewx.service
-rw-r--r-- 1 root  424 Apr  2 12:04 /usr/lib/systemd/system/weewx.service
-rw-r--r-- 1 root  417 Feb  9 23:03 
/usr/share/weewx/weewx_data/util/systemd/weewx.service

(I added a few spaces to the output above for readability)

On Tuesday, April 2, 2024 at 2:02:07 PM UTC-7 crecre9 wrote:

> That's what my service file looked like. i was getting the error saying 
> the path wasn't absolute, so i removed the "weewxd" portion from the 
> ExecStart line, but as i mentioned, i don't have any idea how to fix that 
> file. I have no idea why it wouldn't work out of the box either. The only 
> thing i can think of is the removal of older versions of weewx were 
> incomplete somehow and is somehow interfering.
>
> On Tuesday, April 2, 2024 at 2:18:26 PM UTC-5 vince wrote:
>
>> Are you running an unusual os on the pi ?
>>  Did you do something to edit the weewx.service file ?
>>
>>  A clean pi running raspios installs+works just fine here with the 
>> apt-get dpkg.
>> The vanilla service file looks like:
>>
>> pi@raspberrypi:~ $ cat /usr/lib/systemd/system/weewx.service
>> # systemd service configuration file for WeeWX
>>
>> [Unit]
>> Description=WeeWX
>> Documentation=https://weewx.com/docs
>> Requires=time-sync.target
>> After=time-sync.target
>> Wants=network-online.target
>> After=network-online.target
>>
>> [Service]
>> ExecStart=weewxd /etc/weewx/weewx.conf
>> StandardOutput=null
>> StandardError=journal+console
>> RuntimeDirectory=weewx
>> RuntimeDirectoryMode=775
>> User=weewx
>> Group=weewx
>>
>> [Install]
>> WantedBy=multi-user.target
>>
>> On Tuesday, April 2, 2024 at 11:50:36 AM UTC-7 crecre9 wrote:
>>
>>> I have a fresh 5.0.2 install using apt-get. The program won't run as a 
>>> service:
>>>
>>> ● weewx.service - WeeWX
>>>Loaded: loaded (/etc/systemd/system/weewx.service; enabled; vendor 
>>> preset: en
>>>Active: failed (Result: exit-code) since Tue 2024-04-02 13:26:02 -05; 
>>> 1min 2s
>>>  Docs: https://weewx.com/docs
>>>   Process: 2178 ExecStart=/etc/weewx/weewx.conf (code=exited, 
>>> status=203/EXEC)
>>>  Main PID: 2178 (code=exited, status=203/EXEC)
>>>
>>> Apr 02 13:26:02 rpi systemd[1]: Started WeeWX.
>>> Apr 02 13:26:02 rpi systemd[1]: weewx.service: Main process exited, 
>>> code=exited,
>>> Apr 02 13:26:02 rpi systemd[1]: weewx.service: Unit entered failed state.
>>> Apr 02 13:26:02 rpi systemd[1]: weewx.service: Failed with result 
>>> 'exit-code'.
>>>
>>> And when I look at status:
>>>
>>> Apr 02 13:28:28 rpi systemd[1]: 
>>> [/usr/lib/systemd/system/weewx.service:12] Executable path is not absolute, 
>>> ignoring: weewxd /etc/weewx/weewx.conf
>>> Apr 02 13:28:28 rpi systemd[1]: weewx.service: Service lacks both 
>>> ExecStart= and ExecStop= setting. Refusing.
>>>
>>>
>>> Any ideas? Its like the installation files improperly set up the daemon 
>>> service.
>>>
>>>
>>> -Joseph
>>>
>>

-- 
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/f32b17bf-46e4-4f3b-bec6-e350c7249283n%40googlegroups.com.

[weewx-user] Re: New 5.0.2 Installation - SystemCtl can't start it, invalid argument

[vince]

Me too but no issues.  All I can suggest is editing the service file as it 
seems to be asking you to do.  Can't explain why.

On Tuesday, April 2, 2024 at 1:45:16 PM UTC-7 crecre9 wrote:

> No, just raspbian. A more recent release.
>
> On Tuesday, April 2, 2024 at 2:18:26 PM UTC-5 vince wrote:
>
>> Are you running an unusual os on the pi ?
>>  Did you do something to edit the weewx.service file ?
>>
>>  A clean pi running raspios installs+works just fine here with the 
>> apt-get dpkg.
>> The vanilla service file looks like:
>>
>> pi@raspberrypi:~ $ cat /usr/lib/systemd/system/weewx.service
>> # systemd service configuration file for WeeWX
>>
>> [Unit]
>> Description=WeeWX
>> Documentation=https://weewx.com/docs
>> Requires=time-sync.target
>> After=time-sync.target
>> Wants=network-online.target
>> After=network-online.target
>>
>> [Service]
>> ExecStart=weewxd /etc/weewx/weewx.conf
>> StandardOutput=null
>> StandardError=journal+console
>> RuntimeDirectory=weewx
>> RuntimeDirectoryMode=775
>> User=weewx
>> Group=weewx
>>
>> [Install]
>> WantedBy=multi-user.target
>>
>> On Tuesday, April 2, 2024 at 11:50:36 AM UTC-7 crecre9 wrote:
>>
>>> I have a fresh 5.0.2 install using apt-get. The program won't run as a 
>>> service:
>>>
>>> ● weewx.service - WeeWX
>>>Loaded: loaded (/etc/systemd/system/weewx.service; enabled; vendor 
>>> preset: en
>>>Active: failed (Result: exit-code) since Tue 2024-04-02 13:26:02 -05; 
>>> 1min 2s
>>>  Docs: https://weewx.com/docs
>>>   Process: 2178 ExecStart=/etc/weewx/weewx.conf (code=exited, 
>>> status=203/EXEC)
>>>  Main PID: 2178 (code=exited, status=203/EXEC)
>>>
>>> Apr 02 13:26:02 rpi systemd[1]: Started WeeWX.
>>> Apr 02 13:26:02 rpi systemd[1]: weewx.service: Main process exited, 
>>> code=exited,
>>> Apr 02 13:26:02 rpi systemd[1]: weewx.service: Unit entered failed state.
>>> Apr 02 13:26:02 rpi systemd[1]: weewx.service: Failed with result 
>>> 'exit-code'.
>>>
>>> And when I look at status:
>>>
>>> Apr 02 13:28:28 rpi systemd[1]: 
>>> [/usr/lib/systemd/system/weewx.service:12] Executable path is not absolute, 
>>> ignoring: weewxd /etc/weewx/weewx.conf
>>> Apr 02 13:28:28 rpi systemd[1]: weewx.service: Service lacks both 
>>> ExecStart= and ExecStop= setting. Refusing.
>>>
>>>
>>> Any ideas? Its like the installation files improperly set up the daemon 
>>> service.
>>>
>>>
>>> -Joseph
>>>
>>

-- 
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/d5bacc47-ad3f-4150-aba0-48699cdce03an%40googlegroups.com.

[weewx-user] Re: New 5.0.2 Installation - SystemCtl can't start it, invalid argument

[vince]

Are you running an unusual os on the pi ?
 Did you do something to edit the weewx.service file ?

 A clean pi running raspios installs+works just fine here with the apt-get 
dpkg.
The vanilla service file looks like:

pi@raspberrypi:~ $ cat /usr/lib/systemd/system/weewx.service
# systemd service configuration file for WeeWX

[Unit]
Description=WeeWX
Documentation=https://weewx.com/docs
Requires=time-sync.target
After=time-sync.target
Wants=network-online.target
After=network-online.target

[Service]
ExecStart=weewxd /etc/weewx/weewx.conf
StandardOutput=null
StandardError=journal+console
RuntimeDirectory=weewx
RuntimeDirectoryMode=775
User=weewx
Group=weewx

[Install]
WantedBy=multi-user.target

On Tuesday, April 2, 2024 at 11:50:36 AM UTC-7 crecre9 wrote:

> I have a fresh 5.0.2 install using apt-get. The program won't run as a 
> service:
>
> ● weewx.service - WeeWX
>Loaded: loaded (/etc/systemd/system/weewx.service; enabled; vendor 
> preset: en
>Active: failed (Result: exit-code) since Tue 2024-04-02 13:26:02 -05; 
> 1min 2s
>  Docs: https://weewx.com/docs
>   Process: 2178 ExecStart=/etc/weewx/weewx.conf (code=exited, 
> status=203/EXEC)
>  Main PID: 2178 (code=exited, status=203/EXEC)
>
> Apr 02 13:26:02 rpi systemd[1]: Started WeeWX.
> Apr 02 13:26:02 rpi systemd[1]: weewx.service: Main process exited, 
> code=exited,
> Apr 02 13:26:02 rpi systemd[1]: weewx.service: Unit entered failed state.
> Apr 02 13:26:02 rpi systemd[1]: weewx.service: Failed with result 
> 'exit-code'.
>
> And when I look at status:
>
> Apr 02 13:28:28 rpi systemd[1]: [/usr/lib/systemd/system/weewx.service:12] 
> Executable path is not absolute, ignoring: weewxd /etc/weewx/weewx.conf
> Apr 02 13:28:28 rpi systemd[1]: weewx.service: Service lacks both 
> ExecStart= and ExecStop= setting. Refusing.
>
>
> Any ideas? Its like the installation files improperly set up the daemon 
> service.
>
>
> -Joseph
>

-- 
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/2cfd6ded-cf91-48bc-8431-74ec8342476an%40googlegroups.com.

[weewx-user] Re: Permissions problems /var/www/html/weewx after running weectl report run

[vince]

Try setting your umask for the meteo account perhaps ?

Once the files are generated initially would user meteo ever need to run 
weectl report again ?
On Tuesday, April 2, 2024 at 9:53:48 AM UTC-7 jterr...@gmail.com wrote:

> I forgot to say that I installed weewx according to 
> http://www.weewx.com/docs/5.0/quickstarts/debian/   on  Debian GNU/Linux 
> 12 (bookworm)
>
>
>
>

-- 
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/def7856b-c187-4a5a-a58a-4a9002e32959n%40googlegroups.com.

Re: [weewx-user] Re: Exclude list or Overwrite behaviour for RSync Report

[vince]

Seems complicated.  

I was suggesting something like adding a general purpose 'rsync_options' 
variable in that section of weewx.conf, and adding the value  to the 
assembled rsync command in the run(self) routine in rsyncupload.py ? 
Then the user could add any combination of the rsync options to the command 
if needed.   Perhaps something like the following (untested):

pi@pi4:/tmp$ diff rsyncupload.py.orig rsyncupload.py -u
--- rsyncupload.py.orig 2024-04-02 08:18:48.311469290 -0700
+++ rsyncupload.py 2024-04-02 08:19:57.970078706 -0700
@@ -46,6 +46,7 @@
 self.delete = delete
 self.port = port
 self.ssh_options = ssh_options
+self.rsync_options = rsync_options   # <== new
 self.compress = compress
 self.log_success = log_success
 self.log_failure = log_failure
@@ -96,6 +97,7 @@
 if self.timeout is not None:
 cmd.extend(["--timeout=%s" % self.timeout])
 cmd.extend(["-e"])
+cmd.extend([rsync_options])# <=== new
 cmd.extend([rsyncsshstring])
 cmd.extend([rsynclocalspec])
 cmd.extend([rsyncremotespec])

And add a rsync_options = "whatever you want here" to the [[RSYNC]] section 
in weewx.conf ala:

   [[RSYNC]]
delete = 0
skin = Rsync
enable = true
server = x.x.x.x 
user = myremoteuser
path = /my/remote/path/here
log_success = true
log_failure = true
rsync_options = "-x -y -z whatever"   # <=== new

Disclaimer - totally untested and no idea if there are security risks of 
doing it this way, but it would seem to be about as flexible as you can get 
toward supporting whatever rsync options the underlying os supports with a 
minimum of change to the existing uploader

On Tuesday, April 2, 2024 at 1:17:58 AM UTC-7 Glenn McKechnie wrote:

> On Tue, 2 Apr 2024 at 15:00, Chris Alemany  wrote:
>
>> Thanks for the hints Vince. I ended up looking through the old Wiki and 
>> came upon this page about backing up databases with the rsync report and 
>> how you can spit rsync into multiple skins.
>>
>>
>> https://github.com/weewx/weewx/wiki/Using-the-RSYNC-skin-as-a-backup-solution
>>
>
> That was a good solution for a while, until - like you - I wanted more.
>
> I eventually pulled the rsyncupload.py code from the main tree and stuffed 
> it into a skin.
> The following was written a while ago. I still use it as is, but it's 
> rough and untidy.  Really does need a clean up but I haven't and still 
> don't have the time do that, so you get it warts and all...
>
> https://github.com/glennmckechnie/weewx-rsynctransfer
>
> It should install  *Gulp*, it should be self explanatory *Gulp* 
> There are plenty of notes and examples in it that show it can handle the 
> additional rsync command line options.
>
> my email address is in the code, there's the  issues tab on github and I 
> always read this group.
>
> Cheers
>  Glenn
>
> Various WeeWx addons at
> https://github.com/glennmckechnie
>

-- 
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/9e03b8fc-ae0d-4eb2-9e10-c32da5f80e88n%40googlegroups.com.

Re: [weewx-user] Re: New install rtldavis & weewx 5

[vince]

No - I don't think multiple rtldavis processes are normal.  Mine only shows 
one.

pi@pi5:~ $ sudo systemctl status weewx
● weewx.service - WeeWX weather system
 Loaded: loaded (/etc/systemd/system/weewx.service; enabled; preset: 
enabled)
 Active: active (running) since Mon 2024-04-01 13:47:45 PDT; 2min 17s 
ago
   Docs: https://weewx.com/docs
   Main PID: 871 (python3)
  Tasks: 14 (limit: 4388)
CPU: 5.050s
 CGroup: /system.slice/weewx.service
 ├─871 /home/pi/weewx-venv/bin/python3 
/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py 
/home/pi/weewx-data/weewx.conf
 └─911 /home/pi/work/bin/rtldavis -tf US -tr 1

Apr 01 13:47:46 pi5 weewxd[871]: DEBUG user.rtldavis: info: 13:47:45.728787 
BlockSize: 512
Apr 01 13:47:46 pi5 weewxd[871]: DEBUG user.rtldavis: info: 13:47:45.728790 
BufferLength: 2048
Apr 01 13:47:46 pi5 weewxd[871]: DEBUG user.rtldavis: info: Detached kernel 
driver
Apr 01 13:47:46 pi5 weewxd[871]: DEBUG user.rtldavis: info: Found Rafael 
Micro R820T tuner
Apr 01 13:47:46 pi5 weewxd[871]: DEBUG user.rtldavis: info: Exact sample 
rate is: 268800.001367 Hz
Apr 01 13:47:46 pi5 weewxd[871]: DEBUG user.rtldavis: info: 13:47:46.323864 
GetTunerGain: 0 Db
Apr 01 13:47:46 pi5 weewxd[871]: DEBUG user.rtldavis: info: 13:47:46.323879 
SetFreqCorrection 0 ppm Successful
Apr 01 13:47:46 pi5 weewxd[871]: DEBUG user.rtldavis: info: Allocating 1 
zero-copy buffers
Apr 01 13:47:46 pi5 weewxd[871]: DEBUG user.rtldavis: info: 13:47:46.327138 
Init channels: wait max 135 seconds for a message of each transmitter
Apr 01 13:49:45 pi5 weewxd[871]: DEBUG user.rtldavis: info: 13:49:45.776726 
TRANSMITTER 0 SEEN

I would stop weewx and kill any rtldavis process(es) that still remain. 
 Sometimes they keep running unless you kill -9 them.

If you needed to use sudo manually then you probably need to add the weewx 
user to the correct groups to be able to attach to the rtlsdr dongle 
hardware. This might help if you wanted to give it a try.

#--- add weewx to all the groups typical 'pi' is in
# which should permit binding to non-privileged ports and typical hardware
for g in adm dialout cdrom sudo audio video plugdev games users input 
render netdev gpio i2c spi
do
  sudo usermod -aG $g weewx
done

Then 'sudo systemctl start weewx' and look at your logs for errors as 
always..

On Monday, April 1, 2024 at 1:08:06 PM UTC-7 Pierre Decamps wrote:

> Yes complete path was full.
>
> I tried adding sudo before the command in weewx.conf and it works !
>
>  
>
> Now I have two instances of rtldavis running, is it normal ?
>
>  
>
> pi@weatherpi:~/work/bin $ sudo systemctl status weewx
>
> weewx.service - WeeWX
>
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
> preset: enabled)
>
>  Active: active (running) since Mon 2024-04-01 22:05:24 CEST; 2s ago
>
>Docs: https://weewx.com/docs
>
>Main PID: 7138 (weewxd)
>
>   Tasks: 15 (limit: 1595)
>
> CPU: 1.130s
>
>  CGroup: /system.slice/weewx.service
>
>  ├─7138 /usr/bin/python3 /usr/local/bin/weewxd 
> /etc/weewx/weewx.conf
>
>  ├─7141 sudo /home/pi/work/bin/rtldavis -fc 5 -ppm 1 -tf 
> EU -tr 1
>
>  └─7144 /home/pi/work/bin/rtldavis -fc 5 -ppm 1 -tf EU -tr 
> 1
>
>  
>
> Apr 01 22:05:25 weatherpi weewxd[7138]: INFO weewx.restx: PWSweather: 
> Posting not enabled.
>
> Apr 01 22:05:25 weatherpi weewxd[7138]: INFO weewx.restx: CWOP: Posting 
> not enabled.
>
> Apr 01 22:05:25 weatherpi weewxd[7138]: INFO weewx.restx: WOW: Posting not 
> enabled.
>
> Apr 01 22:05:25 weatherpi weewxd[7138]: INFO weewx.restx: AWEKAS: Posting 
> not enabled.
>
> Apr 01 22:05:25 weatherpi weewxd[7138]: INFO weewx.engine: 'pyephem' 
> detected, extended almanac data is available
>
> Apr 01 22:05:25 weatherpi weewxd[7138]: INFO weewxd: Starting up weewx 
> version 5.0.2
>
> Apr 01 22:05:25 weatherpi weewxd[7138]: INFO weewx.engine: Using binding 
> 'wx_binding' to database 'weewx.sdb'
>
> Apr 01 22:05:25 weatherpi weewxd[7138]: INFO weewx.manager: Starting 
> backfill of daily summaries
>
> Apr 01 22:05:25 weatherpi weewxd[7138]: INFO weewx.manager: Daily 
> summaries up to date
>
> Apr 01 22:05:25 weatherpi weewxd[7138]: INFO weewx.engine: Starting main 
> packet loop.
>
>  
>
> *De : * au nom de vince 
> *Répondre à : *"weewx...@googlegroups.com" 
> *Date : *lundi 1 avril 2024 à 20:48
> *À : *weewx-user 
> *Objet : *[weewx-user] Re: New install rtldavis & weewx 5
>
>  
>
> Did you set the full path to the rtldavis binary in your weewx.conf file ? 
>
>  
>
> Mine that worked here (US) is here (link) 
> <https://github.com/vinceskahan/weewx-rtldavis/blob/main/

[weewx-user] Re: New install rtldavis & weewx 5

[vince]

Did you set the full path to the rtldavis binary in your weewx.conf file ?

Mine that worked here (US) is here (link) 
 if 
you wanted to compare with yours

On Monday, April 1, 2024 at 9:36:00 AM UTC-7 Pierre Decamps wrote:

> Hi everybody,
>
>  
>
> I installed a Davis VP2 Pro Plus Wireless last week and made a fresh 
> install of weewx and rtldavis plugin.
>
>  
>
> When I checked status of weewx, I see it :
>
>  
>
> Apr 01 18:21:31 weatherpi weewxd[2247]: INFO weewxd: Starting up weewx 
> version 5.0.2
>
> Apr 01 18:21:31 weatherpi weewxd[2247]: INFO weewx.engine: Using binding 
> 'wx_binding' to database 'weewx.sdb'
>
> Apr 01 18:21:31 weatherpi weewxd[2247]: INFO weewx.manager: Starting 
> backfill of daily summaries
>
> Apr 01 18:21:32 weatherpi weewxd[2247]: INFO weewx.manager: Daily 
> summaries up to date
>
> Apr 01 18:21:32 weatherpi weewxd[2247]: INFO weewx.engine: Starting main 
> packet loop.
>
> Apr 01 18:21:32 weatherpi weewxd[2247]: ERROR user.rtldavis: err: 
> 
>
> Apr 01 18:21:32 weatherpi weewxd[2247]: INFO weewx.engine: Main loop 
> exiting. Shutting engine down.
>
> Apr 01 18:21:33 weatherpi weewxd[2247]: INFO user.rtldavis: shutdown 
> process /home/pi/work/bin/rtldavis -fc 5 -ppm 1 -tf EU -tr 1
>
> Apr 01 18:21:33 weatherpi weewxd[2247]: CRITICAL weewxd: Caught 
> WeeWxIOError: rtldavis process is not running
>
> Apr 01 18:21:33 weatherpi weewxd[2247]: CRITICAL weewxd:   Waiting 
> 60.0 seconds then retrying...
>
>  
>
> If I start /home/weewx/bin/user/rtldavis.py
>
>  
>
> 18:25:42.266024 rtldavis.go VERSION=0.15
>
> 18:25:42.266426 tr=1 fc=5 ppm=0 gain=0 maxmissed=51 ex=0 
> receiveWindow=300 actChan=[0] maxChan=1
>
> 18:25:42.266448 undefined=false verbose=false disableAfc=false 
> deviceString=0
>
> 18:25:42.266690 BitRate: 19200
>
> 18:25:42.266708 SymbolLength: 14
>
> 18:25:42.266718 SampleRate: 268800
>
> 18:25:42.266726 Preamble: 1100101110001001
>
> 18:25:42.266734 PreambleSymbols: 16
>
> 18:25:42.266742 PreambleLength: 224
>
> 18:25:42.266750 PacketSymbols: 80
>
> 18:25:42.266758 PacketLength: 1120
>
> 18:25:42.266766 BlockSize: 512
>
> 18:25:42.266774 BufferLength: 2048
>
> Found Rafael Micro R820T tuner
>
> 18:25:42.681319 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0 
> Transmitter:0}
>
> Exact sample rate is: 268800.001367 Hz
>
> 18:25:42.854909 GetTunerGain: 0 Db
>
> 18:25:42.854949 SetFreqCorrection 0 ppm Successful
>
> 18:25:42.858456 Init channels: wait max 17 seconds for a message of each 
> transmitter
>
> Allocating 1 zero-copy buffers
>
> Traceback (most recent call last):
>
>   File "/etc/weewx/bin/user/./rtldavis.py", line 1366, in 
>
> payload = lines[0].strip()
>
> IndexError: list index out of range
>
>  
>
>  
>
> And if I start the /home/pi/work/bin/rtldavis : 
>
>  
>
> Found Rafael Micro R820T tuner
>
> 18:28:13.224537 tr=0 ch=0 freqCorr=0 lastFreqError=0, freqerrTrChList=[0 0 
> 0 0 0 0 0 0 0 0]
>
> 18:28:13.224608 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0 
> Transmitter:0}
>
> Exact sample rate is: 268800.001367 Hz
>
> 18:28:13.397912 GetTunerGain: 0 Db
>
> 18:28:13.397946 SetFreqCorrection 0 ppm Successful
>
> Allocating 1 zero-copy buffers
>
> 18:28:13.401414 Init channels: wait max 17 seconds for a message of each 
> transmitter
>
> 18:28:16.590622 m1: -0.057257 l: 224 c: 16 x: [-0.11 0.30 -0.13 -0.08 0.29 
> -0.07 -0.18 -0.16 -0.14 -0.12 -0.09 -0.08 -0.08 -0.09 -0.08 -0.08]
>
> 18:28:16.590820 TRANSMITTER 0 SEEN
>
> 18:28:16.591143 tr=0 ch=2 freqCorr=0 lastFreqError=0, freqerrTrChList=[0 0 
> 0 0 0 0 0 0 0 0]
>
> 18:28:16.591507 Hop: {ChannelIdx:2 ChannelFreq:868317250 FreqError:0 
> Transmitter:0}
>
> 18:28:16.591582 applied freqCorrection=0
>
> 18:28:19.152466 m1: -0.053535 l: 224 c: 16 x: [0.23 -0.07 0.34 -0.16 -0.16 
> -0.04 0.27 -0.12 -0.20 -0.15 -0.10 -0.10 -0.13 -0.15 -0.14 -0.16]
>
> 18:28:19.152891 5001CBFF71008375 2 0 0 0 0 msg.ID=0
>
> 18:28:19.153198 tr=0 ch=4 freqCorr=0 lastFreqError=0, freqerrTrChList=[0 0 
> 0 0 0 0 0 0 0 0]
>
> 18:28:19.153409 Hop: {ChannelIdx:4 ChannelFreq:868557250 FreqError:0 
> Transmitter:0}
>
> 18:28:19.153443 applied freqCorrection=0
>
> 18:28:21.714449 m1: -0.033016 l: 224 c: 16 x: [-0.14 0.23 0.31 0.34 -0.19 
> -0.12 0.30 -0.18 -0.11 -0.16 -0.16 -0.10 -0.09 -0.14 -0.16 -0.15]
>
> 18:28:21.714587 9000CB0701591E62 3 0 0 0 0 msg.ID=0
>
> 18:28:21.714705 tr=0 ch=1 freqCorr=0 lastFreqError=0, freqerrTrChList=[0 0 
> 0 0 0 0 0 0 0 0]
>
> 18:28:21.714798 Hop: {ChannelIdx:1 ChannelFreq:868197250 FreqError:0 
> Transmitter:0}
>
> 18:28:21.714828 applied freqCorrection=0
>
> 18:28:24.276257 m1: 0.015400 l: 224 c: 16 x: [0.02 0.37 0.37 0.37 0.33 
> 0.12 -0.19 -0.18 -0.16 -0.12 -0.10 -0.09 -0.09 -0.11 -0.14 -0.16]
>
> 18:28:24.276400 8001CB21D900CD83 4 0 0 0 0 msg.ID=0
>
> 18:28:24.276507 tr=0 ch=3 freqCorr=0 lastFreqError=0, freqerrTrChList=[0 0 
> 0 0 0 0 0 0 0 0]
>
> 18:28:24.276628 Hop: 

[weewx-user] Re: weatherflowpdp timeout

[vince]

And for others who'll run into this, what did you do ?
Did you just need to line up your actual sensor id(s) correctly to match 
your hardware ?

On Monday, April 1, 2024 at 5:41:56 AM UTC-7 Glen Briggs wrote:

> I got it going. Thank you. 
>
> Now to learn how to customize and setup things.
>
> On Sunday, March 31, 2024 at 10:28:40 PM UTC-5 vince wrote:
>
>>
>> The usual mistake is people putting in their station id (not the sensor 
>> id) or removing the leading zeroes in the sensor id. In your case you have 
>> it configured to use an air and sky original old station with both having 
>> the same id numbers which is impossible.
>>
>> AR-00091987 and.SK-00091987 are clearly incorrect.
>>
>> You might to install my wfudptools app via pip and run the listener with 
>> the —raw option to tell you your correct sensor id(s). See 
>> https://pypi.org/project/wfudptools/ which has a link to the github page 
>> for usage examples
>>
>> On Sunday, March 31, 2024 at 8:02:13 PM UTC-7 Glen Briggs wrote:
>>
>>> it appears to be running now, but i am getting nothing. no webpages, no 
>>> data, no time outs, it just does nothing
>>>
>>>
>>>
>>> 2024-03-31T21:30:54.734273-05:00 frost systemd[1]: Started weewx.service 
>>> - WeeWX.
>>> 2024-03-31T21:30:54.958929-05:00 frost weewxd[7210]: INFO __main__: 
>>> Initializing weewxd version 5.0.2
>>> 2024-03-31T21:30:54.959612-05:00 frost weewxd[7210]: INFO __main__: 
>>> Command line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>>> 2024-03-31T21:30:54.959979-05:00 frost weewxd[7210]: INFO __main__: 
>>> Using Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0]
>>> 2024-03-31T21:30:54.960361-05:00 frost weewxd[7210]: INFO __main__: 
>>> Located at /usr/bin/python3
>>> 2024-03-31T21:30:54.965927-05:00 frost weewxd[7210]: INFO __main__: 
>>> Platform Linux-6.1.0-12-686-i686-with-glibc2.36
>>> 2024-03-31T21:30:54.966200-05:00 frost weewxd[7210]: INFO __main__: 
>>> Locale: 'en_US.UTF-8'
>>> 2024-03-31T21:30:54.966522-05:00 frost weewxd[7210]: INFO __main__: 
>>> Entry path: /usr/share/weewx/weewxd.py
>>> 2024-03-31T21:30:54.966718-05:00 frost weewxd[7210]: INFO __main__: 
>>> WEEWX_ROOT: /etc/weewx
>>> 2024-03-31T21:30:54.966902-05:00 frost weewxd[7210]: INFO __main__: 
>>> Configuration file: /etc/weewx/weewx.conf
>>> 2024-03-31T21:30:54.972439-05:00 frost weewxd[7210]: INFO __main__: User 
>>> module: /etc/weewx/bin/user
>>> 2024-03-31T21:30:54.972699-05:00 frost weewxd[7210]: INFO __main__: 
>>> Debug: 1
>>> 2024-03-31T21:30:54.972902-05:00 frost weewxd[7210]: DEBUG __main__: 
>>> Initializing engine
>>> 2024-03-31T21:30:54.973165-05:00 frost weewxd[7210]: INFO weewx.engine: 
>>> Loading station type WeatherFlowUDP (user.weatherflowudp)
>>> 2024-03-31T21:30:54.978061-05:00 frost weewxd.py: weatherflowudp: 
>>> MainThread: driver version is 1.10
>>> 2024-03-31T21:30:54.978421-05:00 frost weewxd.py: weatherflowudp: 
>>> MainThread: sensor map is {'outTemp': 
>>> 'air_temperature.AR-00091987.obs_air', 'outHumidity': 
>>> 'relative_humidity.AR-00091987.obs_air', 'pressure': 
>>> 'station_pressure.AR-00091987.obs_air', 'lightning_strikes': 
>>> 'lightning_strike_count.AR-00091987.obs_air', 'avg_distance': 
>>> 'lightning_strike_avg_distance.AR-00091987.obs_air', 
>>> 'outTempBatteryStatus': 'battery.AR-00091987.obs_air', 'windSpeed': 
>>> 'wind_speed.SK-00091987.rapid_wind', 'windDir': 
>>> 'wind_direction.SK-00091987.rapid_wind', 'lux': 
>>> 'illuminance.SK-00091987.obs_sky', 'UV': 'uv.SK-00091987.obs_sky', 'rain': 
>>> 'rain_accumulated.SK-00091987.obs_sky', 'windBatteryStatus': 
>>> 'battery.SK-00091987.obs_sky', 'radiation': 
>>> 'solar_radiation.SK-00091987.obs_sky', 'lightningYYY': 
>>> 'distance.AR-00091987.evt_strike', 'lightningZZZ': 
>>> 'energy.AR-00091987.evt_strike'}
>>> 2024-03-31T21:30:54.988145-05:00 frost weewxd.py: weatherflowudp: 
>>> MainThread: *** Sensor names per packet type
>>> 2024-03-31T21:30:54.988531-05:00 frost weewxd.py: weatherflowudp: 
>>> MainThread: packet obs_air: ('time_epoch', 'station_pressure', 
>>> 'air_temperature', 'relative_humidity', 'lightning_strike_count', 
>>> 'lightning_strike_avg_distance', 'battery', 'report_interval')
>>> 2024-03-31T21:30:54.988855-05:00 frost weewxd.py: weatherflowudp: 
>>> MainThread: packet obs_sky: ('time_epoch', 'illuminance', 'uv', 
>>> 'rain_accumulated', 'win

[weewx-user] Re: weatherflowpdp timeout

[vince]

31T21:30:55.053073-05:00 frost weewxd[7210]: DEBUG weewx.engine: 
> Finished loading service weewx.restx.StdCWOP
> 2024-03-31T21:30:55.053436-05:00 frost weewxd[7210]: DEBUG weewx.engine: 
> Loading service weewx.restx.StdWOW
> 2024-03-31T21:30:55.053764-05:00 frost weewxd[7210]: INFO weewx.restx: 
> WOW: Posting not enabled.
> 2024-03-31T21:30:55.054130-05:00 frost weewxd[7210]: DEBUG weewx.engine: 
> Finished loading service weewx.restx.StdWOW
> 2024-03-31T21:30:55.054468-05:00 frost weewxd[7210]: DEBUG weewx.engine: 
> Loading service weewx.restx.StdAWEKAS
> 2024-03-31T21:30:55.054794-05:00 frost weewxd[7210]: INFO weewx.restx: 
> AWEKAS: Posting not enabled.
> 2024-03-31T21:30:55.055133-05:00 frost weewxd[7210]: DEBUG weewx.engine: 
> Finished loading service weewx.restx.StdAWEKAS
> 2024-03-31T21:30:55.055478-05:00 frost weewxd[7210]: DEBUG weewx.engine: 
> Loading service weewx.engine.StdPrint
> 2024-03-31T21:30:55.055803-05:00 frost weewxd[7210]: DEBUG weewx.engine: 
> Finished loading service weewx.engine.StdPrint
> 2024-03-31T21:30:55.056138-05:00 frost weewxd[7210]: DEBUG weewx.engine: 
> Loading service weewx.engine.StdReport
> 2024-03-31T21:30:55.059708-05:00 frost weewxd[7210]: INFO weewx.engine: 
> 'pyephem' detected, extended almanac data is available
> 2024-03-31T21:30:55.060078-05:00 frost weewxd[7210]: DEBUG weewx.engine: 
> Finished loading service weewx.engine.StdReport
> 2024-03-31T21:30:55.060419-05:00 frost weewxd[7210]: INFO __main__: 
> Starting up weewx version 5.0.2
> 2024-03-31T21:30:55.060749-05:00 frost weewxd[7210]: DEBUG weewx.engine: 
> Station does not support reading the time
> 2024-03-31T21:30:55.061122-05:00 frost weewxd[7210]: INFO weewx.engine: 
> Using binding 'wx_binding' to database 'weewx.sdb'
> 2024-03-31T21:30:55.061465-05:00 frost weewxd[7210]: INFO weewx.manager: 
> Starting backfill of daily summaries
> 2024-03-31T21:30:55.061795-05:00 frost weewxd[7210]: INFO weewx.manager: 
> Empty database
> 2024-03-31T21:30:55.062109-05:00 frost weewxd[7210]: INFO weewx.engine: 
> Starting main packet loop.
> 2024-03-31T21:30:55.062446-05:00 frost weewxd.py: weatherflowudp: 
> MainThread: Listening for UDP broadcasts to IP address  on port 
> 50222, with timeout 90 and share_socket False...
>
> On Saturday, March 30, 2024 at 10:34:29 AM UTC-5 vince wrote:
>
>> Not without seeing some debug=1 logs. See ‘how to report a problem” in 
>> the faq and wiki
>>
>> On Friday, March 29, 2024 at 10:58:35 PM UTC-7 Glen Briggs wrote:
>>
>>> I have managed to get weewx running, weatherflowudp is installed, but it 
>>> doesn't appear to gather any data, I changed my ST- to the correct number, 
>>> and i have tried all three UDP listener settings, but it keeps saying 
>>> timeout. 
>>>
>>> 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/5021353d-af34-4553-84dc-e890eb28b419n%40googlegroups.com.

Re: [weewx-user] Re: Ventus W830 or Ecowitt GW2000 help for Raspberry Pi

[vince]

Not understanding (yet) is more than fine, and tying and failing (and as a 
result, learning) is part of the adventure, but you really do need to 
provide log snippets for folks to look at if you want to get some help. 
 Just saying "I am still struggling" and "I am still unable to xyz" doesn't 
provide any info others would need in order to try to help at all.

Give the clean setup a try.  Be sure to match the port in weewx.conf with 
whatever you tell your gear to send to.   It should hear 'something'.


On Saturday, March 30, 2024 at 4:34:42 PM UTC-7 radio4pi wrote:

> I was trying to thank you again, and to apologise for my lack of 
> understanding. I have managed to get so far each time, but then stumble at 
> different points due to my insufficient understanding of some basic 
> Raspberry Pi functions and features.
>
> But I think each time I am building on my previous attempts, and just 
> compounding my mistakes. So yes,  a 'clean' pi installation for my next 
> attempt.
>
>
> On 30 Mar 2024 at 23:16, vince  wrote: 
>
> Without providing logs, there is little we can do to read your mind.
>
> This script works on a 'clean' pi to install weewx+interceptor using the 
> dpkg and install interceptor over v5 weewx.   You'll have to manually edit 
> weewx.conf to set the listening port to match your station's setup (this 
> example uses 8000) and then you'll need to restart weewx to make it take 
> effect. 
>
> Unfortunately I don't have any gear to listen to, so I can't test it 
> completely, but weewx 'does' run the interceptor and it 'does' listen on 
> the specified port.
>
> #-- install weewx using the dpkg installation method
> sudo apt install -y wget gnupg
> wget -qO - https://weewx.com/keys.html | \
> sudo gpg --dearmor --output /etc/apt/trusted.gpg.d/weewx.gpg
>
> echo "deb [arch=all] https://weewx.com/apt/python3 buster main" | \
> sudo tee /etc/apt/sources.list.d/weewx.list
>
> sudo apt update
> sudo DEBIAN_FRONTEND=noninteractive apt install -y weewx
>
> #--- install interceptor and hook into weewx
> sudo apt-get install -y libpcap-dev
> sudo python3 -m pip install libpcap pypcap --break-system-packages
> sudo weectl extension install 
> https://github.com/matthewwall/weewx-interceptor/archive/master.zip
> sudo weectl station reconfigure --no-prompt --driver=user.interceptor
>
> #--- add weewx to all the groups typical 'pi' is
> # which should permit binding to non-privileged ports
> for g in adm dialout cdrom sudo audio video plugdev games users input 
> render netdev gpio i2c spi
> do
>   sudo usermod -aG $g weewx
> done
>
> #--- manual steps to do to complete the installation are below
> #
> # sudo vi /etc/weewx.conf
> #   and add "listen = 8000" to the Interceptor section
> #   and run "sudo systemctl restart weewx" to restart weewx
> #
> # sudo tail /var/log/syslog should show weewx log entries
> # or alternately "sudo journalctl -xe -u weewx" to do it that way
> #
>
>
> On Saturday, March 30, 2024 at 12:21:36 PM UTC-7 radio4pi wrote:
>
>> Thank you all for your help on this.
>>
>> I am still struggling unfortunately, and not understanding what I am 
>> doing wrong. Nor, to be honest, not understanding what I am doing? I am not 
>> a programmer, and I am just following what others have written verbatim. So 
>> when it fails I don't know why? It would be great to have a Step-by-step 
>> guide, even though the Help pages are very informative, it doesn't alter 
>> the fact that I don't know what I don't know. Sort of like learning to 
>> drive a car without having a car, if you get what I mean? This must he 
>> frustrating for you all too?
>>
>> The Android app that I use is WS View Plus;
>>
>> I kept getting Timeout Errors when trying to get the "Customized" set to 
>> Port 8080. But I managed to get it set to Port 8000 as suggested elsewhere. 
>> I also had Timeout Errors when trying to set the Path, but it seems to like 
>> the Path set as "/". Again as suggested elswhere. At some point I did get 
>> it set to Path 8000.
>>
>>
>> But I am still struggling trying to get the Interceptor to install? 
>> Whether I am in the wrong Folder, or the respective part of the 
>> Installation is in the wrong Folder, or I am not in Root, or whatever else 
>> Error I get, I am unable to resolve the issue. 
>>
>> I think eventually the penny will drop, and it will "click" as to what I 
>> am reading, and I will suddenly see what I am doing wrong. But when sat in 
>> front of the Keyboard and Screen on my own,

Re: [weewx-user] Re: Ventus W830 or Ecowitt GW2000 help for Raspberry Pi

[vince]

(try 2 - google groups is autodeleting my followup for some reason)

That should be "port = 8000" in the script posted a few minutes ago, not 
"listen = 8000".  Sorry for the typo.

-- 
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/6eb41fa0-36cc-4c3d-977d-9a6efc8ba91fn%40googlegroups.com.

Re: [weewx-user] Re: Ventus W830 or Ecowitt GW2000 help for Raspberry Pi

[vince]

Without providing logs, there is little we can do to read your mind.

This script works on a 'clean' pi to install weewx+interceptor using the 
dpkg and install interceptor over v5 weewx.   You'll have to manually edit 
weewx.conf to set the listening port to match your station's setup (this 
example uses 8000) and then you'll need to restart weewx to make it take 
effect. 

Unfortunately I don't have any gear to listen to, so I can't test it 
completely, but weewx 'does' run the interceptor and it 'does' listen on 
the specified port.

#-- install weewx using the dpkg installation method
sudo apt install -y wget gnupg
wget -qO - https://weewx.com/keys.html | \
sudo gpg --dearmor --output /etc/apt/trusted.gpg.d/weewx.gpg

echo "deb [arch=all] https://weewx.com/apt/python3 buster main" | \
sudo tee /etc/apt/sources.list.d/weewx.list

sudo apt update
sudo DEBIAN_FRONTEND=noninteractive apt install -y weewx

#--- install interceptor and hook into weewx
sudo apt-get install -y libpcap-dev
sudo python3 -m pip install libpcap pypcap --break-system-packages
sudo weectl extension install 
https://github.com/matthewwall/weewx-interceptor/archive/master.zip
sudo weectl station reconfigure --no-prompt --driver=user.interceptor

#--- add weewx to all the groups typical 'pi' is
# which should permit binding to non-privileged ports
for g in adm dialout cdrom sudo audio video plugdev games users input 
render netdev gpio i2c spi
do
  sudo usermod -aG $g weewx
done

#--- manual steps to do to complete the installation are below
#
# sudo vi /etc/weewx.conf
#   and add "listen = 8000" to the Interceptor section
#   and run "sudo systemctl restart weewx" to restart weewx
#
# sudo tail /var/log/syslog should show weewx log entries
# or alternately "sudo journalctl -xe -u weewx" to do it that way
#


On Saturday, March 30, 2024 at 12:21:36 PM UTC-7 radio4pi wrote:

> Thank you all for your help on this.
>
> I am still struggling unfortunately, and not understanding what I am doing 
> wrong. Nor, to be honest, not understanding what I am doing? I am not a 
> programmer, and I am just following what others have written verbatim. So 
> when it fails I don't know why? It would be great to have a Step-by-step 
> guide, even though the Help pages are very informative, it doesn't alter 
> the fact that I don't know what I don't know. Sort of like learning to 
> drive a car without having a car, if you get what I mean? This must he 
> frustrating for you all too?
>
> The Android app that I use is WS View Plus;
>
> I kept getting Timeout Errors when trying to get the "Customized" set to 
> Port 8080. But I managed to get it set to Port 8000 as suggested elsewhere. 
> I also had Timeout Errors when trying to set the Path, but it seems to like 
> the Path set as "/". Again as suggested elswhere. At some point I did get 
> it set to Path 8000.
>
>
> But I am still struggling trying to get the Interceptor to install? 
> Whether I am in the wrong Folder, or the respective part of the 
> Installation is in the wrong Folder, or I am not in Root, or whatever else 
> Error I get, I am unable to resolve the issue. 
>
> I think eventually the penny will drop, and it will "click" as to what I 
> am reading, and I will suddenly see what I am doing wrong. But when sat in 
> front of the Keyboard and Screen on my own, without anyone to guide me, or 
> anyone else to soundboard off of, this is a bit of a learning curve. But 
> that's half of the fun! When I get it working correctly I'll let you all 
> know .
>
> On 29 Mar 2024 at 15:53, Kruse Ludington  wrote: 
>
> I had to struggle to but mine now works and hopefully the below 
> information will help. 
>
> I have a Raspberry PI connected by ethernet to the same network that my 
> AmbientWeather WS-2902C console is connected to, so they can talk to each 
> other.
>
> The interceptor section of my weewx.conf file has (between the  only):
> 
> [Interceptor]
> # This section is for the network traffic interceptor driver.
> 
> # The driver to use:
> driver = user.interceptor
> 
> # Specify the hardware device to capture.  Options include:
> #   acurite-bridge - acurite internet bridge, smarthub, or access
> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
> #   lw30x - oregon scientific LW301/LW302
> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
> #   ecowitt-client - any hardware that uses the ecowitt protocol
> #   wu-client - any hardware that uses the weather underground protocol
> device_type = observer
> port = 8080
> iface = eth0
> 
>
> iface is eth0 as I have it weewx on the rpi over ethernet, and note the 
> port 8080 is important (must match awnet) as per the bottom of this message:
>
> For the WS-2902C console to connect to weatherunderground and other 
> places, on my andoid phone (they have a smilar app for iphones) - the app 
> is 

[weewx-user] Re: weatherflowpdp timeout

[vince]

Not without seeing some debug=1 logs. See ‘how to report a problem” in the 
faq and wiki

On Friday, March 29, 2024 at 10:58:35 PM UTC-7 Glen Briggs wrote:

> I have managed to get weewx running, weatherflowudp is installed, but it 
> doesn't appear to gather any data, I changed my ST- to the correct number, 
> and i have tried all three UDP listener settings, but it keeps saying 
> timeout. 
>
> 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/bf53c839-a3cb-4a3d-a705-30f109f4d19an%40googlegroups.com.

Re: [weewx-user] Setting up rtldavis - where to get?

[vince]

Try it and let everybody know!

On Friday, March 29, 2024 at 6:32:52 AM UTC-7 pli...@googlemail.com wrote:

> Hello to all!
> I want to build the setup with an rtl-sdr stick to receive the data from 
> my Vantage Pro 2.
>
> The rtl-sdr stick which i have bought is the new version v4 which cames in 
> 2023.
> https://www.rtl-sdr.com/rtl-sdr-blog-v4-dongle-initial-release/
>
> Is this new hardware version compatible with the solution of luc 
> https://github.com/lheijst/weewx-rtldavis
> and the new install from vince under 
> https://github.com/vinceskahan/weewx-rtldavis
>
> Does anyone have i tested with the v4 stick?
>
> Many thanks and greetings
> plinepa
>
>
> vince schrieb am Montag, 25. März 2024 um 03:58:49 UTC+1:
>
>> An inexpensive bme280 handles the inside t,h,p stuff but yup the 
>> datalogger functionality is nice to have
>>
>> On Sunday, March 24, 2024 at 7:47:13 PM UTC-7 Graham Eddy wrote:
>>
>>> this sounds great.
>>> for the record, eliminating the davis console and its need for a 
>>> serial/usb port also eliminates what it provides: various indoor sensors 
>>> (including barometer i think) and -crucially- the hardware data logger
>>> *⊣GE⊢*
>>>
>>> On 25 Mar 2024, at 3:46 AM, vince  wrote:
>>>
>>> Short answer is '*yes it takes care of things just fine*'...
>>>
>>> Loosely related - I recently updated my repo containing a script to set 
>>> up v5 weewx/nginx with rtldavis (link) 
>>> <https://github.com/vinceskahan/weewx-rtldavis> if anybody is having 
>>> issues following Luc's ancient documentation for his driver.  The issue if 
>>> you follow Luc's old docs as written these days is that the go language 
>>> folks induced breaking changes in golang-1.16 and later. Simply specifying 
>>> an older version of golang does the trick in preventing getting bitten by 
>>> that upstream breaking change.
>>>
>>> (I noticed this workaround buried in an attachment in an old thread 
>>> (link) 
>>> <https://groups.google.com/g/weewx-user/c/bGiQPuOljqs/m/Mrvwe50UCQAJ> from 
>>> last year from another user here)
>>>
>>> Some disclaimers on my script linked above:
>>>
>>>- it assumes you are on a pi running as user 'pi'
>>>- it only supports v5 pip installations of weewx
>>>- and I have 'no' plans be able to handle dpkg installs, running as 
>>>other users, docker, whatever.
>>>- (but it should be a good starting point for how to install 
>>>librtlsdr and rtldavis nowadays)
>>>
>>>
>>> On Sunday, March 24, 2024 at 8:05:22 AM UTC-7 bgra...@umw.edu wrote:
>>>
>>>> Vince,
>>>> According to Davis for the Vantage Pro 2:
>>>> Operates on frequency-hopping spread spectrum of 902 to 928 MHz. 
>>>> Vantage Pro units operated at 916.5 MHz
>>>>
>>>> *Does the rtldavis take care of this? Is it able to scan for spread 
>>>> spectrum data? I don’t know a lot about this.*
>>>> *Thanks.*
>>>>
>>>> *Bob*
>>>> On Saturday, March 23, 2024 at 3:09:10 PM UTC-4 vince wrote:
>>>>
>>>>> Sorry - late reply.  I don't understand the frequency hopping 
>>>>> question.  The rtldavis just kinda works and hears the ISS just fine.  I 
>>>>> didn't do an exhaustive test but I did run it for a couple three days and 
>>>>> it was nice and stable here.
>>>>>
>>>>> On Sunday, March 10, 2024 at 6:56:07 AM UTC-7 bgra...@umw.edu wrote:
>>>>>
>>>>>>
>>>>>> Hello,
>>>>>> I need some help setting up a VantagePro2 with this. Vince’s How To 
>>>>>> was helpful but doesn’t address the VP2 and its frequency hopping. Could 
>>>>>> someone running a successful setup post details? I’m running Bookworm on 
>>>>>> an 
>>>>>> RPI5. Thanks in advance.
>>>>>> Bob
>>>>>>
>>>>>> On Sunday, March 10, 2024 at 3:12:55 AM UTC-4 mihec wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>> I need help setting up the rtldavis as well. Currently I'm using 
>>>>>>> Ubuntu22.04 (as a test polygon) and latest weewx version (5.0x). I did 
>>>>>>> follow up instructions from the github link but got stuck at step 4) 
>>>>>>> where 
>>>>>>> I should reconfigure the driver. The new &

Re: [weewx-user] Ventus W830 or Ecowitt GW2000 help for Raspberry Pi

[vince]

I added the commands for getting interceptor to (seem to) work on a v5 dpkg 
installation.  See  
https://github.com/matthewwall/weewx-interceptor/issues/120 for details.

On Thursday, March 28, 2024 at 10:17:33 AM UTC-7 vince wrote:

> Couple things.  First - google groups can seemingly randomly eat posts. 
>  Nobody knows why.
>
> Secondly -  "*sudo --install weewx-interceptor-master*" - There is no 
> such command and you're probably getting frustrated enough at this point to 
> essentially just make up commands at this point.  Suggest you take a 
> breath, walk away for an hour, and revisit the documentation for weewx v5 
> and specifically how to use the extension installer, specifically the 
> installaing a driver and skin/extension sections near the top of  
> <https://www.weewx.com/docs/5.0/usersguide/installing/>
> https://www.weewx.com/docs/5.0/usersguide/installing/ - basically step 
> back and read the usersguide.  That's why hundreds of hours were spent 
> writing it.
>
> The interceptor driver docs online are old and show v4 weewx syntax for 
> how to install things.  The v5 commands are different and simpler.  I'd do 
> the following:
>
> sudo weectl extension install 
> https://github.com/matthewwall/weewx-interceptor/archive/master.zip
> sudo weectl station reconfigure --no-prompt --driver=user.interceptor
>  
> I opened https://github.com/matthewwall/weewx-interceptor/issues/120 
> documenting how I got interceptor to work on v5 with a 'pip' installation. 
> Doing so with a dpkg installation is a little more difficult because you'll 
> run into that "*This environment is externally managed*" error from newer 
> versions of python. You can work around that by adding a flag to your pip 
> command ala "*pip install package_name --break-system-packages*". Yes 
> that flag is very badly worded to my eyes too but that's what they called 
> it.
>
> Or you can go back and use weewx v4 and you might be able to use the 
> existing interceptor documentation.
>
>

-- 
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/d74de058-13f0-4342-b1bc-954e560bd5c0n%40googlegroups.com.

Re: [weewx-user] Ventus W830 or Ecowitt GW2000 help for Raspberry Pi

[vince]

Couple things.  First - google groups can seemingly randomly eat posts. 
 Nobody knows why.

Secondly -  "*sudo --install weewx-interceptor-master*" - There is no such 
command and you're probably getting frustrated enough at this point to 
essentially just make up commands at this point.  Suggest you take a 
breath, walk away for an hour, and revisit the documentation for weewx v5 
and specifically how to use the extension installer, specifically the 
installaing a driver and skin/extension sections near the top of  

https://www.weewx.com/docs/5.0/usersguide/installing/ - basically step back 
and read the usersguide.  That's why hundreds of hours were spent writing 
it.

The interceptor driver docs online are old and show v4 weewx syntax for how 
to install things.  The v5 commands are different and simpler.  I'd do the 
following:

sudo weectl extension install 
https://github.com/matthewwall/weewx-interceptor/archive/master.zip
sudo weectl station reconfigure --no-prompt --driver=user.interceptor
 
I opened https://github.com/matthewwall/weewx-interceptor/issues/120 
documenting how I got interceptor to work on v5 with a 'pip' installation. 
Doing so with a dpkg installation is a little more difficult because you'll 
run into that "*This environment is externally managed*" error from newer 
versions of python. You can work around that by adding a flag to your pip 
command ala "*pip install package_name --break-system-packages*". Yes that 
flag is very badly worded to my eyes too but that's what they called it.

Or you can go back and use weewx v4 and you might be able to use the 
existing interceptor documentation.

-- 
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/ce28c3d0-46d2-44f7-aef2-9957ccdd5a33n%40googlegroups.com.

[weewx-user] Re: Not running correctly

[vince]

As always we need more info.  Need to see your debug snippet from 
weewx.conf and a few lines above and below there.

Run  "head -n 25 /etc/weewx/weewx.conf" and lets see what it looks like...


On Wednesday, March 27, 2024 at 11:44:06 AM UTC-7 Dan Becker wrote:

> Have been using weewx for well over a decade.  I am running on a rasp-pi 
> and since moving up to version 5 it just does not work correctly.  So I am 
> now on a fresh install of bookworm and weewx 5.02.
> This is the error I get 
> weewxd
> Unable to set up logger: invalid literal for int() with base 10: ''
> Traceback (most recent call last):
>   File "/usr/share/weewx/weewxd.py", line 93, in main
> weeutil.logger.setup(namespace.log_label, config_dict)
>   File "/usr/share/weewx/weeutil/logger.py", line 110, in setup
> weewx.debug = int(config_dict.get('debug', 0))
>   
> ValueError: invalid literal for int() with base 10: ''
>
> DanB
>

-- 
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/8ea22330-b53e-4355-802e-cb2c6f6993b5n%40googlegroups.com.

[weewx-user] Re: Unexpected weewx stop: ERROR weewx.engine: Import of driver failed

[vince]

Perhaps this setting (link) 
<https://unix.stackexchange.com/questions/564443/what-does-restart-on-abort-mean-in-a-systemd-service>
 is 
something to try if you want to experiment and let us know if it works…

On Monday, March 25, 2024 at 3:11:41 PM UTC-7 Thomas Hackler wrote:

> thank you for the answer, then it was maybe soemthing wrong with the wifi
>
> does it make sense to increase the attempts before exit ?
>
> I try to find something to check if the process is running
> I have some experience with monit, so maybe I find an example or anything 
> else
>
>
> vince schrieb am Montag, 25. März 2024 um 22:09:58 UTC+1:
>
>> I have also seen my gw1000 weewx setup abort on the pi4 occasionally when 
>> the wifi network bounces for some reason.  Mine's been up for 6 weeks now 
>> so it is definitely a transient kind of thing.
>>
>> Writing yourself a little cron job to look for the weewxd process and if 
>> it's not there restart it wouldn't be too tough to do.   Perhaps there is 
>> some systemd configuration magic that is possible, but I'm not sure there 
>> what a safe+effective way to leverage systemd would look like.  I know how 
>> cron works :-)
>>
>> On Monday, March 25, 2024 at 1:56:10 PM UTC-7 Thomas Hackler wrote:
>>
>>> Hello,
>>> my weewx stopped yesterday unexpected. The last logs are attached. It 
>>> ran stable for over 1 week. I have restarts of my raspberry pi with cron 
>>> every 1 or 2 days. What is the reason that the gw1000 driver has suddenly a 
>>> problem? How can I avoid it in future? Should I increase the attemps if 
>>> there is a short problem with the wifi connection?
>>> It is a problem of my gw1000 device? I see no problems with the ecowitt 
>>> app.
>>> Thank you!
>>> Regards
>>> Thomas
>>>
>>

-- 
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/0ad581b5-8ae0-4d26-84e3-bbf6c87cbdecn%40googlegroups.com.

[weewx-user] Re: Unexpected weewx stop: ERROR weewx.engine: Import of driver failed

[vince]

I have also seen my gw1000 weewx setup abort on the pi4 occasionally when 
the wifi network bounces for some reason.  Mine's been up for 6 weeks now 
so it is definitely a transient kind of thing.

Writing yourself a little cron job to look for the weewxd process and if 
it's not there restart it wouldn't be too tough to do.   Perhaps there is 
some systemd configuration magic that is possible, but I'm not sure there 
what a safe+effective way to leverage systemd would look like.  I know how 
cron works :-)

On Monday, March 25, 2024 at 1:56:10 PM UTC-7 Thomas Hackler wrote:

> Hello,
> my weewx stopped yesterday unexpected. The last logs are attached. It ran 
> stable for over 1 week. I have restarts of my raspberry pi with cron every 
> 1 or 2 days. What is the reason that the gw1000 driver has suddenly a 
> problem? How can I avoid it in future? Should I increase the attemps if 
> there is a short problem with the wifi connection?
> It is a problem of my gw1000 device? I see no problems with the ecowitt 
> app.
> Thank you!
> Regards
> Thomas
>

-- 
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/c220117e-b402-4e2a-a749-9e1117949eden%40googlegroups.com.

[weewx-user] Re: Weewx install error

[vince]

Lets see the snippet for longitude from weewx.conf please...

On Monday, March 25, 2024 at 10:47:04 AM UTC-7 John Lowry wrote:

> Converting string to float in install.
>
> HW: RPI5
> SW: error on both RaspOS (bookworm) and Ubuntu
>
> During install, the user is prompted for lat/long of the weather station.  
> The installation fails with the following error output:
>
> File "/usr/share/weewx/weectllib/station_actions.py", line 205, in 
> config_config
> config_latlon(config_dict, latitude=latitude, longitude=longitude, 
> no_prompt=no_prompt)
>   File "/usr/share/weewx/weectllib/station_actions.py", line 345, in 
> config_latlon
> config_dict['Station']['longitude'] = float(final_longitude)
>   ^^
> ValueError: could not convert string to float: '0.00048.830545'
>
> The value I entered was 48.830545, not 0.000etc
>
> Any suggestions highly appreciated.
>

-- 
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/defd9bf1-c403-40de-a807-9122606a5dddn%40googlegroups.com.

Re: [weewx-user] Setting up rtldavis - where to get?

[vince]

An inexpensive bme280 handles the inside t,h,p stuff but yup the datalogger 
functionality is nice to have

On Sunday, March 24, 2024 at 7:47:13 PM UTC-7 Graham Eddy wrote:

> this sounds great.
> for the record, eliminating the davis console and its need for a 
> serial/usb port also eliminates what it provides: various indoor sensors 
> (including barometer i think) and -crucially- the hardware data logger
> *⊣GE⊢*
>
> On 25 Mar 2024, at 3:46 AM, vince  wrote:
>
> Short answer is '*yes it takes care of things just fine*'...
>
> Loosely related - I recently updated my repo containing a script to set up 
> v5 weewx/nginx with rtldavis (link) 
> <https://github.com/vinceskahan/weewx-rtldavis> if anybody is having 
> issues following Luc's ancient documentation for his driver.  The issue if 
> you follow Luc's old docs as written these days is that the go language 
> folks induced breaking changes in golang-1.16 and later. Simply specifying 
> an older version of golang does the trick in preventing getting bitten by 
> that upstream breaking change.
>
> (I noticed this workaround buried in an attachment in an old thread (link) 
> <https://groups.google.com/g/weewx-user/c/bGiQPuOljqs/m/Mrvwe50UCQAJ> from 
> last year from another user here)
>
> Some disclaimers on my script linked above:
>
>- it assumes you are on a pi running as user 'pi'
>- it only supports v5 pip installations of weewx
>- and I have 'no' plans be able to handle dpkg installs, running as 
>other users, docker, whatever.
>- (but it should be a good starting point for how to install librtlsdr 
>    and rtldavis nowadays)
>
>
> On Sunday, March 24, 2024 at 8:05:22 AM UTC-7 bgra...@umw.edu wrote:
>
>> Vince,
>> According to Davis for the Vantage Pro 2:
>> Operates on frequency-hopping spread spectrum of 902 to 928 MHz. Vantage 
>> Pro units operated at 916.5 MHz
>>
>> *Does the rtldavis take care of this? Is it able to scan for spread 
>> spectrum data? I don’t know a lot about this.*
>> *Thanks.*
>>
>> *Bob*
>> On Saturday, March 23, 2024 at 3:09:10 PM UTC-4 vince wrote:
>>
>>> Sorry - late reply.  I don't understand the frequency hopping question. 
>>>  The rtldavis just kinda works and hears the ISS just fine.  I didn't do an 
>>> exhaustive test but I did run it for a couple three days and it was nice 
>>> and stable here.
>>>
>>> On Sunday, March 10, 2024 at 6:56:07 AM UTC-7 bgra...@umw.edu wrote:
>>>
>>>>
>>>> Hello,
>>>> I need some help setting up a VantagePro2 with this. Vince’s How To was 
>>>> helpful but doesn’t address the VP2 and its frequency hopping. Could 
>>>> someone running a successful setup post details? I’m running Bookworm on 
>>>> an 
>>>> RPI5. Thanks in advance.
>>>> Bob
>>>>
>>>> On Sunday, March 10, 2024 at 3:12:55 AM UTC-4 mihec wrote:
>>>>
>>>>> Hi,
>>>>> I need help setting up the rtldavis as well. Currently I'm using 
>>>>> Ubuntu22.04 (as a test polygon) and latest weewx version (5.0x). I did 
>>>>> follow up instructions from the github link but got stuck at step 4) 
>>>>> where 
>>>>> I should reconfigure the driver. The new "weectl" binary does not seem to 
>>>>> have this option but I was assuming it might do it with "weectl extension 
>>>>> install" already?
>>>>> The next issue is with the build. I don't understand 5b): Since I am 
>>>>> supposed to "cd" into a directory, it should have already exist. But when 
>>>>> was the "$GOPATH/src/github.com/lheijst/rtldavis" created?
>>>>> I managed to compile some code (honestly don't know how :-) ), I have 
>>>>> a rtldavis binary which seems to recognize my Realtek RTLSDR dongle. I 
>>>>> then 
>>>>> try step 7) but it fails with 
>>>>> File "/etc/weewx/bin/user/rtldavis.py", line 93, in 
>>>>>   import weewx.drivers
>>>>> ModuleNotFoundError: No module named 'weewx'
>>>>>
>>>>> Can you please help with this? 
>>>>> Thank you.
>>>>> torek, 23. avgust 2022 ob 05:56:50 UTC+2 je oseba storm...@gmail.com 
>>>>> napisala:
>>>>>
>>>>>> Take a look here:
>>>>>>
>>>>>> https://github.com/lheijst/weewx-rtldavis
>>>>>>
>>>>>> On Monday, August 22, 2022 at 11:42:38 PM UTC-4 f4

[weewx-user] Re: Setting up rtldavis - where to get?

[vince]

Short answer is '*yes it takes care of things just fine*'...

Loosely related - I recently updated my repo containing a script to set up 
v5 weewx/nginx with rtldavis (link) 
<https://github.com/vinceskahan/weewx-rtldavis> if anybody is having issues 
following Luc's ancient documentation for his driver.  The issue if you 
follow Luc's old docs as written these days is that the go language folks 
induced breaking changes in golang-1.16 and later. Simply specifying an 
older version of golang does the trick in preventing getting bitten by that 
upstream breaking change.

(I noticed this workaround buried in an attachment in an old thread (link) 
<https://groups.google.com/g/weewx-user/c/bGiQPuOljqs/m/Mrvwe50UCQAJ> from 
last year from another user here)

Some disclaimers on my script linked above:

   - it assumes you are on a pi running as user 'pi'
   - it only supports v5 pip installations of weewx
   - and I have 'no' plans be able to handle dpkg installs, running as 
   other users, docker, whatever.
   - (but it should be a good starting point for how to install librtlsdr 
   and rtldavis nowadays)


On Sunday, March 24, 2024 at 8:05:22 AM UTC-7 bgra...@umw.edu wrote:

> Vince,
> According to Davis for the Vantage Pro 2:
> Operates on frequency-hopping spread spectrum of 902 to 928 MHz. Vantage 
> Pro units operated at 916.5 MHz
>
> *Does the rtldavis take care of this? Is it able to scan for spread 
> spectrum data? I don’t know a lot about this.*
> *Thanks.*
>
> *Bob*
> On Saturday, March 23, 2024 at 3:09:10 PM UTC-4 vince wrote:
>
>> Sorry - late reply.  I don't understand the frequency hopping question. 
>>  The rtldavis just kinda works and hears the ISS just fine.  I didn't do an 
>> exhaustive test but I did run it for a couple three days and it was nice 
>> and stable here.
>>
>> On Sunday, March 10, 2024 at 6:56:07 AM UTC-7 bgra...@umw.edu wrote:
>>
>>>
>>> Hello,
>>> I need some help setting up a VantagePro2 with this. Vince’s How To was 
>>> helpful but doesn’t address the VP2 and its frequency hopping. Could 
>>> someone running a successful setup post details? I’m running Bookworm on an 
>>> RPI5. Thanks in advance.
>>> Bob
>>>
>>> On Sunday, March 10, 2024 at 3:12:55 AM UTC-4 mihec wrote:
>>>
>>>> Hi,
>>>> I need help setting up the rtldavis as well. Currently I'm using 
>>>> Ubuntu22.04 (as a test polygon) and latest weewx version (5.0x). I did 
>>>> follow up instructions from the github link but got stuck at step 4) where 
>>>> I should reconfigure the driver. The new "weectl" binary does not seem to 
>>>> have this option but I was assuming it might do it with "weectl extension 
>>>> install" already?
>>>> The next issue is with the build. I don't understand 5b): Since I am 
>>>> supposed to "cd" into a directory, it should have already exist. But when 
>>>> was the "$GOPATH/src/github.com/lheijst/rtldavis" created?
>>>> I managed to compile some code (honestly don't know how :-) ), I have a 
>>>> rtldavis binary which seems to recognize my Realtek RTLSDR dongle. I then 
>>>> try step 7) but it fails with 
>>>> File "/etc/weewx/bin/user/rtldavis.py", line 93, in 
>>>>   import weewx.drivers
>>>> ModuleNotFoundError: No module named 'weewx'
>>>>
>>>> Can you please help with this? 
>>>> Thank you.
>>>> torek, 23. avgust 2022 ob 05:56:50 UTC+2 je oseba storm...@gmail.com 
>>>> napisala:
>>>>
>>>>> Take a look here:
>>>>>
>>>>> https://github.com/lheijst/weewx-rtldavis
>>>>>
>>>>> On Monday, August 22, 2022 at 11:42:38 PM UTC-4 f4n...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> Hi, does anyone have the installation files for rtldavis? It seems to 
>>>>>> be archived (https://github.com/bemasher/rtldavis) and not longer 
>>>>>> available in the repository if I try to install it with golang.
>>>>>>
>>>>>> Is anyone having long term experience and still running it? How 
>>>>>> stable is the signal with a R820T/T2 chip? Does it get every 2.5s wind 
>>>>>> packet?
>>>>>>
>>>>>> Thanks for any advice,
>>>>>> fankyy
>>>>>>
>>>>>

-- 
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/2505d1fe-4ea0-4cae-9730-159e1c907ab7n%40googlegroups.com.

[weewx-user] Re: Setting up rtldavis - where to get?

[vince]

Sorry - late reply.  I don't understand the frequency hopping question. 
 The rtldavis just kinda works and hears the ISS just fine.  I didn't do an 
exhaustive test but I did run it for a couple three days and it was nice 
and stable here.

On Sunday, March 10, 2024 at 6:56:07 AM UTC-7 bgra...@umw.edu wrote:

>
> Hello,
> I need some help setting up a VantagePro2 with this. Vince’s How To was 
> helpful but doesn’t address the VP2 and its frequency hopping. Could 
> someone running a successful setup post details? I’m running Bookworm on an 
> RPI5. Thanks in advance.
> Bob
>
> On Sunday, March 10, 2024 at 3:12:55 AM UTC-4 mihec wrote:
>
>> Hi,
>> I need help setting up the rtldavis as well. Currently I'm using 
>> Ubuntu22.04 (as a test polygon) and latest weewx version (5.0x). I did 
>> follow up instructions from the github link but got stuck at step 4) where 
>> I should reconfigure the driver. The new "weectl" binary does not seem to 
>> have this option but I was assuming it might do it with "weectl extension 
>> install" already?
>> The next issue is with the build. I don't understand 5b): Since I am 
>> supposed to "cd" into a directory, it should have already exist. But when 
>> was the "$GOPATH/src/github.com/lheijst/rtldavis" created?
>> I managed to compile some code (honestly don't know how :-) ), I have a 
>> rtldavis binary which seems to recognize my Realtek RTLSDR dongle. I then 
>> try step 7) but it fails with 
>> File "/etc/weewx/bin/user/rtldavis.py", line 93, in 
>>   import weewx.drivers
>> ModuleNotFoundError: No module named 'weewx'
>>
>> Can you please help with this? 
>> Thank you.
>> torek, 23. avgust 2022 ob 05:56:50 UTC+2 je oseba storm...@gmail.com 
>> napisala:
>>
>>> Take a look here:
>>>
>>> https://github.com/lheijst/weewx-rtldavis
>>>
>>> On Monday, August 22, 2022 at 11:42:38 PM UTC-4 f4n...@gmail.com wrote:
>>>
 Hi, does anyone have the installation files for rtldavis? It seems to 
 be archived (https://github.com/bemasher/rtldavis) and not longer 
 available in the repository if I try to install it with golang.

 Is anyone having long term experience and still running it? How stable 
 is the signal with a R820T/T2 chip? Does it get every 2.5s wind packet?

 Thanks for any advice,
 fankyy

>>>

-- 
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/76f7026c-a17b-418c-a241-43be8cf47dcan%40googlegroups.com.

[weewx-user] Re: Exclude list or Overwrite behaviour for RSync Report

[vince]

Check out the options in https://ss64.com/bash/rsync_options.htm 
l and see if you can make vanilla 
rsync from the shell do (or not do) what you want.  If that doesn't solve 
it, I'd doubt weewx can help much there as a wrapper over rsync.   The -u 
option might be what you're looking for possibly.

But the rsync uploader (rsyncupload.py) doesn't seem to have the ability to 
provide additional flags to the underlying rsync command.  I'm sure Tom 
would appreciate a PR to add more functionality if you can figure out an 
incantation works and some more general purpose thing to add to weewx 
(possibly something like a rsync_options = "whatever" thing?).

That said - if you're trying to use weewx as the source of the 
authoritative file to upload something, why would you externally mess with 
the file(s) on the far side after that ?  I'm sure there's some use case 
you have but I can't think of a reason why it would be necessary

On Thursday, March 21, 2024 at 9:34:27 AM UTC-7 Chris Alemany wrote:

> And just to be complete, this is on weewx 5.0.2, pip install on Debian.
>
> On Thursday, March 21, 2024 at 9:19:55 AM UTC-7 Chris Alemany wrote:
>
>> Good morning all, 
>>
>> I’m having some trouble with the weewx RSync report overwriting files 
>> that have changed on the remote side independent of weewx. Are there any 
>> provisions in the RSync report to exclude a list of files and/or folders 
>> (including in skins) or otherwise change the way the process operates so 
>> that files that exist on both ends but with a newer timestamp on the remote 
>> side don’t get overwritten by the older local file? 
>> Thanks very much 
>>
>> Chris 
>> https://alberniweather.ca 
>>
>>

-- 
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/d848223c-fe8f-493b-999e-c839e25ed5e7n%40googlegroups.com.

Re: [weewx-user] Re: Failed new install

[vince]

try:
   sudo sh -c 'echo PURGE | debconf-communicate weewx'


On Wednesday, March 20, 2024 at 12:56:27 PM UTC-7 Ron Walker wrote:

> Thanks all so much for the quick replies!  I attempted to implement your 
> suggestion and got the following:
>
> ron@WeatherPi5:~ $ sudo echo PURGE | debconf-communicate weewx
> debconf: DbDriver "passwords" warning: could not open 
> /var/cache/debconf/passwords.dat: Permission denied
> 0
> debconf: DbDriver "config": could not write 
> /var/cache/debconf/config.dat-new: Permission denied
>
>
> On Wednesday, March 20, 2024 at 3:00:59 PM UTC-4 Tom Keffer wrote:
>
>> I think Michael is on the right track. You may have typed "feet" instead 
>> of "foot". 
>>
>> Debian remembers your prior responses, so now you have a bad response in 
>> its database and that's why your stuck. To purge the database, do this
>>
>>
>> *  sudo echo PURGE | debconf-communicate weewx*
>>
>> then start all over.
>>
>>
>> On Wed, Mar 20, 2024 at 11:54 AM 'michael.k...@gmx.at' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>>
>>> Just guessing by the error message:
>>>
>>> weectl.py: error: unrecognized arguments: feet,foot
>>>
>>>
>>> https://weewx.com/docs/5.0/reference/skin-options/units/?h=singular#groups
>>> Note that the measurement unit is always specified in the singular. 
>>> That is, specify degree_C or foot, not degrees_C or feet.
>>>
>>>
>>>
>>> Ron Walker schrieb am Mittwoch, 20. März 2024 um 19:24:41 UTC+1:
>>>
 I have been through the forum looking for this issue , but have not 
 seen this issue addressed.

 I;m trying to install weewx 5.02 on a fresh install of Debian Buster on 
 a Raspberry Pi 3.  When I attempt to install weewx, I get the following:

 ron@WeatherPi5:~ $ wget -qO - https://weewx.com/apt/weewx-python3.list 
 | sudo tee /etc/apt/sources.list.d/weewx.list
 deb [arch=all] http://weewx.com/apt/python3 buster main
 ron@WeatherPi5:~ $ sudo apt update
 Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
 Get:2 http://weewx.com/apt/python3 buster InRelease [4,252 B] 
  
 Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease 
 
 Get:4 http://weewx.com/apt/python3 buster/main all Packages [4,988 B]
 Fetched 9,240 B in 2s (5,992 B/s)  
 Reading package lists... Done
 Building dependency tree... Done
 Reading state information... Done
 All packages are up to date.
 ron@WeatherPi5:~ $ sudo apt install weewx
 Reading package lists... Done
 Building dependency tree... Done
 Reading state information... Done
 The following package was automatically installed and is no longer 
 required:
   libfuse2
 Use 'sudo apt autoremove' to remove it.
 The following additional packages will be installed:
   python3-cheetah python3-configobj python3-ephem python3-usb
 Suggested packages:
   python-cheetah-doc python3-markdown python3-memcache 
 python-configobj-doc
   sqlite ftp httpd
 The following NEW packages will be installed:
   python3-cheetah python3-configobj python3-ephem python3-usb weewx
 0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
 Need to get 2,370 kB of archives.
 After this operation, 9,616 kB of additional disk space will be used.
 Do you want to continue? [Y/n] y
 Get:2 http://weewx.com/apt/python3 buster/main all weewx all 5.0.2-1 
 [1,556 kB]
 Get:1 http://mirror.us.leaseweb.net/raspbian/raspbian bullseye/main 
 armhf python3-configobj all 5.0.6-4 [35.8 kB]
 Get:3 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf 
 python3-cheetah armhf 3.2.6-1+b1 [142 kB]
 Get:4 http://mirror.us.leaseweb.net/raspbian/raspbian bullseye/main 
 armhf python3-usb all 1.0.2-2 [38.9 kB]
 Get:5 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf 
 python3-ephem armhf 3.7.7.1-1+b1 [596 kB]
 Fetched 2,370 kB in 2s (1,376 kB/s)
 Preconfiguring packages ...
 Selecting previously unselected package python3-configobj.
 (Reading database ... 173112 files and directories currently installed.)
 Preparing to unpack .../python3-configobj_5.0.6-4_all.deb ...
 Unpacking python3-configobj (5.0.6-4) ...
 Selecting previously unselected package python3-cheetah.
 Preparing to unpack .../python3-cheetah_3.2.6-1+b1_armhf.deb ...
 Unpacking python3-cheetah (3.2.6-1+b1) ...
 Selecting previously unselected package python3-usb.
 Preparing to unpack .../python3-usb_1.0.2-2_all.deb ...
 Unpacking python3-usb (1.0.2-2) ...
 Selecting previously unselected package python3-ephem.
 Preparing to unpack .../python3-ephem_3.7.7.1-1+b1_armhf.deb ...
 Unpacking python3-ephem (3.7.7.1-1+b1) ...
 Selecting previously unselected package weewx.
 Preparing to unpack .../archives/weewx_5.0.2-1_all.deb ...
 Unpacking weewx (5.0.2-1) ...

[weewx-user] v5 pip - interceptor in sniff mode permissions question

[vince]

I'm fiddling around trying to learn interceptor and how to set it up for v5 
and have it at least listening without errors as user 'pi' as long as I'm 
listening on an unprivileged port.   

But 'sniff' mode requires being able to get into promiscuous mode it seems 
and then I'm hitting permission issues. I use the 'pip' installation for 
weewx but I'd expect the dpkg would have the same issues since weewx now 
runs unprivileged.

I did find some cryptic google hits suggesting that I can give the python 
interpreter permission to do so ala "sudo setcap cap_net_raw+eip 
/usr/bin/python3.11"  which seems to permit weewxd to sniff for packets, 
but that seems like a security risk isn't it ?

Is there a preferred way to get the unprivileged weewxd user the ability to 
sniff for packets if you have to run interceptor in that mode ???

My pip3 list includes:

PackageVersion
-- ---
libpcap1.11.0b8
pypcap 1.3.0
(others omitted for brevity)

My Interceptor stanza looks like:
[Interceptor]
# This section is for the network traffic interceptor driver.

# The driver to use:
driver = user.interceptor

# Specify the hardware device to capture. Options include:
#   acurite-bridge - acurite internet bridge, smarthub, or access
#   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
#   lw30x - oregon scientific LW301/LW302
#   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
#   ecowitt-client - any hardware that uses the ecowitt protocol
#   wu-client - any hardware that uses the weather underground protocol
device_type = ecowitt-client
iface = wlan0

# listen
#mode = listen
#port = 8000

# or sniff
   mode = sniff
   pcap_filter = src 192.168.1.201 and dst port 8001

-- 
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/38403d42-3bb5-4003-9786-308c39309ec9n%40googlegroups.com.

[weewx-user] Re: Failed new install

[vince]

check your altitude in weewx.conf - you possibly have a typo there.  It 
should look like:

altitude = 365, foot# Choose 'foot' or 'meter' for unit

On Wednesday, March 20, 2024 at 11:54:05 AM UTC-7 michael.k...@gmx.at wrote:

> Just guessing by the error message:
>
> weectl.py: error: unrecognized arguments: feet,foot
>
> https://weewx.com/docs/5.0/reference/skin-options/units/?h=singular#groups
> Note that the measurement unit is always specified in the singular. That 
> is, specify degree_C or foot, not degrees_C or feet.
>
>
>
> Ron Walker schrieb am Mittwoch, 20. März 2024 um 19:24:41 UTC+1:
>
>> I have been through the forum looking for this issue , but have not seen 
>> this issue addressed.
>>
>> I;m trying to install weewx 5.02 on a fresh install of Debian Buster on a 
>> Raspberry Pi 3.  When I attempt to install weewx, I get the following:
>>
>> ron@WeatherPi5:~ $ wget -qO - https://weewx.com/apt/weewx-python3.list | 
>> sudo tee /etc/apt/sources.list.d/weewx.list
>> deb [arch=all] http://weewx.com/apt/python3 buster main
>> ron@WeatherPi5:~ $ sudo apt update
>> Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
>> Get:2 http://weewx.com/apt/python3 buster InRelease [4,252 B]   
>>
>> Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease   
>>   
>> Get:4 http://weewx.com/apt/python3 buster/main all Packages [4,988 B]
>> Fetched 9,240 B in 2s (5,992 B/s)  
>> Reading package lists... Done
>> Building dependency tree... Done
>> Reading state information... Done
>> All packages are up to date.
>> ron@WeatherPi5:~ $ sudo apt install weewx
>> Reading package lists... Done
>> Building dependency tree... Done
>> Reading state information... Done
>> The following package was automatically installed and is no longer 
>> required:
>>   libfuse2
>> Use 'sudo apt autoremove' to remove it.
>> The following additional packages will be installed:
>>   python3-cheetah python3-configobj python3-ephem python3-usb
>> Suggested packages:
>>   python-cheetah-doc python3-markdown python3-memcache 
>> python-configobj-doc
>>   sqlite ftp httpd
>> The following NEW packages will be installed:
>>   python3-cheetah python3-configobj python3-ephem python3-usb weewx
>> 0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
>> Need to get 2,370 kB of archives.
>> After this operation, 9,616 kB of additional disk space will be used.
>> Do you want to continue? [Y/n] y
>> Get:2 http://weewx.com/apt/python3 buster/main all weewx all 5.0.2-1 
>> [1,556 kB]
>> Get:1 http://mirror.us.leaseweb.net/raspbian/raspbian bullseye/main 
>> armhf python3-configobj all 5.0.6-4 [35.8 kB]
>> Get:3 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf 
>> python3-cheetah armhf 3.2.6-1+b1 [142 kB]
>> Get:4 http://mirror.us.leaseweb.net/raspbian/raspbian bullseye/main 
>> armhf python3-usb all 1.0.2-2 [38.9 kB]
>> Get:5 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf 
>> python3-ephem armhf 3.7.7.1-1+b1 [596 kB]
>> Fetched 2,370 kB in 2s (1,376 kB/s)
>> Preconfiguring packages ...
>> Selecting previously unselected package python3-configobj.
>> (Reading database ... 173112 files and directories currently installed.)
>> Preparing to unpack .../python3-configobj_5.0.6-4_all.deb ...
>> Unpacking python3-configobj (5.0.6-4) ...
>> Selecting previously unselected package python3-cheetah.
>> Preparing to unpack .../python3-cheetah_3.2.6-1+b1_armhf.deb ...
>> Unpacking python3-cheetah (3.2.6-1+b1) ...
>> Selecting previously unselected package python3-usb.
>> Preparing to unpack .../python3-usb_1.0.2-2_all.deb ...
>> Unpacking python3-usb (1.0.2-2) ...
>> Selecting previously unselected package python3-ephem.
>> Preparing to unpack .../python3-ephem_3.7.7.1-1+b1_armhf.deb ...
>> Unpacking python3-ephem (3.7.7.1-1+b1) ...
>> Selecting previously unselected package weewx.
>> Preparing to unpack .../archives/weewx_5.0.2-1_all.deb ...
>> Unpacking weewx (5.0.2-1) ...
>> Setting up python3-usb (1.0.2-2) ...
>> Setting up python3-ephem (3.7.7.1-1+b1) ...
>> Setting up python3-cheetah (3.2.6-1+b1) ...
>> Setting up python3-configobj (5.0.6-4) ...
>> Setting up weewx (5.0.2-1) ...
>> Using weewx:weewx as user:group
>> Creating /etc/default/weewx
>> usage: weectl.py -v|--version
>>weectl.py -h|--help
>>weectl.py database --help
>>weectl.py debug --help
>>weectl.py device --help
>>weectl.py extension --help
>>weectl.py import --help
>>weectl.py report --help
>>weectl.py station --help
>> weectl.py: error: unrecognized arguments: feet,foot
>> dpkg: error processing package weewx (--configure):
>>  installed weewx package post-installation script subprocess returned 
>> error exit
>>  status 2
>> Processing triggers for man-db (2.9.4-2) ...
>> Errors were encountered while processing:
>>  weewx
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>  
>> The result is 

[weewx-user] Re: WeeWX 5 error

[vince]

>From the FAQ - 
https://github.com/weewx/weewx/wiki/WeeWX-Frequently-Asked-Questions#why-do-i-get-permission-denied
>From the wiki - 
https://github.com/weewx/weewx/wiki/Understanding-permissions

and always google for your exact error messagegoogle for 
"*serial.serialutil.SerialException: 
[Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or 
directory: '/dev/ttyUSB0*'" and look at the hits it returns.

In your case I'd start by unplugging/re-plugging your station into the pi 
and running "sudo dmesg" to see it detected the station at the hardware 
level.   If it did then you have a permission issue the links above will 
point you to how to work that

-- 
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/b62e7bd6-5838-4d09-9756-7539db330ff8n%40googlegroups.com.

Re: [weewx-user] Ventus W830 or Ecowitt GW2000 help for Raspberry Pi

[vince]

Interceptor can be 'very' difficult to figure out from the docs which are 
so old and cryptic that I've given up a half dozen times.  But there are 
about 50 interceptor systems running v5 according to the weewx registered 
system map so it is definitely possible.

It would be 'very' helpful if one of the folks who've been there before 
would write up an end-to-end step-by-step howto with a complete+working set 
of config file entries for how to do this in v5 weewx under python3 (and 
link it into the weewx wiki for others).


-- 
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/cba5137d-acc9-459a-b9b8-35785bd3f57cn%40googlegroups.com.

Re: [weewx-user] Re: Cumulus MX -> weewx

[vince]

You didn't provide enough detail to really understand your setup.   Does 
Cumulus MX have some software it runs that responds on port 8998 ?

Did you even install a normal webserver such as nginx or apache ?   If not, 
see the wiki (link) 

 for 
how to do install one and hook it together with weewx.

On Tuesday, March 19, 2024 at 1:23:58 PM UTC-7 Sidney wrote:

> Thank you for a quick response. web server is for sure installed as I do 
> see Cumulus web server:
> [image: Screenshot 2024-03-19 at 21.20.46.png]
> When I try to go to http://192.168.0.40/weewx I'm getting  This site 
> can’t be reached. Sorry for probably a silly question. Appreciate your 
> support. THank you. 
>
> On Tuesday, March 19, 2024 at 9:12:41 PM UTC+1 Rainer Lang wrote:
>
>> correct, but weewx (its Seasons skin) doesn't have a realtime dashboard 
>> (except you install the mqtt based Belchertown skin).
>> The update interval is defined in weewx.conf and could go down to one 
>> minute instead of five minutes (in theory - in practice to be found out if 
>> the reports can complete in that short time)
>> On 19.03.2024 21:07, Sidney wrote:
>>
>> And for example, when I want to view my CumulusMX Dashboard, I call for: 
>> "http://192.168.0.40:8998/; 
>>
>> On Tuesday, March 19, 2024 at 9:06:32 PM UTC+1 Sidney wrote:
>>
>>> Hi, I believe I've successfully installed weewx. The manual says: 
>>>
>>> After about 5 minutes (the exact length of time depends on your archive 
>>> interval), copy the following and paste into a web browser. You should see 
>>> your station information and data.
>>> /var/www/html/weewx/index.html
>>> Can anyone help me how to call for this index from another computer on 
>>> the same network? I'm connected to my Raspberry over SSH and cannot open 
>>> the browser there. Thank you.
>>> [image: Screenshot 2024-03-19 at 21.03.34.png]
>>>
>>> On Sunday, March 17, 2024 at 8:09:30 PM UTC+1 Sidney wrote:
>>>
 Hi, I would love to switch from Cumulus MX template to weewx. How can I 
 become a tester to get the latest installation files please? Thank you. 
 Sidney
>>>
>>> -- 
>>
>> 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+...@googlegroups.com.
>>
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/559472bb-05d0-419b-a38e-0a6d2331596dn%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/7129bb57-21df-4129-a50b-37c5a1d8a912n%40googlegroups.com.

Re: [weewx-user] Re: new install weewx on a new RPi 4b

[vince]

We cannot help if you say you have errors on permissions if you do not 
include the logs so we can look at them.

On Monday, March 18, 2024 at 1:49:21 PM UTC-7 salinois wrote:

> again, I follow the link an other time ; I found also the same link with 
> my error
>
> I put this line in my config.txt
>
> # Uncomment some or all of these to enable the optional hardware interfaces
> dtparam=i2c_arm=on
> #dtparam=i2s=on
>
> dtparam=spi=on
>
> but always an issue with permissions !
>
> sorry for my ignorance but I can't find it.
>
> Patrick
> Le 18/03/2024 à 21:09, salinois a écrit :
>
> YES YES
>
> but I don't use SPI in my driver 
>
>
> Le 18/03/2024 à 20:57, vince a écrit :
>
> Look at the answer in 
> https://raspberrypi.stackexchange.com/questions/69911/how-to-make-raspbian-load-the-spi-module-on-boot-up
>
> Always always always google for your exact error message.  If you had 
> googled for "*SPISoftwareFallback: failed to initialize hardware SPI, 
> falling back to software"* you would have found this and similar pages.
>
> On Monday, March 18, 2024 at 12:34:24 PM UTC-7 salinois wrote:
>
>> hello Vince,
>>
>> I am come back at home.
>>
>> And I have always an error but different:
>>
>> Mar 18 19:20:51 raspberrypi weewxd[1976]: INFO weewx.engine: Loading 
>> station type BYOWS (user.byows)
>> Mar 18 19:20:51 raspberrypi weewxd.py: BYOWS RPi: using driver BYOWS
>> Mar 18 19:20:51 raspberrypi weewxd.py: BYOWS RPi: driver version is 0.51
>> Mar 18 19:20:51 raspberrypi weewxd[1976]: 
>> /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
>> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
>> software (error was: [Errno 2] Aucun fichier ou dossier de ce type)
>> Mar 18 19:20:51 raspberrypi weewxd[1976]:   warnings.warn(
>> Mar 18 19:20:51 raspberrypi weewxd[1976]: INFO weewx.engine: StdConvert 
>> target unit is 0x1
>>
>> just after a restart of weewx; *but weewx works fine.*
>>
>> lines in my /boot/config.txt:
>>
>> # Uncomment some or all of these to enable the optional hardware 
>> interfaces
>> dtparam=i2c_arm=on
>> #dtparam=i2s=on
>> #dtparam=spi=on
>>
>>
>> I follow all requisites for permissions.
>>
>> I don't see where is the issue.
>>
>> Patrick
>>
>>
>> Le 07/03/2024 à 01:53, vince a écrit :
>>
>> Patrick - when the sun comes around again in France and you get back to 
>> this, I did more research and updated the permissions wiki page.  Check out 
>> the new section at the bottom of the page (link) 
>> <https://github.com/weewx/weewx/wiki/Understanding-permissions#more-details-about-which-groups-can-do-what>
>>  which 
>> hopefully explains better.  I got this information from the debian wiki and 
>> a few blogs and other documents available online in recent years.
>>
>> On Wednesday, March 6, 2024 at 2:06:03 PM UTC-8 salinois wrote:
>>
>>> OK Vince,
>>>
>>> this is new with the version 5.
>>>
>>> I'm going to watch the link "github' and I comme back to you.
>>>
>>> good night from France.
>>>
>>> Patrick
>>> Le 06/03/2024 à 22:52, vince a écrit :
>>>
>>> 4.9 runs as root so you do not see permission issues there. 
>>>
>>> 5.x runs as user 'weewx' so you have to add that user to the correct 
>>> group(s) to access hardware
>>>
>>>
>>> https://github.com/weewx/weewx/wiki/WeeWX-Frequently-Asked-Questions#why-do-i-get-permission-denied
>>>
>>> On Wednesday, March 6, 2024 at 1:46:44 PM UTC-8 salinois wrote:
>>>
>>>> I understand that you say me, but why I don't have this issue with 
>>>> version weewx 4.9 ?
>>>>
>>>> the only difference is RPi 3b and now RPi 4b with bulleyes.
>>>>
>>>> Weewx 4.9 on RPi 3b with Buster
>>>>
>>>> Weewx 5.0.2 on RPi 4b with bulleyes "error"
>>>>
>>>> I am watching the link "robotics"
>>>>
>>>> Patrick
>>>>
>>>>
>>>>
>>>> Le 06/03/2024 à 22:31, vince a écrit :
>>>>
>>>> You need to work through googling your exact error message. 
>>>> "SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
>>>> software (error was: [Errno 13] Permission" 
>>>>
>>>> See if https://roboticsbackend.com/raspberry-pi-hardware-permissions/ 
>>>> helps an

Re: [weewx-user] Ventus W830 or Ecowitt GW2000 help for Raspberry Pi

[vince]

FWIW the gw1000 driver is 'much' easier to get going especially if you're 
new to the pi.  Works great.

On Monday, March 18, 2024 at 1:12:19 PM UTC-7 Pi Radio wrote:

> Interceptor... I saw that earlier?  
>
> Going forwards I'll stop running and walk slowly through this. Thank you.
>
> By the way the Clock on my VHS VCR is still Flashing... I must read the 
> Instruction Manual one day. (If you are not of a certain age, you are not 
> going to get that joke).
>
> But in all seriousness, I am struggling a bit finding my way around all of 
> this jargon, so I thought that before getting too much further lost, I 
> thought I'd wave and ask for guidance.
>
> I've learnt a great deal so far on this massive learning curve, but 
> obviously I am not up to this ...yet.
>
> Bear with me whilst I uninstall it all again, and start a fresh again.
>
> Many thanks for the Links, I'm off to do some more reading.
>
> On Mon, Mar 18, 2024 at 7:55 PM 'Rainer Lang' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> The Ventus W830 is a Ecowitt WH2910 clone. In your mail it is not clear 
>> what "it" means. Your RaspberryPi, weewx, the console ?
>> Maybe you should first make yourself familiar with your environment, your 
>> setup, the architecture and then see where weewx comes into play.
>>
>> I suggest you read https://www.wxforum.net/index.php?topic=40730.0 and 
>> read the Ecowitt/FineOffset WiKi linked therein.
>> Read the chapters about data flow and understand where weewx comes into 
>> play. 
>> Then there are several chapters about how to connect an Ecowitt console 
>> to data logger programs like weewx - even with the special example of weewx.
>>
>> For your W830 you can (only) use the weewx interceptor driver, for your 
>> GW2000 the Ecowitt gateway driver aka GW1000 driver.
>>
>> The weewx WiKi, even though having significantly improved over time, does 
>> not give too much attention to the Ecowitt universe yet.
>> But there is the Fine Offset / Ecowitt WiKi which jumps in here regarding 
>> which Ecowitt (clone) consoles are supported.
>> The weewx WiKi itself is still widely focused on old legacy models of 
>> Fine Offset clone consoles and stations.
>>
>> So, I suggest you read this first (see above) and then come back here if 
>> still needed - by the way, the Simulator driver is only to show that weewx 
>> has been set up properly in principle. It won't work with your console 
>> (Weather Station). Having read the weewx documentation you could have 
>> understood that - but to be fair, it took me also a longer time to come to 
>> grips with the jargon etc. used even though being an IT professional.
>>
>>
>> On 18.03.2024 20:15, Pi Radio wrote:
>>
>> I have just joined, and cannot get my Raspberry Pi configured for my 
>> Ventus W830 PWS.  It is linked to various Online Weather sites including 
>> Weather Underground via it's Display. I also have it linked to an Ecowitt 
>> GW2000 that is not currently linked to any Online Weather sites. 
>>
>> I have read the User Guide, and followed various Tutorials, but I am none 
>> the wiser as to why it does not work?
>>
>> Is there a step by step guide that is written for a complete novice like 
>> me to follow?
>>
>> Although the Ventus W830 is listed in the Compatible Hardware List as a 
>> Fine Offset model it does not appear in the Available Hardware Types in the 
>> Software on my Raspberry Pi. I have tried using Simulator, plus all of the 
>> (dozen or so) options for the various types of PWS listed in the software. 
>>
>> What am I not doing correctly, or what I have missed, I have no idea? I 
>> have just followed the Instructions in the "Guide". But there still seem to 
>> be lots of CRITICAL __main__: errors in Red, so it is a bit catistrophic?
>>
>> I am not a programmer, nor that familiar with a Raspberry Pi. All I know 
>> is what I have been struggling with here, and following YouTube videos.
>>
>> Any help would be very, very much appreciated.  
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/b6dde367-1685-40a0-a908-8050ccbe9e86n%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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/ec992847-5678-43b7-b314-2be91f896aff%40gmail.com
>>  
>> 

Re: [weewx-user] Re: new install weewx on a new RPi 4b

[vince]

Look at the answer in 
https://raspberrypi.stackexchange.com/questions/69911/how-to-make-raspbian-load-the-spi-module-on-boot-up

Always always always google for your exact error message.  If you had 
googled for "*SPISoftwareFallback: failed to initialize hardware SPI, 
falling back to software"* you would have found this and similar pages.

On Monday, March 18, 2024 at 12:34:24 PM UTC-7 salinois wrote:

> hello Vince,
>
> I am come back at home.
>
> And I have always an error but different:
>
> Mar 18 19:20:51 raspberrypi weewxd[1976]: INFO weewx.engine: Loading 
> station type BYOWS (user.byows)
> Mar 18 19:20:51 raspberrypi weewxd.py: BYOWS RPi: using driver BYOWS
> Mar 18 19:20:51 raspberrypi weewxd.py: BYOWS RPi: driver version is 0.51
> Mar 18 19:20:51 raspberrypi weewxd[1976]: 
> /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
> software (error was: [Errno 2] Aucun fichier ou dossier de ce type)
> Mar 18 19:20:51 raspberrypi weewxd[1976]:   warnings.warn(
> Mar 18 19:20:51 raspberrypi weewxd[1976]: INFO weewx.engine: StdConvert 
> target unit is 0x1
>
> just after a restart of weewx; *but weewx works fine.*
>
> lines in my /boot/config.txt:
>
> # Uncomment some or all of these to enable the optional hardware interfaces
> dtparam=i2c_arm=on
> #dtparam=i2s=on
> #dtparam=spi=on
>
>
> I follow all requisites for permissions.
>
> I don't see where is the issue.
>
> Patrick
>
>
> Le 07/03/2024 à 01:53, vince a écrit :
>
> Patrick - when the sun comes around again in France and you get back to 
> this, I did more research and updated the permissions wiki page.  Check out 
> the new section at the bottom of the page (link) 
> <https://github.com/weewx/weewx/wiki/Understanding-permissions#more-details-about-which-groups-can-do-what>
>  which 
> hopefully explains better.  I got this information from the debian wiki and 
> a few blogs and other documents available online in recent years.
>
> On Wednesday, March 6, 2024 at 2:06:03 PM UTC-8 salinois wrote:
>
>> OK Vince,
>>
>> this is new with the version 5.
>>
>> I'm going to watch the link "github' and I comme back to you.
>>
>> good night from France.
>>
>> Patrick
>> Le 06/03/2024 à 22:52, vince a écrit :
>>
>> 4.9 runs as root so you do not see permission issues there. 
>>
>> 5.x runs as user 'weewx' so you have to add that user to the correct 
>> group(s) to access hardware
>>
>>
>> https://github.com/weewx/weewx/wiki/WeeWX-Frequently-Asked-Questions#why-do-i-get-permission-denied
>>
>> On Wednesday, March 6, 2024 at 1:46:44 PM UTC-8 salinois wrote:
>>
>>> I understand that you say me, but why I don't have this issue with 
>>> version weewx 4.9 ?
>>>
>>> the only difference is RPi 3b and now RPi 4b with bulleyes.
>>>
>>> Weewx 4.9 on RPi 3b with Buster
>>>
>>> Weewx 5.0.2 on RPi 4b with bulleyes "error"
>>>
>>> I am watching the link "robotics"
>>>
>>> Patrick
>>>
>>>
>>>
>>> Le 06/03/2024 à 22:31, vince a écrit :
>>>
>>> You need to work through googling your exact error message. 
>>> "SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
>>> software (error was: [Errno 13] Permission" 
>>>
>>> See if https://roboticsbackend.com/raspberry-pi-hardware-permissions/ 
>>> helps any.   It might be group 'spi' that you need to add the user to.
>>>
>>> Rather than changing things randomly please read the link end to end to 
>>> understand it.
>>>
>>>
>>> On Wednesday, March 6, 2024 at 1:25:20 PM UTC-8 salinois wrote:
>>>
>>>> Yes, Vince, I took as you said me.
>>>>
>>>>  $ getent group gpio
>>>> gpio:x:997:pi,weewx
>>>>
>>>> but it is always the same things, this error come , only when I restart 
>>>> weewx. !!!
>>>>
>>>> patrick
>>>> Le 06/03/2024 à 22:15, vince a écrit :
>>>>
>>>> patrick - as I said earlier, 
>>>> " /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
>>>> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
>>>> software (error was: [Errno 13] Permission non accordée)" clearly 
>>>> indicates 
>>>> a permission issue. 
>>>>
>>>> add the weewx user to group gpio.  Really.
>>>>
>>>&g

[weewx-user] Re: Ventus W830 or Ecowitt GW2000 help for Raspberry Pi

[vince]

It's a little hard to guess what exactly you're trying to do and certainly 
impossible to guess what you're seeing as errors.   Are you trying to get 
weewx to get your Ventus data from the gw2000 gateway ? 

But regardless, you should take tiny steps toward the goal:

   - there are zillions of "Guide"(s).  Which one are you using ?
   - what did you do ?  What did you see ?
   - Hopefully you are following the 'debian' instructions (link) 
    to install it. 
  - That should run almost certainly without error on a pi to install a 
  working setup using the Simulator driver
  - if you tried, but failed there, what exactly did you see in 
  console/logfile output ?  Again, please no screenshots.  Copy/paste what 
  you see as output
   - once you get the Simulator running, we can help you switch to getting 
   data from the gw2000if that is what you're trying to do 
   
You might start with the FAQ (link) 
 and 
how to ask questions and provide enough detail that we can try to help. 
 There's info there on how to find your logs as well.

On Monday, March 18, 2024 at 12:17:38 PM UTC-7 Pi Radio wrote:

> I have just joined, and cannot get my Raspberry Pi configured for my 
> Ventus W830 PWS.  It is linked to various Online Weather sites including 
> Weather Underground via it's Display. I also have it linked to an Ecowitt 
> GW2000 that is not currently linked to any Online Weather sites. 
>
> I have read the User Guide, and followed various Tutorials, but I am none 
> the wiser as to why it does not work?
>
> Is there a step by step guide that is written for a complete novice like 
> me to follow?
>
> Although the Ventus W830 is listed in the Compatible Hardware List as a 
> Fine Offset model it does not appear in the Available Hardware Types in the 
> Software on my Raspberry Pi. I have tried using Simulator, plus all of the 
> (dozen or so) options for the various types of PWS listed in the software. 
>
> What am I not doing correctly, or what I have missed, I have no idea? I 
> have just followed the Instructions in the "Guide". But there still seem to 
> be lots of CRITICAL __main__: errors in Red, so it is a bit catistrophic?
>
> I am not a programmer, nor that familiar with a Raspberry Pi. All I know 
> is what I have been struggling with here, and following YouTube videos.
>
> Any help would be very, very much appreciated.  
>

-- 
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/0db49652-ef8b-49ca-8a93-7ef885464f8fn%40googlegroups.com.

[weewx-user] Re: After new installation problems with season skin / no site

[vince]

Not quite.

You need to install all added user extensions and skins. In your case it 
looks like you had the bootstrap skin on your old system which has a file 
bin/user/historygenerator.py that you are missing on the new system. Either 
remove the reference to historygenerator in your weewx.conf or install the 
bootstrap skin to add the missing file.


On Sunday, March 17, 2024 at 12:23:43 PM UTC-7 Thomas Hackler wrote:

> sorry I don't understand, I followed this guide
>
> https://weewx.com/docs/5.0/usersguide/backup/
>
> I compared the weewx.conf file from the fresh installation with my old one 
> and added all the missing things
> so I guess everything should work after that? 
> The neowx skin works normal at the moment, so I will check the warnings 
> later
>
>
> vince schrieb am Sonntag, 17. März 2024 um 18:33:09 UTC+1:
>
>> ModuleNotFoundError: No module named 'user.historygenerator'
>> You need to install all skins and extensions referenced in your .conf 
>> files
>>
>> You also have a variety of warnings from neowx:
>> _etc_weewx_skins_neowx_material_month__Y__m_html_tmpl.py:406: 
>> SyntaxWarning: "is not" with a literal. Did you mean "!="?
>>
>> I 'think' this is related to newer versions of python being more strict. 
>>  I recall trying neowx once and simply editing all the places that weewx 
>> logged those warnings and they went away.
>>
>> On Sunday, March 17, 2024 at 8:12:09 AM UTC-7 Thomas Hackler wrote:
>>
>>> Hello,
>>> my raspberry pi crashed and I started with a new system. Fortunately I 
>>> have copies from my database and the skins.
>>> I started installing weewx and the gw1000 driver, then I copied the skin 
>>> folder and the database.
>>> I had some issues with permissions with the database but this works now. 
>>> I use two skins. The neowx skin works fine but I get errors for the 
>>> season skin and no site is made and I don't understand why.
>>>
>>> Mar 17 15:45:28 raspberrypi weewxd[114945]: ERROR weewx.reportengine: 
>>> Caught unrecoverable exception in generator 
>>> 'weewx.cheetahgenerator.CheetahGenerator'
>>>
>>> Full log file attached.
>>> Thank you for helping!
>>> Thomas Hackler
>>>
>>>
>>>

-- 
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/9615441e-0b9f-4a51-b664-d80701250d5bn%40googlegroups.com.

[weewx-user] Re: After new installation problems with season skin / no site

[vince]

ModuleNotFoundError: No module named 'user.historygenerator'
You need to install all skins and extensions referenced in your .conf 
files

You also have a variety of warnings from neowx:
_etc_weewx_skins_neowx_material_month__Y__m_html_tmpl.py:406: 
SyntaxWarning: "is not" with a literal. Did you mean "!="?

I 'think' this is related to newer versions of python being more strict.  I 
recall trying neowx once and simply editing all the places that weewx 
logged those warnings and they went away.

On Sunday, March 17, 2024 at 8:12:09 AM UTC-7 Thomas Hackler wrote:

> Hello,
> my raspberry pi crashed and I started with a new system. Fortunately I 
> have copies from my database and the skins.
> I started installing weewx and the gw1000 driver, then I copied the skin 
> folder and the database.
> I had some issues with permissions with the database but this works now. 
> I use two skins. The neowx skin works fine but I get errors for the season 
> skin and no site is made and I don't understand why.
>
> Mar 17 15:45:28 raspberrypi weewxd[114945]: ERROR weewx.reportengine: 
> Caught unrecoverable exception in generator 
> 'weewx.cheetahgenerator.CheetahGenerator'
>
> Full log file attached.
> Thank you for helping!
> Thomas Hackler
>
>
>

-- 
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/dc020363-3049-4c88-a902-92cbedd11733n%40googlegroups.com.

[weewx-user] Re: USB/Serial permissions

[vince]

Give https://github.com/weewx/weewx/wiki/Understanding-permissions a read 
and see if that helps.

Summary is at 
https://github.com/weewx/weewx/wiki/Understanding-permissions#the-weewx-user 
and which group typically permits most is at the bottom of the same page.

On Monday, March 11, 2024 at 4:13:49 PM UTC-7 Gord Snarr (GSFarm) wrote:

> New install on a fresh RPI4B, new card etc. 
>
> Installation seems to go fine, but there seems to be a permissions issue 
> with the USB0 port I am using for the USB -> serial adapter to the serial 
> console on the Davis VP.
>
> Log as follows:
>
> × weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; preset: 
> enabled)
>  Active: failed (Result: exit-code) since Mon 2024-03-11 17:10:35 CDT; 
> 38min ago
>Duration: 342ms
>Docs: https://weewx.com/docs
> Process: 2511 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
> status=4)
>Main PID: 2511 (code=exited, status=4)
> CPU: 343ms
>
> Mar 11 17:10:35 raspberrypi weewxd[2511]: CRITICAL weewx.engine:  
> 
> ^
> Mar 11 17:10:35 raspberrypi weewxd[2511]: CRITICAL weewx.engine:  
>File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 244, in 
> __init__
> Mar 11 17:10:35 raspberrypi weewxd[2511]: CRITICAL weewx.engine:  
>  self.open()
> Mar 11 17:10:35 raspberrypi weewxd[2511]: CRITICAL weewx.engine:  
>File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 325, 
> in open
> Mar 11 17:10:35 raspberrypi weewxd[2511]: CRITICAL weewx.engine:  
>  raise SerialException(msg.errno, "could not open port {}: 
> {}".format(self._port, msg))
> Mar 11 17:10:35 raspberrypi weewxd[2511]: CRITICAL weewx.engine:  
>  serial.serialutil.SerialException: [Errno 13] could not open port 
> /dev/ttyUSB0: [Errno 13] Permission denied: '/dev/ttyUSB0'
> Mar 11 17:10:35 raspberrypi weewxd[2511]: CRITICAL __main__: Unable to 
> load driver: [Errno 13] could not open port /dev/ttyUSB0: [Errno 13] 
> Permission denied: '/dev/ttyUSB0'
> Mar 11 17:10:35 raspberrypi weewxd[2511]: CRITICAL __main__:  
>  Exiting...
> Mar 11 17:10:35 raspberrypi systemd[1]: weewx.service: Main process 
> exited, code=exited, status=4/NOPERMISSION
> Mar 11 17:10:35 raspberrypi systemd[1]: weewx.service: Failed with result 
> 'exit-code'.
> ~
>
> VER:
> Linux raspberrypi 6.6.20+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 
> (2024-03-07) aarch64
>
> HRDWR
> RPI-4B
> Davis Vantage Pro (not the II).
> Weewx version (what ever downloaded today using "apt install weewx"). 
> Think it's 5.0.2.
>
> What should the permissions be set to the port, or user added? Is it 
> weewxd, root, pi?
> SHould I change the user in the weewx.conf, or change the chmod the port?
>
> Maybe I should have started with an older weewx version and upgraded? This 
> may have been sorted out already previously.
> Thankx in advance,
> -G.
>

-- 
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/56d26d74-b088-425e-92a3-7a30370f98bbn%40googlegroups.com.

[weewx-user] Re: No column extraHumid3, though Interceptor maps to this column

[vince]

oops - that is 
a https://www.weewx.com/docs/4.10/utilities.htm#Action_--add-column to add 
the column.  Sorry for the typo.

On Monday, March 11, 2024 at 1:05:19 PM UTC-7 vince wrote:

> You're on v4 so you can add a column via 
> https://www.weewx.com/docs/4.10/utilities.htm#Action_--rebuild-daily and 
> I think a subsequent 
> https://www.weewx.com/docs/4.10/utilities.htm#Action_--rebuild-daily
>
> On Monday, March 11, 2024 at 12:53:24 PM UTC-7 Invisible Man wrote:
>
>> Hi,
>> In WeeWx, if I inspect the archive table, there is an extraTemp3, but no 
>> extraHumid3.
>> Why is that? And is it possible to get a extraHumid3? Indeed, I have a 
>> sensor 3 which provides both temperature and humidity.
>>
>> ```
>> sqlite> .schema archive
>> CREATE TABLE archive (`dateTime` INTEGER NOT NULL UNIQUE PRIMARY KEY, 
>> `usUnits` INTEGER NOT NULL, `interval` INTEGER NOT NULL, `barometer` REAL, 
>> `pressure` REAL, `altimeter` REAL, `inTemp` REAL, `outTemp` REAL, 
>> `inHumidity` REAL, `outHumidity` REAL, `windSpeed` REAL, `windDir` REAL, 
>> `windGust` REAL, `windGustDir` REAL, `rainRate` REAL, `rain` REAL, 
>> `dewpoint` REAL, `windchill` REAL, `heatindex` REAL, `ET` REAL, `radiation` 
>> REAL, `UV` REAL, `extraTemp1` REAL, `extraTemp2` REAL, `extraTemp3` REAL, 
>> `soilTemp1` REAL, `soilTemp2` REAL, `soilTemp3` REAL, `soilTemp4` REAL, 
>> `leafTemp1` REAL, `leafTemp2` REAL, `extraHumid1` REAL, `extraHumid2` REAL, 
>> `soilMoist1` REAL, `soilMoist2` REAL, `soilMoist3` REAL, `soilMoist4` REAL, 
>> `leafWet1` REAL, `leafWet2` REAL, `rxCheckPercent` REAL, `txBatteryStatus` 
>> REAL, `consBatteryVoltage` REAL, `hail` REAL, `hailRate` REAL, 
>> `heatingTemp` REAL, `heatingVoltage` REAL, `supplyVoltage` REAL, 
>> `referenceVoltage` REAL, `windBatteryStatus` REAL, `rainBatteryStatus` 
>> REAL, `outTempBatteryStatus` REAL, `inTempBatteryStatus` REAL);
>> ```
>>
>> Note I am using WeeWx 4.10.2 with Interceptor.
>> My weather station provides a humidity_3 (63%) which gets mapped by 
>> Interceptor to extraHumid3 (see below).
>>
>>
>> Mar 11 20:49:37 vegan weewx[21485] DEBUG user.interceptor: raw packet: 
>> {'dateTime': 1710186576, 'usUnits': 1, 'temperature_in': 69.1, 
>> 'humidity_in': 63.0, 'pressure': 29.477, 'temperature_out': 46.6, 
>> 'humidity_out': 98.0, 'wind_dir': 333.0, 'wind_speed': 0.67, 'wind_gust': 
>> 1.12, 'solar_radiation': 0.0, 'uv': 0.0, 'rain_rate': 0.0, 'rain_total': 
>> 22.039, 'temperature_3': 68.4, 'humidity_3': 63.0, 'soil_moisture_1': 50.0, 
>> 'wn34_temperature_1': 51.1, 'wh65_battery': 0.0, 'wh25_battery': 0.0, 
>> 'battery_3': 0.0, 'soil_battery_1': 1.4, 'rain': 0.0}
>> Mar 11 20:49:37 vegan weewx[21485] DEBUG user.interceptor: mapped packet: 
>> {'dateTime': 1710186576, 'usUnits': 1, 'pressure': 29.477, 'outHumidity': 
>> 98.0, 'inHumidity': 63.0, 'outTemp': 46.6, 'inTemp': 69.1, 'windSpeed': 
>> 0.67, 'windGust': 1.12, 'windDir': 333.0, 'radiation': 0.0, 'rain': 0.0, 
>> 'rainRate': 0.0, 'UV': 0.0, 'extraTemp2': 51.1, 'extraTemp3': 68.4, 
>> 'soilMoist1': 50.0, 'extraHumid3': 63.0}
>>
>> Thanks!
>>
>

-- 
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/397bf375-268f-4049-be33-f48f9480de84n%40googlegroups.com.

[weewx-user] Re: No column extraHumid3, though Interceptor maps to this column

[vince]

You're on v4 so you can add a column via 
https://www.weewx.com/docs/4.10/utilities.htm#Action_--rebuild-daily and I 
think a 
subsequent https://www.weewx.com/docs/4.10/utilities.htm#Action_--rebuild-daily

On Monday, March 11, 2024 at 12:53:24 PM UTC-7 Invisible Man wrote:

> Hi,
> In WeeWx, if I inspect the archive table, there is an extraTemp3, but no 
> extraHumid3.
> Why is that? And is it possible to get a extraHumid3? Indeed, I have a 
> sensor 3 which provides both temperature and humidity.
>
> ```
> sqlite> .schema archive
> CREATE TABLE archive (`dateTime` INTEGER NOT NULL UNIQUE PRIMARY KEY, 
> `usUnits` INTEGER NOT NULL, `interval` INTEGER NOT NULL, `barometer` REAL, 
> `pressure` REAL, `altimeter` REAL, `inTemp` REAL, `outTemp` REAL, 
> `inHumidity` REAL, `outHumidity` REAL, `windSpeed` REAL, `windDir` REAL, 
> `windGust` REAL, `windGustDir` REAL, `rainRate` REAL, `rain` REAL, 
> `dewpoint` REAL, `windchill` REAL, `heatindex` REAL, `ET` REAL, `radiation` 
> REAL, `UV` REAL, `extraTemp1` REAL, `extraTemp2` REAL, `extraTemp3` REAL, 
> `soilTemp1` REAL, `soilTemp2` REAL, `soilTemp3` REAL, `soilTemp4` REAL, 
> `leafTemp1` REAL, `leafTemp2` REAL, `extraHumid1` REAL, `extraHumid2` REAL, 
> `soilMoist1` REAL, `soilMoist2` REAL, `soilMoist3` REAL, `soilMoist4` REAL, 
> `leafWet1` REAL, `leafWet2` REAL, `rxCheckPercent` REAL, `txBatteryStatus` 
> REAL, `consBatteryVoltage` REAL, `hail` REAL, `hailRate` REAL, 
> `heatingTemp` REAL, `heatingVoltage` REAL, `supplyVoltage` REAL, 
> `referenceVoltage` REAL, `windBatteryStatus` REAL, `rainBatteryStatus` 
> REAL, `outTempBatteryStatus` REAL, `inTempBatteryStatus` REAL);
> ```
>
> Note I am using WeeWx 4.10.2 with Interceptor.
> My weather station provides a humidity_3 (63%) which gets mapped by 
> Interceptor to extraHumid3 (see below).
>
>
> Mar 11 20:49:37 vegan weewx[21485] DEBUG user.interceptor: raw packet: 
> {'dateTime': 1710186576, 'usUnits': 1, 'temperature_in': 69.1, 
> 'humidity_in': 63.0, 'pressure': 29.477, 'temperature_out': 46.6, 
> 'humidity_out': 98.0, 'wind_dir': 333.0, 'wind_speed': 0.67, 'wind_gust': 
> 1.12, 'solar_radiation': 0.0, 'uv': 0.0, 'rain_rate': 0.0, 'rain_total': 
> 22.039, 'temperature_3': 68.4, 'humidity_3': 63.0, 'soil_moisture_1': 50.0, 
> 'wn34_temperature_1': 51.1, 'wh65_battery': 0.0, 'wh25_battery': 0.0, 
> 'battery_3': 0.0, 'soil_battery_1': 1.4, 'rain': 0.0}
> Mar 11 20:49:37 vegan weewx[21485] DEBUG user.interceptor: mapped packet: 
> {'dateTime': 1710186576, 'usUnits': 1, 'pressure': 29.477, 'outHumidity': 
> 98.0, 'inHumidity': 63.0, 'outTemp': 46.6, 'inTemp': 69.1, 'windSpeed': 
> 0.67, 'windGust': 1.12, 'windDir': 333.0, 'radiation': 0.0, 'rain': 0.0, 
> 'rainRate': 0.0, 'UV': 0.0, 'extraTemp2': 51.1, 'extraTemp3': 68.4, 
> 'soilMoist1': 50.0, 'extraHumid3': 63.0}
>
> Thanks!
>

-- 
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/c2e136b3-7c5b-451e-8547-1406e222fe59n%40googlegroups.com.

[weewx-user] Re: Daily rain total and daylight saving time error.

[vince]

I've learned many years ago to just ignore any days when daylight savings 
changes either way

On Sunday, March 10, 2024 at 10:00:32 AM UTC-7 Russell Swan wrote:

> Hi, daylight saving time happened last night and my rain total 
> ($day.rain.sum) for the day does not equal that on the Davis Vantage Pro2. 
> The console reads 0.73" and weewx puts out 0.52". Interestingly, my Steel 
> Gauges indicate the correct 0.73". I think an hour of rain was dropped. 
>
> weewx version 5.02
>

-- 
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/051a0e83-5b29-44f0-85e8-c91df744cc40n%40googlegroups.com.

Re: [weewx-user] Fedora Weewx RPM install

[vince]

You could git clone the repo and build your own from the makefile. Looks 
like it calls rpmbuild -ba so it should build the srpm hopefully.

On Wednesday, March 6, 2024 at 9:55:19 PM UTC-8 John wrote:

> Not withstanding all of that below Is there a weewx-5.0.2 source rpm 
> (.srpm)
> anywhere public?
>
> I'm a Mageia user who's been installing the Fedora rpms for years (2009) 
> without
> having dependency issues and I'm keen to condition the tradition :-)
>
> Cheers
>
> John in NZ
>
>
> On 7/03/24 04:32, Tom Keffer wrote:
> > See issue #940 .
> >
> > On Wed, Mar 6, 2024 at 3:57 AM Mark Jenks  wrote:
> >
> > Good morning!
> >
> > I was going to do PIP for the new 5.x install, instead of using
> > the setup.py like I have for years.
> > Then I saw the RPM, and figured I was take a look at that, except
> > the rpm doesn't work for Fedora.
> > Fedora is not Enterprise Linux, so you can not install EPEL-Repo
> > for it, but all packages that are in the EPEL, are already avail
> > for Fedora.
> >
> > Looking at the RPM, epel-release is a dependency which is required
> > by the RPM.  So either you create a new RPM for Fedora only, or
> > the dependency needs to be removed.
> >
> > -Mark
> >
> > #
> > dnf install weewx
> > Last metadata expiration check: 0:25:37 ago on Wed 06 Mar 2024
> > 05:30:57 AM CST.
> > Dependencies resolved.
> >
> >  Problem: cannot install the best candidate for the job
> >   - nothing provides epel-release needed by
> > weewx-5.0.2-1.el9.noarch from weewx
> > 
> >
> > rpm -qpR weewx-5.0.2-1.el9.noarch.rpm
> > /bin/sh
> > /bin/sh
> > /bin/sh
> > /usr/bin/getent
> > /usr/sbin/groupadd
> > /usr/sbin/useradd
> > *epel-release*
> > python3
> > python3-cheetah
> > python3-configobj
> > python3-pillow
> > python3-pyserial
> > python3-pyusb
> > rpmlib(CompressedFileNames) <= 3.0.4-1
> > rpmlib(FileDigests) <= 4.6.0-1
> > rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> > rpmlib(PayloadIsXz) <= 5.2-1
> > -- 
> > 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+...@googlegroups.com.
> > To view this discussion on the web visit
> > 
> https://groups.google.com/d/msgid/weewx-user/b8af8921-dcb7-4bfa-9e21-dfdbfb26682cn%40googlegroups.com
> > <
> https://groups.google.com/d/msgid/weewx-user/b8af8921-dcb7-4bfa-9e21-dfdbfb26682cn%40googlegroups.com?utm_medium=email_source=footer
> >.
> >
> > -- 
> > 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+...@googlegroups.com.
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEAf7aEay_sUddjZeR-wMwrL5BR5T0N%3DfLfiyo7Dnhy7fQ%40mail.gmail.com
>  
> > <
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEAf7aEay_sUddjZeR-wMwrL5BR5T0N%3DfLfiyo7Dnhy7fQ%40mail.gmail.com?utm_medium=email_source=footer
> >.
>
>

-- 
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/e2896b36-4345-4bc1-986c-0fe65f6ea322n%40googlegroups.com.

Re: [weewx-user] Re: new install weewx on a new RPi 4b

[vince]

Patrick - when the sun comes around again in France and you get back to 
this, I did more research and updated the permissions wiki page.  Check out 
the new section at the bottom of the page (link) 
<https://github.com/weewx/weewx/wiki/Understanding-permissions#more-details-about-which-groups-can-do-what>
 which 
hopefully explains better.  I got this information from the debian wiki and 
a few blogs and other documents available online in recent years.

On Wednesday, March 6, 2024 at 2:06:03 PM UTC-8 salinois wrote:

> OK Vince,
>
> this is new with the version 5.
>
> I'm going to watch the link "github' and I comme back to you.
>
> good night from France.
>
> Patrick
> Le 06/03/2024 à 22:52, vince a écrit :
>
> 4.9 runs as root so you do not see permission issues there. 
>
> 5.x runs as user 'weewx' so you have to add that user to the correct 
> group(s) to access hardware
>
>
> https://github.com/weewx/weewx/wiki/WeeWX-Frequently-Asked-Questions#why-do-i-get-permission-denied
>
> On Wednesday, March 6, 2024 at 1:46:44 PM UTC-8 salinois wrote:
>
>> I understand that you say me, but why I don't have this issue with 
>> version weewx 4.9 ?
>>
>> the only difference is RPi 3b and now RPi 4b with bulleyes.
>>
>> Weewx 4.9 on RPi 3b with Buster
>>
>> Weewx 5.0.2 on RPi 4b with bulleyes "error"
>>
>> I am watching the link "robotics"
>>
>> Patrick
>>
>>
>>
>> Le 06/03/2024 à 22:31, vince a écrit :
>>
>> You need to work through googling your exact error message. 
>> "SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
>> software (error was: [Errno 13] Permission" 
>>
>> See if https://roboticsbackend.com/raspberry-pi-hardware-permissions/ 
>> helps any.   It might be group 'spi' that you need to add the user to.
>>
>> Rather than changing things randomly please read the link end to end to 
>> understand it.
>>
>>
>> On Wednesday, March 6, 2024 at 1:25:20 PM UTC-8 salinois wrote:
>>
>>> Yes, Vince, I took as you said me.
>>>
>>>  $ getent group gpio
>>> gpio:x:997:pi,weewx
>>>
>>> but it is always the same things, this error come , only when I restart 
>>> weewx. !!!
>>>
>>> patrick
>>> Le 06/03/2024 à 22:15, vince a écrit :
>>>
>>> patrick - as I said earlier, 
>>> " /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
>>> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
>>> software (error was: [Errno 13] Permission non accordée)" clearly indicates 
>>> a permission issue. 
>>>
>>> add the weewx user to group gpio.  Really.
>>>
>>> On Wednesday, March 6, 2024 at 1:12:57 PM UTC-8 salinois wrote:
>>>
>>>> yes, I took that.
>>>>
>>>> ls -ail /etc/weewx/bin/user/
>>>> total 36
>>>> 526359 drwxrwsr-x 3 weewx weewx  4096  6 mars  21:52 .
>>>>
>>>>
>>>> 526358 drwxrwsr-x 3 weewx weewx  4096  7 févr. 22:15 ..
>>>> 524298 -rw-r--r-- 1 weewx weewx 10990  8 févr. 13:05 byows.py
>>>> 526361 -rw-rw-r-- 1 weewx weewx   541  7 févr. 22:15 extensions.py
>>>> 526360 -rw-rw-r-- 1 weewx weewx   306  7 févr. 22:15 __init__.py
>>>>
>>>> 655698 drwxr-sr-x 2 weewx weewx  4096  6 mars  21:54 __pycache__
>>>> 524317 -rw-r--r-- 1 piweewx  4052  6 mars  21:52 stats.py
>>>>
>>>> This is again better.
>>>>
>>>> [Mar  6 21:57:13 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>>>> value: 0.0
>>>> Mar  6 21:57:15 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>>>> value: 0.0
>>>> Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager: Added 
>>>> record 2024-03-06 21:57:00 CET (1709758620) to database 'weewx.sdb'
>>>> Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager: Added 
>>>> record 2024-03-06 21:57:00 CET (1709758620) to daily summary in 'weewx.sdb'
>>>> Mar  6 21:57:16 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>>>> value: 0.0
>>>> Mar  6 21:57:17 raspberrypi weewxd[31835]: INFO weewx.cheetahgenerator: 
>>>> Generated 8 files for report SeasonsReport in 1.26 seconds
>>>> Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO weewx.imagegenerator: 
>>>> Generated 15 images for report SeasonsReport in 0.65 seconds
>>>> Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO weewx.reportengine: 
>>&

[weewx-user] Re: weewx-sdr howto document available on git hub

[vince]

Nice.  Lets see your system service file(s) to match !

How would you use that way as a driver and not even need to user weewx-sdr 
?  Not remembering if MQTT subscribe can run as a driver.  I just run it as 
an extension.

On Wednesday, March 6, 2024 at 2:06:27 PM UTC-8 bell...@gmail.com wrote:

> Vince,
> Nice write up.
> Begin shameless plug…
> Since I am heavily invested in reading things from MQTT, I just run 
> rtl_433 as a separate service and subscribe to the topic. I did this 
> primarily to get the data in a service and secondarily to get sensors that 
> were not ’mapped’.
> The service invocation, ‘ExecStart=/usr/local/bin/rtl_433 -M utc -F 
> mqtt://localhost:1883,retain=0,devices=rtl_433[/host]/devices[/type][/model][/subtype][/channel][/id]’
> And one topic config looks like this
> [[topics]]
> ignore = True
> [[[message]]] type = individual # Upright freezer (basement) 
> [[[rtl_433/weather-data/devices/Acurite-606TX/77/temperature_C]]] ignore = 
> False unit_system = METRIC name = extraTemp8 
>
> It may seem more complicated, but since I was invested in MQTT, it 
> actually simplified it. This was primarily because I could treat rtl_433 as 
> a separate service
>
> End plug
>
> On Wednesday 6 March 2024 at 16:14:25 UTC-5 vince wrote:
>
>> In working with another weewx user to help him gets his SDR station 
>> online, it was clear that lots of people (like me) have some problems 
>> really understanding some of the rtl-433 and sdr documentation that is out 
>> there.
>>
>> After working through it end-to-end a few times on both ubuntu and on a 
>> raspberry pi, I wrote up the whole setup as a howto with examples mainly 
>> for future-me but I thought it might be of general interest.  At worst a 
>> google search should find it for future folks trying to battle SDR into 
>> submission :-)
>>
>> The howto and a small github repo with a patched/enhanced fork of the SDR 
>> driver is at https://github.com/vinceskahan/sdr-howto if you have 
>> interest.  Start with the toplevel readme file then read the howto.txt file 
>> for how I got it working here.
>>
>>

-- 
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/030139c5-c82b-4bb5-8bbf-540f66bf6579n%40googlegroups.com.

Re: [weewx-user] Re: new install weewx on a new RPi 4b

[vince]

4.9 runs as root so you do not see permission issues there.

5.x runs as user 'weewx' so you have to add that user to the correct 
group(s) to access hardware

https://github.com/weewx/weewx/wiki/WeeWX-Frequently-Asked-Questions#why-do-i-get-permission-denied

On Wednesday, March 6, 2024 at 1:46:44 PM UTC-8 salinois wrote:

> I understand that you say me, but why I don't have this issue with version 
> weewx 4.9 ?
>
> the only difference is RPi 3b and now RPi 4b with bulleyes.
>
> Weewx 4.9 on RPi 3b with Buster
>
> Weewx 5.0.2 on RPi 4b with bulleyes "error"
>
> I am watching the link "robotics"
>
> Patrick
>
>
>
> Le 06/03/2024 à 22:31, vince a écrit :
>
> You need to work through googling your exact error message. 
> "SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
> software (error was: [Errno 13] Permission" 
>
> See if https://roboticsbackend.com/raspberry-pi-hardware-permissions/ 
> helps any.   It might be group 'spi' that you need to add the user to.
>
> Rather than changing things randomly please read the link end to end to 
> understand it.
>
>
> On Wednesday, March 6, 2024 at 1:25:20 PM UTC-8 salinois wrote:
>
>> Yes, Vince, I took as you said me.
>>
>>  $ getent group gpio
>> gpio:x:997:pi,weewx
>>
>> but it is always the same things, this error come , only when I restart 
>> weewx. !!!
>>
>> patrick
>> Le 06/03/2024 à 22:15, vince a écrit :
>>
>> patrick - as I said earlier, 
>> " /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
>> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
>> software (error was: [Errno 13] Permission non accordée)" clearly indicates 
>> a permission issue. 
>>
>> add the weewx user to group gpio.  Really.
>>
>> On Wednesday, March 6, 2024 at 1:12:57 PM UTC-8 salinois wrote:
>>
>>> yes, I took that.
>>>
>>> ls -ail /etc/weewx/bin/user/
>>> total 36
>>> 526359 drwxrwsr-x 3 weewx weewx  4096  6 mars  21:52 .
>>>
>>>
>>> 526358 drwxrwsr-x 3 weewx weewx  4096  7 févr. 22:15 ..
>>> 524298 -rw-r--r-- 1 weewx weewx 10990  8 févr. 13:05 byows.py
>>> 526361 -rw-rw-r-- 1 weewx weewx   541  7 févr. 22:15 extensions.py
>>> 526360 -rw-rw-r-- 1 weewx weewx   306  7 févr. 22:15 __init__.py
>>>
>>> 655698 drwxr-sr-x 2 weewx weewx  4096  6 mars  21:54 __pycache__
>>> 524317 -rw-r--r-- 1 piweewx  4052  6 mars  21:52 stats.py
>>>
>>> This is again better.
>>>
>>> [Mar  6 21:57:13 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>>> value: 0.0
>>> Mar  6 21:57:15 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>>> value: 0.0
>>> Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager: Added 
>>> record 2024-03-06 21:57:00 CET (1709758620) to database 'weewx.sdb'
>>> Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager: Added 
>>> record 2024-03-06 21:57:00 CET (1709758620) to daily summary in 'weewx.sdb'
>>> Mar  6 21:57:16 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>>> value: 0.0
>>> Mar  6 21:57:17 raspberrypi weewxd[31835]: INFO weewx.cheetahgenerator: 
>>> Generated 8 files for report SeasonsReport in 1.26 seconds
>>> Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO weewx.imagegenerator: 
>>> Generated 15 images for report SeasonsReport in 0.65 seconds
>>> Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO weewx.reportengine: 
>>> Copied 0 files to /var/www/html/weewx
>>> Mar  6 21:57:18 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>>> value: 0.0]
>>>
>>> Weird, I don't use statistics in my driver !!!
>>>
>>> but I had just an error When I restart weewx 
>>>
>>> Mar  6 22:05:16 raspberrypi weewxd[32027]: 
>>> /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
>>> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
>>> software (error was: [Errno 13] Permission non accordée)
>>> Mar  6 22:05:16 raspberrypi weewxd[32027]: 
>>>
>>>   warnings.warn(
>>>
>>> My command that say "OK"
>>>
>>>  sudo pip3 install gpiozero
>>> Looking in indexes: https://pypi.org/simple, 
>>> https://www.piwheels.org/simple
>>> Requirement already satisfied: gpiozero in 
>>> /usr/lib/python3/dist-packages (1.6.2)
>>>
>>>
>>> patrick
>>>
>>>
>>> Le 06/03/2024 à 21:43, Tom Keffer a écrit 

Re: [weewx-user] Re: new install weewx on a new RPi 4b

[vince]

You need to work through googling your exact error message. 
"SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
software (error was: [Errno 13] Permission"

See if https://roboticsbackend.com/raspberry-pi-hardware-permissions/ helps 
any.   It might be group 'spi' that you need to add the user to.

Rather than changing things randomly please read the link end to end to 
understand it.


On Wednesday, March 6, 2024 at 1:25:20 PM UTC-8 salinois wrote:

> Yes, Vince, I took as you said me.
>
>  $ getent group gpio
> gpio:x:997:pi,weewx
>
> but it is always the same things, this error come , only when I restart 
> weewx. !!!
>
> patrick
> Le 06/03/2024 à 22:15, vince a écrit :
>
> patrick - as I said earlier, 
> " /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
> software (error was: [Errno 13] Permission non accordée)" clearly indicates 
> a permission issue. 
>
> add the weewx user to group gpio.  Really.
>
> On Wednesday, March 6, 2024 at 1:12:57 PM UTC-8 salinois wrote:
>
>> yes, I took that.
>>
>> ls -ail /etc/weewx/bin/user/
>> total 36
>> 526359 drwxrwsr-x 3 weewx weewx  4096  6 mars  21:52 .
>>
>>
>> 526358 drwxrwsr-x 3 weewx weewx  4096  7 févr. 22:15 ..
>> 524298 -rw-r--r-- 1 weewx weewx 10990  8 févr. 13:05 byows.py
>> 526361 -rw-rw-r-- 1 weewx weewx   541  7 févr. 22:15 extensions.py
>> 526360 -rw-rw-r-- 1 weewx weewx   306  7 févr. 22:15 __init__.py
>>
>> 655698 drwxr-sr-x 2 weewx weewx  4096  6 mars  21:54 __pycache__
>> 524317 -rw-r--r-- 1 piweewx  4052  6 mars  21:52 stats.py
>>
>> This is again better.
>>
>> [Mar  6 21:57:13 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>> value: 0.0
>> Mar  6 21:57:15 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>> value: 0.0
>> Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager: Added 
>> record 2024-03-06 21:57:00 CET (1709758620) to database 'weewx.sdb'
>> Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager: Added 
>> record 2024-03-06 21:57:00 CET (1709758620) to daily summary in 'weewx.sdb'
>> Mar  6 21:57:16 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>> value: 0.0
>> Mar  6 21:57:17 raspberrypi weewxd[31835]: INFO weewx.cheetahgenerator: 
>> Generated 8 files for report SeasonsReport in 1.26 seconds
>> Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO weewx.imagegenerator: 
>> Generated 15 images for report SeasonsReport in 0.65 seconds
>> Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO weewx.reportengine: 
>> Copied 0 files to /var/www/html/weewx
>> Mar  6 21:57:18 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>> value: 0.0]
>>
>> Weird, I don't use statistics in my driver !!!
>>
>> but I had just an error When I restart weewx 
>>
>> Mar  6 22:05:16 raspberrypi weewxd[32027]: 
>> /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
>> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
>> software (error was: [Errno 13] Permission non accordée)
>> Mar  6 22:05:16 raspberrypi weewxd[32027]: 
>>
>>   warnings.warn(
>>
>> My command that say "OK"
>>
>>  sudo pip3 install gpiozero
>> Looking in indexes: https://pypi.org/simple, 
>> https://www.piwheels.org/simple
>> Requirement already satisfied: gpiozero in /usr/lib/python3/dist-packages 
>> (1.6.2)
>>
>>
>> patrick
>>
>>
>> Le 06/03/2024 à 21:43, Tom Keffer a écrit :
>>
>> You are missing a search list extension called "stats". I suspect that 
>> this is the old stats module that came with WeeWX until v4.6. 
>>
>> If that's the case, I've attached it. Put it in /etc/weewx/bin/user
>>
>> If it came from somewhere else, I have no idea what it is. Or, perhaps 
>> you don't use it at all.
>>
>> On Wed, Mar 6, 2024 at 12:32 PM salinois  wrote:
>>
>>> OK, I took that, thanks.
>>>
>>> but I use this command:
>>>
>>> # Reconfigure to use your hardware*weectl station reconfigure
>>>
>>> *watch:
>>>
>>> [weectl station reconfigure
>>> Using configuration file /etc/weewx/weewx.conf
>>> Processing configuration file /etc/weewx/weewx.conf
>>>
>>> Give a description of the station. This will be used for the title of 
>>> reports.
>>> description [Loulle, Jura (France)]:
>>>
>>> Specify altitude, with units 'foot' or 'meter'.  For example:
>>>   3

Re: [weewx-user] Re: new install weewx on a new RPi 4b

[vince]

gt;>>
>>> *[Station]*
>>>
>>> # Description of the station location, such as your town.
>>> location = "Loulle, Jura (France)"
>>>
>>> # Latitude in decimal degrees. Negative for southern hemisphere.
>>> latitude = 46.2539
>>> # Longitude in decimal degrees. Negative for western hemisphere.
>>> longitude = 5.3168
>>>
>>> # Altitude of the station, with the unit it is in. This is used only
>>> # if the hardware cannot supply a value.
>>> altitude = 700, meter# Choose 'foot' or 'meter' for unit
>>>
>>> # Set to type of station hardware. There must be a corresponding 
>>> stanza
>>> # in this file, which includes a value for the 'driver' option.
>>>* station_type = BYOWS*
>>>
>>> and next
>>>
>>>
>>>
>>>
>>>
>>> *#
>>>  
>>> [BYOWS]* # This section is for the Raspberry Pi Bring Your Own 
>>> Weather Station driver.
>>>
>>> # The driver to use
>>> * driver = byows ===> is it the good syntax ? *in version 4.9 I 
>>> have user.byows
>>>
>>> but now, there no more errors:
>>>
>>> [ sudo systemctl status weewx.service
>>> ● weewx.service - WeeWX
>>>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
>>> preset: enabled)
>>>  Active: failed (Result: exit-code) since Wed 2024-03-06 20:21:34 
>>> CET; 3s ago
>>>Docs: https://weewx.com/docs
>>> Process: 29896 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
>>> status=1/FAILURE)
>>>Main PID: 29896 (code=exited, status=1/FAILURE)
>>> CPU: 337ms
>>>
>>> mars 06 20:21:34 raspberrypi weewxd[29896]: 
>>> self.setupStation(config_dict)
>>> mars 06 20:21:34 raspberrypi weewxd[29896]:   File 
>>> "/usr/share/weewx/weewx/engine.py", line 104, in setupStation
>>> mars 06 20:21:34 raspberrypi weewxd[29896]: __import__(driver)
>>> mars 06 20:21:34 raspberrypi weewxd[29896]: ModuleNotFoundError: *No 
>>> module named 'byows'*
>>> mars 06 20:21:34 raspberrypi weewxd[29896]: CRITICAL __main__: 
>>> File "/usr/share/weewx/weewx/engine.py", line 104, in setupStation
>>> mars 06 20:21:34 raspberrypi weewxd[29896]: CRITICAL __main__: 
>>>   __import__(driver)
>>> mars 06 20:21:34 raspberrypi weewxd[29896]: CRITICAL __main__:   
>>> ModuleNotFoundError: No module named 'byows'
>>> mars 06 20:21:34 raspberrypi weewxd[29896]: CRITICAL __main__:   
>>> Exiting.
>>> mars 06 20:21:34 raspberrypi systemd[1]: weewx.service: Main process 
>>> exited, code=exited, status=1/FAILURE
>>> mars 06 20:21:34 raspberrypi systemd[1]: weewx.service: Failed with 
>>> result 'exit-code'.]
>>>
>>> Patrick
>>>
>>>
>>>
>>>
>>> Le 06/03/2024 à 19:23, Tom Keffer a écrit :
>>>
>>> If you did a package install, the driver byows.py should go in 
>>> /etc/weewx/bin/user. But, frankly, this should have been done for you if 
>>> you did an upgrade from V4 to V5. Take a look in /etc/weewx/bin/user and 
>>> see if it's in there.
>>>
>>> But, the error in the little snippet from your status report is a 
>>> different one. For some reason, your installation thinks it is not running 
>>> on a Raspberry Pi, so it cannot access the gpio pins. I'm not an expert on 
>>> that, but it may be due to a missing installation package. 
>>>
>>> On Wed, Mar 6, 2024 at 10:13 AM salinois  wrote:
>>>
>>>> again me
>>>>
>>>> perhaps , I found
>>>>
>>>> Should I use this method now?
>>>>
>>>> [weectl extension install /home/pi/byows.py]
>>>>
>>>> and after: 
>>>>
>>>> weectl station reconfigures --no-prompt --driver=weewx.drivers.byows
>>>>
>>>>
>>>> Patrick
>>>> Le 06/03/2024 à 18:47, salinois a écrit :
>>>>
>>>> hello,
>>>>
>>>> I restart my installation with version weewx 5.0.1 and I have these 
>>>> errors:
>>>>
>>>> on my version which works in 4.10.2, my "byows.py" driver is located 
>>>> here: [/usr/share/weewx/us

[weewx-user] weewx-sdr howto document available on git hub

[vince]

In working with another weewx user to help him gets his SDR station online, 
it was clear that lots of people (like me) have some problems really 
understanding some of the rtl-433 and sdr documentation that is out there.

After working through it end-to-end a few times on both ubuntu and on a 
raspberry pi, I wrote up the whole setup as a howto with examples mainly 
for future-me but I thought it might be of general interest.  At worst a 
google search should find it for future folks trying to battle SDR into 
submission :-)

The howto and a small github repo with a patched/enhanced fork of the SDR 
driver is at https://github.com/vinceskahan/sdr-howto if you have interest. 
 Start with the toplevel readme file then read the howto.txt file for how I 
got it working here.

-- 
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/ceae74e5-6194-4c88-b079-603746e2cc7en%40googlegroups.com.

[weewx-user] Re: Raddy L7 Weather Station: XML of Current Conditions-How to Feed WeeWx?

[vince]

You have some pretty hideously formatted JSON to parse, but here's what it 
looks like in a more readable format after piping it through 'jq' and doing 
a little hand editing for readability

{
  "sensor": [
{
  "title": "Indoor",
  "list": [
[ "Temperature", "68.9", "°F" ],
[ "Humidity", "38", "%" ] ]
},
{
  "title": "Outdoor",
  "list": [
[ "Temperature", "61.7", "°F" ],
[ "Humidity", "29", "%" ] ]
},
{
  "title": "Pressure", "list": [
[ "Absolute", "26.76", "inhg" ],
[ "Relative", "29.84", "inhg" ] ]
},
{
  "title": "Wind Speed",
  "list": [
[ "Max Daily Gust", "5.1", "mph" ],
[ "Wind", "1.1", "mph" ],
[ "Gust", "1.6", "mph" ],
[ "Direction", "123", "°" ],
[ "Wind Average 2 Minute", "0.4", "mph" ],
[ "Direction Average 2 Minute", "111", "°" ],
[ "Wind Average 10 Minute", "1.3", "mph" ],
[ "Direction Average 10 Minute", "134", "°" ]
  ]
},
{
  "title": "Rainfall",
  "list": [
[ "Rate", "0.0", "inch/hr" ],
[ "Hour", "0.0", "inch", "43" ],
[ "Day", "0.0", "inch", "44" ],
[ "Week", "0.0", "inch", "45" ],
[ "Month", "0.0", "inch", "46" ],
[ "Year", "5.72", "inch", "47" ],
[ "Total", "10.65", "inch", "48" ]
  ],
  "range": "Range: 0inch to 393.7inch."
},
{
  "title": "Solar",
  "list": [
[ "Light", "261.36", "w/m²" ],
[ "UVI", "1.2", "" ]
  ]
}
  ],
  "battery": {
"title": "Battery",
"list": [ "All battery are ok" ]
  }
}


On Wednesday, March 6, 2024 at 11:59:36 AM UTC-8 Michael wrote:

> I have officially given up on getting interceptor to work in sniffing mode 
> on Phython3.  
>
> On Wednesday, March 6, 2024 at 11:17:39 AM UTC-7 matthew wall wrote:
>
>> it looks like the raddy L7 can upload to wundgerground, so if you are 
>> using the raddy's wifi, you should be able to use the interceptor driver to 
>> capture or directly receive the wunderground output.  setting up the 
>> interceptor is not trivial, but there are many examples.
>>
>> it would be nice if there were a generic json driver, analogous to the 
>> fileparse driver.  but the json structure varies a lot from one device to 
>> another, and the mechanism for obtaining that json output also varies.  for 
>> example, the tempest broadcasts json data, whereas the ruddy emits json as 
>> a response to http request.  so i understand why no one has written one yet.
>>
>> m
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/421d1ce1-9dcf-4148-827d-b97c92a4495cn%40googlegroups.com.

Re: [weewx-user] Re: new install weewx on a new RPi 4b

[vince]

I did find some google links where this message appears due to permission 
problems accessing the hardware. If you look at your error it also says 
NOPERMISSION.  Try adding the user weewx runs as to group gpio via ‘sudo 
usermod -aG gpio weewx’ and see if it works now.

On Wednesday, March 6, 2024 at 10:23:59 AM UTC-8 Tom Keffer wrote:

> If you did a package install, the driver byows.py should go in 
> /etc/weewx/bin/user. But, frankly, this should have been done for you if 
> you did an upgrade from V4 to V5. Take a look in /etc/weewx/bin/user and 
> see if it's in there.
>
> But, the error in the little snippet from your status report is a 
> different one. For some reason, your installation thinks it is not running 
> on a Raspberry Pi, so it cannot access the gpio pins. I'm not an expert on 
> that, but it may be due to a missing installation package. 
>
> On Wed, Mar 6, 2024 at 10:13 AM salinois  wrote:
>
>> again me
>>
>> perhaps , I found
>>
>> Should I use this method now?
>>
>> [weectl extension install /home/pi/byows.py]
>>
>> and after: 
>>
>> weectl station reconfigures --no-prompt --driver=weewx.drivers.byows
>>
>>
>> Patrick
>> Le 06/03/2024 à 18:47, salinois a écrit :
>>
>> hello,
>>
>> I restart my installation with version weewx 5.0.1 and I have these 
>> errors:
>>
>> on my version which works in 4.10.2, my "byows.py" driver is located 
>> here: [/usr/share/weewx/user/] but I saw that the tree structure has 
>> changed; where should I put my driver now?
>>
>> watch these errors:
>>
>> sudo systemctl status weewx.service
>> ● weewx.service - WeeWX
>>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
>> preset: enabled)
>>  Active: failed (Result: exit-code) since Wed 2024-03-06 18:32:05 
>> CET; 2s ago
>>Docs: https://weewx.com/docs
>> Process: 11182 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
>> status=4)
>>Main PID: 11182 (code=exited, status=4)
>> CPU: 682ms
>>
>> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
>>   pin = self.pin_factory.pin(pin)
>> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
>> File "/usr/lib/python3/dist-packages/gpiozero/pins/pi.py", line 
>> 103, in pin
>> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
>>   pin = self.pin_class(self, n)
>> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
>> File "/usr/lib/python3/dist-packages/gpiozero/pins/rpigpio.py", 
>> line 111, in __init__
>> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
>>   GPIO.setup(self.number, GPIO.IN, 
>> self.GPIO_PULL_UPS[self._pull])
>> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
>>   RuntimeError: Not running on a RPi!
>> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL __main__:* Unable 
>> to load driver: Not running on a RPi!*
>> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL __main__:   
>> Exiting...
>> mars 06 18:32:05 raspberrypi systemd[1]: weewx.service: Main process 
>> exited, code=exited, status=4/NOPERMISSION
>> mars 06 18:32:05 raspberrypi systemd[1]: weewx.service: Failed with 
>> result 'exit-code'.
>>
>> Patrick
>> Le 08/02/2024 à 08:59, salinois a écrit :
>>
>> hello Matthew
>>
>> OK I understand if that works
>>
>> thanks also to vince.
>>
>> Now , I must to try the 5.0.0 version
>>
>> Patrick
>> Le 07/02/2024 à 23:06, matthew wall a écrit :
>>
>> On Wednesday, February 7, 2024 at 3:36:55 PM UTC-5 sali...@gmail.com 
>> wrote: 
>>
>> pi@raspberrypi:~ $ wget -qO - https://weewx.com/apt/weewx-python3.list | 
>> sudo tee /etc/apt/sources.list.d/weewx.list 
>> *deb [arch=all] http://weewx.com/apt/python3 
>> <http://weewx.com/apt/python3> buster main ==> why Buster*
>>
>>
>> 'buster' (i.e., debian 10) is the oldest release on which the deb package 
>> will install.
>>
>> if you look at the python2 configuration, it uses the label 'squeeze' 
>> (debian 6)
>>
>> the weewx packages are *really* stable with respect to dependencies, so 
>> the same package that works with debian 10 also works with debian 11 and 
>> debian 12.  besides, i am too old and lazy to build a new deb and new apt 
>> repository for every major debian release that comes out :) 
>>  
>&

[weewx-user] Re: Raddy L7 Weather Station: XML of Current Conditions-How to Feed WeeWx?

[vince]

Something like the purpleair or davis airlink extensions could perhaps be 
modified. Query the endpoint and map it to weewx db elements. Or query 
periodically and feed MQTT.  SHOULD BE DOABLE.

On Wednesday, March 6, 2024 at 10:17:39 AM UTC-8 matthew wall wrote:

> it looks like the raddy L7 can upload to wundgerground, so if you are 
> using the raddy's wifi, you should be able to use the interceptor driver to 
> capture or directly receive the wunderground output.  setting up the 
> interceptor is not trivial, but there are many examples.
>
> it would be nice if there were a generic json driver, analogous to the 
> fileparse driver.  but the json structure varies a lot from one device to 
> another, and the mechanism for obtaining that json output also varies.  for 
> example, the tempest broadcasts json data, whereas the ruddy emits json as 
> a response to http request.  so i understand why no one has written one yet.
>
> m
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7c67d0fb-91c1-477d-9e98-9b580d735eben%40googlegroups.com.

Re: [weewx-user] Re: WeeWx Upgrade Failure

[vince]

Again, asked and answered a hundred times here.  The version in weewx.conf 
shows what you 'started' with, so no. Leave it alone. Weewx pulls its 
version that it logs from the code itself.

On Monday, March 4, 2024 at 2:53:03 PM UTC-8 Fred Keller wrote:

> Thanks for your quick reply.I went to the Upgrade guide and I now see 
> that the commands changed and the new commands are working. 
>
> I have another question.  After the upgrade WeeWx is using my prior 
> configuration file which I think is the default.  However, my current file 
> shows version 4.10.2.  Should I manually edit my config file to show the 
> current version.  I notice that the standard webpage in 192.168.../weewx is 
> still showing version 4.10.2.
>
> Thanks for your help,
>
> Fred
>
> On Mon, Mar 4, 2024 at 5:31 PM vince  wrote:
>
>> Read the upgrade guide and at least a dozen posts from others who didn’t 
>> do so either. The commands changed.
>>
>> On Monday, March 4, 2024 at 2:20:09 PM UTC-8 Fred Keller wrote:
>>
>>> I think my Ubuntu system tried to update my WeeWx 4.10.2 installation 
>>> and had an issue.  I notice that there is a new generic 5.0 configuration 
>>> file in my /etc/weewx directory.  However, I don't think my installation 
>>> file was updated to version 5.  I tried to use wee_config --version to 
>>> determine my version number, but the system does not seem to be able to 
>>> locate wee_config.   It has been so long since I setup WeeWx that I do not 
>>> know if I am doing something wrong when I issue the command.  I am using:  
>>>
>>> sudo wee_config --version. 
>>>
>>> However, when I try this now it cannot find wee_config
>>>
>>> Any help would be appreciated.
>>>
>>> Fred Keller
>>>
>>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/jg1WbAoln60/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/b2dfa0eb-c8ed-4842-9267-1f7b77bc2377n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/b2dfa0eb-c8ed-4842-9267-1f7b77bc2377n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/0cf87552-6d31-4c2c-83be-355b3bee41a5n%40googlegroups.com.

[weewx-user] Re: WeeWx Upgrade Failure

[vince]

Read the upgrade guide and at least a dozen posts from others who didn’t do 
so either. The commands changed.

On Monday, March 4, 2024 at 2:20:09 PM UTC-8 Fred Keller wrote:

> I think my Ubuntu system tried to update my WeeWx 4.10.2 installation and 
> had an issue.  I notice that there is a new generic 5.0 configuration file 
> in my /etc/weewx directory.  However, I don't think my installation file 
> was updated to version 5.  I tried to use wee_config --version to determine 
> my version number, but the system does not seem to be able to locate 
> wee_config.   It has been so long since I setup WeeWx that I do not know if 
> I am doing something wrong when I issue the command.  I am using:  
>
> sudo wee_config --version. 
>
> However, when I try this now it cannot find wee_config
>
> Any help would be appreciated.
>
> Fred Keller
>
>

-- 
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/b2dfa0eb-c8ed-4842-9267-1f7b77bc2377n%40googlegroups.com.

[weewx-user] Re: Comparison of method of using WeeWX

[vince]

There are almost infinite ways to start a process on Linux/unix.

Just use way your os dictates which is likely systemd on a modern system.

On Sunday, March 3, 2024 at 11:45:50 AM UTC-8 Remy Lavabre wrote:

> Good morning,
>
> Small question(s) for a PIP installation:
>
> 1/ Is there a difference between:
> - the use of the weewx daemon
> - the weewxd command placed in the contrab at the RPi starting
> - the manually typed command "nohup weewxd &"?
>
> 2/What is the interest/advantage of one method compared to others?
>
> THANKS
>

-- 
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/aa8f8432-37e0-48bd-b3aa-2e05a0ec8dc4n%40googlegroups.com.

[weewx-user] Re: Weewx 5.0.2, saving sql-backups on a usb stick fails.

[vince]

Permission non accordée: '/media/pi/WEEWX-BU'

You need to give the user running the weewx process to write to the usb 
stick.   This has come up many many times regarding usb devices and v5.

The command is likely "sudo usermod -aG dialout weewx" if your weewx is 
running as user 'weewx'.

On Sunday, March 3, 2024 at 1:57:05 PM UTC-8 Pierre-Yves wrote:

> Hello,
> I am running Weewx on a Rpi4-2GB (user.sdr driver + BME280 and as3935 
> extensions). That works very well.
> I am able to save sql-backups on the default directory (/var/tmp/backups) 
> but I fail to save to a USB stick connected to the Pi USB2 port, with an 
> [errno 13] error Permission denied: '/media/pi/WEEWX-BU'
> The same configuration was working properly with Weewx 4.10.2
>
> I read and followed the Github wiki but have still the same error.
>
> Below, the log, the first part of the sql-backup skin.conf and details on 
> the usb disk connected.
>
> Any clue ?
>
> Thanks,
>
> Pierre-Yves

-- 
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/fa4815dc-9927-45e6-95dc-25e4d7fc059cn%40googlegroups.com.

Re: [weewx-user] sdr packets timezone differ from rtl_433 packets timezone

[vince]

Perfect.  Wow I definitely read the rtl_433 usage backwards.  Thanks !!!

On Sunday, March 3, 2024 at 12:43:52 PM UTC-8 Stefanos Kalaitzis wrote:

I think in the command you can use utc option .. something like this 

cmd = /usr/local/bin/rtl_433 -M utc -F json -f 868.2M -R 172

 

-- 
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/44560a5f-c289-439e-b1f3-fa54d43b2f2cn%40googlegroups.com.

[weewx-user] sdr packets timezone differ from rtl_433 packets timezone

[vince]

I'm fiddling on the side with the SDR driver trying to help another user 
set up weewx with the sdr driver but have run into some oddities here on my 
system.

Short description is the packets as decoded by the sdr driver have a 
dateTime that is many hours behind reality. 

The sdr driver is generating packets with a dateTime that is behind 
localtime reality by the exact number of hours as my GMT offset here (8 
hours)

Yet the system clock on the os looks correct, syslog logs correctly, etc. 
in every other way.   Here are the details

~/weewx-data/bin/user$ date
Sun Mar  3 11:40:44 AM PST 2024

~/weewx-data/bin/user$ date -u
Sun Mar  3 07:40:46 PM UTC 2024

~/weewx-data/bin/user$ timedatectl status
   Local time: Sun 2024-03-03 11:41:20 PST
   Universal time: Sun 2024-03-03 19:41:20 UTC
 RTC time: Sun 2024-03-03 19:41:20
Time zone: America/Los_Angeles (PST, -0800)
System clock synchronized: yes
  NTP service: n/a
  RTC in local TZ: no

>From the syslogs...
2024-03-03T*11:25:39*.336424-08:00 nuc weewxd[9124]: DEBUG user.sdr: 
packet={'extraTemp1': 19.9, 'extraHumid1': 44.0, 'batteryStatus1': 1, 
'dateTime': 1709465136, 'usUnits': 17}

Then decoding the dateTime
~/weewx-data/bin/user$ date -d @1709465136
Sun Mar  3 *03:25:36* AM PST 2024

==> note the decoded dateTime is off by 8 hours.

But when using rtl_433 directly
{"time" : "2024-03-03 *11:39:21*", "model" : "AmbientWeather-WH31B", "id" : 
202, "channel" : 5, "battery_ok" : 1, "temperature_C" : 4.600, "humidity" : 
87, "data" : "785c00", "mic" : "CRC"}

Note the rtl_433 time is correct.

So there's a bug or misconfiguration somewhere but I'm not sure where:

   - system clock looks correct
   - rtl_433 decodes the dateTime correctly
   - but weewx sdr is off by 8 hours
   - and the result also seems to be that weewx doesn't save anything to 
   the archive table at all.  It doesn't even seem to try from what I can see 
   with debug=1.  Could that be due to the dateTime SDR is generating being 8 
   hours slow ?

weewx.conf snippet is as follows:

[SDR]
# This section is for the software-defined radio driver.

# The driver to use
driver = user.sdr
cmd = rtl_433

log_unknown_sensors  = True
log_unmapped_sensors = True

log_duplicate_readings = False # patched sdr.py to quiet logs down 
log_packets= True # patched sdr.py to quiet logs down

[[sensor_map]]
extraTemp1 = temperature.145.AmbientWH31BPacket
extraHumid1= humidity.145.AmbientWH31BPacket
batteryStatus1 = battery.145.AmbientWH31BPacket

extraTemp2 = temperature.153.AmbientWH31BPacket
extraHumid2= humidity.153.AmbientWH31BPacket
batteryStatus2 = battery.153.AmbientWH31BPacket

extraTemp3 = temperature.196.AmbientWH31BPacket
extraHumid3= humidity.196.AmbientWH31BPacket
batteryStatus3 = battery.196.AmbientWH31BPacket

extraTemp4 = temperature.55.AmbientWH31BPacket
extraHumid4= humidity.55.AmbientWH31BPacket
batteryStatus4 = battery.55.AmbientWH31BPacket

extraTemp5 = temperature.202.AmbientWH31BPacket
extraHumid5= humidity.202.AmbientWH31BPacket
batteryStatus5 = battery.202.AmbientWH31BPacket

outTemp  = temperature.35.AmbientWH31BPacket
outHumidity  = humidity.35.AmbientWH31BPacket
outTempBatteryStatus = battery.35.AmbientWH31BPacket

soilMoist1 = soil_moisture_percent.001260.FOWH51Packet

I did patch sdr.py to add a couple new sensor types it didn't know about 
and also to be able to more discretely control logging.  The upstream 
version is a bit verbose when debug=1 (I'd be happy to PR those).   I 
didn't do anything to alter how sdr.py actually does its thing in decoding 
packets it hears via rtl_433.

Sensors are all ecowitt and I did verify in the ecowitt gateway app that 
its timezone is set correctly but given I'm sniffing RF via SDR, I'm 
guessing it doesn't really matter what the ecowitt iphone app is set to do 
(?)

~/.config/rtl_433/rtl_433.conf has nothing time-related in it
frequency 915M
output json

Suggestions or pointers to where anybody's run into this before 
appreciated


-- 
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/08103768-5d95-4066-8274-c1fac496073dn%40googlegroups.com.

Re: [weewx-user] Reinstalling weewx

[vince]

Couple things

   - you're asking for a feature to be able to skip saving data to the db...
   - yet you want to check your new installation works...
   - which 'requires' saving data to the db so you can check that
   - in other words - what you're asking for would prevent you doing what 
   you want to do (huh?)
   - and secondly missing a few readings isn't the end of the world worst 
   case

If you have the official Davis datalogger that stores up to a week or so of 
readings from your sensors as long as the console is powered up.  Weewx 
will gracefully catch up to any records the datalogger has that the db 
doesn't (yet) have stored and you won't miss any readings.  If you have a 
third party logger with no such storage, your mileage may vary.

On Friday, March 1, 2024 at 8:51:00 AM UTC-8 John Smith wrote:

> Pretty sure you can boot from usb on a rpi3b
>
> https://www.instructables.com/Booting-Raspberry-Pi-3-B-With-a-USB-Drive/
>
> On Sat, 2 Mar 2024 at 03:44, Bill Petheram  wrote:
>
>> Vantage Pro2 connected with USB.
>>
>> On Friday, March 1, 2024 at 4:38:21 PM UTC Tom Keffer wrote:
>>
>>> What kind of hardware?
>>>
>>> On Fri, Mar 1, 2024 at 8:36 AM Bill Petheram  
>>> wrote:
>>>
 I wasn't being clear. 

 There is no way for preventing records being read from the hardware and 
 so they get lost. 

 I did ry not connecting the hardware but then weewx doesn't start 
 properly.

 Bil


 On Sunday, February 25, 2024 at 9:51:00 PM UTC Neville Davis wrote:

> I have a Pi4 with external SSD and I did exactly what Tom has 
> suggested without any problems.
>
> I have done this every time I have had a new hardware config to ensure 
> all is well.
>
> Nev
>
> On Monday, February 26, 2024 at 1:02:08 AM UTC+10 Tom Keffer wrote:
>
>> Move a temporary database into position, then set it aside when 
>> you're satisfied.
>>
>> On Sun, Feb 25, 2024 at 3:39 AM Bill Petheram  
>> wrote:
>>
>>> I had to reinstall weewx due to a bad system upgrade on a Raspberry 
>>> Pi with an external SSD.
>>>
>>> I wanted to check my installation was OK. I found that weewx started 
>>> to read data from my station before I was sure everything was setup 
>>> properly.
>>>
>>> It would be nice to be able to turnoff data download at startup to 
>>> check that the installation works OK and files are in the correct 
>>> positions. Then turn on data loading.
>>>
>>> This I guess is less of a problem on Rpi 4 as you can boot from USB. 
>>> I am using Rpi 3B so I have to use symbolic links.
>>>
>>> -- 
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/38bba562-b306-4d76-86f6-7ebc31bad1bfn%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+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/ec2c7968-5801-4b15-a80f-a386b3aac967n%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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/b6925f28-8a42-4f33-bbb9-4d6509585b78n%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/6bb031fb-be0a-4311-a04d-4b9ba08c99ffn%40googlegroups.com.

Re: [weewx-user] Broken installation after upgrade to v5.0.2

[vince]

If you're python 3.7 on the raspi os, you are running an old debian-10 
based system which although it's as patched up as it can be, it's not 
really current.  I have an old pi running that os and my python3 is 3.7.3 
FWIW.  But the underlying problem is you likely didn't get something quite 
right in compiling your own python 3.9 version. Hopefully your driver 
author can tweak things so you can use the system python version.

Don't sweat venv if you use a dpkg package of weewx.

On Thursday, February 29, 2024 at 11:42:13 PM UTC-8 fLsh wrote:

> Yeah I even had problems creating the venv environment with 3.9 and that 
> worked in the past with other software on 3.7.
> But I have a Debian Package installation and don't want to lose all my 
> changes so I am hoping that I will get it to work with python 3.7 and new 
> driver version.
> Or is venv a must-have on weewx 5? And will install also work with pipx? I 
> remember cloudy that I had problems with pip in the past and solved it by 
> using pipx.
>
> Tom Keffer schrieb am Donnerstag, 29. Februar 2024 um 21:24:31 UTC+1:
>
>> Not sure what's going on there, but it may have something to do with 
>> attempting to install as root. Try installing as an unprivileged user, say 
>> "pi".
>>
>> $ *su - pi*
>> $ *whoami*
>> pi
>> $ *cd*
>> $ *python3.9 -m venv weewx-venv*
>> $ *source weewx-venv/bin/activate*
>> $ *python3.9 -m pip install weewx*
>> $ *weectl station create*
>> *...*
>> $ *weectl extension install 
>>  
>> https://github.com/michael-slx/weewx-weatherlink-live/releases/download/v1.1.3/weewx-weatherlink-live-v1.1.3.tar.xz
>>  
>> *
>> $ *weectl extension list*
>> Using configuration file /home/pi/weewx-data/weewx.conf
>> Extension NameVersion   Description
>> weatherlink-live  1.1.3 WeeWX driver for Davis WeatherLink Live.
>>
>> -tk
>>
>>
>>
>>
>>
>>
>> On Thu, Feb 29, 2024 at 11:44 AM fLsh  wrote:
>>
>>> Author of the driver suggested to use Python 3.9 which I installed and 
>>> now I get a different error:
>>> Feb 29 19:57:12 loxberry systemd[1]: Started WeeWX.
>>> Feb 29 19:57:12 loxberry weewxd[30842]: Traceback (most recent call 
>>> last):
>>> Feb 29 19:57:12 loxberry weewxd[30842]: File 
>>> "/usr/share/weewx/weewxd.py", line 18, in 
>>> Feb 29 19:57:12 loxberry weewxd[30842]: import configobj
>>> Feb 29 19:57:12 loxberry weewxd[30842]: ModuleNotFoundError: No module 
>>> named 'configobj'
>>> Feb 29 19:57:12 loxberry systemd[1]: weewx.service: Main process exited, 
>>> code=exited, status=1/FAILURE
>>> Feb 29 19:57:12 loxberry systemd[1]: weewx.service: Failed with result 
>>> 'exit-code'.
>>>
>>> Installation of Python3.9 was by following this: 
>>> https://itheo.tech/install-python-39-on-raspberry-pi
>>> I don't know how to install configobj. I am having a debian installation 
>>> (at least I think I have) and in the docs there are no dependencies listed.
>>> In the git docs there is installation mentioned:
>>> python3 -m pip install CT3 python3 -m pip install configobj python3 -m 
>>> pip install Pillow
>>>
>>> failed: 
>>> root@loxberry:~# python3 -m pip install configobj 
>>> ERROR: Exception:
>>> Traceback (most recent call last):
>>> File 
>>> "/usr/lib/python3.9/site-packages/pip/_internal/cli/base_command.py", line 
>>> 228, in _main
>>> status = self.run(options, args)
>>> File 
>>> "/usr/lib/python3.9/site-packages/pip/_internal/cli/req_command.py", line 
>>> 182, in wrapper
>>> return func(self, options, args)
>>> File 
>>> "/usr/lib/python3.9/site-packages/pip/_internal/commands/install.py", line 
>>> 272, in run
>>> session = self.get_default_session(options)
>>> File 
>>> "/usr/lib/python3.9/site-packages/pip/_internal/cli/req_command.py", line 
>>> 80, in get_default_sess
>>> ion
>>> self._session = self.enter_context(self._build_session(options))
>>> File 
>>> "/usr/lib/python3.9/site-packages/pip/_internal/cli/req_command.py", line 
>>> 90, in _build_session
>>> session = PipSession(
>>> File 
>>> "/usr/lib/python3.9/site-packages/pip/_internal/network/session.py", line 
>>> 249, in __init__
>>> self.headers["User-Agent"] = user_agent()
>>> File 
>>> "/usr/lib/python3.9/site-packages/pip/_internal/network/session.py", line 
>>> 132, in user_agent
>>> zip(["name", "version", "id"], distro.linux_distribution()),
>>> File "/usr/lib/python3.9/site-packages/pip/_vendor/distro.py", line 125, 
>>> in linux_distribution
>>> return _distro.linux_distribution(full_distribution_name)
>>> File "/usr/lib/python3.9/site-packages/pip/_vendor/distro.py", line 681, 
>>> in linux_distribution
>>> self.version(),
>>> File "/usr/lib/python3.9/site-packages/pip/_vendor/distro.py", line 741, 
>>> in version
>>> self.lsb_release_attr('release'),
>>> File "/usr/lib/python3.9/site-packages/pip/_vendor/distro.py", line 903, 
>>> in lsb_release_attr
>>> return self._lsb_release_info.get(attribute, '')
>>> File 

Re: [weewx-user] Broken installation after upgrade to v5.0.2

[vince]

That's very odd. Are you running a very unusual or very ancient os on your 
pi ?

I don't think I've ever seen lsb_release 'fail' but I recall some os didn't 
have that command years ago

What do the following commands return when you run them from the shell ?

   - lsb_release -a
   - cat /etc/os-release
   - cat /etc/debian_version
   - uname -a
   - cat /boot/issue.txt


On Thursday, February 29, 2024 at 11:44:39 AM UTC-8 fLsh wrote:

> Author of the driver suggested to use Python 3.9 which I installed and now 
> I get a different error:
> Feb 29 19:57:12 loxberry systemd[1]: Started WeeWX.
> Feb 29 19:57:12 loxberry weewxd[30842]: Traceback (most recent call last):
> Feb 29 19:57:12 loxberry weewxd[30842]: File "/usr/share/weewx/weewxd.py", 
> line 18, in 
> Feb 29 19:57:12 loxberry weewxd[30842]: import configobj
> Feb 29 19:57:12 loxberry weewxd[30842]: ModuleNotFoundError: No module 
> named 'configobj'
> Feb 29 19:57:12 loxberry systemd[1]: weewx.service: Main process exited, 
> code=exited, status=1/FAILURE
> Feb 29 19:57:12 loxberry systemd[1]: weewx.service: Failed with result 
> 'exit-code'.
>
> Installation of Python3.9 was by following this: 
> https://itheo.tech/install-python-39-on-raspberry-pi
> I don't know how to install configobj. I am having a debian installation 
> (at least I think I have) and in the docs there are no dependencies listed.
> In the git docs there is installation mentioned:
> python3 -m pip install CT3 python3 -m pip install configobj python3 -m pip 
> install Pillow
>
> failed: 
> root@loxberry:~# python3 -m pip install configobj 
> ERROR: Exception:
> Traceback (most recent call last):
> File "/usr/lib/python3.9/site-packages/pip/_internal/cli/base_command.py", 
> line 228, in _main
> status = self.run(options, args)
> File "/usr/lib/python3.9/site-packages/pip/_internal/cli/req_command.py", 
> line 182, in wrapper
> return func(self, options, args)
> File "/usr/lib/python3.9/site-packages/pip/_internal/commands/install.py", 
> line 272, in run
> session = self.get_default_session(options)
> File "/usr/lib/python3.9/site-packages/pip/_internal/cli/req_command.py", 
> line 80, in get_default_sess
> ion
> self._session = self.enter_context(self._build_session(options))
> File "/usr/lib/python3.9/site-packages/pip/_internal/cli/req_command.py", 
> line 90, in _build_session
> session = PipSession(
> File "/usr/lib/python3.9/site-packages/pip/_internal/network/session.py", 
> line 249, in __init__
> self.headers["User-Agent"] = user_agent()
> File "/usr/lib/python3.9/site-packages/pip/_internal/network/session.py", 
> line 132, in user_agent
> zip(["name", "version", "id"], distro.linux_distribution()),
> File "/usr/lib/python3.9/site-packages/pip/_vendor/distro.py", line 125, 
> in linux_distribution
> return _distro.linux_distribution(full_distribution_name)
> File "/usr/lib/python3.9/site-packages/pip/_vendor/distro.py", line 681, 
> in linux_distribution
> self.version(),
> File "/usr/lib/python3.9/site-packages/pip/_vendor/distro.py", line 741, 
> in version
> self.lsb_release_attr('release'),
> File "/usr/lib/python3.9/site-packages/pip/_vendor/distro.py", line 903, 
> in lsb_release_attr
> return self._lsb_release_info.get(attribute, '')
> File "/usr/lib/python3.9/site-packages/pip/_vendor/distro.py", line 556, 
> in __get__
> ret = obj.__dict__[self._fname] = self._f(obj)
> File "/usr/lib/python3.9/site-packages/pip/_vendor/distro.py", line 1014, 
> in _lsb_release_info
> stdout = subprocess.check_output(cmd, stderr=devnull)
> File "/usr/lib/python3.9/subprocess.py", line 420, in check_output
> return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
> File "/usr/lib/python3.9/subprocess.py", line 524, in run
> raise CalledProcessError(retcode, process.args,
> subprocess.CalledProcessError: Command '('lsb_release', '-a')' returned 
> non-zero exit status 1.
> Traceback (most recent call last): 
> File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main 
> return _run_code(code, main_globals, None, 
> File "/usr/lib/python3.9/runpy.py", line 87, in _run_code 
> exec(code, run_globals) 
> File "/usr/lib/python3.9/site-packages/pip/__main__.py", line 26, in 
>  
> sys.exit(_main()) 
> File "/usr/lib/python3.9/site-packages/pip/_internal/cli/main.py", line 
> 75, in main 
> return command.main(cmd_args) 
> File "/usr/lib/python3.9/site-packages/pip/_internal/cli/base_command.py", 
> line 121, in main 
> return self._main(args) 
> File "/usr/lib/python3.9/site-packages/pip/_internal/cli/base_command.py", 
> line 265, in _main 
> self.handle_pip_version_check(options) 
> File "/usr/lib/python3.9/site-packages/pip/_internal/cli/req_command.py", 
> line 149, in handle_pip_vers
> ion_check 
> session = self._build_session( 
> File "/usr/lib/python3.9/site-packages/pip/_internal/cli/req_command.py", 
> line 90, in _build_session 
> session = PipSession( 
> File "/usr/lib/python3.9/site-packages/pip/_internal/network/session.py", 
> line 249, in