Re: [weewx-user] Re: Belchertown and MQTT configuration error

[Stefanos Kalaitzis]

Try this in weewx.conf :** but be careful with the unit_system
[[MQTT]]
topic = your_topic
unit_system = METRICWX
binding = loop
aggregation = aggregate
log_success = false
log_failure = true
server_url = mqtt://broker.hivemq.com:1883

  [[[inputs]]]
windSpeed
units = km_per_hour
windGust
units = km_per_hour

In belchertown stanza :
#--- MQTT Websockets (for Real Time Streaming) Options ---
mqtt_websockets_enabled = 1
mqtt_websockets_host = broker.hivemq.com
mqtt_websockets_port = 8884
mqtt_websockets_ssl = 1
mqtt_websockets_topic = yourtopic/loop
# disconnect_live_website_visitor = 180

**Change only the topic and the unit system you are using. Because i am
writing from mobile please forgive me if something is strange to your eyes.

Στις Παρ 2 Αυγ 2024, 21:42 ο χρήστης vince  έγραψε:

> You're probably overthinking. It's really very simple.   You don't need
> SSL if you're just going to run on your LAN.  You likely don't even need to
> password protect it either if you are LAN only.
>
> See the example starting at line 72 of
> https://github.com/vinceskahan/weewx-odds-and-ends/blob/master/install-belchertown-websockets
> for the minimal mosquitto MQTT server setup that works for me.
>
> On Friday, August 2, 2024 at 10:56:59 AM UTC-7 M&M wrote:
>
>> I've read a bunch about MQTT, Belchertown, and Weewx so I thought I would
>> able to get this working.  From the pages I read on github and such, it
>> didn't seem like it took a lot of configuration to mosquitto to get it
>> working.  From the links I posted above that I followed, it didn't seem
>> that I needed to have SSL certs working yet to get it working locally.  I
>> figured I would do that first before venturing out to get this working on a
>> website.  So I'll go back and see what I can configure to get the certs
>> added to my conf files.
>>
>> Do you have any websites that you suggest to use to get this working?  I
>> feel like I'm close.
>>
>> On Friday, August 2, 2024 at 8:41:28 AM UTC-4 gary@gmail.com wrote:
>>
>>> I see you haven't done much research.
>>> If you want to understand this and get the Belchertown skin to work, you
>>> need to do some.
>>> A default mosquitto.conf isn't going to work as you want.
>>> You will likely need SSL certs in order to have websockets work via the
>>> internet vs local LAN.
>>> You should have writing to mosquitto password protected, but
>>> allow anonymous reading.
>>>
>>> When MQTT/Websockets works, it is great. Getting there requires a
>>> passing familiarity with the care and feeding of mosquitto.
>>>
>>> On Thursday, August 1, 2024 at 11:38:28 PM UTC-4 M&M wrote:
>>>
 Where can I find out if I have acl?

 My mosquitto.conf file looks a bit different.  I didn't change any of
 it after it was installed besides the two listener lines.  It looks like
 this:

 pi@raspberrypi:~ $ more /etc/mosquitto/mosquitto.conf
 # Place your local configuration in /etc/mosquitto/conf.d/
 #
 # A full description of the configuration file is at
 # /usr/share/doc/mosquitto/examples/mosquitto.conf.example

 pid_file /run/mosquitto/mosquitto.pid

 persistence true
 persistence_location /var/lib/mosquitto/

 log_dest file /var/log/mosquitto/mosquitto.log

 include_dir /etc/mosquitto/conf.d

 listener 1883
 listener 9001
 protocol websockets

 On Thursday, August 1, 2024 at 9:38:48 AM UTC-4 gary@gmail.com
 wrote:

> Do you have an acl and does it resemble this?
> # Allow anonymous access to the sys
> topic read $SYS/#
>
> # Allow anonymous to read weather
> topic read weather/#
> topic read tester/#
>
> # weewx readwrite to the loop
> user weewx
> topic weather/#
> topic tester/#
>
> Did you create a password for the weewx user (not the linux user, the
> mqtt user)?
>
> Does your mosquitto conf file resemble this?
> persistence false
> allow_anonymous true
> password_file /etc/mosquitto/pwfile
> acl_file /etc/mosquitto/acl
> # Insecure mqtt to localhost only, and secure mqtt
> listener 1883
> listener 8883
> certfile /etc/mosquitto/certs/cert.pem
> cafile /etc/mosquitto/certs/chain.pem
> keyfile /etc/mosquitto/certs/privkey.pem
> protocol mqtt
>
> # websockets
> listener 8080
> certfile /etc/mosquitto/certs/cert.pem
> cafile /etc/mosquitto/certs/chain.pem
> keyfile /etc/mosquitto/certs/privkey.pem
> protocol websockets
> On Wednesday, July 31, 2024 at 11:47:46 PM UTC-4 M&M wrote:
>
>> I checked mosquitto.conf and it has "listener 1883" in it.  I also
>> disabled my pihole and checked that my raspberry pi is listening on port
>> 1883.
>>
>> On Fr

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

[Stefanos Kalaitzis]

You helped me so many times here So i am happy that i gave you a little
hand ☺️ 👌

Στις Κυρ 3 Μαρ 2024, 23:16 ο χρήστης vince  έγραψε:

> Perfect.  Wow I definitely read the rtl_433 usage backwards.  Thanks !!!
>
> On Sunday, March 3, 2024 at 12:43:52 PM UTC-8 Stefanos Kalaitzis wrote:
>
> I think in the command you can use utc option .. something like this
>
> cmd = /usr/local/bin/rtl_433 -M utc -F json -f 868.2M -R 172
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/44560a5f-c289-439e-b1f3-fa54d43b2f2cn%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/44560a5f-c289-439e-b1f3-fa54d43b2f2cn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAERekb_wo6p17JteSybt7%2BeAaEeAvZWNwgJRnGnX73NNU2%3DEFQ%40mail.gmail.com.

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

[Stefanos Kalaitzis]

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

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

Στις Κυρ 3 Μαρ 2024, 22:10 ο χρήστης vince  έγραψε:

> I'm fiddling on the side with the SDR driver trying to help another user
> set up weewx with the sdr driver but have run into some oddities here on my
> system.
>
> Short description is the packets as decoded by the sdr driver have a
> dateTime that is many hours behind reality.
>
> The sdr driver is generating packets with a dateTime that is behind
> localtime reality by the exact number of hours as my GMT offset here (8
> hours)
>
> Yet the system clock on the os looks correct, syslog logs correctly, etc.
> in every other way.   Here are the details
>
> ~/weewx-data/bin/user$ date
> Sun Mar  3 11:40:44 AM PST 2024
>
> ~/weewx-data/bin/user$ date -u
> Sun Mar  3 07:40:46 PM UTC 2024
>
> ~/weewx-data/bin/user$ timedatectl status
>Local time: Sun 2024-03-03 11:41:20 PST
>Universal time: Sun 2024-03-03 19:41:20 UTC
>  RTC time: Sun 2024-03-03 19:41:20
> Time zone: America/Los_Angeles (PST, -0800)
> System clock synchronized: yes
>   NTP service: n/a
>   RTC in local TZ: no
>
> From the syslogs...
> 2024-03-03T*11:25:39*.336424-08:00 nuc weewxd[9124]: DEBUG user.sdr:
> packet={'extraTemp1': 19.9, 'extraHumid1': 44.0, 'batteryStatus1': 1,
> 'dateTime': 1709465136, 'usUnits': 17}
>
> Then decoding the dateTime
> ~/weewx-data/bin/user$ date -d @1709465136
> Sun Mar  3 *03:25:36* AM PST 2024
>
> ==> note the decoded dateTime is off by 8 hours.
>
> But when using rtl_433 directly
> {"time" : "2024-03-03 *11:39:21*", "model" : "AmbientWeather-WH31B", "id"
> : 202, "channel" : 5, "battery_ok" : 1, "temperature_C" : 4.600, "humidity"
> : 87, "data" : "785c00", "mic" : "CRC"}
>
> Note the rtl_433 time is correct.
>
> So there's a bug or misconfiguration somewhere but I'm not sure where:
>
>- system clock looks correct
>- rtl_433 decodes the dateTime correctly
>- but weewx sdr is off by 8 hours
>- and the result also seems to be that weewx doesn't save anything to
>the archive table at all.  It doesn't even seem to try from what I can see
>with debug=1.  Could that be due to the dateTime SDR is generating being 8
>hours slow ?
>
> weewx.conf snippet is as follows:
>
> [SDR]
> # This section is for the software-defined radio driver.
>
> # The driver to use
> driver = user.sdr
> cmd = rtl_433
>
> log_unknown_sensors  = True
> log_unmapped_sensors = True
>
> log_duplicate_readings = False # patched sdr.py to quiet logs down
> log_packets= True # patched sdr.py to quiet logs down
>
> [[sensor_map]]
> extraTemp1 = temperature.145.AmbientWH31BPacket
> extraHumid1= humidity.145.AmbientWH31BPacket
> batteryStatus1 = battery.145.AmbientWH31BPacket
>
> extraTemp2 = temperature.153.AmbientWH31BPacket
> extraHumid2= humidity.153.AmbientWH31BPacket
> batteryStatus2 = battery.153.AmbientWH31BPacket
>
> extraTemp3 = temperature.196.AmbientWH31BPacket
> extraHumid3= humidity.196.AmbientWH31BPacket
> batteryStatus3 = battery.196.AmbientWH31BPacket
>
> extraTemp4 = temperature.55.AmbientWH31BPacket
> extraHumid4= humidity.55.AmbientWH31BPacket
> batteryStatus4 = battery.55.AmbientWH31BPacket
>
> extraTemp5 = temperature.202.AmbientWH31BPacket
> extraHumid5= humidity.202.AmbientWH31BPacket
> batteryStatus5 = battery.202.AmbientWH31BPacket
>
> outTemp  = temperature.35.AmbientWH31BPacket
> outHumidity  = humidity.35.AmbientWH31BPacket
> outTempBatteryStatus = battery.35.AmbientWH31BPacket
>
> soilMoist1 = soil_moisture_percent.001260.FOWH51Packet
>
> I did patch sdr.py to add a couple new sensor types it didn't know about
> and also to be able to more discretely control logging.  The upstream
> version is a bit verbose when debug=1 (I'd be happy to PR those).   I
> didn't do anything to alter how sdr.py actually does its thing in decoding
> packets it hears via rtl_433.
>
> Sensors are all ecowitt and I did verify in the ecowitt gateway app that
> its timezone is set correctly but given I'm sniffing RF via SDR, I'm
> guessing it doesn't really matter what the ecowitt iphone app is set to do
> (?)
>
> ~/.config/rtl_433/rtl_433.conf has nothing time-related in it
> frequency 915M
> output json
>
> Suggestions or pointers to where anybody's run into this before
> appreciated
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.co

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Stefanos Kalaitzis]

i forgot to write in my last message  that when you finished you must 
restart udev or restart the device you using( p.c , rpi ,... etc)

On Tuesday, February 6, 2024 at 7:11:07 PM UTC+2 matthew wall wrote:

> On Tuesday, February 6, 2024 at 11:38:24 AM UTC-5 Pierre-Yves wrote:
>
> It seems to be a problem of rules change. In fact, I first upgraded from 
> 4.10.2 to 5.0.0 and weewx worked perfectly. 
>
>
> weewx was running as root:root. weewx 5.0.0 did not modify any permissions 
> when it upgraded from 4.10.2.
>  
>
> Then I went from 5.0.0 to 5.0.1 an weewx failed to start.
>
>
> weewx was running as weewx:weewx.  weewx 5.0.1 converts from root:root 
> permissions to weewx:weewx permissions, and runs the daemon as weewx.
>  
>
> For Weewx,, I did a deb/rpm install and, as far I remember, I installed 
> rtl-sdr following your Git (https://github.com/matthewwall/weewx-sdr).
>
> I tried the command you proposed (sudo usermod -aG plugdev weewx) but that 
> doesn't solve the problem.
>
>
> is there a udev rules file for sdr?  (it is a separate step when you build 
> rtl-sdr from source)
> if there is a udev rules file for sdr, how are the permissions set?
> did the usermod for weewx succeed?
> is weewx in the plugdev group?  (grep weewx /etc/group)
> did you restart weewxd after putting weewx into the plugdev group?
>  
>
> Regarding the rtl-sdr rules, I have a doubt. I installed the file in 
> /etc/weewx/udev/rules.d. Maybe it is a wrong place... I read in another 
> thread that it should be in /usr/lib/udev/rules.d... What about ?
>
>
> packages install to /usr/lib/udev/rules.d
>
> system administrators (or end-users acting as system administrators) put 
> things in /etc/udev/rules.d
>
> that way you can override whatever a package installs, and your changes 
> will not be overwritten by the package when you upgrade/update.
>  
>

-- 
You received this message because you are subscribed 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/a48a3432-f9a6-422e-9cd2-827379e7e557n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Stefanos Kalaitzis]

I use a nooelec rtl-sdr.  On a fresh install  of bookworm 64bit in a 
Raspberry pi 4 and weewx v5  i solved the error like this:
i run  *lsusb*
and i saw a line similar to this 
 Bus 001 Device 008: ID 0bda:2838 Realtek Semiconductor Corp.

**  "0bda" is the vendor id and "2838" is the product id (maybe yours are 
different)**

then i made a new file as root in  /etc/udev/rules.d/rtl-sdr.rules
next i modifyed this: *sudo nano  /etc/udev/rules.d/rtl-sdr.rules*
and i added this line :
 SUBSYSTEM=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2838", 
GROUP="adm", MODE="0666", SYMLINK+="rtl_sdr"  

hope this will help you 

On Tuesday, February 6, 2024 at 6:38:24 PM UTC+2 Pierre-Yves wrote:

> @ Matthew,
>
> Thanks a lot for the feedback.
>
> It seems to be a problem of rules change. In fact, I first upgraded from 
> 4.10.2 to 5.0.0 and weewx worked perfectly. Then I went from 5.0.0 to 5.0.1 
> an weewx failed to start.
>
> For Weewx,, I did a deb/rpm install and, as far I remember, I installed 
> rtl-sdr following your Git (https://github.com/matthewwall/weewx-sdr).
>
> I tried the command you proposed (sudo usermod -aG plugdev weewx) but that 
> doesn't solve the problem.
>
> Regarding the rtl-sdr rules, I have a doubt. I installed the file in 
> /etc/weewx/udev/rules.d. Maybe it is a wrong place... I read in another 
> thread that it should be in /usr/lib/udev/rules.d... What about ?
>
> Pierre-Yves
>
>
>
> Le mardi 6 février 2024 à 17:09:36 UTC+1, Tom Hogland a écrit :
>
>> In case anyone else runs into this - my Ubuntu server/Davis VP2 and 
>> serial datalogger had ownership set to root:dialout, so I had to add the 
>> weewx user to the dialout group for things to work. 
>>
>> On Tuesday, February 6, 2024 at 6:23:15 AM UTC-9 matthew wall wrote:
>>
>>> when you install rtl-sdr, it typically, but not always, installs udev 
>>> rules for *many* sdr devices.  the udev rules that it installs make it 
>>> possible for anyone in the 'plugdev' group to read/write to the sdr 
>>> device.  (this is true when you install rtl-sdr from source - if you 
>>> install rtl-sdr from a deb/rpm package, it might be different - anyone with 
>>> this configuration please let us know)
>>>
>>> weewx v4 runs as root:root, so it has access to the sdr device no matter 
>>> what the udev rules might be
>>>
>>> weewx v5 runs as weewx:weewx (for a deb/rpm install) or as a regular 
>>> non-root user (for pip installs).  so udev rules are required.
>>>
>>> btw, weewx 5.0.1 *always* converts to weewx:weewx, whereas 5.0.0 did not 
>>> (it would continue to run as root - we changed in 5.0.1 because overall 
>>> security and best practice)
>>>
>>> the udev rules installed by rtl-sdr will not help for a deb/rpm install, 
>>> since the user 'weewx' is not in the plugdev group.  you can either added 
>>> the user weewx to the plugdev group, or modify the udev rules to use 
>>> 'weewx' instead of 'plugdev' as the group.  this is how to do the former:
>>>
>>> sudo usermod -aG plugdev weewx
>>>
>>> for a pip install, be sure that the user running weewx is in the 
>>> 'plugdev' group.
>>>
>>> restart of the weewxd daemon is almost certainly required so that the 
>>> daemon process has the right group.  reboot is not necessary.
>>>
>>> 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/b009ccff-87bc-4c60-b003-23389a098724n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Stefanos Kalaitzis]

I had the same error with sdr driver(weewx v5 )  running on debian 12 . The
problem solved by making udev rules ... maybe you are in the same situation
as i was.

Στις Τρί 6 Φεβ 2024, 11:29 ο χρήστης Mks Mk  έγραψε:

> The system was running weewx v5.0.0 with no issue then we did the upgrade
> to v5.0.1 (sudo apt update) and weewx failed to run.
> we downgraded weewx to v5.0.0 but it did not work this time, so we went
> back to v4.10.2 and it run just fine.
> did the upgrade again and got the same error.so we are back to v4.10.2
> we tested the sdr hardware using rtl_433 and it is working fine.
> we are not sure of what to do next!
>
> log:
> weewxd[2386]: INFO __main__: Starting up weewx version 5.0.1
> weewxd[2386]: INFO weewx.engine: Using binding 'wx_binding' to database
> 'weewx.sdb'
> weewxd[2386]: INFO weewx.manager: Starting backfill of daily summaries
> weewxd[2386]: INFO weewx.manager: Daily summaries up to date
> weewxd[2386]: INFO weewx.engine: Starting main packet loop.
> weewxd[2386]: ERROR user.sdr: rtl_433 version 23.11-41-g06b03b7a branch
> master at 202402051043 inputs file rtl_tcp RTL-SDR
> weewxd[2386]: ERROR user.sdr: Use "-F log" if you want any messages,
> warnings, and errors in the console.
> weewxd[2386]: ERROR user.sdr: usb_open error -3
> weewxd[2386]: ERROR user.sdr: Please fix the device permissions, e.g. by
> installing the udev rules file rtl-sdr.rules
> weewxd[2386]: INFO weewx.engine: Main loop exiting. Shutting engine down.
> weewxd[2386]: INFO user.sdr: shutdown process rtl_433 -f 433.7M -s 1024k
> -R 40
> weewxd[2386]: Exception in thread stdout-thread:
> weewxd[2386]: Traceback (most recent call last):
> weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in
> _bootstrap_inner
> weewxd[2386]: Exception in thread stderr-thread:
> weewxd[2386]: Traceback (most recent call last):
> weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in
> _bootstrap_inner
> weewxd[2386]: self.run()
> weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
> weewxd[2386]: for line in iter(self._fd.readline, ''):
> weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not be
> NULL
> weewxd[2386]: self.run()
> weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
> weewxd[2386]: for line in iter(self._fd.readline, ''):
> weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not be
> NULL
> weewxd[2386]: INFO user.sdr: shutdown complete
> weewxd[2386]: CRITICAL __main__: Caught WeeWxIOError: rtl_433 process is
> not running
> weewxd[2386]: CRITICAL __main__:   Waiting 60.0 seconds then
> retrying...
>
> --
> You received this message because you are subscribed 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/4c62d6c3-d690-49e8-8151-8b9af8dd5b43n%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/CAERekb9xjoLYZAFcRMLwVCEHPHqaqMvEmGUFCY2EyheB2FdugA%40mail.gmail.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: Weewx 5.0 with Rpi4 bookworm 64bit

[Stefanos Kalaitzis]

Hi Matthew ... keys still have error ... with keys-old everything is fine
Also what i noticed : when i was trying to install sdr driver even though i 
was able to run the driver directly , with 
PYTHONPATH=/usr/share/weewx python /etc/weewx/bin/user/sdr.py 
--cmd="rtl_433 -M utc -F json -f 868.2M -R 172"
when i started weewx i had this error:
raspberrypi weewxd[2999]:   File "/etc/weewx/bin/user/sdr.py", line 198, in 
run
Ιαν 25 19:57:11 raspberrypi weewxd[2999]: for line in 
iter(self._fd.readline, ''):
Ιαν 25 19:57:11 raspberrypi weewxd[2999]: ValueError: 
PyMemoryView_FromBuffer(): info->buf must not be NULL
Ιαν 25 19:57:11 raspberrypi weewxd[2999]: self.run()
Ιαν 25 19:57:11 raspberrypi weewxd[2999]:   File 
"/etc/weewx/bin/user/sdr.py", line 198, in run
Ιαν 25 19:57:11 raspberrypi weewxd[2999]: for line in 
iter(self._fd.readline, ''):
Ιαν 25 19:57:11 raspberrypi weewxd[2999]: ValueError: 
PyMemoryView_FromBuffer(): info->buf must not be NULL
Ιαν 25 19:57:11 raspberrypi weewxd[2999]: INFO user.sdr: shutdown complete
Ιαν 25 19:57:11 raspberrypi weewxd[2999]: CRITICAL __main__: Caught 
WeeWxIOError: rtl_433 process is not running   
   
Ιαν 25 19:57:11 raspberrypi weewxd[2999]: CRITICAL __main__:  
 Waiting 60.0 seconds then retrying... 

The problem solved by reading this:
https://www.instructables.com/rtl-sdr-on-Ubuntu/
and making udev rules
now everyhting working as it should be 
  

On Thursday, January 25, 2024 at 4:32:05 AM UTC+2 matthew wall wrote:

> On Wednesday, January 24, 2024 at 12:48:33 PM UTC-5 stefanos...@gmail.com 
> wrote:
>
>   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 public key is not 
> available: NO_PUBKEY ED444FCCF0E2B09E
>
>
> sorry about that.  i rearranged the key files before i finished the rest 
> of the release.  keys have been restored.
>
> for future reference: the current keys will always be in 
> https://weewx.com/keys.html, while all of the keys (current and all 
> previous keys) will be in https://weewx.com/keys-old.html.  if you need 
> to install an older deb/rpm that was signed by an older key, use keys-old.  
> use keys.html for recent systems, since they will probably reject the older 
> keys we used to sign things before 2024.
>
> 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/44ceff70-5496-4488-8a83-1ae9539f5400n%40googlegroups.com.

Re: [weewx-user] Re: Weewx 5.0 with Rpi4 bookworm 64bit

[Stefanos Kalaitzis]

Oh 😱 ..!! First of all thank you for the quick reply ... The truth is that
i made several searches but not with the key value ..!! I apologise for
that !!

Also Something  else ... a question to Gary ...
In weewx saratoga extension the wind and wind gust are always the same ..
probably the extension pass wind value to wind gust ! I have the 0.1.7
version . All the others are working fine . See the last messages
https://groups.google.com/g/weewx-user/c/DiR9FEVYnb4
Thanks again

Στις Τετ 24 Ιαν 2024, 21:32 ο χρήστης vince  έγραψε:

> As always, look up your exact error message "NO_PUBKEY ED444FCCF0E2B09E"
> in the group archives, which points you to.
>
> https://groups.google.com/g/weewx-user/c/AJlPGe61xVU/m/AuOh3oiZAAAJ
>
> Looks like the keys.html file mentioned in the docs still has issues.   I
> got this error too on a clean deb12 install attempt just now.
>
> On Wednesday, January 24, 2024 at 9:48:33 AM UTC-8 Stefanos Kalaitzis
> wrote:
>
>> Hi to all and many thanks to creators and to all that contribute to have
>> the best weather software by far
>> I have already running weewx 4.10.2 (2 stations , one sdr and the other
>> gw1000) with no problem at all and i am very happy . Today i had free time
>> so i decided to try an installation in an other sd card everything from the
>> beginning (rasbian OS ,weewx 5, etc)
>> I follow the steps of debian installation (apt)  as described in official
>> weewx page and after step 2 i had the following error :
>>
>> sudo apt update
>> sudo apt install weewx
>>
>> Hit:1 http://archive.raspberrypi.com/debian bookworm InRelease
>> Hit:2 http://deb.debian.org/debian bookworm InRelease
>>
>> Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease
>>
>> Hit:4 http://deb.debian.org/debian bookworm-updates InRelease
>>
>> Get:5 https://weewx.com/apt/python3 buster InRelease [3614 B]
>> Err:5 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 public key is not
>> available: NO_PUBKEY ED444FCCF0E2B09E
>> E: *The repository 'https://weewx.com/apt/python3
>> <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.
>> Reading package lists... Done
>> Building dependency tree... Done
>> Reading state information... Done
>> E: *Unable to locate package weewx*
>>
>> I hope that i didnt miss something . As i wrote above because i have
>> already running weewx i am not in a hurry so if someone knows what i am
>> doing wrong i would be appreciated
>> Thank you in advanced
>>
> --
> You received this message because you are subscribed 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/a9f195da-f8a7-4fdb-a6c1-39acb9f9cb2cn%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/a9f195da-f8a7-4fdb-a6c1-39acb9f9cb2cn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

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

[weewx-user] Weewx 5.0 with Rpi4 bookworm 64bit

[Stefanos Kalaitzis]

Hi to all and many thanks to creators and to all that contribute to have 
the best weather software by far 
I have already running weewx 4.10.2 (2 stations , one sdr and the other 
gw1000) with no problem at all and i am very happy . Today i had free time 
so i decided to try an installation in an other sd card everything from the 
beginning (rasbian OS ,weewx 5, etc)
I follow the steps of debian installation (apt)  as described in official 
weewx page and after step 2 i had the following error :

sudo apt update
sudo apt install weewx

Hit:1 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease   
   
Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease 
   
Hit:4 http://deb.debian.org/debian bookworm-updates InRelease   
   
Get:5 https://weewx.com/apt/python3 buster InRelease [3614 B]
Err:5 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 public 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.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: *Unable to locate package weewx*

I hope that i didnt miss something . As i wrote above because i have 
already running weewx i am not in a hurry so if someone knows what i am 
doing wrong i would be appreciated
Thank you in advanced 

-- 
You received this message because you are subscribed 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/eff9055d-cef6-42f6-86a8-8f46cb6e2045n%40googlegroups.com.

Re: [weewx-user] adding mm to daily rainfall

[Stefanos Kalaitzis]

t; rain plots (all except the 'today' plot), the June 2023 and 2023 NOAA
>>>> format reports and the statistics widget/page. All should come good in time
>>>> (max 24 hours) provided you update your data sometime this month, but if
>>>> you want to speed things up delete all your rain plots on your WeeWX
>>>> machine. If you update your data in say July you will need to delete the
>>>> June 2023 and 2023 NOAA format reports and all subsequent NOAA format
>>>> reports to force regeneration.
>>>>
>>>> Can't speak for any other skins.
>>>>
>>>> Gary
>>>> On Tuesday, 20 June 2023 at 07:04:56 UTC+1 hobbyl...@gmail.com wrote:
>>>>
>>>> here is me commands in terminal . trying to plus 12.1 missing mm  in 17
>>>> july  total rainfall
>>>>
>>>> metfm@metfm:~$ sudo sqlite3 /var/weewx/weewx.sdb
>>>> [sudo] password for metfm:
>>>> SQLite version 3.34.1 2021-01-20 14:10:07
>>>> Enter ".help" for usage hints.
>>>> sqlite> select datetime, datetime(dateTime, 'unixepoch','localtime'),
>>>> rain from archive where dateTime > 1686881600 and dateTime <= 1686981600
>>>>...> update archive set rain=12.6 where dateTime = 1686975900
>>>>...> .quit
>>>>...>
>>>> metfm@metfm:~$ sudo wee_database --rebuild-daily --from=2023-06-17
>>>> --to=2023-06-17
>>>> [sudo] password for metfm:
>>>> Using configuration file /etc/weewx/weewx.conf
>>>> Using database binding 'wx_binding', which is bound to database
>>>> 'archive_sqlite'
>>>> Daily summary for 2023-06-17 will be rebuilt.
>>>> Proceed (y/n)? y
>>>> Rebuilding daily summaries in database 'weewx.sdb' ...
>>>> Processed 276 records to rebuild 1 daily summary in 0.12 seconds
>>>> Rebuild of daily summaries in database 'weewx.sdb' complete
>>>> metfm@metfm:~$ sudo /etc/init.d/weewx start
>>>> Starting weewx (via systemctl): weewx.service.
>>>> metfm@metfm:~$
>>>>
>>>> something missing? something im doing wrong? the exetra mm never shows
>>>> in weewx restarting and updating.
>>>>
>>>>
>>>>
>>>> Στις Σάββατο 17 Ιουνίου 2023 στις 12:11:40 μ.μ. UTC+3, ο χρήστης
>>>> Stefanos Kalaitzis έγραψε:
>>>>
>>>> First find the range of time(epoch)  that you want to add the rain
>>>> Enter to weeex.sdb
>>>>
>>>> sudo sqlite3 /home/weewx/archive/weewx.sdb
>>>>
>>>> Then check what values your station recorded
>>>>
>>>>  select datetime, datetime(dateTime, 'unixepoch','localtime'), rain
>>>> from archive where dateTime > 1686881600 and dateTime <= 1686981600;
>>>>
>>>> Then correct the time you want
>>>> For example
>>>>
>>>> update archive set rain=1.0 where dateTime = 1686975900;
>>>>
>>>> Then exit the db
>>>>
>>>> .quit
>>>>
>>>> Stop weewx
>>>>
>>>> After all corrections rebuild the data base for that day
>>>>
>>>>
>>>> sudo /home/weewx/bin/wee_database --rebuild-daily --from=2023-06-17
>>>> --to=2023-06-17
>>>>
>>>> Start weewx
>>>>
>>>> Thats what i am doing when i have to add some missing mm in my db
>>>>
>>>>
>>>>
>>>> Στις Σάβ, 17 Ιουν 2023, 11:42 ο χρήστης Δημήτρης Βήχος <
>>>> hobbyl...@gmail.com> έγραψε:
>>>>
>>>> i want like to add some mm to my daily rainfall beacuse after power
>>>> loss , my console (fine offset)  have 10mm above the weewx after the power
>>>> on again.
>>>> i had loss 10mm in my daily rain.
>>>>
>>>> thank you!
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "weewx-user" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to weewx-user+...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/weewx-user/e96ce7e9-1085-46f6-adf4-b82275bf4df4n%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/weewx-user/e96ce7e9-1085-46f6-adf4-b82275bf4df4n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/88595a49-17a9-4e1f-9fc1-6d884f9f1863n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/88595a49-17a9-4e1f-9fc1-6d884f9f1863n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAERekb-WdE5z5QAY8F_mrS0uz-i6Tm43-xZkpDtyRtjBqWuSXw%40mail.gmail.com.

Re: [weewx-user] adding mm to daily rainfall

[Stefanos Kalaitzis]

First find the range of time(epoch)  that you want to add the rain
Enter to weeex.sdb

sudo sqlite3 /home/weewx/archive/weewx.sdb

Then check what values your station recorded

 select datetime, datetime(dateTime, 'unixepoch','localtime'), rain from
archive where dateTime > 1686881600 and dateTime <= 1686981600;

Then correct the time you want
For example

update archive set rain=1.0 where dateTime = 1686975900;

Then exit the db

.quit

Stop weewx

After all corrections rebuild the data base for that day


sudo /home/weewx/bin/wee_database --rebuild-daily --from=2023-06-17
--to=2023-06-17

Start weewx

Thats what i am doing when i have to add some missing mm in my db



Στις Σάβ, 17 Ιουν 2023, 11:42 ο χρήστης Δημήτρης Βήχος <
hobbyline...@gmail.com> έγραψε:

> i want like to add some mm to my daily rainfall beacuse after power loss ,
> my console (fine offset)  have 10mm above the weewx after the power on
> again.
> i had loss 10mm in my daily rain.
>
> thank you!
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/e96ce7e9-1085-46f6-adf4-b82275bf4df4n%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/CAERekb8DhKsq%2BmDywJ3rxqnJ0C1o8%3D1E4XSkpdAaB7WPO6hk_A%40mail.gmail.com.

Re: [weewx-user] Re: installing belchertown extension

[Stefanos Kalaitzis]

Also i think by default the belchertown skin its published in
public_html/Belchertown ... So if you want it to be your main page change
it to HTML_ROOT = public_html

Here is my configuration in weewx.conf
[[Belchertown]]
enable = true
log_success = False
log_failure = True
skin = Belchertown
HTML_ROOT = public_html

Στις Τετ, 16 Νοε 2022, 20:39 ο χρήστης vince  έγραψε:

> On Wednesday, November 16, 2022 at 9:57:59 AM UTC-8 vanuxe...@gmail.com
> wrote:
>
>> Did uninstall and instal a few times. And i always use sudo.
>>
>
> Download a new copy of the Belchertown skin and try installing that.
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/a21f0316-99a8-4263-9a1b-4eb7d21f602cn%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/CAERekb-UN7rFjdQCv8rZgHJ%2BsDRPu4SDtyuuGyUoc9u6q%2BJFoQ%40mail.gmail.com.

Re: [weewx-user] Re: installing belchertown extension

[Stefanos Kalaitzis]

Check weewx.conf to enable skin


enable = true

Στις Τετ, 16 Νοε 2022, 19:57 ο χρήστης Alex Vanuxem 
έγραψε:

> Did uninstall and instal a few times. And i always use sudo.
>
> Op wo 16 nov. 2022 18:55 schreef vince :
>
>> Just install it again and remember to use 'sudo'.  Sheesh.
>>
>> On Wednesday, November 16, 2022 at 9:34:17 AM UTC-8 vanuxe...@gmail.com
>> wrote:
>>
>>> Hi
>>>
>>> Thanks for your answer.
>>>
>>> Unfortunately nothing is there.
>>>
>>> The skins folder is also not updated to show belchertown.
>>>
>>> Please advise.
>>>
>>> Thx
>>>
>>> Alex
>>>
>>> Op di 15 nov. 2022 21:37 schreef vince :
>>>
 Look for Belchertown with an upper case 'B'.

 You should see a long stanza for Belchertown in the StdReport section
 of weewx.conf

 On Tuesday, November 15, 2022 at 11:30:05 AM UTC-8 vanuxe...@gmail.com
 wrote:

> Hi all,
>
> I installed the belchertown skin into the wee_extension.
>
> if i do a --list the belchertown is listed
>
> i have a setup.py install
>
> and running weewx under a virtual box environment.
>
> normally i guess the weewx.conf should be updated with this extension?
> but it's not ...
>
> do I miss something?
>
> thx
>
> grtz
>
> alex
>
 --
 You received this message because you are subscribed 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/af8576b1-2575-4117-b043-2cc7946e1e2cn%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/1d9b8920-cef8-4085-a9de-5395c54868cbn%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/CAHaYyoK9ATNG5YioqgRz_L2HkB6CxcTR7OPmY3cQJZN_25B5-Q%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAERekb8uyFLpaKtkrpBQf4O%3DKRdOF-k2jzgfjRM0ZAA%2BKCgBEw%40mail.gmail.com.

Re: [weewx-user] Weewx 4.7.0 & Weewx -WD

[Stefanos Kalaitzis]

Hi Gary , 

-- how you have configured the RealtimeClientraw service:
[[RealtimeClientraw]]
   rtcr_path = /home/weewx/public_html/WD
   min_interval = 12 (i have changed this now according to your 
instructions because is my loop period)
the other values are untouched 

-- how you have configured the Saratoga templates:
untouched too now  (ajaxWEEWXwx.js is the original and virgin :P from 
weewx-plugin.zip ) 

-- how are you transferring clientraw.txt to your web server? 
I use this address  
https://northmeteo.gr/weather_stations/tagarades/index.php to post the 
clientraw.txt through remote_server_url under  [[RealtimeClientraw]] 
section 
For the other address http://tagarades-weather.epizy.com/WD/index.php i use 
the ftp report (every archive interval -2,5min) . I was wondering if we can 
put another one   remote_server_url in weewx.conf as the example:

[WeewxSaratoga]

[[RealtimeClientraw]]

   remote_server_url = htttp://one.address.com/post_clientraw.php
   remote_server_url = htttp://second.address.com/post_clientraw.php

I am still having same values for wind speed and gust speed . Have you 
looked at the saratoga WEEWXwx 
 testing page . I noticed the 
same .Sometimes  only when you manually refresh the page probably you will 
see different values  . Ofcourse sometimes are the same indeed in low wind 
conditions.

Greetings from Greece 
Stefanos  
On Thursday, March 10, 2022 at 10:55:22 AM UTC+2 gjr80 wrote:

> Dale,
>
> I am not aware of any means of having WeeWX ingest data via clientraw.txt. 
> I wouldn't be writing off fileparse either, I've never used Weather Display 
> but if I was trying to do what want I would look at using Weather Display's 
> tag system to generate a custom document/report in a format that fileparse 
> can read. The custom document/report should be fairly compact as it only 
> need contain those observations that you wish WeeWX to record. By using 
> fileparse you avoid the need to write any python code and importantly you 
> keep things simple.
>
> Gary
>
> On Thursday, 10 March 2022 at 13:26:46 UTC+10 daleea...@gmail.com wrote:
>
>> Gary, 
>>
>> Pardon me for jumping in on this thread, butseeing Weather Display and 
>> clientraw.txt terms grabbed my attention. 
>>
>> I've read through this message, and it lead me to the WeeWx-WD (end of 
>> life) and the WeeWx-Saratoga portions, which I read, and partially 
>> understand. 
>>
>> My main goal is to find some station code for WeeWx which will take my 
>> WeatherDisplay clientraw file and allow it to drive WeeWx.  I looked at 
>> this a couple years ago and was given a lead to use fileparser, but that 
>> station base code requires a observation name followed by the value; as 
>> you know clientraw.txt is just a string of numbers, which is incredibly 
>> well analyzed in one of the files on Saratoga 
>> (https://saratoga-weather.org/wdparser.php). 
>>
>> As a clarification, you might ask why in the world if I'm running 
>> Weather Display, why would I want it to feed WeeWx?  First, with Weather 
>> Display Brian H. has implemented an amazing number of weather station 
>> interfaces which just plain work.  I have a passion for hardware, and 
>> have at least five stations feeding Weather  Display.  Therefore not 
>> only am I running Weather Display, but it is functioning as an interface 
>> to those stations. I could fiddle with my WeeWx installations and feed 
>> different ones from different stations, especially if there are not 
>> direct drivers native to WeeWx. All I'd need to do is have Weather 
>> Display output through  clientraw.txt, to my WeeWx Raspberry Pi 
>> configurations. 
>>
>> I love WeeWx, and am far from a programmer, but have followed the 
>> discussions and made some modifications to the basic code (all 
>> suggested, I'm not that smart to figure it out but I'm getting better) 
>> and also have selected to run the Belchertown as an output skin also. 
>>
>> So what I'm looking for and haven't apparently found it quite yet, is 
>> some station driver which will take the clientraw. txt and act like a 
>> LOOP feeder for WeeWx.  Fileparser requires a format that is far 
>> different from what WD outputs.  I haven't been able to produce 
>> functioning code which inserts the necessary value identifiers to make 
>> this work.  I see this thread and hope wells up, especially after 
>> looking at the Saratoga examples which seem to look into a URL, analyze 
>> the WeatherDisplay output, and produce such a file.  As far as I can 
>> determine, that whole thing was done just to make the Saratoga work. 
>>
>> Obviously I'm missing something, like why is WeeWx involved in the 
>> conversion at all?  I thought (although never set it up) that WD output 
>> can directly drive Saratoga but I could be all wet on that conclusion. 
>>
>>
>> The last question, straight out, is:  Is there a WeeWx station code that 
>> I can use to 

Re: [weewx-user] Weewx 4.7.0 & Weewx -WD

[Stefanos Kalaitzis]

r site.
>
> Gary
> On Wednesday, 9 March 2022 at 07:50:22 UTC+10 stefanos...@gmail.com wrote:
>
>> Hi Gary ...
>> Time of min-max temp ...ok ... It wasnt the clientraw as you said but i 
>> reinstall the weewx plugin for Sarratoga template and all good
>> Now i have also  max rain/rate value correct  but i dont know about 
>> rain/rate because it stop raining
>> Wind values are mystery I edited the ajaxweewx js file and i put [1] 
>> for avg_speed instead of [140] and [2] for gust_speed instead of [1]
>>
>>
>> On Tuesday, March 8, 2022 at 8:59:33 AM UTC+2 Stefanos Kalaitzis wrote:
>>
>>> Hi Gary ... Thanks !!
>>>
>>> Also Time of min-max temp still not updated 
>>>
>>> On Tuesday, March 8, 2022 at 12:31:21 AM UTC+2 gjr80 wrote:
>>>
>>>> > How do you find me...??
>>>> That was not too difficult, your user name sounded very Greek so I 
>>>> looked at the WeeWX user map <http://weewx.com/stations.html> and 
>>>> there are not that many stations in Greece. I knew you were using SDR and 
>>>> there are not that many SDR stations around. Finding clientraw.txt was the 
>>>> clincher.
>>>>
>>>> > 1. I cant change path of clientrraw.txt (always is saved to 
>>>> puplic_html and i want to public_html/WD) even if i edit the rtcr.py
>>>> I still need to finish off documenting the WeeWX-Saratoga options. You 
>>>> can change the location that clientraw.txt is saved using the 
>>>> rtcr_patth setting under [WeewxSaratoga] [[RealtimeClientraw]] in 
>>>> weewx.conf, eg:
>>>>
>>>> [WeewxSaratoga]
>>>> 
>>>> [[RealtimeClientraw]]
>>>> # Path to clientraw.txt. Can be an absolute or relative path. 
>>>> Relative
>>>> # paths are relative to HTML_ROOT. Optional, default setting is 
>>>> to use
>>>> # HTML_ROOT.
>>>> rtcr_path = /home/weewx/public_html 
>>>>
>>>> Until I finish documenting the options the best source of 
>>>> RealtimeClientraw (the service that WeeWX-Saratoga uses to generate 
>>>> clientraw.txt) is the comments at the top of rtcr.py. I don't 
>>>> recommend editing the rtcr.py code to force things, it is far to easy 
>>>> to break something else, it is a complex service.
>>>>
>>>> > 2. The dewpoint gets value 0 (i attached a screen shot  when i made 
>>>> again the upgrade)
>>>> I have a suspicion this could be related to the gaps I saw in some of 
>>>> your plots, depending on your system dewpoint may be a calculated 
>>>> value and if any of the prerequisites for its calculation are missing it 
>>>> will not be calculated and clientraw.txt will then display it as 0.0.
>>>>
>>>> > 3. When i made a split with python to clientraw.txt to data[174] for 
>>>> example i get 0 value
>>>> It is possible there could be some corner cases that are causing a 
>>>> field to be omitted when clientraw.txt is generated, I would like to think 
>>>> I have hardened the code to prevent this but it is possible. If one field 
>>>> is omitted that shuffles every later field along and they become out of 
>>>> place. If you use a clientraw.txt parser like the one at Saratoga 
>>>> Weather <https://saratoga-weather.org/wdparser.php> it is usually 
>>>> pretty obvious where the omission is. We can work through this one now 
>>>> that 
>>>> you have installed v4.5.1 and WeeWX-Saratoga.
>>>>
>>>> > 4. Sometimes not always the avg_speed gets bigger values than the 
>>>> gust_speed.
>>>> This should not happen, again can work through.
>>>>
>>>> > Probably when you saw my clientraw.txt that is correct was from the 
>>>> weewx-wd and not from Saratoga
>>>> No, was definitely from WeeWX-Saratoga, if you look at the end of the 
>>>> file you will see something like:
>>>>
>>>> 102.9 16:37 06:52 68 !!WS0.3.3!!
>>>>
>>>> The 'WS0.3.3' indicates WeeWX-Saratoga v0.3.3, WeatherDisplay and 
>>>> WeeWX-WD generated clientraw.txt files terminate differently.
>>>>
>>>> > Now that it is raining , i noticed that rain rate and max rain rate 
>>>> have 0.0 value
>>>> OK. I will work through this and the other issues you have raised.
>>>>
>>&

Re: [weewx-user] Weewx 4.7.0 & Weewx -WD

[Stefanos Kalaitzis]

Hi Gary ...
Time of min-max temp ...ok ... It wasnt the clientraw as you said but i 
reinstall the weewx plugin for Sarratoga template and all good
Now i have also  max rain/rate value correct  but i dont know about 
rain/rate because it stop raining
Wind values are mystery I edited the ajaxweewx js file and i put [1] 
for avg_speed instead of [140] and [2] for gust_speed instead of [1]


On Tuesday, March 8, 2022 at 8:59:33 AM UTC+2 Stefanos Kalaitzis wrote:

> Hi Gary ... Thanks !!
>
> Also Time of min-max temp still not updated 
>
> On Tuesday, March 8, 2022 at 12:31:21 AM UTC+2 gjr80 wrote:
>
>> > How do you find me...??
>> That was not too difficult, your user name sounded very Greek so I looked 
>> at the WeeWX user map <http://weewx.com/stations.html> and there are not 
>> that many stations in Greece. I knew you were using SDR and there are not 
>> that many SDR stations around. Finding clientraw.txt was the clincher.
>>
>> > 1. I cant change path of clientrraw.txt (always is saved to puplic_html 
>> and i want to public_html/WD) even if i edit the rtcr.py
>> I still need to finish off documenting the WeeWX-Saratoga options. You 
>> can change the location that clientraw.txt is saved using the rtcr_patth 
>> setting under [WeewxSaratoga] [[RealtimeClientraw]] in weewx.conf, eg:
>>
>> [WeewxSaratoga]
>> 
>> [[RealtimeClientraw]]
>> # Path to clientraw.txt. Can be an absolute or relative path. 
>> Relative
>> # paths are relative to HTML_ROOT. Optional, default setting is 
>> to use
>> # HTML_ROOT.
>> rtcr_path = /home/weewx/public_html 
>>
>> Until I finish documenting the options the best source of 
>> RealtimeClientraw (the service that WeeWX-Saratoga uses to generate 
>> clientraw.txt) is the comments at the top of rtcr.py. I don't recommend 
>> editing the rtcr.py code to force things, it is far to easy to break 
>> something else, it is a complex service.
>>
>> > 2. The dewpoint gets value 0 (i attached a screen shot  when i made 
>> again the upgrade)
>> I have a suspicion this could be related to the gaps I saw in some of 
>> your plots, depending on your system dewpoint may be a calculated value 
>> and if any of the prerequisites for its calculation are missing it will not 
>> be calculated and clientraw.txt will then display it as 0.0.
>>
>> > 3. When i made a split with python to clientraw.txt to data[174] for 
>> example i get 0 value
>> It is possible there could be some corner cases that are causing a field 
>> to be omitted when clientraw.txt is generated, I would like to think I have 
>> hardened the code to prevent this but it is possible. If one field is 
>> omitted that shuffles every later field along and they become out of place. 
>> If you use a clientraw.txt parser like the one at Saratoga Weather 
>> <https://saratoga-weather.org/wdparser.php> it is usually pretty obvious 
>> where the omission is. We can work through this one now that you have 
>> installed v4.5.1 and WeeWX-Saratoga.
>>
>> > 4. Sometimes not always the avg_speed gets bigger values than the 
>> gust_speed.
>> This should not happen, again can work through.
>>
>> > Probably when you saw my clientraw.txt that is correct was from the 
>> weewx-wd and not from Saratoga
>> No, was definitely from WeeWX-Saratoga, if you look at the end of the 
>> file you will see something like:
>>
>> 102.9 16:37 06:52 68 !!WS0.3.3!!
>>
>> The 'WS0.3.3' indicates WeeWX-Saratoga v0.3.3, WeatherDisplay and 
>> WeeWX-WD generated clientraw.txt files terminate differently.
>>
>> > Now that it is raining , i noticed that rain rate and max rain rate 
>> have 0.0 value
>> OK. I will work through this and the other issues you have raised.
>>
>> > That's all for now. :p ..I hope that i didnt inconvenience you
>> Not at all, it's can be difficult to write something like 
>> RealtimeClientraw and cover all the corner cases so you have to rely on 
>> people finding bugs.
>>
>> 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/00c8de57-6e88-4f9c-97a9-7b5b1c991e3en%40googlegroups.com.

Re: [weewx-user] Weewx 4.7.0 & Weewx -WD

[Stefanos Kalaitzis]

Hi Gary ... Thanks !!

Also Time of min-max temp still not updated 

On Tuesday, March 8, 2022 at 12:31:21 AM UTC+2 gjr80 wrote:

> > How do you find me...??
> That was not too difficult, your user name sounded very Greek so I looked 
> at the WeeWX user map  and there are not 
> that many stations in Greece. I knew you were using SDR and there are not 
> that many SDR stations around. Finding clientraw.txt was the clincher.
>
> > 1. I cant change path of clientrraw.txt (always is saved to puplic_html 
> and i want to public_html/WD) even if i edit the rtcr.py
> I still need to finish off documenting the WeeWX-Saratoga options. You can 
> change the location that clientraw.txt is saved using the rtcr_patth 
> setting under [WeewxSaratoga] [[RealtimeClientraw]] in weewx.conf, eg:
>
> [WeewxSaratoga]
> 
> [[RealtimeClientraw]]
> # Path to clientraw.txt. Can be an absolute or relative path. 
> Relative
> # paths are relative to HTML_ROOT. Optional, default setting is to 
> use
> # HTML_ROOT.
> rtcr_path = /home/weewx/public_html 
>
> Until I finish documenting the options the best source of 
> RealtimeClientraw (the service that WeeWX-Saratoga uses to generate 
> clientraw.txt) is the comments at the top of rtcr.py. I don't recommend 
> editing the rtcr.py code to force things, it is far to easy to break 
> something else, it is a complex service.
>
> > 2. The dewpoint gets value 0 (i attached a screen shot  when i made 
> again the upgrade)
> I have a suspicion this could be related to the gaps I saw in some of your 
> plots, depending on your system dewpoint may be a calculated value and if 
> any of the prerequisites for its calculation are missing it will not be 
> calculated and clientraw.txt will then display it as 0.0.
>
> > 3. When i made a split with python to clientraw.txt to data[174] for 
> example i get 0 value
> It is possible there could be some corner cases that are causing a field 
> to be omitted when clientraw.txt is generated, I would like to think I have 
> hardened the code to prevent this but it is possible. If one field is 
> omitted that shuffles every later field along and they become out of place. 
> If you use a clientraw.txt parser like the one at Saratoga Weather 
>  it is usually pretty obvious 
> where the omission is. We can work through this one now that you have 
> installed v4.5.1 and WeeWX-Saratoga.
>
> > 4. Sometimes not always the avg_speed gets bigger values than the 
> gust_speed.
> This should not happen, again can work through.
>
> > Probably when you saw my clientraw.txt that is correct was from the 
> weewx-wd and not from Saratoga
> No, was definitely from WeeWX-Saratoga, if you look at the end of the file 
> you will see something like:
>
> 102.9 16:37 06:52 68 !!WS0.3.3!!
>
> The 'WS0.3.3' indicates WeeWX-Saratoga v0.3.3, WeatherDisplay and 
> WeeWX-WD generated clientraw.txt files terminate differently.
>
> > Now that it is raining , i noticed that rain rate and max rain rate have 
> 0.0 value
> OK. I will work through this and the other issues you have raised.
>
> > That's all for now. :p ..I hope that i didnt inconvenience you
> Not at all, it's can be difficult to write something like 
> RealtimeClientraw and cover all the corner cases so you have to rely on 
> people finding bugs.
>
> 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/88e288c1-a0c3-4011-a268-c7809f292a3an%40googlegroups.com.

Re: [weewx-user] Weewx 4.7.0 & Weewx -WD

[Stefanos Kalaitzis]

Now that it is raining , i noticed that rain rate and max rain rate have 
0.0 value

That's all for now. :p ..I hope that i didnt inconvenience you 

On Monday, March 7, 2022 at 9:54:38 PM UTC+2 Stefanos Kalaitzis wrote:

> On Monday, March 7, 2022 at 9:47:43 PM UTC+2 Stefanos Kalaitzis wrote:
>
>> Hi Gary...I did what you said... 
>>
>> 1. I upgraded from 4.2.0 to 4.5.1 with weewx-wd plugin (everything fine)
>> 2. I uninstalled the weewx-wd and installed the saratoga (seems that the 
>> dew point is correct now and i will leave it to see if the time of max-min 
>> temp are updated )
>> Issues that are remaining are
>> 1. the avg_speed gets higher values than the gust_speed *sometimes* (Its 
>> ok for me )
>> 2. path of clientraraw.txt -  always is saved to public_html  (i send 
>> clientraw files with a second ftp report so i want to have them in 
>> public_html/WD folder) (Its ok - i made a python script to send 
>> clientraw.txt alone)
>>
>> You can check now better and let me know if i miss something
>> Thanks again for your support
>>
>> On Monday, March 7, 2022 at 7:39:33 PM UTC+2 Stefanos Kalaitzis wrote:
>>
>>> Also i didnt mentioned that the issue is maybe the correspondence with 
>>> the template fields and not the client raw file itself
>>>
>>>
>>> On Monday, March 7, 2022 at 11:25:17 AM UTC+2 Stefanos Kalaitzis wrote:
>>>
>>>> Hi Gary... I am imprsessed How do you find me...?? :p 
>>>> Yes thats my site (https://tagarades-weather.epizy.com/WD) but i made 
>>>> it to test things before i upload my data to a weather provider 
>>>> https://northmeteo.gr/weather_stations/tagarades/index.php?lang=en . 
>>>> For the main site i am using the belchertown skin ( is without the /WD).  
>>>> I 
>>>> am using now the 4.2.0 version with weewx-wd but i kept the clientraw file 
>>>> of weewx saratoga... 
>>>> Few things that i noticed in weewx -saratoga ...
>>>> 1. I cant change path of clientraraw.txt (always is saved to 
>>>> puplic_html and i want to public_html/WD) even if i edit the rtcr.py
>>>> 2. The dewpoint gets value 0 (i attached a screen shot  when i made 
>>>> again the upgrade)
>>>> 3. When i made a split with python to clinentraw.txt to data[174] for 
>>>> example i get 0 value
>>>> 4. Sometimes not always the avg_speed gets bigger values than the 
>>>> gust_speed.
>>>>
>>>> Probably when you saw my clientraw.txt that is correct was from the 
>>>> weewx-wd and not from Saratoga
>>>>
>>>> Anyway , thank you for your time and for your support 
>>>> Maybe i did something wrong but i didnt touch anything when i upgrade 
>>>> to 4.7.0 . I use the sdr driver . After i saw the incorrect values i tried 
>>>> to change the time format (only that)
>>>>
>>>> p.s the saratoga clientraw was from yesterday (compared with the -wd i 
>>>> see that after station location have different values, those with solar 
>>>> radiation percent i think)
>>>>
>>>>  
>>>>
>>>>
>>>> On Monday, March 7, 2022 at 5:02:26 AM UTC+2 gjr80 wrote:
>>>>
>>>>> I did some debugging of the WeeWX-Saratoga service that generates 
>>>>> clientraw.txt. My test environment running the simulator shows the 
>>>>> WeeWX-Saratoga clientraw.txt service is working correctly. The outTemp 
>>>>> loop cache was being correctly seeded from the daily summaries at startup 
>>>>> and max/min and associated time correctly updated on arrival of loop 
>>>>> packets. dewpoint was also being correctly calculated. I also took 
>>>>> another look at my live site and day max/min outTemp and associated 
>>>>> times are correct; I suspect I was looking at old data this morning.
>>>>>
>>>>> I am guessing this is your site -  https://tagarades-weather.epizy.com 
>>>>> ? I found a WeeWX-Saratoga generated clientraw.txt at this address - 
>>>>> https://tagarades-weather.epizy.com/clientraw.txt - the timestamp is 
>>>>> 1825 on 6 March. Unfortunately your site graphs have moved on to 7 March 
>>>>> so 
>>>>> I cannot correlate the day max/min temps and times as they would have 
>>>>> been 
>>>>> at 1825 on 6 March. However, your NOAA format reports indicate the 
>>>>> maximum 
>>>>> temp

Re: [weewx-user] Weewx 4.7.0 & Weewx -WD

[Stefanos Kalaitzis]

On Monday, March 7, 2022 at 9:47:43 PM UTC+2 Stefanos Kalaitzis wrote:

> Hi Gary...I did what you said... 
>
> 1. I upgraded from 4.2.0 to 4.5.1 with weewx-wd plugin (everything fine)
> 2. I uninstalled the weewx-wd and installed the saratoga (seems that the 
> dew point is correct now and i will leave it to see if the time of max-min 
> temp are updated )
> Issues that are remaining are
> 1. the avg_speed gets higher values than the gust_speed *sometimes* (Its 
> ok for me )
> 2. path of clientraraw.txt -  always is saved to public_html  (i send 
> clientraw files with a second ftp report so i want to have them in 
> public_html/WD folder) (Its ok - i made a python script to send 
> clientraw.txt alone)
>
> You can check now better and let me know if i miss something
> Thanks again for your support
>
> On Monday, March 7, 2022 at 7:39:33 PM UTC+2 Stefanos Kalaitzis wrote:
>
>> Also i didnt mentioned that the issue is maybe the correspondence with 
>> the template fields and not the client raw file itself
>>
>>
>> On Monday, March 7, 2022 at 11:25:17 AM UTC+2 Stefanos Kalaitzis wrote:
>>
>>> Hi Gary... I am imprsessed How do you find me...?? :p 
>>> Yes thats my site (https://tagarades-weather.epizy.com/WD) but i made 
>>> it to test things before i upload my data to a weather provider 
>>> https://northmeteo.gr/weather_stations/tagarades/index.php?lang=en . 
>>> For the main site i am using the belchertown skin ( is without the /WD).  I 
>>> am using now the 4.2.0 version with weewx-wd but i kept the clientraw file 
>>> of weewx saratoga... 
>>> Few things that i noticed in weewx -saratoga ...
>>> 1. I cant change path of clientraraw.txt (always is saved to puplic_html 
>>> and i want to public_html/WD) even if i edit the rtcr.py
>>> 2. The dewpoint gets value 0 (i attached a screen shot  when i made 
>>> again the upgrade)
>>> 3. When i made a split with python to clinentraw.txt to data[174] for 
>>> example i get 0 value
>>> 4. Sometimes not always the avg_speed gets bigger values than the 
>>> gust_speed.
>>>
>>> Probably when you saw my clientraw.txt that is correct was from the 
>>> weewx-wd and not from Saratoga
>>>
>>> Anyway , thank you for your time and for your support 
>>> Maybe i did something wrong but i didnt touch anything when i upgrade to 
>>> 4.7.0 . I use the sdr driver . After i saw the incorrect values i tried to 
>>> change the time format (only that)
>>>
>>> p.s the saratoga clientraw was from yesterday (compared with the -wd i 
>>> see that after station location have different values, those with solar 
>>> radiation percent i think)
>>>
>>>  
>>>
>>>
>>> On Monday, March 7, 2022 at 5:02:26 AM UTC+2 gjr80 wrote:
>>>
>>>> I did some debugging of the WeeWX-Saratoga service that generates 
>>>> clientraw.txt. My test environment running the simulator shows the 
>>>> WeeWX-Saratoga clientraw.txt service is working correctly. The outTemp 
>>>> loop cache was being correctly seeded from the daily summaries at startup 
>>>> and max/min and associated time correctly updated on arrival of loop 
>>>> packets. dewpoint was also being correctly calculated. I also took 
>>>> another look at my live site and day max/min outTemp and associated 
>>>> times are correct; I suspect I was looking at old data this morning.
>>>>
>>>> I am guessing this is your site -  https://tagarades-weather.epizy.com 
>>>> ? I found a WeeWX-Saratoga generated clientraw.txt at this address - 
>>>> https://tagarades-weather.epizy.com/clientraw.txt - the timestamp is 
>>>> 1825 on 6 March. Unfortunately your site graphs have moved on to 7 March 
>>>> so 
>>>> I cannot correlate the day max/min temps and times as they would have been 
>>>> at 1825 on 6 March. However, your NOAA format reports indicate the maximum 
>>>> temperature on 6 March was 8.5C at 1637 - this agrees with the data in 
>>>> clientraw.txt (fields 46 and 174 respectively). According to the NOAA 
>>>> reports the day min outTemp occurred after 1825 so the NOAA format 
>>>> report data cannot be used to verify the clientraw.txt min outTemp and 
>>>> time as it would have been at 1825. Looking at your weekly plot though I 
>>>> see a minimum outTemp before 1825 of 5.5C at 0737 and 0837. The 1825 
>>>> clientraw.txt has minimum outTemp of 5.2 at 0652. Given the weekly 
>>>> p

Re: [weewx-user] Weewx 4.7.0 & Weewx -WD

[Stefanos Kalaitzis]

Hi Gary...I did what you said... 

1. I upgraded from 4.2.0 to 4.5.1 with weewx-wd plugin (everything fine)
2. I uninstalled the weewx-wd and installed the saratoga (seems that the 
dew point is correct now and i will leave it to see if the time of max-min 
temp are updated )
Issues that are remaining are
1. the avg_speed gets higher values than the gust_speed *sometimes* (Its ok 
for me )
2. path of clientraraw.txt -  always is saved to public_html  (i send 
clientraw files with a second ftp report so i want to have them in 
public_html/WD folder) (Its ok - i made a python script to send 
clientraw.txt alone)

You can check now better and let me know if i miss something
Thanks again for your support

On Monday, March 7, 2022 at 7:39:33 PM UTC+2 Stefanos Kalaitzis wrote:

> Also i didnt mentioned that the issue is maybe the correspondence with the 
> template fields and not the client raw file itself
>
>
> On Monday, March 7, 2022 at 11:25:17 AM UTC+2 Stefanos Kalaitzis wrote:
>
>> Hi Gary... I am imprsessed How do you find me...?? :p 
>> Yes thats my site (https://tagarades-weather.epizy.com/WD) but i made it 
>> to test things before i upload my data to a weather provider 
>> https://northmeteo.gr/weather_stations/tagarades/index.php?lang=en . For 
>> the main site i am using the belchertown skin ( is without the /WD).  I am 
>> using now the 4.2.0 version with weewx-wd but i kept the clientraw file of 
>> weewx saratoga... 
>> Few things that i noticed in weewx -saratoga ...
>> 1. I cant change path of clientraraw.txt (always is saved to puplic_html 
>> and i want to public_html/WD) even if i edit the rtcr.py
>> 2. The dewpoint gets value 0 (i attached a screen shot  when i made again 
>> the upgrade)
>> 3. When i made a split with python to clinentraw.txt to data[174] for 
>> example i get 0 value
>> 4. Sometimes not always the avg_speed gets bigger values than the 
>> gust_speed.
>>
>> Probably when you saw my clientraw.txt that is correct was from the 
>> weewx-wd and not from Saratoga
>>
>> Anyway , thank you for your time and for your support 
>> Maybe i did something wrong but i didnt touch anything when i upgrade to 
>> 4.7.0 . I use the sdr driver . After i saw the incorrect values i tried to 
>> change the time format (only that)
>>
>> p.s the saratoga clientraw was from yesterday (compared with the -wd i 
>> see that after station location have different values, those with solar 
>> radiation percent i think)
>>
>>  
>>
>>
>> On Monday, March 7, 2022 at 5:02:26 AM UTC+2 gjr80 wrote:
>>
>>> I did some debugging of the WeeWX-Saratoga service that generates 
>>> clientraw.txt. My test environment running the simulator shows the 
>>> WeeWX-Saratoga clientraw.txt service is working correctly. The outTemp 
>>> loop cache was being correctly seeded from the daily summaries at startup 
>>> and max/min and associated time correctly updated on arrival of loop 
>>> packets. dewpoint was also being correctly calculated. I also took 
>>> another look at my live site and day max/min outTemp and associated 
>>> times are correct; I suspect I was looking at old data this morning.
>>>
>>> I am guessing this is your site -  https://tagarades-weather.epizy.com 
>>> ? I found a WeeWX-Saratoga generated clientraw.txt at this address - 
>>> https://tagarades-weather.epizy.com/clientraw.txt - the timestamp is 
>>> 1825 on 6 March. Unfortunately your site graphs have moved on to 7 March so 
>>> I cannot correlate the day max/min temps and times as they would have been 
>>> at 1825 on 6 March. However, your NOAA format reports indicate the maximum 
>>> temperature on 6 March was 8.5C at 1637 - this agrees with the data in 
>>> clientraw.txt (fields 46 and 174 respectively). According to the NOAA 
>>> reports the day min outTemp occurred after 1825 so the NOAA format 
>>> report data cannot be used to verify the clientraw.txt min outTemp and 
>>> time as it would have been at 1825. Looking at your weekly plot though I 
>>> see a minimum outTemp before 1825 of 5.5C at 0737 and 0837. The 1825 
>>> clientraw.txt has minimum outTemp of 5.2 at 0652. Given the weekly plot 
>>> only shows data points every hour we can't really draw any conclusion from 
>>> this other than the clientraw.txt min outTemp is not obviously wrong. 
>>> dewpoint in the 1825 clientraw.txt is 0.0 and looking at your week plot 
>>> you had not dewpoint data from (around) 1537 to 1837, the WeeWX-Saratoga 
>>> clientraw.txt service substitutes 0.0 if a temperature based 
>>> obs

Re: [weewx-user] Weewx 4.7.0 & Weewx -WD

[Stefanos Kalaitzis]

Also i didnt mentioned that the issue is maybe the correspondence with the 
template fields and not the client raw file itself


On Monday, March 7, 2022 at 11:25:17 AM UTC+2 Stefanos Kalaitzis wrote:

> Hi Gary... I am imprsessed How do you find me...?? :p 
> Yes thats my site (https://tagarades-weather.epizy.com/WD) but i made it 
> to test things before i upload my data to a weather provider 
> https://northmeteo.gr/weather_stations/tagarades/index.php?lang=en . For 
> the main site i am using the belchertown skin ( is without the /WD).  I am 
> using now the 4.2.0 version with weewx-wd but i kept the clientraw file of 
> weewx saratoga... 
> Few things that i noticed in weewx -saratoga ...
> 1. I cant change path of clientraraw.txt (always is saved to puplic_html 
> and i want to public_html/WD) even if i edit the rtcr.py
> 2. The dewpoint gets value 0 (i attached a screen shot  when i made again 
> the upgrade)
> 3. When i made a split with python to clinentraw.txt to data[174] for 
> example i get 0 value
> 4. Sometimes not always the avg_speed gets bigger values than the 
> gust_speed.
>
> Probably when you saw my clientraw.txt that is correct was from the 
> weewx-wd and not from Saratoga
>
> Anyway , thank you for your time and for your support 
> Maybe i did something wrong but i didnt touch anything when i upgrade to 
> 4.7.0 . I use the sdr driver . After i saw the incorrect values i tried to 
> change the time format (only that)
>
> p.s the saratoga clientraw was from yesterday (compared with the -wd i see 
> that after station location have different values, those with solar 
> radiation percent i think)
>
>  
>
>
> On Monday, March 7, 2022 at 5:02:26 AM UTC+2 gjr80 wrote:
>
>> I did some debugging of the WeeWX-Saratoga service that generates 
>> clientraw.txt. My test environment running the simulator shows the 
>> WeeWX-Saratoga clientraw.txt service is working correctly. The outTemp 
>> loop cache was being correctly seeded from the daily summaries at startup 
>> and max/min and associated time correctly updated on arrival of loop 
>> packets. dewpoint was also being correctly calculated. I also took 
>> another look at my live site and day max/min outTemp and associated 
>> times are correct; I suspect I was looking at old data this morning.
>>
>> I am guessing this is your site -  https://tagarades-weather.epizy.com ? 
>> I found a WeeWX-Saratoga generated clientraw.txt at this address - 
>> https://tagarades-weather.epizy.com/clientraw.txt - the timestamp is 
>> 1825 on 6 March. Unfortunately your site graphs have moved on to 7 March so 
>> I cannot correlate the day max/min temps and times as they would have been 
>> at 1825 on 6 March. However, your NOAA format reports indicate the maximum 
>> temperature on 6 March was 8.5C at 1637 - this agrees with the data in 
>> clientraw.txt (fields 46 and 174 respectively). According to the NOAA 
>> reports the day min outTemp occurred after 1825 so the NOAA format 
>> report data cannot be used to verify the clientraw.txt min outTemp and 
>> time as it would have been at 1825. Looking at your weekly plot though I 
>> see a minimum outTemp before 1825 of 5.5C at 0737 and 0837. The 1825 
>> clientraw.txt has minimum outTemp of 5.2 at 0652. Given the weekly plot 
>> only shows data points every hour we can't really draw any conclusion from 
>> this other than the clientraw.txt min outTemp is not obviously wrong. 
>> dewpoint in the 1825 clientraw.txt is 0.0 and looking at your week plot 
>> you had not dewpoint data from (around) 1537 to 1837, the WeeWX-Saratoga 
>> clientraw.txt service substitutes 0.0 if a temperature based observation 
>> does not exist (it must output something otherwise the clientraw.txt 
>> format will be corrupted) so it is quite possible the clientraw.txt 
>> dewpoint value of 0.0 was the expected result at the time.
>>
>> The upshot of this analysis of your site is that I cannot find any 
>> obvious issues with the clientraw.txt data. One thing you may consider 
>> doing is upgrade to WeeWX v4.5.1. This would allow WeeWX-WD to continue to 
>> operate without error (it is changes introduced in v4.6.0 that breaks 
>> WeeWX-WD) and it would also allow you to re-install WeeWX-Saratoga (it 
>> requires v4.5.0 or later) to allow proper troubleshooting of the 
>> clientraw.txt issue.
>>
>> Gary
>>
>> On Monday, 7 March 2022 at 07:48:44 UTC+10 gjr80 wrote:
>>
>>> clientraw.txt is indeed a fixed format, space delimited file that 
>>> should have the same observation/stat in the same location irrespective of 
>>> source. If dewpoint and ti

Re: [weewx-user] Weewx 4.7.0 & Weewx -WD

[Stefanos Kalaitzis]

Thanks Tom... Weewx -wd doesnt run in 4.7.0 ... I checked all the necessary 
conf files and the result is the same .
Also tried the weewx -saratoga  that runs without problem but the 
clientraw.txt that generated is a little bit different than the weewx-wd as 
a result the saratoga template gets different values in the appropriate 
fields and i have to modify the dashboard script file and i dont have much 
time :p
I thought that clientraw gets standard values in standard place 
Example
Temp, wind ,baro, and rain are correct but dew point is wrong and time of 
max-min temp is not updated

I can live with the 4.2.0 ... :)

On Saturday, March 5, 2022 at 9:57:59 PM UTC+2 tke...@gmail.com wrote:

> See if this thread helps: 
> https://groups.google.com/g/weewx-user/c/rnLNpNoX0U0/m/stFp0t_MEAAJ
>
> On Sat, Mar 5, 2022 at 8:41 AM Stefanos Kalaitzis  
> wrote:
>
>> Hi everyone...I am running weewx with sdr driver  I decided to update 
>> from weewx 4.2.0 to 4.7.0 and i have several errors in Clientraw skinIt 
>> doesnt generate the clientraw.txt but all the others clientrawhour,-daily - 
>> extra are generated.In the 4.2.0 version evrything was flawless .I also 
>> made a clean install of weewx 4.7.0 and the errors are the same ... I kept 
>> the log from 4.7.0 and i downgraded again to the old version. If someone 
>> knows whats going on i would appreciate it.
>>  I didnt make any change to weewx.conf after the update .
>>
>> Thank you in advanced 
>>
>> -- 
>> You received this message because you are subscribed 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/b200d823-4ee6-4e64-8164-b531a227d54bn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/b200d823-4ee6-4e64-8164-b531a227d54bn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e94f614b-75d6-48ce-bc14-91c13ad6de2fn%40googlegroups.com.

[weewx-user] Weewx 4.7.0 & Weewx -WD

[Stefanos Kalaitzis]

Hi everyone...I am running weewx with sdr driver  I decided to update from 
weewx 4.2.0 to 4.7.0 and i have several errors in Clientraw skinIt 
doesnt generate the clientraw.txt but all the others clientrawhour,-daily - 
extra are generated.In the 4.2.0 version evrything was flawless .I also 
made a clean install of weewx 4.7.0 and the errors are the same ... I kept 
the log from 4.7.0 and i downgraded again to the old version. If someone 
knows whats going on i would appreciate it.
 I didnt make any change to weewx.conf after the update .

Thank you in advanced 

-- 
You received this message because you are subscribed 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/b200d823-4ee6-4e64-8164-b531a227d54bn%40googlegroups.com.
Mar  5 16:47:58 raspberrypi weewx[685] INFO weewx.restx: AWEKAS: Published 
record 2022-03-05 16:47:30 EET (1646491650)
Mar  5 16:47:58 raspberrypi weewx[685] INFO user.belchertown: version 1.2
Mar  5 16:47:58 raspberrypi weewx[685] INFO weewx.restx: StationRegistry: 
Published record 2022-03-05 16:47:30 EET (1646491650)
Mar  5 16:48:00 raspberrypi weewx[685] INFO user.belchertown: New forecast file 
downloaded to /home/weewx/public_html/json/forecast.json
Mar  5 16:48:15 raspberrypi weewx[685] INFO weewx.cheetahgenerator: Generated 
39 files for report Belchertown in 17.63 seconds
Mar  5 16:48:15 raspberrypi weewx[685] INFO weewx.reportengine: Copied 37 files 
to /home/weewx/public_html
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: Evaluation 
of template /home/weewx/skins/Testtags/testtags.php.tmpl failed with exception 
''
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:  
Ignoring template /home/weewx/skins/Testtags/testtags.php.tmpl
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:  
Reason: 'trend'
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
Traceback (most recent call last):
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: 
File "/home/weewx/bin/weewx/cheetahgenerator.py", line 348, in generate
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
unicode_string = compiled_template.respond()
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: 
File "_home_weewx_skins_Testtags_testtags_php_tmpl.py", line 1062, in respond
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: 
File "/home/weewx/bin/weewx/tags.py", line 65, in trend
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
time_grace = to_int(self.option_dict['trend'].get('time_grace', 300))
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
KeyError: 'trend'
Mar  5 16:48:20 raspberrypi weewx[685] INFO weewx.cheetahgenerator: Generated 0 
files for report wdTesttags in 3.23 seconds
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: Evaluation 
of template /home/weewx/skins/Clientraw/clientraw.txt.tmpl failed with 
exception ''
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:  
Ignoring template /home/weewx/skins/Clientraw/clientraw.txt.tmpl
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:  
Reason: 'trend'
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
Traceback (most recent call last):
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: 
File "/home/weewx/bin/weewx/cheetahgenerator.py", line 348, in generate
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
unicode_string = compiled_template.respond()
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: 
File "_home_weewx_skins_Clientraw_clientraw_txt_tmpl.py", line 330, in respond
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: 
File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1458, in 
varExists
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
varName.replace('$', ''), autoCall)
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: 
File "/home/weewx/bin/weewx/tags.py", line 63, in trend
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
time_delta = to_int(self.option_dict['trend'].get('time_delta', 10800))
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
KeyError: 'trend'
Mar  5 16:48:20 raspberrypi weewx[685] INFO weewx.cheetahgenerator: Generated 0 
files for report wdClientraw in 0.50 seconds

[weewx-user] Re: SDR and Backfill

[Stefanos Kalaitzis]

Thank you gjr80... Ups was my plan B ... I think if the power outage 
extends to the next day probably the amount of rain will passed to the next 
day too ... You will have one wrong saved record but your total will be 
correct... Anyway i thought that will be easier to do this but as you said 
other approach is going to be messy

On Saturday, January 15, 2022 at 12:16:31 AM UTC+2 gjr80 wrote:

> My vote is put the necessary equipment on UPS. Any other approach is going 
> to be messy to handle no matter how you do it, what do you do if the power 
> outage extends over a midnight boundary? How do you apportion rainfall 
> across the outage period? 
>
> Gary
> On Saturday, 15 January 2022 at 05:00:06 UTC+10 vince wrote:
>
>> (following up for others who might help)
>>
>> Stefanos told me via email that his rain sensor reports a rain_total 
>> value that continually increments, so what he's looking to do is reflect 
>> whatever the sensor detected during a power outage and have an accurate 
>> total rain for the day.
>>
>> The example he gave was:
>>
>>- assume the total_rain counter started at 0 mm
>>- day-one 20mm of rain falls.  The sensor reports total rain = 20mm
>>- day-two 5mm of rain falls but there was a power outage while the 
>>rain was falling
>>- when the power goes back on SDR reads the sensor's new reading 
>>which correctly shows 25mm accumulated in total over all days
>>- so what he's looking for (I think) is how to set weewx up so 
>>day-two's rain shows 5mm (new total of 25 - old total of 20)
>>
>> Hope this helps.
>>
>> (Stefanos please correct me if I interpreted your email wrong)
>>
>>

-- 
You received this message because you are subscribed 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/f192faaa-e788-4a98-9da3-a56916f8d47an%40googlegroups.com.

[weewx-user] Re: SDR and Backfill

[Stefanos Kalaitzis]

Perfect Vince  Thank you for your translation :-) ... That's exactly 
what i am trying to achieve 

''so what he's looking for (I think) is how to set weewx up so day-two's 
rain shows 5mm (new total of 25 - old total of 20)'' and not 0mm because of 
lost connection even if a power off or a system failure happens  .
On Friday, January 14, 2022 at 9:00:06 PM UTC+2 vince wrote:

> (following up for others who might help)
>
> Stefanos told me via email that his rain sensor reports a rain_total value 
> that continually increments, so what he's looking to do is reflect whatever 
> the sensor detected during a power outage and have an accurate total rain 
> for the day.
>
> The example he gave was:
>
>- assume the total_rain counter started at 0 mm
>- day-one 20mm of rain falls.  The sensor reports total rain = 20mm
>- day-two 5mm of rain falls but there was a power outage while the 
>rain was falling
>- when the power goes back on SDR reads the sensor's new reading which 
>correctly shows 25mm accumulated in total over all days
>- so what he's looking for (I think) is how to set weewx up so 
>day-two's rain shows 5mm (new total of 25 - old total of 20)
>
> Hope this helps.
>
> (Stefanos please correct me if I interpreted your email wrong)
>
>

-- 
You received this message because you are subscribed 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/69691b9d-0339-4177-87a4-80cb988cb6b0n%40googlegroups.com.

[weewx-user] Re: Having trouble setting up MQTTSubscribe

[Stefanos Kalaitzis]

hi ... I will show mine ... may help you ..
in skin.conf i have added this
# MQTT Websockets defaults
mqtt_websockets_enabled = 1
mqtt_websockets_host = "broker.emqx.io"
mqtt_websockets_port = 8084
mqtt_websockets_ssl = 1
mqtt_websockets_topic = "*whatever_name_you_want*/loop" 
disconnect_live_website_visitor = 180

in weewx.conf i use this:
[[MQTT]]
server_url = mqtt://broker.emqx.io:8883
topic = *same_as_in_skin.conf*  #mqtt_websokets_topic
unit_system = METRICWX
binding = loop
aggregation = aggregate
log_success = False
log_failure = True
[[[tls]]]
ca_certs = /etc/ssl/certs/broker.emqx.io-ca.crt
[[[inputs]]]
windSpeed
units = km_per_hour
windGust
units = km_per_hour
the only thing to do before you done it is to download from emqx broker 
their free certificate and save it to /etc/ssl/certs/
On Friday, January 14, 2022 at 6:49:33 PM UTC+2 kavanag...@gmail.com wrote:

> Also meant to add I am using an Acurite5N1 weather station. I will also 
> have several ESP8266/ESP32 boards with temp/humidity/pressure sensors 
> reporting via MQTT.
>
> Nick
>
> On Friday, January 14, 2022 at 11:47:53 AM UTC-5 Nick Kavanagh wrote:
>
>> Hello,
>>
>> I am setting up a new weewx server, with an sdr driver, Belchertown skin, 
>> and MQTTSubscibe.
>>
>> I installed weewx on a RaspberryPi 4 (4GB) using sudo apt install weewx.
>> I then followed the steps here: 
>> https://osmocom.org/projects/rtl-sdr/wiki#Source-Code
>> Next, here: 
>> https://github.com/merbanan/rtl_433/blob/master/docs/BUILDING.md
>> Next here: https://pimylifeup.com/raspberry-pi-mosquitto-mqtt-server/
>> Then here: https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki
>> And finally here: https://github.com/poblabs/weewx-belchertown/releases
>>
>> When I issue the command sudo systemctl start (or restart) weewx, I get 
>> this message under status and under /var/log/syslog:
>>
>> sudo systemctl status weewx
>> ● weewx.service - LSB: weewx weather system
>>Loaded: loaded (/etc/init.d/weewx; generated)
>>Active: active (exited) since Fri 2022-01-14 10:27:28 EST; 1h 5min ago
>>  Docs: man:systemd-sysv-generator(8)
>>   Process: 1049 ExecStart=/etc/init.d/weewx start (code=exited, 
>> status=0/SUCCESS)
>>
>> Jan 14 10:27:29 weewxserver python3[1064]: weewx[1064] CRITICAL __main__: 
>> File "/usr/share/weewx/weewxd", line 151, in main
>> Jan 14 10:27:29 weewxserver python3[1064]: weewx[1064] CRITICAL __main__: 
>>   engine = weewx.engine.StdEngine(config_dict)
>> Jan 14 10:27:29 weewxserver python3[1064]: weewx[1064] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/engine.py", line 93, in __init__
>> Jan 14 10:27:29 weewxserver python3[1064]: weewx[1064] CRITICAL __main__: 
>>   self.loadServices(config_dict)
>> Jan 14 10:27:29 weewxserver python3[1064]: weewx[1064] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/engine.py", line 161, in 
>> loadServices
>> Jan 14 10:27:29 weewxserver python3[1064]: weewx[1064] CRITICAL __main__: 
>>   obj = weeutil.weeutil.get_object(svc)(self, config_dict)
>> Jan 14 10:27:29 weewxserver python3[1064]: weewx[1064] CRITICAL __main__: 
>> File "/usr/share/weewx/weeutil/weeutil.py", line 1119, in 
>> get_object
>> Jan 14 10:27:29 weewxserver python3[1064]: weewx[1064] CRITICAL __main__: 
>>   mod = __import__(module)
>> Jan 14 10:27:29 weewxserver python3[1064]: weewx[1064] CRITICAL __main__: 
>>   ModuleNotFoundError: No module named 'user.MQTTSubscribe'
>> Jan 14 10:27:29 weewxserver python3[1064]: weewx[1064] CRITICAL __main__: 
>>   Exiting
>>
>> I am unsure what I have done wrong. What other information can I provide 
>> to help track down my error? Where should user.MQTTSubscribe be located?
>>
>> Thanks, 
>> Nick
>>
>

-- 
You received this message because you are subscribed 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/1692ee30-b896-45be-8362-0833e6855d78n%40googlegroups.com.

[weewx-user] Re: SDR and Backfill

[Stefanos Kalaitzis]

i dont know if my english is good enough to understand ... but my console 
(i plug it to electricity power, no batteries) do that thing ... when it 
turns back on , it gives me the amount of rain that fell in this period

On Tuesday, January 11, 2022 at 8:46:23 AM UTC+2 Stefanos Kalaitzis wrote:

> I see your point and i fully understand it but i dont care for other 
> values when we have power off except for rain 
> For example my station calculate rain from rain total and if for example 
> my rain total is 20mm  (weewx is calculating ,20 -20 = 0mm which is right, 
> new total - old total) and we have power off ,and for that period 5mm fall 
> , i think that the station because has batteries transmits 25mm rain total 
> but of course sdr is off   So when weewx start again loop periods and 
> gets data from sdr sorry the rain total will be 25mm and if it has saved 
> the last value of rain total then it is 25 - 20 = 5 mm 
>
> On Tuesday, January 11, 2022 at 12:06:32 AM UTC+2 vince wrote:
>
>> Where would weewx get the data from ?
>>
>> If you lose power, your SDR isn't listening to the sensors, so how could 
>> weewx know what the weather conditions were ?
>>
>>

-- 
You received this message because you are subscribed 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/fbfc19a6-1195-4581-87de-d76d93c1bc70n%40googlegroups.com.

[weewx-user] Re: SDR and Backfill

[Stefanos Kalaitzis]

I see your point and i fully understand it but i dont care for other values 
when we have power off except for rain 
For example my station calculate rain from rain total and if for example my 
rain total is 20mm  (weewx is calculating ,20 -20 = 0mm which is right, new 
total - old total) and we have power off ,and for that period 5mm fall , i 
think that the station because has batteries transmits 25mm rain total but 
of course sdr is off   So when weewx start again loop periods and gets 
data from sdr sorry the rain total will be 25mm and if it has saved the 
last value of rain total then it is 25 - 20 = 5 mm 

On Tuesday, January 11, 2022 at 12:06:32 AM UTC+2 vince wrote:

> Where would weewx get the data from ?
>
> If you lose power, your SDR isn't listening to the sensors, so how could 
> weewx know what the weather conditions were ?
>
>

-- 
You received this message because you are subscribed 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/2c012514-bb9c-45fe-affb-e66966e652e2n%40googlegroups.com.

[weewx-user] SDR and Backfill

[Stefanos Kalaitzis]

Hi ... I am running weewx with sdr driver without any problem a long time 
now... but i noticed that when we have a power off and and rain falls for 
that period , when it comes up weewx doesn't back fill the amount of rain 

i dont know if weewx stores the last value of rain total so then its easy 
to calculate the missing values or if i must do some changes to weewx.conf 
or sdr.py

thank u in advanced 

-- 
You received this message because you are subscribed 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/62be4272-72c8-4178-9699-a7da440424fan%40googlegroups.com.

[weewx-user] Re: Weewx + Bresser Wifi Station + sdr

[Stefanos Kalaitzis]

Hi ... Please help I have Bresser 5in1 7002580 I am using rpi4 with 
weewx 4.2.0 and nooelec sdr  The sdr delivered to weewx the rain_total 
packet but weewx in my case doesn't make the deltas calculations so the 
rain is always 0.00mm ... I have tried almost everything in weewx.conf 
(because i think that something have to trigger weewx to calculate the rain 
value with rain_total packet ) but no rain ... Only pain ... Both sdr.py 
and weewx.conf are set up correctly (i think) and i have in the [sdr] field

[[deltas ]]
rain = rain_total
the station sends 2 partial packets ... fisrt has the rain and wind values 
and the second all except rain
my log
raspberrypi weewx[12220] DEBUG user.sdr: lines=['{"time" : "2020-12-07 
15:27:56", "model" : "Bresser-6in1", "id" : 411043787, "channel" : 0, 
"battery_ok" : 1, "sensor_type" : 1, "wind_max_m_s" : 0.200, "wind_avg_m_s" 
: 0.200, "wind_dir_deg" : 248, "rain_mm" : 80.800, "mic" : "CRC"}\n']
Dec 7 17:27:59 raspberrypi weewx[12220] DEBUG user.sdr: packet={'windDir': 
248.0, 'windSpeed': 0.2, 'windGust': 0.2, 'outTemp': None, 'outHumidity': 
None, 'barometer': 1009.1, 'rain_total': 80.8, 'dateTime': 
1607354876, 'usUnits': 17}
7 17:27:47 raspberrypi weewx[12220] DEBUG user.sdr: lines=['{"time" : 
"2020-12-07 15:27:44", "model" : "Bresser-6in1", "id" : 411043787, 
"channel" : 0, "battery_ok" : 1, "temperature_C" : 10.700, "humidity" : 97, 
"sensor_type" : 1, "wind_max_m_s" : 0.200, "wind_avg_m_s" : 0.200, 
"wind_dir_deg" : 248, "mic" : "CRC"}\n']
Dec 7 17:27:47 raspberrypi weewx[12220] DEBUG user.sdr: packet={'windDir': 
248.0, 'windSpeed': 0.2, 'windGust': 0.2, 'outTemp': 10.7, 'outHumidity': 
97.0, 'barometer': 1009.1, 'rain_total': None, 'dateTime': 
1607354864, 'usUnits': 17}

Probably you will notice that in log the station appears like 6in1  i 
dont know why but i modified (with a big help of my friend) the sdr.py and 
returns bresser5in1.packets all the others values transmitted to 
weather sites without any problem...
sensor map
[SDR]
# This section is for the software-defined radio driver. # The driver to 
use driver = user.sdr cmd = /usr/local/bin/rtl_433 -M utc -F json -f 868.2M 
-R 172 [[sensor_map]] windDir = wind_dir.411043787.Bresser5in1Packet 
windSpeed = wind_speed.411043787.Bresser5in1Packet windGust = 
wind_gust.411043787.Bresser5in1Packet outTemp = 
temperature.411043787.Bresser5in1Packet outHumidity = 
humidity.411043787.Bresser5in1Packet barometer = 
pressure.411043787.Bresser5in1Packet rain_total = 
rain_total.411043787.Bresser5in1Packet [[deltas]] rain = rain_total 

Thank you in advanced if any help provided
On Sunday, October 4, 2020 at 10:21:37 AM UTC+3 Rafael Moslin wrote:

> The Bresser 5in1 868 Mhz (868.200 in my case) certainly works with a Pi0W 
> and a £23 USB SDR radio bought off Amazon 
> .
>
> On Thursday, 24 September 2020 at 22:25:33 UTC+1 sc.lep...@gmail.com 
> wrote:
>
>> Hello 
>>
>> I am interested in bresser Station  with Wifi support but station base as 
>> no usb port to connect to an rpi.
>>
>> Bresser station like this  : 
>> https://www.bresser.de/fr/Temps/Stations-Meteo/Centrale-meteo/BRESSER-Centrale-meteo-WIFI-ClearView-avec-capteur-7-en-1.html
>>
>> If I buy usb sdr key like here : 
>> https://github.com/weewx/weewx/wiki/sdr-rpi-recipe
>> It will be possible to get packet from sensors ?  
>>
>> Frequency  :  868 MHz for sensors 
>>
>> Thanks a lot 
>>
>>

-- 
You received this message because you are subscribed 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/0d6a4209-e451-4e6d-b9c8-6fcdf7197e75n%40googlegroups.com.