[weewx-user] Re: How to use SQlite database to generate date to date images ?

[storm...@gmail.com]

Take a look at Belchertown skin:

https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation

https://github.com/poblabs/weewx-belchertown

On Saturday, January 7, 2023 at 10:35:47 AM UTC-5 jlk...@gmail.com wrote:

> Hello all !
> I'use a small station using weewx with an sdr key
>  . It has the standard skin that gives me pictures for last day, week, 
> month and year . 
>
> I'm searching for a solution to generate images from "old" months or " 
> date to date " 
> ex : today i'd like to generate a picture with temperature from 2021/07/01 
> to 2021/07/31 .
>
> Do you know an external software, a weewx-plugin or maybe another 
> weewx-skin that can extract the datas in the sqlite database and generate 
> the picture ? 
> Hope you have an idea ! 
>
> have a nice WE ! 
>

-- 
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/46c814d8-c522-4b2f-8b20-9c0d0f22ac38n%40googlegroups.com.

[weewx-user] Re: How to use SQlite database to generate date to date images ?

[storm...@gmail.com]

Take a look at belchertown skin:

https://github.com/poblabs/weewx-belchertown

On Saturday, January 7, 2023 at 10:35:47 AM UTC-5 jlk...@gmail.com wrote:

> Hello all !
> I'use a small station using weewx with an sdr key
>  . It has the standard skin that gives me pictures for last day, week, 
> month and year . 
>
> I'm searching for a solution to generate images from "old" months or " 
> date to date " 
> ex : today i'd like to generate a picture with temperature from 2021/07/01 
> to 2021/07/31 .
>
> Do you know an external software, a weewx-plugin or maybe another 
> weewx-skin that can extract the datas in the sqlite database and generate 
> the picture ? 
> Hope you have an idea ! 
>
> have a nice WE ! 
>

-- 
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/ea1f7eb5-3779-4cae-a154-9691675e9aa9n%40googlegroups.com.

Re: [weewx-user] Davis VP2 reliability with Rasp Pi zero

[storm...@gmail.com]

Would also look at adding a DS1307 or DS3231 RTC Module to RPI zero. This 
should maintain the time when the RPI zero loses power.

On Friday, January 6, 2023 at 7:59:16 AM UTC-5 tke...@gmail.com wrote:

> If weewx causes the corruption, I sure don't see how. It operates well 
> within the published API provided by Davis. 
>
> Graham is probably right: a power spike from when power comes on is likely 
> the problem. It's coming through either the VP2 power supply or, more 
> likely, the Pi's. 
>
> Try at least a surge suppressor. A UPS would be even better.
>
> On Thu, Jan 5, 2023 at 5:46 PM iams...@gmail.com  
> wrote:
>
>> "What happens if you 'pull the plug' on your VP2? Does it keep running? 
>> Perhaps the batteries are bad?
>>
>> Yes, it keeps running, that is why it seems to be a weewx issue to me. In 
>> other words, if the Pi Zero running weewx were not connected to the VP2, 
>> the data logger memory would not get corrupted. In fact, weewx is able to 
>> recover data that was gathered during the power outage (while the Pi is 
>> shut down). It is only when power is *restored *that the data logger 
>> corruption happens. At least I assume that is really the root of the issue, 
>> I really don't know. All I know is that almost every time the power goes 
>> out, I get the record time error and all data recording and uploading stops.
>>
>> I've looked into getting a UPS for the Pi, which really appears to be 
>> nothing more than a $15 ext phone battery, but it seems to me this is a 
>> weewx problem that should be addressed. Alternately, I can contact Davis to 
>> see what they say.
>> "
>>
>> On Thursday, January 5, 2023 at 3:34:40 PM UTC-8 tke...@gmail.com wrote:
>>
>>> It should work.
>>>
>>> What happens if you 'pull the plug' on your VP2? Does it keep running? 
>>> Perhaps the batteries are bad?
>>>
>>> Personally, I use a UPS for both the weewx server and the VP2 and 
>>> haven't had a memory corruption problem in at least a decade. So, you could 
>>> try that.
>>>
>>>
>>>
>>>
>>> On Thu, Jan 5, 2023 at 11:30 AM iams...@gmail.com  
>>> wrote:
>>>
 I've been using weewx running on a Pi Zero with no other tasks. 
 Unfortunately, I live in a area that suffers power losses, often during a 
 weather events, so I lose that data. What typically happens is that when 
 the power comes back on, I get the dreaded "..page timestamp... less than 
 final timestamp..." error. The only way I have been able to address it is 
 to use the memory dump and clear.

  I don't understand why this happens since the VP2 is running with 
 battery backup, yet the memory on the datalogger gets corrupted. Is this 
 an 
 issue with weewx that could be addressed?

 Failing that, can I address this issue by adding a backup supply to my 
 Pi Zero?

 Thanks!

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

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/7bd3876d-96a1-4c3a-82fb-c4f406234066n%40googlegroups.com
>>  
>> 
>> .
>>
>

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

[weewx-user] Re: Working drivers for TWI, Vaisala WXT, Peet Bros Ultimeter

[storm...@gmail.com]

Dale

Hopefully you are feeling better. Could the driver be "fileparser".  

Storm

On Wednesday, November 16, 2022 at 10:59:18 PM UTC-5 wxe...@gmail.com wrote:

> After many years and a comfortable implementation of the Rainwise IP-100 
> driver, my Rainwise station has died, seems currently unfixable.  
> Despite loosing most of the summer trying to get the ISS to transmit 
> again, I've lost all taht time and have to look for other inputs.
>
> Looking through the Wiki, I see there may be three other station types 
> for which there are drivers which I might try.
>
>
> I have a Vaisala WXT520, a Texas Weather Instruments, and a Peet Bros 
> Ultimeter which I might try.
>
> Having followed the messages here, I know there were updates to Python 
> 3, which required some modifications to the drivers that are on GitHub, 
> and then a recent upgrade in WeeWx itself.
>
>
> My question is to current users of WeeWx, do you have a station working 
> with the latest WeeWx, the latest Python and any of the three drivers 
> mentioned here?
>
>
> If there is success, I will focus on trying to get my WeeWx working again.
>
>
> I know the ultimate would be to learn enough Python to implement my own 
> driver and be able to fix it, but quite honestly, after a several month 
> illness, I find that my previous understanding which I was proud of now 
> has become fuzzy and a personal expectation to rev my mental processes 
> up may take longer than I want to be without a WeeWx running, so I'm 
> looking for the most likely path to success, and then get back on trying 
> to get things working with understanding Python.
>
>
> I appreciate any comments that might steer me to one of these three 
> mentioned drivers to see if I should even start down a particular path 
> with a station type.
>
>
> Oh, one last question:  I had some notes on a sort of universal driver 
> which was mentioned as a starting point for someone wishing to begin to 
> learn how things work.  If I recall, it took a text file of the 
> station's readings and converted it into a LOOP type input for WeeWx to 
> ingest.  One 'only' needed to get data from the weather station, format 
> it into a list or dictionary, and then give it to WeeWx.  I have been 
> through the developer's guide and hardware guide and the wiki but for 
> the life of me cannot see the name of that referenced.  Have I triggered 
> enough recognition that someone might tell me the name of the driver and 
> I'll go study that again to start.
>
> Thank youDale
>
>
>

-- 
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/121f42cd-f61f-4f17-802c-0e2064fb6ea3n%40googlegroups.com.

[weewx-user] Re: Upgrade Weewx 3.9.2 to 4.6 ?

[storm...@gmail.com]

Did you check this link?

https://weewx.com/docs/upgrading.htm

On Saturday, September 10, 2022 at 10:28:02 PM UTC-4 Yves Martin wrote:

> What is the simplest way to upgrade weewx 3.9.2 to 4.6 (or the last 
> version)?
>
> YM
>

-- 
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/507dba16-4db5-46f8-b01c-bfb06b3a4450n%40googlegroups.com.

[weewx-user] Re: Setting up rtldavis - where to get?

[storm...@gmail.com]

Take a look here:

https://github.com/lheijst/weewx-rtldavis

On Monday, August 22, 2022 at 11:42:38 PM UTC-4 f4n...@gmail.com wrote:

> Hi, does anyone have the installation files for rtldavis? It seems to be 
> archived (https://github.com/bemasher/rtldavis) and not longer available 
> in the repository if I try to install it with golang.
>
> Is anyone having long term experience and still running it? How stable is 
> the signal with a R820T/T2 chip? Does it get every 2.5s wind packet?
>
> Thanks for any advice,
> fankyy
>

-- 
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/95e5ed49-9007-4fc4-9985-da5cc2ba7a54n%40googlegroups.com.

[weewx-user] Re: Newbie how-to question

[storm...@gmail.com]

Going after 433Mhz sensor (THN132N) should only give you Temp.  Did you 
search here? https://groups.google.com/g/rtl_433

On Sunday, August 21, 2022 at 1:00:05 AM UTC-4 es...@ieee.org wrote:

>
> The remote sensor THN132N
>
> I can detect the bluetooth unit but have no idea if it csn be read or if 
> it receive only. If ther was a waynto read it,  that might be an option.
> I think going after the 433 signal would be more reliable
> On Saturday, August 20, 2022 at 3:50:22 PM UTC-7 storm...@gmail.com wrote:
>
>>
>> Are you talking about interfacing the EMR211 console , which is 
>> bluetooth, or the remote sensor THN132N which is 433MHz.  
>>
>> Someone wrote a driver to interface a bluetooth enabled wx station.  This 
>> might provide some insight.
>>
>> https://github.com/daduke/ventusw820
>> On Saturday, August 20, 2022 at 6:13:47 PM UTC-4 es...@ieee.org wrote:
>>
>>> I'm working on the dosc but if I can't recive from the EMR211 there 
>>> won't be anything to view and reading the docs may or may not answer my 
>>> question.  I know that I won't know for sure until I've read every scrap 
>>> but that's a lot of effort for an uncertain result.
>>>
>>> Thanks
>>>
>>> On Saturday, August 20, 2022 at 2:24:29 PM UTC-7 storm...@gmail.com 
>>> wrote:
>>>
>>>> You can view web pages locally and/or upload to a web host. Did you 
>>>> read through the documents:
>>>>
>>>> https://weewx.com/docs.html
>>>>
>>>> On Saturday, August 20, 2022 at 4:49:08 PM UTC-4 es...@ieee.org wrote:
>>>>
>>>>> Hello,
>>>>> I just discovered this site. I have a project and would appreciate 
>>>>> help in understanding whether weewx would work.
>>>>>
>>>>> I have an oregon scientific EMR211 outdoor thermometer. I also have 
>>>>> 433mhz receiver modules, an rtl-sdr (not used yet) and raspberry pi's. I 
>>>>> have been able to connect a receiver module to a logic analyzer and 
>>>>> decode 
>>>>> the signal with PulseView using the manchester/oregon decoder. I'm 
>>>>> getting 
>>>>> temps and battery status messages.
>>>>>
>>>>> I have tried to decode this on an esp8266 with some posted python code 
>>>>> but one is not designed to generate output :( and the other displays 
>>>>> values 
>>>>> that are all over the map (like negative temps). So I need a 
>>>>> different/better approach.
>>>>>
>>>>> I see that there is support for a number of Oregon Scientific products 
>>>>> and I'm guessing that many of them transmit on 433 withe the same 
>>>>> protocol. 
>>>>> Is it possible to connect any of this to weewx so that I could make the 
>>>>> temps viewable in a web browser? 
>>>>>
>>>>> Help would be 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/0352a40f-f9fa-41b4-8d7e-1cdf68df7debn%40googlegroups.com.

[weewx-user] Re: Newbie how-to question

[storm...@gmail.com]

Are you talking about interfacing the EMR211 console , which is bluetooth, 
or the remote sensor THN132N which is 433MHz.  

Someone wrote a driver to interface a bluetooth enabled wx station.  This 
might provide some insight.

https://github.com/daduke/ventusw820
On Saturday, August 20, 2022 at 6:13:47 PM UTC-4 es...@ieee.org wrote:

> I'm working on the dosc but if I can't recive from the EMR211 there won't 
> be anything to view and reading the docs may or may not answer my question. 
>  I know that I won't know for sure until I've read every scrap but that's a 
> lot of effort for an uncertain result.
>
> Thanks
>
> On Saturday, August 20, 2022 at 2:24:29 PM UTC-7 storm...@gmail.com wrote:
>
>> You can view web pages locally and/or upload to a web host. Did you read 
>> through the documents:
>>
>> https://weewx.com/docs.html
>>
>> On Saturday, August 20, 2022 at 4:49:08 PM UTC-4 es...@ieee.org wrote:
>>
>>> Hello,
>>> I just discovered this site. I have a project and would appreciate help 
>>> in understanding whether weewx would work.
>>>
>>> I have an oregon scientific EMR211 outdoor thermometer. I also have 
>>> 433mhz receiver modules, an rtl-sdr (not used yet) and raspberry pi's. I 
>>> have been able to connect a receiver module to a logic analyzer and decode 
>>> the signal with PulseView using the manchester/oregon decoder. I'm getting 
>>> temps and battery status messages.
>>>
>>> I have tried to decode this on an esp8266 with some posted python code 
>>> but one is not designed to generate output :( and the other displays values 
>>> that are all over the map (like negative temps). So I need a 
>>> different/better approach.
>>>
>>> I see that there is support for a number of Oregon Scientific products 
>>> and I'm guessing that many of them transmit on 433 withe the same protocol. 
>>> Is it possible to connect any of this to weewx so that I could make the 
>>> temps viewable in a web browser? 
>>>
>>> Help would be 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/a5ba82b1-73c2-4eba-aa28-0e45479d77a7n%40googlegroups.com.

[weewx-user] Re: Newbie how-to question

[storm...@gmail.com]

You can view web pages locally and/or upload to a web host. Did you read 
through the documents:

https://weewx.com/docs.html

On Saturday, August 20, 2022 at 4:49:08 PM UTC-4 es...@ieee.org wrote:

> Hello,
> I just discovered this site. I have a project and would appreciate help in 
> understanding whether weewx would work.
>
> I have an oregon scientific EMR211 outdoor thermometer. I also have 433mhz 
> receiver modules, an rtl-sdr (not used yet) and raspberry pi's. I have been 
> able to connect a receiver module to a logic analyzer and decode the signal 
> with PulseView using the manchester/oregon decoder. I'm getting temps and 
> battery status messages.
>
> I have tried to decode this on an esp8266 with some posted python code but 
> one is not designed to generate output :( and the other displays values 
> that are all over the map (like negative temps). So I need a 
> different/better approach.
>
> I see that there is support for a number of Oregon Scientific products and 
> I'm guessing that many of them transmit on 433 withe the same protocol. Is 
> it possible to connect any of this to weewx so that I could make the temps 
> viewable in a web browser? 
>
> Help would be 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/8a90c694-d6c9-4775-8651-f89eabc70955n%40googlegroups.com.

[weewx-user] Re: Recommends for new station under 300

[storm...@gmail.com]

Check out Scaled Instruments: 

https://www.scaledinstruments.com/product-category/davis-instruments/complete-weather-stations/vantage-vue-series/

On Wednesday, August 10, 2022 at 9:50:13 AM UTC-4 kavanag...@gmail.com 
wrote:

> 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/1129d648-80d3-43d2-ac04-c0fb896e8555n%40googlegroups.com.

[weewx-user] Re: Adding BME280 to WeeWX

[storm...@gmail.com]

Take a look at this extension:
 
https://gitlab.com/wjcarpenter/bme280wx



On Wednesday, May 11, 2022 at 7:24:40 PM UTC-4 dave.sp...@gmail.com wrote:

> Ok, I have been doing a lot of research, but can’t seem to find what I 
> need to do exactly. 
>
>  
>
> My setup is as follows:
>
>   WeeWX Version 4.5.1 running on a Raspberry Pi 3
>
>   Station_type of SDR to get the weather data from acurite 
> atlas 5-n-1.
>
>  
>
> I am trying to add a BME280. I have it connected to the same RPi that is 
> running weewx. I can run a test program to verify that it does in fact get 
> the temp, humidity, pressure, altitude. 
>
>  
>
> What I would like to have done is when I go and view weewx web pages, I 
> mainly want the barometer reading to populate. I am not too concerned about 
> the others. With that being said does this mean that I need to have 2 
> instances of weewx running or can I add this sensor into the weewx.conf 
> file and still have all of my SDR config. 
>
>  
>
> Any help would be appreciated
>
> Thanks
>
>  
>

-- 
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/04f98b22-10e9-4ac5-aca0-c04c3785b4c9n%40googlegroups.com.

[weewx-user] Re: Atlas Lightning Count Accuracy

[storm...@gmail.com]

If I'm not mistaken,  '"lightning_strike_count': 243," is just the counter 
value from the sensor which rolls over to 0  after the counter reaches 255.

On Tuesday, May 3, 2022 at 1:13:52 PM UTC-4 an oldman wrote:

> try changing lightning_strike_count = strike_count.011D.AcuriteAtlasPacket 
> to strikes_total = strike_count.011D.AcuriteAtlasPacket in your sensor_map
>
> On Tuesday, May 3, 2022 at 10:12:24 AM UTC-5 knnni...@gmail.com wrote:
>
>> All - I've almost got the lightning sensor in my Atlas reporting 
>> correctly in weewx, and I am hoping someone can get me over the threshold.
>>
>> I am using a very recent build of rtl-433, the latest sdr, and weewx 
>> 4.8.0.
>>
>> By apparent design, the Atlas reports the same value for lightning 
>> strikes at each reporting interval, when no additional strikes occur:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *May 03 09:05:49 vWebapp.derbauer.local.lan weewxd[885258]: weewx[885258] 
>> DEBUG user.sdr: packet={'windSpeed': 5.0, 'outTemp': 65.0, 'outHumidity': 
>> 91.0, 'outTempBatteryStatus': 0, 'lightning_distance': 5, 
>> 'lightning_strike_count': 243, 'dateTime': 1651586746, 'usUnits': 1}May 03 
>> 09:05:49 vWebapp.derbauer.local.lan weewxd[885258]: weewx[885258] DEBUG 
>> user.sdr: packet={'windSpeed': 5.0, 'outTemp': 65.0, 'outHumidity': 91.0, 
>> 'outTempBatteryStatus': 0, 'lightning_distance': 5, 
>> 'lightning_strike_count': 243, 'dateTime': 1651586746, 'usUnits': 1}May 03 
>> 09:05:49 vWebapp.derbauer.local.lan weewxd[885258]: weewx[885258] DEBUG 
>> user.sdr: packet={'windSpeed': 5.0, 'outTemp': 65.0, 'outHumidity': 91.0, 
>> 'outTempBatteryStatus': 0, 'lightning_distance': 5, 
>> 'lightning_strike_count': 243, 'dateTime': 1651586746, 'usUnits': 1}May 03 
>> 09:06:00 vWebapp.derbauer.local.lan weewxd[885258]: weewx[885258] DEBUG 
>> user.sdr: packet={'windDir': 235.0, 'windSpeed': 4.0, 'rain_total': 4.29, 
>> 'outTempBatteryStatus': 0, 'lightning_distance': 5, 
>> 'lightning_strike_count': 243, 'dateTime': 1651586756, 'usUnits': 1}May 03 
>> 09:06:00 vWebapp.derbauer.local.lan weewxd[885258]: weewx[885258] DEBUG 
>> user.sdr: packet={'windDir': 235.0, 'windSpeed': 4.0, 'rain_total': 4.29, 
>> 'outTempBatteryStatus': 0, 'lightning_distance': 5, 
>> 'lightning_strike_count': 243, 'dateTime': 1651586756, 'usUnits': 1}May 03 
>> 09:06:00 vWebapp.derbauer.local.lan weewxd[885258]: weewx[885258] DEBUG 
>> user.sdr: packet={'windDir': 235.0, 'windSpeed': 4.0, 'rain_total': 4.29, 
>> 'outTempBatteryStatus': 0, 'lightning_distance': 5, 
>> 'lightning_strike_count': 243, 'dateTime': 1651586756, 'usUnits': 1}May 03 
>> 09:06:10 vWebapp.derbauer.local.lan weewxd[885258]: weewx[885258] DEBUG 
>> user.sdr: packet={'windSpeed': 3.0, 'outTempBatteryStatus': 0, 'radiation': 
>> 13510, 'UV': 2, 'lightning_distance': 5, 'lightning_strike_count': 243, 
>> 'dateTime': 1651586767, 'usUnits': 1}May 03 09:06:10 
>> vWebapp.derbauer.local.lan weewxd[885258]: weewx[885258] DEBUG user.sdr: 
>> packet={'windSpeed': 3.0, 'outTempBatteryStatus': 0, 'radiation': 13510, 
>> 'UV': 2, 'lightning_distance': 5, 'lightning_strike_count': 243, 
>> 'dateTime': 1651586767, 'usUnits': 1}May 03 09:06:10 
>> vWebapp.derbauer.local.lan weewxd[885258]: weewx[885258] DEBUG user.sdr: 
>> packet={'windSpeed': 3.0, 'outTempBatteryStatus': 0, 'radiation': 13510, 
>> 'UV': 2, 'lightning_distance': 5, 'lightning_strike_count': 243, 
>> 'dateTime': 1651586767, 'usUnits': 1}May 03 09:06:21 
>> vWebapp.derbauer.local.lan weewxd[885258]: weewx[885258] DEBUG user.sdr: 
>> packet={'windSpeed': 2.0, 'outTemp': 65.0, 'outHumidity': 91.0, 
>> 'outTempBatteryStatus': 0, 'lightning_distance': 5, 
>> 'lightning_strike_count': 243, 'dateTime': 1651586777, 'usUnits': 1}May 03 
>> 09:05:49 vWebapp.derbauer.local.lan weewxd[885258]: weewx[885258] DEBUG 
>> user.sdr: packet={'windSpeed': 5.0, 'outTemp': 65.0, 'outHumidity': 91.0, 
>> 'outTempBatteryStatus': 0, 'lightning_distance': 5, 
>> 'lightning_strike_count': 243, 'dateTime': 1651586746, 'usUnits': 1}May 03 
>> 09:05:49 vWebapp.derbauer.local.lan weewxd[885258]: weewx[885258] DEBUG 
>> user.sdr: packet={'windSpeed': 5.0, 'outTemp': 65.0, 'outHumidity': 91.0, 
>> 'outTempBatteryStatus': 0, 'lightning_distance': 5, 
>> 'lightning_strike_count': 243, 'dateTime': 1651586746, 'usUnits': 1}May 03 
>> 09:05:49 vWebapp.derbauer.local.lan weewxd[885258]: weewx[885258] DEBUG 
>> user.sdr: packet={'windSpeed': 5.0, 'outTemp': 65.0, 'outHumidity': 91.0, 
>> 'outTempBatteryStatus': 0, 'lightning_distance': 5, 
>> 'lightning_strike_count': 243, 'dateTime': 1651586746, 'usUnits': 1}May 03 
>> 09:06:00 vWebapp.derbauer.local.lan weewxd[885258]: weewx[885258] DEBUG 
>> user.sdr: packet={'windDir': 235.0, 'windSpeed': 4.0, 'rain_total': 4.29, 
>> 'outTempBatteryStatus': 0, 'lightning_distance': 5, 
>> 'lightning_strike_count': 243, 'dateTime': 1651586756, 'usUnits': 1}May 03 
>> 09:06:00 vWebapp.derbauer.local.lan weewxd[885258]: weewx[885258] 

[weewx-user] Re: do two sept. instances of weewx using weewx-sdr require to rtl-sdr radios?

[storm...@gmail.com]

I would assume that you would need to separate SDR dongles, since the 
rtl_433 instance #1 would claim the usb port for the SDR Dongle.  What are 
the frequencies for both the weather stations?  If the frequencies are the 
same; i.e. 433MHz or 915MHz, you should be able to decode both stations 
with one dongle.  Or if they are different; i.e. 433MHz and 915MHz and 
don't mind the possibility of missing packets, you should be able to decode 
both stations with one dongle by hopping between both frequencies. 

On Thursday, April 28, 2022 at 9:24:05 PM UTC-4 william...@att.net wrote:

> how about if you run two instances of rtl_433 and one dongle using rtl_tcp 
> sending to both rtl_433s.
>
> On Thursday, April 28, 2022 at 5:43:45 PM UTC-7 William Garber wrote:
>
>> Suppose you have two weather stations each represented by a respective 
>> different simultaneously running instance of weewx.  Both instances of 
>> weewx use weewx-sdr as driver for a rtl-sdr radio device connected by usb 
>> to the computer.  You have to configure the rtl-sdr radio using rtl_433 
>> which in turn uses the rtl-sdr linux driver.  
>>
>> The question may be really dumb but don't you have to have two separate 
>> rtl-sdr radio devices (each on different usb connections) to run both 
>> weather stations at the same time?
>>
>

-- 
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/46c3a519-6958-42b3-a218-0ed5c13fadc7n%40googlegroups.com.

Re: [weewx-user] Reading rain rate more frequently than the archive period

[storm...@gmail.com]

Look in the beginning of the MQTT.py file for some configuration options.  

On Saturday, April 9, 2022 at 5:42:02 PM UTC-4 gagnon@gmail.com wrote:

> Yes! That did it! Where did you did the doc on this. I search for what 
> parameters were available to the MQTT module and couldn't find anything!
>
> Le samedi 9 avril 2022 à 17 h 19 min 50 s UTC-4, storm...@gmail.com a 
> écrit :
>
>> Try adding the following:
>>
>> [[MQTT]]
>> server_url = mqtt://username:password@host:1883/
>> topic = weather#
>> unit_system = US
>> binding = archive, loop
>> aggregation = aggregate
>> log_success = false
>> log_failure = true
>>
>> On Saturday, April 9, 2022 at 3:50:46 PM UTC-4 gagnon@gmail.com 
>> wrote:
>>
>>> Must I do something special to push the LOOP records more frequently 
>>> through MQTT? I've imported the Paho MQTT Python library and the loop 
>>> record is being pushed at the ARCHIVE interval, which is also confirmed 
>>> with MQTT Explorer. I've seen timestamp of 15:45:27, 15:40:10, 15:35:29 and 
>>> 15:30:20 for the 'acurite/loop' topic. This is what I have in the 
>>> weewx.conf file for MQTT
>>>
>>> [[MQTT]]
>>> server_url = mqtt://username:password@hostname:1883/
>>> topic = acurite
>>> unit_system = METRIC
>>> retain = true
>>>
>>> Is there something missing?
>>>
>>> Thanks for your help
>>>
>>> Le samedi 9 avril 2022 à 07 h 20 min 13 s UTC-4, do...@dougjenkins.com 
>>> a écrit :
>>>
>>>> have you considered MQTT? You could setup the MQTT WeeWX Extension in 
>>>> which it will push both LOOP and ARCHIVE records to a MQTT broker. I have 
>>>> an Acurite 5-n-1 weather station and use MQTT to update my website as the 
>>>> LOOP data changes. I get updates around every 18 seconds or so.
>>>>
>>>> In your Python program, you use Paho Python library to "subscribe" to 
>>>> your MQTT host and invoke an event when you get a LOOP Record. From there 
>>>> evaluate the rain values and take action with your car windows at that 
>>>> moment based on the data.
>>>>
>>>> MQTT is a small, lightweight protocol that will update in near real 
>>>> time. It is used a lot in IOT devices.
>>>>
>>>>
>>>> On Saturday, April 9, 2022 at 2:31:03 AM UTC-4 Graham Eddy wrote:
>>>>
>>>>> your Acurite driver creates a ‘loop packet’ each time it receives a 
>>>>> reading from the station. you can have a ’service’ immediately export 
>>>>> selected data from each loop packet, not wait until the end of the 
>>>>> archive 
>>>>> interval (which is when database is updated). depending how you want the 
>>>>> data exported, there could be an existing service extension available 
>>>>> off-the-shelf
>>>>>
>>>>> On 9 Apr 2022, at 3:23 pm, Sylvain Gagnon  
>>>>> wrote:
>>>>>
>>>>> Hi, I've been using WeeWx for many years now but first time posting 
>>>>> here.
>>>>>
>>>>> I'm writing a program in Python that queries my Acurite 5 in 1 probe 
>>>>> through WeeWX for the rain rate and if it's above 0mm, then it will close 
>>>>> the car windows if they are opened and the car is parked. It works well 
>>>>> but 
>>>>> relies on daily.json to fetch the rain rate and that value I believe 
>>>>> updates at the archive frequency (ie, 5 minutes) but the stations sends 
>>>>> that data every 36 seconds. Is there a way to fetch this value? The only 
>>>>> other option that I can think of is to set the "archive_interval" to 60 
>>>>> instead of 300 in [StdArchive]. If I do that, will that mess up all the 
>>>>> historical data already in the database? Any other side effects?
>>>>>
>>>>> Thanks for your help at keeping the inside of my car dry :-)
>>>>>
>>>>>
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "weewx-user" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to weewx-user+...@googlegroups.com.
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/weewx-user/c90fb5b9-f691-4024-a00f-ab55a340fb04n%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/weewx-user/c90fb5b9-f691-4024-a00f-ab55a340fb04n%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>>>
>>>>>

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

Re: [weewx-user] Reading rain rate more frequently than the archive period

[storm...@gmail.com]

Try adding the following:

[[MQTT]]
server_url = mqtt://username:password@host:1883/
topic = weather#
unit_system = US
binding = archive, loop
aggregation = aggregate
log_success = false
log_failure = true

On Saturday, April 9, 2022 at 3:50:46 PM UTC-4 gagnon@gmail.com wrote:

> Must I do something special to push the LOOP records more frequently 
> through MQTT? I've imported the Paho MQTT Python library and the loop 
> record is being pushed at the ARCHIVE interval, which is also confirmed 
> with MQTT Explorer. I've seen timestamp of 15:45:27, 15:40:10, 15:35:29 and 
> 15:30:20 for the 'acurite/loop' topic. This is what I have in the 
> weewx.conf file for MQTT
>
> [[MQTT]]
> server_url = mqtt://username:password@hostname:1883/
> topic = acurite
> unit_system = METRIC
> retain = true
>
> Is there something missing?
>
> Thanks for your help
>
> Le samedi 9 avril 2022 à 07 h 20 min 13 s UTC-4, do...@dougjenkins.com a 
> écrit :
>
>> have you considered MQTT? You could setup the MQTT WeeWX Extension in 
>> which it will push both LOOP and ARCHIVE records to a MQTT broker. I have 
>> an Acurite 5-n-1 weather station and use MQTT to update my website as the 
>> LOOP data changes. I get updates around every 18 seconds or so.
>>
>> In your Python program, you use Paho Python library to "subscribe" to 
>> your MQTT host and invoke an event when you get a LOOP Record. From there 
>> evaluate the rain values and take action with your car windows at that 
>> moment based on the data.
>>
>> MQTT is a small, lightweight protocol that will update in near real time. 
>> It is used a lot in IOT devices.
>>
>>
>> On Saturday, April 9, 2022 at 2:31:03 AM UTC-4 Graham Eddy wrote:
>>
>>> your Acurite driver creates a ‘loop packet’ each time it receives a 
>>> reading from the station. you can have a ’service’ immediately export 
>>> selected data from each loop packet, not wait until the end of the archive 
>>> interval (which is when database is updated). depending how you want the 
>>> data exported, there could be an existing service extension available 
>>> off-the-shelf
>>>
>>> On 9 Apr 2022, at 3:23 pm, Sylvain Gagnon  wrote:
>>>
>>> Hi, I've been using WeeWx for many years now but first time posting here.
>>>
>>> I'm writing a program in Python that queries my Acurite 5 in 1 probe 
>>> through WeeWX for the rain rate and if it's above 0mm, then it will close 
>>> the car windows if they are opened and the car is parked. It works well but 
>>> relies on daily.json to fetch the rain rate and that value I believe 
>>> updates at the archive frequency (ie, 5 minutes) but the stations sends 
>>> that data every 36 seconds. Is there a way to fetch this value? The only 
>>> other option that I can think of is to set the "archive_interval" to 60 
>>> instead of 300 in [StdArchive]. If I do that, will that mess up all the 
>>> historical data already in the database? Any other side effects?
>>>
>>> Thanks for your help at keeping the inside of my car dry :-)
>>>
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/c90fb5b9-f691-4024-a00f-ab55a340fb04n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/42d7b5f1-8d5c-49bd-9b1f-52e720f5b55dn%40googlegroups.com.

[weewx-user] Re: SQL Count Statement

[storm...@gmail.com]

Update:

Figured out the SQL statement to use:

SELECT count(*) FROM wxalerts WHERE event_id like '%{event_id_code}%'



On Sunday, February 6, 2022 at 3:33:36 PM UTC-5 storm...@gmail.com wrote:

> I'm attempting to count the number of times a certain string appears in a 
> row/column using the following SQL statement:
>
> "SELECT count(*) FROM wxalerts WHERE event_id like (?)", [event_id_code]
>
> When I run the statement, it always returns 0.
>
> If I run the following statement, it returns the correct number of the 
> string appears.
>
> "SELECT count(*) FROM wxalerts WHERE event_id like 
> '%d137c21374c749704530e9a1e52cff46%'
>
> Does someone see where my issue is?  Right now this is a stand alone 
> python program querying a SQLite DB, but once it is functional would like 
> to convert the program over to a weewx service.
>

-- 
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/d5a4d143-3208-416e-b873-efed2dba41fcn%40googlegroups.com.

[weewx-user] SQL Count Statement

[storm...@gmail.com]

I'm attempting to count the number of times a certain string appears in a 
row/column using the following SQL statement:

"SELECT count(*) FROM wxalerts WHERE event_id like (?)", [event_id_code]

When I run the statement, it always returns 0.

If I run the following statement, it returns the correct number of the 
string appears.

"SELECT count(*) FROM wxalerts WHERE event_id like 
'%d137c21374c749704530e9a1e52cff46%'

Does someone see where my issue is?  Right now this is a stand alone python 
program querying a SQLite DB, but once it is functional would like to 
convert the program over to a weewx service.

-- 
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/12ecbfe3-fe27-4648-aea7-70aa10706e75n%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

[storm...@gmail.com]

Nice work (Morrowwn  thanks!).  If you have any nulls in the data during 
the selected timeframe, change the query to read:  (Cameron D thanks!)

*query = "select datetime, barometer from archive where datetime > %.0f and 
datetime < %.0f and barometer is not null order by dateTime;" % 
(start_time, stop_time)*




[image: hunga_tonga.png]

If you want the bars closer to the rise and falls of the events, need to 
adjust the speed of sound slightly.
On Saturday, January 22, 2022 at 2:37:09 PM UTC-5 pmcg...@gmail.com wrote:

> WOW!  This is some interesting data, here is my location in Northern 
> Utah.  Looks like the reverse may be a little off in calculation but this 
> made it easy to find instead of hunting through the data.
>
> Great Work!
> [image: hunga_tonga.png]
> On Saturday, January 22, 2022 at 12:16:45 PM UTC-7 morr...@gmail.com 
> wrote:
>
>> Did an update to my script at: 
>> https://github.com/morrowwm/weewx_tonga_browse
>>
>> Mostly incorporating additions from Cameron (thanks!)
>>
>> All parameters you likely want to set are near the top of the script.
>>
>>1. support for mysql (untested, I don't have a mysql based weewx 
>>installation)
>>2. calculation and display of all three initial arrival, arrival from 
>>opposite direction, and second arrival after one trip around the globe
>>3. highlighting of the three events with grey bars
>>4. cubic spline curve fit of raw data and use of that fit to remove 
>>the base pressure variations. The new smoothing_hours parameter can be 
>> used 
>>to control how close the fit is. 
>>5. changed the display of data to highlight the extracted events and 
>>subdue the original data, other cosmetic changes
>>
>> I had a data outage about 26 hours after the event, we're quite a 
>> distance from Tonga, plus a major storm was clearing out in our area. So 
>> not obviously anything unusual happened.
>>
>> Some scientist might be interested in the arrival times of all this data, 
>> though.
>> [image: hunga_tonga.png]
>>
>>

-- 
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/80a10960-7af0-44ec-9fd8-bb0a9cf74e55n%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

[storm...@gmail.com]

If I recall looking @ MADIS 15 minute data, it least for me, the pressure 
of the opposite wave did drop a some before the major spike. After changing 
the colors on the charts, it aligns with the first drop in pressure.

On Thursday, January 20, 2022 at 11:28:41 PM UTC-5 Cameron D wrote:

> There are certainly uncertainties in the barometric data timings. My 
> system is probably a worst case - it only reports a value every 15 minutes, 
> and I don't know if that is an average of the previous 15 minutes or just a 
> snapshot reading at the transition time. So for me 20 minutes is within the 
> uncertainty.
> Also, I don't know if it is expected, but the  pulses that travelled 
> further show only the negative part, which comes after the positive. So 
> there is extra lag in that.
>
> I derived a speed by fitting data to Australian bureau charts, and they 
> only show 30 minute samples, so my speed is hardly definitive.  I would 
> expect it to vary a bit around the globe.  The average speed I derived from 
> the first peak alone was 0.30 m/s, so that is either an indicator of the 
> uncertainty in the fitting or that the average speed increased as it 
> progressed.
> On Friday, 21 January 2022 at 2:05:49 pm UTC+10 storm...@gmail.com wrote:
>
>> Yes, the image files are being produced. Only thing I noticed was the 
>> arrival time for the opposite pulse is off by approx. 20 minutes according 
>> to the actual PWS data, this could be due to the wave speeding up or 
>> slowing down as it made its way around the globe.  Right now I'm using your 
>> default settings.
>>
>> On Thursday, January 20, 2022 at 10:40:36 PM UTC-5 Cameron D wrote:
>>
>>> the RankWarning is just a warning, you should still have image files 
>>> produced.  I expect the polyfit it just ignores higher order terms and just 
>>> returns a quadratic.
>>>
>>> That is because the polynomial is a poor representation of the 
>>> background, and the spline fit works better, if you get the parameters 
>>> correct.
>>>
>>> Initially you are better just to view the results without trend 
>>> removal.  If the peaks  do not stand out then  background removal is 
>>> unlikely to help much.
>>> Also, with my code,  make sure you start with oversampling set to 1. 
>>> Only adjust it if you see a stair-step effect.
>>>
>>> On Friday, 21 January 2022 at 1:09:28 pm UTC+10 storm...@gmail.com 
>>> wrote:
>>>
>>>> Modified the query and added the print statement as suggested 
>>>> by Cameron D and here are the results:
>>>>
>>>> *Morrowwn Script:*
>>>>
>>>> raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
>>>> distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 
>>>> 10:47:08)
>>>> select datetime, barometer from archive where datetime > 1642172400 and 
>>>> datetime < 1642693629 order by dateTime;
>>>> Traceback (most recent call last):
>>>>   File "tonga_barometer.py", line 47, in 
>>>> coeff = np.polyfit(xdata, ydata, 2)
>>>>   File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 
>>>> 590, in polyfit
>>>> y = NX.asarray(y) + 0.0
>>>> TypeError: unsupported operand type(s) for +: 'NoneType' and 'float'
>>>>
>>>>
>>>> *Cameron D Script*:
>>>>
>>>> raspberrypi:~/Desktop/Tonga $ python3 tonga_baro.py
>>>> distance to eruption 12255.7 km arrival at 1642258384 (2022-01-15 
>>>> 09:53:04)
>>>>   opposite pulse arrival at 1642306911 (2022-01-15 23:21:50)
>>>>   second time around pulse arrival at 1642383509 (2022-01-16 
>>>> 20:38:29)
>>>> query returned 96 data points
>>>> query returned 96 data points
>>>> query returned 95 data points
>>>> tonga_baro.py:108: RankWarning: Polyfit may be poorly conditioned
>>>>   coeff = np.polyfit(xdata, ydata, 5 )
>>>>
>>>> Note: LAT/Long and speed of sound are identical in both scripts.
>>>> On Thursday, January 20, 2022 at 9:27:13 PM UTC-5 Cameron D wrote:
>>>>
>>>>> and add a debug printout for how many result lines there are after ...
>>>>> result = cursor.fetchall()
>>>>> add the line:
>>>>> 
>>>>> *print( "query returned {} data points".format(len(result)))*
>>>>>
>>>>> On Friday, 21 January 2022 at 12:21:59 pm UTC+10 Cameron D wrote:
>>>&g

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

[storm...@gmail.com]

Yes, the image files are being produced. Only thing I noticed was the 
arrival time for the opposite pulse is off by approx. 20 minutes according 
to the actual PWS data, this could be due to the wave speeding up or 
slowing down as it made its way around the globe.  Right now I'm using your 
default settings.

On Thursday, January 20, 2022 at 10:40:36 PM UTC-5 Cameron D wrote:

> the RankWarning is just a warning, you should still have image files 
> produced.  I expect the polyfit it just ignores higher order terms and just 
> returns a quadratic.
>
> That is because the polynomial is a poor representation of the background, 
> and the spline fit works better, if you get the parameters correct.
>
> Initially you are better just to view the results without trend removal.  
> If the peaks  do not stand out then  background removal is unlikely to help 
> much.
> Also, with my code,  make sure you start with oversampling set to 1. Only 
> adjust it if you see a stair-step effect.
>
> On Friday, 21 January 2022 at 1:09:28 pm UTC+10 storm...@gmail.com wrote:
>
>> Modified the query and added the print statement as suggested by Cameron 
>> D and here are the results:
>>
>> *Morrowwn Script:*
>>
>> raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
>> distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 
>> 10:47:08)
>> select datetime, barometer from archive where datetime > 1642172400 and 
>> datetime < 1642693629 order by dateTime;
>> Traceback (most recent call last):
>>   File "tonga_barometer.py", line 47, in 
>> coeff = np.polyfit(xdata, ydata, 2)
>>   File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 
>> 590, in polyfit
>> y = NX.asarray(y) + 0.0
>> TypeError: unsupported operand type(s) for +: 'NoneType' and 'float'
>>
>>
>> *Cameron D Script*:
>>
>> raspberrypi:~/Desktop/Tonga $ python3 tonga_baro.py
>> distance to eruption 12255.7 km arrival at 1642258384 (2022-01-15 
>> 09:53:04)
>>   opposite pulse arrival at 1642306911 (2022-01-15 23:21:50)
>>   second time around pulse arrival at 1642383509 (2022-01-16 20:38:29)
>> query returned 96 data points
>> query returned 96 data points
>> query returned 95 data points
>> tonga_baro.py:108: RankWarning: Polyfit may be poorly conditioned
>>   coeff = np.polyfit(xdata, ydata, 5 )
>>
>> Note: LAT/Long and speed of sound are identical in both scripts.
>> On Thursday, January 20, 2022 at 9:27:13 PM UTC-5 Cameron D wrote:
>>
>>> and add a debug printout for how many result lines there are after ...
>>> result = cursor.fetchall()
>>> add the line:
>>> 
>>> *print( "query returned {} data points".format(len(result)))*
>>>
>>> On Friday, 21 January 2022 at 12:21:59 pm UTC+10 Cameron D wrote:
>>>
>>>> To eliminate NULL data points use a query like:
>>>> select datetime, barometer from archive where datetime > 1642172400 and 
>>>> datetime < 1642693629* and barometer is not null *order by dateTime;
>>>>  You could add the part in bold into the query in the python script.
>>>>
>>>> Of course, if they are all null...
>>>>
>>>> On Friday, 21 January 2022 at 12:14:44 pm UTC+10 storm...@gmail.com 
>>>> wrote:
>>>>
>>>>> Download the latest script from 
>>>>> https://github.com/morrowwm/weewx_tonga_browse. Beside installing the 
>>>>> Python Modules Vince stated above, I needed to also install  
>>>>> python3-scipy. I do have data between 1642172400 and 1642693629; 
>>>>> except for a couple "null" in that time period.   So when I run the 
>>>>> script, 
>>>>> I get the following error.
>>>>>
>>>>> raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
>>>>> distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 
>>>>> 10:47:08)
>>>>> select datetime, barometer from archive where datetime > 1642172400 
>>>>> and datetime < 1642693629 order by dateTime;
>>>>> Traceback (most recent call last):
>>>>>   File "tonga_barometer.py", line 47, in 
>>>>> coeff = np.polyfit(xdata, ydata, 2)
>>>>>   File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 
>>>>> 590, in polyfit
>>>>> y = NX.asarray(y) + 0.0
>>>>> TypeError: unsupported operand type(s) for +: 'NoneType' and

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

[storm...@gmail.com]

Modified the query and added the print statement as suggested by Cameron D 
and here are the results:

*Morrowwn Script:*

raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 10:47:08)
select datetime, barometer from archive where datetime > 1642172400 and 
datetime < 1642693629 order by dateTime;
Traceback (most recent call last):
  File "tonga_barometer.py", line 47, in 
coeff = np.polyfit(xdata, ydata, 2)
  File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 590, 
in polyfit
y = NX.asarray(y) + 0.0
TypeError: unsupported operand type(s) for +: 'NoneType' and 'float'


*Cameron D Script*:

raspberrypi:~/Desktop/Tonga $ python3 tonga_baro.py
distance to eruption 12255.7 km arrival at 1642258384 (2022-01-15 09:53:04)
  opposite pulse arrival at 1642306911 (2022-01-15 23:21:50)
  second time around pulse arrival at 1642383509 (2022-01-16 20:38:29)
query returned 96 data points
query returned 96 data points
query returned 95 data points
tonga_baro.py:108: RankWarning: Polyfit may be poorly conditioned
  coeff = np.polyfit(xdata, ydata, 5 )

Note: LAT/Long and speed of sound are identical in both scripts.
On Thursday, January 20, 2022 at 9:27:13 PM UTC-5 Cameron D wrote:

> and add a debug printout for how many result lines there are after ...
> result = cursor.fetchall()
> add the line:
> 
> *print( "query returned {} data points".format(len(result)))*
>
> On Friday, 21 January 2022 at 12:21:59 pm UTC+10 Cameron D wrote:
>
>> To eliminate NULL data points use a query like:
>> select datetime, barometer from archive where datetime > 1642172400 and 
>> datetime < 1642693629* and barometer is not null *order by dateTime;
>>  You could add the part in bold into the query in the python script.
>>
>> Of course, if they are all null...
>>
>> On Friday, 21 January 2022 at 12:14:44 pm UTC+10 storm...@gmail.com 
>> wrote:
>>
>>> Download the latest script from 
>>> https://github.com/morrowwm/weewx_tonga_browse. Beside installing the 
>>> Python Modules Vince stated above, I needed to also install  
>>> python3-scipy. I do have data between 1642172400 and 1642693629; except 
>>> for a couple "null" in that time period.   So when I run the script, I get 
>>> the following error.
>>>
>>> raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
>>> distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 
>>> 10:47:08)
>>> select datetime, barometer from archive where datetime > 1642172400 and 
>>> datetime < 1642693629 order by dateTime;
>>> Traceback (most recent call last):
>>>   File "tonga_barometer.py", line 47, in 
>>> coeff = np.polyfit(xdata, ydata, 2)
>>>   File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 
>>> 590, in polyfit
>>> y = NX.asarray(y) + 0.0
>>> TypeError: unsupported operand type(s) for +: 'NoneType' and 'float'
>>>
>>> There should be a way to check for "null" data within the time period.
>>> On Thursday, January 20, 2022 at 8:12:55 PM UTC-5 Cameron D wrote:
>>>
>>>> yes, definitely looks like there is no data.
>>>> I have attached another version of mine, in which the trend line is 
>>>> disabled by default, but I suspect that would just delay the inevitable 
>>>> and 
>>>> it would crash trying to do the plot.
>>>>
>>>> I also fixed up a few plotting errors in my code to do with the 
>>>> mysteries (to me) of layer ordering.
>>>> I also had a background bar showing either side of expected arrival - 
>>>> in this version I have now changed that to start at the expected arrival 
>>>> and stop 1 hour later.
>>>>
>>>> On Friday, 21 January 2022 at 3:29:36 am UTC+10 bgra...@umw.edu wrote:
>>>>
>>>>> Hello,
>>>>> Not being a programmer, I probably shouldn't have messed with this, 
>>>>> but being curious...
>>>>>
>>>>> I tried the code posted on github as well as the one by Cameron D. In 
>>>>> both cases I got the following error:
>>>>> ```
>>>>> root@n4mrv:/home/bg/weewx_tonga_browse-main# python3 ./tonga.py   [file 
>>>>> from Cameron D]
>>>>>
>>>>> distance to eruption 12056.6 km arrival at 1642258360 (2022-01-15 
>>>>> 09:52:39)
>>>>>   opposite pulse arrival at 1642308921 (2022-01-15 23:55:21)
>>>>>

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

[storm...@gmail.com]

Download the latest script from 
https://github.com/morrowwm/weewx_tonga_browse. Beside installing the 
Python Modules Vince stated above, I needed to also install  python3-scipy. I 
do have data between 1642172400 and 1642693629; except for a couple "null" 
in that time period.   So when I run the script, I get the following error.

raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 10:47:08)
select datetime, barometer from archive where datetime > 1642172400 and 
datetime < 1642693629 order by dateTime;
Traceback (most recent call last):
  File "tonga_barometer.py", line 47, in 
coeff = np.polyfit(xdata, ydata, 2)
  File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 590, 
in polyfit
y = NX.asarray(y) + 0.0
TypeError: unsupported operand type(s) for +: 'NoneType' and 'float'

There should be a way to check for "null" data within the time period.
On Thursday, January 20, 2022 at 8:12:55 PM UTC-5 Cameron D wrote:

> yes, definitely looks like there is no data.
> I have attached another version of mine, in which the trend line is 
> disabled by default, but I suspect that would just delay the inevitable and 
> it would crash trying to do the plot.
>
> I also fixed up a few plotting errors in my code to do with the mysteries 
> (to me) of layer ordering.
> I also had a background bar showing either side of expected arrival - in 
> this version I have now changed that to start at the expected arrival and 
> stop 1 hour later.
>
> On Friday, 21 January 2022 at 3:29:36 am UTC+10 bgra...@umw.edu wrote:
>
>> Hello,
>> Not being a programmer, I probably shouldn't have messed with this, but 
>> being curious...
>>
>> I tried the code posted on github as well as the one by Cameron D. In 
>> both cases I got the following error:
>> ```
>> root@n4mrv:/home/bg/weewx_tonga_browse-main# python3 ./tonga.py   [file 
>> from Cameron D]
>>
>> distance to eruption 12056.6 km arrival at 1642258360 (2022-01-15 
>> 09:52:39)
>>   opposite pulse arrival at 1642308921 (2022-01-15 23:55:21)
>>   second time around pulse arrival at 1642385471 (2022-01-16 21:11:10)
>> Traceback (most recent call last):
>>   File "./tonga.py", line 178, in 
>> plot_burst( cursor, arrival_time, hour_span, "primary" )
>>   File "./tonga.py", line 54, in plot_burst
>> coeff = np.polyfit(xdata, ydata, background_order )
>>   File "<__array_function__ internals>", line 180, in polyfit
>>   File "/usr/local/lib/python3.8/dist-packages/numpy/lib/polynomial.py", 
>> line 638, in polyfit
>> raise TypeError("expected non-empty vector for x")
>> TypeError: expected non-empty vector for x
>> ```
>> I added my lat/lon information but may have missed something else I need 
>> to change. Python modules were installed as directed. Copy of weewx.sdb is 
>> in the same directory as the program.
>> Thanks.
>> Bob
>> On Wednesday, January 19, 2022 at 10:32:49 AM UTC-5 morr...@gmail.com 
>> wrote:
>>
>>> On Wednesday, January 19, 2022 at 12:42:04 a.m. UTC-4 Cameron D wrote:
>>>

- as you get closer to the equator, tidal changes dominate the 
baseline in that timescale - I tried higher order polynomials, but they 
 are 
next to useless.

 I also had little luck with higher order polynomials to remove the 
>>> general trend.
>>>
>>> I've put the script here: https://github.com/morrowwm/weewx_tonga_browse
>>>
>>

-- 
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/21baed8f-5d82-4657-9227-c354eb95169en%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station?

[storm...@gmail.com]

First, not starting any arguments. Second the chart is over a 48 Hr period, 
sample at 5 minutes intervals.  Both my stations had basically shown the 
same increase and decrease for each wave. And according to the following  
link: https://twitter.com/akrherz/status/1482436390105272320, the direct 
wave passed through the area around 15:00 UTC (10:00 AM) and the second 
wave (much strong) from the opposite direction  passed through the 
area around 05:10 UTC (12:10 AM) Jan 16.  

On Monday, January 17, 2022 at 10:51:05 PM UTC-5 ln77 wrote:

> I think you’re looking at the wrong time period.  The initial, direct wave 
> arrived at the U.S. west coast — about 8400 Km from Tonga — around 4:00am 
> Pacific time on Jan 15.  It should take 3-1/2 to 4 hours to travel the 
> additional 4600 Km to your location.  That, plus the 4 hour time 
> difference, would put it at around 12:00 noon your time on Jan 15, not Jan 
> 16.  The long path wave should’ve arrived at your location something like 
> 13-14 hours later, or shortly after midnight on Jan 16.  The second trip 
> around the Earth of the initial wave would be something like 32-36 hours 
> after the first arrival, or 20:00-24:00 your time on Jan 16.  What you’ve 
> plotted here misses all of those.  
>
>   -Les
>
>
>
> On 17 Jan 2022, at 11:58, morr...@gmail.com  wrote:
>
> Not sure I am really seeing it here in maritime Canada. We're about 13000 
> km from Tonga.
>
> Attached is a gnuplot command file and its output is:
>
>

-- 
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/d0009835-c280-4ede-8754-2c9354950cc5n%40googlegroups.com.

[weewx-user] Re: When did the blast wave of the eruption "hit" your station?

[storm...@gmail.com]

Check early morning Jan 16, when the wave came the opposite direction. 
Might of capture that wave.  They say the second wave was stronger on the 
east coast.

[image: Eruption Pressure Blips.png]  

On Monday, January 17, 2022 at 10:24:20 PM UTC-5 robcr...@gmail.com wrote:

> [image: TongaPressureWave.jpg]
> Seattle, Washington! I noticed it the same day, but didn't read y'all's 
> comments till now. Pretty cool. :-)
>
> On Sunday, January 16, 2022 at 2:46:25 AM UTC-8 michael.k...@gmx.at wrote:
>
>> As you may have noticed, there was a huge vulcano eruption in the 
>> southern pacific. The blast wave hit central europe yesterday n the evening 
>> around 20:10 CET.
>>
>> You can observe a steep rise in pressure at the time:
>> [image: 2022-01-16 11_40_47-Das Wetter in Rif - Brave.png]
>> You can see the spike in weewx stations around the world...
>>
>

-- 
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/ce6a3a60-1f40-4e08-8000-26aea498c84cn%40googlegroups.com.

Re: [weewx-user] When die the blast wave of the eruption "hit" your station?

[storm...@gmail.com]

I'm assuming I caught both pulses; first was around Jan 15 10:25 am EST 
(pulse 0.40  ), second  around Jan 16 12:10 am EST (pulse 2.42 mb).

[image: Eruption Pressure Blips.png] 
Both times weather was clear.

On Sunday, January 16, 2022 at 10:07:47 AM UTC-5 christoph...@gmail.com 
wrote:

> I have the same spike here in California around the same time.
>
>
>
> On Sun, Jan 16, 2022 at 7:02 AM Greg Troxel  wrote:
>
>>
>> I did not expect to be able to see this.  I looked at a BME680 that is
>> logging every minute, as I only store 5-minute data in weewx.
>>
>> Nea Boston, MA, US, I saw the peak of the positive spike at 0448 UTC on
>> Jan 16.  Compared to your graph, the amplitude is a bit lower and it's a
>> little more spread out in time.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/rmiiluj9121.fsf%40s1.lexort.com
>> .
>>
>

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

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

[storm...@gmail.com]

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 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/8d40d62e-75da-4b9a-a483-636b3b5b93dcn%40googlegroups.com.

[weewx-user] Re: WeeWX - missing weewx folder in var/www/html

[storm...@gmail.com]

It depends on how you installed Weewx.  Check the following link: 
https://weewx.com/docs/usersguide.htm#Where_to_find_things

On Thursday, December 23, 2021 at 7:57:39 AM UTC-5 familieme...@gmail.com 
wrote:

> Hi after an sd cart crash i had to reinstall weewx. I've tried a lot now, 
> but I can't get the idea - where my html folder "weewx" is, despite 
> repeated instlling it doesn't exist. has anyone ever had something like 
> this? thank you
>

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

[weewx-user] Re: Some missing data in Current Conditions on Standard skin

[storm...@gmail.com]

Bob

Do you have this sensor --- "SenseCAP Wireless CO2 Sensor – LoRaWAN"   By 
default it is set to upload data once an hour according to the 
manufacturer.  Can you change the data upload to 15 or 5 minutes for the 
sensor? 
On Saturday, December 4, 2021 at 3:25:48 PM UTC-5 vince wrote:

> Bob - suggest you think about having your node-red (?) that is capturing 
> the once/hour co2 data write out an intermediate file whenever that 
> happens, and have weewx always read from that scratch file.  That should 
> get you something that should look like a step function where you'd have no 
> nulls, just four 15-minute periods with the same value in it, then four 
> with the next value, and so on.
>
> There are lots of ways for weewx to ingest data from external files 
> nowadays that might be worth a look.  Write a scratch file out 
> periodically, read it always.
>
> Might be worth a try.
>
>

-- 
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/ff7cfe7c-b175-48d0-aba0-edcd6ac721f8n%40googlegroups.com.

[weewx-user] Re: Some missing data in Current Conditions on Standard skin

[storm...@gmail.com]

If Vince's suggestion does not help, try adding the following to your 
weewx.conf:

[Accumulator]
[[co2]]
accumulator = firstlast
extractor = last

On Friday, December 3, 2021 at 6:24:46 PM UTC-5 vince wrote:

> See if $last rather than $current helps (untested)
>
> On Friday, December 3, 2021 at 2:53:22 PM UTC-8 bgra...@umw.edu wrote:
>
>> Hello,
>> With lots of good help from the group, I have my Seeed CO2 monitor (LoRa) 
>> sending data to my weewx.sdb archive. I have weewx 4.5.1 (setup.py) on 
>> Focus Ubuntu.
>>
>> The sensor sends data only every 60 minutes and my archive update is 
>> every15 minutes.
>> Looking at weewx.sdb, I have a reading recorded every hour but a null 
>> every 15 minutes when there is no new data.
>>
>> co2 column
>> 417.0
>> null
>> null
>> null
>> 390.0
>> null
>> null
>> null
>> 394.0
>>
>> My settings in (Standard) index.html.tmpl are:
>> Current Conditions
>>   CO2 level
>>   $current.co2
>> Sometimes I get a data reading and others just "N/A"
>>
>> My settings in weewx.conf:
>> [MQTTSubscribeService]
>> # Turn the service on and off.
>> enable = true
>> binding = loop
>>  [[[mytopic]]]
>> ignore = true
>>  CO2_Value_PPM
>>  name = co2
>>  ignore = false
>>  contains total = false
>>  conversion type = float
>>
>> Since everything seems to be working, the "$current.co2" may not be the 
>> correct form to use here as the display needs to retain the last value 
>> until it's replaced with a new reading coming every 60 minutes from the 
>> sensor.
>>
>> Much appreciated if someone could point out my mistake in configuration 
>> here.
>> The display can be seen at: http://grattans.org/wx
>>
>> Cheers,
>> Bob
>>
>

-- 
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/b666e3b0-3c9a-4cd8-9a98-79ce970cbf1en%40googlegroups.com.

Re: [weewx-user] Re: Getting LoRa data from server into weewx

[storm...@gmail.com]

Glad you have it working now.  What type of CO2 sensor are you using?

On Tuesday, November 30, 2021 at 5:38:43 PM UTC-5 colin@gmail.com wrote:

> Good work Bob, well done getting it sorted :)
>
> Cheers
> Colin
>
> On Wed, 1 Dec 2021 at 09:21, bgra...@umw.edu  wrote:
>
>> I'm very happy to say that I have three successful (hourly) readings of 
>> CO2 in the weewx db, thanks to everyone who has been patient and helpful 
>> with an 81-year-old retired librarian attempting to do something that was 
>> beyond his reach. 
>> [I just heard a cumulative sigh of relief circle 
>> the globe]
>> In the end, my main problem was adjusting the elements in weewx.conf with 
>> a combination of some of the last suggestions. I found that the sensor, 
>> once every 24 hours, sends out a different string of data with battery 
>> information which doesn't include any CO2 data. My next step is setting 
>> up a display of the data with a graph on my main page. 
>>
>> Many thanks again to everyone who helped solve my problem. I now have 
>> another window into the ills that plague our planet
>>
>> Cheers,
>> Bob
>> http://grattans.org/wx
>>
>> On Tuesday, November 30, 2021 at 12:15:33 AM UTC-5 vince wrote:
>>
>>> I'd go with something like..
>>>
>>> [[topics]]
>>> [[[mytopic]]]
>>>CO2_Value_PPM
>>>name = co2
>>>contains total = false
>>>conversion type = float
>>>measurementID
>>>ignore = true
>>>report_telemetry
>>>ignore = true
>>>
>>> Define the topic to subscribe to.
>>> Do not ignore the one element therein that you want.
>>> Ignore the elements you don't want.
>>>
>>> On Monday, November 29, 2021 at 6:20:28 PM UTC-8 storm...@gmail.com 
>>> wrote:
>>>
>>>>  *"Is it possible to have weewx ignore these elements and only process 
>>>> the  "CO2_Value_PPM": 419 ?"  *Yes, Rich provided the possible 
>>>> solution.
>>>>
>>>> * "I'm not sure what "float" does but mayve that's a problem...?"  *A 
>>>> float is a real number.  It is trying to convert  'report_telemetry' which 
>>>> is a string to a real number causing the failure.
>>>>
>>>> On Monday, November 29, 2021 at 9:05:54 PM UTC-5 bell...@gmail.com 
>>>> wrote:
>>>>
>>>>> Bob,
>>>>> You are correct. The extra data is causing the problem. Due to a poor 
>>>>> early design decision, MQTTSubscribe defaults to converting everything to 
>>>>> float. Obviously, 'report_telemetry' cannot be converted to float. The 
>>>>> following configuration should work. It ignores all but 'CO2_Value_PPM'.
>>>>> [[topics]]
>>>>> [[[mytopic]]]
>>>>> ignore = true
>>>>> CO2_Value_PPM
>>>>> name = co2
>>>>> ignore = false
>>>>> If that doesn't work, let me know and I can give a different 
>>>>> configuration.
>>>>> rich
>>>>>
>>>>> On Monday, 29 November 2021 at 19:53:46 UTC-5 bgra...@umw.edu wrote:
>>>>>
>>>>>> Last post of the day, I promise!
>>>>>> I think the node-red flow is working the way it should and reporting 
>>>>>> the parsed message as in my last post.
>>>>>>
>>>>>> weewx.conf configuration (changed topic to "mytopic" in the flow and 
>>>>>> in weewx).
>>>>>>
>>>>>> [MQTTSubscribeService]
>>>>>> # This section is for the MQTTSubscribe service.
>>>>>> enable = true# false
>>>>>>
>>>>>> # The MQTT server.
>>>>>> # Default is localhost.
>>>>>> host = localhost
>>>>>> port = 1883
>>>>>> keepalive = 60
>>>>>>
>>>>>> username = None #admin#None
>>>>>>password = None  #admin#None
>>>>>>   binding = loop
>>>>>>
>>>>>>[[message_callback]]
>>>>>> type = json#REPLACE_ME
>>>>>>
>>>>>> #  mytopic  is the

[weewx-user] Re: Getting LoRa data from server into weewx

[storm...@gmail.com]

 *"Is it possible to have weewx ignore these elements and only process the  
"CO2_Value_PPM": 419 ?"  *Yes, Rich provided the possible solution.

* "I'm not sure what "float" does but mayve that's a problem...?"  *A float 
is a real number.  It is trying to convert  'report_telemetry' which is a 
string to a real number causing the failure.

On Monday, November 29, 2021 at 9:05:54 PM UTC-5 bell...@gmail.com wrote:

> Bob,
> You are correct. The extra data is causing the problem. Due to a poor 
> early design decision, MQTTSubscribe defaults to converting everything to 
> float. Obviously, 'report_telemetry' cannot be converted to float. The 
> following configuration should work. It ignores all but 'CO2_Value_PPM'.
> [[topics]]
> [[[mytopic]]]
> ignore = true
> CO2_Value_PPM
> name = co2
> ignore = false
> If that doesn't work, let me know and I can give a different configuration.
> rich
>
> On Monday, 29 November 2021 at 19:53:46 UTC-5 bgra...@umw.edu wrote:
>
>> Last post of the day, I promise!
>> I think the node-red flow is working the way it should and reporting the 
>> parsed message as in my last post.
>>
>> weewx.conf configuration (changed topic to "mytopic" in the flow and in 
>> weewx).
>>
>> [MQTTSubscribeService]
>> # This section is for the MQTTSubscribe service.
>> enable = true# false
>>
>> # The MQTT server.
>> # Default is localhost.
>> host = localhost
>> port = 1883
>> keepalive = 60
>>
>> username = None #admin#None
>>password = None  #admin#None
>>   binding = loop
>>
>>[[message_callback]]
>> type = json#REPLACE_ME
>>
>> #  mytopic  is the topic to subscribe to.
>> [[topics]]
>>
>> unit_system = US
>>
>> [[[mytopic]]]
>>
>> #data  sent from RAK7244
>> #ignore = true
>> CO2_Value_PPM
>> #weewx db field name
>> name = co2
>> ignore = false
>> contains total = false
>> conversion type = float
>> #units = ppm
>> #[[[SECOND/REPLACE_ME]]]
>>
>> *This is the weewx.log debug info:*
>>
>> Nov 29 19:20:58 n4mrv weewx[17143] DEBUG user.MQTTSubscribe: (Service) 
>> MessageCallbackProvider data-> incoming topic: mytopic, QOS: 0, retain: 0, 
>> payload: b'{\n"CO2_Value_PPM": 419,\n"measurementId": 4100,\n   
>>  "type": "report_telemetry"\n}'
>> Nov 29 19:20:58 n4mrv weewx[17143] ERROR user.MQTTSubscribe: (Service) 
>> MessageCallbackProvider on_message_json failed with > 'user.MQTTSubscribe.ConversionError'> and reason Failed converting field 
>> type with value report_telemetry using 'lambda x: to_float(x)' with reason 
>> could not convert string to float: 'report_telemetry'..
>> Nov 29 19:20:58 n4mrv weewx[17143] ERROR user.MQTTSubscribe: (Service) 
>>  MessageCallbackProvider Ignoring topic=mytopic and payload=b'{\n   
>>  "CO2_Value_PPM": 419,\n"measurementId": 4100,\n"type": 
>> "report_telemetry"\n}'
>> Nov 29 19:20:58 n4mrv weewx[17143] ERROR user.MQTTSubscribe: (Service) 
>>  MessageCallbackProvider Traceback (most recent call last):#012  File 
>> "/home/weewx/bin/user/MQTTSubscribe.py", line 1263, in _convert_value#012   
>>  return conversion_func['compiled'](value)#012  File "", line 1, in 
>> #012  File "/home/weewx/bin/weeutil/weeutil.py", line 1276, in 
>> to_float#012return float(x) if x is not None else None#012ValueError: 
>> could not convert string to float: 'report_telemetry'#012#012During 
>> handling of the above exception, another exception 
>> occurred:#012#012Traceback (most recent call last):#012  File 
>> "/home/weewx/bin/user/MQTTSubscribe.py", line 1427, in _on_message_json#012 
>>(fieldname, value) = self._update_data(fields, fields_conversion_func, 
>> lookup_key, data_flattened[key], unit_system)#012  File 
>> "/home/weewx/bin/user/MQTTSubscribe.py", line 1230, in _update_data#012   
>>  value = self._convert_value(fields, default_field_conversion_func, 
>> orig_name, orig_value)#012  File "/home/weewx/bin/user/MQTTSubscribe.py", 
>> line 1268, in _convert_value#012raise ConversionError("Failed 
>> converting field %s with value %s using '%s' with reason %s." 
>> \#012user.MQTTSubscribe.ConversionError: Failed converting field type with 
>> value report_telemetry using 'lambda x: to_float(x)' with reason could not 
>> convert string to float: 'report_telemetry'.
>> Nov 29 19:20:59 n4mrv weewx[17143] DEBUG user.purple: 
>> new_loop_packet(Event type:  | packet: 
>> {'dateTime': 1638231660, 'usUnits': 1, 'barometer': 30.091, 'inTemp': 79.0, 
>> 'inHumidity': 27.0, 'outTemp': 33.7, 'windSpeed': 0.0, 'windSpeed10': 0.0, 
>> 'windDir': 0, 'extraTemp1': 72.0, 'soilTemp1': 51.0, 'soilTemp2': 97.0, 
>> 'soilTemp4': 47.0, 'leafTemp1': 51.0, 'leafTemp2': 97.0, 'outHumidity': 
>> 74.0, 'rainRate': 0.0, 

[weewx-user] Re: Getting LoRa data from server into weewx

[storm...@gmail.com]

Since you are using Node Red, a possible solution is to use a Change Node 
and delete the payload that you don't want to include in weewx.

On Sunday, November 28, 2021 at 1:41:56 PM UTC-5 bell...@gmail.com wrote:

> I looked more closely at the payload format and I don't think that format 
> is currently supported. specifically the 'nested array'..
>
> "object":{"err":0,"messages":[{"CO2_Value_PPM":433,"measurementId":4100,"type":"report_telemetry"}]
> Busy time of the year, so not sure when I'll have time to delve into a 
> solution.
> rich
> On Sunday, 28 November 2021 at 12:22:22 UTC-5 bell...@gmail.com wrote:
>
>>
>> Bob,
>> Since you have a lot of fields that you want to ignore, try setting the 
>> ignore flag to true at the 'topic' level. Also I don’t think you want to 
>> set contains_total.  So you would end up with something like this, 
>> [[topics]]
>> [[[application/18/device/2cf7f12122500013/rx]]]
>> ignore = true
>> CO2_Value_PPM
>> name = co2
>> ignore = false
>>
>> Since the data is published so infrequently, once you get the basic 
>> configuration working, you might want to look into the expires_after 
>> option. This will cache the value between publications. For additional 
>> information see, 
>> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring-additional-options#expires_after
>>
>> rich
>>
>> On Sunday, 28 November 2021 at 11:21:43 UTC-5 bgra...@umw.edu wrote:
>>
>>> Thanks for coming back so soon with help Storm and Vince.
>>> I am attaching three things in a .txt file rather than pasting in as the 
>>> format seems messy and I'm not sure how to make it easier to read.
>>>
>>> 1.  My modified section of weewx.conf . Among other things, there seems 
>>> to be a problem with float.
>>>
>>> 2.  The data sent from the LoRa server when I subscribe 
>>> to applications/18/devices/2cf7f12122500013/rx  (using MQTT-explorer). Lots 
>>> of unneeded things  but it contains the CO2_Value_PPM data.
>>>
>>> 3.  A listing of weewx.log in debug mode showing the problems (I hope). 
>>> The data seems to be getting there but is not being parsed out for what I 
>>> need.
>>>
>>> Hopefully this will give you an idea of what's going on.  Thanks again 
>>> for your help.
>>> Bob
>>>
>>> On Saturday, November 27, 2021 at 5:36:51 PM UTC-5 vince wrote:
>>>
>>>> My example:
>>>>
>>>> [MQTTSubscribeService]
>>>> enable = True
>>>> host = 192.168.1.171
>>>> port = 1883
>>>> keepalive = 60
>>>> username = None
>>>> password = None
>>>> binding = loop
>>>> [[message_callback]]
>>>> type = json
>>>> [[topics]]
>>>> unit_system = US
>>>> #
>>>> #--- these are emitted every 5 minutes ---
>>>> # mosquitto_sub -t BaseballRoomConditions -h nuc2
>>>> # {"dateTime": 1621715702, "extraTemp1": 63.16, 
>>>> "extraTemp2": 63.5, "pi": 100.28}
>>>> #
>>>> [[[BaseballRoomConditions]]]<=== the topic to subscribe to
>>>> dateTime<=== the element in that topic
>>>> ignore = True   <=== optionally ignore this 
>>>> item within the topic
>>>> extraTemp1
>>>> name = extraTemp1   <=== db element to map the item 
>>>> to
>>>> units = degree_F<=== its units
>>>> extraTemp2
>>>> name = extraTemp2
>>>> units = degree_F
>>>> pi
>>>> ignore = True
>>>>
>>>>
>>>> On Saturday, November 27, 2021 at 2:26:46 PM UTC-8 storm...@gmail.com 
>>>> wrote:
>>>>
>>>>>  I believe you need to add the topic you subscribing to in 
>>>>> [[[first/topic]]]. 
>>>>>
>>>>> Example:
>>>>>
>>>>>
>>>>> ##
>>>>>   #  Acurite-5n1 Sensors
>>

[weewx-user] Re: Getting LoRa data from server into weewx

[storm...@gmail.com]

 I believe you need to add the topic you subscribing to in 
[[[first/topic]]]. 

Example:

##
  #  Acurite-5n1 Sensors
  #  SDR # 1 
  #  433 MHz
  
##
  
 


[[[Acurite-Tower/8785/]]]
   
   temperature_F
name = extraTemp7
ignore = False
contains_total = False
conversion_type = float
units = degree_F

On Saturday, November 27, 2021 at 5:15:24 PM UTC-5 bgra...@umw.edu wrote:

> Hello,
> I'm running a RAK7244 LoRaWAN server/gateway on a local network to which 
> my weewx server is connected. Weeex is the latest stable on Ubuntu with 
> extended db.
>
> A CO2 sensor is sending data to the LoRa server. I have node-red on my 
> weewx server with a flow  connecting to the RAK7244. I want to have the CO2 
> data put into the co2 slot that is available on the weewx db.
>
> I have installed the weewx extension Mosquitto-subscribe and attempted to 
> configure weewx.conf as:
> #
> # Options for 'MQTTSubscribeService'
> [MQTTSubscribeService]
> # This section is for the MQTTSubscribe service.
> # Turn the service on and off.
> # Default is: true
> # Only used by the service.
> enable = true# false
> 
> # The MQTT server.
> # Default is localhost.
> host = localhost  #192.168.1.10#localhost
> 
> # The port to connect to.
> # Default is 1883.
> port = 1883
> 
> # Maximum period in seconds allowed between communications with the 
> broker.
> # Default is 60.
> keepalive = 60
> 
> # username for broker authentication.
> # Default is None.
> username = None
> 
> # password for broker authentication.
> # Default is None.
> password = None 
> 
> # The binding, loop or archive.
> # Default is: loop
> # Only used by the service.
> binding = loop
> 
> # The message handler to use
> [[message_callback]]
> # The format of the MQTT payload.
> # Currently support: individual, json, keyword
> # Must be specified.
> type = json#REPLACE_ME
> 
> # The application/18/device/2cf7f12122500013/rx  topics to subscribe 
> to.
> [[topics]]
> # Units for MQTT payloads without unit value.
> # Valid values: US, METRIC, METRICWX
> # Default is: US
> unit_system = US
> 
> [[[first/topic]]]
>
> #value sent from RAK7244
>
> CO2_Value_PPM
> #weewx db name
> name = co2
> ignore = false
> contains total = True
> conversion type = float
> 
> #[[[SECOND/REPLACE_ME]]]
> 
>
> The message (data) every 60 minutes coming from the node-red function is:
>
> {"CO2_Value_PPM":401} 
>
> I may have too many things going here but, as I'm not a programmer, I'm 
> stuck trying to figure out the problem. The node-red flow is connected on 
> both ends (RAK7244-->weewx) but I don't see any data reaching the db.
>
> Thanks in advance if anyone can help on this.
> Cheers'
> Bob
>
>

-- 
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/fa6dccfd-64e5-4b67-aae1-8224c10b1d78n%40googlegroups.com.

[weewx-user] Re: Acurite Atlas (status?)

[storm...@gmail.com]

By "stable" I mean the oscillator frequency does not drift over time.  That 
will be fine for what you want to do.

On Tuesday, November 16, 2021 at 8:13:08 PM UTC-5 kkru...@gmail.com wrote:

> By "stable" do you mean signal strength / quality / SNR, lapses in 
> connection, availability to the OS, or something else? 
> I'm not too concerned about interference as the location for this is quite 
> rural, in the woods. 
>
> Unfortunately, I ordered the NESDR Mini 2 before reading your comment. Yet 
> I'm wondering if it it'll be "good enough" for what I'm trying to 
> accomplish. 
>
> On Monday, November 15, 2021 at 8:02:31 PM UTC-8 storm...@gmail.com wrote:
>
>> In my opinion, I would look at something like this:
>>
>>
>> https://www.amazon.com/NooElec-NESDR-Smart-Bundle-R820T2-Based/dp/B01GDN1T4S/ref=sr_1_4?keywords=rtl-sdr=1637035059=8-4
>>
>> The V3/V4 versions are much more stable then the originals.
>>
>>
>> On Monday, November 15, 2021 at 10:07:38 PM UTC-5 kkru...@gmail.com 
>> wrote:
>>
>>> Thanks so much for the responses so far. Stephen... I think I've seen 
>>> some of your posts re: Atlas. I may just give this another chance with the 
>>> SDR. Can you (or anyone) tell me if one or both of these works out of the 
>>> box:
>>>
>>> https://www.nooelec.com/store/sdr/sdr-receivers/nesdr-mini.html
>>> https://www.nooelec.com/store/sdr/sdr-receivers/nesdr-mini-2.html
>>>
>>> And thanks Vince for informing me about the Ecowitt products. I haven't 
>>> looked at those until now. Very interesting! 
>>>
>>> On Monday, November 15, 2021 at 3:59:29 PM UTC-8 vince wrote:
>>>
>>>> You can get into ecowitt 'very' inexpensively especially if you don't 
>>>> need a display.  Gary's weewx driver is very solid.
>>>>
>>>> Disclaimer - the gateway module requires internet connectivity or it'll 
>>>> reboot very often due to its watchdog timers.  If that's ok for your site, 
>>>> you might want to give them a look.
>>>>
>>>> Poke around https://www.amazon.com/ecowitt/s?k=ecowitt for 
>>>> possibilities.   You can do it ala-carte piece by piece or they have more 
>>>> integrated solutions with/without a console.
>>>>
>>>>
>>>>

-- 
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/90a38794-c0fd-4044-b277-de183c8688aan%40googlegroups.com.

[weewx-user] Re: Acurite Atlas (status?)

[storm...@gmail.com]

In my opinion, I would look at something like this:

https://www.amazon.com/NooElec-NESDR-Smart-Bundle-R820T2-Based/dp/B01GDN1T4S/ref=sr_1_4?keywords=rtl-sdr=1637035059=8-4

The V3/V4 versions are much more stable then the originals.


On Monday, November 15, 2021 at 10:07:38 PM UTC-5 kkru...@gmail.com wrote:

> Thanks so much for the responses so far. Stephen... I think I've seen some 
> of your posts re: Atlas. I may just give this another chance with the SDR. 
> Can you (or anyone) tell me if one or both of these works out of the box:
>
> https://www.nooelec.com/store/sdr/sdr-receivers/nesdr-mini.html
> https://www.nooelec.com/store/sdr/sdr-receivers/nesdr-mini-2.html
>
> And thanks Vince for informing me about the Ecowitt products. I haven't 
> looked at those until now. Very interesting! 
>
> On Monday, November 15, 2021 at 3:59:29 PM UTC-8 vince wrote:
>
>> You can get into ecowitt 'very' inexpensively especially if you don't 
>> need a display.  Gary's weewx driver is very solid.
>>
>> Disclaimer - the gateway module requires internet connectivity or it'll 
>> reboot very often due to its watchdog timers.  If that's ok for your site, 
>> you might want to give them a look.
>>
>> Poke around https://www.amazon.com/ecowitt/s?k=ecowitt for 
>> possibilities.   You can do it ala-carte piece by piece or they have more 
>> integrated solutions with/without a console.
>>
>>
>>

-- 
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/2a812184-f91e-4743-bf9e-e6cf0a20a0b7n%40googlegroups.com.

[weewx-user] Re: Cheetah Template --see if a variable contains a certain string value

[storm...@gmail.com]

Sorry Gary been a little busy here.  Yes it does work.

On Monday, September 13, 2021 at 8:46:01 PM UTC-4 storm...@gmail.com wrote:

> Thanks Gary for quick response.  I will give that a try.
>
> On Monday, September 13, 2021 at 8:41:44 PM UTC-4 gjr80 wrote:
>
>> Simple, just some in-line python code. Something like (untested):
>>
>> #if 'some_string' in $my_string
>> ## 'some_string' is in $my_string, do something 
>> #pass
>> #else
>> ## 'some_string' is not in $my_string, do something else 
>> #pass
>> #end if
>>
>> Gary
>>
>> On Tuesday, 14 September 2021 at 10:33:59 UTC+10 storm...@gmail.com 
>> wrote:
>>
>>> Wondering if there is a way using Cheetah to check for a string value in 
>>> a variable.
>>
>>

-- 
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/a34e3587-3f46-407b-a79b-8cefa81223e1n%40googlegroups.com.

Re: [weewx-user] Import MQTT value into weewx database, display via seasons skin

[storm...@gmail.com]

Take a look at these links:

https://github.com/weewx/weewx/wiki/mqtt
https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/
https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki

On Wednesday, September 15, 2021 at 4:30:35 PM UTC-4 bgra...@umw.edu wrote:

> Vince and everyone,
> I have a RAK7244 LoRa (chirpstack) setup on my LAN that is getting data 
> from two LHT65 temp/hum sensors. All seems to be working correctly. 
> My goal is to import the data into weewx which I have running on an rpi. 
> Not being a programmer, I seem to be WAY OVER my head with how to set up 
> mqtt and deal with json files. I have tried the python program kindly 
> offered by Ralph Underwood and it seems to be subscribing to the json data:
>
> MQTT_SERVER = "192.168.1.10"
> MQTT_TOPIC = "application/#"  *** [using '#' to get everything]
>
> Connected with result code 0
> application/7/device/a8404117b18312e9/rx 
> {"applicationID":"7","applicationName":"LHT65","deviceName":"LHT65x","devEUI":"a8404117b18312e9","txInfo":{"frequency":90510,"dr":0},"adr":true,"fCnt":1376,"fPort":2,"data":"y+wJUAHgAQlHf/8=","object":{"BatV":3.052,"Ext_sensor":"Temperature
>  
> Sensor LHT65","Hum_SHT":"48.0","TempF_DS":"74.75","TempF_SHT":"74.91"}}
> {"applicationID":"7","applicationName":"LHT65","deviceName":"LHT65x","devEUI":"a8404117b18312e9","txInfo":{"frequency":90510,"dr":0},"adr":true,"fCnt":1376,"fPort":2,"data":"y+wJUAHgAQlHf/8=","object":{"BatV":3.052,"Ext_sensor":"Temperature
>  
> Sensor LHT65","Hum_SHT":"48.0","TempF_DS":"74.75","TempF_SHT":"74.91"}}
>
> application/7/device/a84041468182b4da/rx 
> {"applicationID":"7","applicationName":"LHT65","deviceName":"LHT65-1","devEUI":"a84041468182b4da","txInfo":{"frequency":90430,"dr":0},"adr":true,"fCnt":1367,"fPort":2,"data":"y9ELFQGRAQr2f/8=","object":{"BatV":3.025,"Ext_sensor":"Temperature
>  
> Sensor LHT65","Hum_SHT":"40.1","TempF_DS":"82.51","TempF_SHT":"83.07"}}
> {"applicationID":"7","applicationName":"LHT65","deviceName":"LHT65-1","devEUI":"a84041468182b4da","txInfo":{"frequency":90430,"dr":0},"adr":true,"fCnt":1367,"fPort":2,"data":"y9ELFQGRAQr2f/8=","object":{"BatV":3.025,"Ext_sensor":"Temperature
>  
> Sensor LHT65","Hum_SHT":"40.1","TempF_DS":"82.51","TempF_SHT":"83.07"}}
>
> At this point I'm not sure what to do to get the data into weewx. If 
> anyone can offer a suggestion I would be most grateful. 
> Thanks.
> Bob
>
> On Saturday, April 6, 2019 at 10:04:28 AM UTC-4 vince wrote:
>
>> On Saturday, April 6, 2019 at 6:52:06 AM UTC-7, Ralph Underwood wrote:
>>>
>>> I have a small python program that subscribes to mqtt and writes a text 
>>> file. I then use the filepile as a service to get the data into WeeWx. The 
>>> "main" data comes from a Ultimeter station via the driver.
>>>
>>>
>>>
>> I have a similar setup that reads pi sensors and writes a JSON file that 
>> nginx serves up on a secondary pi.  I wrote a weewx service that grabs that 
>> file and populates a custom weewx db, although the code is somewhat ugly 
>> under the hood to say the least.
>>
>> A better example is the weatherflow UDP driver.  That does a web get of a 
>> JSON formatted file, maps the elements to a database schema of your 
>> choosing, and populates the database.   Very very stable.  It would be a 
>> great example for how to grab a web endpoint and populate a custom db.
>>
>>
>>

-- 
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/ccfd9751-4e5a-4e67-b44d-e17b024c3140n%40googlegroups.com.

[weewx-user] Re: Cheetah Template --see if a variable contains a certain string value

[storm...@gmail.com]

Thanks Gary for quick response.  I will give that a try.

On Monday, September 13, 2021 at 8:41:44 PM UTC-4 gjr80 wrote:

> Simple, just some in-line python code. Something like (untested):
>
> #if 'some_string' in $my_string
> ## 'some_string' is in $my_string, do something 
> #pass
> #else
> ## 'some_string' is not in $my_string, do something else 
> #pass
> #end if
>
> Gary
>
> On Tuesday, 14 September 2021 at 10:33:59 UTC+10 storm...@gmail.com wrote:
>
>> Wondering if there is a way using Cheetah to check for a string value in 
>> a variable.
>
>

-- 
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/de3c2491-6d7c-4308-8dd6-8e5ba0a3d60cn%40googlegroups.com.

[weewx-user] Cheetah Template --see if a variable contains a certain string value

[storm...@gmail.com]

Wondering if there is a way using Cheetah to check for a string value in a 
variable.

-- 
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/bf09-af6b-4c33-9e7a-8e4b426f67ffn%40googlegroups.com.

Re: [weewx-user] Fog detection?

[storm...@gmail.com]

In general, the possibility of fog developing is when the dewpoint spread 
is less then  5 degrees F.

On Tuesday, August 31, 2021 at 6:02:58 PM UTC-4 n0...@n0nb.us wrote:

> * On 2021 31 Aug 14:35 -0500, František Slimařík wrote:
> > 
> > Hi all,
> > 
> > I got question for hardcore meteorologists here. Is it possible to 
> detect 
> > fog based on classic meassured values like temperature, humidity, 
> preasure, 
> > etc?
> > Logically I would say fog appears when dew point equals current 
> > temeperature but I guess it will not be so easy. Fogs didn't appear here 
> > this year in my locality so I am waiting for autumn to start with 
> > observations.
>
> I'm certainly no meteorologist!
>
> It seems we've had more foggy mornings this summer than in years past.
> Humidity has certainly been high with only a handful of stretches with
> more than a day below 50% relative humidity.
>
> Many times it seems as though warm air over cooler moist ground is
> necessary for its formation. I don't think this is a temperature
> inversion, as such, but they also seem to sometimes be quite localized
> and are related to some interesting effects.
>
> I along with other radio amateurs and possibly Greg find the effects of
> these weather phenomena on VHF and UHF radio propagation interesting.
>
> - Nate
>
> -- 
> "The optimist proclaims that we live in the best of all
> possible worlds. The pessimist fears this is true."
> Web: https://www.n0nb.us
> Projects: https://github.com/N0NB
> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
>
>

-- 
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/9220d1ae-4b82-4b85-998b-e331388b9b93n%40googlegroups.com.

[weewx-user] Re: Looking for example MQTTSubscribe configurations

[storm...@gmail.com]

Here is what I have currently.   It is definitely a work in progress.  I'm 
subscribing to a broker on a second RPI, which receiving its data from two 
SDRs.  Additionally goes out on web (Every 5 minutes) to download Alerts. 

[MQTTSubscribeService]

# This section is for the MQTTSubscribe service.
# Turn the service on and off.
# Default is: true
# Only used by the service.
enable = true

# The MQTT server.
# Default is localhost.
host = 192.168.1.240

# The port to connect to.
# Default is 1883.
port = 1883

# Maximum period in seconds allowed between communications with the 
broker.
# Default is 60.
keepalive = 60

# username for broker authentication.
# Default is None.
username = None

# password for broker authentication.
# Default is None.
password = None

# The binding, loop or archive.
# Default is: loop
# Only used by the service.
binding = loop

# The message handler to use
[[message_callback]]

# The format of the MQTT payload.
# Currently support: individual, json, keyword
# Must be specified.
type = json

# The topics to subscribe to.
[[topics]]

# Units for MQTT payloads without unit value.
# Valid values: US, METRIC, METRICWX
# Default is: US
unit_system = US

# With the exception of wind data, by default a packet is created 
for every MQTT message received.
# When this is true, MQTTSubscribe attempts to collect observations 
across messages into a packet.
# Default is False.
# This is experimental and may be removed.
collect_observations = True

# With the exception of wind data, by default a queue is created 
for every MQTT topic.
# When this is true, MQTTSubsribe uses a single queue for all non 
wind data.
# This is useful when 'collect_observations = True'.
# Default is False.
# This is experimental and may be removed.
single_queue = True
  
  
  
##
  #  Fineoffset-WH51 Sensors
  #  SDR # 2 
  #  915 MHz
  
##
 
  
  
[[[Fineoffset-WH51/00e121/]]]
  
model
# True if the incoming data should not be processed into 
WeeWX.
# Valid values: True, False
# Default is False
ignore = True

id
# True if the incoming data should not be processed into 
WeeWX.
# Valid values: True, False
# Default is False
ignore = True

battery_ok
# True if the incoming data should not be processed into 
WeeWX.
# Valid values: True, False
# Default is False
ignore = True

battery_mV
# True if the incoming data should not be processed into 
WeeWX.
# Valid values: True, False
# Default is False
ignore = True

boost
# True if the incoming data should not be processed into 
WeeWX.
# Valid values: True, False
# Default is False
ignore = True

moisture

# The WeeWX name.
# Default is the name from MQTT.
name = soilMoist1

# True if the incoming data should not be processed into 
WeeWX.
# Valid values: True, False
# Default is False
ignore = False

# True if the incoming data is cumulative.
# Valid values: True, False
# Default is False
contains_total = False

# The conversion type necessary for WeeWX compatibility
# Valid values: bool, float, int, none
# Default is float
conversion_type = float  

ad_raw
# True if the incoming data should not be processed into 
WeeWX.
# Valid values: True, False
# Default is False
ignore = True


mic
# True if the incoming data should not be processed into 
WeeWX.
# Valid values: True, False
# Default is False
ignore = True

mod
# True if the incoming data should not be processed into 
WeeWX.

Re: [weewx-user] Weewx DB Column Data Types

[storm...@gmail.com]

I'll look into writing  an xtype extension(s).

On Tuesday, August 17, 2021 at 2:21:04 PM UTC-4 tke...@gmail.com wrote:

> From a strict data science point of view, you’re better off  deriving 
> those from primary observations. Writing an xtype extension would be more 
> effective.
>
> On Tue, Aug 17, 2021 at 10:27 AM storm...@gmail.com  
> wrote:
>
>> Thanks Tom, that did the trick.  
>>
>> Some general information on the two text fields:
>>
>> Lightning Frequency is based on number of Lightning Strikes over 5 minute 
>> period
>> '' --- 0 
>> Occasional --- 1 to 5
>> Frequent --- 6 to 30
>> Continuous --- over 31
>>  
>> Comfort level is based off of the dewpoint.
>> Pleasant dp <= 55.9
>> Comfortable dp between 56.0 --- 60.9
>> Getting Sticky dp between 61.0 --- 65.9
>> Uncomfortable dp between 66.0 --- 70.9
>> Oppressive dp between 71.0 --- 75.9 
>> Miserable dp > 76.0
>>
>> Rich
>> On Tuesday, August 17, 2021 at 11:54:34 AM UTC-4 tke...@gmail.com wrote:
>>
>>> Oops. I forgot yet another step! TEXT types cannot use the daily 
>>> summaries, so they should be left out of the schema for the summaries:
>>>
>>> day_summaries = [(e[0], 'scalar') for e in table
>>>  if e[0] not in ('dateTime', 'usUnits', 'interval', 
>>>'lightning_frequency', 'comfort_level')] + [('wind', 
>>> 'VECTOR')]
>>>
>>> If you don't want to start all over, you can just drop the two tables:
>>>
>>> *sqlite3 weewx.sdb*
>>> sqlite> *DROP TABLE archive_day_lightning_frequency;*
>>> sqlite> *DROP TABLE archive_day_comfort_level;*
>>> sqlite> *.quit*
>>>
>>> This is getting complicated enough that we probably should have some 
>>> directions in either the *Customizing Guide* or in the wiki for how to 
>>> do this. I've created issue #688 
>>> <https://github.com/weewx/weewx/issues/688> to track.
>>>
>>> On Tue, Aug 17, 2021 at 8:19 AM storm...@gmail.com  
>>> wrote:
>>>
>>>> The accumulator stanza was configured correctly in weewx.conf.  
>>>> Everything works as expected but still have the following error:
>>>>
>>>> Aug 17 11:15:24 raspberrypi weewx[8482] ERROR weewx.manager: Replace 
>>>> failed for database weewx.sdb: table archive_day_comfort_level has 9 
>>>> columns but 5 values were supplied
>>>> Aug 17 11:15:24 raspberrypi weewx[8482] ERROR weewx.manager: Replace 
>>>> failed for database weewx.sdb: table archive_day_lightning_frequency has 9 
>>>> columns but 5 values were supplied
>>>> Aug 17 11:15:24 raspberrypi weewx[8482] INFO weewx.manager: Added 
>>>> record 2021-08-17 11:15:00 EDT (1629213300) to database 'weewx.sdb'
>>>> Aug 17 11:15:24 raspberrypi weewx[8482] ERROR weewx.manager: Replace 
>>>> failed for database weewx.sdb: table archive_day_comfort_level has 9 
>>>> columns but 5 values were supplied
>>>> Aug 17 11:15:24 raspberrypi weewx[8482] ERROR weewx.manager: Replace 
>>>> failed for database weewx.sdb: table archive_day_lightning_frequency has 9 
>>>> columns but 5 values were supplied
>>>>
>>>> I'm summing the reason for this error is the those fields are text 
>>>> values not the expected integer or real values.
>>>>
>>>> Rich 
>>>>
>>>>
>>>> On Tuesday, August 17, 2021 at 8:30:50 AM UTC-4 tke...@gmail.com wrote:
>>>>
>>>>> The problem is that I forgot a step. In weewx.conf, you need to set an 
>>>>> appropriate extractor for the string. For example,
>>>>>
>>>>> [Accumulator]
>>>>> [[comfort_level]]
>>>>> accumulator = firstlast
>>>>> extractor = last
>>>>> [[lightning_frequency]]
>>>>> accumulator = firstlast
>>>>> extractor = last
>>>>>
>>>>>
>>>>> This means that what will be stored in the database will be the last 
>>>>> value seen during an archive period. An alternative is "first".
>>>>>
>>>>> One other detail: if you want to use it in tags, you also need to 
>>>>> specify the ".raw" suffix. For example:
>>>>>
>>>>> Current = $current.comfort_level.raw
>>>>> First string of the day = $day.comfort_level.first.raw
>>>

Re: [weewx-user] Weewx DB Column Data Types

[storm...@gmail.com]

Thanks Tom, that did the trick.  

Some general information on the two text fields:

Lightning Frequency is based on number of Lightning Strikes over 5 minute 
period
'' --- 0 
Occasional --- 1 to 5
Frequent --- 6 to 30
Continuous --- over 31
 
Comfort level is based off of the dewpoint.
Pleasant dp <= 55.9
Comfortable dp between 56.0 --- 60.9
Getting Sticky dp between 61.0 --- 65.9
Uncomfortable dp between 66.0 --- 70.9
Oppressive dp between 71.0 --- 75.9 
Miserable dp > 76.0

Rich
On Tuesday, August 17, 2021 at 11:54:34 AM UTC-4 tke...@gmail.com wrote:

> Oops. I forgot yet another step! TEXT types cannot use the daily 
> summaries, so they should be left out of the schema for the summaries:
>
> day_summaries = [(e[0], 'scalar') for e in table
>  if e[0] not in ('dateTime', 'usUnits', 'interval', 
>'lightning_frequency', 'comfort_level')] + [('wind', 
> 'VECTOR')]
>
> If you don't want to start all over, you can just drop the two tables:
>
> *sqlite3 weewx.sdb*
> sqlite> *DROP TABLE archive_day_lightning_frequency;*
> sqlite> *DROP TABLE archive_day_comfort_level;*
> sqlite> *.quit*
>
> This is getting complicated enough that we probably should have some 
> directions in either the *Customizing Guide* or in the wiki for how to do 
> this. I've created issue #688 <https://github.com/weewx/weewx/issues/688> 
> to track.
>
> On Tue, Aug 17, 2021 at 8:19 AM storm...@gmail.com  
> wrote:
>
>> The accumulator stanza was configured correctly in weewx.conf.  
>> Everything works as expected but still have the following error:
>>
>> Aug 17 11:15:24 raspberrypi weewx[8482] ERROR weewx.manager: Replace 
>> failed for database weewx.sdb: table archive_day_comfort_level has 9 
>> columns but 5 values were supplied
>> Aug 17 11:15:24 raspberrypi weewx[8482] ERROR weewx.manager: Replace 
>> failed for database weewx.sdb: table archive_day_lightning_frequency has 9 
>> columns but 5 values were supplied
>> Aug 17 11:15:24 raspberrypi weewx[8482] INFO weewx.manager: Added record 
>> 2021-08-17 11:15:00 EDT (1629213300) to database 'weewx.sdb'
>> Aug 17 11:15:24 raspberrypi weewx[8482] ERROR weewx.manager: Replace 
>> failed for database weewx.sdb: table archive_day_comfort_level has 9 
>> columns but 5 values were supplied
>> Aug 17 11:15:24 raspberrypi weewx[8482] ERROR weewx.manager: Replace 
>> failed for database weewx.sdb: table archive_day_lightning_frequency has 9 
>> columns but 5 values were supplied
>>
>> I'm summing the reason for this error is the those fields are text values 
>> not the expected integer or real values.
>>
>> Rich 
>>
>>
>> On Tuesday, August 17, 2021 at 8:30:50 AM UTC-4 tke...@gmail.com wrote:
>>
>>> The problem is that I forgot a step. In weewx.conf, you need to set an 
>>> appropriate extractor for the string. For example,
>>>
>>> [Accumulator]
>>> [[comfort_level]]
>>> accumulator = firstlast
>>> extractor = last
>>> [[lightning_frequency]]
>>> accumulator = firstlast
>>> extractor = last
>>>
>>>
>>> This means that what will be stored in the database will be the last 
>>> value seen during an archive period. An alternative is "first".
>>>
>>> One other detail: if you want to use it in tags, you also need to 
>>> specify the ".raw" suffix. For example:
>>>
>>> Current = $current.comfort_level.raw
>>> First string of the day = $day.comfort_level.first.raw
>>> Last string = $day.comfort_level.last.raw
>>>
>>>
>>> -tk
>>>
>>>
>>>
>>> On Tue, Aug 17, 2021 at 4:52 AM Tom Keffer  wrote:
>>>
>>>> I was able to reproduce the problem. 
>>>>
>>>> Let me work on a solution. 
>>>>
>>>> -tk
>>>>
>>>> On Mon, Aug 16, 2021 at 9:50 PM storm...@gmail.com  
>>>> wrote:
>>>>
>>>>> Tom
>>>>>
>>>>> Added two columns via the schema:  comfort_level and  
>>>>> lightning_frequency; in which the data types are TEXT. Again the database 
>>>>> gets populated with the correct data.
>>>>>
>>>>> Aug 17 00:35:26 raspberrypi weewx[1359] ERROR weewx.manager: Replace 
>>>>> failed for database weewx.sdb: table archive_day_comfort_level has 9 
>>>>> columns but 5 values were supplied
>>>>> Aug 17 00:35:26 raspberrypi weewx[1359] ERROR weewx.manager: Replace 
&

Re: [weewx-user] Weewx DB Column Data Types

[storm...@gmail.com]

The accumulator stanza was configured correctly in weewx.conf.  Everything 
works as expected but still have the following error:

Aug 17 11:15:24 raspberrypi weewx[8482] ERROR weewx.manager: Replace failed 
for database weewx.sdb: table archive_day_comfort_level has 9 columns but 5 
values were supplied
Aug 17 11:15:24 raspberrypi weewx[8482] ERROR weewx.manager: Replace failed 
for database weewx.sdb: table archive_day_lightning_frequency has 9 columns 
but 5 values were supplied
Aug 17 11:15:24 raspberrypi weewx[8482] INFO weewx.manager: Added record 
2021-08-17 11:15:00 EDT (1629213300) to database 'weewx.sdb'
Aug 17 11:15:24 raspberrypi weewx[8482] ERROR weewx.manager: Replace failed 
for database weewx.sdb: table archive_day_comfort_level has 9 columns but 5 
values were supplied
Aug 17 11:15:24 raspberrypi weewx[8482] ERROR weewx.manager: Replace failed 
for database weewx.sdb: table archive_day_lightning_frequency has 9 columns 
but 5 values were supplied

I'm summing the reason for this error is the those fields are text values 
not the expected integer or real values.

Rich 


On Tuesday, August 17, 2021 at 8:30:50 AM UTC-4 tke...@gmail.com wrote:

> The problem is that I forgot a step. In weewx.conf, you need to set an 
> appropriate extractor for the string. For example,
>
> [Accumulator]
> [[comfort_level]]
> accumulator = firstlast
> extractor = last
> [[lightning_frequency]]
> accumulator = firstlast
> extractor = last
>
>
> This means that what will be stored in the database will be the last value 
> seen during an archive period. An alternative is "first".
>
> One other detail: if you want to use it in tags, you also need to specify 
> the ".raw" suffix. For example:
>
> Current = $current.comfort_level.raw
> First string of the day = $day.comfort_level.first.raw
> Last string = $day.comfort_level.last.raw
>
>
> -tk
>
>
>
> On Tue, Aug 17, 2021 at 4:52 AM Tom Keffer  wrote:
>
>> I was able to reproduce the problem. 
>>
>> Let me work on a solution. 
>>
>> -tk
>>
>> On Mon, Aug 16, 2021 at 9:50 PM storm...@gmail.com  
>> wrote:
>>
>>> Tom
>>>
>>> Added two columns via the schema:  comfort_level and  
>>> lightning_frequency; in which the data types are TEXT. Again the database 
>>> gets populated with the correct data.
>>>
>>> Aug 17 00:35:26 raspberrypi weewx[1359] ERROR weewx.manager: Replace 
>>> failed for database weewx.sdb: table archive_day_comfort_level has 9 
>>> columns but 5 values were supplied
>>> Aug 17 00:35:26 raspberrypi weewx[1359] ERROR weewx.manager: Replace 
>>> failed for database weewx.sdb: table archive_day_lightning_frequency has 9 
>>> columns but 5 values were supplied
>>> Aug 17 00:35:26 raspberrypi weewx[1359] INFO weewx.manager: Added record 
>>> 2021-08-17 00:35:00 EDT (1629174900) to database 'weewx.sdb'
>>> Aug 17 00:35:26 raspberrypi weewx[1359] ERROR weewx.manager: Replace 
>>> failed for database weewx.sdb: table archive_day_comfort_level has 9 
>>> columns but 5 values were supplied
>>> Aug 17 00:35:26 raspberrypi weewx[1359] ERROR weewx.manager: Replace 
>>> failed for database weewx.sdb: table archive_day_lightning_frequency has 9 
>>> columns but 5 values were supplied
>>>
>>> This is the schema:
>>>
>>> table = [('dateTime', 'INTEGER NOT NULL UNIQUE PRIMARY KEY'),
>>>  ('usUnits',  'INTEGER NOT NULL'),
>>>  ('interval', 'INTEGER NOT NULL'),
>>>  ('altimeter','REAL'),
>>>  ('appTemp',  'REAL'),
>>>  ('appTemp1', 'REAL'),
>>>  ('barometer','REAL'),
>>>  ('batteryStatus1',   'REAL'),
>>>  ('batteryStatus2',   'REAL'),
>>>  ('batteryStatus3',   'REAL'),
>>>  ('batteryStatus4',   'REAL'),
>>>  ('batteryStatus5',   'REAL'),
>>>  ('batteryStatus6',   'REAL'),
>>>  ('batteryStatus7',   'REAL'),
>>>  ('batteryStatus8',   'REAL'),
>>>  ('cloudbase','REAL'),
>>>  ('co',   'REAL'),
>>>  ('co2',  'REAL'),
>>>  ('consBatteryVoltage',   'REAL'),
>>>  ('dewpoint', 'REAL'),
>>>  ('dewpoint1','REAL'),
>>>  ('ET',   'REAL'),
>>>  ('extraHumid1',  'REAL'),
>>>  

Re: [weewx-user] Weewx DB Column Data Types

[storm...@gmail.com]

'),
 ('snowBatteryStatus','REAL'),
 ('snowDepth','REAL'),
 ('snowMoisture', 'REAL'),
 ('snowRate', 'REAL'),
 ('so2',  'REAL'),
 ('soilMoist1',   'REAL'),
 ('soilMoist2',   'REAL'),
 ('soilMoist3',   'REAL'),
 ('soilMoist4',   'REAL'),
 ('soilTemp1','REAL'),
 ('soilTemp2','REAL'),
 ('soilTemp3','REAL'),
 ('soilTemp4','REAL'),
 ('supplyVoltage','REAL'),
 ('txBatteryStatus',  'REAL'),
 ('UV',   'REAL'),
 ('uvBatteryStatus',  'REAL'),
 ('windBatteryStatus','REAL'),
 ('windchill','REAL'),
 ('windDir',  'REAL'),
 ('windGust', 'REAL'),
 ('windGustDir',  'REAL'),
 ('windrun',  'REAL'),
 ('windSpeed','REAL'),
 ('lightning_frequency',  'TEXT'),
 ('comfort_level','TEXT'),
 ]

day_summaries = [(e[0], 'scalar') for e in table
 if e[0] not in ('dateTime', 'usUnits', 'interval')] + 
[('wind', 'VECTOR')]

schema = {
'table': table,
'day_summaries' : day_summaries
}

Rich
On Monday, August 16, 2021 at 10:32:02 PM UTC-4 storm...@gmail.com wrote:

> Tom
>
> I tried adding the column using the following command: 
>
> wee_database --add-column=lightning_frequency --type=TEXT
>
> It does add the column and populates the data but generates an error 
> during the archival cycle. I guess it looking for integers and real type 
> values.
>
> Aug 16 22:00:22 raspberrypi weewx[24285] ERROR weewx.manager: Replace 
> failed for database weewx.sdb: table archive_day_lightning_frequency has 9 
> columns but 5 values were supplied
> Aug 16 22:00:22 raspberrypi weewx[24285] INFO weewx.manager: Added record 
> 2021-08-16 22:00:00 EDT (1629165600) to database 'weewx.sdb'
> Aug 16 22:00:22 raspberrypi weewx[24285] ERROR weewx.manager: Replace 
> failed for database weewx.sdb: table archive_day_lightning_frequency has 9 
> columns but 5 values were supplied
>
> Next I will try adding using the schema.
>
> Rich
> On Monday, August 16, 2021 at 6:55:55 PM UTC-4 tke...@gmail.com wrote:
>
>> Can't say that I've tried that, but I don't see why it wouldn't work. 
>> It's certainly simpler.
>>
>> Let me know how it goes.
>>
>> On Mon, Aug 16, 2021 at 9:11 AM storm...@gmail.com  
>> wrote:
>>
>>> Thanks Tom.
>>>
>>> I have another question before proceeding.  Do I need to physically 
>>> update the schema to include column and type or could I just use the 
>>> following command:  
>>>
>>> wee_database --add-column=comments --type=TEXT
>>>
>>> Rich
>>>
>>> On Monday, August 16, 2021 at 8:29:16 AM UTC-4 tke...@gmail.com wrote:
>>>
>>>> Good question. Yes, it is possible to store text. 
>>>>
>>>> 1. Assuming you're using sqlite, make sure you read their documentation 
>>>> on data types: https://sqlite.org/datatype3.html
>>>>
>>>> 2. Create a new schema accordingly. For example,
>>>>
>>>> table = [('dateTime', 'INTEGER NOT NULL UNIQUE PRIMARY KEY'),
>>>>  ('usUnits', 'INTEGER NOT NULL'),
>>>>  ('interval', 'INTEGER NOT NULL'),
>>>>  ('outTemp',  'REAL'),
>>>>  ('comments', 'TEXT')
>>>>  ]
>>>>
>>>>
>>>> day_summaries = [('outTemp', 'scalar'), ('comments', 'scalar')]
>>>>
>>>> schema = {
>>>> 'table': table,
>>>> 'day_summaries' : day_summaries
>>>> }
>>>>
>>>>
>>>> This is just an example. Your schema is likely to have many more types 
>>>> than this.
>>>>
>>>> 3. See the directions in the Customizing Guide for how to specify that 
>>>> your new schema be used. *Picking a starting schema 
>>>> <http://www.weewx.com/docs/customizing.htm#Picking_a_starting_schema>*.
>>>>
>>>> 4. Read the developer's notes on Accumulators 
>>>> <https://github.com/weewx/weewx/wiki/Accumulators>. In your weewx.conf 
>>>> file, specify that your text type should be accumulated using the "
>>>> firstlast" accumulator. This will prevent it from trying to find the 
>>>> average, etc, of a string.
>>>>
>>>> [Accumulator]
>>>> [[comments]]
>>>>   

Re: [weewx-user] Weewx DB Column Data Types

[storm...@gmail.com]

Tom

I tried adding the column using the following command: 

wee_database --add-column=lightning_frequency --type=TEXT

It does add the column and populates the data but generates an error during 
the archival cycle. I guess it looking for integers and real type values.

Aug 16 22:00:22 raspberrypi weewx[24285] ERROR weewx.manager: Replace 
failed for database weewx.sdb: table archive_day_lightning_frequency has 9 
columns but 5 values were supplied
Aug 16 22:00:22 raspberrypi weewx[24285] INFO weewx.manager: Added record 
2021-08-16 22:00:00 EDT (1629165600) to database 'weewx.sdb'
Aug 16 22:00:22 raspberrypi weewx[24285] ERROR weewx.manager: Replace 
failed for database weewx.sdb: table archive_day_lightning_frequency has 9 
columns but 5 values were supplied

Next I will try adding using the schema.

Rich
On Monday, August 16, 2021 at 6:55:55 PM UTC-4 tke...@gmail.com wrote:

> Can't say that I've tried that, but I don't see why it wouldn't work. It's 
> certainly simpler.
>
> Let me know how it goes.
>
> On Mon, Aug 16, 2021 at 9:11 AM storm...@gmail.com  
> wrote:
>
>> Thanks Tom.
>>
>> I have another question before proceeding.  Do I need to physically 
>> update the schema to include column and type or could I just use the 
>> following command:  
>>
>> wee_database --add-column=comments --type=TEXT
>>
>> Rich
>>
>> On Monday, August 16, 2021 at 8:29:16 AM UTC-4 tke...@gmail.com wrote:
>>
>>> Good question. Yes, it is possible to store text. 
>>>
>>> 1. Assuming you're using sqlite, make sure you read their documentation 
>>> on data types: https://sqlite.org/datatype3.html
>>>
>>> 2. Create a new schema accordingly. For example,
>>>
>>> table = [('dateTime', 'INTEGER NOT NULL UNIQUE PRIMARY KEY'),
>>>  ('usUnits', 'INTEGER NOT NULL'),
>>>  ('interval', 'INTEGER NOT NULL'),
>>>  ('outTemp',  'REAL'),
>>>  ('comments', 'TEXT')
>>>  ]
>>>
>>>
>>> day_summaries = [('outTemp', 'scalar'), ('comments', 'scalar')]
>>>
>>> schema = {
>>> 'table': table,
>>> 'day_summaries' : day_summaries
>>> }
>>>
>>>
>>> This is just an example. Your schema is likely to have many more types 
>>> than this.
>>>
>>> 3. See the directions in the Customizing Guide for how to specify that 
>>> your new schema be used. *Picking a starting schema 
>>> <http://www.weewx.com/docs/customizing.htm#Picking_a_starting_schema>*.
>>>
>>> 4. Read the developer's notes on Accumulators 
>>> <https://github.com/weewx/weewx/wiki/Accumulators>. In your weewx.conf 
>>> file, specify that your text type should be accumulated using the "
>>> firstlast" accumulator. This will prevent it from trying to find the 
>>> average, etc, of a string.
>>>
>>> [Accumulator]
>>> [[comments]]
>>> accumulator = firstlast
>>>
>>>
>>> That's it. If your new type appears in the archive record, then it will 
>>> be included in the database. 
>>>
>>> Tags like
>>>
>>> Details: $current.comments, last recorded at $day.comments.last
>>>
>>>
>>> should also work.
>>>
>>>
>>> On Sun, Aug 15, 2021 at 8:43 PM storm...@gmail.com  
>>> wrote:
>>>
>>>> In the Weewx DB, the column data types are  primary Real or Integer but 
>>>> is it possible to store data as Text? 
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "weewx-user" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to weewx-user+...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/faf66dd7-7e4a-45fa-9737-6f0094024c88n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/faf66dd7-7e4a-45fa-9737-6f0094024c88n%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/c4c792b5-c214-446e-9e4b-6d76dbc14aabn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/c4c792b5-c214-446e-9e4b-6d76dbc14aabn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

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

Re: [weewx-user] Weewx DB Column Data Types

[storm...@gmail.com]

Thanks Tom.

I have another question before proceeding.  Do I need to physically update 
the schema to include column and type or could I just use the following 
command:  

wee_database --add-column=comments --type=TEXT

Rich

On Monday, August 16, 2021 at 8:29:16 AM UTC-4 tke...@gmail.com wrote:

> Good question. Yes, it is possible to store text. 
>
> 1. Assuming you're using sqlite, make sure you read their documentation on 
> data types: https://sqlite.org/datatype3.html
>
> 2. Create a new schema accordingly. For example,
>
> table = [('dateTime', 'INTEGER NOT NULL UNIQUE PRIMARY KEY'),
>  ('usUnits', 'INTEGER NOT NULL'),
>  ('interval', 'INTEGER NOT NULL'),
>  ('outTemp',  'REAL'),
>  ('comments', 'TEXT')
>  ]
>
>
> day_summaries = [('outTemp', 'scalar'), ('comments', 'scalar')]
>
> schema = {
> 'table': table,
> 'day_summaries' : day_summaries
> }
>
>
> This is just an example. Your schema is likely to have many more types 
> than this.
>
> 3. See the directions in the Customizing Guide for how to specify that 
> your new schema be used. *Picking a starting schema 
> <http://www.weewx.com/docs/customizing.htm#Picking_a_starting_schema>*.
>
> 4. Read the developer's notes on Accumulators 
> <https://github.com/weewx/weewx/wiki/Accumulators>. In your weewx.conf 
> file, specify that your text type should be accumulated using the "
> firstlast" accumulator. This will prevent it from trying to find the 
> average, etc, of a string.
>
> [Accumulator]
> [[comments]]
> accumulator = firstlast
>
>
> That's it. If your new type appears in the archive record, then it will be 
> included in the database. 
>
> Tags like
>
> Details: $current.comments, last recorded at $day.comments.last
>
>
> should also work.
>
>
> On Sun, Aug 15, 2021 at 8:43 PM storm...@gmail.com  
> wrote:
>
>> In the Weewx DB, the column data types are  primary Real or Integer but 
>> is it possible to store data as Text? 
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/faf66dd7-7e4a-45fa-9737-6f0094024c88n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/faf66dd7-7e4a-45fa-9737-6f0094024c88n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

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

[weewx-user] Weewx DB Column Data Types

[storm...@gmail.com]

In the Weewx DB, the column data types are  primary Real or Integer but is 
it possible to store data as Text?

-- 
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/faf66dd7-7e4a-45fa-9737-6f0094024c88n%40googlegroups.com.

[weewx-user] Re: MQTTSubscribe and Array of String data

[storm...@gmail.com]

Yes, it is possible  to process array of string data as shown below.

Aug 12 21:27:40 raspberrypi weewx[18618] DEBUG user.MQTTSubscribe: 
(Service) MessageCallbackProvider data-> incoming topic: Alerts/NWS/, QOS: 
0, retain: 0, payload: b'{"alert_NWS0":"Current Watches, Warnings and 
Advisories for Allegheny (PAC003) Pennsylvania Issued by the National 
Weather Service","alert_NWS1":"Severe Thunderstorm Warning issued August 12 
at 8:39PM EDT until August 12 at 9:30PM EDT by NWS","alert_NWS2":"Flash 
Flood Warning issued August 12 at 8:36PM EDT until August 12 at 11:45PM EDT 
by NWS","alert_NWS3":"Flash Flood Warning issued August 12 at 8:32PM EDT 
until August 12 at 10:30PM EDT by NWS","alert_NWS4":"Severe Thunderstorm 
Watch issued August 12 at 7:48PM EDT until August 12 at 10:00PM EDT by 
NWS"}'

I made the assumption that a county will not have more than 9 alerts at one 
time. 

 [[topics]]
.
.
.
 [[[Alerts/NWS/]]]

alert_NWS0
   name = alert_0
   conversion_type = None
   
alert_NWS1
   name = alert_1
   conversion_type = None
   
alert_NWS2
   name = alert_2
   conversion_type = None
   
alert_NWS3
   name = alert_3
   conversion_type = None
   
alert_NWS4
   name = alert_4
   conversion_type = None
   
alert_NWS5
   name = alert_5
   conversion_type = None 
   
alert_NWS6
   name = alert_6
   conversion_type = None
   
alert_NWS7
   name = alert_7
   conversion_type = None
   
alert_NWS8
   name = alert_8
   conversion_type = None
   
alert_NWS9
   name = alert_9
   conversion_type = None
   
alert_NWS10 
   name = alert_10
   conversion_type = None 

[Accumulator]

 [[alert_0]]
accumulator = firstlast
extractor = last

[[alert_1]]
accumulator = firstlast
extractor = last

[[alert_2]]
accumulator = firstlast
extractor = last

[[alert_3]]
accumulator = firstlast
extractor = last

[[alert_4]]
accumulator = firstlast
extractor = last

[[alert_5]]
accumulator = firstlast
extractor = last 

[[alert_6]]
accumulator = firstlast
extractor = last

[[alert_7]]
accumulator = firstlast
extractor = last

[[alert_8]]
accumulator = firstlast
extractor = last

[[alert_9]]
accumulator = firstlast
extractor = last

[[alert_10]]
    accumulator = firstlast
extractor = last

On Friday, August 13, 2021 at 10:57:41 PM UTC-4 storm...@gmail.com wrote:

> Rich...Thanks for the effort you put into this and for the info.  Yes, the 
> data is in json format and I do have the  conversion_type = None.  I need 
> to read up on the accumulators and the message formats.
>
> On Friday, August 13, 2021 at 10:12:32 PM UTC-4 bell...@gmail.com wrote:
>
>> The short answer is no. 
>> But that data looks a lot like json to me … Because you are dealing with 
>> text, you will want to set conversion_type = None. See, 
>> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring#conversion_type
>>  You 
>> will also do some WeeWx configuration related to accumulators. See, 
>> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring#conversion_type
>>
>> If it is not json, I suppose you could read it as a ‘individual’ payload 
>> and have a service post process it.
>>
>> The final option is to write a custom parser. This is still experimental 
>> and would probably be more work than a standalone service to post process. 
>> A bit of information is here, 
>> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Handling-different-MQTT-message-formats
>>
>> rich
>>
>> On Thursday, 12 August 2021 at 22:04:43 UTC-4 storm...@gmail.com wrote:
>>
>>> Is it possible for MQTTSubscribe to process array of string data as 
>>> shown below.
>>>
>>> Aug 12 21:27:40 raspberrypi weewx[18618] DEBUG user.MQTTSubscribe: 
>>> (Service) MessageCallbackProvider data-> incoming topic: Alerts/NWS/, QOS: 
>>> 0, retain: 0, payload: b'{"alert_NWS0":"Curre

[weewx-user] Re: MQTTSubscribe and Array of String data

[storm...@gmail.com]

Rich...Thanks for the effort you put into this and for the info.  Yes, the 
data is in json format and I do have the  conversion_type = None.  I need 
to read up on the accumulators and the message formats.

On Friday, August 13, 2021 at 10:12:32 PM UTC-4 bell...@gmail.com wrote:

> The short answer is no. 
> But that data looks a lot like json to me … Because you are dealing with 
> text, you will want to set conversion_type = None. See, 
> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring#conversion_type
>  You 
> will also do some WeeWx configuration related to accumulators. See, 
> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring#conversion_type
>
> If it is not json, I suppose you could read it as a ‘individual’ payload 
> and have a service post process it.
>
> The final option is to write a custom parser. This is still experimental 
> and would probably be more work than a standalone service to post process. 
> A bit of information is here, 
> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Handling-different-MQTT-message-formats
>
> rich
>
> On Thursday, 12 August 2021 at 22:04:43 UTC-4 storm...@gmail.com wrote:
>
>> Is it possible for MQTTSubscribe to process array of string data as shown 
>> below.
>>
>> Aug 12 21:27:40 raspberrypi weewx[18618] DEBUG user.MQTTSubscribe: 
>> (Service) MessageCallbackProvider data-> incoming topic: Alerts/NWS/, QOS: 
>> 0, retain: 0, payload: b'{"alert_NWS0":"Current Watches, Warnings and 
>> Advisories for Allegheny (PAC003) Pennsylvania Issued by the National 
>> Weather Service","alert_NWS1":"Severe Thunderstorm Warning issued August 12 
>> at 8:39PM EDT until August 12 at 9:30PM EDT by NWS","alert_NWS2":"Flash 
>> Flood Warning issued August 12 at 8:36PM EDT until August 12 at 11:45PM EDT 
>> by NWS","alert_NWS3":"Flash Flood Warning issued August 12 at 8:32PM EDT 
>> until August 12 at 10:30PM EDT by NWS","alert_NWS4":"Severe Thunderstorm 
>> Watch issued August 12 at 7:48PM EDT until August 12 at 10:00PM EDT by 
>> NWS"}'
>>
>>
>>

-- 
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/0f69ab57-c4b9-4db9-9fd5-bfa737c5be4fn%40googlegroups.com.

[weewx-user] Re: Set up Belchertown for using Dark Sky for the time being for forecast

[storm...@gmail.com]

Check this link out. 

https://github.com/poblabs/weewx-belchertown/issues/704


On Friday, August 13, 2021 at 7:42:20 PM UTC-4 daleea...@gmail.com wrote:

> Since I'm just getting my station rebuilt and set up, I cannot get an 
> aeris key or password yet since I"m still running the station emulator and 
> getting simulated data.  Of course with DS on the way out, I will feed 
> pwsweather and be entitled to get a key, but so far, I'm not online.
>
> I'd like to proceed with getting Belcherweather set up.  Pat has 
> apparently been busy and so far hasn't answered a question I posted on his 
> site.
>
> In the configuration skin for Belcher, there is a section that says 
> 'aeris' is the forecast source, but says Dark Sky for those with a still 
> functioning API can be used, but there is no example that I can find as to 
> what to put into those " " for DarkSky.
>
> Has anyone set this up for DS and know what the entry should be?
> Dale
>
>

-- 
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/aa9d12d0-aeae-4806-bfe8-130ac5f831e8n%40googlegroups.com.

[weewx-user] MQTTSubscribe and Array of String data

[storm...@gmail.com]

Is it possible for MQTTSubscribe to process array of string data as shown 
below.

Aug 12 21:27:40 raspberrypi weewx[18618] DEBUG user.MQTTSubscribe: 
(Service) MessageCallbackProvider data-> incoming topic: Alerts/NWS/, QOS: 
0, retain: 0, payload: b'{"alert_NWS0":"Current Watches, Warnings and 
Advisories for Allegheny (PAC003) Pennsylvania Issued by the National 
Weather Service","alert_NWS1":"Severe Thunderstorm Warning issued August 12 
at 8:39PM EDT until August 12 at 9:30PM EDT by NWS","alert_NWS2":"Flash 
Flood Warning issued August 12 at 8:36PM EDT until August 12 at 11:45PM EDT 
by NWS","alert_NWS3":"Flash Flood Warning issued August 12 at 8:32PM EDT 
until August 12 at 10:30PM EDT by NWS","alert_NWS4":"Severe Thunderstorm 
Watch issued August 12 at 7:48PM EDT until August 12 at 10:00PM EDT by 
NWS"}'


-- 
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/1aefe26e-8c20-4654-a557-0f6e74c13ff0n%40googlegroups.com.

[weewx-user] Re: Trouble setting up Grove BME280 on weewx 4.5.1 RPi

[storm...@gmail.com]

Give the following a try

https://gitlab.com/wjcarpenter/bme280wx

I ran this without any issues

On Sunday, July 18, 2021 at 5:44:06 PM UTC-4 Elie R wrote:

> Thanks, I did initially follow those instructions, this is the error I 
> received  running python3 -c "import bme280":
>
> pi@raspberrypi:~ $ python3 -c "import bme280"
>
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/home/pi/bme280.py", line 162
> print "Chip ID :", chip_id
> ^
> SyntaxError: Missing parentheses in call to 'print'. Did you mean 
> print("Chip ID :", chip_id)?
>
> def main():
>
>   (chip_id, chip_version) = readBME280ID()
>   print "Chip ID :", chip_id
>   print "Version :", chip_version
>
>   temperature,pressure,humidity = readBME280All()
>
>   print "Temperature : ", temperature, "C"
>   print "Pressure : ", pressure, "hPa"
>   print "Humidity : ", humidity, "%"
>
> Added the missing parentheses, tried running it again but still received a 
> bunch of different errors, so I decided to uninstall all instances of 
> bme280 and RPi.bme280 (python 2 and 3) and start over using pip3 install. 
>
> I can now run bme280 sample script directly from within its own directory 
> under python3 :
>
>  pi@raspberrypi:~/.local/lib/python3.7/site-packages/bme280 $ python 
> sample.py
> 33fd4292-66f4-4994-8b69-523d13a7c3a7
> 2021-07-18 17:12:20.905437
> 21.5680572186
> 1013.10937762
> 58.1974230463
> compensated_reading(id=33fd4292-66f4-4994-8b69-523d13a7c3a7, 
> timestamp=2021-07-18 17:12:20.905437, temp=21.568 °C, pressure=1013.11 hPa, 
> humidity=58.20 % rH)
>
> but it fails if I try to run it from anywhere else, and if I try running 
> weewxd, I get:
>
> Traceback (most recent call last):
>   File "/usr/share/weewx/weewxd", line 264, in 
> main()
>   File "/usr/share/weewx/weewxd", line 151, in main
> engine = weewx.engine.StdEngine(config_dict)
>   File "/usr/share/weewx/weewx/engine.py", line 93, in __init__
> self.loadServices(config_dict)
>   File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices
> obj = weeutil.weeutil.get_object(svc)(self, config_dict)
>   File "/usr/share/weewx/weeutil/weeutil.py", line 1119, in get_object
> mod = __import__(module)
>
> or trying to run the example script:
>
> Traceback (most recent call last): File "sensor.py", line 8, in  
> calibration_params = bme280.load_calibration_params(bus, address) 
> AttributeError: 'module' object has no attribute 'load_calibration_params' 
>
> Under python3  I'm seeing:
> pi@raspberrypi:~/.local/lib/python3.7/site-packages/bme280 $ ls
> const.py  __init__.py  __pycache__  reader.py  sample.py
>
> but under python2 I'm getting (no sample.py installed with this package)
> pi@raspberrypi:~/.local/lib/python2.7/site-packages/bme280 $ ls
> const.py  const.pyc  __init__.py  __init__.pyc  reader.py  reader.pyc
>
> I have no problem starting everything over from scratch, but not sure if 
> I'm missing something obvious with bme280 install? weewx, rtl-sdr, 
> Belchertown, i2c, etc   all went quite smoothly, but bme280 isn't being as 
> nice.  
>
> Cheers
>
>
>
>
>
> On Saturday, 17 July 2021 at 21:17:45 UTC-4 vince wrote:
>
>> On Saturday, July 17, 2021 at 1:38:02 PM UTC-7 Elie R wrote:
>>
>>>   File "/usr/share/weewx/user/bme280wx.py", line 6, in 
>>> import bme280
>>> ModuleNotFoundError: No module named 'bme280'
>>>
>>>
>> This one seems like you didn't install the bme280 module for the version 
>> of python (2 or 3) that weewx is using.  A quick search points to 
>> https://pypi.org/project/RPi.bme280/  for installation instructions.
>>
>> You might try a couple simple tests.
>>
>>- python -c "import bme280"
>>- python3 -c "import bme280"
>>
>> You should get an error if that version of python does not have the 
>> module installed.
>>
>>
>>
>>

-- 
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/0c44f374-18f5-4127-a128-f2a4ed8c1ad6n%40googlegroups.com.

[weewx-user] WeeWX-MQTTSubscribe and Message

[storm...@gmail.com]

Would like to subscribe to individual messages and was wondering if that is 
possible. I have no issues subscribing to topics.

-- 
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/b294b4d5-c6d2-4f93-b238-c14364a556a9n%40googlegroups.com.

[weewx-user] Re: Config settings for Acurite 1536

[storm...@gmail.com]

In the weewx.conf file, do you have the following:

[Station]

# Description of the station location
location = Multiple SDR/Ext Sensor Test w Console

# Latitude in decimal degrees. Negative for southern hemisphere
latitude = XX.
# Longitude in decimal degrees. Negative for western hemisphere.
longitude = -XX.

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 1703, foot# Choose 'foot' or 'meter' for unit

# Set to type of station hardware. There must be a corresponding stanza
# in this file with a 'driver' parameter indicating the driver to be 
used.
station_type = AcuRite

# If you have a website, you may specify an URL
#station_url = http://www.example.com

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 6

##

[AcuRite]
# This section is for AcuRite weather stations.

# The station model, e.g., 'AcuRite 01025' or 'AcuRite 02032C'
model = AcuRite 01035

# The driver to use:
driver = weewx.drivers.acurite

##

On Tuesday, July 13, 2021 at 8:50:08 AM UTC-4 kjf...@gmail.com wrote:

> Hello,
> I'm new to weewx and am trying to setup a basic weewx instance on a 
> *Raspberry 
> Pi 4 to connect to my Costco Acurite 1536.* At this point I'd just like 
> to know how others have made this work.  I've already searched this group 
> and find plenty of references from people who have the 1536 working but I 
> can't seem to find anything basic such as which Acurite hardware to 
> specify.  *Since 1536 is not listed in the hardware list I am hoping it's 
> just as simple as specifying one of the others and it will just work.*  
> When I entered 01536 during the setup portion of the install it seems to 
> start and then die so no need for me to post a portion of the system log.  
> If it matters I did the standard Pi install using apt-get and it's 
> installed in the standard /etc... path.  Thanks much for anyone who can 
> help.
>

-- 
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/be47e3b9-cef1-4a24-8d25-d64924e9ecd3n%40googlegroups.com.

[weewx-user] Re: Starter Station - Noob Question

[storm...@gmail.com]

Griffi - I have one.  It runs with in a degree or two of my Davis.

On Thursday, June 24, 2021 at 3:20:04 PM UTC-4 griffi...@gmail.com wrote:

> Vince -
>
> Would this pretty much be the same as what you are proposing currently?
> Amazon.com: ECOWITT HP3501 TFT Wi-Fi Weather Station with Solar Powered 
> Wireless Anemometer, UV & Light Sensor, Self-Emptying Rain Collector, Color 
> Graph Display, Weather APP and PC Software: Industrial & Scientific 
> 
>
> If so, I may honestly just break the bank a little more just to jump on it.
>
> On Thursday, June 24, 2021 at 2:10:27 PM UTC-5 vince wrote:
>
>> On Thursday, June 24, 2021 at 12:02:18 PM UTC-7 griffi...@gmail.com 
>> wrote:
>>
>>> As far as for the budget Vince, I know.  I would love to be able to 
>>> spend more but with my wife and health issues, that kind of limits my 
>>> budget and I want to get something going at least as a small quick project 
>>> for my son and I since he has been looking at all sorts of stuff like this 
>>> lately.
>>>
>>
>> That makes the Ecowitt piecemeal approach perhaps more worth thinking 
>> about.
>>
>> Go for inside+outside temp+humidity for starters which would require the 
>> gateway and the outside sensor only.  That would be under $50 plus the pi 
>> you already have  Add rain+wind as budget/inclination permit.
>>
>> I might add the little inside/outside temp/hum sensors are a steal for 
>> $12.99 considering they have a nice little display on them.  They'd work 
>> fine standalone even without the gateway, although gateway and (free) phone 
>> app let you apply a little tuning if you find they read a bit high/low 
>> versus some reference you believe is accurate.
>>  
>>
>

-- 
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/f81e5935-4928-431f-be11-9e523bd261f8n%40googlegroups.com.

[weewx-user] Re: Starter Station - Noob Question

[storm...@gmail.com]

Here is an AcuRite station:

https://www.amazon.com/AcuRite-01036M-Wireless-Weather-Programmable/dp/B00FWSP3UC/ref=sr_1_2_sspa?dchild=1=acurite+weather+station=1624559281=8-2-spons=1=ZW5jcnlwdGVkUXVhbGlmaWVyPUExQVBXTlI0T1RENVRDJmVuY3J5cHRlZElkPUEwMzA0NDM5MldOVjhPTEJZRU41MyZlbmNyeXB0ZWRBZElkPUEwNzIxNzgxM0FYRVU0TjMyOEZSOCZ3aWRnZXROYW1lPXNwX2F0ZiZhY3Rpb249Y2xpY2tSZWRpcmVjdCZkb05vdExvZ0NsaWNrPXRydWU=

I see it is on sale for $127.00  You can connect the console directly 
to the RPI.
On Thursday, June 24, 2021 at 12:15:22 PM UTC-4 griffi...@gmail.com wrote:

> That is a fair question.  I guess I should have provided more of a 
> detailed answer instead of just a generalized "Hey, I want to do this" 
> without proper details.
>
> I would like to spend between $100 - $150 and if I were to need to stretch 
> the budget, probably another $20 to $30 *CURRENTLY* at this time.  If I 
> need to wait, I may be able to up the budget a little more.
>
> As far as Data and what means the most to me:
> * Temp
> * Wing
> * Rain
> *Those are the main three that I would consider important.  I do not 
> require a console or indoor info*.
>
> As far as for Solar and Lightning is concerned, that would be the "I want" 
> but not an "I do not need" feature and I am sure that is more part of the 
> higher priced ones.  As far as for internet connection, I am probably going 
> to get it hooked into weather underground if that is a separate function 
> but honestly it does not bother me if there is a separate connection as I 
> am going to vLAN it to the IoT group on my network so it really isn't going 
> to give me any issues on internal equipment, etc.
>
> Vince, I hope this helps to clear up quite a bit of things.  If you need 
> anymore questions answered that would help out a bit more, I really do not 
> mind answering them and again I am sorry for the brain-fart moment I gave 
> you and probably a lot of other guys / gals on the group posting.
>
> On Thursday, June 24, 2021 at 10:52:05 AM UTC-5 vince wrote:
>
>> On Thursday, June 24, 2021 at 7:36:05 AM UTC-7 griffi...@gmail.com wrote:
>>
>>> So, any weather equipment you believe is the best bang for the buck when 
>>> it comes to a low budget at the time being?
>>>
>>
>> That's impossible to even speculate on without more information.
>>
>>- how much 'can' you spend ? 
>>- what's your target price ?
>>   - if you need to stretch that, how high can you go ?
>>- what data means most to you ?
>>   - temperature ?
>>   - humidity ?
>>   - wind ?
>>   - rain ?
>>   - solar ?
>>   - lightning ?
>>   - do you need a console on it ?
>>   - do you need indoor temperature/humidity readings ?
>>- do you care if the gear requires an internet connection to a vendor 
>>in order to function ?
>>
>>
>>

-- 
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/29550f8f-68fd-4d45-aa0e-248864d3fe31n%40googlegroups.com.

Re: [weewx-user] Re: no connection to the web server

[storm...@gmail.com]

Check to see if the  weewx.conf  is also in  /etc/apache2/conf-available 
folder.

On Saturday, May 29, 2021 at 4:25:05 AM UTC-4 eckha...@googlemail.com wrote:

> i reinstalled all of them ... then i checked the folders on the spot and 
> checked their contents. without success! I give up. 
>
> vince schrieb am Samstag, 29. Mai 2021 um 03:45:52 UTC+2:
>
>>
>> See if the FAQ 
>> <https://github.com/weewx/weewx/wiki/faq-web-pages-not-appearing> helps 
>> any.
>>
>> You've established weewx is generating files.  You haven't pinned down 
>> whether weewx+apache are in agreement on where the web pages are, nor if 
>> apache is running at all.
>>
>>
>> On Friday, May 28, 2021 at 6:22:18 PM UTC-7 storm...@gmail.com wrote:
>>
>>> Do you have the file "weewx.conf" in  "/etc/apache2/conf-enabled/" 
>>> folder?
>>>
>>>
>>> Alias /weewx /home/weewx/public_html
>>> 
>>> Options FollowSymlinks
>>> AllowOverride None
>>> Require all granted
>>> 
>>>
>>> If not, add the file and restart apache2
>>>
>>> On Friday, May 28, 2021 at 9:08:58 PM UTC-4 tke...@gmail.com wrote:
>>>
>>>> Everything looks totally normal to me. Did you browse 
>>>> to file:///home/weewx/public_html/?
>>>>
>>>> Or, did you tell your webserver to look there?
>>>>
>>>> On Fri, May 28, 2021 at 5:40 PM 'eckha...@googlemail.com' via 
>>>> weewx-user  wrote:
>>>>
>>>>>
>>>>> [image: index.PNG]
>>>>>
>>>>>
>>>>> the funny thing is there is also data in the file but i can't call it 
>>>>> up 
>>>>>
>>>>>
>>>>> eckha...@googlemail.com schrieb am Samstag, 29. Mai 2021 um 02:34:30 
>>>>> UTC+2:
>>>>>
>>>>>> [image: Unbenannt.PNG]
>>>>>>
>>>>>> eckha...@googlemail.com schrieb am Samstag, 29. Mai 2021 um 02:33:35 
>>>>>> UTC+2:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> [image: weewx.PNG]
>>>>>>> tke...@gmail.com schrieb am Samstag, 29. Mai 2021 um 02:15:55 UTC+2:
>>>>>>>
>>>>>>>> Weewx seems to be running normally. 
>>>>>>>>
>>>>>>>> Is there a question in there? Did you look in 
>>>>>>>> /home/weewx/public_html?
>>>>>>>>
>>>>>>>> On Fri, May 28, 2021 at 5:00 PM 'eckha...@googlemail.com' via 
>>>>>>>> weewx-user  wrote:
>>>>>>>>
>>>>>>>>> addendum 
>>>>>>>>>
>>>>>>>>> May 29 00:56:02 raspberrypi weewx[471] INFO weewx.manager: Added 
>>>>>>>>> record 2021-05-29 00:55:00 BST (1622246100) to database 'weewx.sdb'
>>>>>>>>> May 29 00:56:02 raspberrypi weewx[471] INFO weewx.manager: Added 
>>>>>>>>> record 2021-05-29 00:55:00 BST (1622246100) to daily summary in 
>>>>>>>>> 'weewx.sdb'
>>>>>>>>> May 29 00:56:02 raspberrypi weewx[471] DEBUG weewx.reportengine: 
>>>>>>>>> Running reports for latest time in the database.
>>>>>>>>> May 29 00:56:02 raspberrypi weewx[471] DEBUG weewx.reportengine: 
>>>>>>>>> Running report 'SeasonsReport'
>>>>>>>>> May 29 00:56:02 raspberrypi weewx[471] DEBUG weewx.reportengine: 
>>>>>>>>> Found configuration file /home/weewx/skins/Seasons/skin.conf for 
>>>>>>>>> report 
>>>>>>>>> 'SeasonsReport'
>>>>>>>>> May 29 00:56:02 raspberrypi weewx[471] DEBUG 
>>>>>>>>> weewx.cheetahgenerator: Using search list 
>>>>>>>>> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
>>>>>>>>> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
>>>>>>>>> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
>>>>>>>>> 'weewx.cheetahgenerator.JSONHelpers']
>>>>>>>>> May 29 00:56:02 raspberrypi weewx[471] DEBUG weewx.manager: Daily 
>>>>>>>>> summary version is 4.0
>>>>>>>>> May 29 00:56:04 raspberr

Re: [weewx-user] Re: no connection to the web server

[storm...@gmail.com]

Do you have the file "weewx.conf" in  "/etc/apache2/conf-enabled/" folder?


Alias /weewx /home/weewx/public_html

Options FollowSymlinks
AllowOverride None
Require all granted


If not, add the file and restart apache2

On Friday, May 28, 2021 at 9:08:58 PM UTC-4 tke...@gmail.com wrote:

> Everything looks totally normal to me. Did you browse 
> to file:///home/weewx/public_html/?
>
> Or, did you tell your webserver to look there?
>
> On Fri, May 28, 2021 at 5:40 PM 'eckha...@googlemail.com' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>>
>> [image: index.PNG]
>>
>>
>> the funny thing is there is also data in the file but i can't call it up 
>>
>>
>> eckha...@googlemail.com schrieb am Samstag, 29. Mai 2021 um 02:34:30 
>> UTC+2:
>>
>>> [image: Unbenannt.PNG]
>>>
>>> eckha...@googlemail.com schrieb am Samstag, 29. Mai 2021 um 02:33:35 
>>> UTC+2:
>>>


 [image: weewx.PNG]
 tke...@gmail.com schrieb am Samstag, 29. Mai 2021 um 02:15:55 UTC+2:

> Weewx seems to be running normally. 
>
> Is there a question in there? Did you look in /home/weewx/public_html?
>
> On Fri, May 28, 2021 at 5:00 PM 'eckha...@googlemail.com' via 
> weewx-user  wrote:
>
>> addendum 
>>
>> May 29 00:56:02 raspberrypi weewx[471] INFO weewx.manager: Added 
>> record 2021-05-29 00:55:00 BST (1622246100) to database 'weewx.sdb'
>> May 29 00:56:02 raspberrypi weewx[471] INFO weewx.manager: Added 
>> record 2021-05-29 00:55:00 BST (1622246100) to daily summary in 
>> 'weewx.sdb'
>> May 29 00:56:02 raspberrypi weewx[471] DEBUG weewx.reportengine: 
>> Running reports for latest time in the database.
>> May 29 00:56:02 raspberrypi weewx[471] DEBUG weewx.reportengine: 
>> Running report 'SeasonsReport'
>> May 29 00:56:02 raspberrypi weewx[471] DEBUG weewx.reportengine: 
>> Found configuration file /home/weewx/skins/Seasons/skin.conf for report 
>> 'SeasonsReport'
>> May 29 00:56:02 raspberrypi weewx[471] DEBUG weewx.cheetahgenerator: 
>> Using search list ['weewx.cheetahgenerator.Almanac', 
>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
>> 'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.JSONHelpers']
>> May 29 00:56:02 raspberrypi weewx[471] DEBUG weewx.manager: Daily 
>> summary version is 4.0
>> May 29 00:56:04 raspberrypi weewx[471] INFO weewx.cheetahgenerator: 
>> Generated 8 files for report SeasonsReport in 2.03 seconds
>> May 29 00:56:04 raspberrypi weewx[471] DEBUG weewx.manager: Daily 
>> summary version is 4.0
>> May 29 00:56:05 raspberrypi weewx[471] INFO weewx.imagegenerator: 
>> Generated 15 images for report SeasonsReport in 0.58 seconds
>> May 29 00:56:05 raspberrypi weewx[471] INFO weewx.reportengine: 
>> Copied 5 files to /home/weewx/public_html
>> May 29 00:56:05 raspberrypi weewx[471] DEBUG weewx.reportengine: 
>> Report 'SmartphoneReport' not enabled. Skipping.
>> May 29 00:56:05 raspberrypi weewx[471] DEBUG weewx.reportengine: 
>> Report 'MobileReport' not enabled. Skipping.
>> May 29 00:56:05 raspberrypi weewx[471] DEBUG weewx.reportengine: 
>> Report 'StandardReport' not enabled. Skipping.
>> May 29 00:56:05 raspberrypi weewx[471] DEBUG weewx.reportengine: 
>> Report 'FTP' not enabled. Skipping.
>> May 29 00:56:05 raspberrypi weewx[471] DEBUG weewx.reportengine: 
>> Report 'RSYNC' not enabled. Skipping.
>> May 29 00:56:50 raspberrypi dhcpcd[601]: eth0: Router Advertisement 
>> from fe80::cece:1eff:fe3a:d164
>>
>> eckha...@googlemail.com schrieb am Samstag, 29. Mai 2021 um 01:59:44 
>> UTC+2:
>>
>>>
>>> Hey 
>>>
>>> Hardware:
>>> Froggit WS1050
>>> Pi 4 
>>> Rasbian os 
>>> Weewx 4.5.1
>>> LOG:
>>> pi@raspberrypi:~ $ tail -f /var/log/syslog
>>> May 29 00:50:23 raspberrypi systemd[727]: Listening on GnuPG network 
>>> certificate 
>>>
>>> management daemon.
>>> May 29 00:50:23 raspberrypi systemd[727]: Listening on GnuPG 
>>> cryptographic 
>>> agent   
>>>  
>>> and passphrase cache (access for web browsers).
>>> May 29 00:50:23 raspberrypi systemd[727]: Reached target Sockets.
>>> May 29 00:50:23 raspberrypi systemd[727]: Reached target Basic 
>>> System.
>>> May 29 00:50:23 raspberrypi systemd[727]: Reached target Default.
>>> May 29 00:50:23 raspberrypi systemd[727]: Startup finished in 163ms.
>>> May 29 00:50:23 raspberrypi systemd[1]: Started User Manager for UID 
>>> 1000.
>>> May 29 00:50:23 raspberrypi systemd[1]: Started Session 1 of user pi.
>>> May 29 00:50:23 raspberrypi dhcpcd[601]: eth0: 
>>> 

[weewx-user] Re: adding graphs to Belchertown skin?

[storm...@gmail.com]

Once you are editing the  graphs.conf.example file, you can save the file 
as  graphs.conf.

On Friday, May 14, 2021 at 12:08:18 PM UTC-4 eric.k...@gmail.com wrote:

> I would like to enable (or add) a lightning graph to the Belchertown skin.
> I'm reading the Belchertown README and FAQ here:
> https://github.com/poblabs/weewx-belchertown
>
> It mentions editing a graphs.conf file.
> I am working on a default install of the Belchertown skin, I see a 
> graphs.conf.example file  in the skins/Belchertown directory but, there 
> isn't a graphs.conf file!
> How is Belchertown displaying any graphs at all, with no graphs.conf file??
>
> Eric
>

-- 
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/7924be0c-772b-474e-8514-9edb9dd6a92bn%40googlegroups.com.

[weewx-user] Re: Forecast in the Database

[storm...@gmail.com]

Is this what you are looking for : 

https://groups.google.com/g/weewx-user/c/pZnD5llxKzA/m/I2kiod2wBwAJ

or

https://github.com/hes19073/hesweewx/blob/master/bin/user/vanfortex.py

On Wednesday, April 21, 2021 at 12:47:41 PM UTC-4 blaise@gmail.com 
wrote:

>
> Hello,
>
> The Vantage Pro has a Forecast variable that I wanted to add in the 
> database. To my surprise, the location is there, with a "null" as values. 
> My question is simple, how to feed it?
>
> Well to you,
> Blaise

-- 
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/9c0707f0-ba56-429f-b1b3-c6eca8fe37a2n%40googlegroups.com.

[weewx-user] Re: trouble installing weewx-sdr driver - help requested

[storm...@gmail.com]

Try this but make sure you are using your path: 
pi@raspberrypi:/home/weewx/bin $ sudo ./wee_extension 
--install=/home/pi/Downloads/weewx-sdr.zip

On Monday, April 19, 2021 at 12:13:35 PM UTC-4 eric.k...@gmail.com wrote:

> I loaded weewx into a Ubuntu 20 vitrual machine I created just to run 
> weewx.
> I created a Linux user called weewx, so the /home/weewx directory exists.
> I installed the rtl-sdr and rtl-433 using apt-get (DEB packages).
> For weewx, I followed the instructions for the "Installation using setup.py
> " method, where you download the source, make and install it.
> see:  https://weewx.com/docs/setup.htm
> That process appeared to work ok - no errors shown during the process.
>
> I'm following the weewx-sdr driver install process and it's falling flat 
> in several places.
> Are the instructions incomplete, or out of date?
> Is there an incompatibility with python 3.8? (the current version)
> https://github.com/matthewwall/weewx-sdr
>
> *Installation *
>  1) download the driver wget -O weewx-sdr.zip 
> https://github.com/matthewwall/weewx-sdr/archive/master.zip 
> *WORKED*
>  2) install the driver sudo wee_extension --install weewx-sdr.zip 
>
> *FAILS with: *
>
> *weewx@Ubuntu20-WEEWX:~/Downloads$ sudo wee_extension --install 
> weewx-sdr.zipsudo: wee_extension: command not found*
> If I remove the sudo, the command runs, but bombs because of permission 
> errors!
>
>
>
>
>
> *FAILS WITH: weewx@Ubuntu20-WEEWX:~/Downloads$ wee_extension --install 
> weewx-sdr.zipRequest to install 'weewx-sdr.zip'Extracting from zip archive 
> weewx-sdr.zipTraceback (most recent call last):  File 
> "/home/weewx/bin/wee_extension", line 88, in *
>   
>
>
>
>
>
>
>
>
>
>
>
> *  main()  File "/home/weewx/bin/wee_extension", line 80, in main
> ext.install_extension(options.install)  File 
> "/home/weewx/bin/weecfg/extension.py", line 125, in install_extension
> self.install_from_dir(extension_dir)  File 
> "/home/weewx/bin/weecfg/extension.py", line 183, in install_from_dir
> shutil.copy(source_path, destination_path)  File 
> "/usr/lib/python3.8/shutil.py", line 415, in copycopyfile(src, dst, 
> follow_symlinks=follow_symlinks)  File "/usr/lib/python3.8/shutil.py", line 
> 261, in copyfilewith open(src, 'rb') as fsrc, open(dst, 'wb') as 
> fdst:PermissionError: [Errno 13] Permission denied: 
> '/home/weewx/bin/user/sdr.py'*
>
> *CAN'T GO ANY FARTHER.   HELP REQUESTED.*
> 3) configure the driver sudo wee_config --reconfigure --driver=user.sdr 
> --no-prompt 
> 4) run the driver directly to identify the packets you want to capture cd 
> /home/weewx sudo PYTHONPATH=bin python bin/user/sdr.py --cmd="rtl_433 -M 
> utc -F json" 
> 5) modify the [SDR] section of weewx.conf using a text editor - create a 
> [[sensor_map]] for the data you want to capture - possibly modify the 'cmd' 
> parameter 
> 6) start weewx sudo /etc/init.d/weewx start
>

-- 
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/1ed67a34-1d5a-4d28-ac9d-a9e422b3efc8n%40googlegroups.com.

[weewx-user] Re: Using Weewx with home-made weather station and RPi

[storm...@gmail.com]

Take a look 
here: https://groups.google.com/g/weewx-user/c/udZCCCJlNE8/m/LeR2Mp3iBQAJ 


On Sunday, March 14, 2021 at 11:08:24 AM UTC-4 johnm...@btinternet.com 
wrote:

> I have developed a simple Raspberry Pi based weather station using the 
> BME280 temperature, pressure, humidity sensor and a Davis anemometer and 
> wind vane.  I have written a short programme in Python3 which takes in the 
> raw sensor values, does some calculations, prints the current measurements 
> from each sensor and stores mean and max values of windspeed and average 
> values for wind direction as a record in a LibreOffice spreadsheet at 5 
> minute archive intervals.
>
> I now want to expand this to take advantage of the functionality of Weewx. 
>  I've read much of the guidance in the Weewx wiki, but am still not clear 
> on the best approach.  So, I'd be keen to hear from anyone who has already 
> done this.  In particular, my questions are:
>
> How much of the above functionality in my current python software would 
> Weewx replace?
> Is there a step-by-step guide available for writing a Weewx driver for a 
> home-made station?
>

-- 
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/004540de-362a-43d4-ba67-296fc6862155n%40googlegroups.com.

[weewx-user] Re: Raspberry pi with sensor (temperature/humidity) working?

[storm...@gmail.com]

Did you read the following:

https://groups.google.com/g/weewx-user/c/udZCCCJlNE8/m/LeR2Mp3iBQAJ

On Thursday, March 4, 2021 at 5:34:07 AM UTC-5 giulianodir...@gmail.com 
wrote:

> Hey
>
> I'm quite new to the field with the Raspberry Pi. Now to my question.. We 
> got a job at school to implement a scientific project with the help of a 
> Raspberry Pie. Since I am very interested in the weather and climatology, I 
> thought that I would build a climate logger/weather staion with the help of 
> a Raspberry Pie. Now before I buy the components, I wanted to let someone 
> look over them again. My idea is using sensors (air 
> pressure/temperature/humidity /CO2 content). 
> display. After a few hours of research I came across the program "Weewx". 
> Now my question is whether it would be possible to implement this project 
> using sensors that I connect to a Raspberry Pi. Since I also met suitable 
> hardware in the documentation on very expensive "finished" weather station 
> modules, I got a bit stupid.
>
> I would be pleased to receive an answer ^^
>
> Hardware:
> -Raspberry Pi Zero
>
> -Air pressure/humidity and temperature sensor  
>
> Would this work with the Weewx program? 
>

-- 
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/dec17274-ea72-40f7-9129-2598d7a9n%40googlegroups.com.

Re: [weewx-user] Re: Sky Cover data to pwsweather.com

[storm...@gmail.com]

Try this link: https://www.aerisweather.com/signup/pws

On Thursday, February 18, 2021 at 6:23:58 AM UTC-5 lang@googlemail.com 
wrote:

> I think, the crucial information we are looking for is hidden here: "You 
> can find more details here.  "
> I suppose there was a link which wasn't copied over with the text.
> Would you mind providing this link ?
>
> Thanks
> On 18.02.2021 11:41, bchap...@gmail.com wrote:
>
> You can find more details here.  
>
>

-- 
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/b6bd8cdc-0eb2-4017-baa3-2a982b18d337n%40googlegroups.com.

Re: [weewx-user] Logia 5in1 - how to get barometer reading (need something like Wunderfixer)

[storm...@gmail.com]

Yes it will.  Been running the bme280wx extension and weewx-rtldavis 
(SDR) without out any issues.

Rich

On Sunday, January 24, 2021 at 3:25:13 PM UTC-5 joewil...@gmail.com wrote:

> Thanks for the thoughts Storm and sbarthes!
>
> Im running an older RPI 3.I really like the idea using the BME280 
> sensor.   I can pick one of those up on Amazon for $15 CDN. :)
>
> I did find this weewx extension for the BME280 sensor… -> 
> https://gitlab.com/wjcarpenter/bme280wx
>
> "bme280wx is an extension to weewx weather station software 
> <https://weewx.com/>. It gives the ability to supplement existing station 
> readings with temperature, pressure, and humidity readings from a Bosch 
> BME280 integrated environmental sensor 
> <https://www.bosch-sensortec.com/bst/products/all_products/bme280>”
>
> Im guessing that the BME280 will happly co-exist with the SDR that I’m 
> using on the RPI.   Think Im going to try this out.
>
> Cheers,
> -Joe
>
>
>
>
> On Jan 24, 2021, at 11:16 AM, storm...@gmail.com  
> wrote:
>
> If you are running a RPI, you can use a BME280 Sensor.
>
> On Sunday, January 24, 2021 at 12:08:47 PM UTC-5 joewil...@gmail.com 
> wrote:
>
>> Hi All,
>>
>> I'm a newbie to weewx,  and I have been able to set up weewx to monitor 
>> my weather station using SDR.   All works great,  but I would like to also 
>> get the barometer reading from the console back into weewx.
>>
>> My color console doesn't have a way to expose the internal sensor data 
>> (no usb/serial port),  but the console has the ability to post data 
>> directly to Weather Underground,  which includes the barometric readings 
>> (which I have been doing for the last couple of weeks).   Im thinking these 
>> are my options at this point..
>>
>> 1) get a sensor that works at 915.000MHz. that sends the barometric 
>> reading,  and add it to my sensor map
>>
>> or
>>
>> 2) write a python script that logs into weather underground,  and grabs 
>> the barometric reading (that was sent by my console),  and stores it back 
>> into the SQLLite database...   Not sure if anyone has done or thought of 
>> this.
>>
>> Like to do 1) if I can get a cheap sensor,  but I can do 2)
>>
>> Thoughts?
>> -Joe
>>
>
> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/Ad7S_WmBXTs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/55ec0c25-1707-43ee-9205-6350031c1744n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/55ec0c25-1707-43ee-9205-6350031c1744n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>
>

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

Re: [weewx-user] Davis VP2, SDR, BMP280

[storm...@gmail.com]

Take a look at this driver: https://gitlab.com/wjcarpenter/bme280wx.  It 
might work with the BMP280.

On Sunday, January 24, 2021 at 3:54:42 PM UTC-5 gary@gmail.com wrote:

> I'll take a look at editing in the 280. Since it is a Davis, we have to 
> use rtldavis, not the sdr.py driver. In the end, the SDR method gives the 
> basic data that comes from the ISS. I may decide if I want to keep the 
> WiFiLogger or the WLL and give the other to my friend. Either are easier in 
> WeeWX, and more important for him, no worries about updating things. That's 
> my main concern with editing/hacking a driver.
>
> On Saturday, January 23, 2021 at 10:02:38 AM UTC-5 rob.s...@googlemail.com 
> wrote:
>
>> I have just posted details of how to do it inside sdr.py. Seems a lot 
>> simpler that messing with the message queue.
>>
>> https://infiniteknowledge.co.uk/2021/01/23/adding-sensors-to-a-rpi-weather-station/
>>
>> On Saturday, 23 January 2021 at 13:55:40 UTC Greg Troxel wrote:
>>
>>>
>>> "gary@gmail.com"  writes: 
>>>
>>> > Thanks to Luc, the SDR is up and running. We interfaced with the 
>>> BMP280, 
>>> > but I am unable to find a service to read the barometer info into 
>>> WeeWX. 
>>> > 
>>> > How do we go about adding the BMP to WeeWX with the SDR? 
>>>
>>> What I would do, perhaps more complicated than you need, is to run an 
>>> mqtt broker and publish the pressure and use MQTTSubscribe. But if 
>>> there's already a temp path, seems best to extend it for pressure. 
>>> (IIRC the BMP280 does not have humidity, and the BME280 does). 
>>>
>>>

-- 
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/87e54268-15ff-4ccb-86a0-ced6e882f6cdn%40googlegroups.com.

[weewx-user] Re: Logia 5in1 - how to get barometer reading (need something like Wunderfixer)

[storm...@gmail.com]

If you are running a RPI, you can use a BME280 Sensor.

On Sunday, January 24, 2021 at 12:08:47 PM UTC-5 joewil...@gmail.com wrote:

> Hi All,
>
> I'm a newbie to weewx,  and I have been able to set up weewx to monitor my 
> weather station using SDR.   All works great,  but I would like to also get 
> the barometer reading from the console back into weewx.
>
> My color console doesn't have a way to expose the internal sensor data (no 
> usb/serial port),  but the console has the ability to post data directly to 
> Weather Underground,  which includes the barometric readings (which I have 
> been doing for the last couple of weeks).   Im thinking these are my 
> options at this point..
>
> 1) get a sensor that works at 915.000MHz. that sends the barometric 
> reading,  and add it to my sensor map
>
> or
>
> 2) write a python script that logs into weather underground,  and grabs 
> the barometric reading (that was sent by my console),  and stores it back 
> into the SQLLite database...   Not sure if anyone has done or thought of 
> this.
>
> Like to do 1) if I can get a cheap sensor,  but I can do 2)
>
> Thoughts?
> -Joe
>

-- 
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/55ec0c25-1707-43ee-9205-6350031c1744n%40googlegroups.com.

[weewx-user] Re: Version 4.3.0 released

[storm...@gmail.com]

Installed and works greatThanks Tom and crew

On Tuesday, January 5, 2021 at 12:23:15 PM UTC-5 WindnFog wrote:

> Installed and works A1.  Thanks, Tom.
>
> - Paul VE1DX
>
> On Monday, January 4, 2021 at 7:28:30 PM UTC-4 tke...@gmail.com wrote:
>
>> This release fixes a bug in V4.2 that caused average values to be calculated 
>> incorrectly if the archive interval changes.
>>
>>
>> 4.3.0 01/04/2020
>>
>> Version 4.2.0 had a bug, which caused the sums in the daily summary to be
>> incorrectly calculated. This version includes a patch to fix the problem. It
>> runs once at startup. Fixes issue #623.
>>
>> The WMR200 driver is no longer supported. An unsupported version can be found
>> at https://github.com/weewx/weewx-wmr200. Support for LaCrosse WS23xx and
>> Oregon WMR300 will continue.
>>
>> Service weewx.wxxtypes.StdDelta was inadvertently left out of the list of
>> services to be run. Fortunately, it is not used. Yet. Added it back in.
>>
>> Added the "old" NWS algorithm as an option for calculating heat index.
>>
>> Changed how various undocumented parameters in [StdWXCalculate] are 
>> specified.
>> The only one people are likely to have used is 'ignore_zero_wind'. Its name 
>> has
>> changed to 'force_null', and it has been moved. See the Upgrading Guide.
>>
>> Documented the various [StdWXCalculate] options.
>>
>> Fixed corner case for windDir when using software record generation,
>> ignore_zero_wind=True, and windSpeed=0 for entire record interval. Now emits
>> last windDir value.
>>
>> Fixed problem when looking up stars with more than one word in their name.
>> Fixes issue #620.
>>
>> Fixed problem where wind gust direction is not available when using software
>> record generation.
>>
>> Added --no-prompt action to wee_import allowing wee_import to be run 
>> unattended.
>>
>> Fixed problem that prevented option `observations` from being used in the
>> simulator. Thanks to user Graham!
>>
>> Fixed problem where wind chill was calculated incorrectly for METRICWX
>> databases. PR #627. Thanks to user edi-x!
>>
>> Allow wind vectors to be converted to unit of beaufort. Fixes issue #629.
>>
>> Option log_failure under [StdReport] is set to True by the upgrade process.
>> See the Upgrading Guide.
>>
>>

-- 
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/016dd5df-3509-4c47-b297-60d1beb77e04n%40googlegroups.com.

[weewx-user] Re: change wind direction from degress

[storm...@gmail.com]

try this:   $current.windDir.ordinal_compass  

On Saturday, January 2, 2021 at 6:42:00 AM UTC-5 hobbyl...@gmail.com wrote:

> hi everybody and happy new year!
>
> I wonder if there is a way to chande the wind direction statistics from 
> degrees to direction original
> for example from 360 to N 
> thank you!
>

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

Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

[storm...@gmail.com]

Or you can look into Berryboot: https://berryterminal.com/doku.php/berryboot

On Friday, January 1, 2021 at 2:21:23 PM UTC-5 steep...@gmail.com wrote:

> There are more SLC cards available from Mouser and other distributors with 
> much lager capacities. Those quoted below would struggle to contain an 
> operating system, WeeWX and data.
>
>  
>
> Sent from Mail  for 
> Windows 10
>
>  
>
> *From: *weather list
> *Sent: *01 January 2021 17:32
> *To: *weewx...@googlegroups.com
> *Subject: *Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 
> months of data?
>
>  
>
> The Meteobridge builder requires a high endurance microSD card for their 
> NANO SD unit; I haven’t investigated to see if they come in higher 
> capacities though it seems likely they would.
>
>  
>
> *Choice of microSD Card *
>
> To avoid lots of system fails caused by worn out consumer microSD cards we 
> restrict microSD cards that can be used in the NANO to 1GB and 2GB 
> industrial SLC cards. These are world-wide available from Mouser and other 
> electronic distributors. We decided to enforce use of these high endurance 
> cards to avoid having tons of unnecessary support requests and not to harm 
> the reputation of the NANO SD by failed cards. Please trust in our 
> experience with flash storage issues that there is simply no reasonable way 
> to avoid buying of high-price, high-endurance SLC storage. These are the 
> currently supported microSD cards: 
>
> swissbit SFSD1024N1BM1TO-I-DF-221-STD (microSD Card, 1 GB, SLC Flash, 
> -40°C - 85°C)
> swissbit SFSD2048N1BM1MT-I-ME-221-STD (microSD Card, 2 GB, SLC Flash, 
> -40°C - 85°C) 
>
> swissbit SFSD2048N1BM1MT-E-ME-221-STD (microSD Card, 2 GB, SLC Flash, 
> -25°C - 85°C)
> ATP AF2GUDI (microSD Card, 2 GB, SLC Flash, -40°C – 80°C)
> Cactus KS2GRIT-803M (microSD Card, 2 GB, SLC Flash, -45°C – 90°C)
>
> Panasonic SMSC02DA1 (microSD Card, 2 GB, SLC Flash, -40°C - 85°C)
>
> Apacer MSD02GIDI-T (microSD Card, 2 GB, SLC Flash) 
>
>
>
>
>
> On 1 Jan, 2021, at 08:52, Joe  wrote:
>
>  
>
> Sandisk extreme with the red and brown two tone color.  Unfortuantely, I 
> did not have one of these in the PI at the time.  Though I do now.  I've 
> never had one fail .
>
> On Monday, December 28, 2020 at 7:23:04 PM UTC-6 robcr...@gmail.com wrote:
>
> With all this talk about "good quality" SD cards, can anyone share a 
> recommendation?
>
>  
>
> I have an SSD that I run my main WeeWX/HomeAssistant server on, but I have 
> several others that I play around with, and need to get some new SD cards 
> for that purpose, so I figure I may as well get some "good" ones.
>
>  
>
> Thanks for any suggestions.
>
>  
>
> On Monday, December 28, 2020 at 4:36:23 AM UTC-8 Joe wrote:
>
> Ok I will get a look at it in about a week after a needed vacation.
>
> On Sunday, December 27, 2020 at 8:38:26 PM UTC-6 graha...@gmail.com wrote:
>
> the .html timestamps are all current (assuming Dec 27 19:50 is current).
>
> the .png timestamps are current until middle of the month images, then all 
> old → stopping part way through image generation.
>
> some of the .png timestamps are very late in the 5 minute reporting period 
> → maybe not finishing one report before starting the next.
>
> you will need to look at (post here) the detailed log showing from before 
> the start of report generation until past the end of completion of report 
> generation to see if there is overlap.
>
> or maybe the image generator is crashing part-way → ditto for need to see 
> detailed logs
>
>
>
> On 28 Dec 2020, at 12:54 pm, Joe  wrote:
>
>  
>
> -rw-r--r-- 1 root root  7357 Dec 27 19:51  daywind.png
>
> -rw-r--r-- 1 root root  6148 Dec 27 19:51  daywindvec.png
>
> -rw-r--r-- 1 root root  1150 Dec 27 19:46  favicon.ico
>
> drwxr-xr-x 2 root root  4096 Dec 25 20:53  font
>
> -rw-r--r-- 1 root root  7315 Dec 27 19:51 '#FTP.last'
>
> -rw-r--r-- 1 root root 25919 Dec 27 19:50  index.html
>
> -rw-r--r-- 1 root root   564 Dec 27 19:46  mobile.css
>
> -rw-r--r-- 1 root root  2413 Dec 27 19:50  mobile.html
>
> -rw-r--r-- 1 root root  7606 Dec 25 20:48  monthbarometer.png
>
> -rw-r--r-- 1 root root 11985 Dec 27 19:50  month.html
>
> -rw-r--r-- 1 root root  7135 Dec 25 20:48  monthhumidity.png
>
> -rw-r--r-- 1 root root  6519 Dec 25 20:53  monthhum.png
>
> -rw-r--r-- 1 root root  8204 Dec 25 20:51  monthinside.png
>
> -rw-r--r-- 1 root root  5436 Dec 25 20:51  monthpond.png
>
> -rw-r--r-- 1 root root  7674 Dec 25 20:51  monthradiation.png
>
> -rw-r--r-- 1 root root  6976 Dec 25 20:48  monthrain.png
>
> -rw-r--r-- 1 root root  7324 Dec 25 20:51  monthrx.png
>
> -rw-r--r-- 1 root root  9045 Dec 25 20:48  monthtempchill.png
>
> -rw-r--r-- 1 root root  9280 Dec 25 20:48  monthtempdew.png
>
>  
>
>  
>
>  
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to 

Re: [weewx-user] Display both °C and °F

[storm...@gmail.com]

I made a little summary paragraph.  I still need to work on it, since I get 
"N/A" if something is missing.

Current Weather for $station.location as of $current.dateTime: 
$current_obs_summary with a temperature of $current.outTemp 
($current.outTemp.degree_C) and a Feel Like Temperature of $current.appTemp 
($current.appTemp.degree_C). The current wet bulb temperature is 
$current.wet_bulb ($current.wet_bulb.degree_C). The wind is blowing from 
the $current.windDir.ordinal_compass ($current.windDir) at 
$current.windSpeed ($current.windSpeed.knot); Gusting to $current.windGust 
($current.windGust.knot) and an average windspeed of 
$hour($hours_ago=1).windSpeed.avg ($hour($hours_ago=1).windSpeed.avg.knot) 
with a max windgust of $hour($hours_ago=1).windGust.max 
($hour($hours_ago=1).windGust.max.knot). The current humidity is 
$current.outHumidity.


Current Weather for X, X as of 12/30/2020 01:45:00 PM: Mostly 
Cloudy with a temperature of 32.3 °F (0.2 °C) and a Feel Like Temperature 
of 25.7 °F (-3.5 °C). The current wet bulb temperature is 26.4 °F (-3.1 
°C). The wind is blowing from the SSE (158°) at 3 mph (3 knots); Gusting to 
7 mph (6 knots) and an average windspeed of 5 mph (5 knots) with a max 
windgust of 17 mph (15 knots). The current humidity is 63%.

Storm
On Wednesday, December 30, 2020 at 1:30:17 PM UTC-5 kb1...@gmail.com wrote:

> Here's what I did.
>
>  Current Conditions
>   
>   
> 
>   
> OUTSIDE 
> TEMP
> $current.outTemp 
> / $current.outTemp.degree_C
>   
>   
> Temperature Trend 
> ($trend.time_delta.hour.format("%.0f"))
> $trend.outTemp
>   
>   
> Wind Chill
> $current.windchill / 
> $current.windchill.degree_C
>   
>   
> Feels Like
> $current.heatindex / 
> $current.heatindex.degree_C
>   
>   
>
>
>
>
> Dave - KB1PVH
>
> On Wed, Dec 30, 2020 at 1:09 PM weather list  
> wrote:
>
>> My system uses US units but I’ve been looking to see if I can somehow 
>> display the temp in both systems:
>>
>> e.g.: 74 °F / 23 °C
>>
>> Perhaps this is in the docs but I have missed it?
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/01F1463B-990C-4F91-B6DF-1C1CD45D146E%40gmail.com
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4679ef9e-2a69-4dce-974c-35dd63ef3b01n%40googlegroups.com.

[weewx-user] Re: Display both °C and °F

[storm...@gmail.com]

Give this a try:  $current.outTemp ($current.outTemp.degree_C) 

On Wednesday, December 30, 2020 at 1:10:02 PM UTC-5 weatherl...@gmail.com 
wrote:

> My system uses US units but I’ve been looking to see if I can somehow 
> display the temp in both systems:
>
> e.g.: 74 °F / 23 °C
>
> Perhaps this is in the docs but I have missed it?

-- 
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/aef9a341-c7da-4dde-bb68-983a46a58153n%40googlegroups.com.

Re: [weewx-user] Davis Forecast Icons

[storm...@gmail.com]

Thanks Tom 

On Saturday, October 10, 2020 at 8:02:38 AM UTC-4 tke...@gmail.com wrote:

> See page 23 of the Davis Communications Reference Manual 
> 
> .
>
> On Fri, Oct 9, 2020 at 7:44 PM rich T  wrote:
>
>> Just wondering if anyone has a cross reference developed for the 
>> forecastIcon integer to the graphic?
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/d48367e6-b067-477d-905c-38c3edc9f45bo%40googlegroups.com
>>  
>> 
>> .
>>
>

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