Re: [weewx-user] Difference between aggregation types has_data and not_null

[Karen K]

Ah.

Tom Keffer schrieb am Samstag, 24. Februar 2024 um 00:00:07 UTC+1:

You should not have to implement either.


For WeeWX 5.0 people experienced that the "GTS", "yearGDD", and "seasonGDD" 
observation types (XTypes calculated out of "outTemp") were not graphed any 
more. After an explicit implementation of "not_null" the graph appeared 
again.

   - https://github.com/roe-dl/weewx-GTS/issues/26
   - https://github.com/roe-dl/weewx-GTS/blob/master/bin/user/GTS.py
   
tags.ObservationBinder.has_data has changed from WeeWX 4.X to 5.0. The old 
version only looked into the database by calling 
self.db_lookup(self.data_binding).has_data(self.obs_type, 
self.timespan). The new version is:

@property
def has_data(self):
db_manager = self.db_lookup(self.data_binding)
# First see if the type exists in the database.
if db_manager.exists(self.obs_type):
# Yes. Is it non-null?
val = bool(weewx.xtypes.get_aggregate(self.obs_type, 
self.timespan,
  'not_null', 
db_manager)[0])
else:
# Nope. Try the xtypes system.
val = weewx.xtypes.has_data(self.obs_type, self.timespan, 
db_manager)
return val

If you look into weewx.xtypes.get_aggregate(...,'not_null',...) and 
weewx.xtypes.has_data() they do almost the same. There is a loop over xtypes, 
and for each xtype get_aggreate() is called. If I understand the code 
right, the result of the has_data property in WeeWX 5.0 is independent of 
the value of the condition of the if statement. And the database lookup, 
that is used in WeeWX 4.X, has gone at all.

-- 
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/e5010568-d6cd-4297-a608-89d1dee91bf0n%40googlegroups.com.

Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

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

Interesting insights. I've always been using the official power supplies 
and SD-Cards and flash drives from major brands. And they always got me 
brand new cards, as the were under warranty. Also, we have super stable 
power supply here. Often years without power surge, the last black some 
years ago, and this only locally. Despite that, my devices are connected to 
a UPS since a while, and I had still issues.

Tom Keffer schrieb am Samstag, 24. Februar 2024 um 00:25:43 UTC+1:

> I'm with Vince. I believe the micro-SD cards are perfectly reliable. As an 
> experiment I've been running WeeWX on an RPi B+ with an SD card for over 9 
> years. The key is a reliable power supply connected to a UPS. Webpage: 
> https://www.threefools.org/weewx/status/index.html
>
> I'm getting tired of waiting for it to break --- it's taking up too much 
> space on my desk. If it doesn't break soon, I'll probably end the 
> experiment.
>
> On Fri, Feb 23, 2024 at 11:41 AM Gábor Szabados  
> wrote:
>
>> Shamefully, running a bit old version of WeeWX, from 2019, on a Raspberry 
>> Pi Zero W, which has Raspbian and mainly default settings WeeWX. The same 
>> SD card since. The Pi operates in an interceptor way, it creates a hotspot 
>> for the weather station which sends all information to WU, WeeWX with 
>> Interceptor intercepts it, meanwhile the Pi connects to the local network 
>> by Wifi as well. A bit over complicated, but it was before the FineOffset 
>> clones were offering a custom URL option in their firmware.
>>
>> It was a minimum budget project, still runs without any issues. (Knock on 
>> wood.)
>>
>> Graham Knights a következőt írta (2024. február 23., péntek, 19:43:49 
>> UTC+1):
>>
>>> I've been running weewx on a RPi 3B+ for just over 5 years, but after a 
>>> couple of other pi's died for various reasons (SD card being one of them), 
>>> I've moved it to a debian install on a VM in a Windows 10 Pro machine (runs 
>>> my automation server).  Hardware is a Lenovo ThinkCentre M700 Tiny which I 
>>> find perfect for running a couple of small linux VM's on it.  Low power, 
>>> tiny, quiet, and versatile, and Lenovo hardware has been good to me over 
>>> the years. Machines are cheap to find on ebay/amazon, probably less than a 
>>> new Pi by the time you add all the parts.
>>>
>>> On Friday, February 23, 2024 at 9:46:42 AM UTC-8 vince wrote:
>>>
 If I was starting clean 'today', I would probably just throw $125 at it 
 and get one of those little beelink boxes amazon sells and toss linux on 
 it.

 But to answer - currently on a 4GB pi4 to sd card for 2+ years with no 
 issues.

 Stability issues on a pi are almost always bad power supply these 
 days.  I've never had a micro-sd fail on a pi3, 3+, 4, or pi5.  Never.   I 
 did burn a 'lot' of big sd cards on the old modelB over the years but 
 again 
 that was related to either (a) cheapo cards or (b) cheapo power adaptors 
 not on surge suppressors.  My one remaining modelB is still happily 
 shooting my timelapse snaps for over a decade now.

 I do make one change to the pi setups to protect the sd card.  I mount 
 some filesystems as tmpfs so the sd can't be hammered by log writes by 
 appending this to /etc/stab

 # put logs and tmp dirs in ramdisk too ---
 tmpfs   /tmptmpfs   
 defaults,nosuid,mode=0755,nodev,noatime   0   0
 tmpfs   /var/logtmpfs   
 defaults,nosuid,mode=0755,nodev,noatime   0   0
 tmpfs   /var/tmptmpfs   
 defaults,nosuid,mode=0755,nodev,noatime   0   0
 #-

 Yes - if I reboot I lose the system logs.  But I basically never reboot.

 I might add that I do install rsyslog and the matching logrotate.d and 
 rsyslog.d files from util/ to my v5 setup, so weewx logs to under 
 /var/log/weewx in that tmpfs partition, so I just run debug=1 here because 
 it's not going to touch the actual sd card.  Super stable.

 -- 
>> 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/86c8becf-edfb-4264-b93f-2626ed9adfacn%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/08904aca-2678-4467-a81e-7972496abb15n%40googlegroups.com.

Re: [weewx-user] Difference between aggregation types has_data and not_null

[Karen K]

Ah.

Tom Keffer schrieb am Samstag, 24. Februar 2024 um 00:00:07 UTC+1:

You should not have to implement either.


For WeeWX 5.0 people experienced that the "GTS", "yearGDD", and "seasonGDD" 
observation types (XTypes calculated out of "outTemp")  were not graphed 
any more. After an explicit implementation of "not_null" the graph appeared 
again. 

https://github.com/roe-dl/weewx-GTS/issues/26

https://github.com/roe-dl/weewx-GTS/blob/master/bin/user/GTS.py




-- 
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/270bcad8-5fce-4356-a921-33ac77d9dc42n%40googlegroups.com.

Re: [weewx-user] Interceptor + weewx + Bresser

[Remy LAVABRE]

stephane hello,
I said something stupid to you previously. interceptor intercepts at the
wifi level and not as I thought at the 400 or 800 Mhz radio level... sorry!

so normal that you have inTemp and barometer! :-)

I too have a Bresser station and retrieve data automatically from Awekas in
the absence of a USB output. I have several exterior sensors and there is a
somewhat similar problem. the hygrometer values ​​of the probes are
retrieved as hygrometer values ​​of the floor probes while the temperatures
are retrieved as temperatures of external probes.

I reported this anomaly to Bresser in France who already reported it almost
a year ago, knowing that I was not the only one to have reported it to them.
I also reported the problem to Germany who basically told me it was
"normal" operation without explanation

As I wrote a driver for weewx which retrieves data directly from Awekas at
regular intervals, I reverse the value fields myself...

Le ven. 23 févr. 2024, 23:19, sc.lep...@gmail.com 
a écrit :

> Hello
> I use  weewx  with interceptor :
>
> Feb 23 23:09:01 meteo-Ubuntu weewx-BRESSER[63190] DEBUG user.interceptor:
> raw packet: {'dateTime': 1708726142, 'usUnits': 1, 'rain_total': 0.09,
> 'barometer': 29.99, 'temperature_out': 34.7, 'humidity_out': 90.0,
> 'wind_speed': 0.0, 'wind_gust': 0.0, 'wind_dir': 138.0, 'dewpoint': 32.0,
> 'temperature_in': 66.2, 'humidity_in': 57.0, 'uv': 0.0, 'solar_radiation':
> 0.0, 'soil_temperature_1': 66.2, 'soil_temperature_2': 70.8,
> 'soil_moisture_2': 60.0, 'rain': None}
> Feb 23 23:09:01 meteo-Ubuntu weewx-BRESSER[63190] DEBUG user.interceptor:
> mapped packet: {'dateTime': 1708726142, 'usUnits': 1, 'barometer': 29.99,
> 'outHumidity': 90.0, 'inHumidity': 57.0, 'outTemp': 34.7, 'inTemp': 66.2,
> 'windSpeed': 0.0, 'windGust': 0.0, 'windDir': 138.0, 'radiation': 0.0,
> 'dewpoint': 32.0, 'rain': None, 'UV': 0.0, 'soilTemp1': 66.2, 'soilTemp2':
> 70.8, 'soilMoist2': 60.0}
>
> I dont understand how to use :
> soilTemp1': 66.2, '
> soilTemp2': 70.8, '
> soil_moist1': 60.0,
> soil_moist2': 60.0,
>
> I've 2 temperatures probes
>
> Can someone explain me how to add this in weewx.conf ?
>
> in section  :
>  [[sensor_map_extensions]]
> ???inTemp = temperature_1
>  ???   inHumidity = humidity_1
>  ???   outTemp = temperature_4
>   ???  outHumidity = humidity_4
>
>
> Thanks a lot  ;)
>
> Stephane
>
> --
> 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/c851119a-b274-4ecd-99a3-605d2e393946n%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/CADhm9Yf4z%3DAm12NEJYBFe6vDQbAUWz-H74mNWnenaQGQ5SdQOg%40mail.gmail.com.

Re: [weewx-user] Interceptor + weewx + Bresser

[Remy LAVABRE]

What is the Bresser station you use Stéphane ?
Normaly no inTemp with bresser and interceptor -> inTemp is given with by
the base and so not radio send as the barometer value...


Le ven. 23 févr. 2024, 23:19, sc.lep...@gmail.com 
a écrit :

> Hello
> I use  weewx  with interceptor :
>
> Feb 23 23:09:01 meteo-Ubuntu weewx-BRESSER[63190] DEBUG user.interceptor:
> raw packet: {'dateTime': 1708726142, 'usUnits': 1, 'rain_total': 0.09,
> 'barometer': 29.99, 'temperature_out': 34.7, 'humidity_out': 90.0,
> 'wind_speed': 0.0, 'wind_gust': 0.0, 'wind_dir': 138.0, 'dewpoint': 32.0,
> 'temperature_in': 66.2, 'humidity_in': 57.0, 'uv': 0.0, 'solar_radiation':
> 0.0, 'soil_temperature_1': 66.2, 'soil_temperature_2': 70.8,
> 'soil_moisture_2': 60.0, 'rain': None}
> Feb 23 23:09:01 meteo-Ubuntu weewx-BRESSER[63190] DEBUG user.interceptor:
> mapped packet: {'dateTime': 1708726142, 'usUnits': 1, 'barometer': 29.99,
> 'outHumidity': 90.0, 'inHumidity': 57.0, 'outTemp': 34.7, 'inTemp': 66.2,
> 'windSpeed': 0.0, 'windGust': 0.0, 'windDir': 138.0, 'radiation': 0.0,
> 'dewpoint': 32.0, 'rain': None, 'UV': 0.0, 'soilTemp1': 66.2, 'soilTemp2':
> 70.8, 'soilMoist2': 60.0}
>
> I dont understand how to use :
> soilTemp1': 66.2, '
> soilTemp2': 70.8, '
> soil_moist1': 60.0,
> soil_moist2': 60.0,
>
> I've 2 temperatures probes
>
> Can someone explain me how to add this in weewx.conf ?
>
> in section  :
>  [[sensor_map_extensions]]
> ???inTemp = temperature_1
>  ???   inHumidity = humidity_1
>  ???   outTemp = temperature_4
>   ???  outHumidity = humidity_4
>
>
> Thanks a lot  ;)
>
> Stephane
>
> --
> 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/c851119a-b274-4ecd-99a3-605d2e393946n%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/CADhm9Yd2YgOuSN%3D8E8%2Bdn78BQJYi12%3Dgaqe1uXGiWBvB%2BriOUw%40mail.gmail.com.

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

[Jamie Stephens]

I'm not code savvy but I seem to recall I personally was running this fork 
from tkeffer that he ported to python 3 
https://github.com/tkeffer/weatherflow-udp/tree/master
I might roll back tot hat and see if the issue go away, I don't think it 
was ever committed to the main

On Friday, February 23, 2024 at 8:29:23 PM UTC-5 vince wrote:

> Source is at 
> https://github.com/captain-coredump/weatherflow-udp/blob/master/bin/user/weatherflowudp.py
>  if 
> some driver experts wanted to suggest fixes. This one is beyond me other 
> than to suggest that since weewx v5 does not support python2 anymore that 
> perhaps the try/except block needs something tweaked to deal with what I'm 
> guessing (like totally guessing) is garbage-in a little more gracefully 
> (anybody ?)
>
> if timeouterr == 0:
> try:
> m0 = str(m[0],'utf-8').replace(",null",",None")# 
> Python 3
> except:
>
> m0 = m[0].replace(",null",",None") # 
> Python 2
> m1=''
> try:
> m1=eval(m0)
> except SyntaxError:
> logerr('Packet parse error: %s' % m0)
> if self._log_raw_packets:
> loginf('raw packet: %s' % m1)
> m2=parseUDPPacket(m1)
> m3=sendMyLoopPacket(m2, self._sensor_map)
> if len(m3) > 2:
> yield m3
>
> On Friday, February 23, 2024 at 12:10:54 PM UTC-8 Jamie Stephens wrote:
>
> i went ahead and opened up a issue with the driver, had another crash today
>
>

-- 
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/8b15753c-088a-449b-87af-d7b37de9a15en%40googlegroups.com.

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

[vince]

Source is at 
https://github.com/captain-coredump/weatherflow-udp/blob/master/bin/user/weatherflowudp.py
 if 
some driver experts wanted to suggest fixes. This one is beyond me other 
than to suggest that since weewx v5 does not support python2 anymore that 
perhaps the try/except block needs something tweaked to deal with what I'm 
guessing (like totally guessing) is garbage-in a little more gracefully 
(anybody ?)

if timeouterr == 0:
try:
m0 = str(m[0],'utf-8').replace(",null",",None")# 
Python 3
except:
m0 = m[0].replace(",null",",None") # 
Python 2
m1=''
try:
m1=eval(m0)
except SyntaxError:
logerr('Packet parse error: %s' % m0)
if self._log_raw_packets:
loginf('raw packet: %s' % m1)
m2=parseUDPPacket(m1)
m3=sendMyLoopPacket(m2, self._sensor_map)
if len(m3) > 2:
yield m3

On Friday, February 23, 2024 at 12:10:54 PM UTC-8 Jamie Stephens wrote:

i went ahead and opened up a issue with the driver, had another crash today

-- 
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/091809f3-9964-4bc5-a5fd-8b407425eb52n%40googlegroups.com.

[weewx-user] Re: Failed publish report by weewx-owm

[vince]

Which precise driver are you using ? 


On Friday, February 23, 2024 at 1:37:42 PM UTC-8 Tomasz J wrote:

> Hi
> Anyone had a similar problem? 
>
> *ERROR weewx.restx: OWM: Failed to publish record 2024-02-23 21:10:00 CET 
> (1708719000): Failed upload after 3 tries*
>
> WeeWX works without any problems, no errors, weewx.conf owm data generated 
> yesterday 

-- 
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/7f80e6d0-a23b-4529-8482-3a5241248ee0n%40googlegroups.com.

Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

[Tom Keffer]

I'm with Vince. I believe the micro-SD cards are perfectly reliable. As an
experiment I've been running WeeWX on an RPi B+ with an SD card for over 9
years. The key is a reliable power supply connected to a UPS. Webpage:
https://www.threefools.org/weewx/status/index.html

I'm getting tired of waiting for it to break --- it's taking up too much
space on my desk. If it doesn't break soon, I'll probably end the
experiment.

On Fri, Feb 23, 2024 at 11:41 AM Gábor Szabados <
gabor.szabados.m...@gmail.com> wrote:

> Shamefully, running a bit old version of WeeWX, from 2019, on a Raspberry
> Pi Zero W, which has Raspbian and mainly default settings WeeWX. The same
> SD card since. The Pi operates in an interceptor way, it creates a hotspot
> for the weather station which sends all information to WU, WeeWX with
> Interceptor intercepts it, meanwhile the Pi connects to the local network
> by Wifi as well. A bit over complicated, but it was before the FineOffset
> clones were offering a custom URL option in their firmware.
>
> It was a minimum budget project, still runs without any issues. (Knock on
> wood.)
>
> Graham Knights a következőt írta (2024. február 23., péntek, 19:43:49
> UTC+1):
>
>> I've been running weewx on a RPi 3B+ for just over 5 years, but after a
>> couple of other pi's died for various reasons (SD card being one of them),
>> I've moved it to a debian install on a VM in a Windows 10 Pro machine (runs
>> my automation server).  Hardware is a Lenovo ThinkCentre M700 Tiny which I
>> find perfect for running a couple of small linux VM's on it.  Low power,
>> tiny, quiet, and versatile, and Lenovo hardware has been good to me over
>> the years. Machines are cheap to find on ebay/amazon, probably less than a
>> new Pi by the time you add all the parts.
>>
>> On Friday, February 23, 2024 at 9:46:42 AM UTC-8 vince wrote:
>>
>>> If I was starting clean 'today', I would probably just throw $125 at it
>>> and get one of those little beelink boxes amazon sells and toss linux on it.
>>>
>>> But to answer - currently on a 4GB pi4 to sd card for 2+ years with no
>>> issues.
>>>
>>> Stability issues on a pi are almost always bad power supply these days.
>>> I've never had a micro-sd fail on a pi3, 3+, 4, or pi5.  Never.   I did
>>> burn a 'lot' of big sd cards on the old modelB over the years but again
>>> that was related to either (a) cheapo cards or (b) cheapo power adaptors
>>> not on surge suppressors.  My one remaining modelB is still happily
>>> shooting my timelapse snaps for over a decade now.
>>>
>>> I do make one change to the pi setups to protect the sd card.  I mount
>>> some filesystems as tmpfs so the sd can't be hammered by log writes by
>>> appending this to /etc/stab
>>>
>>> # put logs and tmp dirs in ramdisk too ---
>>> tmpfs   /tmptmpfs
>>> defaults,nosuid,mode=0755,nodev,noatime   0   0
>>> tmpfs   /var/logtmpfs
>>> defaults,nosuid,mode=0755,nodev,noatime   0   0
>>> tmpfs   /var/tmptmpfs
>>> defaults,nosuid,mode=0755,nodev,noatime   0   0
>>> #-
>>>
>>> Yes - if I reboot I lose the system logs.  But I basically never reboot.
>>>
>>> I might add that I do install rsyslog and the matching logrotate.d and
>>> rsyslog.d files from util/ to my v5 setup, so weewx logs to under
>>> /var/log/weewx in that tmpfs partition, so I just run debug=1 here because
>>> it's not going to touch the actual sd card.  Super stable.
>>>
>>> --
> 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/86c8becf-edfb-4264-b93f-2626ed9adfacn%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/CAPq0zEANbQMnA4NNC7f1Ps3eMhUUsE5qEBp%2BeU9fLrSvo2qQcg%40mail.gmail.com.

Re: [weewx-user] Difference between aggregation types has_data and not_null

[Tom Keffer]

You should not have to implement either.

The implementation of has_data runs a not_null query over the aggregation
period. In turn not_null either consults the database or, if it's an xtype,
runs get_scalar() over the aggregation period. The first non-null value
seen causes it to return True.

Of course, that's a fairly compute intensive way of checking for non-null
xtype values, but it will work for any xtype. One could optimize the
calculation with a specialized version for your type, but so far I haven't
heard of a case where it's needed.

-tk


On Fri, Feb 23, 2024 at 7:48 AM Karen K  wrote:

> Do I have to implement both the not_null and has_data aggregation in an
> XType extension?
>
>
> Tom Keffer schrieb am Freitag, 23. Februar 2024 um 14:01:45 UTC+1:
>
> The aggregation not_null does not check first to see if the type exists.
> If you know the type exists, it's slightly faster.
>
> In practice, I don't think it's very useful. I may remove it from the
> documentation.
>
> On Fri, Feb 23, 2024 at 3:48 AM Karen K  wrote:
>
> What is the difference between the aggregation types has_data and not_null
> according to the documentation in
> http://weewx.com/docs/5.0/reference/aggtypes/.
>
> --
> 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/8abfecfb-7fe5-4e6c-aace-540ed933ea8en%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/CAPq0zEAGi1sLuP_23WvoXMc3F1eusA1LK45OMVCtgxCRq39rPQ%40mail.gmail.com.

[weewx-user] Interceptor + weewx + Bresser

[sc.lep...@gmail.com]

Hello 
I use  weewx  with interceptor : 

Feb 23 23:09:01 meteo-Ubuntu weewx-BRESSER[63190] DEBUG user.interceptor: 
raw packet: {'dateTime': 1708726142, 'usUnits': 1, 'rain_total': 0.09, 
'barometer': 29.99, 'temperature_out': 34.7, 'humidity_out': 90.0, 
'wind_speed': 0.0, 'wind_gust': 0.0, 'wind_dir': 138.0, 'dewpoint': 32.0, 
'temperature_in': 66.2, 'humidity_in': 57.0, 'uv': 0.0, 'solar_radiation': 
0.0, 'soil_temperature_1': 66.2, 'soil_temperature_2': 70.8, 
'soil_moisture_2': 60.0, 'rain': None}
Feb 23 23:09:01 meteo-Ubuntu weewx-BRESSER[63190] DEBUG user.interceptor: 
mapped packet: {'dateTime': 1708726142, 'usUnits': 1, 'barometer': 29.99, 
'outHumidity': 90.0, 'inHumidity': 57.0, 'outTemp': 34.7, 'inTemp': 66.2, 
'windSpeed': 0.0, 'windGust': 0.0, 'windDir': 138.0, 'radiation': 0.0, 
'dewpoint': 32.0, 'rain': None, 'UV': 0.0, 'soilTemp1': 66.2, 'soilTemp2': 
70.8, 'soilMoist2': 60.0}

I dont understand how to use :
soilTemp1': 66.2, '
soilTemp2': 70.8, '
soil_moist1': 60.0, 
soil_moist2': 60.0, 

I've 2 temperatures probes

Can someone explain me how to add this in weewx.conf ? 

in section  :
 [[sensor_map_extensions]]
???inTemp = temperature_1
 ???   inHumidity = humidity_1
 ???   outTemp = temperature_4
  ???  outHumidity = humidity_4


Thanks a lot  ;) 

Stephane

-- 
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/c851119a-b274-4ecd-99a3-605d2e393946n%40googlegroups.com.

[weewx-user] Failed publish report by weewx-owm

[Tomasz J]

 Hi
Anyone had a similar problem? 

*ERROR weewx.restx: OWM: Failed to publish record 2024-02-23 21:10:00 CET 
(1708719000): Failed upload after 3 tries*

WeeWX works without any problems, no errors, weewx.conf owm data generated 
yesterday 

-- 
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/35cbed7a-8066-4697-a5d2-fcb82e06ce2en%40googlegroups.com.

Re: [weewx-user] updated to 5.0.1 still no joy

[Glen N]

Thanks,
I got it to run again, by restarting weewx???

I will keep an eye on it and it if plays up again come back for help.
Glen

On Fri, 23 Feb 2024 at 05:44, vince  wrote:

> You're going to need to share your weewx.conf file for this one.
> You have to be referencing gpio stuff somewhere under the hood.
>
> Running 'weectl extension list' would help explain your setup too
>
> On Thursday, February 22, 2024 at 2:18:28 AM UTC-8 Glen N wrote:
>
>> After updating DietPi to version 9.1.1
>>
>> I am getting GPIOzero BadPinFactory errors again. I tried commenting out
>> the weewx user in the service file as above, but the error remains.
>>
>> ● weewx.service - WeeWX
>>
>>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor
>> preset: enabled)
>>  Active: failed (Result: exit-code) since Thu 2024-02-22 21:02:32
>> AEDT; 12min ago
>>Docs: https://weewx.com/docs
>>Main PID: 23495 (code=exited, status=1/FAILURE)
>> CPU: 1.834s
>>
>> Feb 22 21:02:32 NapsberryPi weewxd[23495]:   File
>> "/usr/lib/python3/dist-packages/gpiozero/devices.py", line 291, in
>> _default_pin_factory
>> Feb 22 21:02:32 NapsberryPi weewxd[23495]: raise
>> BadPinFactory('Unable to load any default pin factory!')
>> Feb 22 21:02:32 NapsberryPi weewxd[23495]: gpiozero.exc.BadPinFactory:
>> Unable to load any default pin factory!
>> Feb 22 21:02:32 NapsberryPi weewxd[23495]: CRITICAL __main__: 
>>  File "/usr/lib/python3/dist-packages/gpiozero/devices.py", line 291, in
>> _default_pin_factory
>> Feb 22 21:02:32 NapsberryPi weewxd[23495]: CRITICAL __main__: 
>>raise BadPinFactory('Unable to load any default pin factory!')
>> Feb 22 21:02:32 NapsberryPi weewxd[23495]: CRITICAL __main__: 
>>  gpiozero.exc.BadPinFactory: Unable to load any default pin factory!
>> Feb 22 21:02:32 NapsberryPi weewxd[23495]: CRITICAL __main__: 
>>  Exiting.
>> Feb 22 21:02:32 NapsberryPi systemd[1]: weewx.service: Main process
>> exited, code=exited, status=1/FAILURE
>> Feb 22 21:02:32 NapsberryPi systemd[1]: weewx.service: Failed with result
>> 'exit-code'.
>> Feb 22 21:02:32 NapsberryPi systemd[1]: weewx.service: Consumed 1.834s
>> CPU time.
>>
>> On Monday 12 February 2024 at 1:01:24 pm UTC+11 Glen N wrote:
>>
>>> I was having a no start problem after upgrading RPi3B running DietPi. I
>>> tried Tom's suggestion and it fixed the problem.
>>>
>>> Prior to the "fix" my log file showed:
>>> -- Journal begins at Mon 2024-02-12 11:47:21 AEDT, ends at Mon
>>> 2024-02-12 12:40:34 AEDT. --
>>> Feb 12 11:47:23 SystemName systemd[1]: Started WeeWX.
>>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Initializing
>>> weewxd version 5.0.1
>>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Command line:
>>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Using Python
>>> 3.9.2 (default, Feb 28 2021, 17:03:44)
>>>  [GCC 10.2.1 20210110]
>>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Located at
>>> /usr/bin/python3
>>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Platform
>>> Linux-6.1.21-v8+-aarch64-with-glibc2.31
>>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Locale:
>>> 'en_AU.UTF-8'
>>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Entry path:
>>> /usr/share/weewx/weewxd.py
>>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: WEEWX_ROOT:
>>> /etc/weewx
>>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Configuration
>>> file: /etc/weewx/weewx.conf
>>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: User module:
>>> /etc/weewx/bin/user
>>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Debug: 0
>>> Feb 12 11:47:24 SystemName weewxd[309]: INFO weewx.engine: Loading
>>> station type FineOffsetUSB (weewx.drivers.fousb)
>>> Feb 12 11:47:24 SystemName weewxd[309]: INFO weewx.drivers.fousb: driver
>>> version is 1.3
>>> Feb 12 11:47:24 SystemName weewxd[309]: INFO weewx.drivers.fousb:
>>> polling mode is PERIODIC
>>> Feb 12 11:47:24 SystemName weewxd[309]: INFO weewx.drivers.fousb:
>>> polling interval is 60
>>> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.drivers.fousb: found
>>> station on USB bus= device=
>>> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.engine: StdConvert
>>> target unit is 0x11
>>> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.wxservices:
>>> StdWXCalculate will use data binding wx_binding
>>> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.engine: Archive will
>>> use data binding wx_binding
>>> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.engine: Record
>>> generation will be attempted in 'software'
>>> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.engine: Using archive
>>> interval of 300 seconds (software record generation)
>>> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.restx:
>>> StationRegistry: Station will not be registered: no station_url 

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

[Jamie Stephens]

i went ahead and opened up a issue with the driver, had another crash today

On Thursday, February 22, 2024 at 1:20:16 PM UTC-5 vince wrote:

> Jamie - I didn't change anything related to how the driver actually works. 
>  I just added one line to hopefully get it to register vs. v5 weewx.  The 
> map shows a few v5 sites using that driver now, so that part seems to be 
> working.
>
> On Thursday, February 22, 2024 at 7:24:23 AM UTC-8 Jamie Stephens wrote:
>
>> Thanks Tom, this is the new updated driver that Vince got pushed on this 
>> thread. maybe it was a one off 
>>
>> On Thursday, February 22, 2024 at 10:07:45 AM UTC-5 Tom Keffer wrote:
>>
>>> It looks like the author of the driver is trying to insert a string into 
>>> a byte array. You should file an issue on the repository's issue list.
>>>
>>> On Thu, Feb 22, 2024 at 6:00 AM Jamie Stephens  
>>> wrote:
>>>
 i manually restarted it and it's running right now just the registry 
 push error but not exited 
 Feb 22 08:50:19 weewx weewxd[68909]: ERROR weewx.restx: 
 StationRegistry: Failed to publish record 2024-02-22 08:50:00 EST 
 (17086098>

 will report back if weewx crashes again

 On Monday, February 19, 2024 at 7:09:16 PM UTC-5 Jamie Stephens wrote:

> Thanks for the fix, I didn't;t even noticed it was not working
>
> On Monday, February 19, 2024 at 4:25:28 AM UTC-5 Ton Karsten wrote:
>
>> Thank you for resolving the error message.
>>
>> Op ma 19 feb 2024 om 01:36 schreef bell...@gmail.com <
>> bell...@gmail.com>:
>>
>>> Thanks for pushing it over the goal line. Always the hardest part.
>>>
>>> On Sunday 18 February 2024 at 19:33:41 UTC-5 vince wrote:
>>>
 Update - the upstream author was nice enough to merge my PR for 
 this problem, so you can simply upgrade your driver to the latest 
 version 
 and your station registration should work again with weewx v5.

 weectl extension install 
 https://github.com/captain-coredump/weatherflow-udp/archive/master.zip
 sudo systemctl restart weewx

 After upgrading your driver you should see the following output 
 from 'weectl extension list':

 Extension NameVersion   Description
 weatherflowudp1.10.2Capture data from WeatherFlow Bridge 
 via UDP broadcast packets

 Thanks again Rich for the nudge(s) !!!

 -- 
>>> 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/9c2ecfe9-0b41-4b33-9295-fc6e9edf0db3n%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+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/2f38f991-b58b-4a9c-ad95-21a63311bb90n%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/a4287633-30a6-490a-9621-c2ee3c6a5323n%40googlegroups.com.

[weewx-user] Re: Seeking Data Logging Options

[Karen K]

What do you mean by "logging"? WeeWX, as it is shipped, stores the readings 
to a database. You can then take that database and do what you have to do 
with it. If you use the default settings, that database is a SQLITE file, 
which can be read and processed by a lot of other software.

-- 
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/2b53f2ff-2615-4c2f-8e1e-02ca8e05e745n%40googlegroups.com.

Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

[Gábor Szabados]

Shamefully, running a bit old version of WeeWX, from 2019, on a Raspberry 
Pi Zero W, which has Raspbian and mainly default settings WeeWX. The same 
SD card since. The Pi operates in an interceptor way, it creates a hotspot 
for the weather station which sends all information to WU, WeeWX with 
Interceptor intercepts it, meanwhile the Pi connects to the local network 
by Wifi as well. A bit over complicated, but it was before the FineOffset 
clones were offering a custom URL option in their firmware.

It was a minimum budget project, still runs without any issues. (Knock on 
wood.)

Graham Knights a következőt írta (2024. február 23., péntek, 19:43:49 
UTC+1):

> I've been running weewx on a RPi 3B+ for just over 5 years, but after a 
> couple of other pi's died for various reasons (SD card being one of them), 
> I've moved it to a debian install on a VM in a Windows 10 Pro machine (runs 
> my automation server).  Hardware is a Lenovo ThinkCentre M700 Tiny which I 
> find perfect for running a couple of small linux VM's on it.  Low power, 
> tiny, quiet, and versatile, and Lenovo hardware has been good to me over 
> the years. Machines are cheap to find on ebay/amazon, probably less than a 
> new Pi by the time you add all the parts.
>
> On Friday, February 23, 2024 at 9:46:42 AM UTC-8 vince wrote:
>
>> If I was starting clean 'today', I would probably just throw $125 at it 
>> and get one of those little beelink boxes amazon sells and toss linux on it.
>>
>> But to answer - currently on a 4GB pi4 to sd card for 2+ years with no 
>> issues.
>>
>> Stability issues on a pi are almost always bad power supply these days. 
>>  I've never had a micro-sd fail on a pi3, 3+, 4, or pi5.  Never.   I did 
>> burn a 'lot' of big sd cards on the old modelB over the years but again 
>> that was related to either (a) cheapo cards or (b) cheapo power adaptors 
>> not on surge suppressors.  My one remaining modelB is still happily 
>> shooting my timelapse snaps for over a decade now.
>>
>> I do make one change to the pi setups to protect the sd card.  I mount 
>> some filesystems as tmpfs so the sd can't be hammered by log writes by 
>> appending this to /etc/stab
>>
>> # put logs and tmp dirs in ramdisk too ---
>> tmpfs   /tmptmpfs   
>> defaults,nosuid,mode=0755,nodev,noatime   0   0
>> tmpfs   /var/logtmpfs   
>> defaults,nosuid,mode=0755,nodev,noatime   0   0
>> tmpfs   /var/tmptmpfs   
>> defaults,nosuid,mode=0755,nodev,noatime   0   0
>> #-
>>
>> Yes - if I reboot I lose the system logs.  But I basically never reboot.
>>
>> I might add that I do install rsyslog and the matching logrotate.d and 
>> rsyslog.d files from util/ to my v5 setup, so weewx logs to under 
>> /var/log/weewx in that tmpfs partition, so I just run debug=1 here because 
>> it's not going to touch the actual sd card.  Super stable.
>>
>>

-- 
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/86c8becf-edfb-4264-b93f-2626ed9adfacn%40googlegroups.com.

Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

[Graham Knights]

I've been running weewx on a RPi 3B+ for just over 5 years, but after a 
couple of other pi's died for various reasons (SD card being one of them), 
I've moved it to a debian install on a VM in a Windows 10 Pro machine (runs 
my automation server).  Hardware is a Lenovo ThinkCentre M700 Tiny which I 
find perfect for running a couple of small linux VM's on it.  Low power, 
tiny, quiet, and versatile, and Lenovo hardware has been good to me over 
the years. Machines are cheap to find on ebay/amazon, probably less than a 
new Pi by the time you add all the parts.

On Friday, February 23, 2024 at 9:46:42 AM UTC-8 vince wrote:

> If I was starting clean 'today', I would probably just throw $125 at it 
> and get one of those little beelink boxes amazon sells and toss linux on it.
>
> But to answer - currently on a 4GB pi4 to sd card for 2+ years with no 
> issues.
>
> Stability issues on a pi are almost always bad power supply these days. 
>  I've never had a micro-sd fail on a pi3, 3+, 4, or pi5.  Never.   I did 
> burn a 'lot' of big sd cards on the old modelB over the years but again 
> that was related to either (a) cheapo cards or (b) cheapo power adaptors 
> not on surge suppressors.  My one remaining modelB is still happily 
> shooting my timelapse snaps for over a decade now.
>
> I do make one change to the pi setups to protect the sd card.  I mount 
> some filesystems as tmpfs so the sd can't be hammered by log writes by 
> appending this to /etc/stab
>
> # put logs and tmp dirs in ramdisk too ---
> tmpfs   /tmptmpfs   
> defaults,nosuid,mode=0755,nodev,noatime   0   0
> tmpfs   /var/logtmpfs   
> defaults,nosuid,mode=0755,nodev,noatime   0   0
> tmpfs   /var/tmptmpfs   
> defaults,nosuid,mode=0755,nodev,noatime   0   0
> #-
>
> Yes - if I reboot I lose the system logs.  But I basically never reboot.
>
> I might add that I do install rsyslog and the matching logrotate.d and 
> rsyslog.d files from util/ to my v5 setup, so weewx logs to under 
> /var/log/weewx in that tmpfs partition, so I just run debug=1 here because 
> it's not going to touch the actual sd card.  Super stable.
>
>

-- 
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/e01b98c9-b636-45e2-ae7d-11fbf9ebff38n%40googlegroups.com.

Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

[vince]

If I was starting clean 'today', I would probably just throw $125 at it and 
get one of those little beelink boxes amazon sells and toss linux on it.

But to answer - currently on a 4GB pi4 to sd card for 2+ years with no 
issues.

Stability issues on a pi are almost always bad power supply these days. 
 I've never had a micro-sd fail on a pi3, 3+, 4, or pi5.  Never.   I did 
burn a 'lot' of big sd cards on the old modelB over the years but again 
that was related to either (a) cheapo cards or (b) cheapo power adaptors 
not on surge suppressors.  My one remaining modelB is still happily 
shooting my timelapse snaps for over a decade now.

I do make one change to the pi setups to protect the sd card.  I mount some 
filesystems as tmpfs so the sd can't be hammered by log writes by appending 
this to /etc/stab

# put logs and tmp dirs in ramdisk too ---
tmpfs   /tmptmpfs   
defaults,nosuid,mode=0755,nodev,noatime   0   0
tmpfs   /var/logtmpfs   
defaults,nosuid,mode=0755,nodev,noatime   0   0
tmpfs   /var/tmptmpfs   
defaults,nosuid,mode=0755,nodev,noatime   0   0
#-

Yes - if I reboot I lose the system logs.  But I basically never reboot.

I might add that I do install rsyslog and the matching logrotate.d and 
rsyslog.d files from util/ to my v5 setup, so weewx logs to under 
/var/log/weewx in that tmpfs partition, so I just run debug=1 here because 
it's not going to touch the actual sd card.  Super stable.

-- 
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/56a6ed65-0fe9-4073-a9c1-d546a421b5d5n%40googlegroups.com.

Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

[p q]

Raspberry pi 3b with nothing more than the standard SD card. Running with
no problems for more than 6 years. I do have a 2hr battery backup so it's
only been down less than once a year.

On Fri, Feb 23, 2024, 6:57 AM Pierre-Yves  wrote:

> My setup:
>
> RPi4-2GB
> Argon-one-M2 case (
> https://argon40.com/products/argon-one-m-2-case-for-raspberry-pi-4)
> Liteon 16GB M.2 2242 SSD
> RTC module integrated into the housing
> Homemade ~ 2hrs UPS (5.2 V, 2.5 A)
> Bresser WSX3001 (7in1), user.sdr driver
> BME280 + AS3935 extensions connected to i2c port
>
> It has been working without problems for 2 years.
> A small SSD capacity (16 GB) makes easier regular full disk image backups.
> Not sure that a UPS is essential since the Argon-one restarts
> automatically after a power outage (POs very infrequent and always of short
> duration).
>
> PYB
>
> Le vendredi 23 février 2024 à 15:44:08 UTC+1, Warren Gill a écrit :
>
>> I have been running weewx on a (now discontinued) Odroid HC2
>> https://ameridroid.com/products/odroid-hc2 for several years now,
>> connected to a Vantage Envoy, that collects data from the Vantage Pro .
>> Since it can move its all but the initial uBoot code to SSD it's been super
>> reliable. I would choose Odroid again... the XU4 uses eMMC, or a Lenovo
>> Tiny PC and also use it for Home Assistant and other automation tasks.
>>
>> On Fri, Feb 23, 2024 at 12:25 AM 'michael.k...@gmx.at' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>>
>>> I'm curious what hardware you are running WeeWX on, and your experience
>>> with it. So, this is not about the weather station and the sensors, but the
>>> device which is running the service. The reason I ask this here, is because
>>> the issues I experienced with my hardware might be related to weewx and
>>> writing it's logs, and we all know the first rule for posting a question
>>> here :D
>>>
>>> Since my first WeeWX installation in 2015, I've been using every
>>> generation of the RaspberryPi B, except for the 5th. But looking back it,
>>> has sometimes has been a royal PITA. It's not that I consider the Pi being
>>> bad at all, but I've been having issues with whatever storage I've been
>>> using. SD-Cards were a total disaster, USB flash drives were slightly
>>> better, USB attached SSDs, at least, lasted more than two years before
>>> being attached to the Pi killed them. The only type that didn't fail so
>>> far, was a NFS provided by a QNAP NAS, but this Kind of setup is a bit
>>> complex to maintain, and starting the NAS over, means quite a bit of
>>> downtime for the Pi also.
>>>
>>> The Pi never was intended to be a server running 24/7, considering this,
>>> it's success in being used as such, is beyond imagination. Anyway, my
>>> experience for the Pi being a storage killer, doesn't seem to be uncommon.
>>> It's original intention was satisfied: I learned a lot about how not to
>>> lose data with unreliable hardware. Since 2015, my database isn't missing
>>> more than one archive value a day in average and the longest gap is about
>>> two hours back in early 2016, using the standard interval of 5 minutes.
>>>
>>> What hardware are you using, what is your experience?
>>> Can you suggest hardware with low power consumption as a requirement?
>>> What about the newest generation, like Intel n100 based systems?
>>>
>>> --
>>> 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/69220248-dd7a-4e8a-a7bb-f3251017e0f5n%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/b634ba6d-0b05-42fe-a16e-19736aa34dfcn%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/CAA1SM20K9uefjGK9tGkDENhHAm6-cAnnDL-hcpAoeQEhA6mHxg%40mail.gmail.com.

Re: [weewx-user] Difference between aggregation types has_data and not_null

[bell...@gmail.com]

I found that you only have to implement ‘not_null’. I believe this is 
because the ‘has_data’ tag (tags.py line 389) enters the xtype system with 
an aggregate of ‘has_data’. This then looks for the aggregate of ‘not_null’ 
(xtypes.py line 156).
Looking forward to hearing if my conclusion was correct.

On Friday 23 February 2024 at 10:48:51 UTC-5 Karen K wrote:

> Do I have to implement both the not_null and has_data aggregation in an 
> XType extension?
>
>
> Tom Keffer schrieb am Freitag, 23. Februar 2024 um 14:01:45 UTC+1:
>
> The aggregation not_null does not check first to see if the type exists. 
> If you know the type exists, it's slightly faster. 
>
> In practice, I don't think it's very useful. I may remove it from the 
> documentation.
>
> On Fri, Feb 23, 2024 at 3:48 AM Karen K  wrote:
>
> What is the difference between the aggregation types has_data and not_null 
> according to the documentation in 
> http://weewx.com/docs/5.0/reference/aggtypes/.
>
>

-- 
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/da719dec-cf71-4ffb-8d0e-a7cb1bdd7d26n%40googlegroups.com.

Re: [weewx-user] Difference between aggregation types has_data and not_null

[Karen K]

Do I have to implement both the not_null and has_data aggregation in an 
XType extension?


Tom Keffer schrieb am Freitag, 23. Februar 2024 um 14:01:45 UTC+1:

The aggregation not_null does not check first to see if the type exists. If 
you know the type exists, it's slightly faster. 

In practice, I don't think it's very useful. I may remove it from the 
documentation.

On Fri, Feb 23, 2024 at 3:48 AM Karen K  wrote:

What is the difference between the aggregation types has_data and not_null 
according to the documentation in 
http://weewx.com/docs/5.0/reference/aggtypes/.

-- 
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/8abfecfb-7fe5-4e6c-aace-540ed933ea8en%40googlegroups.com.

Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

[Pierre-Yves]

My setup:

RPi4-2GB
Argon-one-M2 case (
https://argon40.com/products/argon-one-m-2-case-for-raspberry-pi-4)
Liteon 16GB M.2 2242 SSD
RTC module integrated into the housing
Homemade ~ 2hrs UPS (5.2 V, 2.5 A)
Bresser WSX3001 (7in1), user.sdr driver
BME280 + AS3935 extensions connected to i2c port

It has been working without problems for 2 years.
A small SSD capacity (16 GB) makes easier regular full disk image backups.
Not sure that a UPS is essential since the Argon-one restarts automatically 
after a power outage (POs very infrequent and always of short duration).

PYB

Le vendredi 23 février 2024 à 15:44:08 UTC+1, Warren Gill a écrit :

> I have been running weewx on a (now discontinued) Odroid HC2 
> https://ameridroid.com/products/odroid-hc2 for several years now, 
> connected to a Vantage Envoy, that collects data from the Vantage Pro . 
> Since it can move its all but the initial uBoot code to SSD it's been super 
> reliable. I would choose Odroid again... the XU4 uses eMMC, or a Lenovo 
> Tiny PC and also use it for Home Assistant and other automation tasks.
>
> On Fri, Feb 23, 2024 at 12:25 AM 'michael.k...@gmx.at' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> I'm curious what hardware you are running WeeWX on, and your experience 
>> with it. So, this is not about the weather station and the sensors, but the 
>> device which is running the service. The reason I ask this here, is because 
>> the issues I experienced with my hardware might be related to weewx and 
>> writing it's logs, and we all know the first rule for posting a question 
>> here :D
>>
>> Since my first WeeWX installation in 2015, I've been using every 
>> generation of the RaspberryPi B, except for the 5th. But looking back it, 
>> has sometimes has been a royal PITA. It's not that I consider the Pi being 
>> bad at all, but I've been having issues with whatever storage I've been 
>> using. SD-Cards were a total disaster, USB flash drives were slightly 
>> better, USB attached SSDs, at least, lasted more than two years before 
>> being attached to the Pi killed them. The only type that didn't fail so 
>> far, was a NFS provided by a QNAP NAS, but this Kind of setup is a bit 
>> complex to maintain, and starting the NAS over, means quite a bit of 
>> downtime for the Pi also.
>>
>> The Pi never was intended to be a server running 24/7, considering this, 
>> it's success in being used as such, is beyond imagination. Anyway, my 
>> experience for the Pi being a storage killer, doesn't seem to be uncommon. 
>> It's original intention was satisfied: I learned a lot about how not to 
>> lose data with unreliable hardware. Since 2015, my database isn't missing 
>> more than one archive value a day in average and the longest gap is about 
>> two hours back in early 2016, using the standard interval of 5 minutes.
>>
>> What hardware are you using, what is your experience?
>> Can you suggest hardware with low power consumption as a requirement?
>> What about the newest generation, like Intel n100 based systems? 
>>
>> -- 
>> 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/69220248-dd7a-4e8a-a7bb-f3251017e0f5n%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/b634ba6d-0b05-42fe-a16e-19736aa34dfcn%40googlegroups.com.

Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

[Warren Gill]

I have been running weewx on a (now discontinued) Odroid HC2
https://ameridroid.com/products/odroid-hc2 for several years now, connected
to a Vantage Envoy, that collects data from the Vantage Pro . Since it can
move its all but the initial uBoot code to SSD it's been super reliable. I
would choose Odroid again... the XU4 uses eMMC, or a Lenovo Tiny PC and
also use it for Home Assistant and other automation tasks.

On Fri, Feb 23, 2024 at 12:25 AM 'michael.k...@gmx.at' via weewx-user <
weewx-user@googlegroups.com> wrote:

> I'm curious what hardware you are running WeeWX on, and your experience
> with it. So, this is not about the weather station and the sensors, but the
> device which is running the service. The reason I ask this here, is because
> the issues I experienced with my hardware might be related to weewx and
> writing it's logs, and we all know the first rule for posting a question
> here :D
>
> Since my first WeeWX installation in 2015, I've been using every
> generation of the RaspberryPi B, except for the 5th. But looking back it,
> has sometimes has been a royal PITA. It's not that I consider the Pi being
> bad at all, but I've been having issues with whatever storage I've been
> using. SD-Cards were a total disaster, USB flash drives were slightly
> better, USB attached SSDs, at least, lasted more than two years before
> being attached to the Pi killed them. The only type that didn't fail so
> far, was a NFS provided by a QNAP NAS, but this Kind of setup is a bit
> complex to maintain, and starting the NAS over, means quite a bit of
> downtime for the Pi also.
>
> The Pi never was intended to be a server running 24/7, considering this,
> it's success in being used as such, is beyond imagination. Anyway, my
> experience for the Pi being a storage killer, doesn't seem to be uncommon.
> It's original intention was satisfied: I learned a lot about how not to
> lose data with unreliable hardware. Since 2015, my database isn't missing
> more than one archive value a day in average and the longest gap is about
> two hours back in early 2016, using the standard interval of 5 minutes.
>
> What hardware are you using, what is your experience?
> Can you suggest hardware with low power consumption as a requirement?
> What about the newest generation, like Intel n100 based systems?
>
> --
> 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/69220248-dd7a-4e8a-a7bb-f3251017e0f5n%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/CA%2Bz%2BvD4aX83WK5V9-EiRGRPcg%3Dt9V%3DFG%3DeRLx_eaxJ%3D-VkmQ-A%40mail.gmail.com.

Re: [weewx-user] Catastrophic apt upgrade to V5.02 on Raspberry Pi

['Peter Fletcher' via weewx-user]

@matthew

I think that the below responds to all your specific questions. Let me know 
if there is any other information that would help you. I am running a 
single instance of weewx on a Raspberry Pi 3B, which also runs various 
systemd services which monitor and manage my heating system and components 
of my power and lighting systems. I am currently running the latest release 
of Bullseye on the Pi. I know that Bookworm has been out and nominally 
stable for a while, and am working with it on a spare system, but some of 
my other software isn't yet convinced that it is happy to run under some of 
the new 'rules' that come with the new version of the OS. I am a reasonably 
competent Unix user and a reasonably competent Python (among other 
languages) programmer, but most of my low level OS and programming 
experience was gained on Windows OSes.

weewx is hooked up to a Davis Vantage Pro 2 Plus weather station, by means 
of a Meteo-pi HAT (which includes a RTC). The interface is seen by the Pi 
as its first serial port (serial0). I have been using weewx to monitor and 
record the weather station's output here since 2020, and for a while before 
that at the house in Illinois from which I moved at that time. The Version 
number in the weewx.conf file (copy attached) is 4.10.2, but it was apt 
installed when I moved to Bullseye, a couple of years ago, so regular apt 
upgrades will have been keeping the software updated.

I have written and use a number of weewx user services to incorporate data 
from other sensors and to 'tweak' some of the data coming from the weather 
station before it gets stored. These have not caused any issues under the 
new version - they do do some file access, but only reading files, so 
access privileges would not be expected to be a problem (and aren't).

I have weewx set up to generate two sets of reports, both using skins based 
on an early version of the Seasons skin, but with some (different) 
modifications and deletions. One of the reports shows all the information 
available to it (including some from independent sensors around my house) 
and is 'for internal use'; the other shows only standard weather 
information and is used for two public sites, one associated with my own 
personal site, and the other with a HOA site that I manage for my 
community. The HOA site 'cross-loads' the charts it displays from my 
personal site, so weewx is not directly concerned with uploading these 
image files to it. However, the HOA site gets current weather information 
from a Cumulus realtime.txt file generated by weewx which is uploaded 
directly to it, so weewx.conf has two FTP stanzas - one for the public 
site, and one for the realtime.txt file.

The 'for internal use' report is written to /var/www/html/weewx, and served 
from there to the local network by an instance of nginx running on the Pi. 
nginx only needs read access to the files, so access rights weren't a 
problem. The public report is written to /var/www/html/weewx2, and FTP 
uploaded from there by weewx to my live site on an ISP's servers. The 
realtime.txt file is written to /var/www/html/weewx3, and FTP uploaded from 
there by weewx to a location on the HOA site. All the folders are regular 
'physical' folders and are directly declared in my conf file - I try to 
avoid using symlinks unless I absolutely have to, since I frequently find 
their behavior non-intuitive!

I actually had two classes of problems. weewx initially not running at all 
after the upgrade was deeply worrying, but relatively easy to troubleshoot, 
since the error reports from systemctl status were relatively clear in 
pointing to the problems. Once I got it running, by sorting out the most 
severe access problems, I had more difficult chasing down problems with my 
public reports, which were not being updated as a result of permissions 
errors that were not causing weewx to crash. As I noted also, my life was 
made immeasurably more difficult by the fact that the symptoms that I was 
initially seeing for the public reports suggested more problems of a type 
that I had already experienced from recent changes to my ISP's FTP servers, 
rather than issues with weewx generating them. I found getting the settings 
right for the two subfolders in my HTML report folders (NOAA and fonts) 
particularly tricky - probably because I initially used a recursive chmod 
command that was wrong for the directories affected.

On Wednesday, February 21, 2024 at 7:13:08 PM UTC-5 matthew wall wrote:

> On Wednesday, February 21, 2024 at 6:50:52 PM UTC-5 Peter Fletcher wrote:
>
> There were essentially no issues with the 4.x->5.x update. What I wasn't 
> prepared for was an update *from 5.01 to 5.02* clobbering everything *that 
> was previously working in 5.01*. I don't think that it is reasonable to 
> expect the user to carefully (re-)read all the documentation before 
> doing/allowing a 'second decimal place' update.
>
>
> peter, it would be helpful if you could describe 

[weewx-user] Seeking Data Logging Options

[DY]

Hey WeeWX users!

I'm a scientist working on a tight budget, and our team needs multiple 
weather stations for deployment in the middle of wetlands, where 
communication isn't an option. These stations will be left in place for 
about two weeks at a time before being moved to different locations. 

I have some experience with microcomputers and coding, having developed an 
irrigation system using Arduino for previous science projects. I've also 
dabbled with RPi, although I found it extremely challenging back in 2017.

What I'm specifically looking for is logging data. I don't need any of the 
other functions that WeeWX would provide. If anyone has already developed 
or provided tutorials specifically for logging purposes, I'd greatly 
appreciate some guidance. 

Additionally, any advice or recommendations for other pre-made stations 
around $400 that are capable of logging would be fantastic.

Thank you in advance for your help and suggestions!

DY

-- 
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/4b0cd6ae-b725-4cf7-b949-e019c83ec332n%40googlegroups.com.

Re: [weewx-user] Difference between aggregation types has_data and not_null

[Karen K]

Thank you.

Tom Keffer schrieb am Freitag, 23. Februar 2024 um 14:01:45 UTC+1:

> The aggregation not_null does not check first to see if the type exists. 
> If you know the type exists, it's slightly faster. 
>
> In practice, I don't think it's very useful. I may remove it from the 
> documentation.
>
> On Fri, Feb 23, 2024 at 3:48 AM Karen K  wrote:
>
>> What is the difference between the aggregation types has_data and 
>> not_null according to the documentation in 
>> http://weewx.com/docs/5.0/reference/aggtypes/. 
>>
>> -- 
>> 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/3eef09c7-c2fe-49a2-9e89-f1957c731a54n%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/92bba5f3-93ed-4d16-963e-06e520c606c1n%40googlegroups.com.

[weewx-user] Re: Your hardware experience (for running WeeWX, the service)

[Andy]

Had good luck with Lenovo ThinkCentre M700 Tiny with 8GB ram.  It runs the 
free version of  VMware ESXi. Two weewx vm's, plex and home assistant run 
fine. USB pass through for the SDR dongle. I have a cold spare M700 Tiny 
and backup the vm's to a network share. Network share is Pine Quartz64 
Model A with SATA card and two SSD's in software RAID 


   - Good SD card
   - Proper Power Supply
   - Try to limit writes
   - UPS  


Had to change a UPS battery, that is why the uptime is so low. 
root@raspberrypi2-0:~# uptime
 05:39:48 up 256 days,  4:43,  1 user,  load average: 0.44, 0.48, 0.49
root@raspberrypi3-1:~# uptime
 13:42:09 up 256 days,  4:45,  2 users,  load average: 0.00, 0.00, 0.00
root@raspberrypi:~# uptime
 13:42:56 up 343 days, 14:50,  1 user,  load average: 0.00, 0.00, 0.00
root@raspberrypi4-1:~# uptime
 05:43:49 up 44 days, 13:49,  1 user,  load average: 0.53, 0.38, 0.30
## This one boots off of a USB SSD, for what ever reason locks up

Andy
On Friday, February 23, 2024 at 4:18:20 AM UTC-8 jterr...@gmail.com wrote:

> I installed my  Weewx in 2019 on a Raspberry Pi 3B+, fitted with an mSATA 
> extension card (such as this one : 
> https://geekworm.com/products/raspberry-pi-3-x850-v3-0-usb-3-0-msata-ssd-storage-expansion-board
>  
> ) and a 120Gb mSATA SSD.
> Zero issues, and still running today.
>
> Le vendredi 23 février 2024 à 07:25:49 UTC+1, michael.k...@gmx.at a 
> écrit :
>
>> I'm curious what hardware you are running WeeWX on, and your experience 
>> with it. So, this is not about the weather station and the sensors, but the 
>> device which is running the service. The reason I ask this here, is because 
>> the issues I experienced with my hardware might be related to weewx and 
>> writing it's logs, and we all know the first rule for posting a question 
>> here :D
>>
>> Since my first WeeWX installation in 2015, I've been using every 
>> generation of the RaspberryPi B, except for the 5th. But looking back it, 
>> has sometimes has been a royal PITA. It's not that I consider the Pi being 
>> bad at all, but I've been having issues with whatever storage I've been 
>> using. SD-Cards were a total disaster, USB flash drives were slightly 
>> better, USB attached SSDs, at least, lasted more than two years before 
>> being attached to the Pi killed them. The only type that didn't fail so 
>> far, was a NFS provided by a QNAP NAS, but this Kind of setup is a bit 
>> complex to maintain, and starting the NAS over, means quite a bit of 
>> downtime for the Pi also.
>>
>> The Pi never was intended to be a server running 24/7, considering this, 
>> it's success in being used as such, is beyond imagination. Anyway, my 
>> experience for the Pi being a storage killer, doesn't seem to be uncommon. 
>> It's original intention was satisfied: I learned a lot about how not to 
>> lose data with unreliable hardware. Since 2015, my database isn't missing 
>> more than one archive value a day in average and the longest gap is about 
>> two hours back in early 2016, using the standard interval of 5 minutes.
>>
>> What hardware are you using, what is your experience?
>> Can you suggest hardware with low power consumption as a requirement?
>> What about the newest generation, like Intel n100 based systems? 
>>
>

-- 
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/696aa1da-4b56-42b0-a0c0-93ad572e016an%40googlegroups.com.

Re: [weewx-user] Difference between aggregation types has_data and not_null

[Tom Keffer]

The aggregation not_null does not check first to see if the type exists. If
you know the type exists, it's slightly faster.

In practice, I don't think it's very useful. I may remove it from the
documentation.

On Fri, Feb 23, 2024 at 3:48 AM Karen K  wrote:

> What is the difference between the aggregation types has_data and not_null
> according to the documentation in
> http://weewx.com/docs/5.0/reference/aggtypes/.
>
> --
> 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/3eef09c7-c2fe-49a2-9e89-f1957c731a54n%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/CAPq0zECeyc90n6f6O1KbmwYTExvOr0NaDvZcNYRtLe-9m7qL4Q%40mail.gmail.com.

[weewx-user] Re: Your hardware experience (for running WeeWX, the service)

[jterr...@gmail.com]

I installed my  Weewx in 2019 on a Raspberry Pi 3B+, fitted with an mSATA 
extension card (such as this one 
: 
https://geekworm.com/products/raspberry-pi-3-x850-v3-0-usb-3-0-msata-ssd-storage-expansion-board
 
) and a 120Gb mSATA SSD.
Zero issues, and still running today.

Le vendredi 23 février 2024 à 07:25:49 UTC+1, michael.k...@gmx.at a écrit :

> I'm curious what hardware you are running WeeWX on, and your experience 
> with it. So, this is not about the weather station and the sensors, but the 
> device which is running the service. The reason I ask this here, is because 
> the issues I experienced with my hardware might be related to weewx and 
> writing it's logs, and we all know the first rule for posting a question 
> here :D
>
> Since my first WeeWX installation in 2015, I've been using every 
> generation of the RaspberryPi B, except for the 5th. But looking back it, 
> has sometimes has been a royal PITA. It's not that I consider the Pi being 
> bad at all, but I've been having issues with whatever storage I've been 
> using. SD-Cards were a total disaster, USB flash drives were slightly 
> better, USB attached SSDs, at least, lasted more than two years before 
> being attached to the Pi killed them. The only type that didn't fail so 
> far, was a NFS provided by a QNAP NAS, but this Kind of setup is a bit 
> complex to maintain, and starting the NAS over, means quite a bit of 
> downtime for the Pi also.
>
> The Pi never was intended to be a server running 24/7, considering this, 
> it's success in being used as such, is beyond imagination. Anyway, my 
> experience for the Pi being a storage killer, doesn't seem to be uncommon. 
> It's original intention was satisfied: I learned a lot about how not to 
> lose data with unreliable hardware. Since 2015, my database isn't missing 
> more than one archive value a day in average and the longest gap is about 
> two hours back in early 2016, using the standard interval of 5 minutes.
>
> What hardware are you using, what is your experience?
> Can you suggest hardware with low power consumption as a requirement?
> What about the newest generation, like Intel n100 based systems? 
>

-- 
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/9a847659-90a3-4922-9cc7-9369c54c9b34n%40googlegroups.com.

[weewx-user] Difference between aggregation types has_data and not_null

[Karen K]

What is the difference between the aggregation types has_data and not_null 
according to the documentation 
in http://weewx.com/docs/5.0/reference/aggtypes/.

-- 
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/3eef09c7-c2fe-49a2-9e89-f1957c731a54n%40googlegroups.com.

[weewx-user] Re: Your hardware experience (for running WeeWX, the service)

[Nick Name]

Goddam auto correct!

On Friday, February 23, 2024 at 9:46:09 AM UTC Nick Name wrote:

> Noobs Journey:
> So probably not precisely what you are look for but.
>
> R.Pi 5 with weewx logging from Davis VP2.
> Disastrous early attempts - but starting from scratch (New Pi (NVME rather 
> than SD card) fresh installs of OS & package install of weewx plus support 
> software (php, MariaDB etc))
> Running 24/7 for 3 weeks now. Zero issues, much happy.
>
> Slowly working my way through documentation and customisation.
> Current "Ultimate Objectives" 
> 1) Figure out how to render wind data on polar display (graph?),
> 2) Skin (or custom web page)  reproducing console display of Davis unit,
>
> Just to add - have previous experience with Oregon Scientific units and 
> meteobridge + numerous other weather logging software.
>
> Current impression is that the new whew based setup offers the best set of 
> options yet .. but more data to collect and work to do.
>
> Regards.
> Frank C.
>
> On Friday, February 23, 2024 at 6:25:49 AM UTC michael.k...@gmx.at wrote:
>
>> I'm curious what hardware you are running WeeWX on, and your experience 
>> with it. So, this is not about the weather station and the sensors, but the 
>> device which is running the service. The reason I ask this here, is because 
>> the issues I experienced with my hardware might be related to weewx and 
>> writing it's logs, and we all know the first rule for posting a question 
>> here :D
>>
>> Since my first WeeWX installation in 2015, I've been using every 
>> generation of the RaspberryPi B, except for the 5th. But looking back it, 
>> has sometimes has been a royal PITA. It's not that I consider the Pi being 
>> bad at all, but I've been having issues with whatever storage I've been 
>> using. SD-Cards were a total disaster, USB flash drives were slightly 
>> better, USB attached SSDs, at least, lasted more than two years before 
>> being attached to the Pi killed them. The only type that didn't fail so 
>> far, was a NFS provided by a QNAP NAS, but this Kind of setup is a bit 
>> complex to maintain, and starting the NAS over, means quite a bit of 
>> downtime for the Pi also.
>>
>> The Pi never was intended to be a server running 24/7, considering this, 
>> it's success in being used as such, is beyond imagination. Anyway, my 
>> experience for the Pi being a storage killer, doesn't seem to be uncommon. 
>> It's original intention was satisfied: I learned a lot about how not to 
>> lose data with unreliable hardware. Since 2015, my database isn't missing 
>> more than one archive value a day in average and the longest gap is about 
>> two hours back in early 2016, using the standard interval of 5 minutes.
>>
>> What hardware are you using, what is your experience?
>> Can you suggest hardware with low power consumption as a requirement?
>> What about the newest generation, like Intel n100 based systems? 
>>
>

-- 
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/d1618d42-752f-41ee-84d3-0f7b5d11b1a4n%40googlegroups.com.

[weewx-user] Re: Your hardware experience (for running WeeWX, the service)

[Nick Name]

Noobs Journey:
So probably not precisely what you are look for but.

R.Pi 5 with weewx logging from Davis VP2.
Disastrous early attempts - but starting from scratch (New Pi (NVME rather 
than SD card) fresh installs of OS & package install of weewx plus support 
software (php, MariaDB etc))
Running 24/7 for 3 weeks now. Zero issues, much happy.

Slowly working my way through documentation and customisation.
Current "Ultimate Objectives" 
1) Figure out how to render wind data on polar display (graph?),
2) Skin (or custom web page)  reproducing console display of Davis unit,

Just to add - have previous experience with Oregon Scientific units and 
meteobridge + numerous other weather logging software.

Current impression is that the new whew based setup offers the best set of 
options yet .. but more data to collect and work to do.

Regards.
Frank C.

On Friday, February 23, 2024 at 6:25:49 AM UTC michael.k...@gmx.at wrote:

> I'm curious what hardware you are running WeeWX on, and your experience 
> with it. So, this is not about the weather station and the sensors, but the 
> device which is running the service. The reason I ask this here, is because 
> the issues I experienced with my hardware might be related to weewx and 
> writing it's logs, and we all know the first rule for posting a question 
> here :D
>
> Since my first WeeWX installation in 2015, I've been using every 
> generation of the RaspberryPi B, except for the 5th. But looking back it, 
> has sometimes has been a royal PITA. It's not that I consider the Pi being 
> bad at all, but I've been having issues with whatever storage I've been 
> using. SD-Cards were a total disaster, USB flash drives were slightly 
> better, USB attached SSDs, at least, lasted more than two years before 
> being attached to the Pi killed them. The only type that didn't fail so 
> far, was a NFS provided by a QNAP NAS, but this Kind of setup is a bit 
> complex to maintain, and starting the NAS over, means quite a bit of 
> downtime for the Pi also.
>
> The Pi never was intended to be a server running 24/7, considering this, 
> it's success in being used as such, is beyond imagination. Anyway, my 
> experience for the Pi being a storage killer, doesn't seem to be uncommon. 
> It's original intention was satisfied: I learned a lot about how not to 
> lose data with unreliable hardware. Since 2015, my database isn't missing 
> more than one archive value a day in average and the longest gap is about 
> two hours back in early 2016, using the standard interval of 5 minutes.
>
> What hardware are you using, what is your experience?
> Can you suggest hardware with low power consumption as a requirement?
> What about the newest generation, like Intel n100 based systems? 
>

-- 
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/2cfe7e80-abcd-42a2-b818-71dcec4e80cbn%40googlegroups.com.