[weewx-user] Re: NEW Weewx extension to add Variable txt to a JPG

[Nate Bargmann]

I don't see that you ever got a reply.

Python f-strings allow for field width specifiers.  For example:

f"{record['outTemp']:.0f}°"
f"{record['barometer']:.2f}

Hope that helps.

- Nate

On Sunday, October 15, 2023 at 12:38:06 PM UTC-5 Lorin Tremblay wrote:

> I always wanted to learn how to code but never had time or a need. 
>
> Now my first attempt to build an extension is in the works.
>
> The 1st question is acceptable to ask help or opinions in this 
> group/community? If so continue reading :)
>
>
> Now I don’t know if this extension already exists, but I know that here a 
> similar extension to do the same, but regardless I want it to be a learning 
> experience.
>
> I’m using pillow to add text to a jpg picture.
>
> So far I capable of adding the txt to the picture with the variable that I 
> want.
> My problems occurs when I want added it in the unit_system (aka US, METRIC 
> and METRICWX) and also rounding it to 2 decimal when there is more than 2.
>
> Here is where I’m at right now 
> Running on a Raspberry Pi3b with weewx 4.10.2 with all the current version 
> as of this date 10/15/2023.
>
>
> The weewx.conf is modified the following way:
>
> *[Engine]*
>
>
> # The following section specifies which services should be run and in 
> what order.
>
> [[Services]]
>
> prep_services = weewx.engine.StdTimeSynch
>
> data_services = user.airlink.AirLink, user.AddTxt2Jpg.AddTxt2Jpg
>
> process_services = weewx.engine.StdConvert, 
> weewx.engine.StdCalibrate, weewx.engine.StdQC, 
> weewx.wxservices.StdWXCalculate, user.aprx.WeewxAprx
>
> xtype_services = weewx.wxxtypes.StdWXXTypes, 
> weewx.wxxtypes.StdPressureCooker, weewx.wxxtypes.StdRainRater, 
> weewx.wxxtypes.StdDelta
>
> archive_services = weewx.engine.StdArchive
>
> restful_services = weewx.restx.StdStationRegistry, 
> weewx.restx.StdWunderground, weewx.restx.StdPWSweather, 
> weewx.restx.StdCWOP, weewx.restx.StdWOW, weewx.restx.StdAWEKAS, 
> user.mqtt.MQTT
>
> report_services = weewx.engine.StdPrint, weewx.engine.StdReport
>
> *[AddTxt2Jpg]*
>
> image_path = "/var/www/html/weewx/webcam/snap.jpg"
>
> output_path = "/var/www/html/weewx/webcam/snap_wx.jpg"
>
> font_path = "/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf"
>
> text_format = "Temperature: {outTemp}°C, Humidity: {outHumidity}%, 
> Total rain:{rain24}, AQI: {pm2_5_aqi}"
>
> text_x = 50
>
> text_y = 1450
>
> text_color = white
>
> text_font_size = 36
>
> fields = "outTemp, outHumidity, pm2_5_aqi, windSpeed, barometer, 
> rain24, windDir.ordinal_compass"
>
> Now the script itself which can be or is a complete mess looks like this:
>
> #!/usr/bin/python3
>
> import weewx
> from weewx.engine import StdService
> import weeutil.weeutil
> import syslog
> from weewx.units import convert, getStandardUnitType
>
> # Check for Pillow library installation
> try:
> from PIL import Image, ImageDraw, ImageFont
> except ImportError:
> syslog.syslog(syslog.LOG_ERR, "AddTxt2Jpg: Pillow library not found. 
> Please install with 'pip install Pillow'.")
> exit(1)
>
> class AddTxt2Jpg(StdService):
> def __init__(self, engine, config_dict):
> super(AddTxt2Jpg, self).__init__(engine, config_dict)
> 
> # Logging tag
> self.log_tag = "AddTxt2Jpg"
> 
> # Get configuration options from weewx.conf
> self.image_path = config_dict.get('AddTxt2Jpg', 
> {}).get('image_path', '')
> self.output_path = config_dict.get('AddTxt2Jpg', 
> {}).get('output_path', '')
> self.font_path = config_dict.get('AddTxt2Jpg', 
> {}).get('font_path', '')
> self.text_format = config_dict.get('AddTxt2Jpg', 
> {}).get('text_format', 'Weather Data: {outTemp}°C, Humidity: 
> {outHumidity}%')
> self.text_x = int(config_dict.get('AddTxt2Jpg', {}).get('text_x', 
> '20'))
> self.text_y = int(config_dict.get('AddTxt2Jpg', {}).get('text_y', 
> '20'))
> self.text_color = config_dict.get('AddTxt2Jpg', 
> {}).get('text_color', 'white')
> self.text_font_size = int(config_dict.get('AddTxt2Jpg', 
> {}).get('text_font_size', '20'))
> 
> # Set up the converter
> target_unit_nickname = config_dict.get("StdConvert", 
> {}).get("target_unit", "METRIC")
> target_unit = 
> weewx.units.unit_constants[target_unit_nickname.upper()]
> self.converter = weewx.units.StdUnitConverters[target_unit]
>
> # Get the list of fields to be extracted from the archive record
> fields = config_dict.get('AddTxt2Jpg', {}).get('fields', [])
> if isinstance(fields, str):
> self.fields = [x.strip() for x in fields.split(',')]
> elif isinstance(fields, list):
> self.fields = fields
> else:
> self.fields = []
>
> # Bind to the new archive record event
> self.bind(weewx.NEW_ARCHIVE_RECORD, self.new_archive_record)
> 
> 

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

[matthew wall]

ken,

what do you see when you point a web browser at the hub?  are all of your 
sensors listed?

check everything.  watch the http requests from the hub to the machine 
running weewx (use tcpdump, or wireshark, or turn up the verbosity in the 
interceptor).  see which sensors are in the requests, see which ones are 
not.  find out if the missing sensor is being reported by the hub but not 
received by weewx.  or not even being reported by the hub.

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/e3d9bc89-ea81-437c-8061-96694ff43158n%40googlegroups.com.

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

[gjr80]

Thank you, yes, self.latest_sensor_data['dateTime'] should be 
self.latest_sensor_data['datetime']. Fixed in 0.6.0b6.

Gary
On Sunday 28 January 2024 at 04:59:19 UTC+10 michael.k...@gmx.at wrote:

> Seems like, changed it to
> if self.latest_sensor_data is None or sensor_data['datetime'] > 
> self.latest_sensor_data['datetime']:
> and it didn't crash again so far.
>
> michael.k...@gmx.at schrieb am Samstag, 27. Januar 2024 um 14:31:43 UTC+1:
>
>> Case typo?
>>
>> if self.latest_sensor_data is None or sensor_data['datetime'] > 
>> self.latest_sensor_data['dateTime']:
>> michael.k...@gmx.at schrieb am Samstag, 27. Januar 2024 um 14:24:58 
>> UTC+1:
>>
>>> That part worked. You can tell by the weewx.restx: MQTT: Published 
>>> record entries in the log, there is only one Loop packet every 10s (the 
>>> poll interval).
>>> But after a few archive_intervals it crashed:
>>>
>>> 2024-01-27 14:17:25 weewxd[657388] INFO weewx.engine: Main loop exiting. 
>>> Shutting engine down.
>>> 2024-01-27 14:17:25 weewxd[657388] INFO weewx.engine: Shutting down 
>>> StdReport thread
>>> 2024-01-27 14:17:26 weewxd[657388] INFO user.gw1000: GatewayCollector 
>>> thread has been terminated
>>> 2024-01-27 14:17:27 weewxd[657388] INFO user.gw1000: GatewayCollector 
>>> thread has been terminated
>>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: Caught 
>>> unrecoverable exception:
>>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
>>>  'dateTime'
>>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
>>>  Traceback (most recent call last):
>>>
>>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
>>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py", line 166, in 
>>> main
>>>
>>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
>>>  engine.run()
>>>
>>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
>>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
>>> 206, in run
>>>
>>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
>>>  self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
>>>
>>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
>>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
>>> 241, in dispatchEvent
>>>
>>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
>>>  callback(event)
>>>
>>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
>>> "/home/pi/weewx-data/bin/user/gw1000.py", line 1504, in new_loop_packet
>>>
>>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
>>>  self.process_queued_sensor_data(queue_data, event.packet['dateTime'])
>>>
>>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
>>> "/home/pi/weewx-data/bin/user/gw1000.py", line 1611, in 
>>> process_queued_sensor_data
>>>
>>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   if 
>>> self.latest_sensor_data is None or sensor_data['datetime'] > 
>>> self.latest_sensor_data['dateTime']:
>>>
>>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
>>>  KeyError: 'dateTime'
>>>
>>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   Exiting.
>>>
>>>
>>> michael.k...@gmx.at schrieb am Donnerstag, 25. Januar 2024 um 10:48:00 
>>> UTC+1:
>>>
 OK, I need to sort this out a little. I think I messed up with 0.6.0bx 
 and 0.5.0bx. Currently I've got too many things on my plate, and wasn't as 
 focused on this topic, as I should have been, sorry for that. I'll do my 
 homework and check everything again.

 gjr80 schrieb am Mittwoch, 24. Januar 2024 um 22:24:13 UTC+1:

> On Thursday 25 January 2024 at 06:56:42 UTC+10 michael.k...@gmx.at 
> wrote:
>
> The log is from latest logs I posted are from b5. Sorry, I forgot to 
> mention that I didn't use the file in your link above, I downloaded from 
> the releases, and for b4 it says: removed, go for b5. b5 is producing two 
> independent LOOP packets after a few on my RPi4.
>
>
> Sorry, but I don't understand this. The latest log you posted 
> yesterday is very clearly from b4:
>
> 2024-01-23 19:46:51 weewxd[232660] INFO weewx.engine: Loading station 
> type GW1000 (user.gw1000) 
> 2024-01-23 19:46:51 weewxd[232660] INFO user.gw1000: GatewayDriver: 
> version is 0.6.0b4 
> 2024-01-23 19:46:51 weewxd[232660] INFO user.gw1000: device address is 
> 10.0.1.85:45000
>
> b4 and b5 have not been published to releases, they have been produced 
> to deal with this issue and I have kept them back until I know the issue 
> is 
> fixed. You need to re-download the driver from the link I provided 
> earlier 
> in order to get b5, b3 (releases) and b4 will never work. Here is the 
> link 
> again:
>
>
> 

Re: [weewx-user] Crash reading from Vantage Pro 2 since v5

[Tom Keffer]

Julian, a couple of questions:

1. These are ip-read and -write errors. What kind of logger are you using?
A WeatherLink IP?

2. The log snippet shows code from when the driver is initially loaded, so
it is unlikely to run 30 minutes in, unless this is actually a restart.
Look farther back in the log and see what triggered the restart.

Most likely this is a network connectivity issue. The only substantive
changes in the Vantage driver have been in reading and setting its
configuration, particularly retransmitters.

-tk

On Sat, Jan 27, 2024 at 3:53 PM Julian Edwards  wrote:

> v4 was flawless for me, but since upgrading to v5 (Debian package) the
> daemon runs for maybe 30 minutes before crashing with this in the log:
>
> Jan 28 09:08:18 jeeves weewxd[3350596]: INFO weewx.engine: Loading station
> type Vantage (weewx.drivers.vantage)
> Jan 28 09:08:25 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage:
> ip-read error: timed out
> Jan 28 09:08:26 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage:
> ip-write error: [Errno 32] Broken pipe
> Jan 28 09:08:29 jeeves weewxd[3350596]: message repeated 3 times: [ ERROR
> weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe]
> Jan 28 09:08:30 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage:
> Unable to wake up Vantage console
> Jan 28 09:08:30 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage:
> ip-write error: [Errno 32] Broken pipe
> Jan 28 09:08:34 jeeves weewxd[3350596]: message repeated 3 times: [ ERROR
> weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe]
> Jan 28 09:08:35 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage:
> Unable to wake up Vantage console
> Jan 28 09:08:35 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage:
> ip-write error: [Errno 32] Broken pipe
> Jan 28 09:08:39 jeeves weewxd[3350596]: message repeated 3 times: [ ERROR
> weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe]
> Jan 28 09:08:40 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage:
> Unable to wake up Vantage console
> Jan 28 09:08:40 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: While
> getting EEPROM data value at address 0x29
> Jan 28 09:08:40 jeeves weewxd[3350596]: ERROR weewx.engine: Import of
> driver failed: While getting EEPROM data value at address 0x29 ( 'weewx.RetriesExceeded'>)
> Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine: 
>  Traceback (most recent call last):
> Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine: 
>File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
> Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine: 
>  self.console = loader_function(config_dict, self)
> Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine: 
>File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader
> Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine: 
>  return VantageService(engine, config_dict)
> Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine: 
>File "/usr/share/weewx/weewx/drivers/vantage.py", line 2046, in __init__
> Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine: 
>  Vantage.__init__(self, **config_dict[DRIVER_NAME])
> Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine: 
>File "/usr/share/weewx/weewx/drivers/vantage.py", line 539, in __init__
> Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine: 
>  self._setup()
> Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine: 
>File "/usr/share/weewx/weewx/drivers/vantage.py", line 1449, in _setup
> Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine: 
>  unit_bits  = self._getEEPROM_value(0x29)[0]
> Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine: 
>File "/usr/share/weewx/weewx/drivers/vantage.py", line 1523, in
> _getEEPROM_value
> Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine: 
>  raise weewx.RetriesExceeded(msg)
> Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine: 
>  weewx.RetriesExceeded: While getting EEPROM data value at address 0x29
> Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL __main__: Unable to load
> driver: While getting EEPROM data value at address 0x29
> Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL __main__: 
>  Exiting...
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/c12c28ce-be30-4c3d-a40e-82619a94f357n%40googlegroups.com
> 
> .
>

-- 
You received this message because you 

[weewx-user] Re: HP1000 Driver Problems discovered

[Susan Mackay]

A new version of the driver is now in the GitHib repository 
(https://github.com/AussieSusan/HP1000).

Ths version has been used with V4.10 of WeeWx but is intended for use with 
V5.

As mentioned above, there was a 'bug' in the previous version that only 
came to light recently (in my case since the start of 2024) when restarting 
the driver. Normally the driver checks for historical records from the 
console but for 2024 the number of historical records was given as 0. This 
was not a situation I anticipated and therefore handled - it resulted in a 
call being made to read records from the console that never came. Hence 
WeeWx hung and appeared to be unresponsive.

This has not been fixed in that all reads now timeout if necessary and also 
if 0 historical records are reported then an estimate is made based on the 
'current' day of the year plus handing cases where an invalid historical 
record is requested.

Please let me know if you run into any issues with the new version of the 
driver.

Susan

On Monday 22 January 2024 at 1:04:05 pm UTC+11 Susan Mackay wrote:

> I'm not sure what happened but I did reply to this topic a few days ago 
> with an explanation of what was happening. So here I go again
>
> Firstly - please DON'T delete the historical records from the console. 
> While that does get WeeWx to again read the current data, it is not 
> necessary given the faults I've found. As long as the console is powered on 
> and working, it will be storing the historical records that can be 
> retrieved by the fixed driver. True, you won't get the data into WeeWx 
> right now but you will soon.
>
> The issue seems to stem from the HP1000 console firmware showing 0 
> historical records for 2024 - there are valid record counts for previous 
> years (at least on my console back to 2017). 
>
> Of course these are only used when WeeWx tries to 'catch up' any 
> historical records it has missed since the last time it was connected to 
> the console. (Normal, on-going data is not affected.)
>
> When the driver saw the '0' record count, it was not expecting this and 
> mishandled the requests for historical record. Basically it sent a request 
> that was never responded to the console but it also never timed out while 
> waiting for that response. The historical are actually there but just not 
> reported by the console when asked for the year-by-year historical record 
> count.
>
> I now detect when that situation arises and use the current date to 
> 'guess' at the number of records. I also allow for a timeout if there is 
> not response from the console. All this seems to work OK (at least for me).
>
> I'm now looking at the code changes needed to make the driver V5 
> compatible and I'm hoping the new driver will be available in the next few 
> days.
>
> Susan
>
> On Wednesday 17 January 2024 at 8:32:59 am UTC+11 Susan Mackay wrote:
>
>> A problem has recently been found with the HP1000 (WS1001, XC0422) driver.
>> While the driver will continue to work correctly, if it is restarted then 
>> it will hand trying to retrieve the 'historical' records from the console..
>> (A 'solution' has been mentioned by some that involves deleting the 
>> historical records form the console and relying on the data held in the 
>> WeeWx database. I don't recommend this approach.)
>> I am looking into the issue and I will post an updated version of the 
>> driver as soon as I can.
>> I also will bring the driver into compliance with the WeeWx V5 driver 
>> requirements. I've heard that it does work under V5 but that it is missing 
>> something for a new installation.
>> Susan
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8f91b513-27e6-48f3-9677-787ada56c37dn%40googlegroups.com.

[weewx-user] Crash reading from Vantage Pro 2 since v5

[Julian Edwards]

v4 was flawless for me, but since upgrading to v5 (Debian package) the 
daemon runs for maybe 30 minutes before crashing with this in the log:

Jan 28 09:08:18 jeeves weewxd[3350596]: INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage) 
Jan 28 09:08:25 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: 
ip-read error: timed out 
Jan 28 09:08:26 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: 
ip-write error: [Errno 32] Broken pipe 
Jan 28 09:08:29 jeeves weewxd[3350596]: message repeated 3 times: [ ERROR 
weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe] 
Jan 28 09:08:30 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: Unable 
to wake up Vantage console 
Jan 28 09:08:30 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: 
ip-write error: [Errno 32] Broken pipe 
Jan 28 09:08:34 jeeves weewxd[3350596]: message repeated 3 times: [ ERROR 
weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe] 
Jan 28 09:08:35 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: Unable 
to wake up Vantage console 
Jan 28 09:08:35 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: 
ip-write error: [Errno 32] Broken pipe 
Jan 28 09:08:39 jeeves weewxd[3350596]: message repeated 3 times: [ ERROR 
weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe] 
Jan 28 09:08:40 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: Unable 
to wake up Vantage console 
Jan 28 09:08:40 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: While 
getting EEPROM data value at address 0x29 
Jan 28 09:08:40 jeeves weewxd[3350596]: ERROR weewx.engine: Import of 
driver failed: While getting EEPROM data value at address 0x29 () 
Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine:  
 Traceback (most recent call last): 
Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine:  
   File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation 
Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine:  
 self.console = loader_function(config_dict, self) 
Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine:  
   File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader 
Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine:  
 return VantageService(engine, config_dict) 
Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine:  
   File "/usr/share/weewx/weewx/drivers/vantage.py", line 2046, in __init__ 
Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine:  
 Vantage.__init__(self, **config_dict[DRIVER_NAME]) 
Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine:  
   File "/usr/share/weewx/weewx/drivers/vantage.py", line 539, in __init__ 
Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine:  
 self._setup() 
Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine:  
   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1449, in _setup 
Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine:  
 unit_bits  = self._getEEPROM_value(0x29)[0] 
Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine:  
   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1523, in 
_getEEPROM_value 
Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine:  
 raise weewx.RetriesExceeded(msg) 
Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL weewx.engine:  
 weewx.RetriesExceeded: While getting EEPROM data value at address 0x29 
Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL __main__: Unable to load 
driver: While getting EEPROM data value at address 0x29 
Jan 28 09:08:40 jeeves weewxd[3350596]: CRITICAL __main__:  
 Exiting...

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c12c28ce-be30-4c3d-a40e-82619a94f357n%40googlegroups.com.

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

[Frank Gruhlke Gg]

This worked!   Vince and Rich, thank you so much!!

sudo weectl extension install 
https://github.com/bellrichm/WeeWX-MQTTSubscribe/archive/refs/tags/v2.3.1.tar.gz

On Saturday, January 27, 2024 at 5:20:52 PM UTC-6 Frank Gruhlke Gg wrote:

> And sorry, yes using WeeWx 5
>
> On Saturday, January 27, 2024 at 5:20:14 PM UTC-6 Frank Gruhlke Gg wrote:
>
>> That got me much closer...but (PermissionError: [Errno 13] Permission 
>> denied: '/etc/weewx/bin/user/MQTTSubscribe.py')
>>
>>
>> frank@pi4:/tmp $ weectl extension install v2.3.1.tar.gz
>> Using configuration file /etc/weewx/weewx.conf
>> Install extension 'v2.3.1.tar.gz' (y/n)? y
>> Extracting from tar archive v2.3.1.tar.gz
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/weectl.py", line 74, in 
>> main()
>>   File "/usr/share/weewx/weectl.py", line 66, in main
>> namespace.func(namespace)
>>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
>> namespace.action_func(config_dict, namespace)
>>   File "/usr/share/weewx/weectllib/extension_cmd.py", line 116, in 
>> install_extension
>> ext.install_extension(namespace.source, no_confirm=namespace.yes)
>>   File "/usr/share/weewx/weecfg/extension.py", line 138, in 
>> install_extension
>> extension_name = self._install_from_file(extension_path, filetype)
>>  ^
>>   File "/usr/share/weewx/weecfg/extension.py", line 168, in 
>> _install_from_file
>> extension_name = self.install_from_dir(extension_dir)
>>  
>>   File "/usr/share/weewx/weecfg/extension.py", line 185, in 
>> install_from_dir
>> self._install_files(installer['files'], extension_dir)
>>   File "/usr/share/weewx/weecfg/extension.py", line 269, in _install_files
>> shutil.copy(source_path, destination_path)
>>   File "/usr/lib/python3.11/shutil.py", line 419, in copy
>> copyfile(src, dst, follow_symlinks=follow_symlinks)
>>   File "/usr/lib/python3.11/shutil.py", line 258, in copyfile
>> with open(dst, 'wb') as fdst:
>>  ^^^
>> PermissionError: [Errno 13] Permission denied: 
>> '/etc/weewx/bin/user/MQTTSubscribe.py'
>>
>>
>> On Saturday, January 27, 2024 at 4:54:23 PM UTC-6 vince wrote:
>>
>>> You didn't say which version of weewx but you probably installed v5.
>>>
>>> See if 'weectl extension install' works (v5 syntax) rather than 
>>> 'wee_extension --install' (v4 syntax).
>>>
>>> On Saturday, January 27, 2024 at 2:34:15 PM UTC-8 Frank Gruhlke Gg wrote:
>>>
 Thanks for helping me out...  here is what got..

 frank@pi4:/tmp $ wee_extension --install=v2.3.1.tar.gz
 bash: wee_extension: command not found

 On Saturday, January 27, 2024 at 4:20:12 PM UTC-6 Rich Bell wrote:

> Drop the BIN_DIR
> wee_extension --install=v2.3.1.tar.gz
> Assuming you are /tmp
>
> On Sat, Jan 27, 2024 at 4:56 PM bell...@gmail.com  
> wrote:
>
>> You caught me in the middle of a major documentation update.
>>
>> For weewx v5 use, 
>> http://www.weewx.com/docs/5.0/utilities/weectl-extension/ and 
>> http://www.weewx.com/docs/5.0/utilities/weectl-station/
>> And v4, 
>> http://www.weewx.com/docs/4.10/utilities.htm#wee_extension_utility 
>> and http://www.weewx.com/docs/4.10/utilities.htm#Action_--reconfigure
>>
>> Then manually update weewx.conf using 
>> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Common-Options 
>> as a reference
>>
>> rich
>>
>> On Saturday 27 January 2024 at 16:38:36 UTC-5 Frank Gruhlke Gg wrote:
>>
>>> Hello all..   hopefully someone can help me!
>>> I have a fresh raspbean install on a pi-4 and want to install the 
>>> MQTT driver found here:
>>> https://github.com/bellrichm/WeeWX-MQTTSubscribe
>>>
>>> So far managed to install the Paho MQTT Python Client but then 
>>> started to run into issues.
>>>
>>> First,  DOWNLOAD_DIR = /tmp   gave me a "bad command error so I 
>>> adjusted and ran:
>>>
>>> /tmp $ wget https://github.com/bellrichm/WeeWX- 
>>> MQTTSubscribe/archive/refs/tags/v2.3.1.tar.gz
>>>
>>> and managed to get "v2.3.1.tar.gz into the /tmp directory
>>>
>>> now it seems no matter what I try I cant install from here..
>>>
>>> frank@pi4:/tmp $ BIN_DIR/wee_extension --install=v2.3.1.tar.gz
>>> bash: BIN_DIR/wee_extension: No such file or directory
>>> also tried 
>>> frank@pi4:/tmp $ BIN_DIR/wee_extension --install v2.3.1.tar.gz
>>> bash: BIN_DIR/wee_extension: No such file or directory
>>>
>>> I am sure its something minor but I have no hair left to pull! 
>>>
>>>
>>>
>>> -- 
>> You received this message because you are subscribed to the Google 
>> Groups "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, 
>> send an email to 

Re: [weewx-user] Integrate rain24 with Packetsloop

[Tom Keffer]

My apologies. I forgot one important detail. The "[Delta]" section tells
WeeWX how to calculate rain, but you also have to include "rain" under
[StdWXCalculations] / [[Calculations]] in order to get it to do the actual
calculation. It looks like

[StdWXCalculate]
[[Calculations]]
...
rain = prefer_hardware
...
[[Delta]]
[[[rain]]]
input = dayRain



On Sat, Jan 27, 2024 at 9:17 AM Remy Lavabre  wrote:

> Hello Tom,
>
> I followed your instructions:
>
> 1/“rain” field present in the database
> 2/ “dayRain” field not present in the database
> 3/ My driver returns “dayRain” values and not “rain” values in the
> packetsloop
> 4/ [[Delta]] [[ [rain]]] input = dayRain added in weewx.conf (under
> [StdWXCalculate]).
>
> I did some tests : my driver returns 0.0 for dayRain but unfortunately the
> "rain" field in my database always remains NULL, even after several
> recordings in weewx.conf.
> Shouldn't "rain" field go to 0.0?
>
> THANKS
>
> Le vendredi 26 janvier 2024 à 22:48:03 UTC+1, Tom Keffer a écrit :
>
>> If an observation type never gets reset to zero, you have two choices.
>> 1. Save the value. If you want to know daily use, take the difference of
>> the value.
>> 2. Save the difference. That is, the change in the value over an archive
>> period. If you want to know daily use, you would sum all the small deltas.
>> This is like rain
>>
>> See the discussion *Accumulated vs delta energy
>> *
>>  in
>> the README of the Brultech driver for the pros and cons of the two
>> approaches.
>>
>> It is not necessary to save "dayRain". WeeWX mostly uses "rain". Besides,
>> as you note, it can always be calculated.
>>
>>
>>
>> On Fri, Jan 26, 2024 at 7:06 AM Remy Lavabre  wrote:
>>
>>> And one more question
>>> Is it absolutely necessary to create a "dayRain" field in addition to
>>> the "rain" field in the weewx.sdb database?
>>> If the database only contains the [rain] field but the Weewx driver
>>> returns a "dayRain" field (cumulative rain over 24 hours since midnight)
>>> with a real value in each packetloop, the class [[Delta]] [[ [rain]]] input
>>> = dayRain will it work??
>>> (the accumulation of rain since midnight is useless to me in a database
>>> field since it is easily calculated)
>>> Sorry for all the questions...and thanks again! ;-)
>>>
>>> Le vendredi 26 janvier 2024 à 15:46:04 UTC+1, Remy Lavabre a écrit :
>>>
 Hello Tom and thank you for your response.

  [StdWXCalculate]
  [[Calculations]]
  ...
  [[Delta]]
  [[[rain]]]
  input = dayRain

 This will calculate the rain difference between two records in weewx
 sql based on the principle that the counter is reset to zero at midnight ->
 PERFECT FOR THE RAIN 24H !

 Small additional question: if we wish to constantly calculate the
 difference between two records values of a meter which *never* resets
 to zero (such as an electricity or water meter), how should we proceed?

 THANKS

 Le jeudi 18 janvier 2024 à 14:05:10 UTC+1, Tom Keffer a écrit :

> Unfortunately (for you), WeeWX mostly uses observation type "rain",
> the amount of rain that fell since the last loop packet (what you are
> calling "instantaneous rain").
>
> You should assign the rain since midnight to type "dayRain".
>
> Then calculate "rain" as the difference between successive
> "dayRain" values. While this is a pretty simple calculation, there is an
> xtype that can do it for you.  See class Delta in weewx.wxxtypes
> .
> To use it, add this to weewx.conf:
>
> [StdWXCalculate]
> [[Calculations]]
> ...
> [[Delta]]
> [[[rain]]]
> input = dayRain
>
>
>
>
> On Wed, Jan 17, 2024 at 11:47 PM Remy Lavabre 
> wrote:
>
>> Good morning,
>>
>> I created a [driver] for weewx to retrieve data from the Awekas API
>> (my Bresser weather station does not have a USB port).
>>
>> This works but regarding the rain, it is not the instantaneous rain
>> (from a packetloop) that we recover but the rain over 24 hours since
>> midnight.
>> Is there a "simple" way to tell WeeWX that the packetsloop rain data
>> corresponds to the cumulative rain since midnight and not the rain that
>> fell during the data retrieval interval (the time gap between two
>> packetsloops) ?
>>
>> Thank you so much...
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to 

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

[Frank Gruhlke Gg]

And sorry, yes using WeeWx 5

On Saturday, January 27, 2024 at 5:20:14 PM UTC-6 Frank Gruhlke Gg wrote:

> That got me much closer...but (PermissionError: [Errno 13] Permission 
> denied: '/etc/weewx/bin/user/MQTTSubscribe.py')
>
>
> frank@pi4:/tmp $ weectl extension install v2.3.1.tar.gz
> Using configuration file /etc/weewx/weewx.conf
> Install extension 'v2.3.1.tar.gz' (y/n)? y
> Extracting from tar archive v2.3.1.tar.gz
> Traceback (most recent call last):
>   File "/usr/share/weewx/weectl.py", line 74, in 
> main()
>   File "/usr/share/weewx/weectl.py", line 66, in main
> namespace.func(namespace)
>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
> namespace.action_func(config_dict, namespace)
>   File "/usr/share/weewx/weectllib/extension_cmd.py", line 116, in 
> install_extension
> ext.install_extension(namespace.source, no_confirm=namespace.yes)
>   File "/usr/share/weewx/weecfg/extension.py", line 138, in 
> install_extension
> extension_name = self._install_from_file(extension_path, filetype)
>  ^
>   File "/usr/share/weewx/weecfg/extension.py", line 168, in 
> _install_from_file
> extension_name = self.install_from_dir(extension_dir)
>  
>   File "/usr/share/weewx/weecfg/extension.py", line 185, in 
> install_from_dir
> self._install_files(installer['files'], extension_dir)
>   File "/usr/share/weewx/weecfg/extension.py", line 269, in _install_files
> shutil.copy(source_path, destination_path)
>   File "/usr/lib/python3.11/shutil.py", line 419, in copy
> copyfile(src, dst, follow_symlinks=follow_symlinks)
>   File "/usr/lib/python3.11/shutil.py", line 258, in copyfile
> with open(dst, 'wb') as fdst:
>  ^^^
> PermissionError: [Errno 13] Permission denied: 
> '/etc/weewx/bin/user/MQTTSubscribe.py'
>
>
> On Saturday, January 27, 2024 at 4:54:23 PM UTC-6 vince wrote:
>
>> You didn't say which version of weewx but you probably installed v5.
>>
>> See if 'weectl extension install' works (v5 syntax) rather than 
>> 'wee_extension --install' (v4 syntax).
>>
>> On Saturday, January 27, 2024 at 2:34:15 PM UTC-8 Frank Gruhlke Gg wrote:
>>
>>> Thanks for helping me out...  here is what got..
>>>
>>> frank@pi4:/tmp $ wee_extension --install=v2.3.1.tar.gz
>>> bash: wee_extension: command not found
>>>
>>> On Saturday, January 27, 2024 at 4:20:12 PM UTC-6 Rich Bell wrote:
>>>
 Drop the BIN_DIR
 wee_extension --install=v2.3.1.tar.gz
 Assuming you are /tmp

 On Sat, Jan 27, 2024 at 4:56 PM bell...@gmail.com  
 wrote:

> You caught me in the middle of a major documentation update.
>
> For weewx v5 use, 
> http://www.weewx.com/docs/5.0/utilities/weectl-extension/ and 
> http://www.weewx.com/docs/5.0/utilities/weectl-station/
> And v4, 
> http://www.weewx.com/docs/4.10/utilities.htm#wee_extension_utility 
> and http://www.weewx.com/docs/4.10/utilities.htm#Action_--reconfigure
>
> Then manually update weewx.conf using 
> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Common-Options 
> as a reference
>
> rich
>
> On Saturday 27 January 2024 at 16:38:36 UTC-5 Frank Gruhlke Gg wrote:
>
>> Hello all..   hopefully someone can help me!
>> I have a fresh raspbean install on a pi-4 and want to install the 
>> MQTT driver found here:
>> https://github.com/bellrichm/WeeWX-MQTTSubscribe
>>
>> So far managed to install the Paho MQTT Python Client but then 
>> started to run into issues.
>>
>> First,  DOWNLOAD_DIR = /tmp   gave me a "bad command error so I 
>> adjusted and ran:
>>
>> /tmp $ wget https://github.com/bellrichm/WeeWX- 
>> MQTTSubscribe/archive/refs/tags/v2.3.1.tar.gz
>>
>> and managed to get "v2.3.1.tar.gz into the /tmp directory
>>
>> now it seems no matter what I try I cant install from here..
>>
>> frank@pi4:/tmp $ BIN_DIR/wee_extension --install=v2.3.1.tar.gz
>> bash: BIN_DIR/wee_extension: No such file or directory
>> also tried 
>> frank@pi4:/tmp $ BIN_DIR/wee_extension --install v2.3.1.tar.gz
>> bash: BIN_DIR/wee_extension: No such file or directory
>>
>> I am sure its something minor but I have no hair left to pull! 
>>
>>
>>
>> -- 
> You received this message because you are subscribed 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/d3d4555a-b6b7-4594-a022-128c6739442cn%40googlegroups.com
>  
> 
> .
>


-- 

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

[Frank Gruhlke Gg]

That got me much closer...but (PermissionError: [Errno 13] Permission 
denied: '/etc/weewx/bin/user/MQTTSubscribe.py')


frank@pi4:/tmp $ weectl extension install v2.3.1.tar.gz
Using configuration file /etc/weewx/weewx.conf
Install extension 'v2.3.1.tar.gz' (y/n)? y
Extracting from tar archive v2.3.1.tar.gz
Traceback (most recent call last):
  File "/usr/share/weewx/weectl.py", line 74, in 
main()
  File "/usr/share/weewx/weectl.py", line 66, in main
namespace.func(namespace)
  File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
namespace.action_func(config_dict, namespace)
  File "/usr/share/weewx/weectllib/extension_cmd.py", line 116, in 
install_extension
ext.install_extension(namespace.source, no_confirm=namespace.yes)
  File "/usr/share/weewx/weecfg/extension.py", line 138, in 
install_extension
extension_name = self._install_from_file(extension_path, filetype)
 ^
  File "/usr/share/weewx/weecfg/extension.py", line 168, in 
_install_from_file
extension_name = self.install_from_dir(extension_dir)
 
  File "/usr/share/weewx/weecfg/extension.py", line 185, in install_from_dir
self._install_files(installer['files'], extension_dir)
  File "/usr/share/weewx/weecfg/extension.py", line 269, in _install_files
shutil.copy(source_path, destination_path)
  File "/usr/lib/python3.11/shutil.py", line 419, in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.11/shutil.py", line 258, in copyfile
with open(dst, 'wb') as fdst:
 ^^^
PermissionError: [Errno 13] Permission denied: 
'/etc/weewx/bin/user/MQTTSubscribe.py'


On Saturday, January 27, 2024 at 4:54:23 PM UTC-6 vince wrote:

> You didn't say which version of weewx but you probably installed v5.
>
> See if 'weectl extension install' works (v5 syntax) rather than 
> 'wee_extension --install' (v4 syntax).
>
> On Saturday, January 27, 2024 at 2:34:15 PM UTC-8 Frank Gruhlke Gg wrote:
>
>> Thanks for helping me out...  here is what got..
>>
>> frank@pi4:/tmp $ wee_extension --install=v2.3.1.tar.gz
>> bash: wee_extension: command not found
>>
>> On Saturday, January 27, 2024 at 4:20:12 PM UTC-6 Rich Bell wrote:
>>
>>> Drop the BIN_DIR
>>> wee_extension --install=v2.3.1.tar.gz
>>> Assuming you are /tmp
>>>
>>> On Sat, Jan 27, 2024 at 4:56 PM bell...@gmail.com  
>>> wrote:
>>>
 You caught me in the middle of a major documentation update.

 For weewx v5 use, 
 http://www.weewx.com/docs/5.0/utilities/weectl-extension/ and 
 http://www.weewx.com/docs/5.0/utilities/weectl-station/
 And v4, 
 http://www.weewx.com/docs/4.10/utilities.htm#wee_extension_utility and 
 http://www.weewx.com/docs/4.10/utilities.htm#Action_--reconfigure

 Then manually update weewx.conf using 
 https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Common-Options 
 as a reference

 rich

 On Saturday 27 January 2024 at 16:38:36 UTC-5 Frank Gruhlke Gg wrote:

> Hello all..   hopefully someone can help me!
> I have a fresh raspbean install on a pi-4 and want to install the MQTT 
> driver found here:
> https://github.com/bellrichm/WeeWX-MQTTSubscribe
>
> So far managed to install the Paho MQTT Python Client but then started 
> to run into issues.
>
> First,  DOWNLOAD_DIR = /tmp   gave me a "bad command error so I 
> adjusted and ran:
>
> /tmp $ wget https://github.com/bellrichm/WeeWX- 
> MQTTSubscribe/archive/refs/tags/v2.3.1.tar.gz
>
> and managed to get "v2.3.1.tar.gz into the /tmp directory
>
> now it seems no matter what I try I cant install from here..
>
> frank@pi4:/tmp $ BIN_DIR/wee_extension --install=v2.3.1.tar.gz
> bash: BIN_DIR/wee_extension: No such file or directory
> also tried 
> frank@pi4:/tmp $ BIN_DIR/wee_extension --install v2.3.1.tar.gz
> bash: BIN_DIR/wee_extension: No such file or directory
>
> I am sure its something minor but I have no hair left to pull! 
>
>
>
> -- 
 You received this message because you are subscribed 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/d3d4555a-b6b7-4594-a022-128c6739442cn%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 

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

[vince]

You didn't say which version of weewx but you probably installed v5.

See if 'weectl extension install' works (v5 syntax) rather than 
'wee_extension --install' (v4 syntax).

On Saturday, January 27, 2024 at 2:34:15 PM UTC-8 Frank Gruhlke Gg wrote:

> Thanks for helping me out...  here is what got..
>
> frank@pi4:/tmp $ wee_extension --install=v2.3.1.tar.gz
> bash: wee_extension: command not found
>
> On Saturday, January 27, 2024 at 4:20:12 PM UTC-6 Rich Bell wrote:
>
>> Drop the BIN_DIR
>> wee_extension --install=v2.3.1.tar.gz
>> Assuming you are /tmp
>>
>> On Sat, Jan 27, 2024 at 4:56 PM bell...@gmail.com  
>> wrote:
>>
>>> You caught me in the middle of a major documentation update.
>>>
>>> For weewx v5 use, 
>>> http://www.weewx.com/docs/5.0/utilities/weectl-extension/ and 
>>> http://www.weewx.com/docs/5.0/utilities/weectl-station/
>>> And v4, 
>>> http://www.weewx.com/docs/4.10/utilities.htm#wee_extension_utility and 
>>> http://www.weewx.com/docs/4.10/utilities.htm#Action_--reconfigure
>>>
>>> Then manually update weewx.conf using 
>>> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Common-Options as 
>>> a reference
>>>
>>> rich
>>>
>>> On Saturday 27 January 2024 at 16:38:36 UTC-5 Frank Gruhlke Gg wrote:
>>>
 Hello all..   hopefully someone can help me!
 I have a fresh raspbean install on a pi-4 and want to install the MQTT 
 driver found here:
 https://github.com/bellrichm/WeeWX-MQTTSubscribe

 So far managed to install the Paho MQTT Python Client but then started 
 to run into issues.

 First,  DOWNLOAD_DIR = /tmp   gave me a "bad command error so I 
 adjusted and ran:

 /tmp $ wget https://github.com/bellrichm/WeeWX- 
 MQTTSubscribe/archive/refs/tags/v2.3.1.tar.gz

 and managed to get "v2.3.1.tar.gz into the /tmp directory

 now it seems no matter what I try I cant install from here..

 frank@pi4:/tmp $ BIN_DIR/wee_extension --install=v2.3.1.tar.gz
 bash: BIN_DIR/wee_extension: No such file or directory
 also tried 
 frank@pi4:/tmp $ BIN_DIR/wee_extension --install v2.3.1.tar.gz
 bash: BIN_DIR/wee_extension: No such file or directory

 I am sure its something minor but I have no hair left to pull! 



 -- 
>>> You received this message because you are subscribed 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/d3d4555a-b6b7-4594-a022-128c6739442cn%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/9263187f-16d8-490d-8dc0-3ffda43688dcn%40googlegroups.com.

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

[Rich Bell]

Just double checking, you installed WeeWX 4.x?
What method, package or setup?
It’s a bit of a matrix of what to do depending on WeeWX version and install
method. I am hoping to simplify my instructions, but the docs are partially
done. Sorry about that. We’ll get you up and running.


On Sat, Jan 27, 2024 at 5:34 PM Frank Gruhlke Gg 
wrote:

> Thanks for helping me out...  here is what got..
>
> frank@pi4:/tmp $ wee_extension --install=v2.3.1.tar.gz
> bash: wee_extension: command not found
>
> On Saturday, January 27, 2024 at 4:20:12 PM UTC-6 Rich Bell wrote:
>
>> Drop the BIN_DIR
>> wee_extension --install=v2.3.1.tar.gz
>> Assuming you are /tmp
>>
>> On Sat, Jan 27, 2024 at 4:56 PM bell...@gmail.com 
>> wrote:
>>
>>> You caught me in the middle of a major documentation update.
>>>
>>> For weewx v5 use,
>>> http://www.weewx.com/docs/5.0/utilities/weectl-extension/ and
>>> http://www.weewx.com/docs/5.0/utilities/weectl-station/
>>> And v4,
>>> http://www.weewx.com/docs/4.10/utilities.htm#wee_extension_utility and
>>> http://www.weewx.com/docs/4.10/utilities.htm#Action_--reconfigure
>>>
>>> Then manually update weewx.conf using
>>> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Common-Options as
>>> a reference
>>>
>>> rich
>>>
>>> On Saturday 27 January 2024 at 16:38:36 UTC-5 Frank Gruhlke Gg wrote:
>>>
 Hello all..   hopefully someone can help me!
 I have a fresh raspbean install on a pi-4 and want to install the MQTT
 driver found here:
 https://github.com/bellrichm/WeeWX-MQTTSubscribe

 So far managed to install the Paho MQTT Python Client but then started
 to run into issues.

 First,  DOWNLOAD_DIR = /tmp   gave me a "bad command error so I
 adjusted and ran:

 /tmp $ wget https://github.com/bellrichm/WeeWX-
 MQTTSubscribe/archive/refs/tags/v2.3.1.tar.gz

 and managed to get "v2.3.1.tar.gz into the /tmp directory

 now it seems no matter what I try I cant install from here..

 frank@pi4:/tmp $ BIN_DIR/wee_extension --install=v2.3.1.tar.gz
 bash: BIN_DIR/wee_extension: No such file or directory
 also tried
 frank@pi4:/tmp $ BIN_DIR/wee_extension --install v2.3.1.tar.gz
 bash: BIN_DIR/wee_extension: No such file or directory

 I am sure its something minor but I have no hair left to pull!



 --
>>> You received this message because you are subscribed 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/d3d4555a-b6b7-4594-a022-128c6739442cn%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/e02afe5c-dad3-4801-a3b1-37d355ba4e96n%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/CAG4CQqwu5QiLgi96Od5UU38v2PGK__eJwe0HX9c61s8jdbCsHw%40mail.gmail.com.

[weewx-user] Re: Needed software for APRS

[Devonian]

Direwolf ?

Nigel
G4ZAL

On Saturday 27 January 2024 at 15:19:46 UTC Massimiliano Buldrini wrote:

> I have a Davis Vantage Pro 2 with Serial".
>
> I have a Raspberry P4, a serial card to connect directly to the GPIO, a 
> CM108 with audio and PTT that I want to connect to a portable radio that 
> acts as a DIGIPEATER
>
> What software are needed besides weewx to transmit data via radio and via 
> igate?
>
> Can someone give me some advice?
>
> Regards
> Massimiliano
> IZ4SJB[image: hardware.jpg]
>

-- 
You received this message because you are subscribed 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/24149b48-8528-457e-af86-d01fba045f2en%40googlegroups.com.

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

[Frank Gruhlke Gg]

Thanks for helping me out...  here is what got..

frank@pi4:/tmp $ wee_extension --install=v2.3.1.tar.gz
bash: wee_extension: command not found

On Saturday, January 27, 2024 at 4:20:12 PM UTC-6 Rich Bell wrote:

> Drop the BIN_DIR
> wee_extension --install=v2.3.1.tar.gz
> Assuming you are /tmp
>
> On Sat, Jan 27, 2024 at 4:56 PM bell...@gmail.com  
> wrote:
>
>> You caught me in the middle of a major documentation update.
>>
>> For weewx v5 use, 
>> http://www.weewx.com/docs/5.0/utilities/weectl-extension/ and 
>> http://www.weewx.com/docs/5.0/utilities/weectl-station/
>> And v4, 
>> http://www.weewx.com/docs/4.10/utilities.htm#wee_extension_utility and 
>> http://www.weewx.com/docs/4.10/utilities.htm#Action_--reconfigure
>>
>> Then manually update weewx.conf using 
>> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Common-Options as 
>> a reference
>>
>> rich
>>
>> On Saturday 27 January 2024 at 16:38:36 UTC-5 Frank Gruhlke Gg wrote:
>>
>>> Hello all..   hopefully someone can help me!
>>> I have a fresh raspbean install on a pi-4 and want to install the MQTT 
>>> driver found here:
>>> https://github.com/bellrichm/WeeWX-MQTTSubscribe
>>>
>>> So far managed to install the Paho MQTT Python Client but then started 
>>> to run into issues.
>>>
>>> First,  DOWNLOAD_DIR = /tmp   gave me a "bad command error so I adjusted 
>>> and ran:
>>>
>>> /tmp $ wget https://github.com/bellrichm/WeeWX- 
>>> MQTTSubscribe/archive/refs/tags/v2.3.1.tar.gz
>>>
>>> and managed to get "v2.3.1.tar.gz into the /tmp directory
>>>
>>> now it seems no matter what I try I cant install from here..
>>>
>>> frank@pi4:/tmp $ BIN_DIR/wee_extension --install=v2.3.1.tar.gz
>>> bash: BIN_DIR/wee_extension: No such file or directory
>>> also tried 
>>> frank@pi4:/tmp $ BIN_DIR/wee_extension --install v2.3.1.tar.gz
>>> bash: BIN_DIR/wee_extension: No such file or directory
>>>
>>> I am sure its something minor but I have no hair left to pull! 
>>>
>>>
>>>
>>> -- 
>> You received this message because you are subscribed 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/d3d4555a-b6b7-4594-a022-128c6739442cn%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/e02afe5c-dad3-4801-a3b1-37d355ba4e96n%40googlegroups.com.

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

[Rich Bell]

Drop the BIN_DIR
wee_extension --install=v2.3.1.tar.gz
Assuming you are /tmp

On Sat, Jan 27, 2024 at 4:56 PM bell...@gmail.com 
wrote:

> You caught me in the middle of a major documentation update.
>
> For weewx v5 use,
> http://www.weewx.com/docs/5.0/utilities/weectl-extension/ and
> http://www.weewx.com/docs/5.0/utilities/weectl-station/
> And v4, http://www.weewx.com/docs/4.10/utilities.htm#wee_extension_utility
> and http://www.weewx.com/docs/4.10/utilities.htm#Action_--reconfigure
>
> Then manually update weewx.conf using
> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Common-Options as a
> reference
>
> rich
>
> On Saturday 27 January 2024 at 16:38:36 UTC-5 Frank Gruhlke Gg wrote:
>
>> Hello all..   hopefully someone can help me!
>> I have a fresh raspbean install on a pi-4 and want to install the MQTT
>> driver found here:
>> https://github.com/bellrichm/WeeWX-MQTTSubscribe
>>
>> So far managed to install the Paho MQTT Python Client but then started to
>> run into issues.
>>
>> First,  DOWNLOAD_DIR = /tmp   gave me a "bad command error so I adjusted
>> and ran:
>>
>> /tmp $ wget https://github.com/bellrichm/WeeWX-
>> MQTTSubscribe/archive/refs/tags/v2.3.1.tar.gz
>>
>> and managed to get "v2.3.1.tar.gz into the /tmp directory
>>
>> now it seems no matter what I try I cant install from here..
>>
>> frank@pi4:/tmp $ BIN_DIR/wee_extension --install=v2.3.1.tar.gz
>> bash: BIN_DIR/wee_extension: No such file or directory
>> also tried
>> frank@pi4:/tmp $ BIN_DIR/wee_extension --install v2.3.1.tar.gz
>> bash: BIN_DIR/wee_extension: No such file or directory
>>
>> I am sure its something minor but I have no hair left to pull!
>>
>>
>>
>> --
> You received this message because you are subscribed 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/d3d4555a-b6b7-4594-a022-128c6739442cn%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/CAG4CQqzg1Ey-wFgYy%3DW3ueY%3DAL%2B%3DKb5iSjNzKo7qknqQXyao%3Dg%40mail.gmail.com.

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

[bell...@gmail.com]

You caught me in the middle of a major documentation update.

For weewx v5 use, http://www.weewx.com/docs/5.0/utilities/weectl-extension/ 
and http://www.weewx.com/docs/5.0/utilities/weectl-station/
And v4, http://www.weewx.com/docs/4.10/utilities.htm#wee_extension_utility 
and http://www.weewx.com/docs/4.10/utilities.htm#Action_--reconfigure

Then manually update weewx.conf 
using https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Common-Options 
as a reference

rich

On Saturday 27 January 2024 at 16:38:36 UTC-5 Frank Gruhlke Gg wrote:

> Hello all..   hopefully someone can help me!
> I have a fresh raspbean install on a pi-4 and want to install the MQTT 
> driver found here:
> https://github.com/bellrichm/WeeWX-MQTTSubscribe
>
> So far managed to install the Paho MQTT Python Client but then started to 
> run into issues.
>
> First,  DOWNLOAD_DIR = /tmp   gave me a "bad command error so I adjusted 
> and ran:
>
> /tmp $ wget https://github.com/bellrichm/WeeWX- 
> MQTTSubscribe/archive/refs/tags/v2.3.1.tar.gz
>
> and managed to get "v2.3.1.tar.gz into the /tmp directory
>
> now it seems no matter what I try I cant install from here..
>
> frank@pi4:/tmp $ BIN_DIR/wee_extension --install=v2.3.1.tar.gz
> bash: BIN_DIR/wee_extension: No such file or directory
> also tried 
> frank@pi4:/tmp $ BIN_DIR/wee_extension --install v2.3.1.tar.gz
> bash: BIN_DIR/wee_extension: No such file or directory
>
> I am sure its something minor but I have no hair left to pull! 
>
>
>
>

-- 
You received this message because you are subscribed 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/d3d4555a-b6b7-4594-a022-128c6739442cn%40googlegroups.com.

[weewx-user] Trouble installing WeeWX-MQTTSubscribe

[Frank Gruhlke Gg]

Hello all..   hopefully someone can help me!
I have a fresh raspbean install on a pi-4 and want to install the MQTT 
driver found here:
https://github.com/bellrichm/WeeWX-MQTTSubscribe

So far managed to install the Paho MQTT Python Client but then started to 
run into issues.

First,  DOWNLOAD_DIR = /tmp   gave me a "bad command error so I adjusted 
and ran:

/tmp $ wget https://github.com/bellrichm/WeeWX- 
MQTTSubscribe/archive/refs/tags/v2.3.1.tar.gz

and managed to get "v2.3.1.tar.gz into the /tmp directory

now it seems no matter what I try I cant install from here..

frank@pi4:/tmp $ BIN_DIR/wee_extension --install=v2.3.1.tar.gz
bash: BIN_DIR/wee_extension: No such file or directory
also tried 
frank@pi4:/tmp $ BIN_DIR/wee_extension --install v2.3.1.tar.gz
bash: BIN_DIR/wee_extension: No such file or directory

I am sure its something minor but I have no hair left to pull! 



-- 
You received this message because you are subscribed 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/2a997691-e207-4bb2-abef-15ae2707cb7an%40googlegroups.com.

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

[Bill Hattel]

Hi Vince,
Not quite solved. It still fails to start after reboot. I think I solved it 
before by adding a line somewhere.

I have this in my notes:

Wait for network before startup:
Add $network to # Required-Start

I can't remember where I placed this before or if there's a better way to 
delay weewx start until the network is ready.

Any suggestions?

Thanks,
Bill

On Saturday, January 27, 2024 at 10:27:52 AM UTC-7 vince wrote:

> Cool you solved it.  Wouldn't have thought that a baud rate thing would 
> get you network unreachable. 
>
> On Saturday, January 27, 2024 at 8:59:15 AM UTC-8 Bill Hattel wrote:
>
>> Hi Vince,
>> Thank you for replying. It turns out, it was something simple as usual. 
>> It's not starting at power-up and in my haste to recognize that, I reset 
>> the Ethernet to serial adapter to factory defaults which set the baud rate 
>> to 115200. Once I set it back to 19200 and started weewx, it began 
>> reporting. I'm still having an issue with it starting after reboot, but I 
>> think I can resolve it without too much trouble. I'd like to hear any 
>> suggestions you have for that issue though.
>>
>> As far as the complexity of my setup, I originally started out with the 
>> Davis Instruments serial module on a PC which was kind of pricey back in 
>> the early 2000s. The NetBurner approach let me keep my existing hardware 
>> and add it to my home network for a reasonable cost.
>>
>> Thanks again!
>> Bill
>>
>> On Friday, January 26, 2024 at 11:11:19 AM UTC-7 vince wrote:
>>
>>> On Friday, January 26, 2024 at 9:33:35 AM UTC-8 Bill Hattel wrote:
>>>
>>> I'm having the same issue after an upgrade to 5.0.0-1. I inspected the 
>>> configuration file even though I selected no changes and found everything 
>>> was correct. I also completely removed weewx and reinstalled it with a new 
>>> configuration file. I can communicate with the Davis console through 
>>> WeatherLink with the same settings and interface with no issue. The port is 
>>> closed when WeatherLink exits.
>>>
>>> Davis Vantage Vue
>>> Raspberry PI
>>> NetBurner SBL2E Dual Serial to Ethernet converter
>>> Homemade RS-232 level shifter.
>>>
>>>
>>> Hmmmthat's pretty unusual/exotic hardware connecting the Vue to the 
>>> pi
>>>  
>>>
>>> Jan 25 19:44:10 raspberrypi weewxd[298]: ERROR weewx.drivers.vantage: 
>>> Socket error while opening port 23 to ethernet host 192.168.50.39.
>>>     this line 
>>> Jan 25 19:44:10 raspberrypi weewxd[298]: ERROR weewx.engine: Import of 
>>> driver failed: [Errno 101] Network is unreachable (>> 'weewx.WeeWxIOError'>)
>>> ]
>>>
>>> Jan 25 19:44:10 raspberrypi weewxd[298]: CRITICAL __main__: Unable to 
>>> load driver: [Errno 101] Network is unreachable
>>> Jan 25 19:44:10 raspberrypi weewxd[298]: CRITICAL __main__:  
>>>  Exiting...
>>> Jan 25 19:44:10 raspberrypi systemd[1]: weewx.service: Main process 
>>> exited, code=exited, status=4/NOPERMISSION
>>>
>>>
>>> Network unreachable is a different issue than others are having. 
>>>
>>> What's your weewx system ip ?  What is the ip you are trying to talk to 
>>> ?   If they're on different networks you are possibly missing a route on 
>>> your weewx system.   From the weewx system you might try "traceroute -n 
>>> 192.168.50.39" if the destination address in your logs is correct.
>>>
>>> This one looks like a routing or packet filter issue on a router in 
>>> between the weewx box and the serial-to-ethernet converter 'if' they are on 
>>> different subnets
>>>
>>>

-- 
You received this message because you are subscribed 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/9db00ef6-f5cf-43f0-a78b-a5bd435944fen%40googlegroups.com.

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

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

Seems like, changed it to
if self.latest_sensor_data is None or sensor_data['datetime'] > 
self.latest_sensor_data['datetime']:
and it didn't crash again so far.

michael.k...@gmx.at schrieb am Samstag, 27. Januar 2024 um 14:31:43 UTC+1:

> Case typo?
>
> if self.latest_sensor_data is None or sensor_data['datetime'] > 
> self.latest_sensor_data['dateTime']:
> michael.k...@gmx.at schrieb am Samstag, 27. Januar 2024 um 14:24:58 UTC+1:
>
>> That part worked. You can tell by the weewx.restx: MQTT: Published record 
>> entries in the log, there is only one Loop packet every 10s (the poll 
>> interval).
>> But after a few archive_intervals it crashed:
>>
>> 2024-01-27 14:17:25 weewxd[657388] INFO weewx.engine: Main loop exiting. 
>> Shutting engine down.
>> 2024-01-27 14:17:25 weewxd[657388] INFO weewx.engine: Shutting down 
>> StdReport thread
>> 2024-01-27 14:17:26 weewxd[657388] INFO user.gw1000: GatewayCollector 
>> thread has been terminated
>> 2024-01-27 14:17:27 weewxd[657388] INFO user.gw1000: GatewayCollector 
>> thread has been terminated
>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: Caught 
>> unrecoverable exception:
>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   'dateTime'
>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   Traceback 
>> (most recent call last):
>>
>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py", line 166, in 
>> main
>>
>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
>>  engine.run()
>>
>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
>> 206, in run
>>
>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
>>  self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
>>
>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
>> 241, in dispatchEvent
>>
>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
>>  callback(event)
>>
>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
>> "/home/pi/weewx-data/bin/user/gw1000.py", line 1504, in new_loop_packet
>>
>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
>>  self.process_queued_sensor_data(queue_data, event.packet['dateTime'])
>>
>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
>> "/home/pi/weewx-data/bin/user/gw1000.py", line 1611, in 
>> process_queued_sensor_data
>>
>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   if 
>> self.latest_sensor_data is None or sensor_data['datetime'] > 
>> self.latest_sensor_data['dateTime']:
>>
>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   KeyError: 
>> 'dateTime'
>>
>> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   Exiting.
>>
>>
>> michael.k...@gmx.at schrieb am Donnerstag, 25. Januar 2024 um 10:48:00 
>> UTC+1:
>>
>>> OK, I need to sort this out a little. I think I messed up with 0.6.0bx 
>>> and 0.5.0bx. Currently I've got too many things on my plate, and wasn't as 
>>> focused on this topic, as I should have been, sorry for that. I'll do my 
>>> homework and check everything again.
>>>
>>> gjr80 schrieb am Mittwoch, 24. Januar 2024 um 22:24:13 UTC+1:
>>>
 On Thursday 25 January 2024 at 06:56:42 UTC+10 michael.k...@gmx.at 
 wrote:

 The log is from latest logs I posted are from b5. Sorry, I forgot to 
 mention that I didn't use the file in your link above, I downloaded from 
 the releases, and for b4 it says: removed, go for b5. b5 is producing two 
 independent LOOP packets after a few on my RPi4.


 Sorry, but I don't understand this. The latest log you posted yesterday 
 is very clearly from b4:

 2024-01-23 19:46:51 weewxd[232660] INFO weewx.engine: Loading station 
 type GW1000 (user.gw1000) 
 2024-01-23 19:46:51 weewxd[232660] INFO user.gw1000: GatewayDriver: 
 version is 0.6.0b4 
 2024-01-23 19:46:51 weewxd[232660] INFO user.gw1000: device address is 
 10.0.1.85:45000

 b4 and b5 have not been published to releases, they have been produced 
 to deal with this issue and I have kept them back until I know the issue 
 is 
 fixed. You need to re-download the driver from the link I provided earlier 
 in order to get b5, b3 (releases) and b4 will never work. Here is the link 
 again:


 https://raw.githubusercontent.com/gjr80/weewx-gw1000/master/bin/user/gw1000.py

 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 

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

[vince]

Cool you solved it.  Wouldn't have thought that a baud rate thing would get 
you network unreachable. 

On Saturday, January 27, 2024 at 8:59:15 AM UTC-8 Bill Hattel wrote:

> Hi Vince,
> Thank you for replying. It turns out, it was something simple as usual. 
> It's not starting at power-up and in my haste to recognize that, I reset 
> the Ethernet to serial adapter to factory defaults which set the baud rate 
> to 115200. Once I set it back to 19200 and started weewx, it began 
> reporting. I'm still having an issue with it starting after reboot, but I 
> think I can resolve it without too much trouble. I'd like to hear any 
> suggestions you have for that issue though.
>
> As far as the complexity of my setup, I originally started out with the 
> Davis Instruments serial module on a PC which was kind of pricey back in 
> the early 2000s. The NetBurner approach let me keep my existing hardware 
> and add it to my home network for a reasonable cost.
>
> Thanks again!
> Bill
>
> On Friday, January 26, 2024 at 11:11:19 AM UTC-7 vince wrote:
>
>> On Friday, January 26, 2024 at 9:33:35 AM UTC-8 Bill Hattel wrote:
>>
>> I'm having the same issue after an upgrade to 5.0.0-1. I inspected the 
>> configuration file even though I selected no changes and found everything 
>> was correct. I also completely removed weewx and reinstalled it with a new 
>> configuration file. I can communicate with the Davis console through 
>> WeatherLink with the same settings and interface with no issue. The port is 
>> closed when WeatherLink exits.
>>
>> Davis Vantage Vue
>> Raspberry PI
>> NetBurner SBL2E Dual Serial to Ethernet converter
>> Homemade RS-232 level shifter.
>>
>>
>> Hmmmthat's pretty unusual/exotic hardware connecting the Vue to the 
>> pi
>>  
>>
>> Jan 25 19:44:10 raspberrypi weewxd[298]: ERROR weewx.drivers.vantage: 
>> Socket error while opening port 23 to ethernet host 192.168.50.39.
>>     this line 
>> Jan 25 19:44:10 raspberrypi weewxd[298]: ERROR weewx.engine: Import of 
>> driver failed: [Errno 101] Network is unreachable (> 'weewx.WeeWxIOError'>)
>> ]
>>
>> Jan 25 19:44:10 raspberrypi weewxd[298]: CRITICAL __main__: Unable to 
>> load driver: [Errno 101] Network is unreachable
>> Jan 25 19:44:10 raspberrypi weewxd[298]: CRITICAL __main__:  
>>  Exiting...
>> Jan 25 19:44:10 raspberrypi systemd[1]: weewx.service: Main process 
>> exited, code=exited, status=4/NOPERMISSION
>>
>>
>> Network unreachable is a different issue than others are having. 
>>
>> What's your weewx system ip ?  What is the ip you are trying to talk to ? 
>>   If they're on different networks you are possibly missing a route on your 
>> weewx system.   From the weewx system you might try "traceroute -n 
>> 192.168.50.39" if the destination address in your logs is correct.
>>
>> This one looks like a routing or packet filter issue on a router in 
>> between the weewx box and the serial-to-ethernet converter 'if' they are on 
>> different subnets
>>
>>

-- 
You received this message because you are subscribed 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/c6dd4f7f-625a-477b-9c0e-dfdad8bc9eben%40googlegroups.com.

Re: [weewx-user] Integrate rain24 with Packetsloop

[Remy Lavabre]

Hello Tom,

I followed your instructions:

1/“rain” field present in the database
2/ “dayRain” field not present in the database
3/ My driver returns “dayRain” values and not “rain” values in the 
packetsloop
4/ [[Delta]] [[ [rain]]] input = dayRain added in weewx.conf (under 
[StdWXCalculate]).

I did some tests : my driver returns 0.0 for dayRain but unfortunately the 
"rain" field in my database always remains NULL, even after several 
recordings in weewx.conf.
Shouldn't "rain" field go to 0.0?

THANKS

Le vendredi 26 janvier 2024 à 22:48:03 UTC+1, Tom Keffer a écrit :

> If an observation type never gets reset to zero, you have two choices.
> 1. Save the value. If you want to know daily use, take the difference of 
> the value.
> 2. Save the difference. That is, the change in the value over an archive 
> period. If you want to know daily use, you would sum all the small deltas. 
> This is like rain
>
> See the discussion *Accumulated vs delta energy 
> *
>  in 
> the README of the Brultech driver for the pros and cons of the two 
> approaches.
>
> It is not necessary to save "dayRain". WeeWX mostly uses "rain". Besides, 
> as you note, it can always be calculated.
>
>
>
> On Fri, Jan 26, 2024 at 7:06 AM Remy Lavabre  wrote:
>
>> And one more question
>> Is it absolutely necessary to create a "dayRain" field in addition to the 
>> "rain" field in the weewx.sdb database?
>> If the database only contains the [rain] field but the Weewx driver 
>> returns a "dayRain" field (cumulative rain over 24 hours since midnight) 
>> with a real value in each packetloop, the class [[Delta]] [[ [rain]]] input 
>> = dayRain will it work??
>> (the accumulation of rain since midnight is useless to me in a database 
>> field since it is easily calculated)
>> Sorry for all the questions...and thanks again! ;-)
>>
>> Le vendredi 26 janvier 2024 à 15:46:04 UTC+1, Remy Lavabre a écrit :
>>
>>> Hello Tom and thank you for your response.
>>>
>>>  [StdWXCalculate]
>>>  [[Calculations]]
>>>  ...
>>>  [[Delta]]
>>>  [[[rain]]]
>>>  input = dayRain
>>>
>>> This will calculate the rain difference between two records in weewx sql 
>>> based on the principle that the counter is reset to zero at midnight -> 
>>> PERFECT FOR THE RAIN 24H !
>>>
>>> Small additional question: if we wish to constantly calculate the 
>>> difference between two records values of a meter which *never* resets 
>>> to zero (such as an electricity or water meter), how should we proceed?
>>>
>>> THANKS
>>>
>>> Le jeudi 18 janvier 2024 à 14:05:10 UTC+1, Tom Keffer a écrit :
>>>
 Unfortunately (for you), WeeWX mostly uses observation type "rain", the 
 amount of rain that fell since the last loop packet (what you are calling 
 "instantaneous rain").

 You should assign the rain since midnight to type "dayRain".

 Then calculate "rain" as the difference between successive 
 "dayRain" values. While this is a pretty simple calculation, there is an 
 xtype that can do it for you.  See class Delta in weewx.wxxtypes 
 . 
 To use it, add this to weewx.conf:

 [StdWXCalculate]
 [[Calculations]]
 ...
 [[Delta]]
 [[[rain]]]
 input = dayRain




 On Wed, Jan 17, 2024 at 11:47 PM Remy Lavabre  
 wrote:

> Good morning,
>
> I created a [driver] for weewx to retrieve data from the Awekas API 
> (my Bresser weather station does not have a USB port).
>
> This works but regarding the rain, it is not the instantaneous rain 
> (from a packetloop) that we recover but the rain over 24 hours since 
> midnight.
> Is there a "simple" way to tell WeeWX that the packetsloop rain data 
> corresponds to the cumulative rain since midnight and not the rain that 
> fell during the data retrieval interval (the time gap between two 
> packetsloops) ?
>
> Thank you so much...
>
> -- 
> You received this message because you are subscribed 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/9887101f-fcc1-45ce-948e-e03429bf7baan%40googlegroups.com
>  
> 
> .
>
 -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.

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

[Bill Hattel]

Hi Vince,
Thank you for replying. It turns out, it was something simple as usual. 
It's not starting at power-up and in my haste to recognize that, I reset 
the Ethernet to serial adapter to factory defaults which set the baud rate 
to 115200. Once I set it back to 19200 and started weewx, it began 
reporting. I'm still having an issue with it starting after reboot, but I 
think I can resolve it without too much trouble. I'd like to hear any 
suggestions you have for that issue though.

As far as the complexity of my setup, I originally started out with the 
Davis Instruments serial module on a PC which was kind of pricey back in 
the early 2000s. The NetBurner approach let me keep my existing hardware 
and add it to my home network for a reasonable cost.

Thanks again!
Bill

On Friday, January 26, 2024 at 11:11:19 AM UTC-7 vince wrote:

> On Friday, January 26, 2024 at 9:33:35 AM UTC-8 Bill Hattel wrote:
>
> I'm having the same issue after an upgrade to 5.0.0-1. I inspected the 
> configuration file even though I selected no changes and found everything 
> was correct. I also completely removed weewx and reinstalled it with a new 
> configuration file. I can communicate with the Davis console through 
> WeatherLink with the same settings and interface with no issue. The port is 
> closed when WeatherLink exits.
>
> Davis Vantage Vue
> Raspberry PI
> NetBurner SBL2E Dual Serial to Ethernet converter
> Homemade RS-232 level shifter.
>
>
> Hmmmthat's pretty unusual/exotic hardware connecting the Vue to the 
> pi
>  
>
> Jan 25 19:44:10 raspberrypi weewxd[298]: ERROR weewx.drivers.vantage: 
> Socket error while opening port 23 to ethernet host 192.168.50.39.
>     this line 
> Jan 25 19:44:10 raspberrypi weewxd[298]: ERROR weewx.engine: Import of 
> driver failed: [Errno 101] Network is unreachable ( 'weewx.WeeWxIOError'>)
> ]
>
> Jan 25 19:44:10 raspberrypi weewxd[298]: CRITICAL __main__: Unable to load 
> driver: [Errno 101] Network is unreachable
> Jan 25 19:44:10 raspberrypi weewxd[298]: CRITICAL __main__:  
>  Exiting...
> Jan 25 19:44:10 raspberrypi systemd[1]: weewx.service: Main process 
> exited, code=exited, status=4/NOPERMISSION
>
>
> Network unreachable is a different issue than others are having. 
>
> What's your weewx system ip ?  What is the ip you are trying to talk to ? 
>   If they're on different networks you are possibly missing a route on your 
> weewx system.   From the weewx system you might try "traceroute -n 
> 192.168.50.39" if the destination address in your logs is correct.
>
> This one looks like a routing or packet filter issue on a router in 
> between the weewx box and the serial-to-ethernet converter 'if' they are on 
> different subnets
>
>

-- 
You received this message because you are subscribed 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/2c296dbd-205d-4dcd-9cb4-96f3cc952dbbn%40googlegroups.com.

Re: [weewx-user] Re: Debian 12 new install

[Stefanos Kalaitzis]

See here
https://groups.google.com/g/weewx-user/c/AJlPGe61xVU/m/AuOh3oiZAAAJ

Στις Σάβ 27 Ιαν 2024, 17:43 ο χρήστης 'super zee' via weewx-user <
weewx-user@googlegroups.com> έγραψε:

> Jon, I am having the same error.  What is the correct procedue to fix
> this?  I am doing a new Bookworm 64 bit install.
> Chris
>
> On Tuesday, January 16, 2024 at 4:31:01 AM UTC-7 Jon Fear wrote:
>
>> Indeed it was user error.
>>
>> I followed the commands in the apt directory and all appears well.
>>
>> Sorry folks.
>>
>> On Tuesday 16 January 2024 at 10:54:08 UTC Jon Fear wrote:
>>
>>> Hi Folks
>>>
>>> Pretty sure this is "user error" however after following the install
>>> notes: I guess the clue is "buster", Deb 12 is "bookworm". I did change in
>>> the apy config file but that did not work...
>>>
>>> jon@weewx-new:~$ sudo apt update
>>> Hit:1 http://deb.debian.org/debian bookworm InRelease
>>> Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
>>> Hit:3 http://security.debian.org/debian-security bookworm-security
>>> InRelease
>>> Get:4 https://weewx.com/apt/python3 buster InRelease [3,614 B]
>>> Err:4 https://weewx.com/apt/python3 buster InRelease
>>> The following signatures couldn't be verified because the public key is
>>> not available: NO_PUBKEY ED444FCCF0E2B09E
>>> Reading package lists... Done
>>> W: GPG error: https://weewx.com/apt/python3 buster InRelease: The
>>> following signatures couldn't be verified because the publi
>>> c key is not available: NO_PUBKEY ED444FCCF0E2B09E
>>> E: The repository 'https://weewx.com/apt/python3 buster InRelease' is
>>> not signed.
>>> N: Updating from such a repository can't be done securely, and is
>>> therefore disabled by default.
>>> N: See apt-secure(8) manpage for repository creation and user
>>> configuration details.
>>>
>>> jon@weewx-new:~$ sudo apt update
>>> Hit:1 http://deb.debian.org/debian bookworm InRelease
>>> Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
>>> Hit:3 http://security.debian.org/debian-security bookworm-security
>>> InRelease
>>> Ign:4 https://weewx.com/apt/python3 bookworm InRelease
>>> Err:5 https://weewx.com/apt/python3 bookworm Release
>>> 404 Not Found [IP: 34.218.218.142 443]
>>> Reading package lists... Done
>>> E: The repository 'https://weewx.com/apt/python3 bookworm Release' does
>>> not have a Release file.
>>> N: Updating from such a repository can't be done securely, and is
>>> therefore disabled by default.
>>> N: See apt-secure(8) manpage for repository creation and user
>>> configuration details.
>>> jon@weewx-new:~$
>>>
>>>
>>> --
> You received this message because you are subscribed 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/943c36d8-0d3b-4d48-8205-9d5e2469d789n%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/CAERekb8yuQPcZcjpOw-4rv9o0vPvsOrOeWOf6C-Ywp_2%3DAQvwA%40mail.gmail.com.

[weewx-user] Re: Debian 12 new install

['super zee' via weewx-user]

Jon, I am having the same error.  What is the correct procedue to fix 
this?  I am doing a new Bookworm 64 bit install.  
Chris 

On Tuesday, January 16, 2024 at 4:31:01 AM UTC-7 Jon Fear wrote:

> Indeed it was user error.
>
> I followed the commands in the apt directory and all appears well.
>
> Sorry folks.
>
> On Tuesday 16 January 2024 at 10:54:08 UTC Jon Fear wrote:
>
>> Hi Folks
>>
>> Pretty sure this is "user error" however after following the install 
>> notes: I guess the clue is "buster", Deb 12 is "bookworm". I did change in 
>> the apy config file but that did not work... 
>>
>> jon@weewx-new:~$ sudo apt update 
>> Hit:1 http://deb.debian.org/debian bookworm InRelease 
>> Hit:2 http://deb.debian.org/debian bookworm-updates InRelease 
>> Hit:3 http://security.debian.org/debian-security bookworm-security 
>> InRelease 
>> Get:4 https://weewx.com/apt/python3 buster InRelease [3,614 B] 
>> Err:4 https://weewx.com/apt/python3 buster InRelease 
>> The following signatures couldn't be verified because the public key is 
>> not available: NO_PUBKEY ED444FCCF0E2B09E 
>> Reading package lists... Done 
>> W: GPG error: https://weewx.com/apt/python3 buster InRelease: The 
>> following signatures couldn't be verified because the publi
>> c key is not available: NO_PUBKEY ED444FCCF0E2B09E 
>> E: The repository 'https://weewx.com/apt/python3 buster InRelease' is 
>> not signed. 
>> N: Updating from such a repository can't be done securely, and is 
>> therefore disabled by default. 
>> N: See apt-secure(8) manpage for repository creation and user 
>> configuration details.   
>>
>> jon@weewx-new:~$ sudo apt update 
>> Hit:1 http://deb.debian.org/debian bookworm InRelease 
>> Hit:2 http://deb.debian.org/debian bookworm-updates InRelease 
>> Hit:3 http://security.debian.org/debian-security bookworm-security 
>> InRelease 
>> Ign:4 https://weewx.com/apt/python3 bookworm InRelease 
>> Err:5 https://weewx.com/apt/python3 bookworm Release 
>> 404 Not Found [IP: 34.218.218.142 443] 
>> Reading package lists... Done 
>> E: The repository 'https://weewx.com/apt/python3 bookworm Release' does 
>> not have a Release file. 
>> N: Updating from such a repository can't be done securely, and is 
>> therefore disabled by default. 
>> N: See apt-secure(8) manpage for repository creation and user 
>> configuration details. 
>> jon@weewx-new:~$ 
>>
>>
>>

-- 
You received this message because you are subscribed 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/943c36d8-0d3b-4d48-8205-9d5e2469d789n%40googlegroups.com.

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

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

Case typo?

if self.latest_sensor_data is None or sensor_data['datetime'] > 
self.latest_sensor_data['dateTime']:
michael.k...@gmx.at schrieb am Samstag, 27. Januar 2024 um 14:24:58 UTC+1:

> That part worked. You can tell by the weewx.restx: MQTT: Published record 
> entries in the log, there is only one Loop packet every 10s (the poll 
> interval).
> But after a few archive_intervals it crashed:
>
> 2024-01-27 14:17:25 weewxd[657388] INFO weewx.engine: Main loop exiting. 
> Shutting engine down.
> 2024-01-27 14:17:25 weewxd[657388] INFO weewx.engine: Shutting down 
> StdReport thread
> 2024-01-27 14:17:26 weewxd[657388] INFO user.gw1000: GatewayCollector 
> thread has been terminated
> 2024-01-27 14:17:27 weewxd[657388] INFO user.gw1000: GatewayCollector 
> thread has been terminated
> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: Caught unrecoverable 
> exception:
> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   'dateTime'
> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   Traceback 
> (most recent call last):
>
> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
> "/home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py", line 166, in 
> main
>
> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
>  engine.run()
>
> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
> "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
> 206, in run
>
> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
>  self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
>
> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
> "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
> 241, in dispatchEvent
>
> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
>  callback(event)
>
> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
> "/home/pi/weewx-data/bin/user/gw1000.py", line 1504, in new_loop_packet
>
> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
>  self.process_queued_sensor_data(queue_data, event.packet['dateTime'])
>
> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
> "/home/pi/weewx-data/bin/user/gw1000.py", line 1611, in 
> process_queued_sensor_data
>
> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   if 
> self.latest_sensor_data is None or sensor_data['datetime'] > 
> self.latest_sensor_data['dateTime']:
>
> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   KeyError: 
> 'dateTime'
>
> 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   Exiting.
>
>
> michael.k...@gmx.at schrieb am Donnerstag, 25. Januar 2024 um 10:48:00 
> UTC+1:
>
>> OK, I need to sort this out a little. I think I messed up with 0.6.0bx 
>> and 0.5.0bx. Currently I've got too many things on my plate, and wasn't as 
>> focused on this topic, as I should have been, sorry for that. I'll do my 
>> homework and check everything again.
>>
>> gjr80 schrieb am Mittwoch, 24. Januar 2024 um 22:24:13 UTC+1:
>>
>>> On Thursday 25 January 2024 at 06:56:42 UTC+10 michael.k...@gmx.at 
>>> wrote:
>>>
>>> The log is from latest logs I posted are from b5. Sorry, I forgot to 
>>> mention that I didn't use the file in your link above, I downloaded from 
>>> the releases, and for b4 it says: removed, go for b5. b5 is producing two 
>>> independent LOOP packets after a few on my RPi4.
>>>
>>>
>>> Sorry, but I don't understand this. The latest log you posted yesterday 
>>> is very clearly from b4:
>>>
>>> 2024-01-23 19:46:51 weewxd[232660] INFO weewx.engine: Loading station 
>>> type GW1000 (user.gw1000) 
>>> 2024-01-23 19:46:51 weewxd[232660] INFO user.gw1000: GatewayDriver: 
>>> version is 0.6.0b4 
>>> 2024-01-23 19:46:51 weewxd[232660] INFO user.gw1000: device address is 
>>> 10.0.1.85:45000
>>>
>>> b4 and b5 have not been published to releases, they have been produced 
>>> to deal with this issue and I have kept them back until I know the issue is 
>>> fixed. You need to re-download the driver from the link I provided earlier 
>>> in order to get b5, b3 (releases) and b4 will never work. Here is the link 
>>> again:
>>>
>>>
>>> https://raw.githubusercontent.com/gjr80/weewx-gw1000/master/bin/user/gw1000.py
>>>
>>> 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/42f2b88d-0e0d-48d5-bbf8-fffa6df490e4n%40googlegroups.com.

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

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

That part worked. You can tell by the weewx.restx: MQTT: Published record 
entries in the log, there is only one Loop packet every 10s (the poll 
interval).
But after a few archive_intervals it crashed:

2024-01-27 14:17:25 weewxd[657388] INFO weewx.engine: Main loop exiting. 
Shutting engine down.
2024-01-27 14:17:25 weewxd[657388] INFO weewx.engine: Shutting down 
StdReport thread
2024-01-27 14:17:26 weewxd[657388] INFO user.gw1000: GatewayCollector 
thread has been terminated
2024-01-27 14:17:27 weewxd[657388] INFO user.gw1000: GatewayCollector 
thread has been terminated
2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: Caught unrecoverable 
exception:
2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   'dateTime'
2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   Traceback 
(most recent call last):

2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
"/home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py", line 166, in 
main

2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
 engine.run()

2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
"/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
206, in run

2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
 self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))

2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
"/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
241, in dispatchEvent

2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
 callback(event)

2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
"/home/pi/weewx-data/bin/user/gw1000.py", line 1504, in new_loop_packet

2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
 self.process_queued_sensor_data(queue_data, event.packet['dateTime'])

2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
"/home/pi/weewx-data/bin/user/gw1000.py", line 1611, in 
process_queued_sensor_data

2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   if 
self.latest_sensor_data is None or sensor_data['datetime'] > 
self.latest_sensor_data['dateTime']:

2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   KeyError: 
'dateTime'

2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   Exiting.


michael.k...@gmx.at schrieb am Donnerstag, 25. Januar 2024 um 10:48:00 
UTC+1:

> OK, I need to sort this out a little. I think I messed up with 0.6.0bx and 
> 0.5.0bx. Currently I've got too many things on my plate, and wasn't as 
> focused on this topic, as I should have been, sorry for that. I'll do my 
> homework and check everything again.
>
> gjr80 schrieb am Mittwoch, 24. Januar 2024 um 22:24:13 UTC+1:
>
>> On Thursday 25 January 2024 at 06:56:42 UTC+10 michael.k...@gmx.at wrote:
>>
>> The log is from latest logs I posted are from b5. Sorry, I forgot to 
>> mention that I didn't use the file in your link above, I downloaded from 
>> the releases, and for b4 it says: removed, go for b5. b5 is producing two 
>> independent LOOP packets after a few on my RPi4.
>>
>>
>> Sorry, but I don't understand this. The latest log you posted yesterday 
>> is very clearly from b4:
>>
>> 2024-01-23 19:46:51 weewxd[232660] INFO weewx.engine: Loading station 
>> type GW1000 (user.gw1000) 
>> 2024-01-23 19:46:51 weewxd[232660] INFO user.gw1000: GatewayDriver: 
>> version is 0.6.0b4 
>> 2024-01-23 19:46:51 weewxd[232660] INFO user.gw1000: device address is 
>> 10.0.1.85:45000
>>
>> b4 and b5 have not been published to releases, they have been produced to 
>> deal with this issue and I have kept them back until I know the issue is 
>> fixed. You need to re-download the driver from the link I provided earlier 
>> in order to get b5, b3 (releases) and b4 will never work. Here is the link 
>> again:
>>
>>
>> https://raw.githubusercontent.com/gjr80/weewx-gw1000/master/bin/user/gw1000.py
>>
>> 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/2ccaf978-3c45-4db4-b557-de7db220d8c1n%40googlegroups.com.
2024-01-27 13:52:25 weewxd[657388] INFO __main__: Initializing weewxd version 
5.0.0
2024-01-27 13:52:25 weewxd[657388] INFO __main__: Command line: 
/home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py 
/home/pi/weewx-data/weewx.conf
2024-01-27 13:52:25 weewxd[657388] INFO __main__: Using Python 3.9.2 (default, 
Feb 28 2021, 17:03:44) 
[GCC 10.2.1 20210110]
2024-01-27 13:52:25 weewxd[657388] INFO __main__: Located at 
/home/pi/weewx-venv/bin/python3
2024-01-27 13:52:25 weewxd[657388] INFO __main__: Platform 
Linux-6.1.42-v8+-aarch64-with-glibc2.31
2024-01-27 13:52:25 weewxd[657388] INFO