Re: [weewx-user] Digest for weewx-user@googlegroups.com - 7 updates in 1 topic

[Nick Kavanagh]

Thanks so much for the opinions and links. Got some good starting points
now, especially now I'm aware of some good places to look for used
equipment to be able to assemble something that does not "phone home". I
had no idea that the newer Davis gear did that.

With the Accurite, I was able to make everything work on a dedicated Pi 4,
with sdr and mqtt. I used sdr to get packets from the Accurite and Accurite
sensors, while my homemade (ESP32 boards with various bme and bmr sensors)
fed weewx through mqtt. The ESP32's sensors seem to agree with one another
within a tight range, and I'm pretty pleased with them. The Accurite
sensors for outdoors often disagreed by quite a lot, not on the mast but
their addon temp and lightning sensors. In fact the lightning sensor was so
often incorrect that I just dropped it. So I like the idea of the big
startup Davis Christmas purchase and adding the extra sensors once a month.

We had a significant wind event here Monday and my internal weather-geek
was very disappointed I couldn't measure it!

Again, thanks to all of you. Now, I'm going shopping!

On Wed, Dec 20, 2023, 06:47  wrote:

> weewx-user@googlegroups.com
> <https://groups.google.com/forum/?utm_source=digest_medium=email#!forum/weewx-user/topics>
>  Google
> Groups
> <https://groups.google.com/forum/?utm_source=digest_medium=email/#!overview>
> <https://groups.google.com/forum/?utm_source=digest_medium=email/#!overview>
> Topic digest
> View all topics
> <https://groups.google.com/forum/?utm_source=digest_medium=email#!forum/weewx-user/topics>
>
>- Best Davis station for my buck, and purpose?
><#m_4459879255494351866_group_thread_0> - 7 Updates
>
> Best Davis station for my buck, and purpose?
> <http://groups.google.com/group/weewx-user/t/23100b66f8ff433f?utm_source=digest_medium=email>
> Nick Kavanagh : Dec 19 10:46AM -0500
>
> I recently moved and made the conscious choice to leave my Accurite 7 in
> one behind, intending on a major upgrade now that I'm a homeowner and not
> renter.
>
> Now, I'm overwhelmed by choice. For my purposes, I'm looking for good
> quality and accuracy, setting my weather website back up, contributing to
> NOAA, and integrating my homemade temp/humidity/pressure sensors within my
> house. I'm not trying to provide data for flight/navigation etc., so I'm
> somewhat in the middle. I want a great system, but not a purely
> professional system either.
>
> Blah, blah, blah... what recommendations do you have for best bang for the
> buck in that kind of use case? My wallet wants to open around 300 dollars,
> but will have to slam shut again at about 800. I THINK I want Davis, but am
> quite willing to look at any others some of you might suggest.
>
> TIA,
> Nick K.
> "michael.k...@gmx.at" : Dec 19 08:05AM -0800
>
> Davis and $300, doesn't sound this fits together.
>
> In my opinion, currently the Ecowitt universe provides the most flexible,
> most adaptable and most extendable hardware on the market. You can start
> tiny and go big, they even provide a whole range of different sensors,
> allowing you to adapt you system to you special needs. Currently, and
> hopefully they don't go the evil way like others, you also have the
> possibility to locally access and collect all your data, even without
> being
> forced to have your devices online.
>
> You can "build your own" station with Ecowitt components. Start, for
> instance, with outTemp/humi, barometer, wind, rain, radiation sensors and
> a
> console for ~$300. Expand your system with a lightning sensor a month
> later, buy soil moisture and leaf wetness sensor for Easter, let Santa
> bring half a dozen extra humi/temp and air quality sensors next Christmas.
> If a sensor breaks? Get a spare, everything is sold separately.
>
> They are not perfect, but usually you find a way to get around the
> limitations.
>
> Their hardware is also sold differently branded by some resellers.
>
> Nick Kavanagh schrieb am Dienstag, 19. Dezember 2023 um 16:46:54 UTC+1:
>
> Tom Hogland : Dec 19 10:02AM -0800
>
> The Davis Vantage Pro2 would do what you want, other than using your
> homemade sensors. The console has built-in sensors, though. I've bought
> two
> of them used - first a cabled one, then a wireless one, and neither was
> over $800. You can find them new in that range these days. Get the old
> console, not the new one, or find a sensor suite and add the console and
> datalogger (either Davis datalogger or the 3rd party one that's been
> discussed here). The dataloggers will connect directly to a PC, or you can
> use the Weatherlink Live and sniff the packets - either way works. I
> recently saw a complete station on eBay in the $500s - sensors, cons

[weewx-user] Best Davis station for my buck, and purpose?

[Nick Kavanagh]

I recently moved and made the conscious choice to leave my Accurite 7 in
one behind, intending on a major upgrade now that I'm a homeowner and not
renter.

Now, I'm overwhelmed by choice. For my purposes, I'm looking for good
quality and accuracy, setting my weather website back up, contributing to
NOAA, and integrating my homemade temp/humidity/pressure sensors within my
house. I'm not trying to provide data for flight/navigation etc., so I'm
somewhat in the middle. I want a great system, but not a purely
professional system either.

Blah,  blah, blah... what recommendations do you have for best bang for the
buck in that kind of use case? My wallet wants to open around 300 dollars,
but will have to slam shut again at about 800. I THINK I want Davis, but am
quite willing to look at any others some of you might suggest.

TIA,
Nick K.

-- 
You received this message because you are subscribed to the Google 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/CABp3gvtWXKQmCTRZJpPd3-rgbaaGzpgG%2BUka9AX61ru6n8_ZVg%40mail.gmail.com.

[weewx-user] Recommends for new station under 300

[Nick Kavanagh]

I have been running an Acurite 5n1 since 2018, using sdr, as well as
multiple esp-8266 with been or bmp280's using matter. The 5n1 has given up
the ghost.

I would like to replace it with something similar, as I already understand
sdr use within weewx. However, I am also interested in using more accurate
technology.

My budget is somewhat limited, so I hope to bring the cost in at under $300
(US).

I am open to all recommendations, and would also, if possible, like to know
WHY you might recommend a particular unit or group of products. If it would
require a change in driver's, etc., please indicate that (if you just say
it would, I'm glad to do the research on how to implement them).

Finally, the main product I have researched at this point is the Acurite
Atlas.

Thank you in advance,

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/CABp3gvtMoSK0XSs55zrheoLHmyi1NBM8dAuFYWjuMGKF_Yiyyg%40mail.gmail.com.

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

[Nick Kavanagh]

Thank you for the link. This wasn't the answer in this case, but will 
certainly help me understand more about the functions of mqtt within the 
belchertown skin.

On Friday, January 14, 2022 at 12:53:48 PM UTC-5 storm...@gmail.com wrote:

> Did you look @ 
> https://github.com/poblabs/weewx-belchertown#mqtt-and-mqtt-websockets-optional
>
> On Friday, January 14, 2022 at 12:44:57 PM UTC-5 stefanos...@gmail.com 
> wrote:
>
>> 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 p

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

[Nick Kavanagh]

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/a08e6871-9746-4b1c-95ef-d87c324a4fedn%40googlegroups.com.

[weewx-user] Having trouble setting up MQTTSubscribe

[Nick Kavanagh]

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/4842991b-efed-4958-90cd-0b1457362d45n%40googlegroups.com.

[weewx-user] Erratic pressure readings using homemade (ESP8266, BMP280) sensor and MQTTsubscribe

[Nick Kavanagh]

my station can be found at https://stonecressweather.ddns.net .

I have two sensors for temperature and pressure which both publish to weewx
using the mqtt subscribe driver. The program I have running on the sensors
takes a reading of pressure and temperature every 10 seconds, keeps a
running average of pressure in avgPressure variable, and publishes on mqtt
topic every five minutes. My station archive records update every five
minutes. Theoretically, both my "Barometer" and "Pressure" values on weewx
should be the five minute avgPressure at each unit. If you look at my
graphs, however, I am experiencing spikes on both sensors at random points.
Having studied serial output from my sensor units, they do not seem to be
putting out the spiked reading. Also, according to my program on the
sensors, they CAN'T output a significant spike.

I'm not quite sure where to begin looking at weewx to find where the spikes
are being introduced to the record and therefore appearing in the graphs.
If someone could point me in the general direction, it would be much
appreciated. As far as log files, please indicate how long of a time period
I should include and I will post them asap.

Thanks
Nick Kavanagh

-- 
You received this message because you are subscribed to the Google 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/CABp3gvt7B7e%3DB%2B%2Bh9oxvA9QUKNDX7BbmmZhhn9t%3DL3RkjbvL1Q%40mail.gmail.com.

[weewx-user] UV Calculation: Where and how?

[Nick Kavanagh]

I am trying to set up a UV sensor on an ESP8266, reporting to Weewx via
mqttSubscribe. The number being transmitted from the ESP8266 is a string
representation of an integer (no decimal value is allowed for in the
calculation of index). The number represented by the UV Index level (in the
Belchertown skin, but using the weewxdb value held in uv index), is a
float. The actual index values are integers, 0-11.

My actual question then, is where and how does weewx calculate the uv index
value? Should my sensor be making the UV Index calculation and sending that
value, or should it be sending the raw UV level to weewx, with weewx
calculationg the index value?

Nick Kavanagh
Very new python hobbyist.

-- 
You received this message because you are subscribed to the Google 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/CABp3gvvur8pfP1tEnkqE-3kkpPVxziC-iRL-uXQkh7PZysb0Nw%40mail.gmail.com.

[weewx-user] Re: Problems with Weewx writing MQTT Broker

[Nick Kavanagh]

Have you tried using the weewx-MQTTSubscribe addon? 

https://github.com/bellrichm/WeeWX-MQTTSubscribe

On Sunday, March 21, 2021 at 2:30:35 AM UTC-4 Dun Mac wrote:

> I have been trying for a week to get the live updates to work for Weewx. 
> But I am not having any luck at all, so can someone please help if they can 
> see where my setup is wrong. For background info: Weewx is running on an 
> RPi 4B 192.168.8.155. I have set up an RPi 3A as the MQTT Broker 
> 192.168.8.158. The "service weewx status" shows the following:
>
>  *Mar 21 12:40:23 RPi-weather python3[2185]: weewx[2185] ERROR 
> weewx.restx: MQTT: Failed to publish record 2021-03-21 11*
>
>  The Belchertown page shows:
>
> *"Connected. Waiting for data. Last Updated 21 March 2021 yada yada"*
>
> My Weewx.conf setup is as follows:
>
>  
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *188 [[MQTT]] 189 server_url = 
> mqtt://vantagepro:xxx...@192.168.8.158:1833/ 
>  190 topic = 
> weather 191 unit_system = METRIC 192 binding = archive,loop 
> 193 aggregation = aggregate 248 [[Belchertown]] 249 
> skin = Belchertown 250 HTML_ROOT = /var/www/html 251  
> [[Services]] 669   674 restful_services = 
> weewx.restx.StdStationRegistry,.., user.mqtt.MQTT*
>
>  
>
> I have not set up SSL on the Broker, hence it is disabled.   
> /etc/weewx/skins/Belchertown/skin.conf 
> is as follows:
>
>
>
>
>
>
>
>
> *35 # MQTT Websockets 36 mqtt_websockets_enabled = 1 37 
> mqtt_websockets_host = 192.168.8.158 38 mqtt_websockets_port = 9001 
> 39 mqtt_websockets_ssl = 0 40 mqtt_websockets_topic = weather/loop 
> 41 disconnect_live_website_visitor = 180*
>
>  
>
> The MQTT (192.168.8.158) broker.conf is:
>
>  
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> * 6 pid_file /run/mosquitto/mosquitto.pid  7  8 persistence true  9 
> persistence_location /var/lib/mosquitto/ 10 11 log_dest file 
> /var/log/mosquitto/mosquitto.log 12 13 log_type all 14 log_facility 5 15 
> log_type error 16 log_type warning 17 log_type notice 18 log_type 
> information 19 20 connection_messages true 21 log_timestamp true 22 23 
> include_dir /etc/mosquitto/conf.d*
>
> and the Broker/conf.d/myconfig.conf
>
>
>
>
>
>
>
>
>
>
>
>
> *# mqtt listener 1883 protocol mqtt # websockets listener 9001 protocol 
> websockets #Allow anonymous to read only and others need to be set in 
> passwd,acl allow_anonymous true password_file /etc/mosquitto/passwd 
> acl_file /etc/mosquitto/acl*
>
>  
>
> The Broker Pub/Sub is working with and without passwords, using terminals 
> in Weewx RPi (192.168.8.155).
>
> The Mosquitto client on the Weewx machine (192.168.8.155) has no 
> configuration file
>
>  
>
> I know I have something wrong but I just have no idea.
>
>  
>
>

-- 
You received this message because you are subscribed to the Google 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/f802af87-3435-4885-9ba5-54b29d9af8a6n%40googlegroups.com.

Re: [weewx-user] Re: Attempting to integrate Acurite 6045M, rtl_433 does not show parsed data, cannot figure out entry for sensor map

[Nick Kavanagh]

Thanks to all of you, I solved it. It appears that in the most current
version of the weewx-sdr code, the 6045M is NOT a recognized model. After
rerunning find with better search parameters, I found it where it belonged
in /usr/share/weewx/user/. Thanks to Andy and his upload of his version of
sdr.py, I replaced the version that came with the most recent code on
github with Andy's version and it was immediately recognized. It also is
using a wild card at this point, but I"m going to edit weewx.conf and try
0009 as the identifier. All I have added now is the temperature reading,
but I will be adding lightning readings tomorrow. Thanks again, and I"m
going to raise an issue on the github page for weewx-sdr.

Nick Kavanagh


On Wed, Feb 10, 2021 at 8:54 PM Mks Mk  wrote:

>
> try the following
> install sdr and follow instructions
> https://github.com/matthewwall/weewx-sdr
> -update rtl_433 to latest
> -edit the sdr.py file and make sure the identifier is "Acurite-6045M"
> -add this to sensor map in weewx.conf file
>
> [[sensor_map]]
> extraTemp2 = temperature.0009.AcuriteLightningPacket
> On Thursday, February 11, 2021 at 4:46:11 AM UTC+3 kavanag...@gmail.com
> wrote:
>
>> I also ran a find on my system to locate sdr.py and see if there was some
>> way to convince it to recognize the 6045M. It appears that I don't have
>> this file. I've downloaded it, but I'm unsure where to place it and cause
>> it to be run when required.
>>
>> On Wednesday, February 10, 2021 at 8:23:31 PM UTC-5 Nick Kavanagh wrote:
>>
>>> I attempted the wildcard with several variatons on the packet name, with
>>> no joy. However, with debug set to 1, and log_unknown and _unmapped_sensors
>>> true, I am getting two lines in the log:
>>>
>>> eb 10 19:57:39 weewxserver weewx[31499] DEBUG user.sdr: parse_json:
>>> unknown model Acurite-6045M
>>> Feb 10 19:57:39 weewxserver weewx[31499] DEBUG user.sdr: punt
>>> unrecognized line '{"time" : "2021-02-11 00:57:36", "model" :
>>> "Acurite-6045M", "id" : 9, "channel" : "C", "battery_ok" : 1,
>>> "temperature_F" : 55.200, "humidity" : 62, "strike_count" : 88,
>>> "storm_dist" : 20, "active" : 1, "rfi" : 0, "exception" : 0, "raw_msg" :
>>> "00096fbecff0ac14b5"}#012'
>>>
>>> what I'm confused by is that it is indicating the Acurite-6045M is an
>>> unknown model. I see from one of the answers above that, at least in that
>>> person's system, it is recognized. Could this be a bug in the latest
>>> release of the sdr driver software?
>>>
>>> Nick Kavanagh
>>>
>>> On Wednesday, February 10, 2021 at 3:58:34 PM UTC-5
>>> weatherl...@gmail.com wrote:
>>>
>>>> Try using a wildcard:
>>>>
>>>> temperature.0009.Acurite6045M
>>>> temperature.*.Acurite6045M
>>>>
>>>> On 10 Feb, 2021, at 12:03, Nick Kavanagh  wrote:
>>>>
>>>> That is not working. It seems like the problem is the id number of the
>>>> sensor. The Id is "9". Converting to hexadecimal, the number is9. Or
>>>> with twos complement 0009. I have tried using both of these in the stanza 
>>>> as
>>>> temperature.9.AcuriteLightningPacket
>>>> &
>>>> temperature.0009.AcuriteLightningPacket
>>>>
>>>> Neither have worked. Any suggestions on what that center portion of the
>>>> stanza should actually be?
>>>>
>>>> Nick Kavanagh
>>>>
>>>> On Tuesday, February 9, 2021 at 9:31:35 AM UTC-5 Andy wrote:
>>>>
>>>>> out: '{"time" : "2021-02-09 14:22:41", "model" : "Acurite-6045M", "id"
>>>>> : 15431, "channel" : "A", "battery_ok" : 1, "temperature_F" : 53.200,
>>>>> "humidity" : 78, "strike_count" : 174, "storm_dist" : 24, "active" : 0,
>>>>> "rfi" : 1, "exception" : 0, "raw_msg" : "fc476f4e0f5cd7b8fa"}\n'
>>>>>
>>>>> parsed: {'dateTime': 1612880561, 'usUnits': 1,
>>>>> 'channel.3C47.AcuriteLightningPacket': 'A',
>>>>> 'temperature.3C47.AcuriteLightningPacket': 53.2,
>>>>> 'battery.3C47.AcuriteLightningPacket': 0,
>>>>> 'humidity.3C47.AcuriteLightningPacket': 78,
>>>>> 'act

Re: [weewx-user] Re: Attempting to integrate Acurite 6045M, rtl_433 does not show parsed data, cannot figure out entry for sensor map

[Nick Kavanagh]

I also ran a find on my system to locate sdr.py and see if there was some 
way to convince it to recognize the 6045M. It appears that I don't have 
this file. I've downloaded it, but I'm unsure where to place it and cause 
it to be run when required.

On Wednesday, February 10, 2021 at 8:23:31 PM UTC-5 Nick Kavanagh wrote:

> I attempted the wildcard with several variatons on the packet name, with 
> no joy. However, with debug set to 1, and log_unknown and _unmapped_sensors 
> true, I am getting two lines in the log:
>
> eb 10 19:57:39 weewxserver weewx[31499] DEBUG user.sdr: parse_json: 
> unknown model Acurite-6045M
> Feb 10 19:57:39 weewxserver weewx[31499] DEBUG user.sdr: punt unrecognized 
> line '{"time" : "2021-02-11 00:57:36", "model" : "Acurite-6045M", "id" : 9, 
> "channel" : "C", "battery_ok" : 1, "temperature_F" : 55.200, "humidity" : 
> 62, "strike_count" : 88, "storm_dist" : 20, "active" : 1, "rfi" : 0, 
> "exception" : 0, "raw_msg" : "00096fbecff0ac14b5"}#012'
>
> what I'm confused by is that it is indicating the Acurite-6045M is an 
> unknown model. I see from one of the answers above that, at least in that 
> person's system, it is recognized. Could this be a bug in the latest 
> release of the sdr driver software?
>
> Nick Kavanagh
>
> On Wednesday, February 10, 2021 at 3:58:34 PM UTC-5 weatherl...@gmail.com 
> wrote:
>
>> Try using a wildcard:
>>
>> temperature.0009.Acurite6045M
>> temperature.*.Acurite6045M
>>
>> On 10 Feb, 2021, at 12:03, Nick Kavanagh  wrote:
>>
>> That is not working. It seems like the problem is the id number of the 
>> sensor. The Id is "9". Converting to hexadecimal, the number is9. Or 
>> with twos complement 0009. I have tried using both of these in the stanza as
>> temperature.9.AcuriteLightningPacket
>> &
>> temperature.0009.AcuriteLightningPacket
>>
>> Neither have worked. Any suggestions on what that center portion of the 
>> stanza should actually be?
>>
>> Nick Kavanagh
>>
>> On Tuesday, February 9, 2021 at 9:31:35 AM UTC-5 Andy wrote:
>>
>>> out: '{"time" : "2021-02-09 14:22:41", "model" : "Acurite-6045M", "id" : 
>>> 15431, "channel" : "A", "battery_ok" : 1, "temperature_F" : 53.200, 
>>> "humidity" : 78, "strike_count" : 174, "storm_dist" : 24, "active" : 0, 
>>> "rfi" : 1, "exception" : 0, "raw_msg" : "fc476f4e0f5cd7b8fa"}\n'
>>>
>>> parsed: {'dateTime': 1612880561, 'usUnits': 1, 
>>> 'channel.3C47.AcuriteLightningPacket': 'A', 
>>> 'temperature.3C47.AcuriteLightningPacket': 53.2, 
>>> 'battery.3C47.AcuriteLightningPacket': 0, 
>>> 'humidity.3C47.AcuriteLightningPacket': 78, 
>>> 'active.3C47.AcuriteLightningPacket': 0, 'rfi.3C47.AcuriteLightningPacket': 
>>> 1, 'exception.3C47.AcuriteLightningPacket': 0, 
>>> 'strikes_total.3C47.AcuriteLightningPacket': 174, 
>>> 'distance.3C47.AcuriteLightningPacket': 24}
>>>
>>> Try this one.
>>>
>>> Andy
>>>
>>>
>>>
>>>
>>> On Monday, February 8, 2021 at 5:41:14 AM UTC-8 kavanag...@gmail.com 
>>> wrote:
>>>
>>>>
>>>> I am running the most current versions of weewx, rtl-sdr, rtl_433, and 
>>>> Belchertown. I am attempting to add the temperature parameter from the 
>>>> 6045M to the sensor map as extraTemp2. When I run 
>>>> sudo PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/sdr.py 
>>>> --cmd="rtl_433 -M utc -F json"
>>>>  
>>>> I get this as output for the 6045M:
>>>> out:[u'{"time" : "2021-02-08 13:34:08", "model" : "Acurite-6045M", "id" 
>>>> : 9, "channel" : "A", "battery_ok" : 1, "temperature_F" : 28.900, 
>>>> "humidity" : 70, "strike_count" : 58, "storm_dist" : 12, "active" : 0, 
>>>> "rfi" : 0, "exception" : 0, "raw_msg" : "c0096fc68d691d0c1d"}\n', 
>>>> u'{"time" 
>>>> : "2021-02-08 13:34:08", "model" : "Acurite-6045M", "id" : 9, "channel" : 
>>>> "A", "battery_ok" : 1, "temperature_F" : 

Re: [weewx-user] Re: Attempting to integrate Acurite 6045M, rtl_433 does not show parsed data, cannot figure out entry for sensor map

[Nick Kavanagh]

I attempted the wildcard with several variatons on the packet name, with no 
joy. However, with debug set to 1, and log_unknown and _unmapped_sensors 
true, I am getting two lines in the log:

eb 10 19:57:39 weewxserver weewx[31499] DEBUG user.sdr: parse_json: unknown 
model Acurite-6045M
Feb 10 19:57:39 weewxserver weewx[31499] DEBUG user.sdr: punt unrecognized 
line '{"time" : "2021-02-11 00:57:36", "model" : "Acurite-6045M", "id" : 9, 
"channel" : "C", "battery_ok" : 1, "temperature_F" : 55.200, "humidity" : 
62, "strike_count" : 88, "storm_dist" : 20, "active" : 1, "rfi" : 0, 
"exception" : 0, "raw_msg" : "00096fbecff0ac14b5"}#012'

what I'm confused by is that it is indicating the Acurite-6045M is an 
unknown model. I see from one of the answers above that, at least in that 
person's system, it is recognized. Could this be a bug in the latest 
release of the sdr driver software?

Nick Kavanagh

On Wednesday, February 10, 2021 at 3:58:34 PM UTC-5 weatherl...@gmail.com 
wrote:

> Try using a wildcard:
>
> temperature.0009.Acurite6045M
> temperature.*.Acurite6045M
>
> On 10 Feb, 2021, at 12:03, Nick Kavanagh  wrote:
>
> That is not working. It seems like the problem is the id number of the 
> sensor. The Id is "9". Converting to hexadecimal, the number is9. Or 
> with twos complement 0009. I have tried using both of these in the stanza as
> temperature.9.AcuriteLightningPacket
> &
> temperature.0009.AcuriteLightningPacket
>
> Neither have worked. Any suggestions on what that center portion of the 
> stanza should actually be?
>
> Nick Kavanagh
>
> On Tuesday, February 9, 2021 at 9:31:35 AM UTC-5 Andy wrote:
>
>> out: '{"time" : "2021-02-09 14:22:41", "model" : "Acurite-6045M", "id" : 
>> 15431, "channel" : "A", "battery_ok" : 1, "temperature_F" : 53.200, 
>> "humidity" : 78, "strike_count" : 174, "storm_dist" : 24, "active" : 0, 
>> "rfi" : 1, "exception" : 0, "raw_msg" : "fc476f4e0f5cd7b8fa"}\n'
>>
>> parsed: {'dateTime': 1612880561, 'usUnits': 1, 
>> 'channel.3C47.AcuriteLightningPacket': 'A', 
>> 'temperature.3C47.AcuriteLightningPacket': 53.2, 
>> 'battery.3C47.AcuriteLightningPacket': 0, 
>> 'humidity.3C47.AcuriteLightningPacket': 78, 
>> 'active.3C47.AcuriteLightningPacket': 0, 'rfi.3C47.AcuriteLightningPacket': 
>> 1, 'exception.3C47.AcuriteLightningPacket': 0, 
>> 'strikes_total.3C47.AcuriteLightningPacket': 174, 
>> 'distance.3C47.AcuriteLightningPacket': 24}
>>
>> Try this one.
>>
>> Andy
>>
>>
>>
>>
>> On Monday, February 8, 2021 at 5:41:14 AM UTC-8 kavanag...@gmail.com 
>> wrote:
>>
>>>
>>> I am running the most current versions of weewx, rtl-sdr, rtl_433, and 
>>> Belchertown. I am attempting to add the temperature parameter from the 
>>> 6045M to the sensor map as extraTemp2. When I run 
>>> sudo PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/sdr.py 
>>> --cmd="rtl_433 -M utc -F json"
>>>  
>>> I get this as output for the 6045M:
>>> out:[u'{"time" : "2021-02-08 13:34:08", "model" : "Acurite-6045M", "id" 
>>> : 9, "channel" : "A", "battery_ok" : 1, "temperature_F" : 28.900, 
>>> "humidity" : 70, "strike_count" : 58, "storm_dist" : 12, "active" : 0, 
>>> "rfi" : 0, "exception" : 0, "raw_msg" : "c0096fc68d691d0c1d"}\n', u'{"time" 
>>> : "2021-02-08 13:34:08", "model" : "Acurite-6045M", "id" : 9, "channel" : 
>>> "A", "battery_ok" : 1, "temperature_F" : 28.900, "humidity" : 70, 
>>> "strike_count" : 58, "storm_dist" : 12, "active" : 0, "rfi" : 0, 
>>> "exception" : 0, "raw_msg" : "c0096fc68d691d0c1d"}\n', u'{"time" : 
>>> "2021-02-08 13:34:08", "model" : "Acurite-6045M", "id" : 9, "channel" : 
>>> "A", "battery_ok" : 1, "temperature_F" : 28.900, "humidity" : 70, 
>>> "strike_count" : 58, "storm_dist" : 12, "active" : 0, "rfi" : 0, 
>>> "exception" : 0, &qu

[weewx-user] Re: Attempting to integrate Acurite 6045M, rtl_433 does not show parsed data, cannot figure out entry for sensor map

[Nick Kavanagh]

That is not working. It seems like the problem is the id number of the 
sensor. The Id is "9". Converting to hexadecimal, the number is9. Or 
with twos complement 0009. I have tried using both of these in the stanza as
temperature.9.AcuriteLightningPacket
&
temperature.0009.AcuriteLightningPacket

Neither have worked. Any suggestions on what that center portion of the 
stanza should actually be?

Nick Kavanagh

On Tuesday, February 9, 2021 at 9:31:35 AM UTC-5 Andy wrote:

> out: '{"time" : "2021-02-09 14:22:41", "model" : "Acurite-6045M", "id" : 
> 15431, "channel" : "A", "battery_ok" : 1, "temperature_F" : 53.200, 
> "humidity" : 78, "strike_count" : 174, "storm_dist" : 24, "active" : 0, 
> "rfi" : 1, "exception" : 0, "raw_msg" : "fc476f4e0f5cd7b8fa"}\n'
>
> parsed: {'dateTime': 1612880561, 'usUnits': 1, 
> 'channel.3C47.AcuriteLightningPacket': 'A', 
> 'temperature.3C47.AcuriteLightningPacket': 53.2, 
> 'battery.3C47.AcuriteLightningPacket': 0, 
> 'humidity.3C47.AcuriteLightningPacket': 78, 
> 'active.3C47.AcuriteLightningPacket': 0, 'rfi.3C47.AcuriteLightningPacket': 
> 1, 'exception.3C47.AcuriteLightningPacket': 0, 
> 'strikes_total.3C47.AcuriteLightningPacket': 174, 
> 'distance.3C47.AcuriteLightningPacket': 24}
>
> Try this one.
>
> Andy
>
>
>
>
> On Monday, February 8, 2021 at 5:41:14 AM UTC-8 kavanag...@gmail.com 
> wrote:
>
>>
>> I am running the most current versions of weewx, rtl-sdr, rtl_433, and 
>> Belchertown. I am attempting to add the temperature parameter from the 
>> 6045M to the sensor map as extraTemp2. When I run 
>> sudo PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/sdr.py 
>> --cmd="rtl_433 -M utc -F json"
>>  
>> I get this as output for the 6045M:
>> out:[u'{"time" : "2021-02-08 13:34:08", "model" : "Acurite-6045M", "id" : 
>> 9, "channel" : "A", "battery_ok" : 1, "temperature_F" : 28.900, "humidity" 
>> : 70, "strike_count" : 58, "storm_dist" : 12, "active" : 0, "rfi" : 0, 
>> "exception" : 0, "raw_msg" : "c0096fc68d691d0c1d"}\n', u'{"time" : 
>> "2021-02-08 13:34:08", "model" : "Acurite-6045M", "id" : 9, "channel" : 
>> "A", "battery_ok" : 1, "temperature_F" : 28.900, "humidity" : 70, 
>> "strike_count" : 58, "storm_dist" : 12, "active" : 0, "rfi" : 0, 
>> "exception" : 0, "raw_msg" : "c0096fc68d691d0c1d"}\n', u'{"time" : 
>> "2021-02-08 13:34:08", "model" : "Acurite-6045M", "id" : 9, "channel" : 
>> "A", "battery_ok" : 1, "temperature_F" : 28.900, "humidity" : 70, 
>> "strike_count" : 58, "storm_dist" : 12, "active" : 0, "rfi" : 0, 
>> "exception" : 0, "raw_msg" : "c0096fc68d691d0c1d"}\n'
>>
>> There is no parsed output.
>>
>> My question is: What do I add in my sensor map as the stanza for 
>> temperature_F to be mapped to extraTemp2? 
>> So far I have attempted multiple versions including:
>> temperature.0009.Acurite6045M
>> temperature_F.0009.Acurite6045M
>> both again as Acurite6045MV2
>>
>> both again as AcuriteLightningPacket
>>
>> both again as AcuriteLightningPacketV2
>>
>> as well as several other variations.
>>
>> Does anyone know how to identify the packet from the 6045M?
>>
>> Thank you,
>> Nick Kavanagh
>> stonecressweather(dot)ddns(dot)net
>>
>> (Apologies if this question was not well asked. Any tips on improving the 
>> question are greatly appreciated.)
>>
>>
>>

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

[weewx-user] Attempting to integrate Acurite 6045M, rtl_433 does not show parsed data, cannot figure out entry for sensor map

[Nick Kavanagh]

I am running the most current versions of weewx, rtl-sdr, rtl_433, and 
Belchertown. I am attempting to add the temperature parameter from the 
6045M to the sensor map as extraTemp2. When I run 
sudo PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/sdr.py 
--cmd="rtl_433 -M utc -F json"
 
I get this as output for the 6045M:
out:[u'{"time" : "2021-02-08 13:34:08", "model" : "Acurite-6045M", "id" : 
9, "channel" : "A", "battery_ok" : 1, "temperature_F" : 28.900, "humidity" 
: 70, "strike_count" : 58, "storm_dist" : 12, "active" : 0, "rfi" : 0, 
"exception" : 0, "raw_msg" : "c0096fc68d691d0c1d"}\n', u'{"time" : 
"2021-02-08 13:34:08", "model" : "Acurite-6045M", "id" : 9, "channel" : 
"A", "battery_ok" : 1, "temperature_F" : 28.900, "humidity" : 70, 
"strike_count" : 58, "storm_dist" : 12, "active" : 0, "rfi" : 0, 
"exception" : 0, "raw_msg" : "c0096fc68d691d0c1d"}\n', u'{"time" : 
"2021-02-08 13:34:08", "model" : "Acurite-6045M", "id" : 9, "channel" : 
"A", "battery_ok" : 1, "temperature_F" : 28.900, "humidity" : 70, 
"strike_count" : 58, "storm_dist" : 12, "active" : 0, "rfi" : 0, 
"exception" : 0, "raw_msg" : "c0096fc68d691d0c1d"}\n'

There is no parsed output.

My question is: What do I add in my sensor map as the stanza for 
temperature_F to be mapped to extraTemp2? 
So far I have attempted multiple versions including:
temperature.0009.Acurite6045M
temperature_F.0009.Acurite6045M
both again as Acurite6045MV2

both again as AcuriteLightningPacket

both again as AcuriteLightningPacketV2

as well as several other variations.

Does anyone know how to identify the packet from the 6045M?

Thank you,
Nick Kavanagh
stonecressweather(dot)ddns(dot)net

(Apologies if this question was not well asked. Any tips on improving the 
question are greatly appreciated.)


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