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

[Nick Name]

Goddam auto correct!

On Friday, February 23, 2024 at 9:46:09 AM UTC Nick Name wrote:

> Noobs Journey:
> So probably not precisely what you are look for but.
>
> R.Pi 5 with weewx logging from Davis VP2.
> Disastrous early attempts - but starting from scratch (New Pi (NVME rather 
> than SD card) fresh installs of OS & package install of weewx plus support 
> software (php, MariaDB etc))
> Running 24/7 for 3 weeks now. Zero issues, much happy.
>
> Slowly working my way through documentation and customisation.
> Current "Ultimate Objectives" 
> 1) Figure out how to render wind data on polar display (graph?),
> 2) Skin (or custom web page)  reproducing console display of Davis unit,
>
> Just to add - have previous experience with Oregon Scientific units and 
> meteobridge + numerous other weather logging software.
>
> Current impression is that the new whew based setup offers the best set of 
> options yet .. but more data to collect and work to do.
>
> Regards.
> Frank C.
>
> On Friday, February 23, 2024 at 6:25:49 AM UTC michael.k...@gmx.at wrote:
>
>> I'm curious what hardware you are running WeeWX on, and your experience 
>> with it. So, this is not about the weather station and the sensors, but the 
>> device which is running the service. The reason I ask this here, is because 
>> the issues I experienced with my hardware might be related to weewx and 
>> writing it's logs, and we all know the first rule for posting a question 
>> here :D
>>
>> Since my first WeeWX installation in 2015, I've been using every 
>> generation of the RaspberryPi B, except for the 5th. But looking back it, 
>> has sometimes has been a royal PITA. It's not that I consider the Pi being 
>> bad at all, but I've been having issues with whatever storage I've been 
>> using. SD-Cards were a total disaster, USB flash drives were slightly 
>> better, USB attached SSDs, at least, lasted more than two years before 
>> being attached to the Pi killed them. The only type that didn't fail so 
>> far, was a NFS provided by a QNAP NAS, but this Kind of setup is a bit 
>> complex to maintain, and starting the NAS over, means quite a bit of 
>> downtime for the Pi also.
>>
>> The Pi never was intended to be a server running 24/7, considering this, 
>> it's success in being used as such, is beyond imagination. Anyway, my 
>> experience for the Pi being a storage killer, doesn't seem to be uncommon. 
>> It's original intention was satisfied: I learned a lot about how not to 
>> lose data with unreliable hardware. Since 2015, my database isn't missing 
>> more than one archive value a day in average and the longest gap is about 
>> two hours back in early 2016, using the standard interval of 5 minutes.
>>
>> What hardware are you using, what is your experience?
>> Can you suggest hardware with low power consumption as a requirement?
>> What about the newest generation, like Intel n100 based systems? 
>>
>

-- 
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/d1618d42-752f-41ee-84d3-0f7b5d11b1a4n%40googlegroups.com.

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

[Nick Name]

Noobs Journey:
So probably not precisely what you are look for but.

R.Pi 5 with weewx logging from Davis VP2.
Disastrous early attempts - but starting from scratch (New Pi (NVME rather 
than SD card) fresh installs of OS & package install of weewx plus support 
software (php, MariaDB etc))
Running 24/7 for 3 weeks now. Zero issues, much happy.

Slowly working my way through documentation and customisation.
Current "Ultimate Objectives" 
1) Figure out how to render wind data on polar display (graph?),
2) Skin (or custom web page)  reproducing console display of Davis unit,

Just to add - have previous experience with Oregon Scientific units and 
meteobridge + numerous other weather logging software.

Current impression is that the new whew based setup offers the best set of 
options yet .. but more data to collect and work to do.

Regards.
Frank C.

On Friday, February 23, 2024 at 6:25:49 AM UTC michael.k...@gmx.at wrote:

> I'm curious what hardware you are running WeeWX on, and your experience 
> with it. So, this is not about the weather station and the sensors, but the 
> device which is running the service. The reason I ask this here, is because 
> the issues I experienced with my hardware might be related to weewx and 
> writing it's logs, and we all know the first rule for posting a question 
> here :D
>
> Since my first WeeWX installation in 2015, I've been using every 
> generation of the RaspberryPi B, except for the 5th. But looking back it, 
> has sometimes has been a royal PITA. It's not that I consider the Pi being 
> bad at all, but I've been having issues with whatever storage I've been 
> using. SD-Cards were a total disaster, USB flash drives were slightly 
> better, USB attached SSDs, at least, lasted more than two years before 
> being attached to the Pi killed them. The only type that didn't fail so 
> far, was a NFS provided by a QNAP NAS, but this Kind of setup is a bit 
> complex to maintain, and starting the NAS over, means quite a bit of 
> downtime for the Pi also.
>
> The Pi never was intended to be a server running 24/7, considering this, 
> it's success in being used as such, is beyond imagination. Anyway, my 
> experience for the Pi being a storage killer, doesn't seem to be uncommon. 
> It's original intention was satisfied: I learned a lot about how not to 
> lose data with unreliable hardware. Since 2015, my database isn't missing 
> more than one archive value a day in average and the longest gap is about 
> two hours back in early 2016, using the standard interval of 5 minutes.
>
> What hardware are you using, what is your experience?
> Can you suggest hardware with low power consumption as a requirement?
> What about the newest generation, like Intel n100 based systems? 
>

-- 
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/2cfe7e80-abcd-42a2-b818-71dcec4e80cbn%40googlegroups.com.

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.

Re: [weewx-user] Advice on replacement WxStn

[Nick Norman]

On 28/12/2021 11:22, Rainer Lang wrote:

Hi Nick
If you want to go with the FOSHK/Ecowitt ecosystem, have a look at their 
offers

(www.ecowitt.com) and what can be combined/extended with what
(https://www.wxforum.net/index.php?topic=40730.0) and what a different 
brands of the same stations

- you need to register in order to see pictures.
In the UK stations are sold via https://www.amazon.co.uk and 
https://weatherspares.co.uk/, also via

https://www.nevadaradio.co.uk/ (Watson 8686)



Many thanks for that Rainer,

Ecowitt/FOSHK only because the cost of a Davies if out of my budget :-(

As long as it works nicely with Weewx that is all that is needed, extra 
sensors might be 'fun'.  The 'works' could be USB or network (Ethernet 
or WiFi) ... the console will be near the wifi AP so ...


The 'search facility' on Amazon is pitiful to say the least, I'm sure it 
is designed to attract the "Ooo shiny" brigade I find it infuriating - 
must be getting old ... :-)


A bit of searching needed I think

Regards

Nick
M0HGU

--
History has a habit of changing the people who think they are changing
it. (Mort)
Tue 10346 Sep 12:25:01 GMT 1993
12:25:01 up 16 days, 1:53, 6 users, load average: 1.34, 1.49, 1.17

--
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/09e51de3-fae4-bfd1-6d6f-a0ea568a7571%40dctower.co.uk.


OpenPGP_signature
Description: OpenPGP digital signature

[weewx-user] Advice on replacement WxStn

[Nick Norman]

Afternoon to all the collective wisdom here,

The current WxStn (a WH3080 - by froggit, but seems ot be a fine offset) 
is playing silly beggars!


The console is not displaying temp/humidity not wind, but is showing luc 
& UV and Weewx reckons it is either not there or disconnected



ERROR weewx.drivers.fousb: get_observations failed: [Errno 19] No such 
device (it may have been disconnected)



and/or


INFO weewx.drivers.fousb: station status {'unknown': 0, 
'lost_connection': 64, 'rain_overflow': 0} (64)



The usual dance of power cycling the console results in no change.

A couple of week ago it did it and I went on the roof and changed the 
batteries, pressed reset and it sill did not work, so back up - take it 
all down, dry (it was not really wet) clean with alcohol and put back - 
still nothing.


I then gave up, powered down the console & stopped Weewx, about 24hrs 
later restarted everything and it worked ...


I've just repeated the dance and nothing ...

Thus the qeustions

a) any ideas?

b) replace but with what?  Thought about a GW1000 based like

<https://www.amazon.co.uk/Wireless-Weather-Station-WeatherSleuth%C2%AE-Professional/dp/B00ZVFZUS6/ref=sr_1_23?crid=TG5JW32AXSSY=ecowitt+gw1002=1640614990=gw1002%2Caps%2C161=8-23> 


or
<https://www.amazon.co.uk/Ecowitt-Wireless-Weather-Station-Built/dp/B0991GVBYK/ref=sr_1_2?crid=TG5JW32AXSSY=ecowitt+gw1002=1640614990=gw1002%2Caps%2C161=8-2>

Thoughts, ideas, suggestions ...

Many thanks

Happy seasonal things etc. & stay safe

Nick
M0HGU

--
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/692b0d75-451f-b158-c4a0-d23d7f405936%40dctower.co.uk.


OpenPGP_signature
Description: OpenPGP digital signature

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

[weewx-user] anyone using Wet Bulb Temperature ?

[Nick DeRoda]

I just set up a station at a Ski Area - we would also like to display "wet 
bulb" temperature we are using a Davis Vantage Pro 2.

Has anyone done this ? all help is appreachated.


-- 
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/f3525396-fd89-480d-ba8f-f1d1c6da3803n%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.

Re: [weewx-user] Fineoffset WH3080 failure???

[Nick Norman]

On 10/08/2020 12:28, Nick Norman wrote:
> Afternoon all,
> 
> Setup:
> 



Braved the loft and ... no data from the outside unit, but screen showed
inside data - however the weewx driver could not see anything,

Went on the roof (bungalow but still ...) all looked OK, checked the
batteries, find 'alkaline' rechargeable - never heard of.  Changed them
for normal NiMH and did the reset dance.

Nothing, gave up in disgust and over heated.



Just looked now and it is all back working ...

So was it dodgy batteries?

Will the normal NiMH be OK?

Nick
M0HGU

-- 
Not only did I wipe Lemmings from my hard disc, I overwrote it so's I
couldn't get it back.
(alt.fan.pratchett)
17:40:01 up 2 days, 38 min, 9 users, load average: 5.69, 5.85, 5.92

-- 
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/bd29f269-7e45-d3a8-ae5b-58e9eb3bc401%40dctower.co.uk.


signature.asc
Description: OpenPGP digital signature

[weewx-user] Fineoffset WH3080 failure???

[Nick Norman]

 for hub 1-1.2 [2001:f103, USB
2.00, 7 ports]
Aug 10 12:23:44 bragi bash: Port 4: 0303 power lowspeed enable connect
[1941:8021]
Aug 10 12:23:44 bragi bash: Sent power off request
Aug 10 12:23:44 bragi bash: New status for hub 1-1.2 [2001:f103, USB
2.00, 7 ports]
Aug 10 12:23:44 bragi bash: Port 4:  off
Aug 10 12:24:14 bragi bash: Current status for hub 1-1.2 [2001:f103, USB
2.00, 7 ports]
Aug 10 12:24:14 bragi bash: Port 4:  off
Aug 10 12:24:14 bragi bash: Sent power on request
Aug 10 12:24:14 bragi bash: New status for hub 1-1.2 [2001:f103, USB
2.00, 7 ports]
Aug 10 12:24:14 bragi bash: Port 4: 0100 power
Aug 10 12:24:14 bragi powercycling: USB port
Aug 10 12:24:14 bragi kernel: usb 1-1.2.4: USB disconnect, device number 59
Aug 10 12:24:14 bragi kernel: usb 1-1.2.4: new low-speed USB device
number 60 using ehci-pci
Aug 10 12:24:14 bragi kernel: usb 1-1.2.4: New USB device found,
idVendor=1941, idProduct=8021
Aug 10 12:24:14 bragi kernel: usb 1-1.2.4: New USB device strings:
Mfr=0, Product=0, SerialNumber=0
Aug 10 12:24:14 bragi kernel: hid-generic 0003:1941:8021.0035:
hiddev0,hidraw1: USB HID v1.00 Device [HID 1941:8021] on
usb-:00:1a.0-1.2.4/input0
Aug 10 12:24:44 bragi journal: weewx[11443]/ERROR weewx.drivers.fousb:
get_observations failed: [Errno 19] No such device (it may have been
disconnected)


Ideas?

Many thanks in advance, any questions - ask.

Regards & stay safe all,

Nick
M0HGU


-- 
No wizard would normally dream of giving a colleague a leg up unless it
was in order to catch them on the hop.
(Sourcery)
12:10:01 up 1 day, 19:08, 9 users, load average: 6.02, 5.83, 5.79

-- 
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/7eb65c8a-dae2-3a23-de34-0fda83717a8b%40dctower.co.uk.


signature.asc
Description: OpenPGP digital signature

[weewx-user] Sending data from WS-1001-Wifi to weewx

[Nick Langan]

Hi all,
I apologize for a topic that probably has already been covered in 
detail...I attempted to conduct a thorough search of my options but I am a 
little confused so I just wanted to see if I could gain some clarity.  I 
have an Ambient Weather WS-1001-Wifi that has been running for several 
years.  A friend's recent addition of weewx to their weather station 
(different brand) got me intrigued and I wanted to see if I could link the 
software with my 1001.  I have it all installed in Ubuntu but now of course 
I run into the issue with finding the best method to get data from the 
1001.  Far as I can tell, my best options are:

1.  Use a driver like this one to obtain the data via Wi-Fi.  However, I 
suspect there must be an issue with this driver and python3 (which weewx v4 
runs on):  https://github.com/AussieSusan/HP1000  I could not get the 
HP1000 driver to show up in the list of drivers after re-running the weewx 
configuration script.  Has anyone had success with this driver and python3 
or is there possibly another driver out there for the HP1000 wx stations?

2.  Would adding an Ecowitt GW1000 to the WS-1001 be my best option?  I 
just haven't been able to confirm that the GW1000 is in fact compatible 
with the WS-1001.  Does anyone know if the GW1000 plugs in directly to the 
weather station itself or the console?  

I sincerely appreciate any insights!

Thank you,
Nick Langan
Tabernacle, NJ

-- 
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/ed6f4f38-712e-47ed-a5c2-948ff1a3baba%40googlegroups.com.

[weewx-user] MQTT setup issues

[Nick]

Hi,

I have been using WeeWx for several years to upload my data to 
Wunderground.  I am trying to configure MQTT so that I can pull the 
information directly into my Home Automation system.  When I try to 
configure using these (https://github.com/weewx/weewx/wiki/mqtt) 
instructions, it does not work and I get the following in the log:

Feb 18 09:22:56 raspberrypi weewx[352]: engine: Caught unrecoverable 
exception in engine:
Feb 18 09:22:56 raspberrypi weewx[352]:   __init__() got an 
unexpected keyword argument 'enable'
Feb 18 09:22:56 raspberrypi weewx[352]:   Traceback (most recent 
call last):
Feb 18 09:22:56 raspberrypi weewx[352]: File 
"/usr/share/weewx/weewx/engine.py", line 888, in main
Feb 18 09:22:56 raspberrypi weewx[352]:   engine = 
engine_class(config_dict)
Feb 18 09:22:56 raspberrypi weewx[352]: File 
"/usr/share/weewx/weewx/engine.py", line 78, in __init__
Feb 18 09:22:56 raspberrypi weewx[352]:   
self.loadServices(config_dict)
Feb 18 09:22:56 raspberrypi weewx[352]: File 
"/usr/share/weewx/weewx/engine.py", line 142, in loadServices
Feb 18 09:22:56 raspberrypi weewx[352]:   
self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
Feb 18 09:22:56 raspberrypi weewx[352]: File 
"/usr/share/weewx/user/mqtt.py", line 240, in __init__
Feb 18 09:22:56 raspberrypi weewx[352]:   self.archive_thread = 
MQTTThread(self.archive_queue, **site_dict)
Feb 18 09:22:56 raspberrypi weewx[352]:   TypeError: __init__() got 
an unexpected keyword argument 'enable'
Feb 18 09:22:56 raspberrypi weewx[352]:   Exiting.

I am using a Pi Zero W running raspbian buster lite and python version 
2.7.16.  WeeWx was installed using these (http://weewx.com/docs/debian.htm) 
instructions.  Station hardware is an an Acu-Rite 02032C hooked up via USB.

Configuration info I have is:

[[MQTT]]
enable = true
server_url = mqtt://mqtt:mqttpassword@192.168.3.9:1883/
topic = weather
unit_system = US

and 

[Engine]

[[Services]]
# This section specifies the services that should be run. They are
# grouped by type, and the order of services within each group
# determines the order in which the services will be run.
prep_services = weewx.engine.StdTimeSynch
data_services = ,
process_services = weewx.engine.StdConvert, 
weewx.engine.StdCalibrate, weewx.engine.StdQC, 
weewx.wxservices.StdWXCalculate
archive_services = weewx.engine.StdArchive
restful_services = weewx.restx.StdStationRegistry, 
weewx.restx.StdWunderground, weewx.restx.StdPWSweather, 
weewx.restx.StdCWOP, weewx.restx.StdWOW, weewx.restx.StdAWEKAS, 
user.mqtt.MQTT
report_services = weewx.engine.StdPrint, weewx.engine.StdReport


Thanks in advance for the time and assistance.

-- 
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/7d186986-7326-4636-b472-0f294161843d%40googlegroups.com.

Re: [weewx-user] Re: WS3080 Lockup - FineOffsetUsb workaround not working.

[Nick]

On 24/06/2019 18:57, Dave, G1OGY wrote:
> 
> 
> On Sunday, 23 June 2019 10:21:29 UTC+1, Nick wrote:
>>
>>
>>
>> Very many thanks 
>>
>>
> You (and all) are welcome.
> 
> Been thinking (bad habit)...
> add to the end of `powercycleusb` - should be OK while `monitor...` is 
> running
> 
> logger -t powercycleusb USB port  - power cycled
> 
> the logger(1) adds the date/time 
> 

:-)

I just got it to send me an email - not had a failure yet ... but it
works as a dry run.

Regards all

Nick
M0HGU

-- 
'You've got the loudest silences I ever did hear from anyone who wasn't
dead!'
(Lords and Ladies)
19:10:01 up 9 days, 9:08, 8 users, load average: 1.05, 1.04, 0.77

-- 
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/2d4411bf-0e11-69dc-442a-d006055c2219%40dctower.co.uk.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [weewx-user] Re: WS3080 Lockup - FineOffsetUsb workaround not working.

[Nick]

On 23/06/2019 09:03, Dave, G1OGY wrote:
> 
> 
> On Sunday, 9 June 2019 13:33:54 UTC+1, Nick wrote:
>>
>> On 09/06/2019 05:51, 'Johannes Ebner' via weewx-user wrote: 
>>> I still have this issue. For me it seems that the Power-Cycle 
>>> Implementation in WeeWx is broken. 
>>>
>>
>> Hi, 
>>
>> I am in the same boat :-( 
>>
>>
>> Likewise.
> 
> I have just implemented a couple of scripts to use `uhubctrl` (which does 
> control the RPi's USB port):
> 
>#!/bin/bash
># monitorlockup
># watch the weewx log file for lockup condition and use USB power 
> recycling to clear the lockup
># 20190622
>   
>LOGfile="/weewx.log"
>tail -Fn0 $LOGfile |
>while read line ; do
>echo "$line" | grep -q "Errno 110"
>   if [ $? = 0 ]
>   then
>   /home/weewx/powercycleusb
>   fi
>   done
> 
> And
> 
>#!/bin/bash
># powercycleusb
> 
>/uhubctl -a off -p2
>sleep 45
>/uhubctl -a on -p2
> 
> Both scripts are executable, owned by root and also setuid root.
> `monitorlockup` will run from /etc/rc.local on boot (I trust).
> 
> Note: The -F (CAPS) in `tail` should track the logfile despite any log 
> rotation.
> 
> It is possible that the 45 second `sleep` could be reduced.  
> My logs show approx 2 minutes between the first (of 4) prints of [`Errno 
> 110]` 
> so I hope to have the console restarted and stable before `weewx` resets 
> itself.
> 
> Does it work?  Time will tell... 
> 
Dave,

Very many thanks

The bit of the puzzle (& confess I'd not looked hard) was how tp parse
the log file - easily (& not read ALL of it each time and keep count or
numbers of errors etc. etc. etc.)

Now in place on my system (not a Pi) and not yet rebooted as it is also
the system for WxSat images (EuMetCast MSG)

Thanks again

Nick
(who really ought to read 'man $CMD' more often)
p.s. I see the cookie monster is reading my emails again :-)

-- 
"But you read a lot of books, I'm thinking. Hard to have faith, ain't
it, when you've read too many books?"
(Carpe Jugulum)
10:15:02 up 8 days, 13 min, 8 users, load average: 0.83, 0.93, 0.91

-- 
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/4f43285d-565e-b284-9dc6-2ecb92324bd0%40dctower.co.uk.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [weewx-user] Re: WS3080 Lockup - FineOffsetUsb workaround not working.

[Nick]

On 09/06/2019 05:51, 'Johannes Ebner' via weewx-user wrote:
> I still have this issue. For me it seems that the Power-Cycle 
> Implementation in WeeWx is broken.
> 

Hi,

I am in the same boat :-(

I am not sure if it is the power cycling in weewx or (here at least) the
implementation of the sub-system used

If I run the usb_control program I get:



sudo python ./usb_control-0.6.py
Traceback (most recent call last):
  File "./usb_control-0.6.py", line 191, in 
main()
  File "./usb_control-0.6.py", line 188, in main
scan()
  File "./usb_control-0.6.py", line 73, in scan
print "device at %s:%03d" % (bus.dirname, dev.devnum)
TypeError: %d format: a number is required, not NoneType



So obviously it won't work ...

However uhubctl work 100% - I am at a loss ...

Any help would be appreciated.

Regards/73

Nick
M0HGU


-- 
The truth may be out there, but lies are inside your head.
(Hogfather)
13:25:02 up 10 days, 1:57, 10 users, load average: 0.81, 0.83, 1.04

-- 
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/1baa272f-282b-cef2-4977-c230d8d4fb5b%40dctower.co.uk.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[weewx-user] Problem with power cycling fineoffset system (long)

[Nick]

 issue to fix ? - I 'hate' centos but it is what works with the
Wx satellite Rx stuff).

Ideas?

If you need more infor - ask

Regards

Nick
M0HGU
-- 
What your soldier wants
-- really, really wants -- is no-one shooting
back at him.
(alt.fan.pratchett)
10:35:01 up 23 days, 13:54, 10 users, load average: 0.42, 0.49, 0.55

-- 
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/80147f95-f939-1567-c2c1-10541c9d8d91%40dctower.co.uk.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [weewx-user] Missing graph since upgrade to 3.7.1

[Nick Mason]

Tom, 

thank you, those two lines of code were missing from skin.conf and from the 
backup. 

Just to prove I wasn't going mad I put the original SD card back in the RPi 
and they are there! 

I also had to add the code to the monthly and yearly sections, modified 
accordingly. 

How they got removed from the backup I have no idea, it seems too specific 
for corruption during the backup but stranger things have happened

Regards 
Nick

On Tuesday, 2 May 2017 22:55:35 UTC+1, Tom Keffer wrote:
>
> If other images are being generated, but only the dayhumidity.png image is 
> missing, the problem must be in the skin.conf file. If you did a Debian 
> install, it will be located in /etc/weewx/skins/Standard/skin.conf
>
> The relevant section should look something like this:
>
>
> ...
> [[[daytempchill]]]
> windchill
> heatindex
>
> [[[dayhumidity]]]
> outHumidity
>
> [[[dayrain]]]
> # Make sure the y-axis increment is at least 0.02 for the rain 
> plot
> yscale = None, None, 0.02
> plot_type = bar
> rain
> aggregate_type = sum
> aggregate_interval = 3600
> label = Rain (hourly total)
> ...
>
>
>
> On Tue, May 2, 2017 at 9:57 AM, Nick Mason <nick@gmail.com 
> > wrote:
>
>> I've had a small but nagging problem for a while with my Raspberry Pi 
>> that runs weewx. When I try to upgrade rasbian I get an error message.
>>
>> I'm not sure if I get a partial upgrade or no upgrade following a;
>>
>> sudo apt-get update
>> sudo apt-get upgrade
>>
>> I finally got around to sorting it out by by creating a new MicroSD card 
>> with the latest rasbian image. I then decide that along with the latest OS 
>> that I'd do a fresh install of weewx as well and this time rather than do a 
>> manual download and install using setup.py I would install weewx via 
>> apt-get install weewx.
>>
>> All went well, it's a lot easier than the manual method and it worked as 
>> advertised. I then replaced the new database with the one from my backup 
>> and weewx dutifully brought it up to date. However, I noticed that the 
>> graphs on the web page were staggered and out of alignment and that this 
>> was because one of the graphs, Outside Humidity, is missing. All that shows 
>> is a small box with 'outside humidity' in it.
>>
>> I've had a look through the code and what should be displayed is the 
>> dayhumidity.png image. This image isn't being generated and does not appear 
>> in /var/www/html/weewx
>>
>> I've compared the new weewx.conf and skin.conf files with the backups I 
>> have from the older version and they look the same.
>>
>> Can someone point me at where the report is generated and the image file 
>> produced please so I can have a look at what's going on.
>>
>> 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Missing graph since upgrade to 3.7.1

[Nick Mason]

I've had a small but nagging problem for a while with my Raspberry Pi that 
runs weewx. When I try to upgrade rasbian I get an error message.

I'm not sure if I get a partial upgrade or no upgrade following a;

sudo apt-get update
sudo apt-get upgrade

I finally got around to sorting it out by by creating a new MicroSD card 
with the latest rasbian image. I then decide that along with the latest OS 
that I'd do a fresh install of weewx as well and this time rather than do a 
manual download and install using setup.py I would install weewx via 
apt-get install weewx.

All went well, it's a lot easier than the manual method and it worked as 
advertised. I then replaced the new database with the one from my backup 
and weewx dutifully brought it up to date. However, I noticed that the 
graphs on the web page were staggered and out of alignment and that this 
was because one of the graphs, Outside Humidity, is missing. All that shows 
is a small box with 'outside humidity' in it.

I've had a look through the code and what should be displayed is the 
dayhumidity.png image. This image isn't being generated and does not appear 
in /var/www/html/weewx

I've compared the new weewx.conf and skin.conf files with the backups I 
have from the older version and they look the same.

Can someone point me at where the report is generated and the image file 
produced please so I can have a look at what's going on.

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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: spikes in rain data

[Nick La Galle]

Thanks, that worked to display the headers.. 

dateTime|min|mintime|max|maxtime|sum|count|wsum|sumtime
1484398800|0.0|1484398842|14.51574801669|1484423589|14.51574801669|224|14.51574801669|224

thats from archive_day_rain

I think the 14.5157... is the rain in inches.. 

On Thursday, 12 January 2017 01:10:11 UTC+11, Andrew Milner wrote:
>
> Try
> .headers on
> select * from archive;  .etc etc
>
> also there are the meta commands
> .tables
> and
> .schema archive or .schema archive_day_rain.. etc 
> etc etc
>
>
>
> On Wednesday, 11 January 2017 15:47:32 UTC+2, Nick La Galle wrote:
>
>> I tried that but I didn't get any column headings.. I'm running it on a 
>> Synology NAS so hoping not to install too many other packages. on top of 
>> whats there.
>>
>> On Sunday, 8 January 2017 15:49:24 UTC+11, Andrew Milner wrote:
>>>
>>> if you do select * from archive you should get the column headings - 
>>> what are you having a problem interpreting?
>>>
>>> You may find it more user friendly to install and use  phpliteadmin to 
>>> access and look at the database and its tables.
>>>
>>>
>>>
>>> .
>>>
>>> On Sunday, 8 January 2017 06:04:40 UTC+2, Nick La Galle wrote:
>>>
>>>> Hi all,
>>>>
>>>> I've been having issues with some spikes in the rate data which I think 
>>>> was caused by the unit playing up. I want to delete these instances of it 
>>>> but I cannot work out how/what I need to do and most of the details I have 
>>>> seen relate to say temperatures. 
>>>>
>>>> I can access the db etc but when i view the table for daily rain I have 
>>>> no idea how it decipher it..
>>>>
>>>>
>>>> 1483275600|0.0|1483275659|0.141732283319983|1483281456|2.3622047211|360|2.3622047211|360
>>>> 1483362000|0.0|1483362059|0.0|1483362059|0.0|360|0.0|360
>>>> 1483448400|0.0|1483448458|0.0|1483448458|0.0|360|0.0|360
>>>>
>>>> 1483534800|0.0|1483534858|0.0472440944400242|1483574315|0.377952755520104|360|0.377952755520104|360
>>>> 1483621200|0.0|1483621237|0.0|1483621237|0.0|253|0.0|253
>>>> 1483707600|0.0|1483707745|0.0|1483707745|0.0|353|0.0|353
>>>> 1483794000|0.0|1483794053|0.0|1483794053|0.0|225|0.0|225
>>>>
>>>> If someone has some tips on how to read it that would be great!
>>>>
>>>> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] spikes in rain data

[Nick La Galle]

Hi all,

I've been having issues with some spikes in the rate data which I think was 
caused by the unit playing up. I want to delete these instances of it but I 
cannot work out how/what I need to do and most of the details I have seen 
relate to say temperatures. 

I can access the db etc but when i view the table for daily rain I have no 
idea how it decipher it..

1483275600|0.0|1483275659|0.141732283319983|1483281456|2.3622047211|360|2.3622047211|360
1483362000|0.0|1483362059|0.0|1483362059|0.0|360|0.0|360
1483448400|0.0|1483448458|0.0|1483448458|0.0|360|0.0|360
1483534800|0.0|1483534858|0.0472440944400242|1483574315|0.377952755520104|360|0.377952755520104|360
1483621200|0.0|1483621237|0.0|1483621237|0.0|253|0.0|253
1483707600|0.0|1483707745|0.0|1483707745|0.0|353|0.0|353
1483794000|0.0|1483794053|0.0|1483794053|0.0|225|0.0|225

If someone has some tips on how to read it that would be great!

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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Graphs with 2 different y-axis

[Nick Mason]

You can produce both the graphs you want Python by importing various 
libraries like;

matplotlib
numpi
sqlite

Then you can embed the SQL you need into the Python to get the data you 
wish to graph and use the matplotlib and numpi functions to graph the data
however you want it. 

Nick
 

On Sunday, 7 August 2016 14:38:45 UTC+1, Ralf Buck wrote:
>
> hello
>
> i want a graph with 2 different units
>
> [[[daybarometer]]]
> barometer
> outHumidity
>
> the graph show only the first unit on the left side.
> how can i add a second unit to the right side?
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.