[weewx-user] Re: Unknown archive type prevents working restart
Morning Gary, Thanks for replying. I hope its not a faulty unit as that could be the death of the weather station for now. She is over 10 years old now and I replaced one of the sensor modules only last year. If she does die I think I would build my own open source kit maybe? Anyway getting ahead of myself. *1) Stop Weewx* *It seems at some point in my wisdom I set up weewx as a Daemon so I have removed weewx from /etc/init.d and restarted the server (Its ubuntu running on QNAP's Virtualisation Station).* *2) Checking for remaining processes* *auser@pecan-ubuntu:/home/weewx$ ps aux | grep -i weewx* *auser** 1238 0.0 0.0 14428 1032 pts/0S+ 07:34 0:00 grep --color=auto -i weewx* *auser**@pecan-ubuntu**:/home/weewx$ pidof weewx* *auser**@pecan-ubuntu**:/home/weewx$ * *3) sudo ./bin/wee_device --clear-memory * *Using configuration file /home/weewx/weewx.conf* *Using Vantage driver version 3.2.1 (weewx.drivers.vantage)* *Proceeding will erase all archive records.* *Are you sure you wish to proceed (y/n)? y* *Erasing all archive records ...* *Archive records erased.* *4) set debug = 1 in weewx.conf and restart WeeWX with sudo ./bin/weewxd* syslog output is in attached file but run terminal output is like: *LOOP: 2021-06-17 07:40:57 BST (1623912057) altimeter: 29.86448769405689, appTemp: 54.776612632572494, barometer: 29.855, beaufort: 0, cloudbase: 1583.4599268474649, consBatteryVoltage: 4.48, dateTime: 1623912057, dayET: 0.0, dayRain: 0.0, dewpoint: 50.709576321871154, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, forecastIcon: 6, forecastRule: 45, heatindex: 54.5, humidex: 57.13247206192764, inDewpoint: 55.93846853316417, inHumidity: 59.0, insideAlarm: 0, inTemp: 71.0, leafWet4: 0.0, maxSolarRad: 363.4009700897632, monthET: 0.0, monthRain: 0.0, outHumidity: 87.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 54.5, pressure: 29.09* The loop date is correct so the question I have here is where has 2112-04-20 come from below? * DEBUG weewx.drivers.vantage: Getting archive packets since 2112-04-20 11:47:00 GMT (4490596020)Jun 17 07:41:14 pecan-ubuntu weewx[1372] DEBUG weewx.drivers.vantage: Gentle wake up of console successfulJun 17 07:41:14 pecan-ubuntu weewx[1372] DEBUG weewx.drivers.vantage: Retrieving 513 page(s); starting index= 3Jun 17 07:41:15 pecan-ubuntu weewx[1372] ERROR weewx.engine: Internal error detected. Catchup abandonedJun 17 07:41:15 pecan-ubuntu weewx[1372] ERROR weewx.engine: Unknown archive type = 0x37* I think my next step is going to be grabbing a copy of the database and seeing if I can see any problems but if you have any thoughts or solutions in mind I'd be grateful. Thanks Chris On Thursday, June 17, 2021 at 12:15:48 AM UTC+1 gjr80 wrote: > The few times this error seems to have come up the solution seems to be > clearing the logger memory or failing that contacting Davis due to a faulty > logger. > > I would not expect wee_device --dump to do anything different, it > essentially is doing the same as the startup catchup just for all records > in the logger memory. You say wee_device --clear-memory 'seems to > succeed', what does that mean, the --clear-memory command gives > appropriate output but subsequent restarting WeeWX causes the same output? > or does it mean that everything cleared up but the problem came back later? > > What does 'clear the logger using its own functions' mean? I thought the > only way to clear the logger was to use some suitable/capable software? And > do you still have a phantom WeeWX process running? > > How about trying this: > 1. stop WeeWX > 2. check for any remaining WeeWX processes and if any exist kill them > manually > 3. run wee_device --clear-memory and post the command used and the > resulting output > 4. set debug = 1 in weewx.conf and restart WeeWX, post the WeeWX log > output from startup through until an error occurs or data is obtained > successfully from the station > > Gary > > On Thursday, 17 June 2021 at 06:25:02 UTC+10 Chris Davies-Barnard wrote: > >> Evening all, >> >> So I had to move the logger and ubuntu box today and upon reconnecting >> and restarting I have encountered the following error. >> >> J*un 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.drivers.vantage: >> Getting archive packets since 2112-04-20 11:47:00 GMT (4490596020)* >> *Jun 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.drivers.vantage: >> Gentle wake up of console successful* >> *Jun 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.drivers.vantage: >> Retrieving 513 page(s); starting index= 2* >> *Jun 16 21:00:16 pecan-ubuntu weewx[1823] ERROR weewx.engine: Internal >> error detected. Catchup abandoned* >> *Jun 16 21:00:16 pecan-ubuntu weewx[1823] ERROR weewx.engine: >> Unknown archive type = 0xae* >> *Jun 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.reportengine: >> Running rep
[weewx-user] Re: Unknown archive type prevents working restart
The few times this error seems to have come up the solution seems to be clearing the logger memory or failing that contacting Davis due to a faulty logger. I would not expect wee_device --dump to do anything different, it essentially is doing the same as the startup catchup just for all records in the logger memory. You say wee_device --clear-memory 'seems to succeed', what does that mean, the --clear-memory command gives appropriate output but subsequent restarting WeeWX causes the same output? or does it mean that everything cleared up but the problem came back later? What does 'clear the logger using its own functions' mean? I thought the only way to clear the logger was to use some suitable/capable software? And do you still have a phantom WeeWX process running? How about trying this: 1. stop WeeWX 2. check for any remaining WeeWX processes and if any exist kill them manually 3. run wee_device --clear-memory and post the command used and the resulting output 4. set debug = 1 in weewx.conf and restart WeeWX, post the WeeWX log output from startup through until an error occurs or data is obtained successfully from the station Gary On Thursday, 17 June 2021 at 06:25:02 UTC+10 Chris Davies-Barnard wrote: > Evening all, > > So I had to move the logger and ubuntu box today and upon reconnecting and > restarting I have encountered the following error. > > J*un 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.drivers.vantage: > Getting archive packets since 2112-04-20 11:47:00 GMT (4490596020)* > *Jun 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.drivers.vantage: > Gentle wake up of console successful* > *Jun 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.drivers.vantage: > Retrieving 513 page(s); starting index= 2* > *Jun 16 21:00:16 pecan-ubuntu weewx[1823] ERROR weewx.engine: Internal > error detected. Catchup abandoned* > *Jun 16 21:00:16 pecan-ubuntu weewx[1823] ERROR weewx.engine: Unknown > archive type = 0xae* > *Jun 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.reportengine: > Running reports for latest time in the database.* > *Jun 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.drivers.vantage: > Requesting 200 LOOP packets.* > > I have tried > > 1) sudo ./bin/wee_device --dump which ends in same/similar error > 2) sudo ./bin/wee_device --clear-memory which seems to succeed. > > I have also cleared the logger using its own functions but thee situation > is the same.. > > What's interesting is that stopping weewx seems to cause a lock and it > never completes. > > If anyone could help me solve the problem I would be very grateful. > > Thanks > > Chris > -- 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/deab4b08-d47f-45e3-8ecd-d1bc14225f79n%40googlegroups.com.
[weewx-user] Unknown archive type prevents working restart
Evening all, So I had to move the logger and ubuntu box today and upon reconnecting and restarting I have encountered the following error. J*un 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.drivers.vantage: Getting archive packets since 2112-04-20 11:47:00 GMT (4490596020)* *Jun 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.drivers.vantage: Gentle wake up of console successful* *Jun 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.drivers.vantage: Retrieving 513 page(s); starting index= 2* *Jun 16 21:00:16 pecan-ubuntu weewx[1823] ERROR weewx.engine: Internal error detected. Catchup abandoned* *Jun 16 21:00:16 pecan-ubuntu weewx[1823] ERROR weewx.engine: Unknown archive type = 0xae* *Jun 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.reportengine: Running reports for latest time in the database.* *Jun 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.drivers.vantage: Requesting 200 LOOP packets.* I have tried 1) sudo ./bin/wee_device --dump which ends in same/similar error 2) sudo ./bin/wee_device --clear-memory which seems to succeed. I have also cleared the logger using its own functions but thee situation is the same.. What's interesting is that stopping weewx seems to cause a lock and it never completes. If anyone could help me solve the problem I would be very grateful. Thanks Chris -- 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/ddff3160-dff7-48d6-9266-5f806fdf872bn%40googlegroups.com.
[weewx-user] Re: lightning sensor made at home cheaply
Very cool, Rich!
I'll put some effort into it.
Based on your earlier coaching, I've been able to successfully accept MQTT
data from every sensor I've tried, including from a Sonoff Zigbee Bridge
with a bunch of Sonoff SNZB-02 temperature sensors!
[[[tele/ZBBridge/SENSOR]]]
# 0x4472 is #10 Living Room
ZbReceived_0x4472_Device
ignore = true
ZbReceived_0x4472_Name
ignore = true
ZbReceived_0x4472_Temperature
# The WeeWX name.
# Default is the name from MQTT.
name = inTemp
ZbReceived_0x4472_Humidity
# The WeeWX name.
# Default is the name from MQTT.
name = inHumidity
ZbReceived_0x4472_BatteryVoltage
ignore = true
ZbReceived_0x4472_BatteryPercentage
ignore = true
ZbReceived_0x4472_Endpoint
ignore = true
ZbRecieved_0x4472_LinkQuality
ignore = true
On Wednesday, June 16, 2021 at 1:00:18 PM UTC-5 bell...@gmail.com wrote:
> Eric,
> For (2), MQTTSubscribe has a 'filter_out_message_when' option. So, you
> would to do something like this in the MQTTSubscribe section
> [[topics]]
> [[[tele/AS3935/SENSOR]]]
> AS3935_Event
> ignore = True
> # MQTT messages with and event value in the following will be ignored.
> filter_out_message_when = 0, 2, 3, 4, 5, 6, 7, 8, 9
> conversion_type = int
> .
> .
> .
>
> A bit more detail on this option can be found here,
> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring-additional-options#filter_out_message_when
> There is some background information here,
> https://github.com/bellrichm/WeeWX-MQTTSubscribe/discussions/112
>
> For (3), read up on WeeWX accumulators here,
> https://github.com/weewx/weewx/wiki/Accumulators
>
> If you get this working, this is exactly the type of MQTTSubscribe
> configuration that I would like to capture as an example to help others in
> the future.
> - Rich
>
>
> On Tuesday, 15 June 2021 at 19:35:19 UTC-4 Eric K wrote:
>
>> I just assembled this exact setup - AS3935 board with a Wemos D1 mini
>> clone and Tasmota 9.4.0 sensor firmware.
>> I didn't snap a picture before I deployed it, but it looks very much like
>> the attached photo.
>> I followed this page: https://tasmota.github.io/docs/AS3935/
>>
>> Its working and I'm getting live data in the Tasmota web interface.
>> I named it AS3935 in the Tasmota MQTT setup and it's sending telemetry to
>> my mosquitto MQTT broker.
>> The MQTT transmissions (seen from the Tasmota console) look like the
>> example on the tasmota.github AS3935 page:
>> 18:07:21.164 MQT: tele/AS3935/SENSOR =
>> {"Time":"2021-06-15T18:07:21","AS3935":{"Event":0,"Distance":0,"Energy":0,"Stage":7}}
>>
>> I think I need to:
>> 1. set the Tasmota setting AS3935lightevent to 1 so it only sends MQTT
>> messages when there is a lightning strike registered.
>> 2. set up weewx to read the MQTT Event variable so I only react to a
>> valid lightning strike with distance (event 1)
>> 3. Set up the lightning_count variable as an accumulator?
>>
>> I'm not quite sure:
>> 1. how often I should set Tasmota's MQTT report period so I don't miss
>> counting a lightning strike? Once per second?
>> 2. how to set up a conditional statement in the MQTTSubscribe section of
>> weewx.conf to increment the lightning_count only when valid lightning
>> events occur.
>>
>> I'll be looking for example weewx.conf file settings that deal with the
>> AS3935.
>> On Sunday, December 6, 2020 at 12:51:45 PM UTC-6 misk...@gmail.com wrote:
>>
>>> Hello guys,
>>> did anyone tried to use *Lightning sensor AS3935* tinkered on cheap
>>> *ESP8266* with WeeWX?
>>>
>>> A time ago, I was user of Tasmota ESP8266 firmware and I know, it can
>>> publish MQTT + JSON data. Here is the manual how to tinker and flash those
>>> two together:
>>> https://tasmota.github.io/docs/AS3935/
>>> I assume, that with JSON / MQTT it would be prety easy to fill WeeWX
>>> database...
>>>
>>> Thanks,
>>> Miso,
>>> Slovakia
>>>
>>
--
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/10f9bd8c-2722-4fed-adab-a54b9d965ab8n%40googlegroups.com.
[weewx-user] Re: How to send AS3935 Thunder Board (SwitchDocs) data to weewx.sdb
I was hoping Mathew Wall would see the question and respond. It appears he wrote it. I have not downloaded the code and looked. Based on the config sections shown on the wiki page, it looks like it's may be hard-coded to talk to a Raspberry Pi port. If that's true, it might not work with the MQTT transport directly, and require more rewriting than I am able to do. I'm primarily a hardware engineer. I can read and write code, but its not my strong suit, or my passion. I like to find out if something is difficult or impossible, before I spend a lot of time on it. Getting answers from people who already know doesn't require much effort from anyone, so its a good plan, in my view. On Wednesday, June 16, 2021 at 12:52:42 PM UTC-5 vince wrote: > On Wednesday, June 16, 2021 at 9:50:22 AM UTC-7 Eric K wrote: > >> Vince, if you don't know the answer to a question, why do you respond? >> >> > You asked a very open ended question. > I'm trying to understand what you have already looked into or tried. > > I took the time to download and look at the code. > The answer to your question is very obvious if take just a little time and > put just a little effort in. > > > -- 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/19aa60ac-ef8a-41f9-afb1-ba8e04d222aen%40googlegroups.com.
[weewx-user] Re: lightning sensor made at home cheaply
Eric,
For (2), MQTTSubscribe has a 'filter_out_message_when' option. So, you
would to do something like this in the MQTTSubscribe section
[[topics]]
[[[tele/AS3935/SENSOR]]]
AS3935_Event
ignore = True
# MQTT messages with and event value in the following will be ignored.
filter_out_message_when = 0, 2, 3, 4, 5, 6, 7, 8, 9
conversion_type = int
.
.
.
A bit more detail on this option can be found here,
https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring-additional-options#filter_out_message_when
There is some background information here,
https://github.com/bellrichm/WeeWX-MQTTSubscribe/discussions/112
For (3), read up on WeeWX accumulators here,
https://github.com/weewx/weewx/wiki/Accumulators
If you get this working, this is exactly the type of MQTTSubscribe
configuration that I would like to capture as an example to help others in
the future.
- Rich
On Tuesday, 15 June 2021 at 19:35:19 UTC-4 Eric K wrote:
> I just assembled this exact setup - AS3935 board with a Wemos D1 mini
> clone and Tasmota 9.4.0 sensor firmware.
> I didn't snap a picture before I deployed it, but it looks very much like
> the attached photo.
> I followed this page: https://tasmota.github.io/docs/AS3935/
>
> Its working and I'm getting live data in the Tasmota web interface.
> I named it AS3935 in the Tasmota MQTT setup and it's sending telemetry to
> my mosquitto MQTT broker.
> The MQTT transmissions (seen from the Tasmota console) look like the
> example on the tasmota.github AS3935 page:
> 18:07:21.164 MQT: tele/AS3935/SENSOR =
> {"Time":"2021-06-15T18:07:21","AS3935":{"Event":0,"Distance":0,"Energy":0,"Stage":7}}
>
> I think I need to:
> 1. set the Tasmota setting AS3935lightevent to 1 so it only sends MQTT
> messages when there is a lightning strike registered.
> 2. set up weewx to read the MQTT Event variable so I only react to a valid
> lightning strike with distance (event 1)
> 3. Set up the lightning_count variable as an accumulator?
>
> I'm not quite sure:
> 1. how often I should set Tasmota's MQTT report period so I don't miss
> counting a lightning strike? Once per second?
> 2. how to set up a conditional statement in the MQTTSubscribe section of
> weewx.conf to increment the lightning_count only when valid lightning
> events occur.
>
> I'll be looking for example weewx.conf file settings that deal with the
> AS3935.
> On Sunday, December 6, 2020 at 12:51:45 PM UTC-6 misk...@gmail.com wrote:
>
>> Hello guys,
>> did anyone tried to use *Lightning sensor AS3935* tinkered on cheap
>> *ESP8266* with WeeWX?
>>
>> A time ago, I was user of Tasmota ESP8266 firmware and I know, it can
>> publish MQTT + JSON data. Here is the manual how to tinker and flash those
>> two together:
>> https://tasmota.github.io/docs/AS3935/
>> I assume, that with JSON / MQTT it would be prety easy to fill WeeWX
>> database...
>>
>> Thanks,
>> Miso,
>> Slovakia
>>
>
--
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/68dbcf0b-f412-41e2-a241-ced2a98aff39n%40googlegroups.com.
[weewx-user] Re: How to send AS3935 Thunder Board (SwitchDocs) data to weewx.sdb
On Wednesday, June 16, 2021 at 9:50:22 AM UTC-7 Eric K wrote: > Vince, if you don't know the answer to a question, why do you respond? > > You asked a very open ended question. I'm trying to understand what you have already looked into or tried. I took the time to download and look at the code. The answer to your question is very obvious if take just a little time and put just a little effort in. -- 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/1a90367e-c519-4cf0-bf90-edb658e651b7n%40googlegroups.com.
[weewx-user] Re: How to send AS3935 Thunder Board (SwitchDocs) data to weewx.sdb
Vince, if you don't know the answer to a question, why do you respond? On Wednesday, June 16, 2021 at 11:46:02 AM UTC-5 vince wrote: > On Wednesday, June 16, 2021 at 9:42:51 AM UTC-7 Eric K wrote: > >> I wonder if anyone knows if this AS9395 service >> https://github.com/weewx/weewx/wiki/as3935 >> can be configured to work with MQTT data, or if its hard-coded to only >> talk to ports on the Raspberry Pi? >> >> > Did you download and look at the code ? > > > -- 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/8f624ea8-9707-4e7b-8cac-6cad273b7fb1n%40googlegroups.com.
[weewx-user] Re: How to send AS3935 Thunder Board (SwitchDocs) data to weewx.sdb
On Wednesday, June 16, 2021 at 9:42:51 AM UTC-7 Eric K wrote: > I wonder if anyone knows if this AS9395 service > https://github.com/weewx/weewx/wiki/as3935 > can be configured to work with MQTT data, or if its hard-coded to only > talk to ports on the Raspberry Pi? > > Did you download and look at the code ? -- 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/99ee9ab3-1fee-4b73-b3c1-f7b317ede0e8n%40googlegroups.com.
[weewx-user] Re: How to send AS3935 Thunder Board (SwitchDocs) data to weewx.sdb
I wonder if anyone knows if this AS9395 service https://github.com/weewx/weewx/wiki/as3935 can be configured to work with MQTT data, or if its hard-coded to only talk to ports on the Raspberry Pi? On Monday, August 20, 2018 at 10:22:36 AM UTC-5 bgra...@umw.edu wrote: > Pat, >>> > This is the board I have: > https://shop.switchdoc.com/collections/grove/products/the-thunder-board-i2c-lightning-detector-grove-connectors > > It looks as if the weewx extension Matt suggests would be the best but I > would prefer to run it in an RPI and not my main weewx server, if possible. > The AS3935 board I have is not the one he references but it seems to have > the same connections using Grove connectors. > > I'm going to play around with the software from SwitchDocs Lab and see > what I come up with. If I can eliminate the PubNub host and produce a web > page on my own server then that might work. However, since weewx already > has a data display and graph built-in then that looks promising also. Sort > of mixed up as to what to do at this point... Thanks. > 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/8ad13457-cbdf-4a02-9c9a-0ffc4e556bb8n%40googlegroups.com.
