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

[Graham Eddy]

i replaced my then-18yo cracked & peeling solar panel with a nice new one - 
just required plugging panel’s lead into ISS
⊣GE⊢

> On 23 Apr 2024, at 2:00 AM, vince  wrote:
> 
> perhaps a solar panel ($55) will handle the data problems, but I'd suggest 
> doing just the battery first to see.

-- 
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/12531242-5DFA-4A81-8F95-EA75CFC5471B%40geddy.au.

Re: [weewx-user] Launching Weewx

[Graham Eddy]

i interpreted the suggestion as making it the default that logging is turned on.
this is self-correcting: when the user has learnt enough to turn logging off, 
they can.
place the instruction how in the documentation that they should have read but 
did not (or did not understand at the time).
i like the idea.
cheers
⊣GE⊢

> On 13 Apr 2024, at 1:05 AM, Tom Keffer  wrote:
> 
> Yes, you can leave it on. It will mean a lot of log entries, but storage is 
> cheap these days. 
> 
> 
> 
> On Fri, Apr 12, 2024 at 6:43 AM DR  > wrote:
>> Tom,
>> 
>> THE most often made comment from the developers is to turn on debug and 
>> then furnish the log.
>> 
>> Question:  Is there a down side to just leaving debug on? Doesn't the 
>> buffer for it just overwrite, and not cause the program to stop once it 
>> is full?  I know that the SD cards don't seem to have the problem with 
>> exceeding their write cycles, so saving the writes to the card doesn't 
>> seem to be as much of a factor.  And I don't gather that a performance 
>> hit of doing all that logging is much of a factor.
>> 
>> 
>> I'm for neat, efficient, focused code, but until an installation has run 
>> perfectly for a few weeks, can we just leave Debug on for awhile?  Just 
>> curious.
>> 
>> Dale
>> 
>> 
>> -- 
>> 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/14e96a89-da15-41de-9414-86e27b5c6119%40gmail.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/CAPq0zECORYCDTMYp%3D9d0TvZ%2BLycV%2Be7Pv9c3EChv-YDt_TM-6g%40mail.gmail.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0328551F-4670-413A-9DF3-93514F08F0BB%40geddy.au.

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

[Graham Eddy]

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) 
>  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) 
>  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
>  
> .

-- 

Re: [weewx-user] MQTTSubscribe and paho mqtt heads up

[Graham Eddy]

i wrapped paho mqtt a few years ago, but not implementing whole interface.
i wote a bunch of apps on top of my wrapper, one being my own weewx mqtt 
service/driver, other apps are various mqtt producers and consumers

thanks for the heads-up on the mqtt interface change.
it prompted me to polish my wrapper a bit, with things i learnt over last few 
years.
one is to put json encoding/decoding at the heart of the wrapper - i expose 
python objects rather than mqtt messages, and the python objects are converted 
to json (strings) in the wrapper to/from the mqtt wire

i’ve yet to find a use for clean_session=false.
cheers
⊣GE⊢

> On 15 Mar 2024, at 10:57 am, bell...@gmail.com  wrote:
> 
> Just a quick update.
> I’m happy with this approach, but eventually V1 API support will be removed. 
> Ideally this will be long after V1 clients are gone. But, I’ve been burnt 
> once…. So, I’m implementing the approach below.
> I’m going to use the factory pattern. I already had a class ‘wrapping’ paho 
> mqtt. I will now have a base class that implements all of the logic. I will 
> have subclasses as necessary for the different versions of paho mqtt. These 
> subclasses will interact with paho mqtt and pass data to the base class to do 
> the real work. I’ll have a factory to provide the appropriate class to 
> interact with paho mqtt.
> Hopefully this will insulate a bit from breaking changes, or at least make it 
> easier to react to them.
> rich
> 
> On Sunday 11 February 2024 at 16:49:25 UTC-5 bell...@gmail.com wrote:
>> I've pretty much settled on this approach. Minimally tested
>> 
>> try:
>> callback_api_version = mqtt.CallbackAPIVersion.VERSION1
>> self.client = 
>> mqtt.Client(callback_api_version=callback_api_version,
>> client_id=mqtt_options['clientid'],
>> userdata=self.userdata,
>> 
>> clean_session=mqtt_options['clean_session'])
>> except AttributeError:
>> self.client = mqtt.Client(client_id=mqtt_options['clientid'],
>> userdata=self.userdata,
>> 
>> clean_session=mqtt_options['clean_session'])
>> 
>> rich
>> On Sunday 11 February 2024 at 15:21:58 UTC-5 matthew wall wrote:
>>> On Sunday, February 11, 2024 at 1:37:20 PM UTC-5 bell...@gmail.com <> wrote:
>>> It currently will not work with paho mqtt 2.0.0 or higher.
>>> 
>>> rich, i too am interested in what you learn, as i will probably have to 
>>> update weewx-mqtt as well. 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/8b3fba7b-dfae-4105-8138-7381e5697017n%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/96563991-9D76-4812-B101-FF1FB2A29BA6%40geddy.au.

Re: [weewx-user] [StdCalibrate][[Corrections]] check if obs_type is present

[Graham Eddy]

oops, python syntax would be: expr if ops_tye in globals() else None
⊣GE⊢

> On 9 Mar 2024, at 10:31 am, Graham Eddy  wrote:
> 
> i think ' if obs_type in globals() then expr else None ' would work
> ⊣GE⊢
> 
>> On 9 Mar 2024, at 9:13 am, 'michael.k...@gmx.at' via weewx-user 
>>  wrote:
>> 
>> I think I remember that this has been asked before, how to check with an 
>> expression in Corrections, if an obs_type is present?
>> 
>> -- 
>> 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 
>> <mailto:weewx-user+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/ae1bbcf8-23b1-475e-8749-62286df24fb0n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/ae1bbcf8-23b1-475e-8749-62286df24fb0n%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/0507D046-7EED-4A96-8F28-038B70BECEC7%40geddy.au.

Re: [weewx-user] [StdCalibrate][[Corrections]] check if obs_type is present

[Graham Eddy]

i think ' if obs_type in globals() then expr else None ' would work
⊣GE⊢

> On 9 Mar 2024, at 9:13 am, 'michael.k...@gmx.at' via weewx-user 
>  wrote:
> 
> I think I remember that this has been asked before, how to check with an 
> expression in Corrections, if an obs_type is present?
> 
> -- 
> 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/ae1bbcf8-23b1-475e-8749-62286df24fb0n%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/799A8DBC-98F3-4CFF-87BB-869C3ED911EC%40geddy.au.

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

[Graham Eddy]

Jsonpath is good for plucking specific values on the subscribe/inward side, but 
it doesn’t help with the publish/outward side (or at least i couldn’t think of 
one). i am still using the eval(expr, weewx-packet or json-message) approach in 
my mqtt implementation
⊣GE⊢

> On 7 Mar 2024, at 11:05 am, Rich Bell  wrote:
> 
> Cool. I’ll check it out. 
> Thanks for the link!
> 
> On Wed, Mar 6, 2024 at 6:33 PM 'Ian Millard' via weewx-user 
> mailto:weewx-user@googlegroups.com>> wrote:
>> FWIW here you can find a very good online json path finder and validator 
>> which is very useful in helping to work out a parsing scheme which can be 
>> adapted for various computer languages: -
>> 
>> JSONPath Finder and Evaluator
>> site24x7.com
>> 
>>  JSONPath 
>> Finder and Evaluator 
>> 
>> site24x7.com  
>>  
>> 
>> 
>>> On 6 Mar 2024, at 21:59, Rich Bell >> > wrote:
>>> 
>>> I have not tried parsing this via MQTTSubscribe, but I have my doubts that 
>>> it currently handles it.
>>> rich
>>> 
>>> On Wed, Mar 6, 2024 at 3:33 PM vince >> > wrote:
 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
  
 .
>>> 
>>> 
>> 
>>> -- 
>>> You received 

Re: [weewx-user] Upgrade to 5.0 from 4.10 the Graphs are not being created

[Graham Eddy]

your archive interval is set to 10 mins, and the log is truncated just where it 
started getting interesting. collect log data for two complete cycles at least, 
in your case 20 mins
⊣GE⊢

> On 5 Mar 2024, at 8:03 pm, Francis Greaves  wrote:
> 
> Thanks Tom for the suggestions.
> I upgraded to 5.0.2 and rebooted to be on the safe side.
> I noticed that the user running the service is now weewx so I changed the 
> permissions on the graphs folder to this: 
> drwxrwsr-x weewx weewx  
> 
> But the graphs are not being updated. They are still dated 1st March when I 
> did the upgrade from version 4.10
> 
> I attach the log as you suggest and my config file.
> 
> 
> On Monday 4 March 2024 at 18:48:35 UTC Tom Keffer wrote:
>> First suggestion is to update to v5.0.2. Version 5.0.0 has a serious bug in 
>> it. There have also been some subtle bug fixes in how permissions are 
>> handled.
>> 
>> When you're done, double check that /etc/systemd/system/weewx.service has 
>> the user set as you expect. Also, check /var/www/html permissions.
>> 
>> If you still have problems after that, set debug=1, restart weewxd, post the 
>> log through the first reporting cycle.
>> 
>> -tk
>> 
>> On Mon, Mar 4, 2024 at 10:41 AM Francis Greaves > 
>> wrote:
>>> I am using a Raspberry Pi running Raspbian 10 (buster). and a Vantage Pro 2 
>>> Station.
>>> I upgraded my Pi and Weewx upgrade to version 5. on 1st March.
>>> The settings in the config file remain unchanged. In particular the 
>>> location of the HTML folder is the same, and the permissions are 775 for 
>>> root:root on that folder.
>>> I have kept the system running as root user.
>>> Weewx is working (I changed to systemd service startup today) the data is 
>>> downloaded.
>>> I am not getting any graphs created.
>>> I have looked through the documentation, but I cannot find out why.
>>> I have set the debug to level 1 and enabled log_success as well as 
>>> log_failure
>>> I attach the Log File which shows no errors.
>>> 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+...@googlegroups.com <>.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/d09dbae9-dce8-46d2-8d05-6a773a16da71n%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/4b739bbf-777a-4082-b551-f0524c94b1c3n%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/AD3D3A89-18F1-4C89-81F7-FFD4A062BDA6%40geddy.au.

Re: [weewx-user] leap year and span

[Graham Eddy]

“month” is a fuzzy measure, not precise. it is not surprising that arithmetic 
with fuzzy numbers produces fuzzy numbers.
what *is* surprising is that people find the above surprising

same as network distributed time - given the variable time it takes to transfer 
a “time” to another place, we all agree that two such “time” values are 
considered “equal” if their difference is within a workable tolerance.
⊣GE⊢

> On 1 Mar 2024, at 8:12 pm, 'michael.k...@gmx.at' via weewx-user 
>  wrote:
> 
> "What is 30 March minus one month? By this solution, it should be 28 Feb.
> So then what is 29 March minus one month? Also 28 Feb? And so would 28 March 
> minus a month. So, "one month earlier" for three days in a row leads to the 
> same date. That doesn't seem right."
> 

-- 
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/0CAA3340-F31E-4B0B-84D3-BCF8CFF87E3C%40geddy.au.

Re: [weewx-user] Two of Same/Similar Model AcuRite 5n1 on Single Host - Station Identification Conflict?

[Graham Eddy]

i tried proxmox on RPi 4 briefly but it was too unstable for a reliable weather 
station - proxmox (pimox) is not supported on RPi and known to have problems 
and limitations (don’t get me started on overlay driver!)

proxmox 8 runs extremely well on bookworm on my mac mini. i pass through a 
usb-serial adapter to a container running several instances of weewx; my 
adapter is actually two serial ports not one, but i happily pass through two 
devices from the one usb port into one container. for encapsulation reasons i 
do not want and have not tried management of serial ports in a second container
(yes, i could have a container for each weewx instance, but i have some 
co-dependencies between the instances that make it easier to treat as a group 
e.g. shared venv, ‘master’ report that binds to all the instance databases, …)
mqtt broker has a container

on mac/proxmox i have had one glitch where the passthrough broke - the perms 
for the pass-through devices suddenly set to 000 - but until it happens again i 
don’t have a good handle on it. rebooting the container did not work, rebooting 
proxmox did work, i was too focussed on getting the station up to properly 
analyse (these things only happen at very interesting data-gathering moments 
such as the peaks of storms…)
⊣GE⊢

> On 25 Feb 2024, at 10:46 am, vince  wrote:
> 
> Not a proxmix user but this link might be worth a read 
> https://www.wundertech.net/how-to-pass-through-usb-devices-in-proxmox/

-- 
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/FC2B1718-DB34-42C6-950F-0859F308D0E6%40geddy.au.

Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

[Graham Knights]

I've been running weewx on a RPi 3B+ for just over 5 years, but after a 
couple of other pi's died for various reasons (SD card being one of them), 
I've moved it to a debian install on a VM in a Windows 10 Pro machine (runs 
my automation server).  Hardware is a Lenovo ThinkCentre M700 Tiny which I 
find perfect for running a couple of small linux VM's on it.  Low power, 
tiny, quiet, and versatile, and Lenovo hardware has been good to me over 
the years. Machines are cheap to find on ebay/amazon, probably less than a 
new Pi by the time you add all the parts.

On Friday, February 23, 2024 at 9:46:42 AM UTC-8 vince wrote:

> If I was starting clean 'today', I would probably just throw $125 at it 
> and get one of those little beelink boxes amazon sells and toss linux on it.
>
> But to answer - currently on a 4GB pi4 to sd card for 2+ years with no 
> issues.
>
> Stability issues on a pi are almost always bad power supply these days. 
>  I've never had a micro-sd fail on a pi3, 3+, 4, or pi5.  Never.   I did 
> burn a 'lot' of big sd cards on the old modelB over the years but again 
> that was related to either (a) cheapo cards or (b) cheapo power adaptors 
> not on surge suppressors.  My one remaining modelB is still happily 
> shooting my timelapse snaps for over a decade now.
>
> I do make one change to the pi setups to protect the sd card.  I mount 
> some filesystems as tmpfs so the sd can't be hammered by log writes by 
> appending this to /etc/stab
>
> # put logs and tmp dirs in ramdisk too ---
> tmpfs   /tmptmpfs   
> defaults,nosuid,mode=0755,nodev,noatime   0   0
> tmpfs   /var/logtmpfs   
> defaults,nosuid,mode=0755,nodev,noatime   0   0
> tmpfs   /var/tmptmpfs   
> defaults,nosuid,mode=0755,nodev,noatime   0   0
> #-
>
> Yes - if I reboot I lose the system logs.  But I basically never reboot.
>
> I might add that I do install rsyslog and the matching logrotate.d and 
> rsyslog.d files from util/ to my v5 setup, so weewx logs to under 
> /var/log/weewx in that tmpfs partition, so I just run debug=1 here because 
> it's not going to touch the actual sd card.  Super stable.
>
>

-- 
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/e01b98c9-b636-45e2-ae7d-11fbf9ebff38n%40googlegroups.com.

[weewx-user] Interceptor (acurite) on weewx > v5.0.1 fix

[Graham Knights]

For others coming here with issues after upgrading to 5.0.1 or greater, my 
interceptor -> acurite hub was no longer working due to weewx no longer 
being run as root and thus being denied permission to port 80. Here is my 
solution for getting the interceptor driver working with the fewest 
workarounds:

Ensure weewx is disabled:
> sudo systemctl stop weewx

Install authbind:
> sudo apt install authbind

Configure authbind to allow weewx:
> sudo touch /etc/authbind/byport/80
> sudo chown weewx /etc/authbind/byport/80
> sudo chmod 777 /etc/authbind/byport/80

Modifiy /etc/weewx/systemd/weewx.service as follows (changes in bold):
[Service]
ExecStart=*authbind --deep* weewxd /etc/weewx/weewx.conf

Reload systemd manager config:
> sudo systemctl daemon-reload

Start weewx:
> sudo systemctl start weewx

Confirm no more errors:
> sudo tail -f /var/log/syslog

It took me forever to find the current weewx.service file as there are 
multiple copies scattered in several directories, and depending how you 
installed weewx the correct/currently used file may be in another directory 
so you may need to hunt and edit until the error stops.

Hopefully this helps others having similar issues!

-- 
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/87c1f9fe-4fd2-48e4-b6a5-2126e05dfe1dn%40googlegroups.com.

Re: [weewx-user] MQTTSubscribe and paho mqtt heads up

[Graham Knights]

I just migrated my install to a new machine and was pulling my hair out 
trying to figure this out until I saw this today, thanks @gary for figuring 
this out.  I've edited the weewx wiki to direct new setups to install the 
v1.6.1 paho-mqtt until the original mqtt extension is updated.  

On Sunday, February 11, 2024 at 5:04:01 PM UTC-8 bell...@gmail.com wrote:

> FWIW 
> Successfully ran integration tests on Ubuntu 22, python 3.12 with 
> paho-mqtt v2.0.0 and v1.6.1.
>
> On Sunday 11 February 2024 at 16:49:25 UTC-5 bell...@gmail.com wrote:
>
>> I've pretty much settled on this approach. Minimally tested
>>
>> try:
>> callback_api_version = mqtt.CallbackAPIVersion.VERSION1
>> self.client = 
>> mqtt.Client(callback_api_version=callback_api_version,
>> client_id=mqtt_options['clientid'],
>> userdata=self.userdata,
>> 
>> clean_session=mqtt_options['clean_session'])
>> except AttributeError:
>> self.client = mqtt.Client(client_id=mqtt_options['clientid'],
>> userdata=self.userdata,
>> 
>> clean_session=mqtt_options['clean_session'])
>>
>> rich
>> On Sunday 11 February 2024 at 15:21:58 UTC-5 matthew wall wrote:
>>
>>> On Sunday, February 11, 2024 at 1:37:20 PM UTC-5 bell...@gmail.com 
>>> wrote:
>>>
>>> It currently will not work with paho mqtt 2.0.0 or higher.
>>>
>>>
>>> rich, i too am interested in what you learn, as i will probably have to 
>>> update weewx-mqtt as well. 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/12548e6a-ba98-4d59-9b57-8ed9bb1f860en%40googlegroups.com.

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

[Graham Eddy]

why are you writing into files outside weewx’s area? weewx user is unlikely to 
have perms to do that
⊣GE⊢

> On 11 Feb 2024, at 1:59 am, Ton Karsten  wrote:
> 
> feb 10 15:10:15 raspberrypi weewxd[4548]: ERROR weewx.reportengine: 
> File "/usr/lib/python3.11/shutil.py", line 258, in copyfile
> feb 10 15:10:15 raspberrypi weewxd[4548]: ERROR weewx.reportengine: 
>   with open(dst, 'wb') as fdst:
> feb 10 15:10:15 raspberrypi weewxd[4548]: ERROR weewx.reportengine: 
>    ^^^
> feb 10 15:10:15 raspberrypi weewxd[4548]: ERROR weewx.reportengine: 
>   PermissionError: [Errno 13] Toegang geweigerd: 
> '/var/www/html/favicon.ico’
...
> feb 10 15:10:16 raspberrypi weewxd[4548]: ERROR weewx.reportengine: 
> File "/etc/weewx/bin/user/belchertown.py", line 2817, in run
> feb 10 15:10:16 raspberrypi weewxd[4548]: ERROR weewx.reportengine: 
>   with open(json_filename, mode="w") as jf:
> feb 10 15:10:16 raspberrypi weewxd[4548]: ERROR weewx.reportengine: 
>    ^
> feb 10 15:10:16 raspberrypi weewxd[4548]: ERROR weewx.reportengine: 
>   FileNotFoundError: [Errno 2] Bestand of map bestaat niet: 
> '/var/www/html/json/homepage.json'

-- 
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/74321F96-4821-463F-A133-4B8DFB18EB71%40geddy.au.

[weewx-user] gday from Hobart

[Graham Stevens]

Hi folks, I am frustrated trying to get my acurite weather station on to 
home assistant and also weather underground. I am happy for the basic steps 
so please point in the right direction to start. I will be using a 
raspberry pi 3 I think for now as that is the one I have spare.
Cheers 
Grazza

-- 
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/004adbed-ee0f-4230-88f7-83876deb5673n%40googlegroups.com.

Re: [weewx-user] Another Davis Vantage unable to start concern

[Graham Eddy]

vantage device is on LAN. wireless interface normally not ready until long 
after weewx tries to start, unusual (but not impossible) for ethernet interface 
to be so late. try the ‘loop-on-init = 1’ in weewx.conf, or insert a delay in 
the startup file
⊣GE⊢

> On 6 Feb 2024, at 8:08 am, Neil B  wrote:
> 
> Feb 05 20:54:10 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Opened up 
> ethernet host 192.168.1.249 on port 2. timeout=4.0, tcp_send_delay=0.5

-- 
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/F018B0FD-2319-41C3-88B1-10EC577E47FB%40geddy.au.

Re: [weewx-user] StdCalibrate math question

[Graham Eddy]

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

> On 22 Jan 2024, at 4:19 am, Tom Keffer  wrote:
> 
> Yes, of course. Just substitute "**" for "^" so it's a Python expression. Or, 
> use the math function pow().
> 
> On Sun, Jan 21, 2024 at 8:14 AM Steve2Q  > wrote:
>> I have a calibration curve for my outdoor humidity sensor that includes 
>> division and an exponent. The formula is : OutHumidity = 
>> 92.2/(1+(1/(OutHumididty/64.6)^3.47))  Can this be handled by StdCalibrate?
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/9e1d1a9b-faa3-48f9-8ca1-5cfeb712def9n%40googlegroups.com
>>  
>> .
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEC1L-%3DKXyMTS9oKA%2Bs92%3DpVh2PDrMGAxKsNVp%2BUFHCY0A%40mail.gmail.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9E0668B3-0B83-408A-8C16-2C01863E3287%40geddy.au.

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

[Graham Eddy]

i found putting the db into a RAM disk for the duration helps in these 
situations (i had to do that for a weewx migration some time ago)
⊣GE⊢

> On 19 Jan 2024, at 3:36 pm, 'michael.k...@gmx.at' via weewx-user 
>  wrote:
> 
> Or, to speed things up, do the "calc-missing" on another machine with a more 
> potent CPU.

-- 
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/0EE301A5-5FC2-4461-9AD4-67D2678ED9FA%40geddy.au.

Re: [weewx-user] Database Error Message

[Graham Eddy]

maybe a bit short?
⊣GE⊢

> On 18 Jan 2024, at 11:55 am, Michael Sanphillipo  
> wrote:
> 
> archive_interval = 120

-- 
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/5DAE5F07-0D79-4BC7-A67D-09FA84035018%40geddy.au.

[weewx-user] Re: V5.0.0 available

[Graham Eddy]

many plaudits to tom, matt and gary for V5, navigating the shifting decks 
of python and linux while preserving the long stability of weewx for 
another milestone release.
the software engineers amongst us understand and appreciate the difficulty, 
attention to detail and sheer volume of work - dedication - this entails.

On Monday 15 January 2024 at 9:25:11 am UTC+11 Tom Keffer wrote:

A year in the making, V5 is finally available! Some minor new features, but 
most of the work has been to keep up with the changing world of Python --- 
lots of things have become obsolete (distutils), while others have just 
changed.

-- 
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/02ceaa54-d4db-423d-aabf-ecb65e7d1682n%40googlegroups.com.

Re: [weewx-user] using 'weectl database' → error "No module named 'user'"

[Graham Eddy]

reasonable questions: yes to both, the ‘(venv)’ in the prompt is the clue to 
the first. i showed content of ~weewx/bin because i was asked for it; i knew it 
did not exist, and what was really being asked was for ~weewx/{venv}/bin and 
~weewx/{station}/bin, so i showed those as well

actually running weewx using ~weewx/{station}/weew.conf via systemd is fine, 
and the CLI tools work fine provided i indicate 
—config=/home/weewx/{station}/weewx.conf (except ‘weectl database rebuild-daily 
—config=/home/weewx/{station}/weewx.conf’ does not work) - it’s not my config 
at fault, it is something in the rebuild-daily that barfed on using non-default 
station name. but debugging efforts will go to the release or release candidate 
not this beta, when i migrate.
cheers
⊣GE⊢

> On 9 Jan 2024, at 3:21 pm, vince  wrote:
> 
> Couple things. You need to source your venv/bin/activate to activate your 
> venv before running weectl. And is your weewx data all within 
> /home/weewx/vantage ?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4707A874-A3E4-421B-8D34-9C924EDD0662%40geddy.au.

Re: [weewx-user] using 'weectl database' → error "No module named 'user'"

[Graham Eddy]

just a standard V5 pip installation that otherwise works fine

(venv) graham@wx:/home/weewx$ ls bin
ls: cannot access 'bin': No such file or directory
(venv) graham@wx:/home/weewx$ ls venv/bin
activate   cheetah  pasteurize  pyserial-miniterm  python3.11
activate.csh   cheetah-analyze  pip pyserial-ports weectl
activate.fish  cheetah-compile  pip3python weewxd
Activate.ps1   futurize pip3.11 python3
(venv) graham@wx:/home/weewx$ ls vantage/bin
user
(venv) graham@wx:/home/weewx$ grep WEEWX_ROOT vantage/weewx.conf
WEEWX_ROOT = /home/weewx/vantage
# Where the skins reside, relative to WEEWX_ROOT
# Where the generated reports should go, relative to WEEWX_ROOT
SQLITE_ROOT = %(WEEWX_ROOT)s/archive

you should put *no* effort into debugging b16, that’s what the release 
candidates are for.
i just wanted to know if this weectl error was known so i could fix my data 
now; it will wait until i’ve updated to release or release candidate.
cheers
⊣GE⊢

> On 9 Jan 2024, at 2:36 am, Tom Keffer  wrote:
> 
> Do you have a value for WEEWX_ROOT in the configuration file 
> /home/weewx/vantage/weewx.conf?
> 
> Also, what is in /home/weewx/bin?
> 
> I'm reluctant to put too much energy in debugging b16, because a lot of how 
> WEEWX_ROOT is handled has changed since then. If you're still having 
> problems, upgrade to the current rc3.
> 
> -tk
> 
> On Mon, Jan 8, 2024 at 4:31 AM Graham Eddy  <mailto:g...@geddy.au>> wrote:
>> running weewx 5.0.0b16 in production quite happily for weeks - it works fine.
>> i needed to delete a bad barometer reading from station called ‘vantage’, so 
>> i stopped unit weewx@vantage, set the value to None, then tried to rebuild 
>> the daily database → following error:
>> 
>> (venv) weewx@wx:~$ weectl database rebuild-daily 
>> --config=/home/weewx/vantage/weewx.conf
>> The configuration file /home/weewx/vantage/weewx.conf will be used.
>> Traceback (most recent call last):
>>   File "/home/weewx/venv/bin/weectl", line 8, in 
>> sys.exit(main())
>>  ^^
>>   File "/home/weewx/venv/lib/python3.11/site-packages/weectl.py", line 69, 
>> in main
>> namespace.func(namespace)
>>   File 
>> "/home/weewx/venv/lib/python3.11/site-packages/weectllib/database_cmd.py", 
>> line 307, in rebuild_daily
>> weectllib.database_actions.rebuild_daily(namespace.config,
>>   File 
>> "/home/weewx/venv/lib/python3.11/site-packages/weectllib/database_actions.py",
>>  line 91, in rebuild_daily
>> config_path, config_dict, database_name = weectllib.prepare(config_path, 
>> db_binding, dry_run)
>>   
>> ^^^
>>   File 
>> "/home/weewx/venv/lib/python3.11/site-packages/weectllib/__init__.py", line 
>> 86, in prepare
>> manager_dict = weewx.manager.get_manager_dict_from_config(config_dict,
>>^^^
>>   File "/home/weewx/venv/lib/python3.11/site-packages/weewx/manager.py", 
>> line 886, in get_manager_dict_from_config
>> manager_dict['schema'] = weeutil.weeutil.get_object(schema_name)
>>  ^^^
>>   File "/home/weewx/venv/lib/python3.11/site-packages/weeutil/weeutil.py", 
>> line 1398, in get_object
>> module = importlib.import_module(module_name)
>>  
>>   File "/usr/lib/python3.11/importlib/__init__.py", line 126, in 
>> import_module
>> return _bootstrap._gcd_import(name[level:], package, level)
>>
>>   File "", line 1206, in _gcd_import
>>   File "", line 1178, in _find_and_load
>>   File "", line 1128, in _find_and_load_unlocked
>>   File "", line 241, in 
>> _call_with_frames_removed
>>   File "", line 1206, in _gcd_import
>>   File "", line 1178, in _find_and_load
>>   File "", line 1128, in _find_and_load_unlocked
>>   File "", line 241, in 
>> _call_with_frames_removed
>>   File "", line 1206, in _gcd_import
>>   File "", line 1178, in _find_and_load
>>   File "", line 1142, in _find_and_load_unlocked
>> ModuleNotFoundError: No module named 'user'
>> 
>> didn’t find this error searching in forum archive. is it a known error? is 
>> it fixed in later release?
>> ⊣GE⊢
>>

[weewx-user] using 'weectl database' → error "No module named 'user'"

[Graham Eddy]

running weewx 5.0.0b16 in production quite happily for weeks - it works fine.
i needed to delete a bad barometer reading from station called ‘vantage’, so i 
stopped unit weewx@vantage, set the value to None, then tried to rebuild the 
daily database → following error:

(venv) weewx@wx:~$ weectl database rebuild-daily 
--config=/home/weewx/vantage/weewx.conf
The configuration file /home/weewx/vantage/weewx.conf will be used.
Traceback (most recent call last):
  File "/home/weewx/venv/bin/weectl", line 8, in 
sys.exit(main())
 ^^
  File "/home/weewx/venv/lib/python3.11/site-packages/weectl.py", line 69, in 
main
namespace.func(namespace)
  File 
"/home/weewx/venv/lib/python3.11/site-packages/weectllib/database_cmd.py", line 
307, in rebuild_daily
weectllib.database_actions.rebuild_daily(namespace.config,
  File 
"/home/weewx/venv/lib/python3.11/site-packages/weectllib/database_actions.py", 
line 91, in rebuild_daily
config_path, config_dict, database_name = weectllib.prepare(config_path, 
db_binding, dry_run)
  
^^^
  File "/home/weewx/venv/lib/python3.11/site-packages/weectllib/__init__.py", 
line 86, in prepare
manager_dict = weewx.manager.get_manager_dict_from_config(config_dict,
   ^^^
  File "/home/weewx/venv/lib/python3.11/site-packages/weewx/manager.py", line 
886, in get_manager_dict_from_config
manager_dict['schema'] = weeutil.weeutil.get_object(schema_name)
 ^^^
  File "/home/weewx/venv/lib/python3.11/site-packages/weeutil/weeutil.py", line 
1398, in get_object
module = importlib.import_module(module_name)
 
  File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
   
  File "", line 1206, in _gcd_import
  File "", line 1178, in _find_and_load
  File "", line 1128, in _find_and_load_unlocked
  File "", line 241, in _call_with_frames_removed
  File "", line 1206, in _gcd_import
  File "", line 1178, in _find_and_load
  File "", line 1128, in _find_and_load_unlocked
  File "", line 241, in _call_with_frames_removed
  File "", line 1206, in _gcd_import
  File "", line 1178, in _find_and_load
  File "", line 1142, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'user'

didn’t find this error searching in forum archive. is it a known error? is it 
fixed in later release?
⊣GE⊢

-- 
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/2A27FC4D-93D4-445A-B259-92E910BAD8C5%40geddy.au.

Re: [weewx-user] Localization，cn--->zh_cn

[Graham Eddy]

maybe check the font_path in skins.conf, ensure the image generator fonts 
include the simplified chinese symbols
⊣GE⊢

> On 6 Jan 2024, at 2:21 pm, Kranz Liang  wrote:
> 
> I have translated the language files in weewx, converting Traditional Chinese 
> into Simplified Chinese and also adjusted some word usages to better conform 
> with the linguistic habits of users in Simplified Chinese regions. However, 
> after these modifications, I am encountering garbled characters on the 
> display interface and am unable to resolve this issue.

-- 
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/F3365F65-68C7-4762-86D6-386676F4E3D5%40geddy.au.

Re: [weewx-user] Pipe errors etc

[Graham Eddy]

the vantage IP device seems to accept a connection, work for a while, then stop 
responding, then connection is reset → sounds like on device side it seizes up 
and the ip protocol times out; establishing new connection just repeats the 
cycle. the device apparently has been working for years and is now failing → 
sounds like device has broken
⊣GE⊢

> On 5 Dec 2023, at 9:23 am, vince  wrote:
> 
> Just a thought, but when I see "weewx.drivers.vantage: ip-read error: timed 
> out" that makes me think your network is unstable.   From your posts in the 
> thread it 'sounds' like it has been working for years without issues.  Did 
> you change anything on your network ? Did you change any firewall settings on 
> your pi or install something like fail2ban or pihole recently ?

-- 
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/6B5C1B94-55F5-484D-8E8E-3142F471AE4C%40geddy.au.

Re: [weewx-user] Unrecoverable error "no such table: forecast_day_wind"

[Graham Eddy]

suggestions:
 (1) maybe the weekly graph is only being calculated in your 0-5 daily hour 
interval → really failing all the time. try hourly or daily graph to verify it 
works during those & other hours
 (2) maybe another deeper exception is happening which happens to be percolated 
up as sqlError that reports the last sqlite error not this error
⊣GE⊢

> On 16 Nov 2023, at 5:49 pm, 'Michael Waldor' via weewx-user 
>  wrote:
> 
> Normally, it uses the "wx_binding" database binding to do this, which is 
> normally pointed at the "archive" table. For whatever reason, your 
> installation is attempting to do this with the "forecast" table. It could be 
> that you are using the wrong binding, or it could be that the wx_binding is 
> pointing to the "forecast" table.
> 

-- 
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/ADE419CC-6E82-4A5E-B775-43845693D994%40geddy.au.

[weewx-user] Re: Ultrasonic vs Microwave vs Immersion sensors for stream height.

[Graham Eddy]

microwave:
i have the wide beam aligned up/downstream to mitigate its width.
my readings are always larger, not smaller, than they should be. successive 
readings that should be nearly identical can be more than 20% different, and i 
notice a general daily oscillation of about 50% but i could not correlate it 
with temperature or humidity. i think the variation is much larger than can be 
accounted for by random large ripples at the peripehery of the beam (giving 
larger distances) but i will be interested to see if your horn reduces it
⊣GE⊢

> On 11 Nov 2023, at 3:19 pm, Greg Hall  wrote:
> 
> If it really is 78 degr wide, then perhaps that axis could be aligned 
> up/downstream, to avoid bridge pylons and streambank?

-- 
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/35BAC30C-8873-44CF-8CD8-6A478584F873%40geddy.au.

Re: [weewx-user] Storm Rain or Pluviograph function?

[Graham Eddy]

river level sensors:
  * my dragino lorawan ultrasonic sensor has been fine, though it has 
condensation problems (to be fair, it is mounted under a bridge a couple metres 
above normal river level)
  * my dragino lorawan microwave radar has been a failure. i get neither 
accurate nor consistent measurements and can’t see any way to use the readings 
i get
  * my old aquagauge differential pressure sensor - proprietary radio network - 
has worked precisely for years, but is not sold any more. after the failure of 
the microwave sensor experiment, i would like to get a lorawan diff pressure 
sensor but they are too expensive - alternative is another ultrasound sensor
⊣GE⊢

> On 11 Nov 2023, at 12:04 pm, Greg Hall  wrote:
> 
> And yes, the advice that stream gauges tell a fuller story is well taken. 
> We're also evaluating ultrasonic and microwave sensors for this.

-- 
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/A8B843CA-75A4-4EF5-9616-D640B7CCDEB0%40geddy.au.

Re: [weewx-user] Replacement humidity sensor

[Graham Eddy]

just looking at the intention of the code without having read the thread 
[always dangerous!]
i cannot quote the original python text here because unfortunately it was 
reported using a screenshot [please don’t do that]
but note that if extraHumid1 is undefined (not present in packet, as opposed to 
present but with value None) then the assignment fails (outHumidity is 
unchanged). maybe check if it is in locals() instead
⊣GE⊢

> On 9 Nov 2023, at 6:01 am, tadej.j...@gmail.com  
> wrote:
> 
> Still the same ..
> SQL from database:
> 
> 
> Screenshot from config:
> 
> 
> And yes I have stopped and restarted weewxd several times.

-- 
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/837ACBA1-2CEC-454E-A257-2A8C97AAB464%40geddy.au.

Re: [weewx-user] The People's Pluviograph!

[Graham Eddy]

i posted details of my implementation of lorawan river level sensors reporting 
via weewx on this forum about a year (or two?) ago. they are anxiously watched 
by community when we have severe rain events in the region (we flood fairly 
often - you learn to deal with weather extremes)

ditto re measuring the river level not the local rain - flooding can be caused 
by rain way up-river when there is no local rain at all
⊣GE⊢

> On 7 Nov 2023, at 1:39 am, matthew wall  wrote:
> 
> there are a *lot* of people doing this kind of work

-- 
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/89448569-352C-41BB-9CE5-D574867EB948%40geddy.au.

Re: [weewx-user] MQTTSubscribeDriver TLS

[Graham Eddy]

for the record, a reminder:
conf syntax is driven by the [..[ ]..] sections, not by indent.
putting ‘username’ after ‘[[tls]]’ means username is inside [[tls]] section, 
not in parent section (indenting irrelevant)
⊣GE⊢

> On 5 Nov 2023, at 2:34 am, Fjordey  wrote:
> 
> #2 That told me right there that the username and password were not being 
> passed - then looking at my config I see I put the  [[tls]]
> tls_version = tls before the username and password when it should have 
> been after. 

-- 
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/594D4600-C02A-41D5-AEF9-EAB26DDF6227%40geddy.au.

Re: [weewx-user] mosquitto & SSL

[Graham Eddy]

i was expecting log file to show either file not found (misnamed) or permission 
denied (user ‘mosquitto’ not able to read). maybe need to add log_type debug to 
config file to get that message. anyway, looks like you fixed perms problem

note: if you moved (not copied) them from letsencrypt, better put them back 
then copy them, or the cert refresh will get confused
⊣GE⊢

> On 30 Sep 2023, at 12:25 am, Stefan Gliessmann  
> wrote:
> 
> Well - I just moved my certs from the lets encrypt dir to the mosquitto/cert 
> dir and now mosquitto restarted without problems ... :)
> 
> 
> On Fri, Sep 29, 2023 at 3:41 PM Graham Eddy  <mailto:g...@geddy.au>> wrote:
>> try sudo journalctl -u mosquitto -n 50 to see the log messages (or sudo tail 
>> -50 /var/log/mosquitto/* if it puts them there instead)
>> ⊣GE⊢
>> 
>>> On 29 Sep 2023, at 11:35 pm, Stefan Gliessmann >> <mailto:stefan.gliessm...@gmail.com>> wrote:
>>> 
>>> I am trying to get my weather station web presence secure with https://
>>> Therefore, I also need my MQTT server be secure via SSL.
>>> 
>>> I followed the setup by 
>>> https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/
>>> 
>>> I received my certificates from Let's encrypt and edited my mosquitto 
>>> config file accordingly:
>>> 
>>>   GNU nano 6.2 /etc/mosquitto/conf.d/myconfig.conf  
>>> 
>>> persistence false
>>> allow_anonymous true
>>> #allow_zero_length_clientid true
>>> password_file /etc/mosquitto/passwd
>>> acl_file /etc/mosquitto/acl
>>> # mqtt
>>> #listener 1883 localhost
>>> listener 8883
>>> certfile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/cert.pem 
>>> <http://weewx.bz3gfkrlqtrsc3sv.myfritz.net/cert.pem>
>>> cafile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/chain.pem 
>>> <http://weewx.bz3gfkrlqtrsc3sv.myfritz.net/chain.pem>
>>> keyfile 
>>> /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/privkey.pem 
>>> <http://weewx.bz3gfkrlqtrsc3sv.myfritz.net/privkey.pem>
>>> tls_version tlsv1.2
>>> protocol mqtt
>>> # websockets
>>> listener 9001
>>> certfile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/cert.pem 
>>> <http://weewx.bz3gfkrlqtrsc3sv.myfritz.net/cert.pem>
>>> cafile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/chain.pem 
>>> <http://weewx.bz3gfkrlqtrsc3sv.myfritz.net/chain.pem>
>>> keyfile 
>>> /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/privkey.pem 
>>> <http://weewx.bz3gfkrlqtrsc3sv.myfritz.net/privkey.pem>
>>> protocol websockets
>>> 
>>> every time I reboot now mosquitto, I get an error by mosquitto:
>>> 
>>> root@weewx:/# sudo systemctl restart mosquitto.service 
>>> Job for mosquitto.service failed because the control process exited with 
>>> error code.
>>> See "systemctl status mosquitto.service" and "journalctl -xeu 
>>> mosquitto.service" for details.
>>> root@weewx:/# sudo systemctl status mosquitto.service 
>>> × mosquitto.service - Mosquitto MQTT Broker
>>>  Loaded: loaded (/lib/systemd/system/mosquitto.service; enabled; vendor 
>>> preset: enabled)
>>>  Active: failed (Result: exit-code) since Fri 2023-09-29 15:32:19 CEST; 
>>> 1s ago
>>>Docs: man:mosquitto.conf(5)
>>>  man:mosquitto(8)
>>> Process: 542132 ExecStartPre=/bin/mkdir -m 740 -p /var/log/mosquitto 
>>> (code=exited, status=0/SUCCESS)
>>> Process: 542133 ExecStartPre=/bin/chown mosquitto /var/log/mosquitto 
>>> (code=exited, status=0/SUCCESS)
>>> Process: 542134 ExecStartPre=/bin/mkdir -m 740 -p /run/mosquitto 
>>> (code=exited, status=0/SUCCESS)
>>> Process: 542135 ExecStartPre=/bin/chown mosquitto /run/mosquitto 
>>> (code=exited, status=0/SUCCESS)
>>> Process: 542136 ExecStart=/usr/sbin/mosquitto -c 
>>> /etc/mosquitto/mosquitto.conf (code=exited, status=1/FAILURE)
>>>Main PID: 542136 (code=exited, status=1/FAILURE)
>>> CPU: 22ms
>>> 
>>> Sep 29 15:32:19 weewx systemd[1]: mosquitto.service: Scheduled restart job, 
>>> restart counter is at 5.
>>> Sep 29 15:32:19 weewx systemd[1]: Stopped Mosquitto MQTT Broker.
>>> Sep 29 15:32:19 weewx systemd[1]: mosquitto.service: Start request repeated 
>>> too quickly.
>>> Sep 29 15:32:19 weewx systemd[1]: m

Re: [weewx-user] mosquitto & SSL

[Graham Eddy]

try sudo journalctl -u mosquitto -n 50 to see the log messages (or sudo tail 
-50 /var/log/mosquitto/* if it puts them there instead)
⊣GE⊢

> On 29 Sep 2023, at 11:35 pm, Stefan Gliessmann  
> wrote:
> 
> I am trying to get my weather station web presence secure with https://
> Therefore, I also need my MQTT server be secure via SSL.
> 
> I followed the setup by 
> https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/
> 
> I received my certificates from Let's encrypt and edited my mosquitto config 
> file accordingly:
> 
>   GNU nano 6.2 /etc/mosquitto/conf.d/myconfig.conf
>   
> persistence false
> allow_anonymous true
> #allow_zero_length_clientid true
> password_file /etc/mosquitto/passwd
> acl_file /etc/mosquitto/acl
> # mqtt
> #listener 1883 localhost
> listener 8883
> certfile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/cert.pem
> cafile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/chain.pem
> keyfile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/privkey.pem
> tls_version tlsv1.2
> protocol mqtt
> # websockets
> listener 9001
> certfile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/cert.pem
> cafile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/chain.pem
> keyfile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/privkey.pem
> protocol websockets
> 
> every time I reboot now mosquitto, I get an error by mosquitto:
> 
> root@weewx:/# sudo systemctl restart mosquitto.service 
> Job for mosquitto.service failed because the control process exited with 
> error code.
> See "systemctl status mosquitto.service" and "journalctl -xeu 
> mosquitto.service" for details.
> root@weewx:/# sudo systemctl status mosquitto.service 
> × mosquitto.service - Mosquitto MQTT Broker
>  Loaded: loaded (/lib/systemd/system/mosquitto.service; enabled; vendor 
> preset: enabled)
>  Active: failed (Result: exit-code) since Fri 2023-09-29 15:32:19 CEST; 
> 1s ago
>Docs: man:mosquitto.conf(5)
>  man:mosquitto(8)
> Process: 542132 ExecStartPre=/bin/mkdir -m 740 -p /var/log/mosquitto 
> (code=exited, status=0/SUCCESS)
> Process: 542133 ExecStartPre=/bin/chown mosquitto /var/log/mosquitto 
> (code=exited, status=0/SUCCESS)
> Process: 542134 ExecStartPre=/bin/mkdir -m 740 -p /run/mosquitto 
> (code=exited, status=0/SUCCESS)
> Process: 542135 ExecStartPre=/bin/chown mosquitto /run/mosquitto 
> (code=exited, status=0/SUCCESS)
> Process: 542136 ExecStart=/usr/sbin/mosquitto -c 
> /etc/mosquitto/mosquitto.conf (code=exited, status=1/FAILURE)
>Main PID: 542136 (code=exited, status=1/FAILURE)
> CPU: 22ms
> 
> Sep 29 15:32:19 weewx systemd[1]: mosquitto.service: Scheduled restart job, 
> restart counter is at 5.
> Sep 29 15:32:19 weewx systemd[1]: Stopped Mosquitto MQTT Broker.
> Sep 29 15:32:19 weewx systemd[1]: mosquitto.service: Start request repeated 
> too quickly.
> Sep 29 15:32:19 weewx systemd[1]: mosquitto.service: Failed with result 
> 'exit-code'.
> Sep 29 15:32:19 weewx systemd[1]: Failed to start Mosquitto MQTT Broker.
> root@weewx:/# 
> 
> Once I command the certificates out, mosquitto starts up fine.
> 
> I double checked that the certificates can be read by everybody.
> 
> Any clue what else I check for?
> 
> TIA,
> Stefan
> 
> 
> -- 
> 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/0fb5acdb-156e-489c-a3bb-06acfe4381a8n%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/049C6B06-B1C3-4335-A1A3-B690452E44B1%40geddy.au.

Re: [weewx-user] Weewx mqtt

[Graham Eddy]

an item timestamped 21:10:05 belongs to the reporting period after 21:10 - it 
doesn’t matter when the report is actually generated
⊣GE⊢

> On 14 Sep 2023, at 11:35 am, kufuu  wrote:
> 
> I reboot the pi zero-w and seen it didnt add the files to database till it 
> ran the second payload
> 
> 
> Sep 13 21:10:09 zero-wx weewx[532] DEBUG user.MQTTSubscribe: (Driver) 
> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
> retain: 0, payload: b'{"readings": {"pressure": 952.05, "rain": 0, 
> "wind_speed": 0, "temperature": 17.41, "humidity": 90.31, "wind_direction": 
> 90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
> "2023-09-14T01:10:05Z"}'

-- 
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/58E01E41-D861-4364-B941-17B92C84C120%40geddy.au.

Re: [weewx-user] weewx V5 report not updating

[Graham Eddy]

perhaps it was generating all reports, as from a clean slate, and in future it 
could just be incremental and less of an issue
⊣GE⊢

> On 4 Sep 2023, at 12:10 pm, Greg from Oz  wrote:
> 
> I guess it was wdc:
> Sep  3 00:21:24 moonbi weewx[1440347] INFO weewx.cheetahgenerator: Generated 
> 11 files for report WdcReport in 330.15 seconds
> 

-- 
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/13A10622-1DBF-4572-97B4-76EE2EB57FD5%40geddy.au.

Re: [weewx-user] Is WeeWx 5.0 beta stable enough for non-experts to fool around with?

[Graham Eddy]

in V5 i am assuming a single station can be created but separate weewx.conf’s 
used, as in V4 weewx-multi config, with the downside that they share same 
extensions.py i.e. not utilising V5’s design change

in my case, i want same codebase and python modules available to all weewx 
instances but each with own extensions.py, so i have in mind to have a weewx 
user whose home dir has a single venv (shared codebase with pip install), and 
station create each instance (has its own extensions.py)

i can see the case for separate venv for each station (conflicts, independence) 
but i don’t require that
⊣GE⊢

> On 1 Sep 2023, at 12:09 am, Tom Hogland  wrote:
> 
> I'm thinking of moving to v5. I have a Tempest and VP2 setup and running a 
> custom weewx-multi. Seems like two venv setups would be a very simple way to 
> replicate this...

-- 
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/6D6A2E62-C98A-4AD6-B834-92C175516408%40geddy.au.

Re: [weewx-user] Is WeeWx 5.0 beta stable enough for non-experts to fool around with?

[Graham Eddy]

my experiments with multiple instances and topologies have been very smooth 
with pip install - that is quite elegant.
i tried the documented github install and fell on my face, even after working 
out to select V5 to clone. i’m not github-savvy (but i look at the source code 
a lot) so ‘here be dragons’ might be a useful comment in the github install 
notes
⊣GE⊢

> On 31 Aug 2023, at 11:11 am, Tom Keffer  wrote:
> 
> It's pretty stable. Most of the work now is about smoothing out the 
> installation process. 
> 
> -tk
> 
> On Wed, Aug 30, 2023 at 6:07 PM DR  > wrote:
>> I have looked gitHub and see there is a 5.0 beta out there.
>> 
>> 
>> I am wondering if it is stable enough for a casual user to fiddle around 
>> with it before official release, or should only experts be using it now 
>> to test and give feedback to the developers?
>> 
>> 
>> Just curious.  Dale
>> 
>> 
>> -- 
>> 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/98fdaa7f-ab40-26e7-326e-dd958fb6695c%40gmail.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/CAPq0zEBQ8tRZ6Nig-LZAw2xNx9mgqAngwDtXHqD0UBtKavnX4w%40mail.gmail.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/A42B776D-921C-420D-AD50-33F0532C40EC%40geddy.au.

Re: [weewx-user] comma in label in Seasons skin.conf causes failure

[Graham Eddy]

for the forum search record, you can do a lot of stuff (especially using 
services) within one instance of weewx. you only *must* use separate instances 
when you need multiple drivers, or services conflict with each other. you *may* 
separate instances for operational or scalability purposes
⊣GE⊢

> On 31 Aug 2023, at 9:09 am, cric...@pobox.com  wrote:
> 
> I'm setting up yet another weewx instance, this time for plotting a solar 
> charge controller.

-- 
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/C6EEC707-1DBC-4DE6-9986-44F604492511%40geddy.au.

Re: [weewx-user] Getting data from weewx

[Graham Eddy]

not quite what is being asked re ‘extract data for the last 5 minutes’…
given weewx usually generates data reports each 5 mins, presumably you just 
want a file generated with the data you specifically want.
i create a json file with basic wx info each 5 mins as a javascript-friendly 
api - it is just a template in a skin
⊣GE⊢

> On 27 Aug 2023, at 12:18 am, Per Weisteen  wrote:
> 
> Hi, I'm running weewx on Raspberry Pi at my summer cabin 
>  and would like to know how to 
> extract data on temperature, pressure, etc for use in another system. Is 
> there a command I could run for extracting data for the last 5 minutes? The 
> RPi has sshd enabled and I can ssh into it and run commands. Could I extract 
> data using wee utilities or should I use SQLite command directly?  
> 
> I'm planning to display the data as text in one corner of short videos I'm 
> getting from my weather camera (Link to camera on Windy 
> ) using ffmpeg to add text to the video. 
> 
> Any suggestions would be most welcome.
> 
> -- 
> 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/23526fa7-48cb-4f3c-b28a-0090dc41eefbn%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/14CA595F-9A3E-4239-807A-E083866AE710%40geddy.au.

Re: [weewx-user] WeeWX v5 pip Install into venv

[Graham Eddy]

use ‘python3 -m venv ~/venv’ to create the environment in ~/venv.
then in your shell run ’source ~/venv/bin/activate’ to set up the shell 
environment (initialised python bindary, PYTHONPATH etc). i put this in my 
~/.bashrc

a key trick is that running the initialised python binary (~/venv/bin/python3) 
on its own sucks in the environment - really, really handy in systemctl unit 
files
⊣GE⊢

> On 25 Aug 2023, at 10:41 am, vince  wrote:
> 
> For the venv you do a 'source weewx-venv/bin/activate' then do a pip install 
> to add modules within the venv.   All you have to remember is to activate the 
> venv before running weectl, as well as read the docs for the new syntax for 
> doing things.  It's pretty easy to pick up.
> 
> systemctl works fine.  Just go with it :-)

-- 
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/AB60763A-9EF8-4C4A-B870-2300896D0768%40geddy.au.

Re: [weewx-user] SolarEdge PV API

[Graham Eddy]

i have been polling a SolarEdge HDWave inverter for a few years.
my inverter has the LED, so it is not the latest version, and doesn’t have 
direct API, so i use the API to the (yuck) vendor cloud API (and not happy 
about it). vendor API throttles to about 1 call/15 mins.
i have a simple daemon that polls then publishes to mqtt (then the route into 
weewx is obvious).
cheers
⊣GE⊢

> On 15 Aug 2023, at 3:35 am, Dan'l B  wrote:
> 
> Just got a new SolarEdge monitoring system running and looking for ways to 
> display its data in WeeWx. It looks as if I might have several options 
>  and I'm wondering if anyone here 
> has explored this project.
> 
> -- 
> 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/dcd61c91-e9ed-420c-9e8b-f2f23a2a232en%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/4B5D6ACD-5553-480E-ACEB-03EB99E467A9%40geddy.au.

Re: [weewx-user] Installing weewx without root access

[Graham Eddy]

read up on python ‘virtual environment’ (venv) to get your libraries etc in 
place.
running it while not logged in - best way depends upon your o/s (eg user mode 
of systemd)
⊣GE⊢

> On 10 Aug 2023, at 2:06 am, Matthew Fields  wrote:
> 
> Might seem like an odd request, but I'm trying to find some guidance on 
> installing weewx as a normal user on a shared linux host without root access.
> 
> I'll be using websockets to get weather station data (Tempest Weatherflow), 
> so I don't need serial or USB access on the server. My goal is to have weewx 
> run on a shared cloud webserver (hosted by Bluehost). As a shared server, I 
> do not have root access so I have to run it as a normal user.
> 
> I have access to the compiler, so I've been trying to install with the python 
> installation instructions. I manage to get everything installed, though I 
> keep running into a lot of fun trying getting weewx to run. I'm sure it has 
> to be configuration settings I need to make, missing python modules, etc.
> 
> Rather than beating my head endlessly, has anyone installed weewx in a shared 
> environment without root access (like bluehost)? Anyone know of any 
> installation guidance for such an environment?
> 
> -- 
> 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/4272f256-db69-4a31-ae68-956f2ba6a6dcn%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/AD949D86-372B-4710-9B3D-E1743DAF9015%40geddy.au.

Re: [weewx-user] Connecting to new Davis Console model 6313

[Graham Eddy]

swap vantage to ecowitt and you lose the data logger (stored in local hardware) 
→ one day you lose critical data

ecowitt already have a ‘regularly call home' to china built in that adds no 
value to customer, only a dependency on ecowitt company. if ecowitt turn off 
their ‘ok’ response, everyone’s stations will reboot continually. i expect them 
to introduce paid-only access - but they are clever not to restrict the data 
but to disable the devices. (you might want to be wary of accepting their 
firmware upgrades in future, for existing devices.)

it is like the printer market - they flog you a printer really cheap but 
'charge like a wounded bull' for the ink. ditto future weather stations: cheap 
hardware, but lock you into constant revenue stream for service. as the weather 
station vendors try to lock down into paid-only services, i plan to migrate to 
open lorawan devices (because i want COTS or public domain products rather than 
build my own - more effective use of my time)

but i do like my current setup, with vantage providing core weather data and 
ecowitt lots of other inexpensive nearby sensors augmenting it, plus lorawan 
for some more distant and more complex sensors than ecowitt provides. 
⊣GE⊢

> On 9 Aug 2023, at 1:35 pm, Bob Rose  wrote:
> 
> I have been using the Ecowitt on my home weather station going on three years 
> now. I can not say anything bad about it. The Davis 6313 I am dealing with is 
> for an organization I belong to. It replaced the failing VP2. They are really 
> bummed that they spent so much money for something that does not have 
> accessible archives. I have even thought about sneaking an Ecowitt system out 
> there and telling them “I got it working”. 
> 
> 
> On Tuesday, August 8, 2023 at 8:05:51 PM UTC-7 Colin Larsen wrote:
>> Strangely enough I just replaced all my DIY hardware (weatherduino) with an 
>> Ecowitt setup and it's excellent for the money
>> 
>> Colin
>> 
>> On Wed, 9 Aug 2023 at 14:35, vince > wrote:
>>> rtl_davis driver can help somewhat at a higher complexity level FWIW
>>> 
>>> 
>> 
>>> -- 
>>> 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/72f7c54d-ed55-4631-8eeb-0339cbf93588n%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/3bbbaaf3-61b5-4574-8078-91992aca8ad4n%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/944805D7-1FD7-4608-9836-A2506B3EE5CB%40geddy.au.

Re: [weewx-user] Connecting to new Davis Console model 6313

[Graham Eddy]

have a look at LoRaWAN (and run your own Network Server, several are available 
to install). their whole point in open communications to sensors (mqtt). the 
price points are higher than Ecowitt, but nowhere near as expensive as Davis
⊣GE⊢

> On 9 Aug 2023, at 9:30 am, Greg from Oz  wrote:
> 
> It will get to the stage where we will have to build our own hardware.

-- 
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/D179E58F-736D-4C7F-AC6B-FD19218BBAA0%40geddy.au.

Re: [weewx-user] Understanding Weewx new method of logging

[Graham Eddy]

see https://docs.python.org/3/library/logging.config.html - weewx logging uses 
this yaml (translated into ini syntax).
perhaps your best option is to set logging level at ‘error’, which is not 
verbose unless you really really need it
⊣GE⊢

> On 27 Jul 2023, at 11:08 pm, Tomasz Lewicki  wrote:
> 
>> But I think that some mechanism to completely turn off logging does/should 
>> exist. I can always turn it on if needed.
>> 
>>  I don't know if it is good approach but I've used "disable_existing_loggers 
>> = True" directive in weewx.conf and log aren't generated - or I can't find 
>> them :)

-- 
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/FFBBF8FF-3141-4F2B-A49D-37B177AF355A%40geddy.au.

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Graham Eddy]

i don’t use belchertown or that mqtt driver so i don’t know the details.
my observation is that the report belchertown seems to be waiting on topic 
‘’weather/loop’’ (i don’t know the syntax but it’s a reasonable presumption), 
but when you printed all the messages being published, none had that topic → 
belchertown quite rightly is not reporting receiving any messages
⊣GE⊢

> On 25 Jul 2023, at 6:03 pm, Stefan Gliessmann  
> wrote:
> 
> GE - could you expand on your statement: "referenced topic not listed in the 
> topics of published messages"?
> 
> what should mqtt_websockets_topic look like? e.g. = 
> weather/inTemp_degree_C/loop?
> 
> TIA,
> Stefan
> 
> On Tuesday, July 25, 2023 at 9:45:40 AM UTC+2 Graham Eddy wrote:
>> referenced topic not listed in the topics of published messages
>> ⊣GE⊢
>> 
>>> On 25 Jul 2023, at 5:34 pm, Stefan Gliessmann > 
>>> wrote:
>>> 
>>> mqtt_websockets_topic = weather/loop
>> 
> 
> 
> -- 
> 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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/58a676a8-50db-4f36-8078-f27ddf27d2c3n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/58a676a8-50db-4f36-8078-f27ddf27d2c3n%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/87896D52-4563-457D-A539-A436ACCAEF10%40geddy.au.

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Graham Eddy]

referenced topic not listed in the topics of published messages
⊣GE⊢

> On 25 Jul 2023, at 5:34 pm, Stefan Gliessmann  
> wrote:
> 
> mqtt_websockets_topic = weather/loop

-- 
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/FEF21BDE-DF2D-4861-AEDF-BE99B8C17C39%40geddy.au.

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Graham Eddy]

i meant ‘mosquito_sub -v -t “#" -h brokerhost’ on weewx host, plus 
authentication if any
⊣GE⊢

> On 25 Jul 2023, at 11:47 am, Graham Eddy  wrote:
> 
> try ‘mosquito_sub -v -t topic_pattern -h brokerhost’ to see what **is** being 
> published
> ⊣GE⊢
> 
>> On 25 Jul 2023, at 5:08 am, vince  wrote:
>> 
>> I think you have a mismatch in what you are publishing vs. what you are 
>> trying to subscribe to.
> 
> 
> -- 
> 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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/686A219D-75B5-431B-9044-215355744BDF%40geddy.au
>  
> <https://groups.google.com/d/msgid/weewx-user/686A219D-75B5-431B-9044-215355744BDF%40geddy.au?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/749B9857-ACE8-4069-87AF-55F0BDB55EFF%40geddy.au.

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Graham Eddy]

try ‘mosquito_sub -v -t topic_pattern -h brokerhost’ to see what **is** being 
published
⊣GE⊢

> On 25 Jul 2023, at 5:08 am, vince  wrote:
> 
> I think you have a mismatch in what you are publishing vs. what you are 
> trying to subscribe to.

-- 
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/686A219D-75B5-431B-9044-215355744BDF%40geddy.au.

Re: [weewx-user] GW1000 stopped working

[Graham Eddy]

windoze xp was my last - i bet it hasn’t improved since
⊣GE⊢

> On 24 Jul 2023, at 7:06 am, vince  wrote:
> 
> I can't speak to using Windows as I haven't needed to do so in well over two 
> years 

-- 
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/00DCA6CA-5258-4EC4-A843-69FCA548765A%40geddy.au.

Re: [weewx-user] wewwx new variables

[Graham Eddy]

values like rain - and, in my own case, energy created by solar panel inverter 
- need to be summed not averaged over the archive interval.
the default accumulator for a data_type is averaging, so you need to specify 
your new data_type explicitly as summed - in my case, ‘’weewx.conf'' has:
[Accumulator]
[[gen_energy]]
extractor = sum
not sure where this is documented. other types are average, last, first, ...
⊣GE⊢

> On 24 Jul 2023, at 3:24 am, maria gourniezaki  wrote:
> 
> How to distinguish between accumulative fields and now accumulative ones?

-- 
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/B8E0470F-5B45-4347-9674-73829A8F70F9%40geddy.au.

Re: [weewx-user] GW1000 stopped working

[Graham Eddy]

can pi1/pi2 ping each other?
what are the IP addrs/netmask for laptop, gw1000, pi1 and pi2?
⊣GE⊢

> On 23 Jul 2023, at 11:58 pm, zasp...@gmail.com  wrote:
> 
> hi
> laptop  can ping PI
> Pi cannot ping laptop
> 
> connected up a second PI (created with a different image file)
> Laptop can ping PI
> Pi cannot ping laptop
> PI cannot ping 192.168.1.248 the GW1000
> 
> i can SSH into both PI's
> 
> 
> 
> 
> 
> On Sunday, 23 July 2023 at 13:22:51 UTC+1 Graham Eddy wrote:
>> laptop can ping gw1000.
>> pi cannot ping gw1000.
>> can laptop ping pi? and pi ping laptop?
>> ⊣GE⊢
>> 
>> 
>>> On 23 Jul 2023, at 9:56 pm, zasp...@gmail.com <> > 
>>> wrote:
>>> 
>> 
>>> i have pinged other IP address on my net work and the PI gets  response its 
>>> only the GW1000 its have an issue with
>>> 
>>> On Sunday, 23 July 2023 at 12:51:15 UTC+1 zasp...@gmail.com 
>>> <http://gmail.com/> wrote:
>>>> hi 
>>>> 
>>>> from my weewx.confg
>>>> 
>>>> [GW1000]
>>>> # This section is for the Ecowitt Gateway driver.
>>>> 
>>>> # How often to poll the API, default is every 20 seconds:
>>>> poll_interval = 20
>>>> 
>>>> # The driver to use:
>>>> driver = user.gw1000
>>>> ip_address = 192.168.1.248
>>>> port = 45000
>>>> [[field_map_extensions]]
>>>> extraTemp10 = temp10
>>>> wxSensor30 = light
>>>> 
>>>> however you are correct its a network issue
>>>> 
>>>> if i ping from my laptop
>>>> C:\Windows\System32>ping 192.168.1.248
>>>> 
>>>> Pinging 192.168.1.248 with 32 bytes of data:
>>>> Reply from 192.168.1.248 <http://192.168.1.248/>: bytes=32 time=5ms TTL=255
>>>> Reply from 192.168.1.248 <http://192.168.1.248/>: bytes=32 time=3ms TTL=255
>>>> Reply from 192.168.1.248 <http://192.168.1.248/>: bytes=32 time=3ms TTL=255
>>>> Reply from 192.168.1.248 <http://192.168.1.248/>: bytes=32 time=3ms TTL=255
>>>> 
>>>> Ping statistics for 192.168.1.248 <http://192.168.1.248/>:
>>>> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>>>> Approximate round trip times in milli-seconds:
>>>> Minimum = 3ms, Maximum = 5ms, Average = 3ms
>>>> 
>>>> if i ping from my PI
>>>> 
>>>> pi@raspberrypiwx:~ $ ping -n 192.168.1.248
>>>> PING 192.168.1.248 (192.168.1.248) 56(84) bytes of data.
>>>> From 192.168.1.242 icmp_seq=1 Destination Host Unreachable
>>>> From 192.168.1.242 icmp_seq=2 Destination Host Unreachable
>>>> From 192.168.1.242 icmp_seq=3 Destination Host Unreachable
>>>> From 192.168.1.242 icmp_seq=4 Destination Host Unreachable
>>>> From 192.168.1.242 icmp_seq=5 Destination Host Unreachable
>>>> From 192.168.1.242 icmp_seq=6 Destination Host Unreachable
>>>> From 192.168.1.242 icmp_seq=7 Destination Host Unreachable
>>>> From 192.168.1.242 icmp_seq=8 Destination Host Unreachable
>>>> From 192.168.1.242 icmp_seq=9 Destination Host Unreachable
>>>> 
>>>> 
>>>> i have no idea why laptop can ping the GW1000 but my PI cant
>>>> 
>>>> On Saturday, 22 July 2023 at 21:19:13 UTC+1 vince wrote:
>>>>> Lets see your [GW1000] stanza from weewx.conf please.  If your 'gateway' 
>>>>> address is 192.168.1.148 then it should look something like the following:
>>>>> 
>>>>> [GW1000]
>>>>> ip_address = 192.168.1.148
>>>>> port = 45000
>>>>> poll_interval = 20
>>>>> driver = user.gw1000
>>>>> 
>>>>> Your gateway should also respond to a ping from your weewx box.   Log 
>>>>> into the weewx box and try "ping -n 192.168.1.148" and verify that you 
>>>>> can get a response.
>>>>> 
>>> 
>>> 
>> 
>>> -- 
>>> 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/131679f4-e4fa-4c90-9baa-712b9cb14f70n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/131679f4-e4fa-4c90-9baa-712b9cb14f70n%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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/8b7a9f80-12cb-4f18-b889-eb8b75b4922fn%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/8b7a9f80-12cb-4f18-b889-eb8b75b4922fn%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/05BE2D6A-31A2-4E97-A045-9592F63FA8B7%40geddy.au.

Re: [weewx-user] GW1000 stopped working

[Graham Eddy]

laptop can ping gw1000.
pi cannot ping gw1000.
can laptop ping pi? and pi ping laptop?
⊣GE⊢

> On 23 Jul 2023, at 9:56 pm, zasp...@gmail.com  wrote:
> 
> i have pinged other IP address on my net work and the PI gets  response its 
> only the GW1000 its have an issue with
> 
> On Sunday, 23 July 2023 at 12:51:15 UTC+1 zasp...@gmail.com 
>  wrote:
>> hi 
>> 
>> from my weewx.confg
>> 
>> [GW1000]
>> # This section is for the Ecowitt Gateway driver.
>> 
>> # How often to poll the API, default is every 20 seconds:
>> poll_interval = 20
>> 
>> # The driver to use:
>> driver = user.gw1000
>> ip_address = 192.168.1.248
>> port = 45000
>> [[field_map_extensions]]
>> extraTemp10 = temp10
>> wxSensor30 = light
>> 
>> however you are correct its a network issue
>> 
>> if i ping from my laptop
>> C:\Windows\System32>ping 192.168.1.248
>> 
>> Pinging 192.168.1.248 with 32 bytes of data:
>> Reply from 192.168.1.248 : bytes=32 time=5ms TTL=255
>> Reply from 192.168.1.248 : bytes=32 time=3ms TTL=255
>> Reply from 192.168.1.248 : bytes=32 time=3ms TTL=255
>> Reply from 192.168.1.248 : bytes=32 time=3ms TTL=255
>> 
>> Ping statistics for 192.168.1.248 :
>> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>> Approximate round trip times in milli-seconds:
>> Minimum = 3ms, Maximum = 5ms, Average = 3ms
>> 
>> if i ping from my PI
>> 
>> pi@raspberrypiwx:~ $ ping -n 192.168.1.248
>> PING 192.168.1.248 (192.168.1.248) 56(84) bytes of data.
>> From 192.168.1.242 icmp_seq=1 Destination Host Unreachable
>> From 192.168.1.242 icmp_seq=2 Destination Host Unreachable
>> From 192.168.1.242 icmp_seq=3 Destination Host Unreachable
>> From 192.168.1.242 icmp_seq=4 Destination Host Unreachable
>> From 192.168.1.242 icmp_seq=5 Destination Host Unreachable
>> From 192.168.1.242 icmp_seq=6 Destination Host Unreachable
>> From 192.168.1.242 icmp_seq=7 Destination Host Unreachable
>> From 192.168.1.242 icmp_seq=8 Destination Host Unreachable
>> From 192.168.1.242 icmp_seq=9 Destination Host Unreachable
>> 
>> 
>> i have no idea why laptop can ping the GW1000 but my PI cant
>> 
>> On Saturday, 22 July 2023 at 21:19:13 UTC+1 vince wrote:
>>> Lets see your [GW1000] stanza from weewx.conf please.  If your 'gateway' 
>>> address is 192.168.1.148 then it should look something like the following:
>>> 
>>> [GW1000]
>>> ip_address = 192.168.1.148
>>> port = 45000
>>> poll_interval = 20
>>> driver = user.gw1000
>>> 
>>> Your gateway should also respond to a ping from your weewx box.   Log into 
>>> the weewx box and try "ping -n 192.168.1.148" and verify that you can get a 
>>> response.
>>> 
> 
> 
> -- 
> 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/131679f4-e4fa-4c90-9baa-712b9cb14f70n%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/34FD2085-EA98-4F56-B756-D6CA6D74DC25%40geddy.au.

Re: [weewx-user] Rain cumulative total wrong total in graph

[Graham Eddy]

i just assumed you were comparing aggregation of 12 months with aggregation 
since start of rainyear
⊣GE⊢

> On 24 Jun 2023, at 3:52 pm, Greg from Oz  wrote:
> 
> I put this part in:
>   rain_year_start = 1
> But still not correct.
> 
> 
> On Saturday, 24 June 2023 at 15:03:26 UTC+10 Greg Reive wrote:
>> What do you mean rain year date?
>> 
>> 
>> On Sat, 24 June 2023, 14:50 Graham Eddy, > wrote:
>>> rainyear date?
>>> ⊣GE⊢
>>> 
>>>> On 24 Jun 2023, at 2:27 pm, Greg from Oz > wrote:
>>>> 
>>>> I have made a graph to show the cumulative rainfall and it seems to show 
>>>> the correct values on the graphs for day, week and month. They tally up 
>>>> with the figures that weewx has calculated but the year total is way out 
>>>> and the graph numbers are way out as well.
>>>> I cannot see why it would be so different.
>>>> 
>>>> I am using weewx version 4.10.2 and mysql
>>>> 
>>>> Here is the year configuration I am using which is similar to the day, 
>>>> week and month.
>>>> 
>>>> [[[yearraincumulation]]]
>>>>rain1
>>>>   data_binding = wx_binding
>>>>   data_type = rain
>>>>   aggregate_type = cumulative
>>>>   aggregate_interval = 604800 #1 day
>>>>   label = Rain cumulative
>>>>   plot_type = line
>>>>   line_type = solid
>>>>   line_gap_fraction = 0.5
>>>> It generates the graph:
>>>> 
>>>> The total weewx tells me for the year is:
>>>> 478.8 mm
>>>> which is nowhere near the 1200 on the graph.
>>>> Very strange the other graphs work.
>>>> 
>>>> Here is my web page:
>>>> https://weather.ubeaut.work/year.html
>>>> 
>>>> Any ideas?
>>>> 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+...@googlegroups.com <>.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/97c7b8b9-d177-465a-b258-692a1e06226dn%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/97c7b8b9-d177-465a-b258-692a1e06226dn%40googlegroups.com?utm_medium=email_source=footer>.
>>>> 
>>> 
>>> 
>>> -- 
>> 
>>> 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/Td-2dHCXwaA/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/35952BFA-6255-4349-88DD-E1BB7B954697%40geddy.au
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/35952BFA-6255-4349-88DD-E1BB7B954697%40geddy.au?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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/4665860b-848b-4ac9-8231-b266de44581fn%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/4665860b-848b-4ac9-8231-b266de44581fn%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/E8B1FD15-0728-4F55-9756-9C86FAAD67AE%40geddy.au.

Re: [weewx-user] Rain cumulative total wrong total in graph

[Graham Eddy]

rainyear date?
⊣GE⊢

> On 24 Jun 2023, at 2:27 pm, Greg from Oz  wrote:
> 
> I have made a graph to show the cumulative rainfall and it seems to show the 
> correct values on the graphs for day, week and month. They tally up with the 
> figures that weewx has calculated but the year total is way out and the graph 
> numbers are way out as well.
> I cannot see why it would be so different.
> 
> I am using weewx version 4.10.2 and mysql
> 
> Here is the year configuration I am using which is similar to the day, week 
> and month.
> 
> [[[yearraincumulation]]]
>rain1
>   data_binding = wx_binding
>   data_type = rain
>   aggregate_type = cumulative
>   aggregate_interval = 604800 #1 day
>   label = Rain cumulative
>   plot_type = line
>   line_type = solid
>   line_gap_fraction = 0.5
> It generates the graph:
> 
> The total weewx tells me for the year is:
> 478.8 mm
> which is nowhere near the 1200 on the graph.
> Very strange the other graphs work.
> 
> Here is my web page:
> https://weather.ubeaut.work/year.html
> 
> Any ideas?
> 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/97c7b8b9-d177-465a-b258-692a1e06226dn%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/35952BFA-6255-4349-88DD-E1BB7B954697%40geddy.au.

Re: [weewx-user] StdQC question

[Graham Eddy]

someone could develop a ‘filter’ service that could hold state (either in 
memory or private database) of successive readings.
conceptually an extension of StdQC
⊣GE⊢

> On 24 Jun 2023, at 6:22 am, gjr80  wrote:
> 
> Hi Steve,
> 
> Unfortunately you are correct; StdQC does a simple check that an obs falls 
> between or is equal to the specified min and max values. So nothing can be 
> done with rates of change short of writing your own custom StdQC. There was 
> some work a good many years back on a 'spike detector' for StdQC (refer issue 
> #3 ) to filter out spikes in a given 
> obs, but nothing became of it in the end.
> 
> You can sometimes achieve more complex checks via StdCalibrate, but you only 
> have obs from the current record/packet available to play with; nothing from 
> earlier packets/records which makes rate of change calculations difficult.
> 
> Gary
> 
> On Friday, 23 June 2023 at 20:26:03 UTC+1 Steve2Q wrote:
>> Hello: I am using v 3.8.2. I currently have the StdQC value set for 
>> outHumidity= 50, 100 and it is working properly. My question is this: Is 
>> there a way to have rate of change rather than set boundaries to be used? I 
>> think the answer is NO, but I wanted to check.
>> 
>> Thanks, Steve
> 
> 
> -- 
> 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/775d23b8-d787-4929-8eee-6625309d816cn%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/7DF60CFF-B2E7-48A5-9424-84AD1ABB8F86%40geddy.au.

Re: [weewx-user] Problemas para publicar mqtt

[Graham Eddy]

does this indicate the same MQTT service is being loaded twice? that might 
confuse the driver
⊣GE⊢

> On 22 Jun 2023, at 8:42 am, jose riaño  wrote:
> 
> Jun 21 17:33:19 raspberrypi weewx[6765]: engine: Loading service 
> user.mqtt.MQTT
> Jun 21 17:33:19 raspberrypi weewx[6765]: restx: MQTT: service version is 0.24
> Jun 21 17:33:19 raspberrypi weewx[6765]: restx: MQTT: binding to archive
> Jun 21 17:33:19 raspberrypi weewx[6765]: restx: MQTT: data_binding is 
> wx_binding
> Jun 21 17:33:19 raspberrypi weewx[6765]: restx: MQTT: topic is 
> estacion_buga/loop
> Jun 21 17:33:19 raspberrypi weewx[6765]: restx: MQTT: data will be uploaded 
> to 
> mqtt://estaciones_meteorologicas:x...@m53bfd36.ala.us-east-1.emqxsl.com:8883 
> 
> Jun 21 17:33:19 raspberrypi weewx[6765]: engine: Finished loading service 
> user.mqtt.MQTT
> Jun 21 17:33:19 raspberrypi weewx[6765]: engine: Loading service 
> weewx.engine.StdPrint
> Jun 21 17:33:19 raspberrypi weewx[6765]: engine: Finished loading service 
> weewx.engine.StdPrint
> Jun 21 17:33:19 raspberrypi weewx[6765]: engine: Loading service 
> weewx.engine.StdReport
> Jun 21 17:33:19 raspberrypi weewx[6765]: engine: Finished loading service 
> weewx.engine.StdReport
> Jun 21 17:33:19 raspberrypi weewx[6765]: engine: Loading service 
> user.mqtt.MQTT
> Jun 21 17:33:19 raspberrypi weewx[6765]: restx: MQTT: service version is 0.24
> Jun 21 17:33:19 raspberrypi weewx[6765]: restx: MQTT: binding to archive
> Jun 21 17:33:19 raspberrypi weewx[6765]: restx: MQTT: data_binding is 
> wx_binding
> Jun 21 17:33:19 raspberrypi weewx[6765]: restx: MQTT: topic is 
> estacion_buga/loop
> Jun 21 17:33:19 raspberrypi weewx[6765]: restx: MQTT: data will be uploaded 
> to 
> mqtt://estaciones_meteorologicas:x...@m53bfd36.ala.us-east-1.emqxsl.com:8883 
> 
> Jun 21 17:33:19 raspberrypi weewx[6765]: engine: Finished loading service 
> user.mqtt.MQTT

-- 
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/F2FFEC67-88BF-4CE3-B311-E43357468281%40geddy.au.

Re: [weewx-user] Weewx keeps restarting

[Graham Eddy]

assuming you rolled everything back, then rolled forward one step at a time 
until it started to fail, what was the last step causing it to fail?
⊣GE⊢

> On 14 Jun 2023, at 1:09 am, Mark Fraser  wrote:
> 
>  I can't think of anything I've changed that would cause this

-- 
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/11AABE7B-E104-4C5A-A1FF-D376430A2841%40geddy.au.

Re: [weewx-user] Weewx keeps restarting

[Graham Eddy]

disable everythng back to bare bones, then add them back again one at a time
⊣GE⊢

> On 12 Jun 2023, at 12:22 am, Mark Fraser  wrote:
> 
> Any ideas how to debug this?

-- 
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/B500FCF8-B986-423B-AB19-44B5DFF11BD7%40geddy.au.

Re: [weewx-user] gw1000 driver: minor logging bug?

[Graham Eddy]

with very long timeout periods allowing underlying problems to report 
themselves, i get occasional flurries of ’No route to host errors’, which cause 
s.connect to fail after 18-19 secs, followed by similar that then times out 
after 2-3 secs, then it works. i would describe it as a local networking issue 
not a gw1000 driver issue

but i did have to insert that extra debug line to report the reason s.connect 
was failing to pin it down

May 31 20:46:23 ironbark weewx-gw1000[807215] DEBUG user.gw1000: #GE before 
s.connect ipaddr=b'192.168.37.58' port=45000
May 31 20:46:41 ironbark weewx-gw1000[807215] DEBUG user.gw1000: #GE caught 
socket.error [Errno 113] No route to host
May 31 20:46:41 ironbark weewx-gw1000[807215] DEBUG user.gw1000: #GE before 
s.shutdown
May 31 20:46:41 ironbark weewx-gw1000[807215] DEBUG user.gw1000: #GE shutdown 
failed: 107
May 31 20:46:41 ironbark weewx-gw1000[807215] DEBUG user.gw1000: #GE before 
s.close
May 31 20:46:41 ironbark weewx-gw1000[807215] DEBUG user.gw1000: Failed attempt 
1 to send command 'CMD_GW1000_LIVEDATA': [Errno 113] No route to host

cheers
⊣GE⊢

> On 28 May 2023, at 10:08 pm, Graham Eddy  wrote:
> 
> nope, adding s.shutdown() call didn’t help, still timing out
> 
> now i’ll try increasing [GW1000]socket_timeout to 59s to see if it blows even 
> that long a period
> ⊣GE⊢
> 
>> On 28 May 2023, at 8:10 pm, Graham Eddy  wrote:
>> 
>> the greater detail shows it is timing out on the s.connect() call, after 
>> going long periods without such timeouts. i have noticed that we open and 
>> close the socket quite rapidly at times, so i wonder if there is some python 
>> garbage-collect lag or TCP FIN lag manifesting
>> 
>> i see in python manual
>> Note close() <https://docs.python.org/3/library/socket.html#socket.close> 
>> releases the resource associated with a connection but does not necessarily 
>> close the connection immediately. If you want to close the connection in a 
>> timely fashion, call shutdown() 
>> <https://docs.python.org/3/library/socket.html#socket.socket.shutdown> 
>> before close() <https://docs.python.org/3/library/socket.html#socket.close>.
>> so i have experimentally inserted a s.shutdown() call just before the 
>> s.connect() call. we’ll see if it makes any difference...
>> ⊣GE⊢
>> 
>>> On 28 May 2023, at 5:30 pm, Graham Eddy  wrote:
>>> 
>>> i should also have mentioned that this same weewx server also hosts another 
>>> instance of weewx, using serial vantage driver, that is having no such 
>>> problems
>>> ⊣GE⊢
>>> 
>>>> On 28 May 2023, at 5:28 pm, Graham Eddy  wrote:
>>>> 
>>>> v0.5.0b5 is in place and i continue to get timeouts and restarts.
>>>> (logging issue is resolved; i am preferring to continue in this thread for 
>>>> situational continuity e.g. logs are all relevant)
>>>> 
>>>> in brief, at intermittent times (less than an hour apart to several days 
>>>> apart), i get three no-response exceptions so a crash/restart of driver.
>>>> until several weeks ago it worked happily without timeouts.
>>>> i have moved to different power source; was on UPS and now is not.
>>>> i have replaced old gw1000 unit with new gw2000 unit with no noticeable 
>>>> improvement.
>>>> i have changed [GW1000]socket_timout to 10s, then to 6s to avoid 
>>>> unfortunate congruity with polling_interval=10s, with no noticeable change
>>>> 
>>>> the only environmental change i can think of was introducing dnsmasq for 
>>>> dns/dhcp into home office network but that was months ago, but i did drop 
>>>> a secondary, non-authoritative dsnmasq server on the weewx server 
>>>> somewhere about this timeframe (hence my idle wonder about dhcp lease 
>>>> interference)
>>>> 
>>>> i have now instrumented the driver with lots more debug statements around 
>>>> every step of sending command & receiving response with gw1000, set the 
>>>> [GW1000]socket_timeout back to 2s, and wait to see what i learn from this 
>>>> extra level of detail.
>>>> cheers
>>>> ⊣GE⊢
>>>> 
>>>>> On 26 May 2023, at 8:03 pm, gjr80  wrote:
>>>>> 
>>>>> v0.5.0b5 has been released for close on a year, it would essentially have 
>>>>> been v0.5.0 but never got around to releasing it. It should be stable
>>>> 
>>> 
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "weewx-user" group

Re: [weewx-user] gw1000 driver: minor logging bug?

[Graham Eddy]

nope, adding s.shutdown() call didn’t help, still timing out

now i’ll try increasing [GW1000]socket_timeout to 59s to see if it blows even 
that long a period
⊣GE⊢

> On 28 May 2023, at 8:10 pm, Graham Eddy  wrote:
> 
> the greater detail shows it is timing out on the s.connect() call, after 
> going long periods without such timeouts. i have noticed that we open and 
> close the socket quite rapidly at times, so i wonder if there is some python 
> garbage-collect lag or TCP FIN lag manifesting
> 
> i see in python manual
> Note close() <https://docs.python.org/3/library/socket.html#socket.close> 
> releases the resource associated with a connection but does not necessarily 
> close the connection immediately. If you want to close the connection in a 
> timely fashion, call shutdown() 
> <https://docs.python.org/3/library/socket.html#socket.socket.shutdown> before 
> close() <https://docs.python.org/3/library/socket.html#socket.close>.
> so i have experimentally inserted a s.shutdown() call just before the 
> s.connect() call. we’ll see if it makes any difference...
> ⊣GE⊢
> 
>> On 28 May 2023, at 5:30 pm, Graham Eddy  wrote:
>> 
>> i should also have mentioned that this same weewx server also hosts another 
>> instance of weewx, using serial vantage driver, that is having no such 
>> problems
>> ⊣GE⊢
>> 
>>> On 28 May 2023, at 5:28 pm, Graham Eddy  wrote:
>>> 
>>> v0.5.0b5 is in place and i continue to get timeouts and restarts.
>>> (logging issue is resolved; i am preferring to continue in this thread for 
>>> situational continuity e.g. logs are all relevant)
>>> 
>>> in brief, at intermittent times (less than an hour apart to several days 
>>> apart), i get three no-response exceptions so a crash/restart of driver.
>>> until several weeks ago it worked happily without timeouts.
>>> i have moved to different power source; was on UPS and now is not.
>>> i have replaced old gw1000 unit with new gw2000 unit with no noticeable 
>>> improvement.
>>> i have changed [GW1000]socket_timout to 10s, then to 6s to avoid 
>>> unfortunate congruity with polling_interval=10s, with no noticeable change
>>> 
>>> the only environmental change i can think of was introducing dnsmasq for 
>>> dns/dhcp into home office network but that was months ago, but i did drop a 
>>> secondary, non-authoritative dsnmasq server on the weewx server somewhere 
>>> about this timeframe (hence my idle wonder about dhcp lease interference)
>>> 
>>> i have now instrumented the driver with lots more debug statements around 
>>> every step of sending command & receiving response with gw1000, set the 
>>> [GW1000]socket_timeout back to 2s, and wait to see what i learn from this 
>>> extra level of detail.
>>> cheers
>>> ⊣GE⊢
>>> 
>>>> On 26 May 2023, at 8:03 pm, gjr80  wrote:
>>>> 
>>>> v0.5.0b5 has been released for close on a year, it would essentially have 
>>>> been v0.5.0 but never got around to releasing it. It should be stable
>>> 
>> 
>> 
>> -- 
>> 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 
>> <mailto:weewx-user+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/75C90738-B0B8-4D68-A122-A2B2AEE9C68F%40geddy.au
>>  
>> <https://groups.google.com/d/msgid/weewx-user/75C90738-B0B8-4D68-A122-A2B2AEE9C68F%40geddy.au?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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/6658CF4E-1D16-40CF-81F3-D95C2E319EE6%40geddy.au
>  
> <https://groups.google.com/d/msgid/weewx-user/6658CF4E-1D16-40CF-81F3-D95C2E319EE6%40geddy.au?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/D238B564-8E0F-4E3C-B320-C1A6ADD14397%40geddy.au.

Re: [weewx-user] gw1000 driver: minor logging bug?

[Graham Eddy]

the greater detail shows it is timing out on the s.connect() call, after going 
long periods without such timeouts. i have noticed that we open and close the 
socket quite rapidly at times, so i wonder if there is some python 
garbage-collect lag or TCP FIN lag manifesting

i see in python manual
Note close() <https://docs.python.org/3/library/socket.html#socket.close> 
releases the resource associated with a connection but does not necessarily 
close the connection immediately. If you want to close the connection in a 
timely fashion, call shutdown() 
<https://docs.python.org/3/library/socket.html#socket.socket.shutdown> before 
close() <https://docs.python.org/3/library/socket.html#socket.close>.
so i have experimentally inserted a s.shutdown() call just before the 
s.connect() call. we’ll see if it makes any difference...
⊣GE⊢

> On 28 May 2023, at 5:30 pm, Graham Eddy  wrote:
> 
> i should also have mentioned that this same weewx server also hosts another 
> instance of weewx, using serial vantage driver, that is having no such 
> problems
> ⊣GE⊢
> 
>> On 28 May 2023, at 5:28 pm, Graham Eddy  wrote:
>> 
>> v0.5.0b5 is in place and i continue to get timeouts and restarts.
>> (logging issue is resolved; i am preferring to continue in this thread for 
>> situational continuity e.g. logs are all relevant)
>> 
>> in brief, at intermittent times (less than an hour apart to several days 
>> apart), i get three no-response exceptions so a crash/restart of driver.
>> until several weeks ago it worked happily without timeouts.
>> i have moved to different power source; was on UPS and now is not.
>> i have replaced old gw1000 unit with new gw2000 unit with no noticeable 
>> improvement.
>> i have changed [GW1000]socket_timout to 10s, then to 6s to avoid unfortunate 
>> congruity with polling_interval=10s, with no noticeable change
>> 
>> the only environmental change i can think of was introducing dnsmasq for 
>> dns/dhcp into home office network but that was months ago, but i did drop a 
>> secondary, non-authoritative dsnmasq server on the weewx server somewhere 
>> about this timeframe (hence my idle wonder about dhcp lease interference)
>> 
>> i have now instrumented the driver with lots more debug statements around 
>> every step of sending command & receiving response with gw1000, set the 
>> [GW1000]socket_timeout back to 2s, and wait to see what i learn from this 
>> extra level of detail.
>> cheers
>> ⊣GE⊢
>> 
>>> On 26 May 2023, at 8:03 pm, gjr80  wrote:
>>> 
>>> v0.5.0b5 has been released for close on a year, it would essentially have 
>>> been v0.5.0 but never got around to releasing it. It should be stable
>> 
> 
> 
> -- 
> 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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/75C90738-B0B8-4D68-A122-A2B2AEE9C68F%40geddy.au
>  
> <https://groups.google.com/d/msgid/weewx-user/75C90738-B0B8-4D68-A122-A2B2AEE9C68F%40geddy.au?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/6658CF4E-1D16-40CF-81F3-D95C2E319EE6%40geddy.au.

Re: [weewx-user] gw1000 driver: minor logging bug?

[Graham Eddy]

i should also have mentioned that this same weewx server also hosts another 
instance of weewx, using serial vantage driver, that is having no such problems
⊣GE⊢

> On 28 May 2023, at 5:28 pm, Graham Eddy  wrote:
> 
> v0.5.0b5 is in place and i continue to get timeouts and restarts.
> (logging issue is resolved; i am preferring to continue in this thread for 
> situational continuity e.g. logs are all relevant)
> 
> in brief, at intermittent times (less than an hour apart to several days 
> apart), i get three no-response exceptions so a crash/restart of driver.
> until several weeks ago it worked happily without timeouts.
> i have moved to different power source; was on UPS and now is not.
> i have replaced old gw1000 unit with new gw2000 unit with no noticeable 
> improvement.
> i have changed [GW1000]socket_timout to 10s, then to 6s to avoid unfortunate 
> congruity with polling_interval=10s, with no noticeable change
> 
> the only environmental change i can think of was introducing dnsmasq for 
> dns/dhcp into home office network but that was months ago, but i did drop a 
> secondary, non-authoritative dsnmasq server on the weewx server somewhere 
> about this timeframe (hence my idle wonder about dhcp lease interference)
> 
> i have now instrumented the driver with lots more debug statements around 
> every step of sending command & receiving response with gw1000, set the 
> [GW1000]socket_timeout back to 2s, and wait to see what i learn from this 
> extra level of detail.
> cheers
> ⊣GE⊢
> 
>> On 26 May 2023, at 8:03 pm, gjr80  wrote:
>> 
>> v0.5.0b5 has been released for close on a year, it would essentially have 
>> been v0.5.0 but never got around to releasing it. It should be stable
> 

-- 
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/75C90738-B0B8-4D68-A122-A2B2AEE9C68F%40geddy.au.

Re: [weewx-user] gw1000 driver: minor logging bug?

[Graham Eddy]

v0.5.0b5 is in place and i continue to get timeouts and restarts.
(logging issue is resolved; i am preferring to continue in this thread for 
situational continuity e.g. logs are all relevant)

in brief, at intermittent times (less than an hour apart to several days 
apart), i get three no-response exceptions so a crash/restart of driver.
until several weeks ago it worked happily without timeouts.
i have moved to different power source; was on UPS and now is not.
i have replaced old gw1000 unit with new gw2000 unit with no noticeable 
improvement.
i have changed [GW1000]socket_timout to 10s, then to 6s to avoid unfortunate 
congruity with polling_interval=10s, with no noticeable change

the only environmental change i can think of was introducing dnsmasq for 
dns/dhcp into home office network but that was months ago, but i did drop a 
secondary, non-authoritative dsnmasq server on the weewx server somewhere about 
this timeframe (hence my idle wonder about dhcp lease interference)

i have now instrumented the driver with lots more debug statements around every 
step of sending command & receiving response with gw1000, set the 
[GW1000]socket_timeout back to 2s, and wait to see what i learn from this extra 
level of detail.
cheers
⊣GE⊢

> On 26 May 2023, at 8:03 pm, gjr80  wrote:
> 
> v0.5.0b5 has been released for close on a year, it would essentially have 
> been v0.5.0 but never got around to releasing it. It should be stable

-- 
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/03C245E5-9D9F-44BD-97D6-94E8CC007F00%40geddy.au.

Re: [weewx-user] gw1000 driver: minor logging bug?

[Graham Eddy]

 30 36 62 00 00 00 03 61 64 70 61 EB 60 0C 19 00 0A 0E 00 00 10 
00 00 11 00 1D 12 00 00 01 F5 13 00 00 08 E6 0D 00 00 70 00 E6 31 00 1A 00 20 
00 17 00 1C 01 EC 01 DF 06 56'
May 26 18:10:19 ironbark weewx-gw1000[363800] DEBUG weewx.engine: Loading 
service weewx.wxxtypes.StdDelta
May 26 18:10:19 ironbark weewx-gw1000[363800] DEBUG weewx.engine: Finished 
loading service weewx.wxxtypes.StdDelta
May 26 18:10:19 ironbark weewx-gw1000[363800] DEBUG weewx.engine: Loading 
service weewx.engine.StdArchive
May 26 18:10:19 ironbark weewx-gw1000[363800] INFO weewx.engine: Archive will 
use data binding wx_binding
May 26 18:10:19 ironbark weewx-gw1000[363800] INFO weewx.engine: Record 
generation will be attempted in 'software'
May 26 18:10:19 ironbark weewx-gw1000[363800] INFO weewx.engine: Using archive 
interval of 300 seconds (software record generation)
May 26 18:10:19 ironbark weewx-gw1000[363800] DEBUG weewx.engine: Use LOOP data 
in hi/low calculations: 1
May 26 18:10:19 ironbark weewx-gw1000[363800] DEBUG weewx.engine: Finished 
loading service weewx.engine.StdArchive
May 26 18:10:19 ironbark weewx-gw1000[363800] DEBUG weewx.engine: Loading 
service weewx.restx.StdStationRegistry
May 26 18:10:19 ironbark weewx-gw1000[363800] DEBUG user.gw1000: Sending packet 
'FF FF 57 03 5A' to 192.168.37.58:45000
May 26 18:10:19 ironbark weewx-gw1000[363800] DEBUG user.gw1000: Received 
response 'FF FF 57 00 29 0E 00 00 10 00 00 00 00 11 00 00 00 1D 12 00 00 01 F5 
13 00 00 08 E6 0D 00 00 0F 00 70 88 00 00 00 7A 01 7B 00 DF'
May 26 18:10:19 ironbark weewx-gw1000[363800] DEBUG user.gw1000: Unknown field 
address '7B' detected. Remaining data '00' ignored.
May 26 18:10:19 ironbark weewx-gw1000[363800] DEBUG user.gw1000: Parsed data: 
{'intemp': 19.0, 'inhumid': 54, 'absbarometer': 990.1, 'relbarometer': 990.1, 
'outtemp': 8.1, 'outhumid': 99, 'winddir': 160, 'windspeed': 0.0, 'gustspeed': 
0.0, 'light': 0.0, 'uv': 0.0, 'uvi': 0, 'pm251': 8.0, 'pm251_24h_avg': 10.1, 
'pm252': 19.0, 'pm252_24h_avg': 10.9, 'soilmoist1': 42, 'soilmoist3': 54, 
'lightningcount': 3, 'lightningdettime': 1685086699, 'lightningdist': 12, 
'daymaxwind': 1.0, 't_rainrate': 0.0, 't_rainday': 0.0, 't_rainweek': 2.9, 
't_rainmonth': 50.1, 't_rainyear': 227.8, 't_rainevent': 0.0, 'temp17': 23.0, 
'humid17': 49, 'pm10': 2.6, 'pm10_24h_avg': 3.2, 'pm255': 2.3, 'pm255_24h_avg': 
2.8, 'co2': 492, 'co2_24h_avg': 479, 't_rainhour': 11.2, 'day_reset': 0, 
'week_reset': 0, 'annual_reset': 0, 'rain_source': 1, 'datetime': 1685088619}

hopefully my no-response errors go away with new unit hardware and its new 
network i/f (ether rather than wlan) and yet another USB power source being 
tried
⊣GE⊢

> On 26 May 2023, at 5:57 pm, gjr80  wrote:
> 
> You might want to upgrade your driver, support for the GW2000 was introduced 
> in v0.5.0.
> 
> Gary
> 
> On Friday, 26 May 2023 at 16:29:03 UTC+10 Graham Eddy wrote:
> May 26 15:33:31 ironbark weewx-gw1000[350663] INFO user.gw1000: driver 
> version is 0.4.0
> 
> -- 
> 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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/4c12bf60-4121-4f54-b119-015eb9e38aadn%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/4c12bf60-4121-4f54-b119-015eb9e38aadn%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/E10DA224-2FB9-4848-84FB-C95DA065F34A%40geddy.au.

[weewx-user] gw1000 driver: minor logging bug?

[Graham Eddy]

for a couple of weeks i have been getting gw1000 driver rebooting after three 
no-responses. old gw1000 unit seems otherwise fine; tried different power 
source, tried rebooting everything occasionally; still failed, sometimes after 
few mins, sometimes 2 hours, 5 hours, sometimes a couple of days. anyway: 
decided to replace old gw1000 unit with new gw2000 unit

pointed driver at IP address of gw2000 unit, fired it up, all works fine. we’ll 
see if i get intermittent failures over next few days…
looking at the logs closely, i think there is a small bug: it reports station 
model as None (as in “None address is 192.168.37.58:45000”).
tracing the logic in the driver, it sends a CMD_READ_FIRMWARE_VERSION request 
and gets response “GW2000C_V2.2.3” (reported in hex) but reports it as None

May 26 15:33:31 ironbark weewx-gw1000[350660] INFO __main__: Initializing weewx 
version 4.10.2
May 26 15:33:31 ironbark weewx-gw1000[350660] INFO __main__: Using Python 3.9.2 
(default, Feb 28 2021, 17:03:44) #012[GCC 10.2.1 20210110]
May 26 15:33:31 ironbark weewx-gw1000[350660] INFO __main__: Located at 
/usr/bin/python3
May 26 15:33:31 ironbark weewx-gw1000[350660] INFO __main__: Platform 
Linux-6.1.21-v8+-aarch64-with-glibc2.31
May 26 15:33:31 ironbark weewx-gw1000[350660] INFO __main__: Locale is 
'en_AU.UTF-8'
May 26 15:33:31 ironbark weewx-gw1000[350660] INFO __main__: Using 
configuration file /home/weewx/gw1000.conf
May 26 15:33:31 ironbark weewx-gw1000[350660] INFO __main__: Debug is 3
May 26 15:33:31 ironbark weewx-gw1000[350660] INFO __main__: PID file is 
/run/weewx/gw1000.pid
May 26 15:33:31 ironbark weewx-gw1000[350663] DEBUG __main__: Initializing 
engine
May 26 15:33:31 ironbark weewx-gw1000[350663] INFO weewx.engine: Loading 
station type GW1000 (user.gw1000)
May 26 15:33:31 ironbark weewx-gw1000[350663] DEBUG user.gw1000: Sending packet 
'FF FF 26 03 29' to '192.168.37.58:45000'
May 26 15:33:31 ironbark weewx-gw1000[350663] DEBUG user.gw1000: Received 
response 'FF FF 26 09 94 3C C6 44 FC A3 A8'
May 26 15:33:31 ironbark weewx-gw1000[350663] DEBUG user.gw1000: Sending packet 
'FF FF 50 03 53' to '192.168.37.58:45000'
May 26 15:33:31 ironbark weewx-gw1000[350663] DEBUG user.gw1000: Received 
response 'FF FF 50 12 0E 47 57 32 30 30 30 43 5F 56 32 2E 32 2E 33 BB'
May 26 15:33:31 ironbark weewx-gw1000[350663] DEBUG user.gw1000: Sending packet 
'FF FF 30 03 33' to '192.168.37.58:45000'
May 26 15:33:31 ironbark weewx-gw1000[350663] DEBUG user.gw1000: Received 
response 'FF FF 30 0B 00 01 64 70 D1 4B 27 01 54'
May 26 15:33:31 ironbark weewx-gw1000[350663] INFO user.gw1000: field map is 
{'co2': 'co2', 'co2_24h_avg': 'co2_24h_avg', 'dateTime': 'datetime', 
'daymaxwind': 'daymaxwind', 'dayRain': 'rainday', 'dewpoint': 'dewpoint', 
'extraHumid1': 'humid1', 'extraHumid2': 'humid2', 'extraHumid3': 'humid3', 
'extraHumid4': 'humid4', 'extraHumid5': 'humid5', 'extraHumid6': 'humid6', 
'extraHumid7': 'humid7', 'extraHumid8': 'humid8', 'extraHumid17': 'humid17', 
'extraTemp1': 'temp1', 'extraTemp2': 'temp2', 'extraTemp3': 'temp3', 
'extraTemp4': 'temp4', 'extraTemp5': 'temp5', 'extraTemp6': 'temp6', 
'extraTemp7': 'temp7', 'extraTemp8': 'temp8', 'extraTemp9': 'temp9', 
'extraTemp10': 'temp10', 'extraTemp11': 'temp11', 'extraTemp12': 'temp12', 
'extraTemp13': 'temp13', 'extraTemp14': 'temp14', 'extraTemp15': 'temp15', 
'extraTemp16': 'temp16', 'extraTemp17': 'temp17', 'heatindex': 'heatindex', 
'hourRain': 'rainhour', 'inHumidity': 'inhumid', 'inTemp': 'intemp', 
'leafWet1': 'leafwet1', 'leafWet2': 'leafwet2', 'leafWet3': 'leafwet3', 
'leafWet4': 'leafwet4', 'leafWet5': 'leafwet5', 'leafWet6': 'leafwet6', 
'leafWet7': 'leafwet7', 'leafWet8': 'leafwet8', 'leak1': 'leak1', 'leak2': 
'leak2', 'leak3': 'leak3', 'leak4': 'leak4', 'lightning_distance': 
'lightningdist', 'lightning_last_det_time': 'lightningdettime', 
'lightning_strike_count': 'lightning_strike_count', 'lightningcount': 
'lightningcount', 'luminosity': 'light', 'monthRain': 'rainmonth', 
'outHumidity': 'outhumid', 'outTemp': 'outtemp', 'pm2_5': 'pm251', 
'pm2_51_24h_avg': 'pm251_24h_avg', 'pm2_52': 'pm252', 'pm2_52_24h_avg': 
'pm252_24h_avg', 'pm2_53': 'pm253', 'pm2_53_24h_avg': 'pm253_24h_avg', 
'pm2_54': 'pm254', 'pm2_54_24h_avg': 'pm254_24h_avg', 'pm2_55': 'pm255', 
'pm2_55_24h_avg': 'pm255_24h_avg', 'pm10_0': 'pm10', 'pm10_0_24h_avg': 
'pm10_24h_avg', 'pressure': 'absbarometer', 'radiation': 'uv', 'rain': 'rain', 
'rainRate': 'rainrate', 'relbarometer': 'relbarometer', 'soilMoist1': 
'soilmoist1', 'soilMoist2': 'soilmoist2', 'soilMoist3': 'soilmoist3', 
'soilMoist4': 'soilmoist4', 'soilMoist5': 'soilmoist5', 'soilMoist6': 
'soilmoist6', 'soilMoist7': 'soilmoist7', 'soilMoist8': 'soilmoist8', 
'soilMoist9': 'soilmoist9', 'soilMoist10': 'soilmoist10', 'soilMoist11': 
'soilmoist11', 'soilMoist12': 'soilmoist12', 'soilMoist13': 'soilmoist13', 
'soilMoist14': 'soilmoist14', 'soilMoist15': 'soilmoist15', 'soilMoist16': 
'soilmoist16', 'soilTemp1': 'soiltemp1', 

Re: [weewx-user] Problems with weewx on MacOS

[Graham Eddy]

tom did not say that 4.10.2 removed [Logging], he did ask you to remove that 
section temporarily, to get it to use default, in case your own content of that 
section was wrong. tom said that you were using a specific item (i think it was 
‘rotate’) that was removed in 4.10.2 and thus causing your runtime error

i think in macOS the default behaviour is to log under /var/log/system.log

once the default configuration is working, no doubt you will add some entries 
to [Logging] to use a file of your choice, such as /var/log/weewx.log
⊣GE⊢

> On 21 May 2023, at 7:33 pm, seano...@gmail.com  wrote:
> 
> However, I am still having some problem and I'm struggling to identify 
> exactly what because I'm not sure how to check the logs on MacOS. I'm sorry 
> for the noob question, but can someone please guide me on where weewx is 
> logging to? I can confirm that it is not /var/log/weewx.log or 
> /var/tmp/weewx.log. Originally I had added a [Logging] section in weewx.conf 
> but now the weewx 4.10.2 has removed that functionality I am not sure how 
> else to log weewx output to a different 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/ADD2976B-D69E-4BD4-A23F-FA1D439063DC%40geddy.au.

Re: [weewx-user] Belchertown MQTT not working

[Graham Eddy]

try subscribe (-v) to topic ‘#’ to examine all messages (in case topic 
mis-named)
⊣GE⊢

> On 9 May 2023, at 9:09 am, Kevin Crivelli  wrote:
> 
> So I am definitely getting records published from MQTT however I still have 
> the same problem where the local address is showing connected waiting for 
> data and the remote instance is just connecting

-- 
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/3E8DEBC0-84A2-4D5C-8150-2C43ABB4EC60%40geddy.au.

Re: [weewx-user] VantageVue rain collector delay

[Graham Eddy]

is the funnel empty when reading slowly?
⊣GE⊢

> On 1 May 2023, at 9:56 pm, Steve C  wrote:
> 
> The wx station is mounted on a steel pole in an open space in my backyard and 
> is very easy to access. As I mentioned, I disassembled it as recently as 
> yesterday. No birds, no spiders, no nuts, no trees. It is almost like a 
> clock. I am (as of this writing) still collecting .01" every 10 minutes or 6 
> times an hour. 
> 
> On Monday, May 1, 2023 at 7:47:17 AM UTC-4 bgra...@umw.edu <http://umw.edu/> 
> wrote:
>> I think Graham has the answer. About twice a year, squirrels crack nuts into 
>> my rain gauge funnel and I get the slow drip.
>> It must be a very uncomfortable task with all the bird spikes around the 
>> outside…
>> Cheers,
>> Bob
>> grattans.org/wx <http://grattans.org/wx>
>> 
>> On Monday, May 1, 2023 at 7:28:56 AM UTC-4 Paul R Anderson wrote:
>>> Very strange blocked rain funnel would be the number one suspect. Only 
>>> other thing that comes to mind is residual 'rain' falling from a tree 
>>> canopy, or any other object that could hold rain droplets, and release them 
>>> long after the rain shower has ended. Wondering if any trees have started 
>>> to encroach on the area above your rain gauge?
>>> 
>>> Paul
>>> 
>>> On Mon, May 1, 2023 at 7:03 AM Steve C > wrote:
>>>> I removed it again yesterday and checked the tip bucket and entrance and 
>>>> exit paths for blockages but found none. The rain ended several hours ago, 
>>>> but my Vue is still counting .01" every few minutes this morning.
>>>> 
>>>> http://livefreeorpi.com <http://livefreeorpi.com/> 
>>>> 
>>>> On Sunday, April 30, 2023 at 1:27:57 PM UTC-4 Karen K wrote:
>>>>> I remember such behavior when a spider let the remains of her meals drop 
>>>>> into the rain bucket.
>>>>> 
>>>>> Graham Eddy schrieb am Sonntag, 30. April 2023 um 02:46:00 UTC+2:
>>>>>> is the outlet from rain bucket partially blocked?
>>>>>> ⊣GE⊢
>>>>>> 
>>>>>> 
>>>>>>> On 29 Apr 2023, at 11:48 pm, Steve C > wrote:
>>>>>>> 
>>>>>> 
>>>>>>> Important distinction! I meant to mention that. Yes, the software seems 
>>>>>>> perfectly fine. The console is reporting the 'slow drip' and WeeWX logs 
>>>>>>> it accordingly. Being a hardware issue I can move this to a Davis forum 
>>>>>>> if it is inappropriate here. 
>>>>>>> 
>>>>>>> On Saturday, April 29, 2023 at 9:42:42 AM UTC-4 Tom Keffer wrote:
>>>>>>>>  What does the console show?
>>>>>>>> 
>>>>>>>> On Sat, Apr 29, 2023 at 6:27 AM Steve C > wrote:
>>>>>>>>> Sorry for the long post, but the details might matter. We had a 
>>>>>>>>> significant rain event last weekend and my rain gauge responded in a 
>>>>>>>>> very weird way (which it has done before). It was raining when I got 
>>>>>>>>> up in the AM, 1/2 inch collected already. After about 3/4in, it 
>>>>>>>>> POURED and the rain rate slowed to something like .07in/hour. I 
>>>>>>>>> replaced the rain gauge (with the Davis rehab kit) last fall and went 
>>>>>>>>> out in the downpour to check the bucket/collector. No blockages, not 
>>>>>>>>> full of water...
>>>>>>>>> 
>>>>>>>>> My next door neighbor's device report 2.19" of rain when it ended 
>>>>>>>>> that day. Mine reported 1.90", however it continued to report .01 or 
>>>>>>>>> .02 clicks at a time until it finally stopped at .42" the next day 
>>>>>>>>> (although we had no rainfall) for a storm total of 2.32", not 
>>>>>>>>> terribly far off from my neighbor's 2.19".  I have attached the chart 
>>>>>>>>> that illustrates the slow collection- as if the collection was full 
>>>>>>>>> of water that slowly leaked out (can't be the case). 
>>>>>>>>> 
>>>>>>>>> The very next day we had a brief, heavy thunderstorm. Both my 
>>>>>>>>> neighbor and I reported the same .30" for the event.
>>>>>>

Re: [weewx-user] VantageVue rain collector delay

[Graham Eddy]

is the outlet from rain bucket partially blocked?
⊣GE⊢

> On 29 Apr 2023, at 11:48 pm, Steve C  wrote:
> 
> Important distinction! I meant to mention that. Yes, the software seems 
> perfectly fine. The console is reporting the 'slow drip' and WeeWX logs it 
> accordingly. Being a hardware issue I can move this to a Davis forum if it is 
> inappropriate here. 
> 
> On Saturday, April 29, 2023 at 9:42:42 AM UTC-4 Tom Keffer wrote:
>>  What does the console show?
>> 
>> On Sat, Apr 29, 2023 at 6:27 AM Steve C > wrote:
>>> Sorry for the long post, but the details might matter. We had a significant 
>>> rain event last weekend and my rain gauge responded in a very weird way 
>>> (which it has done before). It was raining when I got up in the AM, 1/2 
>>> inch collected already. After about 3/4in, it POURED and the rain rate 
>>> slowed to something like .07in/hour. I replaced the rain gauge (with the 
>>> Davis rehab kit) last fall and went out in the downpour to check the 
>>> bucket/collector. No blockages, not full of water...
>>> 
>>> My next door neighbor's device report 2.19" of rain when it ended that day. 
>>> Mine reported 1.90", however it continued to report .01 or .02 clicks at a 
>>> time until it finally stopped at .42" the next day (although we had no 
>>> rainfall) for a storm total of 2.32", not terribly far off from my 
>>> neighbor's 2.19".  I have attached the chart that illustrates the slow 
>>> collection- as if the collection was full of water that slowly leaked out 
>>> (can't be the case). 
>>> 
>>> The very next day we had a brief, heavy thunderstorm. Both my neighbor and 
>>> I reported the same .30" for the event.
>>> 
>>> Weewx  4.9.1
>>> Vantage Vue with an IPconnect.  
>>> 
>>> We're looking at another 1-3" of rain this weekend, and I'd love to hear 
>>> any suggestions!
>>> 
>>> Thanks,
>>> Steve
>>> 
>> 
>>> -- 
>>> 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/f4c19b77-1dd3-4573-9bec-ac5098a68158n%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/47944903-4d2a-4ca7-94d9-a3e0add0fd86n%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/8C9B81ED-90CD-4F2B-A1C3-731296ED737E%40geddy.au.

Re: [weewx-user] Error in log. How to find what issue actually is?

[Graham Eddy]

looks like to separate problems
(1) something in interceptor driver - might be benign (ignorable), or might be 
serious
(2) logging misconfigured. check the syslog interface mechanism for your 
specific o/s
⊣GE⊢

> On 27 Apr 2023, at 11:00 am, Marcin Metter  wrote:
> 
> I've been seeing the following error recently not sure what is going on. 
> Looks like some file is missing.
> 
> I am running mitct02/weewx docker image (/ 
> https://registry.hub.docker.com/r/mitct02/weewx/) on a Synology NAS. It use 
> to work in the past not sure wy it now fails? Any hints on how to debug this?
> 
> --- Logging error ---
> Traceback (most recent call last):
> File "/home/weewx/bin/user/interceptor.py", line 2550, in genLoopPackets
> data = self._device.get_queue().get(True, self._queue_timeout)
> File "/usr/lib/python3.10/queue.py", line 179, in get raise Empty
> _queue. Empty
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
> File "/usr/lib/python3.10/logging/handlers.py", line 987, in emit 
> self.socket.send(msg)
> OSError: [Errno 9] Bad file descriptor
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
> File "/usr/lib/python3.10/logging/handlers.py", line 908, in 
> _connect_unixsocket self.socket.connect(address)
> FileNotFoundError: [Errno 2] No such file or directory
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
> File "/usr/lib/python3.10/logging/handlers.py", line 990, in emit 
> self._connect_unixsocket(self. Address)
> File "/usr/lib/python3.10/logging/handlers.py", line 919, in 
> _connect_unixsocket self.socket.connect(address)
> FileNotFoundError: [Errno 2] No such file or directory
> Call stack:
> File "/home/weewx/bin/weewxd", line 249, in main()
> File "/home/weewx/bin/weewxd", line 154, in main engine. Run()
> File "/home/weewx/bin/weewx/engine.py", line 208, in run for packet in 
> self.console.genLoopPackets():
> File "/home/weewx/bin/user/interceptor.py", line 2566, in genLoopPackets 
> logdbg('empty queue')
> File "/home/weewx/bin/user/interceptor.py", line 284, in logdbg log. 
> Debug(msg)
> Message: 'empty queue'
> Arguments: ()
> 
> -- 
> 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/2f40bb32-bb14-4e82-bd47-051629f86de7n%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/B396A1BC-04D6-43AD-A3B7-3242B4C7F3EA%40geddy.au.

Re: [weewx-user] water tank level monitoring ?

[Graham Eddy]

i continue to run my old pressure river level sensor with my new ultrasound 
river level sensor.
i found the cable from pressure sensor (at river bottom) to prioprietary 
transmitter (above flood level) very inconvenient, whereas ultrasound 
sensor/transmitter are together (above flood level), much more convenient.
as i am measuring out in the open, i don’t have the echo issues described for a 
tank. but i will add that there are pressure sensors avail for LoRaWAN.
cheers
⊣GE⊢

> On 19 Apr 2023, at 3:41 am, MikeQ  wrote:
> 
> Having worked on industrial water systems for many years, I highly recommend 
> you use a pressure transducer to measure water tank levels instead of 
> ultrasonics.  I have a 2500 gal poly irrigation tank in my yard with a 
> booster pump.  It was there when I bought the house so I didn't get to pick 
> the tank and I had to use an ultrasonic in the top of tank as there were no 
> locations to mount a pressure transducer at the bottom of the tank.  
> Ultrasonics in tanks need to be mounted in the middle of the tank so they are 
> not effected by the tank walls, and at low water levels you can have issues 
> with the signal bouncing off the bottom of the tank.  Even with a good 
> mounting location, you are going to have some echo in a closed tank and that 
> will make your signal less stable.

-- 
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/4F548CF6-9532-405E-9C55-811AEBB2613A%40geddy.au.

Re: [weewx-user] water tank level monitoring ?

[Graham Eddy]

i put a detailed description of lorawan river level/temp sensors under weewx in 
this forum not long ago. a search will find it. cheers
⊣GE⊢

> On 17 Apr 2023, at 9:38 am, Tim Tuck  wrote:
> 
> Just wondering if anyone has network attached water tank level meters ?
> 
> Also wondering if anyone has such things integrated with Weewx ?

-- 
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/42E23933-1FA2-4C74-B4FC-E49BB0F8138B%40geddy.au.

Re: [weewx-user] weewx with davis weather station and ecowitt gw1000

[Graham Eddy]

congratulations to gary for a brilliant diagnosis
⊣GE⊢

> On 9 Apr 2023, at 12:44 pm, Mike  wrote:
> 
> i have found the excluded fields option for rain in weewx.conf, I have added 
> all the lightning fields and it has sorted the issue.

-- 
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/1F174B9B-C96E-4500-9541-C1C33E568A32%40geddy.au.

[weewx-user] weekly chart strips

[Graham Eddy]

suppose you look at a given weekly plot of some observation e.g. outside 
temperature.
suppose further that you can scroll left or right to see earlier or later 
weekly plots - much easier to see trends going over months e.g. how the 
temperature is varying over several months.
(in my case looking at rainfall and river level together are of most interest)

i have implemented this on my site, by
 * creating an archive of all weekly plots of all observations that my weather 
stations have measured
 * implementing infinite load-on-demand scrolling left-right through all the 
weekly plots of a given observation
 * scrollable strips for every observation the station supports
 * allow pick a start date so it starts centred on some historical time rather 
than scrolling through years of plots (my weewx ones start in 2007 with just a 
VP2)

i am still refining it, but it might give people some ideas.
see wx.geddy.au and reveal ‘Week Strips’.
cheers
⊣GE⊢

-- 
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/88F089AA-8B4F-427D-95B4-F4E4DF40BA5B%40geddy.au.

Re: [weewx-user] meanmax not working with data_binding

[Graham Eddy]

reading weewx/manager.py and weewx/xtypes.py, i think i see why it is not 
working. the log shows the following string exactly once:
DEBUG weewx.manager: Daily summary version is 4.0
which means exactly one DaySummaryManager instance is created (for wx_binding), 
meaning none for the other database (gw1000_binding), so when xtypes evaluates 
the external data_type’s meanmax aggregation it has no daily summary tables and 
silently gives up on it → nobody claims the evaluation so the original tag text 
is not substituted with a value

is there any reason a $data_binding is not allocated a DaySummaryManager 
instance for its database?
⊣GE⊢

> On 12 Mar 2023, at 8:45 pm, Graham Eddy  wrote:
> 
> i have updated the NOAA reports to include fields from another weewx database 
> (using $data_binding in tags). these external fields all work fine for 
> min,mintime,max,maxtime,avg,count but not for meanmax,meanmin. weewx v4.10.2
> 
> the period tags are $day,$month,$year (all at least one day) so i expect 
> meanmax,meanmin to work, but instead they are not recognised as valid, and 
> the (unresolved) tag literal text is inserted instead of its value
> 
> following is an extract from the generated report text file showing the mixed 
> success. i instrumented the report to display a few values that illustrate 
> the problem:
> ——
>   
> $~month.cloudbase.count.raw=8928
> $~month.cloudbase.avg.format($~Height,$~NONE,add_label=False)=  1129
> $~month($~data_binding="wx_binding").cloudbase.avg.format($~Height,$~NONE,add_label=False)=
>   1129
> $~month.cloudbase.meanmax.format($~Height,$~NONE,add_label=False)=  2263
> $~month($~data_binding="wx_binding").cloudbase.meanmax.format($~Height,$~NONE,add_label=False)=
>   2263
> $~month($~data_binding="gw1000_binding").UV.count.raw=8927
> $~month($~data_binding="gw1000_binding").UV.avg.format($~Uv,$~NONE,add_label=False)=
>  2
> $~month($~data_binding="gw1000_binding").UV.meanmax.format($~Uv,$~NONE,add_label=False)=$month($data_binding="gw1000_binding").UV.meanmax.format($Uv,$NONE,add_label=False)
> 
> ——
> to explain,
> the excerpt lines are in the form ’tag=value’, where in the ’tag’ i have 
> suffixed the $ with ~ to suppress substitution for display purposes. it shows 
> data_type ‘cloudbase', which is in the local database (data_binding 
> “wx_binding”), and data_type ‘UV’, which is in the other weewx database 
> (data_binding “gw1000_binding”)
> ‘cloudbase’ works for aggregations count,avg,meanmax as expected, even when 
> the explicit $data_binding argument is used
> ‘UV’ works for count,avg but not meanmax. this proves the data_binding works 
> and that UV is a valid data_type there, as well as showing meanmax does not 
> work. because of this, i have not included extracts from the weewx .conf 
> files showing definitions
> 
> following is extract from the log, running ‘wee_reports’ with weewx debug=5. 
> it begins with starting wee_reports and finishes when the report has 
> completed:
> ——
> Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Loading 
> service weewx.engine.StdTimeSynch
> Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Finished 
> loading service weewx.engine.StdTimeSynch
> Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Loading 
> service user.mqtt.MQTTInward
> Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG user.mqtt:  
> starting v0.1.3
> Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG user.mqttif:  localhost:1883 True> request connect
> Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG user.mqttif: 
>  request subscribe
> Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG user.mqttif: 
>  request subscribe
> Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG user.mqttif: 
>  request subscribe
> Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG user.mqttif: 
>  request subscribe
> Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG user.mqttif: 
>  request subscribe
> Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG user.mqttif: 
>  request subscribe
> Mar 12 19:33:57 paperbark wee_reports[204990] INFO user.mqtt:  
> started
> Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Finished 
> loading service user.mqtt.MQTTInward
> Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Loading 
> service user.vitalstats.VitalStatsSvc
> Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Finished 
> loading service user.vitalstats.VitalStatsSvc
> Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Loading 
> service weewx.engine.StdConvert
> Mar 12 19:33:57 paperbark wee_reports[204990] INFO weewx.engine:

[weewx-user] meanmax not working with data_binding

[Graham Eddy]

i have updated the NOAA reports to include fields from another weewx database 
(using $data_binding in tags). these external fields all work fine for 
min,mintime,max,maxtime,avg,count but not for meanmax,meanmin. weewx v4.10.2

the period tags are $day,$month,$year (all at least one day) so i expect 
meanmax,meanmin to work, but instead they are not recognised as valid, and the 
(unresolved) tag literal text is inserted instead of its value

following is an extract from the generated report text file showing the mixed 
success. i instrumented the report to display a few values that illustrate the 
problem:
——
  
$~month.cloudbase.count.raw=8928
$~month.cloudbase.avg.format($~Height,$~NONE,add_label=False)=  1129
$~month($~data_binding="wx_binding").cloudbase.avg.format($~Height,$~NONE,add_label=False)=
  1129
$~month.cloudbase.meanmax.format($~Height,$~NONE,add_label=False)=  2263
$~month($~data_binding="wx_binding").cloudbase.meanmax.format($~Height,$~NONE,add_label=False)=
  2263
$~month($~data_binding="gw1000_binding").UV.count.raw=8927
$~month($~data_binding="gw1000_binding").UV.avg.format($~Uv,$~NONE,add_label=False)=
 2
$~month($~data_binding="gw1000_binding").UV.meanmax.format($~Uv,$~NONE,add_label=False)=$month($data_binding="gw1000_binding").UV.meanmax.format($Uv,$NONE,add_label=False)

——
to explain,
the excerpt lines are in the form ’tag=value’, where in the ’tag’ i have 
suffixed the $ with ~ to suppress substitution for display purposes. it shows 
data_type ‘cloudbase', which is in the local database (data_binding 
“wx_binding”), and data_type ‘UV’, which is in the other weewx database 
(data_binding “gw1000_binding”)
‘cloudbase’ works for aggregations count,avg,meanmax as expected, even when the 
explicit $data_binding argument is used
‘UV’ works for count,avg but not meanmax. this proves the data_binding works 
and that UV is a valid data_type there, as well as showing meanmax does not 
work. because of this, i have not included extracts from the weewx .conf files 
showing definitions

following is extract from the log, running ‘wee_reports’ with weewx debug=5. it 
begins with starting wee_reports and finishes when the report has completed:
——
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Loading 
service weewx.engine.StdTimeSynch
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Finished 
loading service weewx.engine.StdTimeSynch
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Loading 
service user.mqtt.MQTTInward
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG user.mqtt:  
starting v0.1.3
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG user.mqttif:  request connect
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG user.mqttif:  request subscribe
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG user.mqttif:  request subscribe
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG user.mqttif:  request subscribe
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG user.mqttif:  request subscribe
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG user.mqttif:  request subscribe
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG user.mqttif:  request subscribe
Mar 12 19:33:57 paperbark wee_reports[204990] INFO user.mqtt:  
started
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Finished 
loading service user.mqtt.MQTTInward
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Loading 
service user.vitalstats.VitalStatsSvc
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Finished 
loading service user.vitalstats.VitalStatsSvc
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Loading 
service weewx.engine.StdConvert
Mar 12 19:33:57 paperbark wee_reports[204990] INFO weewx.engine: StdConvert 
target unit is 0x1
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Finished 
loading service weewx.engine.StdConvert
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Loading 
service weewx.engine.StdCalibrate
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Finished 
loading service weewx.engine.StdCalibrate
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Loading 
service weewx.engine.StdQC
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Finished 
loading service weewx.engine.StdQC
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.engine: Loading 
service weewx.wxservices.StdWXCalculate
Mar 12 19:33:57 paperbark wee_reports[204990] DEBUG weewx.wxservices: 
Calculations for LOOP packets: {'pressure': 'prefer_hardware', 'altimeter': 
'prefer_hardware', 'appTemp': 'prefer_hardware', 'barometer': 
'prefer_hardware', 'cloudbase': 'prefer_hardware', 'dewpoint': 
'prefer_hardware', 'heatindex': 'prefer_hardware', 'humidex': 
'prefer_hardware', 'inDewpoint': 'prefer_hardware', 'maxSolarRad': 
'prefer_hardware', 'rainRate': 'prefer_hardware', 'windchill': 

Re: [weewx-user] wee_import

[Graham Eddy]

isn’t this parsed as a list?
⊣GE⊢

> On 12 Mar 2023, at 12:28 pm, gjr80  wrote:
> 
>  delimiter = ,

-- 
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/40AFBA0A-B077-4F4A-8614-14109D231389%40geddy.au.

Re: [weewx-user] MQTTSubscribe service - not getting extraTemp1 or 2

[Graham Eddy]

looks like wrongly set unit label (not unit name)
⊣GE⊢

> On 3 Mar 2023, at 12:44 pm, lloyd...@gmail.com  wrote:
> 
> it shows on the skin (whatever the default is)  RTD Temperature 20%  and 
> TMP117 temperature 18% for temperatures of 20.46 and 18.09 respectively

-- 
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/0AE2C082-0C84-4856-878E-AFF8353CE8F4%40geddy.au.

Re: [weewx-user] new install LOOP batch try #3; error: Unable to wake up Vantage console

[Graham Eddy]

sounds like XON/XOFF problem (slow receiving side hardware/driver)
⊣GE⊢

> On 20 Feb 2023, at 4:15 am, Brian Waligorski / N6RZR  
> wrote:
> 
> I tried each successive slower rate until I arrived at 1200 baud and it's 
> been now a month with no problem.
> 

-- 
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/B89519E1-8AE5-4665-97FE-6AD194724640%40geddy.au.

Re: [weewx-user] No Rain data used

[Graham Eddy]

rain in LOOP packet (inches) equals rain in wsview app (mm)
⊣GE⊢

> On 7 Feb 2023, at 11:15 pm, Christian H.  wrote:
> 
> LOOP:   2023-02-07 13:10:50 CET (1675771850) 'dateTime': '1675771850', 
> 'daymaxwind': '6.0', 'dummyTemp': '96.3', 'inHumidity': '38', 'inTemp': 
> '64.22', 'luminosity': '12780.0', 'outHumidity': '62', 'outTemp': '39.38', 
> 'p_dayRain': '0.003937007874015749', 'p_monthRain': '0.03937007874015748', 
> 'p_rain': 'None', 'p_rainRate': '0.0', 'p_stormRain': '0.0', 'p_weekRain': 
> '0.03937007874015748', 'p_yearRain': '0.03937007874015748', 'pressure': 
> '30.229848203750002', 'relbarometer': '1023.7', 'usUnits': '1', 'UV': '0', 
> 'uvradiation': '0.0', 'windDir': '71', 'windGust': '6.71082817913', 
> 'windSpeed': '4.026495333490748', 'ws90_batt': '2.96', 'ws90_sig': '4'
> LOOP:   2023-02-07 13:11:01 CET (1675771861) 'dateTime': '1675771861', 
> 'dummyTemp': '96.3', 'usUnits':
> 
> 

-- 
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/469715AB-5867-483D-A327-F9F2D01F66E5%40geddy.au.

Re: [weewx-user] Backup Sensors

[Graham Eddy]

untested: put in Corrections section of weewx.conf something like
  PRIMARY_V = PRIMARY_V if PRIMARY_V in locals() else BACKUP_V
(weewx packet is used as local bindings in python eval)
⊣GE⊢

> On 1 Feb 2023, at 5:18 pm, p q  wrote:
> 
> Yes, but by modifying the driver code, which is not the preferred path. There 
> is probably a better way.
> 
> On Wed, Feb 1, 2023 at 10:30 AM dshanske  > wrote:
>> Was wondering about this. I have some issues with one of my sensors going 
>> offline. I am working on a secondary way to notify me if this goes offline, 
>> but I was wondering if anyone came up with a way to have a secondary sensor 
>> be used if the primary goes offline.
>> 
>> -- 
>> 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/b2f32836-f32b-472b-9a0d-4d1036cbba2en%40googlegroups.com
>>  
>> .
> 
> 
> -- 
> Peter Quinn
> (415)794-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/CAA1SM23nOxt4XCz1QWWcTrumn5nUFpZ9qDw0TyTFUts-_fdEFA%40mail.gmail.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3C68357B-3B9C-474A-91BD-F60795978667%40geddy.au.

[weewx-user] new river level monitor

[Graham Eddy]

i posted some time ago about my trusty old river level monitor. i am still 
receiving occasional enquiries about it - yes, unfortunately that product i 
used is no longer available. whilst it is still working for me, i have now 
deployed a new river level monitor in parallel, some details below

old river level monitor

Aquagauge provided a radio receiver with serial interface and a number of 
sensor types with radio transmitters. a receiver could support up to 8 
transmitters. the radio and serial protocols are proprietary

i wrote a weewx service that read the serial interface and inserted the data 
values into weewx packets. later i migrated this to a daemon that emitted the 
data as mqtt messages, and weewx reads the mqtt messages. this works fine; it 
is still in use

this river level sensor is pressure-based i.e. the probe sits on river bottom 
(in my case wrapped around a brick and tucked into a river bank nook) and 
measures the water pressure. there is a very inconvenient cable from the probe 
to the transmitter. the latter measures atmospheric pressure, the pressure 
difference is the weight of the water above the sensor thence deriving water 
depth. it proved to be quite accurate

the transmitter has suffered many travails, the latest being going for a swim 
during a flood when the bridge it was on was swept downstream. it is very 
robust but now failing more often and i fear one day soon not being able to 
rescusitate it → motivation for replacement. this product is no longer sold or 
supported

new river level sensor

i decided to try an ultrasound sensor i.e. the probe measures round-trip time 
for a signal reflected from river surface back to probe with known speed of 
signal. this means there is no cable needed to run into the river

my river level sensor must be a commercial off-the-shelf product, for which i 
am happy to write interface software. it also has to be wireless connection to 
RPi at least 50 meters away and be powered by long-life battery

i picked a Dragino LDDS75 Distance Detector 
(https://www.dragino.com/products/distance-level-sensor/item/161-ldds75.html). 
i mounted it under the sparkling new bridge i built over the river, higher than 
the old bridge. it sends quite large and complex messages via mqtt, so i wrote 
a daemon that plucks the salient data and re-publishes as simple message, 
imported into weewx. my daemon also configures a fix-point height for the 
sensor, so the simplified mqtt message includes a ‘level’ field as well as 
‘distance’ for easy digestion

this is a LoRaWAN device so provides the long distance and battery longevity i 
require

radio receiver server

the new river level sensor is the first of several sensors on my new open radio 
network, as opposed to the closed proprietary radio network per Aquagauge, so i 
need a radio transceiver to talk to them. i assume familiarity with LoRaWAN 
(https://www.thethingsnetwork.org/docs/lorawan/architecture/)

for the local LoWRaWAN gateway, i put a RAK 2245 LoRaWAN HAT 
(https://www.rakwireless.com/en-us/products/lpwan-gateways-and-concentrators/rak2245-pihat)
 on an RPi 4B and installed RAK’s gateway software from their GitHub

i tried using the chirpstack LoRaWAN stack running on local server but couldn’t 
get it to work reliably, it seemed to work only intermittently. i think i was 
having trouble with not picking up the radio packet preamble but, not being a 
radiohead, gave it up as too much like hard work. i tried The Things Network 
stack (https://www.thethingsindustries.com/docs/getting-started/ttn/) and, to 
paraphrase steve jobs, ‘it just worked’. i am using the ’community edition’, 
which is a subscribed but free service. the downside is that the network server 
and join server run on TTN’s hardware over the internet so i lose device 
connectivity when internet link is down. they provide the software to run your 
own copy of the stack, which i plan to do in future

so, the river level sensor emits radio packets, my RPi gateway receives the 
packets and sends to TTN stack, the TTN stack processes and emits them as 
complex mqtt messages, which my dameon picks up and simplifies, then weewx 
digests the simplified mqtt messages. (i have chosen to put LoRaWAN gateway on 
a separate RPi from the weewx RPi)

the TTN stack’s mqtt broker is on their remote server. i have chosen to bridge 
that mqtt broker to my RPi gateway so that, from my home network’s perspective, 
all that LoRaWAN stuff is happening on my RPi gateway. this fits my plan to 
move the TTN stack to the RPi gateway in future

the RAK 2245 includes an itty bitty antenna. i get a good signal and reliable 
connection at 100 meters, haven’t tested further distance. LoRa supports 10 km 
with a decent antenna

additional sensors

the LoRaWAN gateway supports a lot of LoRa devices simultaneously, it is just a 
case of joining them to the radio network and processing their dat

i have also deployed a river temperature sensor (replacing the VP2 

Re: [weewx-user] line gaps

[Graham Eddy]

fair request, but i don’t GitHub, so some code follows.
my old RPi test box is now my production LoRaWAN box, so i worked using my 
production weewx box, so testing is pretty minimal (seems to work on my two 
graphs)

see weeplot/utilities.py:520 on weewx 5.8.0:

line = []
last_x = None
for xy in zip(x, y):
#GE start new
# If the y coordinate is None, ignore it
if xy[1] is None:
continue
#GE end new 
dx = xy[0] - last_x if last_x is not None else 0
last_x = xy[0]
#GE start original
#GE# If the y coordinate is None or dx > maxdx, that marks a break
#GEif xy[1] is None or (maxdx is not None and dx > maxdx):
#GE end original
#GE start new
# If dx > maxdx, that marks a break
if (maxdx is not None and dx > maxdx):
#GE end new 
# If the length of the line is non-zero, yield it
if len(line):
yield line
line = [] if xy[1] is None else [xy]
else:   
line.append(xy)
if len(line):
yield line

cheers
⊣GE⊢

> On 19 Jan 2023, at 12:50 pm, Tom Keffer  wrote:
> 
> Speaking of dumb, in retrospect, this seems like a dumb choice. It should be 
> at least optional.
> 
> The code was written about 10 years ago. I simply cannot remember why I chose 
> to always honor None values, despite any value of line_gap_fraction.
> 
> A PR would be welcome, should you wish to write one.
> 
> On Wed, Jan 18, 2023 at 4:55 PM Graham Eddy  <mailto:g...@geddy.au>> wrote:
>> this means line_gap_fraction relates only to interval gaps of whole records, 
>> not of column value gaps within successive records.
>> hmm, inserting interpolated values to cover interval gaps in a column can 
>> only be done to past records - nope, i don’t want to go there...
>> well, now i know - learn to love the ‘mark’ not the ‘line'.
>> thanks
>> ⊣GE⊢
>> 
>>> On 19 Jan 2023, at 2:49 am, Tom Keffer >> <mailto:tkef...@gmail.com>> wrote:
>>> 
>>> You're not doing something dumb. None values always mark line breaks. 
>>> 
>>> On Wed, Jan 18, 2023 at 6:30 AM Graham Eddy >> <mailto:g...@geddy.au>> wrote:
>>> 
>> 
>> 
>> -- 
>> 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 
>> <mailto:weewx-user+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/D4BCD919-180F-45F4-AA01-845B49CB9A74%40geddy.au
>>  
>> <https://groups.google.com/d/msgid/weewx-user/D4BCD919-180F-45F4-AA01-845B49CB9A74%40geddy.au?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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEAoEWv3TdnHZ%2BJeWmbQV7t20-h2N9La3geer7eiLyavMA%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEAoEWv3TdnHZ%2BJeWmbQV7t20-h2N9La3geer7eiLyavMA%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/6EF71977-00B3-465E-A252-2CC02F7B1C3E%40geddy.au.

Re: [weewx-user] line gaps

[Graham Eddy]

this means line_gap_fraction relates only to interval gaps of whole records, 
not of column value gaps within successive records.
hmm, inserting interpolated values to cover interval gaps in a column can only 
be done to past records - nope, i don’t want to go there...
well, now i know - learn to love the ‘mark’ not the ‘line'.
thanks
⊣GE⊢

> On 19 Jan 2023, at 2:49 am, Tom Keffer  wrote:
> 
> You're not doing something dumb. None values always mark line breaks. 
> 
> On Wed, Jan 18, 2023 at 6:30 AM Graham Eddy  <mailto:g...@geddy.au>> wrote:
> 

-- 
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/D4BCD919-180F-45F4-AA01-845B49CB9A74%40geddy.au.

[weewx-user] line gaps

[Graham Eddy]

i am getting a sequence of points plotted rather than a line showing.
line_type = solid
line_gap_fraction = 0.3
the points are 20 mins apart. 20min/24hrs = 0.013 so i expect the points to be 
joined.
i have tried line_gap_fraction 0.9 and - just to be thorough - 1.0 and (being 
silly) 10.0 - with no change.
any ideas how to ‘join the dots’?
google is my friend but he didn’t help this time.
cheers


⊣GE⊢

-- 
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/5E209B62-AD8B-4F6E-8219-EC2778D16E35%40geddy.au.

Re: [weewx-user] Davis VP2 reliability with Rasp Pi zero

[Graham Eddy]

It is much more likely your power supply being the problem. Get a ups to smooth the spikes (dunno if rpi hat does that)⊣ GE ⊢    phone➔brevityOn 6 Jan 2023 12:46 pm, "iams...@gmail.com"  wrote:"What happens if you 'pull the plug' on your VP2? Does it keep running? Perhaps the batteries are bad?Yes, it keeps running, that is why it seems to be a weewx issue to me. In other words, if the Pi Zero running weewx were not connected to the VP2, the data logger memory would not get corrupted. In fact, weewx is able to recover data that was gathered during the power outage (while the Pi is shut down). It is only when power is restored that the data logger corruption happens. At least I assume that is really the root of the issue, I really don't know. All I know is that almost every time the power goes out, I get the record time error and all data recording and uploading stops.I've looked into getting a UPS for the Pi, which really appears to be nothing more than a $15 ext phone battery, but it seems to me this is a weewx problem that should be addressed. Alternately, I can contact Davis to see what they say."On Thursday, January 5, 2023 at 3:34:40 PM UTC-8 tke...@gmail.com wrote:It should work.What happens if you 'pull the plug' on your VP2? Does it keep running? Perhaps the batteries are bad?Personally, I use a UPS for both the weewx server and the VP2 and haven't had a memory corruption problem in at least a decade. So, you could try that.On Thu, Jan 5, 2023 at 11:30 AM iams...@gmail.com  wrote:I've been using weewx running on a Pi Zero with no other tasks. Unfortunately, I live in a area that suffers power losses, often during a weather events, so I lose that data. What typically happens is that when the power comes back on, I get the dreaded "..page timestamp... less than final timestamp..." error. The only way I have been able to address it is to use the memory dump and clear. I don't understand why this happens since the VP2 is running with battery backup, yet the memory on the datalogger gets corrupted. Is this an issue with weewx that could be addressed?Failing that, can I address this issue by adding a backup supply to my Pi Zero?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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/c833a23b-2957-4311-882a-cda796d0c928n%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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/7bd3876d-96a1-4c3a-82fb-c4f406234066n%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/709fe62a-0bad-4448-9b1f-318c3e05bb72%40email.android.com.

Re: [weewx-user] Never thought it could happen

[Graham Eddy]

i was travelling when it flooded back home (se oz) 6 weeks ago. lots of folk 
watch my river depth graph so as the value unexpectedly went off the top of 
graph, i updated the y-scale to compensate a few times. someone asked me to 
stop increasing it because i was dragging the river level up :-)
⊣GE⊢

> On 1 Jan 2023, at 10:21 am, Gerard Cerchio  wrote:
> 
> When I set up my station  I 
> wrote in 2 rain gauges, a weekly and an annual. I had never seen more than 3 
> inches of rain in a week so I set a 4 rain inch high graphic for the week. In 
> this single past week we got more rain then we got all year. Who'd a thunk 
> 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/75e68c94-3b32-49a2-91ec-b10f91e295b8n%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/51E45CF8-8603-4BE6-8E76-28F8D194B96E%40geddy.au.

Re: [weewx-user] Only use wee_import without connecting a weather station

[Graham Eddy]

perhaps consider the provided ‘fileparse’ driver - see 
~weewx/examples/fileparse/readme.txt

> On 29 Aug 2022, at 7:43 pm, Stein Arne Storslett  wrote:
> 
> Is there a way to only run the weewx database with data through "wee_import" 
> without connecting a weather station?
> I.e. just producing the web pages / reports.
> 
> Re another thread I have issues getting weewx to connect to my weather 
> station console, the Cotech Weather Station sold by ClasOhlson in the 
> nordics, Europe.
> 
> However I've been able to produce data via the station's (somewhat arcane) 
> software WeatherHome so I want to create the reports based on 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/fc0712e7-326d-45ed-811b-3e4c6c3a94b0n%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/9FA4093A-41D4-4B19-928D-C762200257EB%40geddy.au.

Re: [weewx-user] howto fix weewx sqlite database

[Graham Eddy]

15 years of data, running happily on RPi 4B:
graham@paperbark:/home/weewx/archive $ ls -l weewx.sdb 
-rw-r--r-- 1 weewx weewx 175935488 Jul 11 00:55 weewx.sdb

> On 11 Jul 2022, at 12:43 am, Fische Namenlos  wrote:
> 
> my station is using sqlite database (weewx.sdb) for nearly 5 years, and now - 
> I suppose - is getting to big for my Raspi-server, it stops working/writting.

-- 
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/8C3EB25A-F4A3-4D14-B43C-16556831AF91%40geddy.au.

Re: [weewx-user] LOOP try problem ...

[Graham Eddy]

as tom noted, you need to configure the vp2 console device to 300 secs to get 
reports each 5 mins (or change weewx.conf file to 1800 secs if every 30 mins 
sufficient)

this would not cause the read errors on the vp2, so is off-topic, but worth 
pointing out.
cheers

> On 18 Jun 2022, at 2:23 pm, mup...@gmail.com  wrote:
> 
>> The archive interval in the configuration file (300) does not match the 
>> station hardware interval (1800)

-- 
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/DBC76C09-79A4-4E00-B5FC-E6B12D8685AB%40geddy.au.

Re: [weewx-user] LOOP try problem ...

[Graham Eddy]

not the reported problem, but config error needs to be fixed nonetheless

> On 18 Jun 2022, at 1:14 am, mup...@gmail.com  wrote:
> 
> Jun 17 08:09:38 weewx-RPi weewx[83743] ERROR weewx.engine: The archive 
> interval in the configuration file (300) does not match the station hardware 
> interval (1800).
> Jun 17 08:09:38 weewx-RPi weewx[83743] INFO weewx.engine: Using archive 
> interval of 1800 seconds (specified by hardware)

-- 
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/33ED3171-3EDD-45D1-82B6-722E0DD6C809%40geddy.au.

Re: [weewx-user] vp2 - how to disable ch2?

[Graham Eddy]

did that - envoy has now forgotten the old wireless station [RESOLVED] - thanks

it has been a lot of years since the envoy was last unpowered!

> On 27 May 2022, at 6:21 am, gjr80  wrote:
> 
> I don't have an Envoy but I understand it is a case of removing all power 
> sources, including batteries, waiting for 10-20 seconds for any capacitance 
> to discharge and then power up again. Don't know I would put the batteries in 
> reverse though.
> 
> Gary
> 
> On Wednesday, 25 May 2022 at 21:05:36 UTC+10 Graham Eddy wrote:
> i can power down, pull it apart, put the batteries in backwards. how do i 
> reset it?
> (and why would wee_device be failing to reconfigure ch2 but work successfully 
> otherwise?)
> 
> 
>> On 25 May 2022, at 8:13 pm, gjr80 > > wrote:
>> 
>> Doesn't leave many options. Can't power down/reset the envoy?
>> 
>> Gary
>> 
>> On Wednesday, 25 May 2022 at 19:53:32 UTC+10 Graham Eddy wrote:
>> data logger is in an envoy
>> 
>> 
>>> On 25 May 2022, at 7:25 pm, gjr80 > wrote:
>>> 
>> 
>>> Can't you set transmitter IDs manually via the console?
>>> 
>>> Gary
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/f5fd67c3-594c-45d3-9000-8f2b09a31e51n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/f5fd67c3-594c-45d3-9000-8f2b09a31e51n%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/13B27969-E764-4CDF-80C8-5B336B8B9EE6%40geddy.au.

Re: [weewx-user] vp2 - how to disable ch2?

[Graham Eddy]

i can power down, pull it apart, put the batteries in backwards. how do i reset 
it?
(and why would wee_device be failing to reconfigure ch2 but work successfully 
otherwise?)

> On 25 May 2022, at 8:13 pm, gjr80  wrote:
> 
> Doesn't leave many options. Can't power down/reset the envoy?
> 
> Gary
> 
> On Wednesday, 25 May 2022 at 19:53:32 UTC+10 Graham Eddy wrote:
> data logger is in an envoy
> 
> 
>> On 25 May 2022, at 7:25 pm, gjr80 > > wrote:
>> 
> 
>> Can't you set transmitter IDs manually via the console?
>> 
>> Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/C6DEC2F7-0B3B-4FD4-ACD7-661727422852%40geddy.au.

Re: [weewx-user] vp2 - how to disable ch2?

[Graham Eddy]

data logger is in an envoy

> On 25 May 2022, at 7:25 pm, gjr80  wrote:
> 
> Can't you set transmitter IDs manually via the console?
> 
> Gary
> 
> On Wednesday, 25 May 2022 at 18:18:36 UTC+10 Graham Eddy wrote:
> QC is filtering out the bad values, but weewx server is currently resetting 
> after 4 failed retries on regular basis while the phantom station haunts the 
> vp2. there is no radio signal being transmitted to provide the extraTemp1 
> values, it is just a figment of data logger’s imagination. the phantom 
> battery-low apparently from the ex-station stopped yesterday, but the data 
> logger is still reporting the extraTemp1 despite my (failed) wee_device 
> instruction just now to desist
> 
> i do ‘wee_device —set-transmitter-type=2,10’ and it gives ’no ’ error.
> then i do ‘wee_device —info’ and it reports ch2 still enabled
> so it is not just a case of resetting memory/power
> 
> weewx v4.5.1 using python3.7 on RPi 4B running buster with usb/serial
> (vp2 firmware is from 2004. lately weewx has been resetting whenever the (now 
> ex-) extra station reported low battery, so this bogus extraTemp1 value 
> upsetting weewx is kinda understandable → i need to turn all vestiges of the 
> (ex-) extra station off)
> 
> 
>> On 25 May 2022, at 5:53 pm, Stephen Hocking > > wrote:
>> 
> 
>> Given such a whacko figure, perhaps under the [[Corrections]] section under 
>> [StdCalibrate], or more suitably, something under [StdQC].
>> 
>> On Wed, 25 May 2022 at 17:45, Graham Eddy > > wrote:
>> my old vantage pro2’s additional wireless temp station at ch2 (iss is at 
>> ch1) has carked it (crushed in tree fall). it exists no more; it is not 
>> transmitting. my vp2 data logger is faithfully reporting a phantom value of 
>> about 150 C (not bad for a river!) every few seconds, how do i disable this 
>> phantom?
>> 
>> i tried (with weewx not running) ‘wee_device --set-transmitter-type=2,10’ to 
>> set ch2 to none, but all i get is an error ‘No  received from Vantage 
>> console’, and it continues reporting the phantom when i start weewx again. 
>> how can i stop this phantom?
>> cheers
>> 
>> -- 
>> 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/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au
>>  
>> <https://groups.google.com/d/msgid/weewx-user/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au?utm_medium=email_source=footer>.
>> 
>> 
>> -- 
>>   "I and the public know
>>   what all schoolchildren learn
>>   Those to whom evil is done
>>   Do evil in return" W.H. Auden, "September 1, 1939"
>> 
>> 
>> -- 
>> 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/CA%2BxzKjDCR-xMeMrCDm7_Nq1XeJikmWSJ9N1TYcPezwLc0x7h%3Dw%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/CA%2BxzKjDCR-xMeMrCDm7_Nq1XeJikmWSJ9N1TYcPezwLc0x7h%3Dw%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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/3b764166-7458-4fd1-a0e7-4acbee17e7d4n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/3b764166-7458-4fd1-a0e7-4acbee17e7d4n%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/D38AF7A8-8AC0-4A50-8F49-F98A595EFEF3%40geddy.au.

Re: [weewx-user] vp2 - how to disable ch2?

[Graham Eddy]

QC is filtering out the bad values, but weewx server is currently resetting 
after 4 failed retries on regular basis while the phantom station haunts the 
vp2. there is no radio signal being transmitted to provide the extraTemp1 
values, it is just a figment of data logger’s imagination. the phantom 
battery-low apparently from the ex-station stopped yesterday, but the data 
logger is still reporting the extraTemp1 despite my (failed) wee_device 
instruction just now to desist

i do ‘wee_device —set-transmitter-type=2,10’ and it gives ’no ’ error.
then i do ‘wee_device —info’ and it reports ch2 still enabled
so it is not just a case of resetting memory/power

weewx v4.5.1 using python3.7 on RPi 4B running buster with usb/serial
(vp2 firmware is from 2004. lately weewx has been resetting whenever the (now 
ex-) extra station reported low battery, so this bogus extraTemp1 value 
upsetting weewx is kinda understandable → i need to turn all vestiges of the 
(ex-) extra station off)

> On 25 May 2022, at 5:53 pm, Stephen Hocking  wrote:
> 
> Given such a whacko figure, perhaps under the [[Corrections]] section under 
> [StdCalibrate], or more suitably, something under [StdQC].
> 
> On Wed, 25 May 2022 at 17:45, Graham Eddy  <mailto:g...@geddy.au>> wrote:
> my old vantage pro2’s additional wireless temp station at ch2 (iss is at ch1) 
> has carked it (crushed in tree fall). it exists no more; it is not 
> transmitting. my vp2 data logger is faithfully reporting a phantom value of 
> about 150 C (not bad for a river!) every few seconds, how do i disable this 
> phantom?
> 
> i tried (with weewx not running) ‘wee_device --set-transmitter-type=2,10’ to 
> set ch2 to none, but all i get is an error ‘No  received from Vantage 
> console’, and it continues reporting the phantom when i start weewx again. 
> how can i stop this phantom?
> cheers
> 
> -- 
> 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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au
>  
> <https://groups.google.com/d/msgid/weewx-user/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au?utm_medium=email_source=footer>.
> 
> 
> -- 
>   "I and the public know
>   what all schoolchildren learn
>   Those to whom evil is done
>   Do evil in return"  W.H. Auden, "September 1, 1939"
> 
> 
> -- 
> 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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/CA%2BxzKjDCR-xMeMrCDm7_Nq1XeJikmWSJ9N1TYcPezwLc0x7h%3Dw%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/weewx-user/CA%2BxzKjDCR-xMeMrCDm7_Nq1XeJikmWSJ9N1TYcPezwLc0x7h%3Dw%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/F4510CA0-CFDC-4855-A336-6A1FCED46B72%40geddy.au.

[weewx-user] vp2 - how to disable ch2?

[Graham Eddy]

my old vantage pro2’s additional wireless temp station at ch2 (iss is at ch1) 
has carked it (crushed in tree fall). it exists no more; it is not 
transmitting. my vp2 data logger is faithfully reporting a phantom value of 
about 150 C (not bad for a river!) every few seconds, how do i disable this 
phantom?

i tried (with weewx not running) ‘wee_device --set-transmitter-type=2,10’ to 
set ch2 to none, but all i get is an error ‘No  received from Vantage 
console’, and it continues reporting the phantom when i start weewx again. how 
can i stop this phantom?
cheers

-- 
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/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au.

Re: [weewx-user] Davis Data Logger - Issue

[Graham Eddy]

i reported earlier that i got a burst of weewx restarts by vantage driver when 
my extra vp2 station (wireless temp) battery started reporting low (i hadn’t 
noticed until this thread started). tom’s new retry patch not applied. this 
happened a second time recently viz. burst of restart activity when extra 
station reported low battery. nothing to do with power supplies or reboots, i 
am more inclined to point to an envoy or data logger/usb firmware bug (they are 
more than 15yo).
(it is possible this firmware bug could lead to phantom battery low reports; i 
think more likely they were genuine battery low events driving the error)

sadly this extra wireless vp2 station has just been borked - it was under water 
for a week in 2010 floods (i mounted it higher after that :-) but a few days 
ago couldn’t survive 2-3 tonnes of tree branch crushing it on rocks. it will be 
replaced by a much much cheaper ecowitt remote temp probe (i run dual 
vp2/gw1000)

> On 19 May 2022, at 1:09 am, Paul Dunphy  wrote:
> 
> Whatever it is, it's related to RPis talking to a Davis Logger via USB. I 
> have a couple of powered USB hubs lying around. I can try putting one of them 
> on in the next day or so . . . now that you mention it, I never had any 
> trouble with an RPi 3. However, it did/does manifest itself on three 
> different RPi 4s. I'll report back when I have results using a powered hub.
> 
> - Paul VE1DX
> 
> On 2022-05-18 11:14 a.m., Tom Keffer wrote:
>> I don't know that it's a "timing issue," but it could certainly be a power 
>> issue. 
>> 
>> The USB power supplies for many RPis can be barely adequate. In particular, 
>> the RPi 4 uses a lot of power. It doesn't take much for the power to sag, 
>> resulting in errors.
>> 
> 
>   >snip<
> 
> -- 
> 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/9d5bf73c-2c97-fd8b-6a14-06dfbeb751d3%40gmail.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/C3966CBD-3617-43B9-9D9A-92FF650FC34F%40geddy.au.

Re: [weewx-user] Davis Data Logger - Issue

[Graham Eddy]

my vp2 (15yo) recently started throwing this error (causing weewx restart) 
every few hours. perhaps coincidence, but it started very soon after after id 
#2 (a davis temperature station - the ISS has id #1) stopped reporting after 
several days of low battery alert on and off (i was travelling), kept happening 
for a few days, then stopped almost immediately after id #2 started reporting 
again after i changed its battery (when i got back)

> On 9 May 2022, at 7:02 am, Tom Keffer  wrote:
> 
> Now that I think about it, there is an experiment I've been meaning to try. 
> Right now, the Vantage driver tries 3 times, then gives up and restarts the 
> program from the top.
> 
> The experiment would be to do something not quite so drastic. Rather than 
> restart the program, try a Vantage "wake up" sequence instead.
> 
> I've never tried this strategy because there hasn't been a logger regularly 
> showing this error that I could test. But it appears yours does. I'm tied up 
> with something else, but give me a few days to come up with a solution.
> 
> In the meantime, I've posted issue #772 
> .

-- 
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/C01F4424-57BD-4650-B92A-0C7AB70F8B0B%40geddy.au.

Re: [weewx-user] Request for assistance - GW2000/WS90

[Graham Eddy]

anyone in australia know how i can order a GW2000 from here at present?
i want the ethernet port and sane power supply

-- 
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/8AA48E8D-7863-4203-B56A-12CC43784064%40geddy.au.