Re: [weewx-user] Update from 5.0 to 5.1 not showing up on the log?
Good morning, Just an update: I was able to fix my problem. I had mistakenly installed venv in a folder that was not a weewx folder. So I installed the venv folder inside the weewx folder and activated venv and then upgraded to 5.0 and then version 5.1. Now the upgrade worked . BR Georg Tom Keffer schrieb am Mittwoch, 17. Juli 2024 um 22:00:00 UTC+2: > Well, how did you do the upgrade? > > On Wed, Jul 17, 2024 at 12:32 PM weerman wrote: > >> >> Hi, >> >> I have just looked for the weewx-data folder and it is in the same folder >> you mentioned.. it looks like i must have messed up something during the >> installation of weewx 5.0. >> Should i try to reinstall weewx 5.0 again? >> >> Best regards >> >> Georg >> Tom Keffer schrieb am Mittwoch, 17. Juli 2024 um 17:49:21 UTC+2: >> >>> Your weewxd module is in an unusual >>> place, /usr/local/lib/python3.9/dist-packages/weewxd.py. It should be in >>> ~/weewx-data/... >>> >>> How did you do the original install? Did you set up a virtual >>> environment? Or, press on using "sudo". >>> >>> Did you remember to activate your virtual environment before upgrading? >>> >>> On Wed, Jul 17, 2024 at 8:38 AM weerman wrote: >>> Hi all, I tried to update yesterday weewx from version 5.0 to 5.1 following the quickstart guide, except for the optional skins and confs upgrade. https://weewx.com/docs/5.1/quickstarts/pip/#upgrade All went well without any errors thrown out. But after i started weewx i noticed that the log still says "weewxd 5.0" is installed. See my attached logfile. Jul 16 17:51:44 raspberrypi weewxd[8824]: INFO weewxd: Initializing weewxd version 5.0.0 Jul 16 17:51:44 raspberrypi weewxd[8824]: INFO weewxd: Command line: /usr/local/bin/weewxd Jul 16 17:51:44 raspberrypi weewxd[8824]: INFO weewxd: Using Python 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110] Jul 16 17:51:44 raspberrypi weewxd[8824]: INFO weewxd: Located at /usr/bin/python3 Jul 16 17:51:44 raspberrypi weewxd[8824]: INFO weewxd: Platform Linux-6.1.21-v7+-armv7l-with-glibc2.31 Jul 16 17:51:44 raspberrypi weewxd[8824]: INFO weewxd: Locale: 'de_DE.UTF-8' Jul 16 17:51:44 raspberrypi weewxd[8824]: INFO weewxd: Entry path: /usr/local/lib/python3.9/dist-packages/weewxd.py Jul 16 17:51:44 raspberrypi weewxd[8824]: INFO weewxd: WEEWX_ROOT: /home/weewx Jul 16 17:51:44 raspberrypi weewxd[8824]: INFO weewxd: Configuration file: /home/weewx/weewx.conf Jul 16 17:51:44 raspberrypi weewxd[8824]: INFO weewxd: User module: /home/weewx/bin/user Jul 16 17:51:44 raspberrypi weewxd[8824]: INFO weewxd: Debug: 0 Jul 16 17:51:44 raspberrypi weewxd[8824]: INFO weewx.engine: Loading station type FineOffsetUSB (weewx.drivers.fousb) Jul 16 17:51:44 raspberrypi weewxd[8824]: INFO weewx.drivers.fousb: driver version is 1.3 Jul 16 17:51:44 raspberrypi weewxd[8824]: INFO weewx.drivers.fousb: polling mode is PERIODIC Jul 16 17:51:44 raspberrypi weewxd[8824]: INFO weewx.drivers.fousb: polling interval is 60 Jul 16 17:51:44 raspberrypi weewxd[8824]: INFO weewx.drivers.fousb: found station on USB bus= device= Jul 16 17:51:45 raspberrypi weewxd[8824]: INFO user.DWD.db: thread 'DWDsave' starting Jul 16 17:51:45 raspberrypi weewxd[8824]: INFO weewx.engine: StdConvert target unit is 0x1 Jul 16 17:51:45 raspberrypi weewxd[8824]: INFO weewx.wxservices: StdWXCalculate will use data binding wx_binding Jul 16 17:51:45 raspberrypi weewxd[8824]: INFO weewx.engine: Archive will use data binding wx_binding Jul 16 17:51:45 raspberrypi weewxd[8824]: INFO weewx.engine: Record generation will be attempted in 'software' Jul 16 17:51:45 raspberrypi weewxd[8824]: INFO weewx.engine: Using archive interval of 300 seconds (software record generation) Jul 16 17:51:45 raspberrypi weewxd[8824]: INFO weewx.restx: StationRegistry: Station will be registered. Jul 16 17:51:45 raspberrypi weewxd[8824]: INFO weewx.restx: Wunderground: Posting not enabled. Jul 16 17:51:45 raspberrypi weewxd[8824]: INFO weewx.restx: PWSweather: Posting not enabled. Jul 16 17:51:45 raspberrypi weewxd[8824]: INFO weewx.restx: CWOP: Posting not enabled. Jul 16 17:51:45 raspberrypi weewxd[8824]: INFO weewx.restx: WOW: Posting not enabled. Jul 16 17:51:45 raspberrypi weewxd[8824]: INFO weewx.restx: AWEKAS: Data will be uploaded for user Georg8019 Jul 16 17:51:45 raspberrypi weewxd[8824]: INFO weewx.engine: 'pyephem' detected, extended almanac data is available Jul 16 17:51:45 raspberrypi weewxd[8824]: INFO weewxd: Starting up weewx version 5.0.0 Jul 16 17:51:45 raspberrypi weewxd[8824]: INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.s
Re: [weewx-user] Re: Belchertown and MQTT configuration error
try "sudo ss -tupl" which should show which process is using port 1883 On Wednesday, August 7, 2024 at 7:49:16 PM UTC-7 M&M wrote: > Thanks for looking into this for me. I feel like I've read a bunch of > pages and that I'm really close to this. I've attached my weewx.conf, > mosquitto.conf, and local.conf (located at /etc/mosquitto/conf.d/). > > Looking at the mosquitto log file, I'm seeing this error a ton of times: > > 1722824003: mosquitto version 2.0.11 starting > 1722824003: Config loaded from /etc/mosquitto/mosquitto.conf. > 1722824003: Opening websockets listen socket on port 9001. > 1722824003: Opening ipv4 listen socket on port 1883. > 1722824003: Opening ipv6 listen socket on port 1883. > 1722824003: Opening ipv4 listen socket on port 1883. > 1722824003: Error: Address already in use > > Although ps -ef is only showing one mosquitto running which I see the > service running with systemctl. > > On Monday, August 5, 2024 at 9:04:15 PM UTC-4 vince wrote: > >> Can't help without seeing your current mosquitto config file and your >> weewx.conf file at a minimum. Remember you need to restart weewx after >> making weewx.conf changes and that your mosquitto broker is running and >> accepting incoming traffic into the ip address you are trying to talk to. >> >> You might check your mosquitto broker's logfile too to see if anything >> there is being logged that might help. >> >> On Sunday, August 4, 2024 at 8:12:53 PM UTC-7 M&M wrote: >> >>> Vince, I followed that link and I'm making some progress. Thank you. I >>> now get the message on my local page: >>> >>> >>> Connected. Waiting for data. Last Updated 4 August 2024, 23:00:00 >>> >>> I've been reading over some threads of people having the same issue but >>> those fixes are not working for me. Thoughts? >>> >>> On Friday, August 2, 2024 at 4:01:58 PM UTC-4 Stefanos Kalaitzis wrote: >>> 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 fe
[weewx-user] Forecast data to InfluxDB?
I have weewx-influx (https://github.com/matthewwall/weewx-influx/tree/master) installed as well as weewx-forecast (https://github.com/chaunceygardiner/weewx-forecast) installed configured to use NWS. Both are working well, however i'm not sure how to get the forecast data flowing into Influx for usage in Grafana. The only values i see in Influx are "record" which are tied to the archive binding, and not the forecast binding that the forecast plugin creates. Any ideas on how I can get all the forecast values going to Influx as well? -- You received this message because you are subscribed to the Google 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/9d4ae538-3124-419a-bfd7-068a63cd1371n%40googlegroups.com.
Re: [weewx-user] Re: Belchertown and MQTT configuration error
Looks like I have two mosquittos running on 1883 but they have the same
PID.
pi@raspberrypi:/etc/weewx/skins/Belchertown $ sudo ss -tupl
NetidState Recv-Q Send-Q Local
Address:Port Peer Address:PortProcess
udp UNCONN 0 0
0.0.0.0:51030 0.0.0.0:*
users:(("avahi-daemon",pid=234,fd=14))
udp UNCONN 0 0
0.0.0.0:mdns0.0.0.0:*
users:(("avahi-daemon",pid=234,fd=12))
udp UNCONN 0 0
0.0.0.0:bootpc 0.0.0.0:*
users:(("dhcpcd",pid=571,fd=13))
udp UNCONN 0 0
*:mdns *:*
users:(("avahi-daemon",pid=234,fd=13))
udp UNCONN 0 0
*:54532 *:*
users:(("avahi-daemon",pid=234,fd=15))
tcp LISTEN 0 100
0.0.0.0:18830.0.0.0:*
users:(("mosquitto",pid=18024,fd=8))
tcp LISTEN 0 128
0.0.0.0:ssh 0.0.0.0:*
users:(("sshd",pid=354,fd=3))
tcp LISTEN 0 100
[::]:1883 [::]:*
users:(("mosquitto",pid=18024,fd=9))
tcp LISTEN 0 4096
*:9001 *:*
users:(("mosquitto",pid=18024,fd=7))
tcp LISTEN 0 511
*:http *:*
users:(("apache2",pid=23498,fd=4),("apache2",pid=23497,fd=4),("apache2",pid=356,fd=4))
tcp LISTEN 0 128
[::]:ssh[::]:*
users:(("sshd",pid=354,fd=4))
On Thursday, August 8, 2024 at 12:14:00 PM UTC-4 vince wrote:
> try "sudo ss -tupl" which should show which process is using port 1883
>
> On Wednesday, August 7, 2024 at 7:49:16 PM UTC-7 M&M wrote:
>
>> Thanks for looking into this for me. I feel like I've read a bunch of
>> pages and that I'm really close to this. I've attached my weewx.conf,
>> mosquitto.conf, and local.conf (located at /etc/mosquitto/conf.d/).
>>
>> Looking at the mosquitto log file, I'm seeing this error a ton of times:
>>
>> 1722824003: mosquitto version 2.0.11 starting
>> 1722824003: Config loaded from /etc/mosquitto/mosquitto.conf.
>> 1722824003: Opening websockets listen socket on port 9001.
>> 1722824003: Opening ipv4 listen socket on port 1883.
>> 1722824003: Opening ipv6 listen socket on port 1883.
>> 1722824003: Opening ipv4 listen socket on port 1883.
>> 1722824003: Error: Address already in use
>>
>> Although ps -ef is only showing one mosquitto running which I see the
>> service running with systemctl.
>>
>> On Monday, August 5, 2024 at 9:04:15 PM UTC-4 vince wrote:
>>
>>> Can't help without seeing your current mosquitto config file and your
>>> weewx.conf file at a minimum. Remember you need to restart weewx after
>>> making weewx.conf changes and that your mosquitto broker is running and
>>> accepting incoming traffic into the ip address you are trying to talk to.
>>>
>>> You might check your mosquitto broker's logfile too to see if anything
>>> there is being logged that might help.
>>>
>>> On Sunday, August 4, 2024 at 8:12:53 PM UTC-7 M&M wrote:
>>>
Vince, I followed that link and I'm making some progress. Thank you.
I now get the message on my local page:
Connected. Waiting for data. Last Updated 4 August 2024, 23:00:00
I've been reading over some threads of people having the same issue but
those fixes are not working for me. Thoughts?
On Friday, August 2, 2024 at 4:01:58 PM UTC-4 Stefanos Kalaitzis wrote:
>
> 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
> mq
Re: [weewx-user] Re: Belchertown and MQTT configuration error
(apologies for the long post below) No - you have one process listening on two ports, which is correct. I just did a full install to a clean pi4 it works for me. Here are the config file snippets and some diagnostic information Note - if you set log_success true in the MQTT section you can verify weewx is publishing to the MQTT broker ok via the weewx log #--- # From the weewx log #--- 2024-08-08T19:55:17.387146-07:00 raspberrypi weewxd[4222]: DEBUG weewx.manager: Daily summary version is 4.0 2024-08-08T19:55:17.876041-07:00 raspberrypi weewxd[4222]: INFO weewx.restx: MQTT: Published record 2024-08-08 19:55:18 PDT (1723172118) 2024-08-08T19:55:18.294317-07:00 raspberrypi weewxd[4222]: INFO weewx.cheetahgenerator: Generated 12 files for report Belchertown in 0.92 seconds 2024-08-08T19:55:18.307852-07:00 raspberrypi weewxd[4222]: INFO weewx.reportengine: Copied 3 files to /home/pi/weewx-data/public_html/belchertown 2024-08-08T19:55:18.324487-07:00 raspberrypi weewxd[4222]: DEBUG weewx.manager: Daily summary version is 4.0 2024-08-08T19:55:18.487352-07:00 raspberrypi weewxd[4222]: DEBUG weewx.reportengine: Report 'FTP' not enabled. Skipping. 2024-08-08T19:55:18.487690-07:00 raspberrypi weewxd[4222]: DEBUG weewx.reportengine: Report 'RSYNC' not enabled. Skipping. 2024-08-08T19:55:20.375037-07:00 raspberrypi weewxd[4222]: INFO weewx.restx: MQTT: Published record 2024-08-08 19:55:20 PDT (1723172120) 2024-08-08T19:55:22.874986-07:00 raspberrypi weewxd[4222]: INFO weewx.restx: MQTT: Published record 2024-08-08 19:55:23 PDT (1723172123) 2024-08-08T19:55:25.375017-07:00 raspberrypi weewxd[4222]: INFO weewx.restx: MQTT: Published record 2024-08-08 19:55:25 PDT (1723172125) #--- # Example mosquitto log #--- 1723168752: mosquitto version 2.0.11 starting 1723168752: Config loaded from /etc/mosquitto/mosquitto.conf. 1723168752: Starting in local only mode. Connections will only be possible from clients running on this machine. 1723168752: Create a configuration file which defines a listener to allow remote access. 1723168752: For more details see https://mosquitto.org/documentation/authentication-methods/ 1723168752: Opening ipv4 listen socket on port 1883. 1723168752: Opening ipv6 listen socket on port 1883. 1723168801: mosquitto version 2.0.11 running 1723170602: Saving in-memory database to /var/lib/mosquitto//mosquitto.db. 1723170686: New connection from 192.168.1.232:56773 on port 1883. 1723170686: New client connected from 192.168.1.232:56773 as weewx_784a909c (p2, c1, k60). 1723170915: Client weewx_784a909c closed its connection. 1723171692: New connection from 192.168.1.232:51645 on port 1883. 1723171692: New client connected from 192.168.1.232:51645 as weewx_b396e0df (p2, c1, k60). 1723171834: New client connected from :::192.168.1.51:54402 as website522586962 (p2, c1, k60). 1723172225: Client weewx_b396e0df closed its connection. 1723172228: New connection from 192.168.1.232:54439 on port 1883. 1723172228: New client connected from 192.168.1.232:54439 as weewx_2d9b84ff (p2, c1, k60). 1723172403: Saving in-memory database to /var/lib/mosquitto//mosquitto.db. #--- # weewx.conf snippets for Belchertown websockets #--- [StdRESTful] [[MQTT]] server_url = mqtt://192.168.1.232:1883/ topic = simulator unit_system = US binding = archive, loop aggregation = aggregate enable = true log_success = true # NOTE: THIS IS VERY CHATTY log_failure = true [StdReport] [[Belchertown]] skin = Belchertown HTML_ROOT = public_html/belchertown enable = true [[[Extras]]] #--- MQTT Websockets (for Real Time Streaming) Options --- mqtt_websockets_enabled = 1 mqtt_websockets_host = 192.168.1.232 mqtt_websockets_port = 9001 mqtt_websockets_ssl = 0 mqtt_websockets_topic = simulator/loop disconnect_live_website_visitor = 180 #- # /etc/mosquitto/conf.d/local.conf for minimal websockets #- listener 9001 protocol websockets listener 1883 allow_anonymous true #- # weectl extension list #- Extension NameVersion Description Belchertown 1.3.1 A clean modern skin with real time streaming updates and interactive charts. Modeled after BelchertownWeather.com mqtt 0.24 Upload weather data to MQTT server. #--
Re: [weewx-user] Re: Belchertown and MQTT configuration error
Interesting. I changed log_success to true however my /var/log/weewx.log file is empty. On Thursday, August 8, 2024 at 11:12:37 PM UTC-4 vince wrote: > (apologies for the long post below) > > No - you have one process listening on two ports, which is correct. > > I just did a full install to a clean pi4 it works for me. Here are the > config file snippets and some diagnostic information > > Note - if you set log_success true in the MQTT section you can verify > weewx is publishing to the MQTT broker ok via the weewx log > > #--- > # From the weewx log > #--- > 2024-08-08T19:55:17.387146-07:00 raspberrypi weewxd[4222]: DEBUG > weewx.manager: Daily summary version is 4.0 > 2024-08-08T19:55:17.876041-07:00 raspberrypi weewxd[4222]: INFO > weewx.restx: MQTT: Published record 2024-08-08 19:55:18 PDT (1723172118) > 2024-08-08T19:55:18.294317-07:00 raspberrypi weewxd[4222]: INFO > weewx.cheetahgenerator: Generated 12 files for report Belchertown in 0.92 > seconds > 2024-08-08T19:55:18.307852-07:00 raspberrypi weewxd[4222]: INFO > weewx.reportengine: Copied 3 files to > /home/pi/weewx-data/public_html/belchertown > 2024-08-08T19:55:18.324487-07:00 raspberrypi weewxd[4222]: DEBUG > weewx.manager: Daily summary version is 4.0 > 2024-08-08T19:55:18.487352-07:00 raspberrypi weewxd[4222]: DEBUG > weewx.reportengine: Report 'FTP' not enabled. Skipping. > 2024-08-08T19:55:18.487690-07:00 raspberrypi weewxd[4222]: DEBUG > weewx.reportengine: Report 'RSYNC' not enabled. Skipping. > 2024-08-08T19:55:20.375037-07:00 raspberrypi weewxd[4222]: INFO > weewx.restx: MQTT: Published record 2024-08-08 19:55:20 PDT (1723172120) > 2024-08-08T19:55:22.874986-07:00 raspberrypi weewxd[4222]: INFO > weewx.restx: MQTT: Published record 2024-08-08 19:55:23 PDT (1723172123) > 2024-08-08T19:55:25.375017-07:00 raspberrypi weewxd[4222]: INFO > weewx.restx: MQTT: Published record 2024-08-08 19:55:25 PDT (1723172125) > > #--- > # Example mosquitto log > #--- > 1723168752: mosquitto version 2.0.11 starting > 1723168752: Config loaded from /etc/mosquitto/mosquitto.conf. > 1723168752: Starting in local only mode. Connections will only be possible > from clients running on this machine. > 1723168752: Create a configuration file which defines a listener to allow > remote access. > 1723168752: For more details see > https://mosquitto.org/documentation/authentication-methods/ > 1723168752: Opening ipv4 listen socket on port 1883. > 1723168752: Opening ipv6 listen socket on port 1883. > 1723168801: mosquitto version 2.0.11 running > 1723170602: Saving in-memory database to /var/lib/mosquitto//mosquitto.db. > 1723170686: New connection from 192.168.1.232:56773 on port 1883. > 1723170686: New client connected from 192.168.1.232:56773 as > weewx_784a909c (p2, c1, k60). > 1723170915: Client weewx_784a909c closed its connection. > 1723171692: New connection from 192.168.1.232:51645 on port 1883. > 1723171692: New client connected from 192.168.1.232:51645 as > weewx_b396e0df (p2, c1, k60). > 1723171834: New client connected from :::192.168.1.51:54402 as > website522586962 (p2, c1, k60). > 1723172225: Client weewx_b396e0df closed its connection. > 1723172228: New connection from 192.168.1.232:54439 on port 1883. > 1723172228: New client connected from 192.168.1.232:54439 as > weewx_2d9b84ff (p2, c1, k60). > 1723172403: Saving in-memory database to /var/lib/mosquitto//mosquitto.db. > > > #--- > # weewx.conf snippets for Belchertown websockets > #--- > > [StdRESTful] > > [[MQTT]] > server_url = mqtt://192.168.1.232:1883/ > topic = simulator > unit_system = US > > binding = archive, loop > aggregation = aggregate > enable = true > log_success = true # NOTE: THIS IS VERY CHATTY > log_failure = true > > > [StdReport] > > [[Belchertown]] > skin = Belchertown > HTML_ROOT = public_html/belchertown > > enable = true > > [[[Extras]]] > > #--- MQTT Websockets (for Real Time Streaming) Options --- > mqtt_websockets_enabled = 1 > mqtt_websockets_host = 192.168.1.232 > > mqtt_websockets_port = 9001 > mqtt_websockets_ssl = 0 > mqtt_websockets_topic = simulator/loop > disconnect_live_website_visitor = 180 > > #- > # /etc/mosquitto/conf.d/local.conf for minimal websockets > #- > > listener 9001 > protocol websockets > > listener 1883 > allow_anonymous true > > #- > # weectl extens
