Re: [weewx-user] Daily rain total and daylight saving time error.

[Russell Swan]

The rain which fell during the missing 2 to 3 o’clock hour seems not to 
have been captured by the WeeWX database. If the console is not correct 
then nothing down stream of it can be correct either, so no need to be 
concerned with that. . The discrepancy between the console and database is 
.21”, and it happened on the day of the daylight saving time change. For 
the previous day of that rain event, there is no discrepancy.

That’s what I know. Why is the question. Thanks for your input. 

On Friday, March 22, 2024 at 11:54:57 AM UTC-4 Greg Troxel wrote:

> Russell Swan  writes:
>
> > Hi, daylight saving time happened last night and my rain total 
> > ($day.rain.sum) for the day does not equal that on the Davis Vantage 
> Pro2. 
> > The console reads 0.73" and weewx puts out 0.52". Interestingly, my 
> Steel 
> > Gauges indicate the correct 0.73". I think an hour of rain was dropped. 
>
> Why do you assume the console is correct? This is an edge case where
> bugs continuing to exist is likely.
>
> If daily rain is midnight to midnight, as is the US custom, then daily
> rain on March 10 will be for 23 hours.
>
> I suspect the difference is between
>
> [ 3/11] - [ 3/10]
>
> and
>
> [ 3/11] - [24 hours earlier]
>
> I think the first expression is correct.
>
> I would look at the hourly rain values and add them up and figure out
> which is right.
>
> Did you have 0.21" from 2300 on the 9th to  on the 10th? I had
> 0.10" during that hour (also in MA, but rain is spatially quite
> variabl). If so, that explains it. If not, more investigation is
> warranted :-)
>
> Greg
>
>
>

-- 
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/b1923e5b-e718-4011-9ec3-46ef1d253707n%40googlegroups.com.

Re: [weewx-user] Daily rain total and daylight saving time error.

[Greg Troxel]

Well, then I suggesat you file a bug with Davis that the console should
be set to and logging everything in UTC, and only displaying in local
time, and could they please issue a firmware update!

But seriously, keeping logs/databases in local time is a mess.

-- 
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/rmiv85ae5q4.fsf%40s1.lexort.com.

[weewx-user] How Remove Telemetry HTML

[Wayne]

Hello -  Am running weewx V 5.0.2 on a RPi 4 (DEB install) currently running 
the simulator driver.  My weather station is hardwired and therefore I have no 
need to display sensor signal, voltage, or battery status in reports.  For the 
Seasons skin how do I remove the "Sensor Status" html from being generated?  
This info appears on left side of the Seasons default web page.  Tried 
commenting-out what I thought was the responsible section in skins.conf but 
that did not work.  

So I'm guessing the lines below from skins.conf are responsible.  Do I delete 
all values to the right of "=" for sensor_connections, sensor_batteries, and 
sensor_voltages?  Comment out these lines entirely?  Something else?

Guidance please.  Thank you.

==
# The sensor status information is used in the sensor pages.  These lists
# determine which database fields will be shown, as well as the order in
# which they will be displayed.
sensor_connections = rxCheckPercent, signal1, signal2, signal3, signal4, 
signal5, signal6, signal7, signal8
sensor_batteries = outTempBatteryStatus, inTempBatteryStatus, 
rainBatteryStatus, hailBatteryStatus, snowBatteryStatus, windBatteryStatus, 
uvBatteryStatus, txBatteryStatus, batteryStatus1, batteryStatus2, 
batteryStatus3, batteryStatus4, batteryStatus5, batteryStatus6, batteryStatus7, 
batteryStatus8
sensor_voltages = consBatteryVoltage, heatingVoltage, supplyVoltage, 
referenceVoltage

==


-- 
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/c313baf6-1aa2-46e5-a1fa-f36035da3380%40app.fastmail.com.

[weewx-user] Weewx install error

[John Lowry]

Converting string to float in install.

HW: RPI5
SW: error on both RaspOS (bookworm) and Ubuntu

During install, the user is prompted for lat/long of the weather station.  
The installation fails with the following error output:

File "/usr/share/weewx/weectllib/station_actions.py", line 205, in 
config_config
config_latlon(config_dict, latitude=latitude, longitude=longitude, 
no_prompt=no_prompt)
  File "/usr/share/weewx/weectllib/station_actions.py", line 345, in 
config_latlon
config_dict['Station']['longitude'] = float(final_longitude)
  ^^
ValueError: could not convert string to float: '0.00048.830545'

The value I entered was 48.830545, not 0.000etc

Any suggestions highly appreciated.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6f7130de-387f-42c0-a322-8bf86cd02941n%40googlegroups.com.

Re: [weewx-user] Wunderground uploads using wunderfixer

['Andy Peterman' via weewx-user]

Actually, I've had this work for entries even older.  I just had it update 
entries from the previous day and it seems to have worked.  

Let's keep wunderfixer around!

On Friday, March 22, 2024 at 5:52:04 AM UTC-7 Tom Keffer wrote:

> Good to know! So, it appears the WU will allow postdating of up to 4 hours.
>
> On Thu, Mar 21, 2024 at 7:42 PM 'Andy Peterman' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> Strange, I'm still running 4.10.2 and just used wunderfixer 
>> successfully.  Our Internet was down for about 3 hours, I ran wunderfixer, 
>> and it filled in the entire period.  Also, last weekend weewx hung right 
>> after the time change (not sure why, but that's another problem) and when I 
>> got it going again, I had about a 4 hour gap.  Once again, I ran 
>> wunderfixer and it filled in the 20+ entries that were missing.  It was a 
>> while before the data showed up, but I checked and it's definitely there.
>>
>> Are you sure that Weather Underground has removed this feature?
>>
>> On Tuesday, October 10, 2023 at 5:33:19 PM UTC-7 Tom Keffer wrote:
>>
>>> Thanks for verifying what we've always suspected. I'm actually surprised 
>>> they responded at all!
>>>
>>> For just this reason we've dropped wunderfixer from V5.
>>>
>>> On Tue, Oct 10, 2023 at 2:16 PM Ernest Jillson  
>>> wrote:
>>>
 Good afternoon group.
  
 I emailed Weather Underground support yesterday about backfilling 
 observations after having no internet for two days. Here was the response:
  
 "Thank you for being so kind as to want to backfill your station's 
 data.  But because of the quality control process we have in place, data 
 that is more than an hour old is discarded.  So the upload is a success, 
 but it will never appear on the site.

 Please let me know if you have any additional questions.  Thank you for 
 being part of the Weather Underground community!

 --Victoria"
  
 While I did reply back and ask if that feature would be restored at any 
 time in the future, I think we can call this process dead. It sounds like 
 wunderfixer will still work, though, for data less than 1 hour old.
  
 Ernie

 -- 
 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/CAC5oUmOeLccyR-Jng%2BZCQBXbfixHNnZCevPJd_0CrwK4GjF%3DRw%40mail.gmail.com
  
 
 .

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/b4276305-cc25-4271-a7ce-0762b1d8c2c5n%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/caa70ba6-93a0-4471-a13d-143b97dbbc22n%40googlegroups.com.

Re: [weewx-user] Wunderground uploads using wunderfixer

[Tom Keffer]

If someone wants to take it on as a project, we could put it in its own
repository.

On Mon, Mar 25, 2024 at 10:47 AM 'Andy Peterman' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Actually, I've had this work for entries even older.  I just had it update
> entries from the previous day and it seems to have worked.
>
> Let's keep wunderfixer around!
>
> On Friday, March 22, 2024 at 5:52:04 AM UTC-7 Tom Keffer wrote:
>
>> Good to know! So, it appears the WU will allow postdating of up to 4
>> hours.
>>
>> On Thu, Mar 21, 2024 at 7:42 PM 'Andy Peterman' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>>
>>> Strange, I'm still running 4.10.2 and just used wunderfixer
>>> successfully.  Our Internet was down for about 3 hours, I ran wunderfixer,
>>> and it filled in the entire period.  Also, last weekend weewx hung right
>>> after the time change (not sure why, but that's another problem) and when I
>>> got it going again, I had about a 4 hour gap.  Once again, I ran
>>> wunderfixer and it filled in the 20+ entries that were missing.  It was a
>>> while before the data showed up, but I checked and it's definitely there.
>>>
>>> Are you sure that Weather Underground has removed this feature?
>>>
>>> On Tuesday, October 10, 2023 at 5:33:19 PM UTC-7 Tom Keffer wrote:
>>>
 Thanks for verifying what we've always suspected. I'm actually
 surprised they responded at all!

 For just this reason we've dropped wunderfixer from V5.

 On Tue, Oct 10, 2023 at 2:16 PM Ernest Jillson 
 wrote:

> Good afternoon group.
>
> I emailed Weather Underground support yesterday about backfilling
> observations after having no internet for two days. Here was the response:
>
> "Thank you for being so kind as to want to backfill your station's
> data.  But because of the quality control process we have in place, data
> that is more than an hour old is discarded.  So the upload is a success,
> but it will never appear on the site.
>
> Please let me know if you have any additional questions.  Thank you
> for being part of the Weather Underground community!
>
> --Victoria"
>
> While I did reply back and ask if that feature would be restored at
> any time in the future, I think we can call this process dead. It sounds
> like wunderfixer will still work, though, for data less than 1 hour old.
>
> Ernie
>
> --
> 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/CAC5oUmOeLccyR-Jng%2BZCQBXbfixHNnZCevPJd_0CrwK4GjF%3DRw%40mail.gmail.com
> 
> .
>
 --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/b4276305-cc25-4271-a7ce-0762b1d8c2c5n%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/caa70ba6-93a0-4471-a13d-143b97dbbc22n%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/CAPq0zEDvk1fG7evTAVZCx5Nr84R4wKK8OEq8RfrgoJWMa2x0Dg%40mail.gmail.com.

[weewx-user] Re: Weewx install error

[vince]

Lets see the snippet for longitude from weewx.conf please...

On Monday, March 25, 2024 at 10:47:04 AM UTC-7 John Lowry wrote:

> Converting string to float in install.
>
> HW: RPI5
> SW: error on both RaspOS (bookworm) and Ubuntu
>
> During install, the user is prompted for lat/long of the weather station.  
> The installation fails with the following error output:
>
> File "/usr/share/weewx/weectllib/station_actions.py", line 205, in 
> config_config
> config_latlon(config_dict, latitude=latitude, longitude=longitude, 
> no_prompt=no_prompt)
>   File "/usr/share/weewx/weectllib/station_actions.py", line 345, in 
> config_latlon
> config_dict['Station']['longitude'] = float(final_longitude)
>   ^^
> ValueError: could not convert string to float: '0.00048.830545'
>
> The value I entered was 48.830545, not 0.000etc
>
> Any suggestions highly appreciated.
>

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

[weewx-user] Re: Weewx install error

[John Lowry]

Thanks !
(sheepish look, operator malfunction...)


On Monday, March 25, 2024 at 2:16:03 PM UTC-4 vince wrote:

> Lets see the snippet for longitude from weewx.conf please...
>
> On Monday, March 25, 2024 at 10:47:04 AM UTC-7 John Lowry wrote:
>
>> Converting string to float in install.
>>
>> HW: RPI5
>> SW: error on both RaspOS (bookworm) and Ubuntu
>>
>> During install, the user is prompted for lat/long of the weather 
>> station.  
>> The installation fails with the following error output:
>>
>> File "/usr/share/weewx/weectllib/station_actions.py", line 205, in 
>> config_config
>> config_latlon(config_dict, latitude=latitude, longitude=longitude, 
>> no_prompt=no_prompt)
>>   File "/usr/share/weewx/weectllib/station_actions.py", line 345, in 
>> config_latlon
>> config_dict['Station']['longitude'] = float(final_longitude)
>>   ^^
>> ValueError: could not convert string to float: '0.00048.830545'
>>
>> The value I entered was 48.830545, not 0.000etc
>>
>> Any suggestions highly appreciated.
>>
>

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

Re: [weewx-user] How Remove Telemetry HTML

[Tom Keffer]

If you don't want it to appear at all, comment out the widget that is
responsible for displaying it. Go into file Seasons/index.html.tmpl and
change this:


  #include "current.inc"
  #include "sunmoon.inc"
  #include "hilo.inc"
  #include "sensors.inc"
  #include "about.inc"
  #include "radar.inc"
  #include "satellite.inc"
  #include "map.inc"


to this:


  #include "current.inc"
  #include "sunmoon.inc"
  #include "hilo.inc"
  ##include "sensors.inc"
  #include "about.inc"
  #include "radar.inc"
  #include "satellite.inc"
  #include "map.inc"


In summary, the hash mark "#" becomes a double hash "##" in order to
comment something out.

-tk

On Mon, Mar 25, 2024 at 10:04 AM Wayne  wrote:

> Hello -  Am running weewx V 5.0.2 on a RPi 4 (DEB install) currently
> running the simulator driver.  My weather station is hardwired and
> therefore I have no need to display sensor signal, voltage, or battery
> status in reports.  For the Seasons skin how do I remove the "Sensor
> Status" html from being generated?  This info appears on left side of the
> Seasons default web page.  Tried commenting-out what I thought was the
> responsible section in skins.conf but that did not work.
>
> So I'm guessing the lines below from skins.conf are responsible.  Do I
> delete all values to the right of "=" for sensor_connections,
> sensor_batteries, and sensor_voltages?  Comment out these lines entirely?
> Something else?
>
> Guidance please.  Thank you.
>
> ==
> # The sensor status information is used in the sensor pages.  These
> lists
> # determine which database fields will be shown, as well as the order
> in
> # which they will be displayed.
> sensor_connections = rxCheckPercent, signal1, signal2, signal3,
> signal4, signal5, signal6, signal7, signal8
> sensor_batteries = outTempBatteryStatus, inTempBatteryStatus,
> rainBatteryStatus, hailBatteryStatus, snowBatteryStatus, windBatteryStatus,
> uvBatteryStatus, txBatteryStatus, batteryStatus1, batteryStatus2,
> batteryStatus3, batteryStatus4, batteryStatus5, batteryStatus6,
> batteryStatus7, batteryStatus8
> sensor_voltages = consBatteryVoltage, heatingVoltage, supplyVoltage,
> referenceVoltage
>
>
> ==
>
>
> --
> 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/c313baf6-1aa2-46e5-a1fa-f36035da3380%40app.fastmail.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/CAPq0zEBsyUJK4jjD6YwxhGBNSraC1e-zvAJZnQvpTjB8dvDPOQ%40mail.gmail.com.

Re: [weewx-user] How Remove Telemetry HTML

[Wayne]

Yes, that worked.  Thank you!

On Mon, Mar 25, 2024, at 12:45 PM, Tom Keffer wrote:
> If you don't want it to appear at all, comment out the widget that is 
> responsible for displaying it. Go into file Seasons/index.html.tmpl and 
> change this:
>
> 
>   #include "current.inc"
>   #include "sunmoon.inc"
>   #include "hilo.inc"
>   #include "sensors.inc"
>   #include "about.inc"
>   #include "radar.inc"
>   #include "satellite.inc"
>   #include "map.inc"
> 
> to this:
> 
>   #include "current.inc"
>   #include "sunmoon.inc"
>   #include "hilo.inc"
>   ##include "sensors.inc"
>   #include "about.inc"
>   #include "radar.inc"
>   #include "satellite.inc"
>   #include "map.inc"
> 
> In summary, the hash mark "#" becomes a double hash "##" in order to 
> comment something out.
>
> -tk
>
> On Mon, Mar 25, 2024 at 10:04 AM Wayne  wrote:
>> Hello -  Am running weewx V 5.0.2 on a RPi 4 (DEB install) currently running 
>> the simulator driver.  My weather station is hardwired and therefore I have 
>> no need to display sensor signal, voltage, or battery status in reports.  
>> For the Seasons skin how do I remove the "Sensor Status" html from being 
>> generated?  This info appears on left side of the Seasons default web page.  
>> Tried commenting-out what I thought was the responsible section in 
>> skins.conf but that did not work.  
>> 
>> So I'm guessing the lines below from skins.conf are responsible.  Do I 
>> delete all values to the right of "=" for sensor_connections, 
>> sensor_batteries, and sensor_voltages?  Comment out these lines entirely?  
>> Something else?
>> 
>> Guidance please.  Thank you.
>> 
>> ==
>> # The sensor status information is used in the sensor pages.  These lists
>> # determine which database fields will be shown, as well as the order in
>> # which they will be displayed.
>> sensor_connections = rxCheckPercent, signal1, signal2, signal3, signal4, 
>> signal5, signal6, signal7, signal8
>> sensor_batteries = outTempBatteryStatus, inTempBatteryStatus, 
>> rainBatteryStatus, hailBatteryStatus, snowBatteryStatus, windBatteryStatus, 
>> uvBatteryStatus, txBatteryStatus, batteryStatus1, batteryStatus2, 
>> batteryStatus3, batteryStatus4, batteryStatus5, batteryStatus6, 
>> batteryStatus7, batteryStatus8
>> sensor_voltages = consBatteryVoltage, heatingVoltage, supplyVoltage, 
>> referenceVoltage
>> 
>> ==
>> 
>> 
>> -- 
>> 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/c313baf6-1aa2-46e5-a1fa-f36035da3380%40app.fastmail.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/CAPq0zEBsyUJK4jjD6YwxhGBNSraC1e-zvAJZnQvpTjB8dvDPOQ%40mail.gmail.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/63e54c85-9b6b-4967-92af-14d8f62aa075%40app.fastmail.com.

[weewx-user] Unexpected weewx stop: ERROR weewx.engine: Import of driver failed

[Thomas Hackler]

Hello,
my weewx stopped yesterday unexpected. The last logs are attached. It ran 
stable for over 1 week. I have restarts of my raspberry pi with cron every 
1 or 2 days. What is the reason that the gw1000 driver has suddenly a 
problem? How can I avoid it in future? Should I increase the attemps if 
there is a short problem with the wifi connection?
It is a problem of my gw1000 device? I see no problems with the ecowitt app.
Thank you!
Regards
Thomas

-- 
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/568aacb7-0c11-443b-af24-7879d4f2afabn%40googlegroups.com.
Mar 24 22:17:53 raspberrypi weewxd[1229]: DEBUG user.gw1000:  battery state 
data will be ignored for legacy WH40
Mar 24 22:17:53 raspberrypi weewxd[1229]: DEBUG user.gw1000:  battery state 
will not be reported for sensors with no signal data
Mar 24 22:17:53 raspberrypi weewxd[1229]: DEBUG user.gw1000:  unknown 
fields will be ignored
Mar 24 22:17:55 raspberrypi weewxd[1229]: DEBUG user.gw1000: Failed to obtain 
response to attempt 1 to send command 'CMD_READ_STATION_MAC': timed out
Mar 24 22:18:07 raspberrypi weewxd[1229]: DEBUG user.gw1000: Failed to obtain 
response to attempt 2 to send command 'CMD_READ_STATION_MAC': timed out
Mar 24 22:18:19 raspberrypi weewxd[1229]: DEBUG user.gw1000: Failed to obtain 
response to attempt 3 to send command 'CMD_READ_STATION_MAC': timed out
Mar 24 22:18:19 raspberrypi weewxd[1229]: ERROR user.gw1000: Failed to obtain 
response to command 'CMD_READ_STATION_MAC' after 3 attempts
Mar 24 22:18:19 raspberrypi weewxd[1229]: ERROR weewx.engine: Import of driver 
failed: Failed to obtain response to command 'CMD_READ_STATION_MAC' after >
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine:   
Traceback (most recent call last):
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine:   
self.console = loader_function(config_dict, self)
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine:    
  ^^
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine: 
File "/etc/weewx/bin/user/gw1000.py", line 1907, in loader
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine:   
return GatewayDriver(**config_dict[DRIVER_NAME])
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine:    
  ^
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine: 
File "/etc/weewx/bin/user/gw1000.py", line 2523, in __init__
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine:   
super(GatewayDriver, self).__init__(**stn_dict)
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine: 
File "/etc/weewx/bin/user/gw1000.py", line 1156, in __init__
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine:   
self.collector = GatewayCollector(ip_address=self.ip_address,
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine:    

Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine: 
File "/etc/weewx/bin/user/gw1000.py", line 2818, in __init__
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine:   
self.device = GatewayDevice(ip_address=ip_address, port=port,
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine:    
 ^^^
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine: 
File "/etc/weewx/bin/user/gw1000.py", line 6240, in __init__
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine:   
self.api = GatewayApi(ip_address=ip_address,
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine:    
  ^
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine: 
File "/etc/weewx/bin/user/gw1000.py", line 4981, in __init__
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine:   
self.mac = self.get_mac_address()
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine:    
  ^^
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine: 
File "/etc/weewx/bin/user/gw1000.py", line 5416, in get_mac_address
Mar 24 22:18:19 raspberrypi weewxd[1229]: CRITICAL weewx.engine:   
response = self.send_cmd_with_retries('CMD_READ_STATION_MAC')
Mar 24 

[weewx-user] Re: Unexpected weewx stop: ERROR weewx.engine: Import of driver failed

[vince]

I have also seen my gw1000 weewx setup abort on the pi4 occasionally when 
the wifi network bounces for some reason.  Mine's been up for 6 weeks now 
so it is definitely a transient kind of thing.

Writing yourself a little cron job to look for the weewxd process and if 
it's not there restart it wouldn't be too tough to do.   Perhaps there is 
some systemd configuration magic that is possible, but I'm not sure there 
what a safe+effective way to leverage systemd would look like.  I know how 
cron works :-)

On Monday, March 25, 2024 at 1:56:10 PM UTC-7 Thomas Hackler wrote:

> Hello,
> my weewx stopped yesterday unexpected. The last logs are attached. It ran 
> stable for over 1 week. I have restarts of my raspberry pi with cron every 
> 1 or 2 days. What is the reason that the gw1000 driver has suddenly a 
> problem? How can I avoid it in future? Should I increase the attemps if 
> there is a short problem with the wifi connection?
> It is a problem of my gw1000 device? I see no problems with the ecowitt 
> app.
> Thank you!
> Regards
> Thomas
>

-- 
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/c220117e-b402-4e2a-a749-9e1117949eden%40googlegroups.com.

[weewx-user] Re: Unexpected weewx stop: ERROR weewx.engine: Import of driver failed

[Thomas Hackler]

thank you for the answer, then it was maybe soemthing wrong with the wifi

does it make sense to increase the attempts before exit ?

I try to find something to check if the process is running
I have some experience with monit, so maybe I find an example or anything 
else


vince schrieb am Montag, 25. März 2024 um 22:09:58 UTC+1:

> I have also seen my gw1000 weewx setup abort on the pi4 occasionally when 
> the wifi network bounces for some reason.  Mine's been up for 6 weeks now 
> so it is definitely a transient kind of thing.
>
> Writing yourself a little cron job to look for the weewxd process and if 
> it's not there restart it wouldn't be too tough to do.   Perhaps there is 
> some systemd configuration magic that is possible, but I'm not sure there 
> what a safe+effective way to leverage systemd would look like.  I know how 
> cron works :-)
>
> On Monday, March 25, 2024 at 1:56:10 PM UTC-7 Thomas Hackler wrote:
>
>> Hello,
>> my weewx stopped yesterday unexpected. The last logs are attached. It ran 
>> stable for over 1 week. I have restarts of my raspberry pi with cron every 
>> 1 or 2 days. What is the reason that the gw1000 driver has suddenly a 
>> problem? How can I avoid it in future? Should I increase the attemps if 
>> there is a short problem with the wifi connection?
>> It is a problem of my gw1000 device? I see no problems with the ecowitt 
>> app.
>> Thank you!
>> Regards
>> Thomas
>>
>

-- 
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/2832f239-3a1b-404a-9904-bc6f7a00aa6cn%40googlegroups.com.

[weewx-user] Re: Unexpected weewx stop: ERROR weewx.engine: Import of driver failed

[vince]

Perhaps this setting (link) 

 is 
something to try if you want to experiment and let us know if it works…

On Monday, March 25, 2024 at 3:11:41 PM UTC-7 Thomas Hackler wrote:

> thank you for the answer, then it was maybe soemthing wrong with the wifi
>
> does it make sense to increase the attempts before exit ?
>
> I try to find something to check if the process is running
> I have some experience with monit, so maybe I find an example or anything 
> else
>
>
> vince schrieb am Montag, 25. März 2024 um 22:09:58 UTC+1:
>
>> I have also seen my gw1000 weewx setup abort on the pi4 occasionally when 
>> the wifi network bounces for some reason.  Mine's been up for 6 weeks now 
>> so it is definitely a transient kind of thing.
>>
>> Writing yourself a little cron job to look for the weewxd process and if 
>> it's not there restart it wouldn't be too tough to do.   Perhaps there is 
>> some systemd configuration magic that is possible, but I'm not sure there 
>> what a safe+effective way to leverage systemd would look like.  I know how 
>> cron works :-)
>>
>> On Monday, March 25, 2024 at 1:56:10 PM UTC-7 Thomas Hackler wrote:
>>
>>> Hello,
>>> my weewx stopped yesterday unexpected. The last logs are attached. It 
>>> ran stable for over 1 week. I have restarts of my raspberry pi with cron 
>>> every 1 or 2 days. What is the reason that the gw1000 driver has suddenly a 
>>> problem? How can I avoid it in future? Should I increase the attemps if 
>>> there is a short problem with the wifi connection?
>>> It is a problem of my gw1000 device? I see no problems with the ecowitt 
>>> app.
>>> Thank you!
>>> Regards
>>> Thomas
>>>
>>

-- 
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/0ad581b5-8ae0-4d26-84e3-bbf6c87cbdecn%40googlegroups.com.