Re: [weewx-user] Database merged - Wview e weewx

[kha...@gmail.com]

Thanks u so much...
I understand how to fix it :)
Now works prefectly
Il giorno giovedì 21 ottobre 2021 alle 13:23:30 UTC+2 itec ha scritto:

> Hi.
> What do you mean for "This unfortunately doesn't works correctly."? What's 
> wrong?
> I think that decimals are not important.
> Have you tried to run "wee_database --drop-daily" and "wee_database 
> --rebuild-daily"?
> Then delete /var/www/html/weewx/ and run "wee_reports" to regenerate all 
> reports
>
> Il giorno domenica 10 ottobre 2021 alle 22:05:50 UTC+2 kha...@gmail.com 
> ha scritto:
>
>> hi,
>> when i started to use weewx i used a new database. Few months later i 
>> merged two database.
>>
>> Il giorno lunedì 4 ottobre 2021 alle 17:24:35 UTC+2 tke...@gmail.com ha 
>> scritto:
>>
>>> Hello, and welcome to weewx.
>>>
>>> I don't know what I'm looking at. What do the red lines mean?
>>>
>>> What do you mean by you merged "the old database with the new one"? 
>>> There is no difference between the wview and weewx databases. You should be 
>>> able to just copy over the old database to the weewx installation.
>>>
>>> Did you read the section *Compatibility with wview 
>>> * in the 
>>> User's Guide?
>>>
>>> On Mon, Oct 4, 2021 at 8:18 AM kha...@gmail.com  
>>> wrote:
>>>
 Hello,
 until to late 2017 i used wview and then weewx.
 When i switched to weewx i merged the old database with the new one.
 This unfortunately doesn't works correctly.
 Now i'd like to recover the old data (database is very big, more than 
 170mb).
 Checking the differences between the two DB,  biggest difference seems 
 the decimal. 
 Could be the problem?
 Is possibile to fix it?
 Thanks in advance!

 -- 
 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/fb76f0f2-cc79-4b2a-ae16-c058caa848f4n%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/2ed5326b-8f0c-41b4-be8e-74c25bc048f0n%40googlegroups.com.

Re: [weewx-user] Database merged - Wview e weewx

[kha...@gmail.com]

Thank u so much...
Now i understand how to fix it.

Using database binding 'wx_binding', which is bound to database 
'archive_sqlite'
All daily summaries will be rebuilt.
Proceed (y/n)? y
Rebuilding daily summaries in database 'weewx.sdb' ...
Records processed: 793000; time: 2021-11-08 07:35:00 CET (1636353300))
Processed 793105 records to rebuild 2811 daily summaries in 73.69 seconds
Rebuild of daily summaries in database 'weewx.sdb' complete

:)

Il giorno giovedì 21 ottobre 2021 alle 13:23:30 UTC+2 itec ha scritto:

> Hi.
> What do you mean for "This unfortunately doesn't works correctly."? What's 
> wrong?
> I think that decimals are not important.
> Have you tried to run "wee_database --drop-daily" and "wee_database 
> --rebuild-daily"?
> Then delete /var/www/html/weewx/ and run "wee_reports" to regenerate all 
> reports
>
> Il giorno domenica 10 ottobre 2021 alle 22:05:50 UTC+2 kha...@gmail.com 
> ha scritto:
>
>> hi,
>> when i started to use weewx i used a new database. Few months later i 
>> merged two database.
>>
>> Il giorno lunedì 4 ottobre 2021 alle 17:24:35 UTC+2 tke...@gmail.com ha 
>> scritto:
>>
>>> Hello, and welcome to weewx.
>>>
>>> I don't know what I'm looking at. What do the red lines mean?
>>>
>>> What do you mean by you merged "the old database with the new one"? 
>>> There is no difference between the wview and weewx databases. You should be 
>>> able to just copy over the old database to the weewx installation.
>>>
>>> Did you read the section *Compatibility with wview 
>>> * in the 
>>> User's Guide?
>>>
>>> On Mon, Oct 4, 2021 at 8:18 AM kha...@gmail.com  
>>> wrote:
>>>
 Hello,
 until to late 2017 i used wview and then weewx.
 When i switched to weewx i merged the old database with the new one.
 This unfortunately doesn't works correctly.
 Now i'd like to recover the old data (database is very big, more than 
 170mb).
 Checking the differences between the two DB,  biggest difference seems 
 the decimal. 
 Could be the problem?
 Is possibile to fix it?
 Thanks in advance!

 -- 
 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/fb76f0f2-cc79-4b2a-ae16-c058caa848f4n%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/07b27216-e358-4bd0-8978-830bfbbcca59n%40googlegroups.com.

[weewx-user] NULL data from some values with WeatherFlow

[Mauro De Lauretis]

Hi All

I was wondering If somebody could help me by finding out why I get NULL daa 
from some values from my WeatherFlow. Wind Data is the only I get without 
problems. This is my weewx.conf:

[WeatherFlowUDP]

driver = user.weatherflowudp

log_raw_packets = False

udp_address = 

# udp_address = 0.0.0.0

# udp_address = 255.255.255.255

udp_port = 50222

udp_timeout = 90

share_socket = True


[[sensor_map]]

outTemp = air_temperature.ST-0048481.obs_air

outHumidity = relative_humidity.ST-00048481.obs_air

pressure =  station_pressure.ST-00048481.obs_air

lightning_strikes =  lightning_strike_count.ST-00048481.obs_air

avg_distance =  lightning_strike_avg_distance.ST-00048481.obs_air

outTempBatteryStatus =  battery.ST-00048481.obs_air

windSpeed = wind_speed.ST-00048481.rapid_wind

windDir = wind_direction.ST-00048481.rapid_wind

lux = illuminance.ST-00048481.obs_sky

UV = uv.ST-00048481.obs_sky

rain = rain_accumulated.ST-00048481.obs_sky

windBatteryStatus = battery.ST-00048481.obs_sky

radiation = solar_radiation.ST-00048481.obs_sky

lightningYYY = distance.ST-00048481.evt_strike

lightningZZZ = energy.ST-00048481.evt_strike



Greetings

-- 
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/7fbf26e4-51f0-4787-9121-afe04c1ecac6n%40googlegroups.com.

[weewx-user] Re: NULL data from some values with WeatherFlow

[vince]

You're going to have to tell us 'which' items have null values, but the WF 
gear does back off on which sensors it reports on (and how often) as the 
battery voltage gets low.  Perhaps your gear is in a degrading state.   
Check your WF app for the voltage and perhaps open a support call via their 
forums.

On Monday, November 8, 2021 at 8:07:22 AM UTC-8 Mauro De Lauretis wrote:

> Hi All
>
> I was wondering If somebody could help me by finding out why I get NULL 
> daa from some values from my WeatherFlow. Wind Data is the only I get 
> without problems. This is my weewx.conf:
>
> [WeatherFlowUDP]
>
> driver = user.weatherflowudp
>
> log_raw_packets = False
>
> udp_address = 
>
> # udp_address = 0.0.0.0
>
> # udp_address = 255.255.255.255
>
> udp_port = 50222
>
> udp_timeout = 90
>
> share_socket = True
>
>
> [[sensor_map]]
>
> outTemp = air_temperature.ST-0048481.obs_air
>
> outHumidity = relative_humidity.ST-00048481.obs_air
>
> pressure =  station_pressure.ST-00048481.obs_air
>
> lightning_strikes =  lightning_strike_count.ST-00048481.obs_air
>
> avg_distance =  lightning_strike_avg_distance.ST-00048481.obs_air
>
> outTempBatteryStatus =  battery.ST-00048481.obs_air
>
> windSpeed = wind_speed.ST-00048481.rapid_wind
>
> windDir = wind_direction.ST-00048481.rapid_wind
>
> lux = illuminance.ST-00048481.obs_sky
>
> UV = uv.ST-00048481.obs_sky
>
> rain = rain_accumulated.ST-00048481.obs_sky
>
> windBatteryStatus = battery.ST-00048481.obs_sky
>
> radiation = solar_radiation.ST-00048481.obs_sky
>
> lightningYYY = distance.ST-00048481.evt_strike
>
> lightningZZZ = energy.ST-00048481.evt_strike
>
>
>
> Greetings
>

-- 
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/6c13907f-a91b-4e88-9d75-b1c52e511feen%40googlegroups.com.

[weewx-user] Re: NULL data from some values with WeatherFlow

[Mauro De Lauretis]

Hi Vince

Thank you for your answer.
The only values I get are the following:

- maxSolarRad
- windDir
- windGust
- windGustDir
- windrun
- windSpeed

I don't think my gear is in a degrading state because the WF was bought in 
December 2020 and the unit itself has been exchanged on warranty just once 
month ago.
The Battery Voltage is 2.56 volts at the moment.

Greetings
Il giorno lunedì 8 novembre 2021 alle 18:15:18 UTC+1 vince ha scritto:

> You're going to have to tell us 'which' items have null values, but the WF 
> gear does back off on which sensors it reports on (and how often) as the 
> battery voltage gets low.  Perhaps your gear is in a degrading state.   
> Check your WF app for the voltage and perhaps open a support call via their 
> forums.
>
> On Monday, November 8, 2021 at 8:07:22 AM UTC-8 Mauro De Lauretis wrote:
>
>> Hi All
>>
>> I was wondering If somebody could help me by finding out why I get NULL 
>> daa from some values from my WeatherFlow. Wind Data is the only I get 
>> without problems. This is my weewx.conf:
>>
>> [WeatherFlowUDP]
>>
>> driver = user.weatherflowudp
>>
>> log_raw_packets = False
>>
>> udp_address = 
>>
>> # udp_address = 0.0.0.0
>>
>> # udp_address = 255.255.255.255
>>
>> udp_port = 50222
>>
>> udp_timeout = 90
>>
>> share_socket = True
>>
>>
>> [[sensor_map]]
>>
>> outTemp = air_temperature.ST-0048481.obs_air
>>
>> outHumidity = relative_humidity.ST-00048481.obs_air
>>
>> pressure =  station_pressure.ST-00048481.obs_air
>>
>> lightning_strikes =  lightning_strike_count.ST-00048481.obs_air
>>
>> avg_distance =  lightning_strike_avg_distance.ST-00048481.obs_air
>>
>> outTempBatteryStatus =  battery.ST-00048481.obs_air
>>
>> windSpeed = wind_speed.ST-00048481.rapid_wind
>>
>> windDir = wind_direction.ST-00048481.rapid_wind
>>
>> lux = illuminance.ST-00048481.obs_sky
>>
>> UV = uv.ST-00048481.obs_sky
>>
>> rain = rain_accumulated.ST-00048481.obs_sky
>>
>> windBatteryStatus = battery.ST-00048481.obs_sky
>>
>> radiation = solar_radiation.ST-00048481.obs_sky
>>
>> lightningYYY = distance.ST-00048481.evt_strike
>>
>> lightningZZZ = energy.ST-00048481.evt_strike
>>
>>
>>
>> Greetings
>>
>

-- 
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/177de093-cfb8-41b1-9005-f716c5bba5b6n%40googlegroups.com.

[weewx-user] Re: NULL data from some values with WeatherFlow

[vince]

maxSolarRad is calculated by weewx, so it sounds like only your wind sensor 
is working unless you typo'd something in weewx.conf.

Voltage looks good. You might have temp+hum sensors that failed but before 
contacting WF again you could check yourself pretty easily.

   - run weewx interactively to see its loop packets (users guide link) 
   
   - or alternately stop weewx and run my UDP listener (github link) 
    with the --raw 
   option to see what the Hub is broadcasting without weewx in the game at 
   least temporarily.   You can run my listener with weewx running if you have 
   share_socket=true in weewx for the UDP driver.
   
Doing a little diagnosis before contacting WF support will probably help 
them out either way.

On Monday, November 8, 2021 at 9:38:19 AM UTC-8 Mauro De Lauretis wrote:

>
> Hi Vince
>
> Thank you for your answer.
> The only values I get are the following:
>
> - maxSolarRad
> - windDir
> - windGust
> - windGustDir
> - windrun
> - windSpeed
>
> I don't think my gear is in a degrading state because the WF was bought in 
> December 2020 and the unit itself has been exchanged on warranty just once 
> month ago.
> The Battery Voltage is 2.56 volts at the moment.
>
> Greetings
> Il giorno lunedì 8 novembre 2021 alle 18:15:18 UTC+1 vince ha scritto:
>
>> You're going to have to tell us 'which' items have null values, but the 
>> WF gear does back off on which sensors it reports on (and how often) as the 
>> battery voltage gets low.  Perhaps your gear is in a degrading state.   
>> Check your WF app for the voltage and perhaps open a support call via their 
>> forums.
>>
>> On Monday, November 8, 2021 at 8:07:22 AM UTC-8 Mauro De Lauretis wrote:
>>
>>> Hi All
>>>
>>> I was wondering If somebody could help me by finding out why I get NULL 
>>> daa from some values from my WeatherFlow. Wind Data is the only I get 
>>> without problems. This is my weewx.conf:
>>>
>>> [WeatherFlowUDP]
>>>
>>> driver = user.weatherflowudp
>>>
>>> log_raw_packets = False
>>>
>>> udp_address = 
>>>
>>> # udp_address = 0.0.0.0
>>>
>>> # udp_address = 255.255.255.255
>>>
>>> udp_port = 50222
>>>
>>> udp_timeout = 90
>>>
>>> share_socket = True
>>>
>>>
>>> [[sensor_map]]
>>>
>>> outTemp = air_temperature.ST-0048481.obs_air
>>>
>>> outHumidity = relative_humidity.ST-00048481.obs_air
>>>
>>> pressure =  station_pressure.ST-00048481.obs_air
>>>
>>> lightning_strikes =  lightning_strike_count.ST-00048481.obs_air
>>>
>>> avg_distance =  lightning_strike_avg_distance.ST-00048481.obs_air
>>>
>>> outTempBatteryStatus =  battery.ST-00048481.obs_air
>>>
>>> windSpeed = wind_speed.ST-00048481.rapid_wind
>>>
>>> windDir = wind_direction.ST-00048481.rapid_wind
>>>
>>> lux = illuminance.ST-00048481.obs_sky
>>>
>>> UV = uv.ST-00048481.obs_sky
>>>
>>> rain = rain_accumulated.ST-00048481.obs_sky
>>>
>>> windBatteryStatus = battery.ST-00048481.obs_sky
>>>
>>> radiation = solar_radiation.ST-00048481.obs_sky
>>>
>>> lightningYYY = distance.ST-00048481.evt_strike
>>>
>>> lightningZZZ = energy.ST-00048481.evt_strike
>>>
>>>
>>>
>>> Greetings
>>>
>>

-- 
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/1b7d3e1a-b597-4a87-ac4a-10f905f26f3cn%40googlegroups.com.

[weewx-user] Re: NULL data from some values with WeatherFlow

[Mauro De Lauretis]

Yes, I was thinking the same.

These are the loop packets by running interactively:

LOOP:   2021-11-08 20:15:12 CET (1636398912) dateTime: 1636398912, 
maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 245, windSpeed: 5.292

LOOP:   2021-11-08 20:15:15 CET (1636398915) dateTime: 1636398915, 
maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 247, windSpeed: 5.076

LOOP:   2021-11-08 20:15:18 CET (1636398918) dateTime: 1636398918, 
maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 247, windSpeed: 5.04

LOOP:   2021-11-08 20:15:21 CET (1636398921) dateTime: 1636398921, 
maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 252, windSpeed: 4.068


By using your tool:

hub_status =>  ts  = 1636400075 firmware_revision  = 171 uptime  = 
195702 rssi  = -52

rapid_wind =>  ts  = 1636400077 mps = 1.35 dir = 252

rapid_wind =>  ts  = 1636400080 mps = 1.34 dir = 251

rapid_wind =>rapid_wind =>  ts  = 1636400083 mps = 1.47 dir = 251

device_status  =>  serial_number  = ST-00048481 device_type = tempest ts  = 
1636400085 uptime  = 280025 voltage  = 2.561 firmware_revision  = 160 rssi  = 
-52 hub_rssi  = -50 sensor_status  = 131076 debug  = 0

obs_st=>  timestamp  = 1636400084 wind_lull  = 1.16 wind_avg  = 
1.41 wind_gust  = 1.68 wind_direction  = 248 wind_sample_interval  = 3 
station_pressure  = 1010.11 temperature  = 13.78 relative_humidity  = 95.59 
illuminance  = 0 uv  = 0.0 solar_radiation  = 0 rain_accumulated  = 
0.031985 precipitation_type  = 1 lightning_strike_avg_distance  = 0 
lightning_strike_count  = 0 battery = 2.561 report_interval = 1 
firmware_revision = 160

-

raw data:  {"hub_sn": "HB-00034777", "ob": [1636400278, 1.88, 233], 
"serial_number": "ST-00048481", "type": "rapid_wind"}

raw data:  {"hub_sn": "HB-00034777", "ob": [1636400281, 2.2, 233], 
"serial_number": "ST-00048481", "type": "rapid_wind"}

raw data:  {"hub_sn": "HB-00034777", "ob": [1636400284, 1.93, 235], 
"serial_number": "ST-00048481", "type": "rapid_wind"}

raw data:  {"firmware_revision": "171", "fs": [1, 0, 15675411, 524288], 
"mqtt_stats": [119, 4], "radio_stats": [25, 1, 0, 3, 16961], "reset_flags": 
"BOR,PIN,POR", "rssi": -57, "seq": 19573, "serial_number": "HB-00034777", 
"timestamp": 1636400285, "type": "hub_status", "uptime": 195912}






Il giorno lunedì 8 novembre 2021 alle 19:49:48 UTC+1 vince ha scritto:

> maxSolarRad is calculated by weewx, so it sounds like only your wind 
> sensor is working unless you typo'd something in weewx.conf.
>
> Voltage looks good. You might have temp+hum sensors that failed but before 
> contacting WF again you could check yourself pretty easily.
>
>- run weewx interactively to see its loop packets (users guide link) 
>
>- or alternately stop weewx and run my UDP listener (github link) 
> with the 
>--raw option to see what the Hub is broadcasting without weewx in the game 
>at least temporarily.   You can run my listener with weewx running if you 
>have share_socket=true in weewx for the UDP driver.
>
> Doing a little diagnosis before contacting WF support will probably help 
> them out either way.
>
> On Monday, November 8, 2021 at 9:38:19 AM UTC-8 Mauro De Lauretis wrote:
>
>>
>> Hi Vince
>>
>> Thank you for your answer.
>> The only values I get are the following:
>>
>> - maxSolarRad
>> - windDir
>> - windGust
>> - windGustDir
>> - windrun
>> - windSpeed
>>
>> I don't think my gear is in a degrading state because the WF was bought 
>> in December 2020 and the unit itself has been exchanged on warranty just 
>> once month ago.
>> The Battery Voltage is 2.56 volts at the moment.
>>
>> Greetings
>> Il giorno lunedì 8 novembre 2021 alle 18:15:18 UTC+1 vince ha scritto:
>>
>>> You're going to have to tell us 'which' items have null values, but the 
>>> WF gear does back off on which sensors it reports on (and how often) as the 
>>> battery voltage gets low.  Perhaps your gear is in a degrading state.   
>>> Check your WF app for the voltage and perhaps open a support call via their 
>>> forums.
>>>
>>> On Monday, November 8, 2021 at 8:07:22 AM UTC-8 Mauro De Lauretis wrote:
>>>
 Hi All

 I was wondering If somebody could help me by finding out why I get NULL 
 daa from some values from my WeatherFlow. Wind Data is the only I get 
 without problems. This is my weewx.conf:

 [WeatherFlowUDP]

 driver = user.weatherflowudp

 log_raw_packets = False

 udp_address = 

 # udp_address = 0.0.0.0

 # udp_address = 255.255.255.255

 udp_port = 50222

 udp_timeout = 90

 share_socket = True


 [[sensor_map]]

 outTemp = air_temperature.ST-0048481.obs_air

 outHumidity = relative_humidity.ST-00048481.obs_air

 pre

[weewx-user] Re: NULL data from some values with WeatherFlow

[vince]

Hmmm - your obs_st shows wind,temperature, humidity, pressure but no UV or 
radiation but the sensor status looks like the uv/light sensor is failed.   
Definitely contact WF support.

sensor_status  = 131076 = binary 100100 - the leading '1' means 
light sensor failed according to sensor_status 
on https://weatherflow.github.io/Tempest/api/udp/v171/ 



On Monday, November 8, 2021 at 11:38:54 AM UTC-8 Mauro De Lauretis wrote:

> Yes, I was thinking the same.
>
> These are the loop packets by running interactively:
>
> LOOP:   2021-11-08 20:15:12 CET (1636398912) dateTime: 1636398912, 
> maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 245, windSpeed: 5.292
>
> LOOP:   2021-11-08 20:15:15 CET (1636398915) dateTime: 1636398915, 
> maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 247, windSpeed: 5.076
>
> LOOP:   2021-11-08 20:15:18 CET (1636398918) dateTime: 1636398918, 
> maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 247, windSpeed: 5.04
>
> LOOP:   2021-11-08 20:15:21 CET (1636398921) dateTime: 1636398921, 
> maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 252, windSpeed: 4.068
>
>
> By using your tool:
>
> hub_status =>  ts  = 1636400075 firmware_revision  = 171 uptime  = 
> 195702 rssi  = -52
>
> rapid_wind =>  ts  = 1636400077 mps = 1.35 dir = 252
>
> rapid_wind =>  ts  = 1636400080 mps = 1.34 dir = 251
>
> rapid_wind =>rapid_wind =>  ts  = 1636400083 mps = 1.47 dir = 251
>
> device_status  =>  serial_number  = ST-00048481 device_type = tempest ts  = 
> 1636400085 uptime  = 280025 voltage  = 2.561 firmware_revision  = 160 rssi  
> = -52 hub_rssi  = -50 sensor_status  = 131076 debug  = 0
>
> obs_st=>  timestamp  = 1636400084 wind_lull  = 1.16 wind_avg  = 
> 1.41 wind_gust  = 1.68 wind_direction  = 248 wind_sample_interval  = 3 
> station_pressure  = 1010.11 temperature  = 13.78 relative_humidity  = 95.59 
> illuminance  = 0 uv  = 0.0 solar_radiation  = 0 rain_accumulated  = 
> 0.031985 precipitation_type  = 1 lightning_strike_avg_distance  = 0 
> lightning_strike_count  = 0 battery = 2.561 report_interval = 1 
> firmware_revision = 160
>
> -
>
> raw data:  {"hub_sn": "HB-00034777", "ob": [1636400278, 1.88, 233], 
> "serial_number": "ST-00048481", "type": "rapid_wind"}
>
> raw data:  {"hub_sn": "HB-00034777", "ob": [1636400281, 2.2, 233], 
> "serial_number": "ST-00048481", "type": "rapid_wind"}
>
> raw data:  {"hub_sn": "HB-00034777", "ob": [1636400284, 1.93, 235], 
> "serial_number": "ST-00048481", "type": "rapid_wind"}
>
> raw data:  {"firmware_revision": "171", "fs": [1, 0, 15675411, 
> 524288], "mqtt_stats": [119, 4], "radio_stats": [25, 1, 0, 3, 16961], 
> "reset_flags": "BOR,PIN,POR", "rssi": -57, "seq": 19573, "serial_number": 
> "HB-00034777", "timestamp": 1636400285, "type": "hub_status", "uptime": 
> 195912}
>
>
>
>
>
>
> Il giorno lunedì 8 novembre 2021 alle 19:49:48 UTC+1 vince ha scritto:
>
>> maxSolarRad is calculated by weewx, so it sounds like only your wind 
>> sensor is working unless you typo'd something in weewx.conf.
>>
>> Voltage looks good. You might have temp+hum sensors that failed but 
>> before contacting WF again you could check yourself pretty easily.
>>
>>- run weewx interactively to see its loop packets (users guide link) 
>>
>>- or alternately stop weewx and run my UDP listener (github link) 
>> with the 
>>--raw option to see what the Hub is broadcasting without weewx in the 
>> game 
>>at least temporarily.   You can run my listener with weewx running if you 
>>have share_socket=true in weewx for the UDP driver.
>>
>> Doing a little diagnosis before contacting WF support will probably help 
>> them out either way.
>>
>> On Monday, November 8, 2021 at 9:38:19 AM UTC-8 Mauro De Lauretis wrote:
>>
>>>
>>> Hi Vince
>>>
>>> Thank you for your answer.
>>> The only values I get are the following:
>>>
>>> - maxSolarRad
>>> - windDir
>>> - windGust
>>> - windGustDir
>>> - windrun
>>> - windSpeed
>>>
>>> I don't think my gear is in a degrading state because the WF was bought 
>>> in December 2020 and the unit itself has been exchanged on warranty just 
>>> once month ago.
>>> The Battery Voltage is 2.56 volts at the moment.
>>>
>>> Greetings
>>> Il giorno lunedì 8 novembre 2021 alle 18:15:18 UTC+1 vince ha scritto:
>>>
 You're going to have to tell us 'which' items have null values, but the 
 WF gear does back off on which sensors it reports on (and how often) as 
 the 
 battery voltage gets low.  Perhaps your gear is in a degrading state.   
 Check your WF app for the voltage and perhaps open a support call via 
 their 
 forums.

 On Monday, November 8, 2021 at 8:07:22 AM UTC-8 Mauro De Lauretis wrote:

> Hi All
>
> I was wondering If somebody could help me by finding out why I get 
> NULL daa fr

[weewx-user] Re: NULL data from some values with WeatherFlow

[Mauro De Lauretis]

Vince, I got the problem.

I needed to change the sensor map from Air to Tempest by replacing the 
obs_air to obs_st :-)
If I take a look into my database now I have following values:

- altimeter
- appTemp
- barometer
- cloudbase
- dewpoint
- humidex
- outHumidity
- outTemp
- outTempBatteryStatus
- pressure
- radiation
- rain
- rainRate
- UV 
- Wind (inl. Gust and Wind Run)


The only lightning is showing "NULL"


Il giorno lunedì 8 novembre 2021 alle 21:26:35 UTC+1 vince ha scritto:

> Hmmm - your obs_st shows wind,temperature, humidity, pressure but no UV or 
> radiation but the sensor status looks like the uv/light sensor is failed.   
> Definitely contact WF support.
>
> sensor_status  = 131076 = binary 100100 - the leading '1' 
> means light sensor failed according to sensor_status on 
> https://weatherflow.github.io/Tempest/api/udp/v171/ 
>
>
>
> On Monday, November 8, 2021 at 11:38:54 AM UTC-8 Mauro De Lauretis wrote:
>
>> Yes, I was thinking the same.
>>
>> These are the loop packets by running interactively:
>>
>> LOOP:   2021-11-08 20:15:12 CET (1636398912) dateTime: 1636398912, 
>> maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 245, windSpeed: 5.292
>>
>> LOOP:   2021-11-08 20:15:15 CET (1636398915) dateTime: 1636398915, 
>> maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 247, windSpeed: 5.076
>>
>> LOOP:   2021-11-08 20:15:18 CET (1636398918) dateTime: 1636398918, 
>> maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 247, windSpeed: 5.04
>>
>> LOOP:   2021-11-08 20:15:21 CET (1636398921) dateTime: 1636398921, 
>> maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 252, windSpeed: 4.068
>>
>>
>> By using your tool:
>>
>> hub_status =>  ts  = 1636400075 firmware_revision  = 171 uptime  = 
>> 195702 rssi  = -52
>>
>> rapid_wind =>  ts  = 1636400077 mps = 1.35 dir = 252
>>
>> rapid_wind =>  ts  = 1636400080 mps = 1.34 dir = 251
>>
>> rapid_wind =>rapid_wind =>  ts  = 1636400083 mps = 1.47 dir = 251
>>
>> device_status  =>  serial_number  = ST-00048481 device_type = tempest ts  
>> = 1636400085 uptime  = 280025 voltage  = 2.561 firmware_revision  = 160 
>> rssi  = -52 hub_rssi  = -50 sensor_status  = 131076 debug  = 0
>>
>> obs_st=>  timestamp  = 1636400084 wind_lull  = 1.16 wind_avg  = 
>> 1.41 wind_gust  = 1.68 wind_direction  = 248 wind_sample_interval  = 3 
>> station_pressure  = 1010.11 temperature  = 13.78 relative_humidity  = 95.59 
>> illuminance  = 0 uv  = 0.0 solar_radiation  = 0 rain_accumulated  = 
>> 0.031985 precipitation_type  = 1 lightning_strike_avg_distance  = 0 
>> lightning_strike_count  = 0 battery = 2.561 report_interval = 1 
>> firmware_revision = 160
>>
>> -
>>
>> raw data:  {"hub_sn": "HB-00034777", "ob": [1636400278, 1.88, 233], 
>> "serial_number": "ST-00048481", "type": "rapid_wind"}
>>
>> raw data:  {"hub_sn": "HB-00034777", "ob": [1636400281, 2.2, 233], 
>> "serial_number": "ST-00048481", "type": "rapid_wind"}
>>
>> raw data:  {"hub_sn": "HB-00034777", "ob": [1636400284, 1.93, 235], 
>> "serial_number": "ST-00048481", "type": "rapid_wind"}
>>
>> raw data:  {"firmware_revision": "171", "fs": [1, 0, 15675411, 
>> 524288], "mqtt_stats": [119, 4], "radio_stats": [25, 1, 0, 3, 16961], 
>> "reset_flags": "BOR,PIN,POR", "rssi": -57, "seq": 19573, "serial_number": 
>> "HB-00034777", "timestamp": 1636400285, "type": "hub_status", "uptime": 
>> 195912}
>>
>>
>>
>>
>>
>>
>> Il giorno lunedì 8 novembre 2021 alle 19:49:48 UTC+1 vince ha scritto:
>>
>>> maxSolarRad is calculated by weewx, so it sounds like only your wind 
>>> sensor is working unless you typo'd something in weewx.conf.
>>>
>>> Voltage looks good. You might have temp+hum sensors that failed but 
>>> before contacting WF again you could check yourself pretty easily.
>>>
>>>- run weewx interactively to see its loop packets (users guide link) 
>>>
>>>- or alternately stop weewx and run my UDP listener (github link) 
>>> with the 
>>>--raw option to see what the Hub is broadcasting without weewx in the 
>>> game 
>>>at least temporarily.   You can run my listener with weewx running if 
>>> you 
>>>have share_socket=true in weewx for the UDP driver.
>>>
>>> Doing a little diagnosis before contacting WF support will probably help 
>>> them out either way.
>>>
>>> On Monday, November 8, 2021 at 9:38:19 AM UTC-8 Mauro De Lauretis wrote:
>>>

 Hi Vince

 Thank you for your answer.
 The only values I get are the following:

 - maxSolarRad
 - windDir
 - windGust
 - windGustDir
 - windrun
 - windSpeed

 I don't think my gear is in a degrading state because the WF was bought 
 in December 2020 and the unit itself has been exchanged on warranty just 
 once month ago.
 The Battery Voltage is 2.56 volts at the moment.

 Greetings

[weewx-user] Re: NULL data from some values with WeatherFlow

[vince]

That's funny.  I totally missed seeing that when I was looking to see if 
you typo'd the serial number :-)

On Monday, November 8, 2021 at 1:06:24 PM UTC-8 Mauro De Lauretis wrote:

> Vince, I got the problem.
>
> I needed to change the sensor map from Air to Tempest by replacing the 
> obs_air to obs_st :-)
> If I take a look into my database now I have following values:
>
> - altimeter
> - appTemp
> - barometer
> - cloudbase
> - dewpoint
> - humidex
> - outHumidity
> - outTemp
> - outTempBatteryStatus
> - pressure
> - radiation
> - rain
> - rainRate
> - UV 
> - Wind (inl. Gust and Wind Run)
>
>
> The only lightning is showing "NULL"
>
>
> Il giorno lunedì 8 novembre 2021 alle 21:26:35 UTC+1 vince ha scritto:
>
>> Hmmm - your obs_st shows wind,temperature, humidity, pressure but no UV 
>> or radiation but the sensor status looks like the uv/light sensor is 
>> failed.   Definitely contact WF support.
>>
>> sensor_status  = 131076 = binary 100100 - the leading '1' 
>> means light sensor failed according to sensor_status on 
>> https://weatherflow.github.io/Tempest/api/udp/v171/ 
>>
>>
>>
>> On Monday, November 8, 2021 at 11:38:54 AM UTC-8 Mauro De Lauretis wrote:
>>
>>> Yes, I was thinking the same.
>>>
>>> These are the loop packets by running interactively:
>>>
>>> LOOP:   2021-11-08 20:15:12 CET (1636398912) dateTime: 1636398912, 
>>> maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 245, windSpeed: 5.292
>>>
>>> LOOP:   2021-11-08 20:15:15 CET (1636398915) dateTime: 1636398915, 
>>> maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 247, windSpeed: 5.076
>>>
>>> LOOP:   2021-11-08 20:15:18 CET (1636398918) dateTime: 1636398918, 
>>> maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 247, windSpeed: 5.04
>>>
>>> LOOP:   2021-11-08 20:15:21 CET (1636398921) dateTime: 1636398921, 
>>> maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 252, windSpeed: 4.068
>>>
>>>
>>> By using your tool:
>>>
>>> hub_status =>  ts  = 1636400075 firmware_revision  = 171 uptime  = 
>>> 195702 rssi  = -52
>>>
>>> rapid_wind =>  ts  = 1636400077 mps = 1.35 dir = 252
>>>
>>> rapid_wind =>  ts  = 1636400080 mps = 1.34 dir = 251
>>>
>>> rapid_wind =>rapid_wind =>  ts  = 1636400083 mps = 1.47 dir = 
>>> 251
>>>
>>> device_status  =>  serial_number  = ST-00048481 device_type = tempest ts  
>>> = 1636400085 uptime  = 280025 voltage  = 2.561 firmware_revision  = 160 
>>> rssi  = -52 hub_rssi  = -50 sensor_status  = 131076 debug  = 0
>>>
>>> obs_st=>  timestamp  = 1636400084 wind_lull  = 1.16 wind_avg  = 
>>> 1.41 wind_gust  = 1.68 wind_direction  = 248 wind_sample_interval  = 3 
>>> station_pressure  = 1010.11 temperature  = 13.78 relative_humidity  = 95.59 
>>> illuminance  = 0 uv  = 0.0 solar_radiation  = 0 rain_accumulated  = 
>>> 0.031985 precipitation_type  = 1 lightning_strike_avg_distance  = 0 
>>> lightning_strike_count  = 0 battery = 2.561 report_interval = 1 
>>> firmware_revision = 160
>>>
>>> -
>>>
>>> raw data:  {"hub_sn": "HB-00034777", "ob": [1636400278, 1.88, 233], 
>>> "serial_number": "ST-00048481", "type": "rapid_wind"}
>>>
>>> raw data:  {"hub_sn": "HB-00034777", "ob": [1636400281, 2.2, 233], 
>>> "serial_number": "ST-00048481", "type": "rapid_wind"}
>>>
>>> raw data:  {"hub_sn": "HB-00034777", "ob": [1636400284, 1.93, 235], 
>>> "serial_number": "ST-00048481", "type": "rapid_wind"}
>>>
>>> raw data:  {"firmware_revision": "171", "fs": [1, 0, 15675411, 
>>> 524288], "mqtt_stats": [119, 4], "radio_stats": [25, 1, 0, 3, 16961], 
>>> "reset_flags": "BOR,PIN,POR", "rssi": -57, "seq": 19573, "serial_number": 
>>> "HB-00034777", "timestamp": 1636400285, "type": "hub_status", "uptime": 
>>> 195912}
>>>
>>>
>>>
>>>
>>>
>>>
>>> Il giorno lunedì 8 novembre 2021 alle 19:49:48 UTC+1 vince ha scritto:
>>>
 maxSolarRad is calculated by weewx, so it sounds like only your wind 
 sensor is working unless you typo'd something in weewx.conf.

 Voltage looks good. You might have temp+hum sensors that failed but 
 before contacting WF again you could check yourself pretty easily.

- run weewx interactively to see its loop packets (users guide link) 

- or alternately stop weewx and run my UDP listener (github link) 
 with the 
--raw option to see what the Hub is broadcasting without weewx in the 
 game 
at least temporarily.   You can run my listener with weewx running if 
 you 
have share_socket=true in weewx for the UDP driver.

 Doing a little diagnosis before contacting WF support will probably 
 help them out either way.

 On Monday, November 8, 2021 at 9:38:19 AM UTC-8 Mauro De Lauretis wrote:

>
> Hi Vince
>
> Thank you for your answer.
> The only values I get are the following:
>
> - maxSolarRad
>>>

[weewx-user] Re: NULL data from some values with WeatherFlow

[Mauro De Lauretis]

No problem! Thank you anyway for your help :-)

Il giorno lunedì 8 novembre 2021 alle 22:32:14 UTC+1 vince ha scritto:

> That's funny.  I totally missed seeing that when I was looking to see if 
> you typo'd the serial number :-)
>
> On Monday, November 8, 2021 at 1:06:24 PM UTC-8 Mauro De Lauretis wrote:
>
>> Vince, I got the problem.
>>
>> I needed to change the sensor map from Air to Tempest by replacing the 
>> obs_air to obs_st :-)
>> If I take a look into my database now I have following values:
>>
>> - altimeter
>> - appTemp
>> - barometer
>> - cloudbase
>> - dewpoint
>> - humidex
>> - outHumidity
>> - outTemp
>> - outTempBatteryStatus
>> - pressure
>> - radiation
>> - rain
>> - rainRate
>> - UV 
>> - Wind (inl. Gust and Wind Run)
>>
>>
>> The only lightning is showing "NULL"
>>
>>
>> Il giorno lunedì 8 novembre 2021 alle 21:26:35 UTC+1 vince ha scritto:
>>
>>> Hmmm - your obs_st shows wind,temperature, humidity, pressure but no UV 
>>> or radiation but the sensor status looks like the uv/light sensor is 
>>> failed.   Definitely contact WF support.
>>>
>>> sensor_status  = 131076 = binary 100100 - the leading '1' 
>>> means light sensor failed according to sensor_status on 
>>> https://weatherflow.github.io/Tempest/api/udp/v171/ 
>>>
>>>
>>>
>>> On Monday, November 8, 2021 at 11:38:54 AM UTC-8 Mauro De Lauretis wrote:
>>>
 Yes, I was thinking the same.

 These are the loop packets by running interactively:

 LOOP:   2021-11-08 20:15:12 CET (1636398912) dateTime: 1636398912, 
 maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 245, windSpeed: 
 5.292

 LOOP:   2021-11-08 20:15:15 CET (1636398915) dateTime: 1636398915, 
 maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 247, windSpeed: 
 5.076

 LOOP:   2021-11-08 20:15:18 CET (1636398918) dateTime: 1636398918, 
 maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 247, windSpeed: 5.04

 LOOP:   2021-11-08 20:15:21 CET (1636398921) dateTime: 1636398921, 
 maxSolarRad: 0.0, rainRate: 0.0, usUnits: 16, windDir: 252, windSpeed: 
 4.068


 By using your tool:

 hub_status =>  ts  = 1636400075 firmware_revision  = 171 uptime  = 
 195702 rssi  = -52

 rapid_wind =>  ts  = 1636400077 mps = 1.35 dir = 252

 rapid_wind =>  ts  = 1636400080 mps = 1.34 dir = 251

 rapid_wind =>rapid_wind =>  ts  = 1636400083 mps = 1.47 dir = 
 251

 device_status  =>  serial_number  = ST-00048481 device_type = tempest 
 ts  = 1636400085 uptime  = 280025 voltage  = 2.561 firmware_revision  = 
 160 rssi  = -52 hub_rssi  = -50 sensor_status  = 131076 debug  = 0

 obs_st=>  timestamp  = 1636400084 wind_lull  = 1.16 wind_avg  = 
 1.41 wind_gust  = 1.68 wind_direction  = 248 wind_sample_interval  = 3 
 station_pressure  = 1010.11 temperature  = 13.78 relative_humidity  = 
 95.59 
 illuminance  = 0 uv  = 0.0 solar_radiation  = 0 rain_accumulated  = 
 0.031985 precipitation_type  = 1 lightning_strike_avg_distance  = 0 
 lightning_strike_count  = 0 battery = 2.561 report_interval = 1 
 firmware_revision = 160

 -

 raw data:  {"hub_sn": "HB-00034777", "ob": [1636400278, 1.88, 233], 
 "serial_number": "ST-00048481", "type": "rapid_wind"}

 raw data:  {"hub_sn": "HB-00034777", "ob": [1636400281, 2.2, 233], 
 "serial_number": "ST-00048481", "type": "rapid_wind"}

 raw data:  {"hub_sn": "HB-00034777", "ob": [1636400284, 1.93, 
 235], "serial_number": "ST-00048481", "type": "rapid_wind"}

 raw data:  {"firmware_revision": "171", "fs": [1, 0, 15675411, 
 524288], "mqtt_stats": [119, 4], "radio_stats": [25, 1, 0, 3, 16961], 
 "reset_flags": "BOR,PIN,POR", "rssi": -57, "seq": 19573, "serial_number": 
 "HB-00034777", "timestamp": 1636400285, "type": "hub_status", "uptime": 
 195912}






 Il giorno lunedì 8 novembre 2021 alle 19:49:48 UTC+1 vince ha scritto:

> maxSolarRad is calculated by weewx, so it sounds like only your wind 
> sensor is working unless you typo'd something in weewx.conf.
>
> Voltage looks good. You might have temp+hum sensors that failed but 
> before contacting WF again you could check yourself pretty easily.
>
>- run weewx interactively to see its loop packets (users guide 
>link) 
>- or alternately stop weewx and run my UDP listener (github link) 
> with the 
>--raw option to see what the Hub is broadcasting without weewx in the 
> game 
>at least temporarily.   You can run my listener with weewx running if 
> you 
>have share_socket=true in weewx for the UDP driver.
>
> Doing a little diagnosis before contacting WF supp

Re: [weewx-user] Re: No AQI on Belchertown Skin

[Doug Jenkins]

No problem Chris! The site looks great and operates well on my side of the
world :)

Pat did mention that to get the webcam working, there is a specific comment
and commit you need to get from his GitHub. I would just go to his github
and search for it. He has it working on his site now and probably will have
the code for his release general release.

Good luck and good reporting!

Doug

On Wed, Oct 27, 2021 at 12:18 PM 'super zee' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Thanks Doug!  Your code worked like a charm.  Here is the current site.  I
> will keep adding the code from Pat to incorporate the web cam.
>
> Tempe AZ Weather Conditions 
>
> Chris Z
> WG7B
>
>
> On Saturday, October 23, 2021 at 10:13:13 PM UTC-7 super zee wrote:
>
>> Thanks Clifford.  Let me try cp -r
>>
>> Chris
>>
>>
>> On Thursday, October 21, 2021 at 7:52:28 AM UTC-7 Clifford Snow wrote:
>>
>>> On Thu, Oct 21, 2021 at 7:08 AM 'super zee' via weewx-user <
>>> weewx...@googlegroups.com> wrote:
>>>
 Okay thanks Doug.  Let me try it.
 If I want to backup copy my whole Belchertown folder, can I use cp
 /etc/weewx/skins/Belchertown /etc/weewx/skins/Belchertown-old  ?

 Will the cp command copy a whole folder to back it up?  Or is it just
 for files?

 I believe the copy command you want is cp -R
>>> /etc/weewx/skins/Belchertown /etc/weewx/skins/Belchertown-old
>>>
>>> The -R recursively copies all folders to the new location. See man cp
>>>
>>> Best,
>>> Clifford
>>> --
>>> @osm_washington
>>> www.snowandsnow.us
>>> OpenStreetMap: Maps with a human touch
>>>
>> --
> 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/85ffb56e-0d86-4a66-83e0-75c067ecf952n%40googlegroups.com
> 
> .
>


-- 
Thanks,

Doug Jenkins
Phone: 813.391.5686 | d...@dougjenkins.com | www.dougjenkins.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/CACC0i0y3GZsTSnxQRN%2BtfQqRTpJDi9DAV8QjGB_MXLRQdjP2aw%40mail.gmail.com.

[weewx-user] Belchertown Error - Any idea what is wrong?

[bchap...@gmail.com]

Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Main loop 
exiting. Shutting engine down.
Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Shutting down 
StdReport thread
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 
'user.belchertown.HighchartsJsonGenerator'
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  database is locked
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  Traceback (most recent call last):
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
File "/usr/share/weewx/weedb/sqlite.py", line 30, in guarded_fn
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  return fn(*args, **kwargs)
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
File "/usr/share/weewx/weedb/sqlite.py", line 219, in execute
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  return sqlite3.Cursor.execute(self, *args, **kwargs)
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  sqlite3.OperationalError: database is locked
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  During handling of the above exception, another exception occurred:
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  Traceback (most recent call last):
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  obj.start()
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  self.run()
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
File "/usr/share/weewx/user/belchertown.py", line 1550, in run
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  start_ts = archive.firstGoodStamp()
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/manager.py", line 247, in 
firstGoodStamp
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  _row = self.getSql("SELECT MIN(dateTime) FROM %s" % 
self.table_name)
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/manager.py", line 449, in getSql
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  _cursor.execute(sql, sqlargs)
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
File "/usr/share/weewx/weedb/sqlite.py", line 44, in guarded_fn
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  raise weedb.OperationalError(e)
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  weedb.OperationalError: database is locked
Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
  Generator terminated
Nov  8 18:53:45 raspberrypi weewx[5618] INFO user.gw1000: Gw1000Collector 
thread has been terminated
Nov  8 18:53:45 raspberrypi weewx[5618] CRITICAL __main__: Database 
OperationalError exception: database is locked
Nov  8 18:53:45 raspberrypi weewx[5618] CRITICAL __main__:   
Waiting 2 minutes then retrying...
Nov  8 18:55:45 raspberrypi weewx[5618] INFO __main__: retrying...

-- 
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/eb3c3a30-f13d-44cf-b859-f90bec27f7f1n%40googlegroups.com.

[weewx-user] Re: Belchertown Error - Any idea what is wrong?

[vince]

Your database is locked :-)

Typically this is when you're trying to do too much too fast on a very slow 
box like a pi-zero or the like.

On Monday, November 8, 2021 at 4:06:48 PM UTC-8 bchap...@gmail.com wrote:

> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Main loop 
> exiting. Shutting engine down.
> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Shutting down 
> StdReport thread
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: Caught 
> unrecoverable exception in generator 
> 'user.belchertown.HighchartsJsonGenerator'
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   database is locked
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   Traceback (most recent call last):
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weedb/sqlite.py", line 30, in guarded_fn
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   return fn(*args, **kwargs)
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weedb/sqlite.py", line 219, in execute
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   return sqlite3.Cursor.execute(self, *args, **kwargs)
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   sqlite3.OperationalError: database is locked
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   During handling of the above exception, another exception occurred:
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   Traceback (most recent call last):
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   obj.start()
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   self.run()
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
> File "/usr/share/weewx/user/belchertown.py", line 1550, in run
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   start_ts = archive.firstGoodStamp()
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/manager.py", line 247, in 
> firstGoodStamp
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   _row = self.getSql("SELECT MIN(dateTime) FROM %s" % 
> self.table_name)
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/manager.py", line 449, in getSql
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   _cursor.execute(sql, sqlargs)
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weedb/sqlite.py", line 44, in guarded_fn
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   raise weedb.OperationalError(e)
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   weedb.OperationalError: database is locked
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>   Generator terminated
> Nov  8 18:53:45 raspberrypi weewx[5618] INFO user.gw1000: Gw1000Collector 
> thread has been terminated
> Nov  8 18:53:45 raspberrypi weewx[5618] CRITICAL __main__: Database 
> OperationalError exception: database is locked
> Nov  8 18:53:45 raspberrypi weewx[5618] CRITICAL __main__:   
> Waiting 2 minutes then retrying...
> Nov  8 18:55:45 raspberrypi weewx[5618] INFO __main__: retrying...
>
>

-- 
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/005fa296-d595-4f83-9626-1d6f45ccf251n%40googlegroups.com.

Re: [weewx-user] Re: Belchertown Error - Any idea what is wrong?

[Tom Keffer]

Yes, tell us what computer you are using. Also, the operating system and
version.

On Mon, Nov 8, 2021 at 4:32 PM vince  wrote:

> Your database is locked :-)
>
> Typically this is when you're trying to do too much too fast on a very
> slow box like a pi-zero or the like.
>
> On Monday, November 8, 2021 at 4:06:48 PM UTC-8 bchap...@gmail.com wrote:
>
>> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Main loop
>> exiting. Shutting engine down.
>> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Shutting down
>> StdReport thread
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: Caught
>> unrecoverable exception in generator
>> 'user.belchertown.HighchartsJsonGenerator'
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>>   database is locked
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>>   Traceback (most recent call last):
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>> File "/usr/share/weewx/weedb/sqlite.py", line 30, in guarded_fn
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>>   return fn(*args, **kwargs)
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>> File "/usr/share/weewx/weedb/sqlite.py", line 219, in execute
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>>   return sqlite3.Cursor.execute(self, *args, **kwargs)
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>>   sqlite3.OperationalError: database is locked
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>> 
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>>   During handling of the above exception, another exception occurred:
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>> 
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>>   Traceback (most recent call last):
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>> File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>>   obj.start()
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>> File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>>   self.run()
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>> File "/usr/share/weewx/user/belchertown.py", line 1550, in run
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>>   start_ts = archive.firstGoodStamp()
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>> File "/usr/share/weewx/weewx/manager.py", line 247, in
>> firstGoodStamp
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>>   _row = self.getSql("SELECT MIN(dateTime) FROM %s" %
>> self.table_name)
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>> File "/usr/share/weewx/weewx/manager.py", line 449, in getSql
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>>   _cursor.execute(sql, sqlargs)
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>> File "/usr/share/weewx/weedb/sqlite.py", line 44, in guarded_fn
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>>   raise weedb.OperationalError(e)
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>>   weedb.OperationalError: database is locked
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>>   Generator terminated
>> Nov  8 18:53:45 raspberrypi weewx[5618] INFO user.gw1000: Gw1000Collector
>> thread has been terminated
>> Nov  8 18:53:45 raspberrypi weewx[5618] CRITICAL __main__: Database
>> OperationalError exception: database is locked
>> Nov  8 18:53:45 raspberrypi weewx[5618] CRITICAL __main__: 
>> Waiting 2 minutes then retrying...
>> Nov  8 18:55:45 raspberrypi weewx[5618] INFO __main__: retrying...
>>
>> --
> 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/005fa296-d595-4f83-9626-1d6f45ccf251n%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/

Re: [weewx-user] Re: Belchertown Error - Any idea what is wrong?

[bchap...@gmail.com]

Raspberry Pi 2 with raspbian buster

This runs in a cycle of approximately every 6 minutes.  Nothing else 
running on this machine.

On Monday, November 8, 2021 at 7:35:14 PM UTC-5 tke...@gmail.com wrote:

> Yes, tell us what computer you are using. Also, the operating system and 
> version.
>
> On Mon, Nov 8, 2021 at 4:32 PM vince  wrote:
>
>> Your database is locked :-)
>>
>> Typically this is when you're trying to do too much too fast on a very 
>> slow box like a pi-zero or the like.
>>
>> On Monday, November 8, 2021 at 4:06:48 PM UTC-8 bchap...@gmail.com wrote:
>>
>>> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Main loop 
>>> exiting. Shutting engine down.
>>> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Shutting down 
>>> StdReport thread
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: Caught 
>>> unrecoverable exception in generator 
>>> 'user.belchertown.HighchartsJsonGenerator'
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   database is locked
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   Traceback (most recent call last):
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine: File 
>>> "/usr/share/weewx/weedb/sqlite.py", line 30, in guarded_fn
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   return fn(*args, **kwargs)
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine: File 
>>> "/usr/share/weewx/weedb/sqlite.py", line 219, in execute
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   return sqlite3.Cursor.execute(self, 
>>> *args, **kwargs)
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   sqlite3.OperationalError: database is 
>>> locked
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   During handling of the above exception, 
>>> another exception occurred:
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   Traceback (most recent call last):
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine: File 
>>> "/usr/share/weewx/weewx/reportengine.py", line 196, in run
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   obj.start()
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine: File 
>>> "/usr/share/weewx/weewx/reportengine.py", line 281, in start
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   self.run()
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine: File 
>>> "/usr/share/weewx/user/belchertown.py", line 1550, in run
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   start_ts = archive.firstGoodStamp()
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine: File 
>>> "/usr/share/weewx/weewx/manager.py", line 247, in firstGoodStamp
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   _row = self.getSql("SELECT 
>>> MIN(dateTime) FROM %s" % self.table_name)
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine: File 
>>> "/usr/share/weewx/weewx/manager.py", line 449, in getSql
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   _cursor.execute(sql, sqlargs)
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine: File 
>>> "/usr/share/weewx/weedb/sqlite.py", line 44, in guarded_fn
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   raise weedb.OperationalError(e)
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   weedb.OperationalError: database is locked
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   Generator terminated
>>> Nov  8 18:53:45 raspberrypi weewx[5618] INFO user.gw1000: 
>>> Gw1000Collector thread has been terminated
>>> Nov  8 18:53:45 raspberrypi weewx[5618] CRITICAL __main__: Database 
>>> OperationalError exception: database is locked
>>> Nov  8 18:53:45 raspberrypi weewx[5618] CRITICAL __main__:   
>>> Waiting 2 minutes then retrying...
>>> Nov  8 18:55:45 raspberrypi weewx[5618] INFO __main__: retrying...
>>>
>>> -- 
>> 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 vi

Re: [weewx-user] Re: Belchertown Error - Any idea what is wrong?

[vince]

I bet if you turn Belchertown off (temporarily) and enable just the 
Standard or Seasons skin that it'll work just fine.

Sometimes you need to throw more compute at the problem.

On Monday, November 8, 2021 at 4:40:00 PM UTC-8 bchap...@gmail.com wrote:

> Raspberry Pi 2 with raspbian buster
>
> This runs in a cycle of approximately every 6 minutes.  Nothing else 
> running on this machine.
>
> On Monday, November 8, 2021 at 7:35:14 PM UTC-5 tke...@gmail.com wrote:
>
>> Yes, tell us what computer you are using. Also, the operating system and 
>> version.
>>
>> On Mon, Nov 8, 2021 at 4:32 PM vince  wrote:
>>
>>> Your database is locked :-)
>>>
>>> Typically this is when you're trying to do too much too fast on a very 
>>> slow box like a pi-zero or the like.
>>>
>>> On Monday, November 8, 2021 at 4:06:48 PM UTC-8 bchap...@gmail.com 
>>> wrote:
>>>
 Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Main loop 
 exiting. Shutting engine down.
 Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Shutting 
 down StdReport thread
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
 Caught unrecoverable exception in generator 
 'user.belchertown.HighchartsJsonGenerator'
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   database is locked
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   Traceback (most recent call last):
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine: File 
 "/usr/share/weewx/weedb/sqlite.py", line 30, in guarded_fn
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   return fn(*args, **kwargs)
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine: File 
 "/usr/share/weewx/weedb/sqlite.py", line 219, in execute
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   return sqlite3.Cursor.execute(self, 
 *args, **kwargs)
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   sqlite3.OperationalError: database is 
 locked
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   During handling of the above exception, 
 another exception occurred:
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   Traceback (most recent call last):
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine: File 
 "/usr/share/weewx/weewx/reportengine.py", line 196, in run
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   obj.start()
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine: File 
 "/usr/share/weewx/weewx/reportengine.py", line 281, in start
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   self.run()
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine: File 
 "/usr/share/weewx/user/belchertown.py", line 1550, in run
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   start_ts = archive.firstGoodStamp()
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine: File 
 "/usr/share/weewx/weewx/manager.py", line 247, in firstGoodStamp
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   _row = self.getSql("SELECT 
 MIN(dateTime) FROM %s" % self.table_name)
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine: File 
 "/usr/share/weewx/weewx/manager.py", line 449, in getSql
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   _cursor.execute(sql, sqlargs)
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine: File 
 "/usr/share/weewx/weedb/sqlite.py", line 44, in guarded_fn
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   raise weedb.OperationalError(e)
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   weedb.OperationalError: database is 
 locked
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   Generator terminated
 Nov  8 18:53:45 raspberrypi weewx[5618] INFO user.gw1000: 
 Gw1000Collector thread has been terminated
 Nov  8 18:53:45 raspberrypi weewx[5618] CRITICAL __main__: Database 
 OperationalError exception: database is locked
 Nov  8 18:53:45 raspberrypi weewx[5618] CRITICAL __main__:   

Re: [weewx-user] Re: Belchertown Error - Any idea what is wrong?

[gjr80]

Would like to see a more extensive log extract, I wouldn’t have though a 
RPi2 would have that much of a problem with just WeeWX and Belchertown 
using a GW1000.

Gary

On Tuesday, 9 November 2021 at 11:02:35 UTC+10 vince wrote:

> I bet if you turn Belchertown off (temporarily) and enable just the 
> Standard or Seasons skin that it'll work just fine.
>
> Sometimes you need to throw more compute at the problem.
>
> On Monday, November 8, 2021 at 4:40:00 PM UTC-8 bchap...@gmail.com wrote:
>
>> Raspberry Pi 2 with raspbian buster
>>
>> This runs in a cycle of approximately every 6 minutes.  Nothing else 
>> running on this machine.
>>
>> On Monday, November 8, 2021 at 7:35:14 PM UTC-5 tke...@gmail.com wrote:
>>
>>> Yes, tell us what computer you are using. Also, the operating system and 
>>> version.
>>>
>>> On Mon, Nov 8, 2021 at 4:32 PM vince  wrote:
>>>
 Your database is locked :-)

 Typically this is when you're trying to do too much too fast on a very 
 slow box like a pi-zero or the like.

 On Monday, November 8, 2021 at 4:06:48 PM UTC-8 bchap...@gmail.com 
 wrote:

> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Main loop 
> exiting. Shutting engine down.
> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Shutting 
> down StdReport thread
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
> Caught unrecoverable exception in generator 
> 'user.belchertown.HighchartsJsonGenerator'
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine:   database is locked
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine:   Traceback (most recent call last):
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine: File 
> "/usr/share/weewx/weedb/sqlite.py", line 30, in guarded_fn
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine:   return fn(*args, **kwargs)
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine: File 
> "/usr/share/weewx/weedb/sqlite.py", line 219, in execute
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine:   return sqlite3.Cursor.execute(self, 
> *args, **kwargs)
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine:   sqlite3.OperationalError: database is 
> locked
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine:   
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine:   During handling of the above exception, 
> another exception occurred:
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine:   
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine:   Traceback (most recent call last):
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine: File 
> "/usr/share/weewx/weewx/reportengine.py", line 196, in run
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine:   obj.start()
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine: File 
> "/usr/share/weewx/weewx/reportengine.py", line 281, in start
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine:   self.run()
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine: File 
> "/usr/share/weewx/user/belchertown.py", line 1550, in run
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine:   start_ts = archive.firstGoodStamp()
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine: File 
> "/usr/share/weewx/weewx/manager.py", line 247, in firstGoodStamp
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine:   _row = self.getSql("SELECT 
> MIN(dateTime) FROM %s" % self.table_name)
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine: File 
> "/usr/share/weewx/weewx/manager.py", line 449, in getSql
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine:   _cursor.execute(sql, sqlargs)
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine: File 
> "/usr/share/weewx/weedb/sqlite.py", line 44, in guarded_fn
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine:   raise weedb.OperationalError(e)
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine:   weedb.OperationalError: database is 
> locked
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
> weewx.reportengine: 

Re: [weewx-user] Re: Belchertown Error - Any idea what is wrong?

[Doug Jenkins]

Rpi2 with the latest O/S version is probably not enough to run both
belchertown and weewx together. Especially if you have a lot of archive
records to generate the NOAA reports on the first go.

The RPI 4 is readily available and will be a good investment for a nominal
fee. It has at least 2GB (vs 512mb) of RAM and a 4 core processor instead
of the single core Broadcom chip that came on that pi.

The bus is a lot better for I/O and you will have a lot less of an issue
with SD card corruption with RPi4 than with RPi2.

Trust me, I started my weewx 3.x site 3 years ago in on a RPi 2 and
struggled with stability with the pi itself. Now I run on a RPi4 with a
portable SSD drive to store my data with no issues.

Just my $0.02



On Mon, Nov 8, 2021, 8:02 PM vince  wrote:

> I bet if you turn Belchertown off (temporarily) and enable just the
> Standard or Seasons skin that it'll work just fine.
>
> Sometimes you need to throw more compute at the problem.
>
> On Monday, November 8, 2021 at 4:40:00 PM UTC-8 bchap...@gmail.com wrote:
>
>> Raspberry Pi 2 with raspbian buster
>>
>> This runs in a cycle of approximately every 6 minutes.  Nothing else
>> running on this machine.
>>
>> On Monday, November 8, 2021 at 7:35:14 PM UTC-5 tke...@gmail.com wrote:
>>
>>> Yes, tell us what computer you are using. Also, the operating system and
>>> version.
>>>
>>> On Mon, Nov 8, 2021 at 4:32 PM vince  wrote:
>>>
 Your database is locked :-)

 Typically this is when you're trying to do too much too fast on a very
 slow box like a pi-zero or the like.

 On Monday, November 8, 2021 at 4:06:48 PM UTC-8 bchap...@gmail.com
 wrote:

> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Main loop
> exiting. Shutting engine down.
> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Shutting
> down StdReport thread
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
> Caught unrecoverable exception in generator
> 'user.belchertown.HighchartsJsonGenerator'
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   database is locked
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   Traceback (most recent call last):
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: File
> "/usr/share/weewx/weedb/sqlite.py", line 30, in guarded_fn
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   return fn(*args, **kwargs)
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: File
> "/usr/share/weewx/weedb/sqlite.py", line 219, in execute
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   return sqlite3.Cursor.execute(self,
> *args, **kwargs)
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   sqlite3.OperationalError: database is
> locked
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: 
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   During handling of the above exception,
> another exception occurred:
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: 
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   Traceback (most recent call last):
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: File
> "/usr/share/weewx/weewx/reportengine.py", line 196, in run
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   obj.start()
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: File
> "/usr/share/weewx/weewx/reportengine.py", line 281, in start
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   self.run()
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: File
> "/usr/share/weewx/user/belchertown.py", line 1550, in run
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   start_ts = archive.firstGoodStamp()
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: File
> "/usr/share/weewx/weewx/manager.py", line 247, in firstGoodStamp
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   _row = self.getSql("SELECT
> MIN(dateTime) FROM %s" % self.table_name)
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: File
> "/usr/share/weewx/weewx/manager.py", line 449, in getSql
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   _cursor.execute(sql, sqlargs)
> Nov  8 18:53

Re: [weewx-user] Re: Belchertown Error - Any idea what is wrong?

[bchap...@gmail.com]

Nov  8 20:03:39 raspberrypi weewx[6055] INFO user.gw1000: driver version is 
0.4.1
Nov  8 20:03:39 raspberrypi weewx[6055] INFO user.gw1000: GW1000 address is 
192.168.20.222:45000
Nov  8 20:03:39 raspberrypi weewx[6055] INFO user.gw1000: poll interval is 
15 seconds
Nov  8 20:03:39 raspberrypi weewx[6055] INFO weewx.engine: StdConvert 
target unit is 0x1
Nov  8 20:03:39 raspberrypi weewx[6055] INFO weewx.engine: Archive will use 
data binding wx_binding
Nov  8 20:03:39 raspberrypi weewx[6055] INFO weewx.engine: Record 
generation will be attempted in 'software'
Nov  8 20:03:39 raspberrypi weewx[6055] INFO weewx.engine: Using archive 
interval of 60 seconds (software record generation)
Nov  8 20:03:39 raspberrypi weewx[6055] INFO weewx.restx: StationRegistry: 
Registration not requested.
Nov  8 20:03:39 raspberrypi weewx[6055] INFO weewx.restx: Wunderground-PWS: 
Data for station KNYGRANV5 will be posted
Nov  8 20:03:39 raspberrypi weewx[6055] INFO weewx.restx: PWSWeather: Data 
for station KNYGRANV5 will be posted
Nov  8 20:03:39 raspberrypi weewx[6055] INFO weewx.restx: CWOP: Data for 
station EW5855 will be posted
Nov  8 20:03:39 raspberrypi weewx[6055] INFO user.wcloud: service version 
is 0.13
Nov  8 20:03:39 raspberrypi weewx[6055] INFO user.wcloud: Data will be 
uploaded for id=efad7e92b2c1e3bd
Nov  8 20:03:39 raspberrypi weewx[6055] INFO user.windy: version is 0.7
Nov  8 20:03:39 raspberrypi weewx[6055] INFO user.windy: Data will be 
uploaded to https://stations.windy.com/pws/update
Nov  8 20:03:39 raspberrypi weewx[6055] INFO user.owm: service version is 
0.9
Nov  8 20:03:39 raspberrypi weewx[6055] ERROR user.owm: Data will not be 
posted: Missing option 'OpenWeatherMap'
Nov  8 20:03:39 raspberrypi weewx[6055] INFO user.rainmachine: service 
version is 0.5
Nov  8 20:03:39 raspberrypi weewx[6055] INFO user.rainmachine: Data will be 
uploaded for RainMachine located at 192.168.20.155 ssl: False
Nov  8 20:03:39 raspberrypi weewx[6055] INFO __main__: Starting up weewx 
version 4.5.1
Nov  8 20:03:39 raspberrypi weewx[6055] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Nov  8 20:03:39 raspberrypi weewx[6055] INFO weewx.manager: Starting 
backfill of daily summaries
Nov  8 20:03:39 raspberrypi weewx[6055] INFO weewx.manager: Daily summaries 
up to date
Nov  8 20:03:39 raspberrypi weewx[6055] INFO weewx.engine: Starting main 
packet loop.
Nov  8 20:03:39 raspberrypi weewx[6055] INFO user.gw1000: Using 'rainyear' 
for rain total
Nov  8 20:03:39 raspberrypi weewx[6055] INFO user.gw1000: skipping rain 
measurement of 292.9: no last rain
Nov  8 20:03:39 raspberrypi weewx[6055] INFO user.gw1000: Skipping 
lightning count of 0: no last count
Nov  8 20:04:25 raspberrypi weewx[6055] INFO weewx.manager: Added record 
2021-11-08 20:04:00 EST (1636419840) to database 'weewx.sdb'
Nov  8 20:04:25 raspberrypi weewx[6055] INFO weewx.manager: Added record 
2021-11-08 20:04:00 EST (1636419840) to daily summary in 'weewx.sdb'
Nov  8 20:04:25 raspberrypi weewx[6055] INFO weewx.restx: RainMachine: 
Published record 2021-11-08 20:04:00 EST (1636419840)
Nov  8 20:04:25 raspberrypi weewx[6055] INFO weewx.restx: Windy: Published 
record 2021-11-08 20:04:00 EST (1636419840)
Nov  8 20:04:25 raspberrypi weewx[6055] INFO weewx.restx: PWSWeather: 
Published record 2021-11-08 20:04:00 EST (1636419840)
Nov  8 20:04:25 raspberrypi weewx[6055] INFO weewx.restx: Wunderground-PWS: 
Published record 2021-11-08 20:04:00 EST (1636419840)
Nov  8 20:04:25 raspberrypi weewx[6055] INFO weewx.restx: CWOP: Published 
record 2021-11-08 20:04:00 EST (1636419840)
Nov  8 20:04:26 raspberrypi weewx[6055] INFO weewx.restx: WeatherCloud: 
Published record 2021-11-08 20:04:00 EST (1636419840)
Nov  8 20:04:30 raspberrypi weewx[6055] INFO weewx.cheetahgenerator: 
Generated 8 files for report SeasonsReport in 5.18 seconds
Nov  8 20:04:36 raspberrypi weewx[6055] INFO weewx.imagegenerator: 
Generated 15 images for report SeasonsReport in 5.53 seconds
Nov  8 20:04:36 raspberrypi weewx[6055] INFO weewx.reportengine: Copied 5 
files to /var/www/html/weewx
Nov  8 20:04:37 raspberrypi weewx[6055] INFO paramiko.transport: Connected 
(version 2.0, client OpenSSH_7.9p1)
Nov  8 20:04:37 raspberrypi weewx[6055] INFO paramiko.transport: 
Authentication (password) successful!
Nov  8 20:04:37 raspberrypi weewx[6055] INFO paramiko.transport.sftp: [chan 
0] Opened sftp connection (server version 3)
Nov  8 20:04:47 raspberrypi weewx[6055] INFO paramiko.transport.sftp: [chan 
0] sftp session closed.
Nov  8 20:04:47 raspberrypi weewx[6055] INFO user.sftp: sftpgenerator: 
transferred 41 files in 10.57 seconds
Nov  8 20:04:53 raspberrypi weewx[6055] INFO weewx.cheetahgenerator: 
Generated 11 files for report Belchertown in 6.58 seconds
Nov  8 20:04:54 raspberrypi weewx[6055] INFO weewx.reportengine: Copied 37 
files to /var/www/html
Nov  8 20:05:23 raspberrypi crontab[6326]: (pi) REPLACE (pi)
Nov  8 20:05:23 raspberrypi crontab[6326]: (pi) END EDIT (pi)
No

Re: [weewx-user] Re: Belchertown Error - Any idea what is wrong?

[Tom Keffer]

There are lots of ways this can happen. Things to try (or, at least, think
about):

1. I would think that an RPi2 would be enough to run WeeWX + Belchertown.
Check by running a tool such as htop or top. How busy is the processor?

Along the same line, what is your archive interval? If it is short (1
minute), and your reports are complex, it is possible you are asking too
much of an RPi2.

2. Database locked errors can be as simple as having an open instance of
sqlite3 or SQLite DB Browser, which are contending for the locks. Running
weewxd and another weewx utility simultaneously can cause this. You can
check to see if more than one process is using the database by using the
"fuser" command:

fuser -v /var/lib/weewx/weewx.sdb

3. Older versions of the underlying "C" library would wait for a full
second if the database was locked. It wouldn't take too many attempts to
exceed the typical 5 second timeout limit. However, I think this has been
fixed in newer versions. Still, it's worth an "apt update", followed by
"apt upgrade" to be sure you're up to date.

4. I am not very familiar with the Belchertown skin, so it's possible that
it's creating this problem internally by holding open two connections
simultaneously, without an intervening commit. Don't know.

5. It's also possible that your SD card is failing, and SQLite is
struggling to finalize the commits, leading to lock contention. The tool
fsck can help to determine the health of your card. Use the utility "top",
and look at the "wa" field (2nd line) while WeeWX is generating reports.





On Mon, Nov 8, 2021 at 5:21 PM Doug Jenkins  wrote:

> Rpi2 with the latest O/S version is probably not enough to run both
> belchertown and weewx together. Especially if you have a lot of archive
> records to generate the NOAA reports on the first go.
>
> The RPI 4 is readily available and will be a good investment for a nominal
> fee. It has at least 2GB (vs 512mb) of RAM and a 4 core processor instead
> of the single core Broadcom chip that came on that pi.
>
> The bus is a lot better for I/O and you will have a lot less of an issue
> with SD card corruption with RPi4 than with RPi2.
>
> Trust me, I started my weewx 3.x site 3 years ago in on a RPi 2 and
> struggled with stability with the pi itself. Now I run on a RPi4 with a
> portable SSD drive to store my data with no issues.
>
> Just my $0.02
>
>
>
> On Mon, Nov 8, 2021, 8:02 PM vince  wrote:
>
>> I bet if you turn Belchertown off (temporarily) and enable just the
>> Standard or Seasons skin that it'll work just fine.
>>
>> Sometimes you need to throw more compute at the problem.
>>
>> On Monday, November 8, 2021 at 4:40:00 PM UTC-8 bchap...@gmail.com wrote:
>>
>>> Raspberry Pi 2 with raspbian buster
>>>
>>> This runs in a cycle of approximately every 6 minutes.  Nothing else
>>> running on this machine.
>>>
>>> On Monday, November 8, 2021 at 7:35:14 PM UTC-5 tke...@gmail.com wrote:
>>>
 Yes, tell us what computer you are using. Also, the operating system
 and version.

 On Mon, Nov 8, 2021 at 4:32 PM vince  wrote:

> Your database is locked :-)
>
> Typically this is when you're trying to do too much too fast on a very
> slow box like a pi-zero or the like.
>
> On Monday, November 8, 2021 at 4:06:48 PM UTC-8 bchap...@gmail.com
> wrote:
>
>> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Main loop
>> exiting. Shutting engine down.
>> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Shutting
>> down StdReport thread
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
>> Caught unrecoverable exception in generator
>> 'user.belchertown.HighchartsJsonGenerator'
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
>> weewx.reportengine:   database is locked
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
>> weewx.reportengine:   Traceback (most recent call last):
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
>> weewx.reportengine: File
>> "/usr/share/weewx/weedb/sqlite.py", line 30, in guarded_fn
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
>> weewx.reportengine:   return fn(*args, **kwargs)
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
>> weewx.reportengine: File
>> "/usr/share/weewx/weedb/sqlite.py", line 219, in execute
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
>> weewx.reportengine:   return sqlite3.Cursor.execute(self,
>> *args, **kwargs)
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
>> weewx.reportengine:   sqlite3.OperationalError: database is
>> locked
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
>> weewx.reportengine: 
>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
>> weewx.reportengine:   During handling of the above exception,
>> another exception occ

Re: [weewx-user] Re: Belchertown Error - Any idea what is wrong?

[gjr80]

And there is the crux of the issue:

Nov  8 20:03:39 raspberrypi weewx[6055] INFO weewx.engine: Using archive 
interval of 60 seconds (software record generation)

Lesser RPis are just fine when used with a reasonable archive interval. 
Cutting it to the minimum 60 seconds is asking for trouble.

Gary

On Tuesday, 9 November 2021 at 11:56:10 UTC+10 tke...@gmail.com wrote:

> There are lots of ways this can happen. Things to try (or, at least, think 
> about):
>
> 1. I would think that an RPi2 would be enough to run WeeWX + Belchertown. 
> Check by running a tool such as htop or top. How busy is the processor?
>
> Along the same line, what is your archive interval? If it is short (1 
> minute), and your reports are complex, it is possible you are asking too 
> much of an RPi2.
>
> 2. Database locked errors can be as simple as having an open instance of 
> sqlite3 or SQLite DB Browser, which are contending for the locks. Running 
> weewxd and another weewx utility simultaneously can cause this. You can 
> check to see if more than one process is using the database by using the 
> "fuser" command:
>
> fuser -v /var/lib/weewx/weewx.sdb
>
> 3. Older versions of the underlying "C" library would wait for a full 
> second if the database was locked. It wouldn't take too many attempts to 
> exceed the typical 5 second timeout limit. However, I think this has been 
> fixed in newer versions. Still, it's worth an "apt update", followed by 
> "apt upgrade" to be sure you're up to date.
>
> 4. I am not very familiar with the Belchertown skin, so it's possible that 
> it's creating this problem internally by holding open two connections 
> simultaneously, without an intervening commit. Don't know.
>
> 5. It's also possible that your SD card is failing, and SQLite is 
> struggling to finalize the commits, leading to lock contention. The tool 
> fsck can help to determine the health of your card. Use the utility "top", 
> and look at the "wa" field (2nd line) while WeeWX is generating reports.
>
>
>
>
>
> On Mon, Nov 8, 2021 at 5:21 PM Doug Jenkins  wrote:
>
>> Rpi2 with the latest O/S version is probably not enough to run both 
>> belchertown and weewx together. Especially if you have a lot of archive 
>> records to generate the NOAA reports on the first go.
>>
>> The RPI 4 is readily available and will be a good investment for a 
>> nominal fee. It has at least 2GB (vs 512mb) of RAM and a 4 core processor 
>> instead of the single core Broadcom chip that came on that pi.
>>
>> The bus is a lot better for I/O and you will have a lot less of an issue 
>> with SD card corruption with RPi4 than with RPi2. 
>>
>> Trust me, I started my weewx 3.x site 3 years ago in on a RPi 2 and 
>> struggled with stability with the pi itself. Now I run on a RPi4 with a 
>> portable SSD drive to store my data with no issues.
>>
>> Just my $0.02
>>
>>
>>
>> On Mon, Nov 8, 2021, 8:02 PM vince  wrote:
>>
>>> I bet if you turn Belchertown off (temporarily) and enable just the 
>>> Standard or Seasons skin that it'll work just fine.
>>>
>>> Sometimes you need to throw more compute at the problem.
>>>
>>> On Monday, November 8, 2021 at 4:40:00 PM UTC-8 bchap...@gmail.com 
>>> wrote:
>>>
 Raspberry Pi 2 with raspbian buster

 This runs in a cycle of approximately every 6 minutes.  Nothing else 
 running on this machine.

 On Monday, November 8, 2021 at 7:35:14 PM UTC-5 tke...@gmail.com wrote:

> Yes, tell us what computer you are using. Also, the operating system 
> and version.
>
> On Mon, Nov 8, 2021 at 4:32 PM vince  wrote:
>
>> Your database is locked :-)
>>
>> Typically this is when you're trying to do too much too fast on a 
>> very slow box like a pi-zero or the like.
>>
>> On Monday, November 8, 2021 at 4:06:48 PM UTC-8 bchap...@gmail.com 
>> wrote:
>>
>>> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Main loop 
>>> exiting. Shutting engine down.
>>> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Shutting 
>>> down StdReport thread
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
>>> Caught unrecoverable exception in generator 
>>> 'user.belchertown.HighchartsJsonGenerator'
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   database is locked
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   Traceback (most recent call last):
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine: File 
>>> "/usr/share/weewx/weedb/sqlite.py", line 30, in guarded_fn
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine:   return fn(*args, **kwargs)
>>> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
>>> weewx.reportengine: File 
>>> "/usr/share/weewx/weedb/sqlite.py", line 219, in execute
>

Re: [weewx-user] Re: Belchertown Error - Any idea what is wrong?

[vince]

There is a LOT enabled on that box if you look at the logs.Long sftp 
session, Windy, PWS, Wunderground, CWOP,  Seasons, Rain Machine extension, 
owmap, and the like.   You just can't run all that stuff and a too-quick 
archive interval on something as weak as a model-B.

On Monday, November 8, 2021 at 6:03:20 PM UTC-8 gjr80 wrote:

> And there is the crux of the issue:
>
> Nov  8 20:03:39 raspberrypi weewx[6055] INFO weewx.engine: Using archive 
> interval of 60 seconds (software record generation)
>
> Lesser RPis are just fine when used with a reasonable archive interval. 
> Cutting it to the minimum 60 seconds is asking for trouble.
>
> Gary
>
> On Tuesday, 9 November 2021 at 11:56:10 UTC+10 tke...@gmail.com wrote:
>
>> There are lots of ways this can happen. Things to try (or, at least, 
>> think about):
>>
>> 1. I would think that an RPi2 would be enough to run WeeWX + Belchertown. 
>> Check by running a tool such as htop or top. How busy is the processor?
>>
>> Along the same line, what is your archive interval? If it is short (1 
>> minute), and your reports are complex, it is possible you are asking too 
>> much of an RPi2.
>>
>> 2. Database locked errors can be as simple as having an open instance of 
>> sqlite3 or SQLite DB Browser, which are contending for the locks. Running 
>> weewxd and another weewx utility simultaneously can cause this. You can 
>> check to see if more than one process is using the database by using the 
>> "fuser" command:
>>
>> fuser -v /var/lib/weewx/weewx.sdb
>>
>> 3. Older versions of the underlying "C" library would wait for a full 
>> second if the database was locked. It wouldn't take too many attempts to 
>> exceed the typical 5 second timeout limit. However, I think this has been 
>> fixed in newer versions. Still, it's worth an "apt update", followed by 
>> "apt upgrade" to be sure you're up to date.
>>
>> 4. I am not very familiar with the Belchertown skin, so it's possible 
>> that it's creating this problem internally by holding open two connections 
>> simultaneously, without an intervening commit. Don't know.
>>
>> 5. It's also possible that your SD card is failing, and SQLite is 
>> struggling to finalize the commits, leading to lock contention. The tool 
>> fsck can help to determine the health of your card. Use the utility "top", 
>> and look at the "wa" field (2nd line) while WeeWX is generating reports.
>>
>>
>>
>>
>>
>> On Mon, Nov 8, 2021 at 5:21 PM Doug Jenkins  
>> wrote:
>>
>>> Rpi2 with the latest O/S version is probably not enough to run both 
>>> belchertown and weewx together. Especially if you have a lot of archive 
>>> records to generate the NOAA reports on the first go.
>>>
>>> The RPI 4 is readily available and will be a good investment for a 
>>> nominal fee. It has at least 2GB (vs 512mb) of RAM and a 4 core processor 
>>> instead of the single core Broadcom chip that came on that pi.
>>>
>>> The bus is a lot better for I/O and you will have a lot less of an issue 
>>> with SD card corruption with RPi4 than with RPi2. 
>>>
>>> Trust me, I started my weewx 3.x site 3 years ago in on a RPi 2 and 
>>> struggled with stability with the pi itself. Now I run on a RPi4 with a 
>>> portable SSD drive to store my data with no issues.
>>>
>>> Just my $0.02
>>>
>>>
>>>
>>> On Mon, Nov 8, 2021, 8:02 PM vince  wrote:
>>>
 I bet if you turn Belchertown off (temporarily) and enable just the 
 Standard or Seasons skin that it'll work just fine.

 Sometimes you need to throw more compute at the problem.

 On Monday, November 8, 2021 at 4:40:00 PM UTC-8 bchap...@gmail.com 
 wrote:

> Raspberry Pi 2 with raspbian buster
>
> This runs in a cycle of approximately every 6 minutes.  Nothing else 
> running on this machine.
>
> On Monday, November 8, 2021 at 7:35:14 PM UTC-5 tke...@gmail.com 
> wrote:
>
>> Yes, tell us what computer you are using. Also, the operating system 
>> and version.
>>
>> On Mon, Nov 8, 2021 at 4:32 PM vince  wrote:
>>
>>> Your database is locked :-)
>>>
>>> Typically this is when you're trying to do too much too fast on a 
>>> very slow box like a pi-zero or the like.
>>>
>>> On Monday, November 8, 2021 at 4:06:48 PM UTC-8 bchap...@gmail.com 
>>> wrote:
>>>
 Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Main 
 loop exiting. Shutting engine down.
 Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Shutting 
 down StdReport thread
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
 Caught unrecoverable exception in generator 
 'user.belchertown.HighchartsJsonGenerator'
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   database is locked
 Nov  8 18:53:44 raspberrypi weewx[5618] ERROR 
 weewx.reportengine:   Traceback (most recent call last):
>>>

Re: [weewx-user] Re: Belchertown Error - Any idea what is wrong?

[bchap...@gmail.com]

Ok...I changed the archive interval to 120...looks good so far.  Might be 
time for a hardware upgrade.

Thanks for the help!

On Monday, November 8, 2021 at 9:07:57 PM UTC-5 vince wrote:

> There is a LOT enabled on that box if you look at the logs.Long sftp 
> session, Windy, PWS, Wunderground, CWOP,  Seasons, Rain Machine extension, 
> owmap, and the like.   You just can't run all that stuff and a too-quick 
> archive interval on something as weak as a model-B.
>
> On Monday, November 8, 2021 at 6:03:20 PM UTC-8 gjr80 wrote:
>
>> And there is the crux of the issue:
>>
>> Nov  8 20:03:39 raspberrypi weewx[6055] INFO weewx.engine: Using archive 
>> interval of 60 seconds (software record generation)
>>
>> Lesser RPis are just fine when used with a reasonable archive interval. 
>> Cutting it to the minimum 60 seconds is asking for trouble.
>>
>> Gary
>>
>> On Tuesday, 9 November 2021 at 11:56:10 UTC+10 tke...@gmail.com wrote:
>>
>>> There are lots of ways this can happen. Things to try (or, at least, 
>>> think about):
>>>
>>> 1. I would think that an RPi2 would be enough to run WeeWX + 
>>> Belchertown. Check by running a tool such as htop or top. How busy is the 
>>> processor?
>>>
>>> Along the same line, what is your archive interval? If it is short (1 
>>> minute), and your reports are complex, it is possible you are asking too 
>>> much of an RPi2.
>>>
>>> 2. Database locked errors can be as simple as having an open instance of 
>>> sqlite3 or SQLite DB Browser, which are contending for the locks. Running 
>>> weewxd and another weewx utility simultaneously can cause this. You can 
>>> check to see if more than one process is using the database by using the 
>>> "fuser" command:
>>>
>>> fuser -v /var/lib/weewx/weewx.sdb
>>>
>>> 3. Older versions of the underlying "C" library would wait for a full 
>>> second if the database was locked. It wouldn't take too many attempts to 
>>> exceed the typical 5 second timeout limit. However, I think this has been 
>>> fixed in newer versions. Still, it's worth an "apt update", followed by 
>>> "apt upgrade" to be sure you're up to date.
>>>
>>> 4. I am not very familiar with the Belchertown skin, so it's possible 
>>> that it's creating this problem internally by holding open two connections 
>>> simultaneously, without an intervening commit. Don't know.
>>>
>>> 5. It's also possible that your SD card is failing, and SQLite is 
>>> struggling to finalize the commits, leading to lock contention. The tool 
>>> fsck can help to determine the health of your card. Use the utility "top", 
>>> and look at the "wa" field (2nd line) while WeeWX is generating reports.
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Nov 8, 2021 at 5:21 PM Doug Jenkins  
>>> wrote:
>>>
 Rpi2 with the latest O/S version is probably not enough to run both 
 belchertown and weewx together. Especially if you have a lot of archive 
 records to generate the NOAA reports on the first go.

 The RPI 4 is readily available and will be a good investment for a 
 nominal fee. It has at least 2GB (vs 512mb) of RAM and a 4 core processor 
 instead of the single core Broadcom chip that came on that pi.

 The bus is a lot better for I/O and you will have a lot less of an 
 issue with SD card corruption with RPi4 than with RPi2. 

 Trust me, I started my weewx 3.x site 3 years ago in on a RPi 2 and 
 struggled with stability with the pi itself. Now I run on a RPi4 with a 
 portable SSD drive to store my data with no issues.

 Just my $0.02



 On Mon, Nov 8, 2021, 8:02 PM vince  wrote:

> I bet if you turn Belchertown off (temporarily) and enable just the 
> Standard or Seasons skin that it'll work just fine.
>
> Sometimes you need to throw more compute at the problem.
>
> On Monday, November 8, 2021 at 4:40:00 PM UTC-8 bchap...@gmail.com 
> wrote:
>
>> Raspberry Pi 2 with raspbian buster
>>
>> This runs in a cycle of approximately every 6 minutes.  Nothing else 
>> running on this machine.
>>
>> On Monday, November 8, 2021 at 7:35:14 PM UTC-5 tke...@gmail.com 
>> wrote:
>>
>>> Yes, tell us what computer you are using. Also, the operating system 
>>> and version.
>>>
>>> On Mon, Nov 8, 2021 at 4:32 PM vince  wrote:
>>>
 Your database is locked :-)

 Typically this is when you're trying to do too much too fast on a 
 very slow box like a pi-zero or the like.

 On Monday, November 8, 2021 at 4:06:48 PM UTC-8 bchap...@gmail.com 
 wrote:

> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Main 
> loop exiting. Shutting engine down.
> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: 
> Shutting down StdReport thread
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine: 
> Caught unrecoverable exception in generato

[weewx-user] Website

['super zee' via weewx-user]

If you add your site to be registered on Weewx, how long does it take to 
show up on the map?  Haven't seen it yet in about 24 hours.  

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/7311cf5c-3f8a-4adb-95f8-5a2ca4ee9d21n%40googlegroups.com.

Re: [weewx-user] Re: No AQI on Belchertown Skin

['super zee' via weewx-user]

I got it working.  I put the code in from Pat that adds a webcam tab behind 
the radar.

Chris 

On Monday, November 8, 2021 at 3:10:44 PM UTC-7 do...@dougjenkins.com wrote:

> No problem Chris! The site looks great and operates well on my side of the 
> world :)
>
> Pat did mention that to get the webcam working, there is a specific 
> comment and commit you need to get from his GitHub. I would just go to his 
> github and search for it. He has it working on his site now and probably 
> will have the code for his release general release.
>
> Good luck and good reporting! 
>
> Doug
>
> On Wed, Oct 27, 2021 at 12:18 PM 'super zee' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> Thanks Doug!  Your code worked like a charm.  Here is the current site.  
>> I will keep adding the code from Pat to incorporate the web cam.  
>>
>> Tempe AZ Weather Conditions 
>>
>> Chris Z
>> WG7B
>>
>>
>> On Saturday, October 23, 2021 at 10:13:13 PM UTC-7 super zee wrote:
>>
>>> Thanks Clifford.  Let me try cp -r
>>>
>>> Chris 
>>>
>>>
>>> On Thursday, October 21, 2021 at 7:52:28 AM UTC-7 Clifford Snow wrote:
>>>
 On Thu, Oct 21, 2021 at 7:08 AM 'super zee' via weewx-user <
 weewx...@googlegroups.com> wrote:

> Okay thanks Doug.  Let me try it.  
> If I want to backup copy my whole Belchertown folder, can I use cp 
> /etc/weewx/skins/Belchertown /etc/weewx/skins/Belchertown-old  ?
>
> Will the cp command copy a whole folder to back it up?  Or is it just 
> for files?
>
> I believe the copy command you want is cp -R 
 /etc/weewx/skins/Belchertown /etc/weewx/skins/Belchertown-old 

 The -R recursively copies all folders to the new location. See man cp

 Best,
 Clifford
 -- 
 @osm_washington
 www.snowandsnow.us
 OpenStreetMap: Maps with a human touch

>>> -- 
>> 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/85ffb56e-0d86-4a66-83e0-75c067ecf952n%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> Thanks,
>
> Doug Jenkins
> Phone: 813.391.5686 <(813)%20391-5686> | do...@dougjenkins.com | 
> www.dougjenkins.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/1059d021-a5a3-4868-9fd3-b52194907f11n%40googlegroups.com.