Re: [weewx-user] Alltime Statistics

[Δημήτρης Βήχος]

in my seasons  skin folder i was replace the statistics.inc   page with the 
attached
no weewx restarting , in next update circle see the change .
works also in weewx 5.0v
actualy ina me page  

alltime records 

Στις Κυριακή 18 Φεβρουαρίου 2024 στις 1:47:50 π.μ. UTC+2, ο χρήστης Tom 
Keffer έγραψε:

> I've been thinking of that too, although with a monthly summary. It would 
> add a *lot* of code and a lot of complexity. I don't think we're quite 
> there yet.
>
> On Sat, Feb 17, 2024 at 9:31 AM Karen K  wrote:
>
>> I just read a post about slow skin creation in a german weather forum. 
>> This made me think about something. There were threads about the same topic 
>> here.
>>
>> Sometime the DaySummaryManager was introduced. And I guess the reason 
>> was to speed up aggregations. Instead of 288 records a day one record had 
>> to be read only. This can make the difference for large databases.
>>
>> Now if I think of a database of 10, 20 or more years. And I want to see 
>> some alltime statistics. Even the day summary table is large in those 
>> cases. 
>>
>> So I wonder if it would help to have a year summary table, too.
>>
>> -- 
>> 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/31290546-1043-4bda-8aac-646e9dd74c88n%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/16471e41-9ed7-4edd-9773-5d2a11ced3cfn%40googlegroups.com.


statistics.inc
Description: Binary data

Re: [weewx-user] Alltime Statistics

[Δημήτρης Βήχος]

in my seasons skin  folder  i was replace the statistics.in with this page.
works  on weewx 5.0 v.
no restarting in next update see the change.
actualy in my page , with greek characters

alltime records 




Στις Κυριακή 18 Φεβρουαρίου 2024 στις 1:47:50 π.μ. UTC+2, ο χρήστης Tom 
Keffer έγραψε:

> I've been thinking of that too, although with a monthly summary. It would 
> add a *lot* of code and a lot of complexity. I don't think we're quite 
> there yet.
>
> On Sat, Feb 17, 2024 at 9:31 AM Karen K  wrote:
>
>> I just read a post about slow skin creation in a german weather forum. 
>> This made me think about something. There were threads about the same topic 
>> here.
>>
>> Sometime the DaySummaryManager was introduced. And I guess the reason 
>> was to speed up aggregations. Instead of 288 records a day one record had 
>> to be read only. This can make the difference for large databases.
>>
>> Now if I think of a database of 10, 20 or more years. And I want to see 
>> some alltime statistics. Even the day summary table is large in those 
>> cases. 
>>
>> So I wonder if it would help to have a year summary table, too.
>>
>> -- 
>> 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/31290546-1043-4bda-8aac-646e9dd74c88n%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/8afcc781-0e89-489b-8820-ec65b244966en%40googlegroups.com.


statistics.inc
Description: Binary data

Re: [weewx-user] Alltime Statistics

[Δημήτρης Βήχος]

its easy in statistics.html with some changes. 

Στις Κυριακή 18 Φεβρουαρίου 2024 στις 1:47:50 π.μ. UTC+2, ο χρήστης Tom 
Keffer έγραψε:

> I've been thinking of that too, although with a monthly summary. It would 
> add a *lot* of code and a lot of complexity. I don't think we're quite 
> there yet.
>
> On Sat, Feb 17, 2024 at 9:31 AM Karen K  wrote:
>
>> I just read a post about slow skin creation in a german weather forum. 
>> This made me think about something. There were threads about the same topic 
>> here.
>>
>> Sometime the DaySummaryManager was introduced. And I guess the reason 
>> was to speed up aggregations. Instead of 288 records a day one record had 
>> to be read only. This can make the difference for large databases.
>>
>> Now if I think of a database of 10, 20 or more years. And I want to see 
>> some alltime statistics. Even the day summary table is large in those 
>> cases. 
>>
>> So I wonder if it would help to have a year summary table, too.
>>
>> -- 
>> 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/31290546-1043-4bda-8aac-646e9dd74c88n%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/50c5d3ef-922c-4ee5-be86-876b029c8cf6n%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[vince]

Meaning what for users or devs ?


On Saturday, February 17, 2024 at 3:45:38 PM UTC-8 Tom Keffer wrote:

> The difference is that to upload to the station registry, V5 uses an HTTP 
> POST with a serialized JSON payload, while V4 uses an HTTP GET.  The GET 
> sent an "unbound method" to the registry as a query parameter. We get a lot 
> of those, so I included a bit of code to salvage the hardware type from the 
> "unbound method" parameter. Hence, no one noticed.
>
>
>
> On Sat, Feb 17, 2024 at 2:24 PM vince  wrote:
>
>> There are 75 currently registered sites using this driver but 'all' are 
>> showing as running 4.x so I'm guessing something changed in v5 weewx..
>>
>> On Saturday, February 17, 2024 at 1:44:38 PM UTC-8 bell...@gmail.com 
>> wrote:
>>
>>> Theory:
>>> Drivers are suppose to implement hardware_name as a property. The driver 
>>> is missing the @property for hardware_name. When WeeWX accesses it as 
>>> property, for example, instance.hardware_name it returns the function 
>>> definition.
>>> Try adding the @property decorator to hardware_name in the driver. (I 
>>> did some minor testing by removing it in my driver)
>>> If this is it, I am stumped why it ever worked….
>>> rich
>>>
>>> On Saturday 17 February 2024 at 13:49:06 UTC-5 vince wrote:
>>>
 Tom - I can duplicate this here with 5.0.2 running vs. my 
 wfudpsimulator tool since I don't have actual hardware any more

 If registering is enabled, you get that error when the archive period 
 rolls around.

 I added some debugging to restx that might help. 

 # Delay the registration by a random amount so all stations 
 don't hit the server
 # at the same time.
 _registry_dict.setdefault('delay_post', random.randint(0, 45))

 log.info("StationRegistry _registry_dict: %s", _registry_dict)

 Which outputs

 2024-02-17T10:36:57.489015-08:00 raspberrypi weewxd[1902]: INFO 
 weewx.restx: StationRegistry _registry_dict: {'log_success': True, 
 'log_failure': True, 'station_url': '
 https://www.example.com/no-station-here', 'station_type': 
 'WeatherFlowUDP', 'description': 'WeatherflowUDP Simulator test station', 
 'latitude': 47.31, 'longitude': -122.36, 'station_model': >>> WeatherFlowUDPDriver.hardware_name of 
 >, 
 'config_path': '/home/pi/weewx-data/weewx.conf', 'entry_path': 
 '/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py', 
 'delay_post': 
 39}

  Notice the station_model value.  Looks a little odd

 The driver sets the following

 # Default settings...
 DRIVER_VERSION = "1.10"
 HARDWARE_NAME = "WeatherFlow"
 DRIVER_NAME = 'WeatherFlowUDP'

 Notice the single quotes around DRIVER_NAME there ?
 Perhaps some obscure single vs. double quote thing going on ?


 -- 
>> 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/742f4e63-77e3-41bc-b24d-ed98a37ab343n%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/8b2c0921-b99f-477f-a77d-65e6e4cd178an%40googlegroups.com.

[weewx-user] Re: Weewx don't work anymore after SD card restore, I don't know why?

[gjr80]

Your Ecowitt gateway driver issue is that the driver is unable to contact 
your gateway device, this is causing WeeWX to exit. This could be due to 
any number of reasons, it's impossible to say much more without seeing the 
full log from startup to failure. Refer to the How to get a good, useful 
log section 

 
of the Help! Posting to weewx-user Wiki page 
 for how 
to get a good log extract. Note that you will likely need to use the 
instructions for journalctl rather than syslog.

Gary
On Saturday 17 February 2024 at 19:58:48 UTC+10 Thomas Hackler wrote:

> I am sorry:
>
> pi@raspberrypi:~ $ systemctl status weewx
> ● weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
> preset: enabled)
>  Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36 CET; 
> 38min ago
>
>Docs: https://weewx.com/docs
> Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
> status=4)
>Main PID: 606 (code=exited, status=4)
> CPU: 621ms
>
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
>self.mac = self.get_mac_address()
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
>  File "/etc/weewx/bin/user/gw1000.py", line 3625, in get_mac_address
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
>return self.send_cmd_with_retries('CMD_READ_STATION_MAC')
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
>  File "/etc/weewx/bin/user/gw1000.py", line 3808, in send_cmd_with_retries
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
>raise GW1000IOError(_msg)
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:  
>  user.gw1000.GW1000IOError: Failed to obtain response to command 
> 'CMD_READ_STATION_MAC' after 3 attempts
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: Unable to load 
> driver: Failed to obtain response to command 'CMD_READ_STATION_MAC' after 3 
> attempts
>
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__:  
>  Exiting...
> Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Main process 
> exited, code=exited, status=4/NOPERMISSION
> Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Failed with result 
> 'exit-code'.
>
> michael.k...@gmx.at schrieb am Samstag, 17. Februar 2024 um 10:53:49 
> UTC+1:
>
>> It will definitely help if you'd attach the log files as a whole, it
>> see>
>> ms >
>> the>
>>  lo>
>> g ab>
>> ove is not showing all the relevant data.
>> Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:41:33 UTC+1:
>>
>>> pi@raspberrypi:~ $ apt policy weewx
>>> weewx:
>>>   Installed: 5.0.2-1
>>>   Candidate: 5.0.2-1
>>>
>>>
>>> Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:39:13 UTC+1:
>>>
 here are some more information, something seems to be wrong with the 
 gw1000 driver, but I changed nothing:

 pi@raspberrypi:~ $ systemctl status weewx*
 ● weewx.service - WeeWX
  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
 preset:>
  Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36 
 CET; 17mi>
Docs: https://weewx.com/docs
 Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
 status=4)
Main PID: 606 (code=exited, status=4)
 CPU: 621ms

 Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: 
   s>
 Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: 
 Fil>
 Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: 
   r>
 Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: 
 Fil>
 Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: 
   r>
 Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: 
   user.>
 Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: Unable to 
 load driv>
 Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__:  
  Exiting...
 Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Main process 
 exited, cod>
 Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Failed with 
 result 'exit>
 lines 1-18/18 (END)...skipping...
 ● weewx.service - WeeWX
  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
 preset: enabled)
  Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36 
 CET; 17min ago
Docs: https://weewx.com/docs
 Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
 status=4)
Main PID: 606 (code=exited, status=4)
 CPU: 621ms

Re: [weewx-user] Alltime Statistics

[Tom Keffer]

I've been thinking of that too, although with a monthly summary. It would
add a *lot* of code and a lot of complexity. I don't think we're quite
there yet.

On Sat, Feb 17, 2024 at 9:31 AM Karen K  wrote:

> I just read a post about slow skin creation in a german weather forum.
> This made me think about something. There were threads about the same topic
> here.
>
> Sometime the DaySummaryManager was introduced. And I guess the reason was
> to speed up aggregations. Instead of 288 records a day one record had to be
> read only. This can make the difference for large databases.
>
> Now if I think of a database of 10, 20 or more years. And I want to see
> some alltime statistics. Even the day summary table is large in those
> cases.
>
> So I wonder if it would help to have a year summary table, too.
>
> --
> 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/31290546-1043-4bda-8aac-646e9dd74c88n%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/CAPq0zEDevgDsSb%2BT3GoAoRaq23Rx4w1%3Dieuy6NubGWnkq93Ajw%40mail.gmail.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Tom Keffer]

The difference is that to upload to the station registry, V5 uses an HTTP
POST with a serialized JSON payload, while V4 uses an HTTP GET.  The GET
sent an "unbound method" to the registry as a query parameter. We get a lot
of those, so I included a bit of code to salvage the hardware type from the
"unbound method" parameter. Hence, no one noticed.



On Sat, Feb 17, 2024 at 2:24 PM vince  wrote:

> There are 75 currently registered sites using this driver but 'all' are
> showing as running 4.x so I'm guessing something changed in v5 weewx..
>
> On Saturday, February 17, 2024 at 1:44:38 PM UTC-8 bell...@gmail.com
> wrote:
>
>> Theory:
>> Drivers are suppose to implement hardware_name as a property. The driver
>> is missing the @property for hardware_name. When WeeWX accesses it as
>> property, for example, instance.hardware_name it returns the function
>> definition.
>> Try adding the @property decorator to hardware_name in the driver. (I did
>> some minor testing by removing it in my driver)
>> If this is it, I am stumped why it ever worked….
>> rich
>>
>> On Saturday 17 February 2024 at 13:49:06 UTC-5 vince wrote:
>>
>>> Tom - I can duplicate this here with 5.0.2 running vs. my wfudpsimulator
>>> tool since I don't have actual hardware any more
>>>
>>> If registering is enabled, you get that error when the archive period
>>> rolls around.
>>>
>>> I added some debugging to restx that might help.
>>>
>>> # Delay the registration by a random amount so all stations
>>> don't hit the server
>>> # at the same time.
>>> _registry_dict.setdefault('delay_post', random.randint(0, 45))
>>>
>>> log.info("StationRegistry _registry_dict: %s", _registry_dict)
>>>
>>> Which outputs
>>>
>>> 2024-02-17T10:36:57.489015-08:00 raspberrypi weewxd[1902]: INFO
>>> weewx.restx: StationRegistry _registry_dict: {'log_success': True,
>>> 'log_failure': True, 'station_url': '
>>> https://www.example.com/no-station-here', 'station_type':
>>> 'WeatherFlowUDP', 'description': 'WeatherflowUDP Simulator test station',
>>> 'latitude': 47.31, 'longitude': -122.36, 'station_model': >> WeatherFlowUDPDriver.hardware_name of
>>> >,
>>> 'config_path': '/home/pi/weewx-data/weewx.conf', 'entry_path':
>>> '/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py', 'delay_post':
>>> 39}
>>>
>>>  Notice the station_model value.  Looks a little odd
>>>
>>> The driver sets the following
>>>
>>> # Default settings...
>>> DRIVER_VERSION = "1.10"
>>> HARDWARE_NAME = "WeatherFlow"
>>> DRIVER_NAME = 'WeatherFlowUDP'
>>>
>>> Notice the single quotes around DRIVER_NAME there ?
>>> Perhaps some obscure single vs. double quote thing going on ?
>>>
>>>
>>> --
> 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/742f4e63-77e3-41bc-b24d-ed98a37ab343n%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/CAPq0zEA4WJfBRNFvGLf5sQFFYd740qb9ERvM9cyjAaHcnFcGsA%40mail.gmail.com.

Re: [weewx-user] Re: Weewx don't work anymore after SD card restore, I don't know why?

[Tom Keffer]

You have given very little information, but you are probably suffering from
a permissions problem. WeeWX V5 runs as user 'weewx' (instead of 'root'),
which doesn't always have the permissions it needs to run weewxd.

Read the wiki article *Understanding permissions
. *Pay
particular attention to the section *How to fix device permissions
*.
See if they help.

-tk

On Sat, Feb 17, 2024 at 1:58 AM Thomas Hackler  wrote:

> I am sorry:
>
> pi@raspberrypi:~ $ systemctl status weewx
> ● weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor
> preset: enabled)
>  Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36 CET;
> 38min ago
>Docs: https://weewx.com/docs
> Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited,
> status=4)
>Main PID: 606 (code=exited, status=4)
> CPU: 621ms
>
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: 
>self.mac = self.get_mac_address()
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: 
>  File "/etc/weewx/bin/user/gw1000.py", line 3625, in get_mac_address
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: 
>return self.send_cmd_with_retries('CMD_READ_STATION_MAC')
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: 
>  File "/etc/weewx/bin/user/gw1000.py", line 3808, in send_cmd_with_retries
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: 
>raise GW1000IOError(_msg)
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: 
>  user.gw1000.GW1000IOError: Failed to obtain response to command
> 'CMD_READ_STATION_MAC' after 3 attempts
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: Unable to load
> driver: Failed to obtain response to command 'CMD_READ_STATION_MAC' after 3
> attempts
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: 
>  Exiting...
> Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Main process
> exited, code=exited, status=4/NOPERMISSION
> Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Failed with result
> 'exit-code'.
>
> michael.k...@gmx.at schrieb am Samstag, 17. Februar 2024 um 10:53:49
> UTC+1:
>
>> It will definitely help if you'd attach the log files as a whole, it
>> see>
>> ms >
>> the>
>>  lo>
>> g ab>
>> ove is not showing all the relevant data.
>> Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:41:33 UTC+1:
>>
>>> pi@raspberrypi:~ $ apt policy weewx
>>> weewx:
>>>   Installed: 5.0.2-1
>>>   Candidate: 5.0.2-1
>>>
>>>
>>> Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:39:13 UTC+1:
>>>
 here are some more information, something seems to be wrong with the
 gw1000 driver, but I changed nothing:

 pi@raspberrypi:~ $ systemctl status weewx*
 ● weewx.service - WeeWX
  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor
 preset:>
  Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36
 CET; 17mi>
Docs: https://weewx.com/docs
 Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited,
 status=4)
Main PID: 606 (code=exited, status=4)
 CPU: 621ms

 Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:
   s>
 Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:
 Fil>
 Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:
   r>
 Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:
 Fil>
 Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:
   r>
 Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:
   user.>
 Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: Unable to
 load driv>
 Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: 
  Exiting...
 Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Main process
 exited, cod>
 Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Failed with
 result 'exit>
 lines 1-18/18 (END)...skipping...
 ● weewx.service - WeeWX
  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor
 preset: enabled)
  Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36
 CET; 17min ago
Docs: https://weewx.com/docs
 Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited,
 status=4)
Main PID: 606 (code=exited, status=4)
 CPU: 621ms

 Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:35:25 UTC+1:

> Hello,
> I use weewx on a raspberry Pi 4. My system crashed and I had to go
> back to an SD card image from January. It was 

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[vince]

There are 75 currently registered sites using this driver but 'all' are 
showing as running 4.x so I'm guessing something changed in v5 weewx..

On Saturday, February 17, 2024 at 1:44:38 PM UTC-8 bell...@gmail.com wrote:

> Theory:
> Drivers are suppose to implement hardware_name as a property. The driver 
> is missing the @property for hardware_name. When WeeWX accesses it as 
> property, for example, instance.hardware_name it returns the function 
> definition.
> Try adding the @property decorator to hardware_name in the driver. (I did 
> some minor testing by removing it in my driver)
> If this is it, I am stumped why it ever worked….
> rich
>
> On Saturday 17 February 2024 at 13:49:06 UTC-5 vince wrote:
>
>> Tom - I can duplicate this here with 5.0.2 running vs. my wfudpsimulator 
>> tool since I don't have actual hardware any more
>>
>> If registering is enabled, you get that error when the archive period 
>> rolls around.
>>
>> I added some debugging to restx that might help. 
>>
>> # Delay the registration by a random amount so all stations don't 
>> hit the server
>> # at the same time.
>> _registry_dict.setdefault('delay_post', random.randint(0, 45))
>>
>> log.info("StationRegistry _registry_dict: %s", _registry_dict)
>>
>> Which outputs
>>
>> 2024-02-17T10:36:57.489015-08:00 raspberrypi weewxd[1902]: INFO 
>> weewx.restx: StationRegistry _registry_dict: {'log_success': True, 
>> 'log_failure': True, 'station_url': '
>> https://www.example.com/no-station-here', 'station_type': 
>> 'WeatherFlowUDP', 'description': 'WeatherflowUDP Simulator test station', 
>> 'latitude': 47.31, 'longitude': -122.36, 'station_model': > WeatherFlowUDPDriver.hardware_name of 
>> >, 
>> 'config_path': '/home/pi/weewx-data/weewx.conf', 'entry_path': 
>> '/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py', 'delay_post': 
>> 39}
>>
>>  Notice the station_model value.  Looks a little odd
>>
>> The driver sets the following
>>
>> # Default settings...
>> DRIVER_VERSION = "1.10"
>> HARDWARE_NAME = "WeatherFlow"
>> DRIVER_NAME = 'WeatherFlowUDP'
>>
>> Notice the single quotes around DRIVER_NAME there ?
>> Perhaps some obscure single vs. double quote thing going on ?
>>
>>
>>

-- 
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/742f4e63-77e3-41bc-b24d-ed98a37ab343n%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[bell...@gmail.com]

Theory:
Drivers are suppose to implement hardware_name as a property. The driver is 
missing the @property for hardware_name. When WeeWX accesses it as 
property, for example, instance.hardware_name it returns the function 
definition.
Try adding the @property decorator to hardware_name in the driver. (I did 
some minor testing by removing it in my driver)
If this is it, I am stumped why it ever worked….
rich

On Saturday 17 February 2024 at 13:49:06 UTC-5 vince wrote:

> Tom - I can duplicate this here with 5.0.2 running vs. my wfudpsimulator 
> tool since I don't have actual hardware any more
>
> If registering is enabled, you get that error when the archive period 
> rolls around.
>
> I added some debugging to restx that might help. 
>
> # Delay the registration by a random amount so all stations don't 
> hit the server
> # at the same time.
> _registry_dict.setdefault('delay_post', random.randint(0, 45))
>
> log.info("StationRegistry _registry_dict: %s", _registry_dict)
>
> Which outputs
>
> 2024-02-17T10:36:57.489015-08:00 raspberrypi weewxd[1902]: INFO 
> weewx.restx: StationRegistry _registry_dict: {'log_success': True, 
> 'log_failure': True, 'station_url': '
> https://www.example.com/no-station-here', 'station_type': 
> 'WeatherFlowUDP', 'description': 'WeatherflowUDP Simulator test station', 
> 'latitude': 47.31, 'longitude': -122.36, 'station_model':  WeatherFlowUDPDriver.hardware_name of 
> >, 
> 'config_path': '/home/pi/weewx-data/weewx.conf', 'entry_path': 
> '/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py', 'delay_post': 
> 39}
>
>  Notice the station_model value.  Looks a little odd
>
> The driver sets the following
>
> # Default settings...
> DRIVER_VERSION = "1.10"
> HARDWARE_NAME = "WeatherFlow"
> DRIVER_NAME = 'WeatherFlowUDP'
>
> Notice the single quotes around DRIVER_NAME there ?
> Perhaps some obscure single vs. double quote thing going on ?
>
>
>

-- 
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/648b2312-d50b-44d7-8d12-ef76a92e55ffn%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[vince]

Tom - I can duplicate this here with 5.0.2 running vs. my wfudpsimulator 
tool since I don't have actual hardware any more

If registering is enabled, you get that error when the archive period rolls 
around.

I added some debugging to restx that might help. 

# Delay the registration by a random amount so all stations don't 
hit the server
# at the same time.
_registry_dict.setdefault('delay_post', random.randint(0, 45))

log.info("StationRegistry _registry_dict: %s", _registry_dict)

Which outputs

2024-02-17T10:36:57.489015-08:00 raspberrypi weewxd[1902]: INFO 
weewx.restx: StationRegistry _registry_dict: {'log_success': True, 
'log_failure': True, 'station_url': 
'https://www.example.com/no-station-here', 'station_type': 
'WeatherFlowUDP', 'description': 'WeatherflowUDP Simulator test station', 
'latitude': 47.31, 'longitude': -122.36, 'station_model': >, 
'config_path': '/home/pi/weewx-data/weewx.conf', 'entry_path': 
'/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py', 'delay_post': 
39}

 Notice the station_model value.  Looks a little odd

The driver sets the following

# Default settings...
DRIVER_VERSION = "1.10"
HARDWARE_NAME = "WeatherFlow"
DRIVER_NAME = 'WeatherFlowUDP'

Notice the single quotes around DRIVER_NAME there ?
Perhaps some obscure single vs. double quote thing going on ?


-- 
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/182ff702-ec25-462f-a070-e75e9869b94en%40googlegroups.com.

[weewx-user] Re: weewx-sftp question

[WindnFog]

Did you install Matthew's sftp extension?

https://github.com/matthewwall/weewx-sftp

You'll also need pysftp, which you install with pip.

I have used sftp with the above for years.  Most hosting sites are moving 
away from ftp for security reasons.

Paul VE1DX

On Saturday, February 17, 2024 at 11:05:28 AM UTC-4 Steve2Q wrote:

> Hello. I am having problems (again) trying to use ftp with DreamHost. They 
> recommend changing to sftp, so I changed weewx conf to make   secure_ftp = 
> True. I am using Weewx V 3.8.2
>
> Apparently, just making secure_ftp = True is not working. Should I try 
> using weewx-sftp and will it work with 3.8.2?
>
>  Thanks
>

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

[weewx-user] Alltime Statistics

[Karen K]

I just read a post about slow skin creation in a german weather forum. This 
made me think about something. There were threads about the same topic here.

Sometime the DaySummaryManager was introduced. And I guess the reason was 
to speed up aggregations. Instead of 288 records a day one record had to be 
read only. This can make the difference for large databases.

Now if I think of a database of 10, 20 or more years. And I want to see 
some alltime statistics. Even the day summary table is large in those 
cases. 

So I wonder if it would help to have a year summary table, too.

-- 
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/31290546-1043-4bda-8aac-646e9dd74c88n%40googlegroups.com.

[weewx-user] Re: weewx-sftp question

[Tom Hogland]

So weewx's secure_ftp is ftps, NOT sftp - two different things. The 
weewx-sftp plugin fills the gap nicely - I'm using it with Gandi hosting. 

Does it work with 3.8.2? No idea, but it's been out for a while, and as 
long as you can load the prerequisites it would work I'd think.

On Saturday, February 17, 2024 at 6:05:28 AM UTC-9 Steve2Q wrote:

> Hello. I am having problems (again) trying to use ftp with DreamHost. They 
> recommend changing to sftp, so I changed weewx conf to make   secure_ftp = 
> True. I am using Weewx V 3.8.2
>
> Apparently, just making secure_ftp = True is not working. Should I try 
> using weewx-sftp and will it work with 3.8.2?
>
>  Thanks
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/08cca574-414b-4158-8904-bf29f06359d2n%40googlegroups.com.

[weewx-user] weewx-sftp question

[Steve2Q]

Hello. I am having problems (again) trying to use ftp with DreamHost. They 
recommend changing to sftp, so I changed weewx conf to make   secure_ftp = 
True. I am using Weewx V 3.8.2

Apparently, just making secure_ftp = True is not working. Should I try 
using weewx-sftp and will it work with 3.8.2?

 Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6de52956-24bf-4a56-b1f8-4574c983c05fn%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[pmcg...@gmail.com]

I am seeing the same issue.  Here is my startup through a reporting cycle 
log with debug=1

Feb 17 06:07:18 Garagepi weewxd-weatherflow[1999]: INFO weewx.engine: Using 
binding 'wx_binding' to database 'weatherflow.sdb'
Feb 17 06:07:18 Garagepi weewxd-weatherflow[1999]: INFO weewx.manager: 
Starting backfill of daily summaries
Feb 17 06:07:18 Garagepi weewxd-weatherflow[1999]: INFO weewx.manager: 
Daily summaries up to date
Feb 17 06:07:18 Garagepi weewxd-weatherflow[1999]: INFO weewx.engine: 
Starting main packet loop.
Feb 17 06:07:18 Garagepi weewxd-weatherflow[1999]: INFO 
user.weatherflowudp: Listening for UDP broadcasts to IP address  
on port 50222, with timeout 90 and share_socket True...
Feb 17 06:07:28 Garagepi weewxd-weatherflow[1999]: INFO weewx.wxxtypes: 
Type beaufort has been deprecated. Use unit beaufort instead.
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: INFO __main__: Received 
signal TERM (15).
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: INFO weewx.engine: Main 
loop exiting. Shutting engine down.
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG weewx.restx: Shut 
down StationRegistry thread.
Feb 17 06:07:57 Garagepi systemd[1]: Stopping WeeWX weatherflow...
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: INFO __main__: 
Terminating weewx version 5.0.2
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
 Traceback (most recent call last):
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
   File "/usr/share/weewx/weewxd.py", line 166, in main
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
 engine.run()
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
   File "/usr/share/weewx/weewx/engine.py", line 204, in run
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
 for packet in self.console.genLoopPackets():
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
   File "/etc/weewx/bin/user/weatherflowudp.py", line 290, in genLoopPackets
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
 for udp_packet in self.gen_udp_packets():
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
   File "/etc/weewx/bin/user/weatherflowudp.py", line 310, in 
gen_udp_packets
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
 m0, host_info = sock.recvfrom(1024)
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
   File "/usr/share/weewx/weewxd.py", line 260, in sigTERMhandler
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
 raise Terminate
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
 Terminate
Feb 17 06:07:57 Garagepi systemd[1]: weewx@weatherflow.service: Main 
process exited, code=killed, status=15/TERM
Feb 17 06:07:57 Garagepi systemd[1]: weewx@weatherflow.service: Succeeded.
Feb 17 06:07:57 Garagepi systemd[1]: Stopped WeeWX weatherflow.
Feb 17 06:07:57 Garagepi systemd[1]: Started WeeWX weatherflow.
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: 
Initializing weewxd version 5.0.2
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: Command 
line: /usr/share/weewx/weewxd.py --log-label weewxd-weatherflow 
/etc/weewx/weatherflow.conf
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: Using 
Python 3.7.3 (default, Oct 11 2023, 09:51:27) #012[GCC 8.3.0]
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: Located 
at /usr/bin/python3
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: Platform 
Linux-5.10.103-v7+-armv7l-with-debian-10.13
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: Locale: 
'en_US.UTF-8'
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: Entry 
path: /usr/share/weewx/weewxd.py
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: 
WEEWX_ROOT: /etc/weewx
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: 
Configuration file: /etc/weewx/weatherflow.conf
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: User 
module: /etc/weewx/bin/user
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: Debug: 1
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: DEBUG __main__: 
Initializing engine
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO weewx.engine: 
Loading station type WeatherFlowUDP (user.weatherflowudp)
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO 
user.weatherflowudp: driver version is 1.11
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO 
user.weatherflowudp: sensor map is {'outTemp': 
'air_temperature.ST-0353.obs_st', 'outHumidity': 
'relative_humidity.ST-0353.obs_st', 'pressure': 
'station_pressure.ST-0353.obs_st', 'lightning_strike_count': 
'lightning_strike_count.ST-0353.obs_st', 'lightning_distance': 

[weewx-user] Re: Can we upgrade to WeeWX 5.0x WITHOUT MAJOR RISK?

[Karen K]

I would suggest creating a backup first. Backups are always a good idea, 
independent of what you want to do. You will surely beat yourself if you 
have not created it. This includes a whole copy of the hard disk.

-- 
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/88344a99-a1d0-4638-8be3-e1195e648ea3n%40googlegroups.com.

[weewx-user] Re: SOLVED as3935 lightining module not detected by I2c on a Rpi4

[Pierre-Yves]

Thanks Karen,
Yes, it is what I understood.
As I explain in my last post, I fixed the problem by extending the range to 
0x03 to 0x77 by the command  sudo i2cdetect -a -y 1 0x03 0x77.
That works perfectly now
PY

Le samedi 17 février 2024 à 08:04:00 UTC+1, Karen K a écrit :

> May be you want to try option -a:
>
> sudo i2cdetect -a -y 1
>
> Adresses below 0x8 are reserved at Raspberry Pi 4. But the lightning 
> module can address 0x0, 0x1, 0x2, or 0x3 only.
>
>

-- 
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/0e8e7602-46d9-4ca8-80e0-f448ee217541n%40googlegroups.com.

[weewx-user] Re: Weewx don't work anymore after SD card restore, I don't know why?

[Thomas Hackler]

I am sorry:

pi@raspberrypi:~ $ systemctl status weewx
● weewx.service - WeeWX
 Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36 CET; 
38min ago
   Docs: https://weewx.com/docs
Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
status=4)
   Main PID: 606 (code=exited, status=4)
CPU: 621ms

Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
   self.mac = self.get_mac_address()
Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
 File "/etc/weewx/bin/user/gw1000.py", line 3625, in get_mac_address
Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
   return self.send_cmd_with_retries('CMD_READ_STATION_MAC')
Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
 File "/etc/weewx/bin/user/gw1000.py", line 3808, in send_cmd_with_retries
Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
   raise GW1000IOError(_msg)
Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:  
 user.gw1000.GW1000IOError: Failed to obtain response to command 
'CMD_READ_STATION_MAC' after 3 attempts
Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: Unable to load 
driver: Failed to obtain response to command 'CMD_READ_STATION_MAC' after 3 
attempts
Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__:  
 Exiting...
Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Main process exited, 
code=exited, status=4/NOPERMISSION
Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Failed with result 
'exit-code'.

michael.k...@gmx.at schrieb am Samstag, 17. Februar 2024 um 10:53:49 UTC+1:

> It will definitely help if you'd attach the log files as a whole, it
> see>
> ms >
> the>
>  lo>
> g ab>
> ove is not showing all the relevant data.
> Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:41:33 UTC+1:
>
>> pi@raspberrypi:~ $ apt policy weewx
>> weewx:
>>   Installed: 5.0.2-1
>>   Candidate: 5.0.2-1
>>
>>
>> Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:39:13 UTC+1:
>>
>>> here are some more information, something seems to be wrong with the 
>>> gw1000 driver, but I changed nothing:
>>>
>>> pi@raspberrypi:~ $ systemctl status weewx*
>>> ● weewx.service - WeeWX
>>>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
>>> preset:>
>>>  Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36 
>>> CET; 17mi>
>>>Docs: https://weewx.com/docs
>>> Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
>>> status=4)
>>>Main PID: 606 (code=exited, status=4)
>>> CPU: 621ms
>>>
>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:  
>>>  s>
>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:  
>>>Fil>
>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:  
>>>  r>
>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:  
>>>Fil>
>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:  
>>>  r>
>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:  
>>>  user.>
>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: Unable to 
>>> load driv>
>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__:  
>>>  Exiting...
>>> Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Main process 
>>> exited, cod>
>>> Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Failed with 
>>> result 'exit>
>>> lines 1-18/18 (END)...skipping...
>>> ● weewx.service - WeeWX
>>>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
>>> preset: enabled)
>>>  Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36 
>>> CET; 17min ago
>>>Docs: https://weewx.com/docs
>>> Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
>>> status=4)
>>>Main PID: 606 (code=exited, status=4)
>>> CPU: 621ms
>>>
>>> Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:35:25 UTC+1:
>>>
 Hello,
 I use weewx on a raspberry Pi 4. My system crashed and I had to go back 
 to an SD card image from January. It was a state were weewx was runing 
 normally.
 But now I don't know why weewx is not working anymore.
 I get no reaction for commands like 

 sudo /etc/init.d/weewx stop
 sudo /etc/init.d/weewx start

 debug = 1 and I don't see something in syslog:

 sudo tail -f /var/log/syslog | grep weewx 

 in January I had a weewx 4 and with apt upgrade I guess I changed to 
 version 5 now but this was not a problem during my last update.

 Any ideas? Thank you!

 Regards
 Thomas

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To 

[weewx-user] Re: Weewx don't work anymore after SD card restore, I don't know why?

['michael.k...@gmx.at' via weewx-user]

It will definitely help if you'd attach the log files as a whole, it
see>
ms >
the>
 lo>
g ab>
ove is not showing all the relevant data.
Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:41:33 UTC+1:

> pi@raspberrypi:~ $ apt policy weewx
> weewx:
>   Installed: 5.0.2-1
>   Candidate: 5.0.2-1
>
>
> Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:39:13 UTC+1:
>
>> here are some more information, something seems to be wrong with the 
>> gw1000 driver, but I changed nothing:
>>
>> pi@raspberrypi:~ $ systemctl status weewx*
>> ● weewx.service - WeeWX
>>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
>> preset:>
>>  Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36 
>> CET; 17mi>
>>Docs: https://weewx.com/docs
>> Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
>> status=4)
>>Main PID: 606 (code=exited, status=4)
>> CPU: 621ms
>>
>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:  
>>  s>
>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:  
>>Fil>
>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:  
>>  r>
>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:  
>>Fil>
>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:  
>>  r>
>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:  
>>  user.>
>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: Unable to 
>> load driv>
>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__:  
>>  Exiting...
>> Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Main process 
>> exited, cod>
>> Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Failed with result 
>> 'exit>
>> lines 1-18/18 (END)...skipping...
>> ● weewx.service - WeeWX
>>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
>> preset: enabled)
>>  Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36 
>> CET; 17min ago
>>Docs: https://weewx.com/docs
>> Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
>> status=4)
>>Main PID: 606 (code=exited, status=4)
>> CPU: 621ms
>>
>> Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:35:25 UTC+1:
>>
>>> Hello,
>>> I use weewx on a raspberry Pi 4. My system crashed and I had to go back 
>>> to an SD card image from January. It was a state were weewx was runing 
>>> normally.
>>> But now I don't know why weewx is not working anymore.
>>> I get no reaction for commands like 
>>>
>>> sudo /etc/init.d/weewx stop
>>> sudo /etc/init.d/weewx start
>>>
>>> debug = 1 and I don't see something in syslog:
>>>
>>> sudo tail -f /var/log/syslog | grep weewx 
>>>
>>> in January I had a weewx 4 and with apt upgrade I guess I changed to 
>>> version 5 now but this was not a problem during my last update.
>>>
>>> Any ideas? 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/a56838d6-6761-4706-bfc6-3af01b7a303an%40googlegroups.com.

[weewx-user] Re: Weewx don't work anymore after SD card restore, I don't know why?

[Thomas Hackler]

pi@raspberrypi:~ $ apt policy weewx
weewx:
  Installed: 5.0.2-1
  Candidate: 5.0.2-1


Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:39:13 UTC+1:

> here are some more information, something seems to be wrong with the 
> gw1000 driver, but I changed nothing:
>
> pi@raspberrypi:~ $ systemctl status weewx*
> ● weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
> preset:>
>  Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36 CET; 
> 17mi>
>Docs: https://weewx.com/docs
> Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
> status=4)
>Main PID: 606 (code=exited, status=4)
> CPU: 621ms
>
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
>s>
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
>  Fil>
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
>r>
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
>  Fil>
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
>r>
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:  
>  user.>
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: Unable to load 
> driv>
> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__:  
>  Exiting...
> Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Main process 
> exited, cod>
> Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Failed with result 
> 'exit>
> lines 1-18/18 (END)...skipping...
> ● weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
> preset: enabled)
>  Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36 CET; 
> 17min ago
>Docs: https://weewx.com/docs
> Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
> status=4)
>Main PID: 606 (code=exited, status=4)
> CPU: 621ms
>
> Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:35:25 UTC+1:
>
>> Hello,
>> I use weewx on a raspberry Pi 4. My system crashed and I had to go back 
>> to an SD card image from January. It was a state were weewx was runing 
>> normally.
>> But now I don't know why weewx is not working anymore.
>> I get no reaction for commands like 
>>
>> sudo /etc/init.d/weewx stop
>> sudo /etc/init.d/weewx start
>>
>> debug = 1 and I don't see something in syslog:
>>
>> sudo tail -f /var/log/syslog | grep weewx 
>>
>> in January I had a weewx 4 and with apt upgrade I guess I changed to 
>> version 5 now but this was not a problem during my last update.
>>
>> Any ideas? 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/6174f92c-8f6a-4dcc-ae29-89650bd74467n%40googlegroups.com.

[weewx-user] Re: Weewx don't work anymore after SD card restore, I don't know why?

[Thomas Hackler]

here are some more information, something seems to be wrong with the gw1000 
driver, but I changed nothing:

pi@raspberrypi:~ $ systemctl status weewx*
● weewx.service - WeeWX
 Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
preset:>
 Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36 CET; 
17mi>
   Docs: https://weewx.com/docs
Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
status=4)
   Main PID: 606 (code=exited, status=4)
CPU: 621ms

Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
   s>
Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
 Fil>
Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
   r>
Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
 Fil>
Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:    
   r>
Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine:  
 user.>
Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: Unable to load 
driv>
Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__:  
 Exiting...
Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Main process exited, 
cod>
Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Failed with result 
'exit>
lines 1-18/18 (END)...skipping...
● weewx.service - WeeWX
 Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36 CET; 
17min ago
   Docs: https://weewx.com/docs
Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
status=4)
   Main PID: 606 (code=exited, status=4)
CPU: 621ms

Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:35:25 UTC+1:

> Hello,
> I use weewx on a raspberry Pi 4. My system crashed and I had to go back to 
> an SD card image from January. It was a state were weewx was runing 
> normally.
> But now I don't know why weewx is not working anymore.
> I get no reaction for commands like 
>
> sudo /etc/init.d/weewx stop
> sudo /etc/init.d/weewx start
>
> debug = 1 and I don't see something in syslog:
>
> sudo tail -f /var/log/syslog | grep weewx 
>
> in January I had a weewx 4 and with apt upgrade I guess I changed to 
> version 5 now but this was not a problem during my last update.
>
> Any ideas? 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/d41a625f-b1ed-4feb-914f-86fbe0a133edn%40googlegroups.com.

[weewx-user] Weewx don't work anymore after SD card restore, I don't know why?

[Thomas Hackler]

Hello,
I use weewx on a raspberry Pi 4. My system crashed and I had to go back to 
an SD card image from January. It was a state were weewx was runing 
normally.
But now I don't know why weewx is not working anymore.
I get no reaction for commands like 

sudo /etc/init.d/weewx stop
sudo /etc/init.d/weewx start

debug = 1 and I don't see something in syslog:

sudo tail -f /var/log/syslog | grep weewx 

in January I had a weewx 4 and with apt upgrade I guess I changed to 
version 5 now but this was not a problem during my last update.

Any ideas? 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/5174210e-81c3-41d5-a798-759e655f665an%40googlegroups.com.

[weewx-user] Re: Can we upgrade to WeeWX 5.0x WITHOUT MAJOR RISK?

['michael.k...@gmx.at' via weewx-user]

...and keep the old installation running on the same machine!

michael.k...@gmx.at schrieb am Samstag, 17. Februar 2024 um 10:11:41 UTC+1:

> You can upgrade without any risk. Just follow the instructions in the 
> quickstart guide for pip: https://www.weewx.com/docs/5.0/quickstarts/pip/ 
> and install the new version in a venv, as described there.
>
> Your present installation won't be affected, as long they don't require 
> any exclusive access to resources, such as direct exclusive access to 
> devices, or servers on distinct local ports.
>
> Remy Lavabre schrieb am Samstag, 17. Februar 2024 um 09:59:19 UTC+1:
>
>> Good morning,
>>
>> I've been seeing various problems (mainly access rights?) for some time 
>> with the 5.x update.
>>
>> For a configuration in 4.10.2 on Pi with Bulleyes 64B, does the 
>> transition to 5.x present risks of malfunction with the use of a modified 
>> base skin (Seasons) but above all:
>>
>> - A personalized driver which retrieves Awekas data from the station via 
>> the internet as well as various other parameters from the Pi (temperature, 
>> memory, SSD status etc.) but also data on external counter modules;
>>
>> - An alarm generator (multialarm.py) allowing you to be notified based on 
>> precise weather criteria defined in advance
>>
>> - the excellent alltimeSeasons skin made by Glenn Mckechnie
>>
>>
>> With experience, are there checks to be made before to avoid surprises 
>> afterwards...?
>>
>> Thank you so much... ;-)
>>
>

-- 
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/b10c72cd-d5d4-4d4e-88f9-97aecd0ee2c7n%40googlegroups.com.

[weewx-user] Re: Can we upgrade to WeeWX 5.0x WITHOUT MAJOR RISK?

['michael.k...@gmx.at' via weewx-user]

You can upgrade without any risk. Just follow the instructions in the 
quickstart guide for pip: https://www.weewx.com/docs/5.0/quickstarts/pip/ 
and install the new version in a venv, as described there.

Your present installation won't be affected, as long they don't require any 
exclusive access to resources, such as direct exclusive access to devices, 
or servers on distinct local ports.

Remy Lavabre schrieb am Samstag, 17. Februar 2024 um 09:59:19 UTC+1:

> Good morning,
>
> I've been seeing various problems (mainly access rights?) for some time 
> with the 5.x update.
>
> For a configuration in 4.10.2 on Pi with Bulleyes 64B, does the transition 
> to 5.x present risks of malfunction with the use of a modified base skin 
> (Seasons) but above all:
>
> - A personalized driver which retrieves Awekas data from the station via 
> the internet as well as various other parameters from the Pi (temperature, 
> memory, SSD status etc.) but also data on external counter modules;
>
> - An alarm generator (multialarm.py) allowing you to be notified based on 
> precise weather criteria defined in advance
>
> - the excellent alltimeSeasons skin made by Glenn Mckechnie
>
>
> With experience, are there checks to be made before to avoid surprises 
> afterwards...?
>
> Thank you so much... ;-)
>

-- 
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/331e3c85-b76a-42e7-aadf-9011d3baad9en%40googlegroups.com.

[weewx-user] Can we upgrade to WeeWX 5.0x WITHOUT MAJOR RISK?

[Remy Lavabre]

Good morning,

I've been seeing various problems (mainly access rights?) for some time 
with the 5.x update.

For a configuration in 4.10.2 on Pi with Bulleyes 64B, does the transition 
to 5.x present risks of malfunction with the use of a modified base skin 
(Seasons) but above all:

- A personalized driver which retrieves Awekas data from the station via 
the internet as well as various other parameters from the Pi (temperature, 
memory, SSD status etc.) but also data on external counter modules;

- An alarm generator (multialarm.py) allowing you to be notified based on 
precise weather criteria defined in advance

- the excellent alltimeSeasons skin made by Glenn Mckechnie


With experience, are there checks to be made before to avoid surprises 
afterwards...?

Thank you so much... ;-)

-- 
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/e518f4f9-6fcb-4a9f-aeba-810781fd1ef7n%40googlegroups.com.

AW: [weewx-user] Display the first date entry in the database

[sschnidrig]

Hey Tom.

 

Hey Tom

Thanks for your help and explanation. With the $alltime.outTemp.firsttime it 
works perfectly

 

 

 

Von: weewx-user@googlegroups.com  Im Auftrag von 
Tom Keffer
Gesendet: Freitag, 16. Februar 2024 22:03
An: weewx-user@googlegroups.com
Betreff: Re: [weewx-user] Display the first date entry in the database

 

Figured out why my first suggestion did not work. A long time ago, if you 
wanted the start time of an aggregation, you used $alltime.dateTime, instead of 
$alltime.start. To keep backwards compatibility, I defined dateTime=start, so 
the net effect is that 

 

$alltime.dateTime.min

 

is equivalent to

 

$alltime.start.min

 

which is nonsense. Hence the error.

 

It may be time to retire the backwards compatibility shim.

 

-tk

 

 

On Fri, Feb 16, 2024 at 12:02 PM Tom Keffer mailto:tkef...@gmail.com> > wrote:

Not sure why that doesn't work --- I'll have to investigate.

 

But, the sure fire way to do this is with

 

$alltime.start

 

See the section start, end, and dateTime 

 .

 

 

On Fri, Feb 16, 2024 at 7:16 AM Meteo Oberwallis mailto:sschnid...@bluewin.ch> > wrote:

Hello Tom.

 

It`s not working

 

Feb 16 16:14:28 wetterstation wee_reports[11564] ERROR weewx.cheetahgenerator: 
 Ignoring template /etc/weewx/skins/Belchertown/about/index.html.tmpl
Feb 16 16:14:28 wetterstation wee_reports[11564] ERROR weewx.cheetahgenerator: 
 Reason: cannot find 'mintime' while searching for 
'alltime.dateTime.mintime  e'
Feb 16 16:14:28 wetterstation wee_reports[11564] ERROR weewx.cheetahgenerator: 
 To debug, try inserting '#errorCatcher Echo' at top of template
Feb 16 16:14:32 wetterstation wee_reports[11564] INFO weewx.cheetahgenerator: 
Generated 11 files for report Belchertown in 13.56 seconds
Feb 16 16:14:32 wetterstation wee_reports[11564] INFO weewx.reportengine: 
Copied 39 files to /var/www/html/weewx/user

 

 

Tom Keffer schrieb am Freitag, 16. Februar 2024 um 16:12:14 UTC+1:

On Fri, Feb 16, 2024 at 6:37 AM Meteo Oberwallis mailto:sschn...@bluewin.ch> > wrote:

Hello.
Thank you for the answers. The $alltime.outTemp.firsttime.raw works. Now I have 
to format the whole thing so that I can get it into a “normal date”. Can anyone 
else give me help?

 

 

$alltime.dateTime.mintime

 

 

-- 
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/930e7c83-39cd-4e8c-aa5d-07090aad8aedn%40googlegroups.com
 

 .

-- 
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/foZYSxdc0Cw/unsubscribe.
To unsubscribe from this group and all its topics, 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/CAPq0zECp%2BJVBFapDb%2Bnh38%3DW%2BXP8Srt4x27rbk4Fi1ZEa%3DAw2w%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/001b01da617b%24fe69cff0%24fb3d6fd0%24%40bluewin.ch.