Re: [weewx-user] Recovery from 3 month outage

[gjr80]

I am not an Acurite user, and am happy to be corrected by one, but I 
suspect you are out of luck:

   - For drivers and stations that support downloading historical data, 
   WeeWX will automatically download historical data upon WeeWX being 
   restarted. There is a caveat though, WeeWX will only download historical 
   data that is newer than the most recent record in the WeeWX database; so if 
   you have a gap in your database (ie records before and after a period of 
   missing data) WeeWX will not download historical data for that gap.
   - For a WeeWX driver to download historical data the driver requires a 
   genArchiveRecords() method, the WeeWX acurite driver has no such method so 
   is unable to download historical data
   - Looking at the WeeWX Hardware Guide 
    the Acurite 1536 
   appears to only operate in USB mode 4 which does not support storing data 
   in the logger (I understand Acurite has never been too forthcoming with 
   detailed technical data on their stations so I don’t know the veracity of 
   this information).

Bottom line is if WeeWX and your station can download historical data it 
would have happened during WeeWX start up/restart, there is nothing you 
need to other than restart WeeWX.

Gary
On Wednesday, 26 May 2021 at 03:48:14 UTC+10 Jeff Carpenter wrote:

> I looked again at the data after letting things run overnight, and it does 
> not appear that recent historical data from (i.e. within the last two 
> weeks) is being pulled, as I only see data since I rebooted the Pi. Is 
> there a way to force weewx to pull whatever historical data is available?
>
> On Tuesday, May 25, 2021 at 2:04:42 AM UTC-7 lang@googlemail.com 
> wrote:
>
>> Searching helps 😎
>> As per that link (review) the 01536 can save records for two weeks (don't 
>> say based on what interval)
>> https://weatherstationexpert.com/acurite-01536/
>>
>>
>>
>> On 25.05.2021 05:45, Jeff Carpenter wrote:
>>
>> Hello 
>>
>> I just discovered that my weewx installation has not been collecting data 
>> from my Acurite weather station for about 3 months, even though it appears 
>> the Raspberry Pi where weewx is running has been up - I haven't restarted 
>> that Pi in probably over a year. I rebooted the PI and weewx is now 
>> collecting new data. 
>>
>> From the documentation it sounds like weewx will go back and collect 
>> historical data from the Acurite, is this correct? How much of that 
>> historical data should I expect to recover?
>>
>> I've attached output of wee_debug command.
>>
>> Thanks
>> Jeff
>>
>> -- 
>> 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/c25e420d-2778-48d9-9622-7cea63fee08cn%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/4e8128be-eef7-4c19-9fe9-73597da78342n%40googlegroups.com.

[weewx-user] Re: Hopefully a simle question WRT WeeWX-MQTTSubscribe...

[richard maliszewski]

And digging through the MQTTSubscribe customization guide, found 
"expires_after", which does exactly what I needed when set to "None".

--Richard

On Monday, May 24, 2021 at 1:46:57 PM UTC-7 richard maliszewski wrote:

> So have MQTTSubscribe installed as a service, and have made what I believe 
> to be reasonable entries into its section of weewx.conf, and modified the 
> Seasons skin.conf and current.inc to display the new data, which I assume 
> is getting archived.  I have two inbound MQTT temperature values assigned 
> to extraTemp1 and extraTemp2.  In the "current" readings, I have seen valid 
> readings, but much of the time, I see "N/A".  I'm guessing this is because 
> there was no published reading received during the archive interval?  The 
> Aqara sensors only send updates when the sensed reading changes, so for one 
> of the sensors ( garage) that can be fairly infrequent.  I see these N/A 
> values whether I use $current or $latest for the displayed values.
>
> How can I get the display of the last published value?  I've done some 
> digging, and I suspect I may have to add an Accumulator section?  If so, 
> what would that look like?
>
> And on a related note, is the last published value getting archived at 
> each archive interval, or only when there's a new value in the current 
> archive interval?
>
> Thanks in advance for any light shined this direction.
>
> --Richard
>
>
>
>
> On Wednesday, May 19, 2021 at 11:00:57 AM UTC-7 bell...@gmail.com wrote:
>
>> Since you have a working install of WeeWX that you want to augment with 
>> MQTT data, you want to run MQTTSubscribe as a service. It doesn't matter 
>> whether the driver is using software or hardware record generation. 
>>
>> rich
>>
>> On Monday, 17 May 2021 at 17:12:49 UTC-4 rlmali...@gmail.com wrote:
>>
>>> I have an AW WS5000 station, and am using the excellent GW1000 driver to 
>>> pull data off of it into WeeWX.  Am also using the Purple Air plugin to 
>>> bring data from our local sesnor in as well.  This all works well.
>>>
>>> We have a handful of Aqara temp/hum/bar sensors that talk to an 
>>> Aqara-Home bridge.  I have Home automations set up to "publish" readings to 
>>> our home automation system, and that all works well.  It'd be lovely to be 
>>> able to send those readings to WeeWX as well, for archiving of data if 
>>> nothing else.
>>>
>>> It's not hard to augment the Home automations to publish readings via 
>>> MQTT as well.  It looks like WeeWX-MQTTSubscribe is a good collector for 
>>> such.  I've bumbled around searching for in-use examples enough that I 
>>> believe I can get the weewx.conf entries correct.
>>>
>>> But to make certain (before I do the wrong thing and break things that 
>>> are currently working quite well), the READE.md says that if I am adding 
>>> data to that provided by another driver, install as a service.  I am 
>>> augmenting data from other drivers, but those are both producing software 
>>> records.  Is service the right way to go, or will this play nicely with the 
>>> other software drivers?
>>>
>>> Thanks in advance.
>>> Richard 
>>>
>>

-- 
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/dd4acf8a-60cf-44be-a0a2-b1b23d5f2194n%40googlegroups.com.

Re: [weewx-user] Recovery from 3 month outage

[Jeff Carpenter]

I looked again at the data after letting things run overnight, and it does 
not appear that recent historical data from (i.e. within the last two 
weeks) is being pulled, as I only see data since I rebooted the Pi. Is 
there a way to force weewx to pull whatever historical data is available?

On Tuesday, May 25, 2021 at 2:04:42 AM UTC-7 lang@googlemail.com wrote:

> Searching helps 😎
> As per that link (review) the 01536 can save records for two weeks (don't 
> say based on what interval)
> https://weatherstationexpert.com/acurite-01536/
>
>
>
> On 25.05.2021 05:45, Jeff Carpenter wrote:
>
> Hello 
>
> I just discovered that my weewx installation has not been collecting data 
> from my Acurite weather station for about 3 months, even though it appears 
> the Raspberry Pi where weewx is running has been up - I haven't restarted 
> that Pi in probably over a year. I rebooted the PI and weewx is now 
> collecting new data. 
>
> From the documentation it sounds like weewx will go back and collect 
> historical data from the Acurite, is this correct? How much of that 
> historical data should I expect to recover?
>
> I've attached output of wee_debug command.
>
> Thanks
> Jeff
>
> -- 
> 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/c25e420d-2778-48d9-9622-7cea63fee08cn%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/b6c3f762-016f-4770-a85f-dbeedd80ce40n%40googlegroups.com.

Re: [weewx-user] Re: new weewx install not creating database or webpage

[Eric K]

I want to point out an error from above, so no one copies my mistake.
The [[Corrections]] section does not belong in the [SDR] driver section!

Here's how it should look:

##

[SDR]
# This section is for the software-defined radio driver.
# collect data from Acurite Atlas sensor 0011

# The driver to use
driver = user.sdr
cmd = rtl_433 -R 40 -M utc -F json

[[sensor_map]]
outTemp = temperature.0011.AcuriteAtlasPacket
outHumidity = humidity.0011.AcuriteAtlasPacket
windSpeed = wind_speed.0011.AcuriteAtlasPacket
windDir = wind_dir.0011.AcuriteAtlasPacket
UV = uv.0011.AcuriteAtlasPacket
Atlas_rain_total = rain_total.0011.AcuriteAtlasPacket
lux = lux.0011.AcuriteAtlasPacket
Atlas_strike_count = strike_count.0011.AcuriteAtlasPacket
lightning_distance = strike_distance.0011.AcuriteAtlasPacket
BatteryStatus = battery.0011.AcuriteAtlasPacket

[[deltas]]
rain = Atlas_rain_total
lightning_strike_count = Atlas_strike_count

##

[StdCalibrate]

[[Corrections]]
lightning_distance = lightning_distance if Atlas_stike_count > 0 
else None
On Tuesday, April 27, 2021 at 8:39:38 PM UTC-5 peterq...@gmail.com wrote:

> Biggest downside to decreasing the interval is the increase in database 
> size for no real gain in accuracy. I have my interval set at 2 minutes and 
> I am thinking about thinning out some of the historical data because the 
> database is 140MB and goes up by about 4mb a month.
>
> There is a real time extension that operates as fast as the data comes in, 
> so if you're looking at wind speed/direction, you can get that.
>
> On Tue, Apr 27, 2021 at 6:32 PM Eric Koester  wrote:
>
>> Thanks for the hints and suggestions.
>> I'm over the hump.  
>> Data is flowing from rtl_433, to weewx-sdr, to weewx!
>>
>> Now, the fine tuning and preference tweaking can occur!
>>
>> Is there any big downside to lowering the archive interval to 60 seconds?
>> What are your favorite weewx webpage skins?
>>
>> Eric
>> On Tuesday, April 27, 2021 at 1:54:19 PM UTC-5 Eric Koester wrote:
>>
>>> I got some hints/tips on getting the correct variable names from the 
>>> parsed and unparsed data that the sdr.py produces.
>>>
>>> I am now getting data into the database and the index.html file has been 
>>> produced!
>>>
>>> Oddly, the Firefox browser is able to 
>>> display file:///home/weewx/public_html/index.html , but Chromium is not.  I 
>>> get an error from Chromium:
>>>
>>> Access to the file was denied
>>>
>>> The file at *file:///home/weewx/public_html/index.html* is not 
>>> readable. It may have been removed, moved, or file permissions may be 
>>> preventing access.
>>>
>>> Now, I'm tweaking the [sensor_map] variables so they line up with the 
>>> variables in weewx, and all the collected data gets displayed.
>>>
>>>
>>> ##
>>>
>>> [SDR]
>>> # This section is for the software-defined radio driver.
>>> # collect data from Acurite Atlas sensor 0011
>>> 
>>> # The driver to use
>>> driver = user.sdr
>>> cmd = rtl_433 -R 40 -M utc -F json
>>> 
>>> [[sensor_map]]
>>> outTemp = temperature.0011.AcuriteAtlasPacket
>>> outHumidity = humidity.0011.AcuriteAtlasPacket
>>> windSpeed = wind_speed.0011.AcuriteAtlasPacket
>>> windDir = wind_dir.0011.AcuriteAtlasPacket
>>> UV = uv.0011.AcuriteAtlasPacket
>>> rain_total = rain_total.0011.AcuriteAtlasPacket
>>> lux = lux.0011.AcuriteAtlasPacket
>>> strikes_total = strike_count.0011.AcuriteAtlasPacket
>>> strike_distance = strike_distance.0011.AcuriteAtlasPacket
>>> BatteryStatus = battery.0011.AcuriteAtlasPacket
>>> 
>>> [[Corrections]]
>>> strike_distance = strike_distance if Lightning_Strikes > 0 else 
>>> None
>>>
>>>
>>> ##
>>>
>>> On Tuesday, April 27, 2021 at 12:06:43 PM UTC-5 Eric Koester wrote:
>>>
 I just posted a request for help on the weewx-sdr github issues tab.
 I demonstrated weewx-sdr working by calling 
 '/home/weewx/bin/user/sdr.py' and showing the valid weather station output.
 I asked them to look over my weewx.conf file for corrections.

 For my own information, I just ran wee_debug and it confirms the 
 database is empty.

 System info
   Platform:   Linux-5.8.0-50-generic-x86_64-with-glibc2.32
   Python Version: 3.8.6

 Load Information
   1 minute load average:  0.00
   5 minute load average:  0.07
   15 minute load average: 0.11

 General Weewx info
   Weewx version 4.5.1 detected.

 Statio

[weewx-user] Re: Lightning Data Stored in weewx.sdb

[Eric K]

It's working as desired now!
Thanks for noticing the incorrect location of the [[Corrections]]

[image: lightning_distance working.JPG]

On Monday, May 24, 2021 at 7:39:25 AM UTC-5 gjr80 wrote:

> I can't explain it, it would require some detailed knowledge of how the 
> Acurite lightning sensor behaves. For example, the Ecowitt lightning sensor 
> reports distance when strikes are detected and that distance value persists 
> for some time before eventually reporting 0. If you had debug logging of 
> the SDR output (as you have in the log extract above) going on for some 
> time previous you could probably work through the log looking at the 
> distance value being obtained by the SDR driver from the Acurite. One thing 
> is certain though, the SDR driver was not applying the correction as the 
> SDR driver contains no code to read those config settings. And if the 
> correction was not under [StdCalibrate] [[Corrections]] then WeeWX wasn't 
> applying the correction either.
>
> Might just have to remain a mystery.
>
> Gary
>
> On Monday, 24 May 2021 at 07:33:56 UTC+10 Eric K wrote:
>
>> Thanks for the pointer.  
>> I also had a [[Corrections]] sections under [StdCalibrate].
>>
>> I just moved the lightning_distance correction to the [StdCalibrate] 
>> section.
>> We'll see if that helps.
>>
>> Isn't it odd that it worked, when the lightning_distance was something 
>> other than 10?
>>
>>
>> On Sunday, May 23, 2021 at 3:10:54 PM UTC-5 gjr80 wrote:
>>
>>> I think you might find the [[Corrections]] stanza belongs under 
>>> [StdCalibrate]  
>>> rather than the SDR driver.
>>>
>>> Gary
>>> On Monday, 24 May 2021 at 02:32:14 UTC+10 Eric K wrote:
>>>
 Here's a relevant section of the log which shows the Acurite Atlas 
 lightning sensor sending the last distance (10) reading over and over.  
 This is expected Acurite Atlas behavior, and the reason we have to put 
 the "if > 0 else None" statement in our [[Corrections]] section.

 Referring back to the 5.64705882352941 value seen in my database:
 I wonder if weewx isn't expecting a decimal reading to be in 
 lightning_distance?
 And that sends it into confusion?

 May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: 
 lines=['{"time" : "2021-05-23 15:56:20", "model" : "Acurite-Atlas", "id" : 
 17, "channel" : "A", "sequence_num" : 0, "battery_ok" : 1, "message_type" 
 : 
 38, "wind_avg_mi_h" : 4.000, "wind_dir_deg" : 190.000, "rain_in" : 2.040, 
 "strike_count" : 45, "strike_distance" : 10, "exception" : 0, "raw_msg" : 
 "c011668205f9cc8baab8"}\n', '{"time" : "2021-05-23 15:56:20", "model" : 
 "Acurite-Atlas", "id" : 17, "channel" : "A", "sequence_num" : 1, 
 "battery_ok" : 1, "message_type" : 38, "wind_avg_mi_h" : 4.000, 
 "wind_dir_deg" : 190.000, "rain_in" : 2.040, "strike_count" : 45, 
 "strike_distance" : 10, "exception" : 0, "raw_msg" : 
 "c411668205f9cc8baabc"}\n', '{"time" : "2021-05-23 15:56:20", "model" : 
 "Acurite-Atlas", "id" : 17, "channel" : "A", "sequence_num" : 2, 
 "battery_ok" : 1, "message_type" : 38, "wind_avg_mi_h" : 4.000, 
 "wind_dir_deg" : 190.000, "rain_in" : 2.040, "strike_count" : 45, 
 "strike_distance" : 10, "exception" : 0, "raw_msg" : 
 "c811668205f9cc8baac0"}\n']
 May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: 
 packet={'windSpeed': 4.0, 'windDir': 190.0, 'Atlas_rain_total': 2.04, 
 'Atlas_strike_count': 45, 'lightning_distance': 10, 'windBatteryStatus': 
 0, 
 'dateTime': 1621785380, 'usUnits': 1}
 May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
 (Service) data-> final packet is 2021-05-23 10:56:20 CDT (1621785380): 
 Atlas_rain_total: 2.04, Atlas_strike_count: 45, dateTime: 1621785380, 
 lightning_distance: 10, lightning_strike_count: 0, rain: 0.0, usUnits: 1, 
 windBatteryStatus: 0, windDir: 190.0, windSpeed: 4.0
 May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: 
 packet={'windSpeed': 4.0, 'windDir': 190.0, 'Atlas_rain_total': 2.04, 
 'Atlas_strike_count': 45, 'lightning_distance': 10, 'windBatteryStatus': 
 0, 
 'dateTime': 1621785380, 'usUnits': 1}
 May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
 (Service) data-> final packet is 2021-05-23 10:56:20 CDT (1621785380): 
 Atlas_rain_total: 2.04, Atlas_strike_count: 45, dateTime: 1621785380, 
 lightning_distance: 10, lightning_strike_count: 0, rain: 0.0, usUnits: 1, 
 windBatteryStatus: 0, windDir: 190.0, windSpeed: 4.0
 May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: 
 packet={'windSpeed': 4.0, 'windDir': 190.0, 'Atlas_rain_total': 2.04, 
 'Atlas_strike_count': 45, 'lightning_distance': 10, 'windBatteryStatus': 
 0, 
 'dateTime': 1621785380, 'usUnits': 1}
 May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
>>>

Re: [weewx-user] Recovery from 3 month outage

[Rainer Lang]

Searching helps 😎
As per that link (review) the 01536 can save records for two weeks 
(don't say based on what interval)

https://weatherstationexpert.com/acurite-01536/



On 25.05.2021 05:45, Jeff Carpenter wrote:

Hello

I just discovered that my weewx installation has not been collecting 
data from my Acurite weather station for about 3 months, even though 
it appears the Raspberry Pi where weewx is running has been up - I 
haven't restarted that Pi in probably over a year. I rebooted the PI 
and weewx is now collecting new data.


From the documentation it sounds like weewx will go back and collect 
historical data from the Acurite, is this correct? How much of that 
historical data should I expect to recover?


I've attached output of wee_debug command.

Thanks
Jeff
--
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/c25e420d-2778-48d9-9622-7cea63fee08cn%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/c208b952-cf5d-006f-a61b-4ea3012f7aa8%40gmail.com.