from:"Rainer Lang"

[weewx-user] Re: gw1000 driver fail on wifi loss

2020-12-27 Thread Rainer Lang

I had the same issue like Vince the other day - and  loop_on_init 
hadn't been set by the install script...

I assume it's to set in the [GW1000] stanza - that's where I added it now.

 Forwarded Message 
Subject:[weewx-user] Re: gw1000 driver fail on wifi loss
Date:   Sun, 27 Dec 2020 13:12:19 -0800 (PST)
From:   gjr80 
Reply-To:   weewx-user@googlegroups.com
To: weewx-user 

That would explain the behaviour then, if loop_on_init is not set the 
loss of connectivity with the station (for whatever reason) will cause 
WeeWX tobeen exit as it does with any other driver. I will make a point 
of pulling the network on my GW1000 and confirming the driver and 
loop_on_init work as expected.

Gary

On Monday, 28 December 2020 at 07:08:28 UTC+10 vince wrote:

   (unsure if this blasted google groups new interface ate my draft
   reply - grr...)

   loop_on_init was not set at all, so it's sure acting like the
   default is False.
   I'll define it as True for the next time, which hopefully won't need
   testing for a long time

   Thanks.

   On Sunday, December 27, 2020 at 11:53:08 AM UTC-8 gjr80 wrote:

   Vince,

   Thank you. From memory the driver should retry continuously when
   the network returns if loop_on_init = True in weewx.conf (though
   I am not sure I tested this by turning of my network). Can you
   confirm the loop_on_init setting at the time?

   Gary

   On Monday, 28 December 2020 at 03:54:33 UTC+10 vince wrote:

   Gary - I wanted to pass along some logs from a gw1000 driver
   abort yesterday.

   I had my home network down for a bit yesterday to do some
   firmware updates on my Ubiquiti USG, Switch and AcLite
   access point and weewx aborted rather quickly.

   The external, wired, and wifi networks were indeed down for
   some minutes so missing some readings was expected, but I
   was hopeful that the driver would recover gracefully after
   things were back up,  however weewx totally aborted and the
   process was gone.

   Just passing along the logs in case you wanted to take a
   look.  Thanks.

   Dec 26 16:26:16 pi3jr weewx[18939] ERROR user.gw1000: Failed
   to obtain response to command 'CMD_GW1000_LIVEDATA' after 3
   attempts
   Dec 26 16:26:16 pi3jr weewx[18939] ERROR user.gw1000: Unable
   to obtain live sensor data
   Dec 26 16:26:16 pi3jr weewx[18939] INFO weewx.engine: Main
   loop exiting. Shutting engine down.
   Dec 26 16:26:16 pi3jr weewx[18939] INFO weewx.engine:
   Shutting down StdReport thread
   Dec 26 16:26:36 pi3jr weewx[18939] ERROR weewx.engine:
   Unable to shut down StdReport thread
   Dec 26 16:26:43 pi3jr weewx[18939] ERROR user.gw1000: Failed
   to obtain response to command 'CMD_GW1000_LIVEDATA' after 3
   attempts
   Dec 26 16:26:43 pi3jr weewx[18939] ERROR user.gw1000: Unable
   to obtain live sensor data
   Dec 26 16:26:44 pi3jr weewx[18939] INFO user.gw1000:
   Gw1000Collector thread has been terminated
   Dec 26 16:26:44 pi3jr weewx[18939] CRITICAL __main__: Caught
   WeeWxIOError: Failed to obtain response to command
   'CMD_GW1000_LIVEDATA' after 3 attempts
   Dec 26 16:26:44 pi3jr weewx[18939] CRITICAL __main__:    
     Waiting 60 seconds then retrying...
   Dec 26 16:27:44 pi3jr weewx[18939] INFO __main__: retrying...
   Dec 26 16:27:44 pi3jr weewx[18939] INFO __main__: Using
   configuration file /etc/weewx/weewx.conf
   Dec 26 16:27:44 pi3jr weewx[18939] INFO __main__: Debug is 0
   Dec 26 16:27:44 pi3jr weewx[18939] INFO weewx.engine:
   Loading station type GW1000 (user.gw1000)
   Dec 26 16:28:08 pi3jr weewx[18939] ERROR user.gw1000: Failed
   to obtain response to command 'CMD_READ_STATION_MAC' after 3
   attempts
   Dec 26 16:28:08 pi3jr weewx[18939] ERROR weewx.engine:
   Import of driver failed: Failed to obtain response to
   command 'CMD_READ_STATION_MAC' after 3 attempts ()
   Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine:  
    Traceback (most recent call last):
   Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine:  
      File "/usr/share/weewx/weewx/engine.py", line
   109, in setupStation
   Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine:  
        self.console = loader_function(config_dict, self)
   Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine:  
      File "/usr/share/weewx/user/gw1000.py", line
   1293, in loader
   Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine:  
        return Gw1000Driver

weewx-user@googlegroups.com

2020-12-31 Thread Rainer Lang


Ever since integrating the new WH45 sensor, weewx went nuts:

(see below): no more reports written, no more archive records stored.

Had to take off the sensor and reset the GW1000 - then weewx went back 
to normal.


I think it's an "API mismatch" - btw - Meteobridge also produces weird 
sensor output, but doesn't crash.


Probably the WH45 with its 5 sensors  (5= T&H&CO2+PM2.5+PM10) is not yet 
properly implemented
as real life examples were missing. I'm holding one of the first sold 
WH45 since today.


Need more info, logs,  - let me know.

regrads

Rainer

Dec 31 15:49:50 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...
Dec 31 15:49:50 raspberrypi weewx[5528] INFO __main__: Initializing 
weewx version 4.2.0
Dec 31 15:49:50 raspberrypi weewx[5528] INFO __main__: Using Python 
2.7.16 (default, Oct 10 2019, 22:02:15) #012[GCC 8.3.0]
Dec 31 15:49:50 raspberrypi weewx[5528] INFO __main__: Platform 
Linux-5.4.79-v7l+-armv7l-with-debian-10.7
Dec 31 15:49:50 raspberrypi weewx[5528] INFO __main__: Locale is 
'en_US.UTF-8'
Dec 31 15:49:50 raspberrypi weewx[5528] INFO __main__: PID file is 
/var/run/weewx.pid
Dec 31 15:49:50 raspberrypi weewx[5532] INFO __main__: Using 
configuration file /etc/weewx/weewx.conf

Dec 31 15:49:50 raspberrypi weewx[5532] INFO __main__: Debug is 0
Dec 31 15:49:50 raspberrypi weewx[5516]: Starting weewx weather system: 
weewx.

Dec 31 15:49:50 raspberrypi systemd[1]: Started LSB: weewx weather system.
Dec 31 15:49:50 raspberrypi weewx[5532] INFO weewx.engine: Loading 
station type GW1000 (user.gw1000)
Dec 31 15:49:50 raspberrypi weewx[5532] INFO user.gw1000: field map is 
{'UV': 'uvi', 'dateTime': 'datetime', 'dayRain': 'rainday', 
'daymaxwind': 'daymaxwind', 'dewpoint': 'dewpoint', 'extraHumid1': 
'humid1', 'extraHumid2': 'humid2', 'extraHumid3': 'humid3', 
'extraHumid4': 'humid4', 'extraHumid5': 'humid5', 'extraHumid6': 
'humid6', 'extraHumid7': 'humid7', 'extraHumid8': 'humid8', 
'extraTemp1': 'temp1', 'extraTemp2': 'temp2', 'extraTemp3': 'temp3', 
'extraTemp4': 'temp4', 'extraTemp5': 'temp5', 'extraTemp6': 'temp6', 
'extraTemp7': 'temp7', 'extraTemp8': 'temp8', 'heatindex': 'heatindex', 
'hourRain': 'rainhour', 'inHumidity': 'inhumid', 'inTemp': 'intemp', 
'leak1': 'leak1', 'leak2': 'leak2', 'leak3': 'leak3', 'leak4': 'leak4', 
'lightning_distance': 'lightningdist', 'lightning_last_det_time': 
'lightningdettime', 'lightning_strike_count': 'lightning_strike_count', 
'luminosity': 'light', 'monthRain': 'rainmonth', 'outHumidity': 
'outhumid', 'outTemp': 'outtemp', 'pm2_5': 'pm251', 'pm2_51_24hav': 
'pm251_24hav', 'pm2_52': 'pm252', 'pm2_52_24hav': 'pm252_24hav', 
'pm2_53': 'pm253', 'pm2_53_24hav': 'pm253_24hav', 'pm2_54': 'pm254', 
'pm2_54_24hav': 'pm254_24hav', 'pressure': 'absbarometer', 'rain': 
'rain', 'rainEvent': 'rainevent', 'rainRate': 'rainrate', 
'relbarometer': 'relbarometer', 'soilMoist1': 'soilmoist1', 
'soilMoist2': 'soilmoist2', 'soilMoist3': 'soilmoist3', 'soilMoist4': 
'soilmoist4', 'soilMoist5': 'soilmoist5', 'soilMoist6': 'soilmoist6', 
'soilMoist7': 'soilmoist7', 'soilMoist8': 'soilmoist8', 'soilMoist9': 
'soilmoist9', 'soilMoist10': 'soilmoist10', 'soilMoist11': 
'soilmoist11', 'soilMoist12': 'soilmoist12', 'soilMoist13': 
'soilmoist13', 'soilMoist14': 'soilmoist14', 'soilMoist15': 
'soilmoist15', 'soilMoist16': 'soilmoist16', 'soilTemp1': 'soiltemp1', 
'soilTemp2': 'soiltemp2', 'soilTemp3': 'soiltemp3', 'soilTemp4': 
'soiltemp4', 'soilTemp5': 'soiltemp5', 'soilTemp6': 'soiltemp6', 
'soilTemp7': 'soiltemp7', 'soilTemp8': 'soiltemp8', 'soilTemp9': 
'soiltemp9', 'soilTemp10': 'soiltemp10', 'soilTemp11': 'soiltemp11', 
'soilTemp12': 'soiltemp12', 'soilTemp13': 'soiltemp13', 'soilTemp14': 
'soiltemp14', 'soilTemp15': 'soiltemp15', 'soilTemp16': 'soiltemp16', 
'totalRain': 'raintotals', 'uvradiation': 'uv', 'weekRain': 'rainweek', 
'wh25_batt': 'wh25_batt', 'wh26_batt': 'wh26_batt', 'wh31_ch1_batt': 
'wh31_ch1_batt', 'wh31_ch2_batt': 'wh31_ch2_batt', 'wh31_ch3_batt': 
'wh31_ch3_batt', 'wh31_ch4_batt': 'wh31_ch4_batt', 'wh31_ch5_batt': 
'wh31_ch5_batt', 'wh31_ch6_batt': 'wh31_ch6_batt', 'wh31_ch7_batt': 
'wh31_ch7_batt', 'wh31_ch8_batt': 'wh31_ch8_batt', 'wh40_batt': 
'wh40_batt', 'wh41_ch1_batt': 'wh41_ch1_batt', 'wh41_ch2_batt': 
'wh41_ch2_batt', 'wh41_ch3_batt': 'wh41_ch3_batt', 'wh41_ch4_batt': 
'wh41_ch4_batt', 'wh51_ch1_batt': 'wh51_ch1_batt', 'wh51_ch2_batt': 
'wh51_ch2_batt', 'wh51_ch3_batt': 'wh51_ch3_batt', 'wh51_ch4_batt': 
'wh51_ch4_batt', 'wh51_ch5_batt': 'wh51_ch5_batt', 'wh51_ch6_batt': 
'wh51_ch6_batt', 'wh51_ch7_batt': 'wh51_ch7_batt', 'wh51_ch8_batt': 
'wh51_ch8_batt', 'wh51_ch9_batt': 'wh51_ch9_batt', 'wh51_ch10_batt': 
'wh51_ch10_batt', 'wh51_ch11_batt': 'wh51_ch11_batt', 'wh51_ch12_batt': 
'wh51_ch12_batt', 'wh51_ch13_batt': 'wh51_ch13_batt', 'wh51_ch14_batt': 
'wh51_ch14_batt', 'wh51_ch15_batt': 'wh51_ch15_batt', 'wh51_ch16_batt': 
'wh51_ch16_batt', 'wh55_ch1_batt': 'wh55_ch1_batt', 'wh55_ch2_batt': 
'wh55_ch2_batt', 'wh55_ch3_

[weewx-user] Re: weewx crashed - issue with gw1000.py when Ecowitt WH45 5-in-1 combo sensor gets activated (5= T&H&CO2+PM2.5+PM10) [2b]

2020-12-31 Thread Rainer Lang

He's already been working on it - will check/test the suggestions 
tomorrow respectively today later in the day - now too early (or late) here.


On 01.01.2021 00:52, galfert wrote:
Hopefully Gary will pick this up and add the WH45 compatibility to the 
GW100 API driver.



On Thursday, December 31, 2020 at 10:10:30 AM UTC-5 
lang@googlemail.com wrote:


Ever since integrating the new WH45 sensor, weewx went nuts:

(see below): no more reports written, no more archive records stored.

Had to take off the sensor and reset the GW1000 - then weewx went
back to normal.

I think it's an "API mismatch" - btw - Meteobridge also produces
weird sensor output, but doesn't crash.

Probably the WH45 with its 5 sensors  (5= T&H&CO2+PM2.5+PM10) is
not yet properly implemented
as real life examples were missing. I'm holding one of the first
sold WH45 since today.

Need more info, logs,  - let me know.

regrads

Rainer

Dec 31 15:49:50 raspberrypi systemd[1]: Starting LSB: weewx
weather system...
Dec 31 15:49:50 raspberrypi weewx[5528] INFO __main__:
Initializing weewx version 4.2.0
Dec 31 15:49:50 raspberrypi weewx[5528] INFO __main__: Using
Python 2.7.16 (default, Oct 10 2019, 22:02:15) #012[GCC 8.3.0]
Dec 31 15:49:50 raspberrypi weewx[5528] INFO __main__: Platform
Linux-5.4.79-v7l+-armv7l-with-debian-10.7
Dec 31 15:49:50 raspberrypi weewx[5528] INFO __main__: Locale is
'en_US.UTF-8'
Dec 31 15:49:50 raspberrypi weewx[5528] INFO __main__: PID file is
/var/run/weewx.pid
Dec 31 15:49:50 raspberrypi weewx[5532] INFO __main__: Using
configuration file /etc/weewx/weewx.conf
Dec 31 15:49:50 raspberrypi weewx[5532] INFO __main__: Debug is 0
Dec 31 15:49:50 raspberrypi weewx[5516]: Starting weewx weather
system: weewx.
Dec 31 15:49:50 raspberrypi systemd[1]: Started LSB: weewx weather
system.
Dec 31 15:49:50 raspberrypi weewx[5532] INFO weewx.engine: Loading
station type GW1000 (user.gw1000)
Dec 31 15:49:50 raspberrypi weewx[5532] INFO user.gw1000: field
map is {'UV': 'uvi', 'dateTime': 'datetime', 'dayRain': 'rainday',
'daymaxwind': 'daymaxwind', 'dewpoint': 'dewpoint', 'extraHumid1':
'humid1', 'extraHumid2': 'humid2', 'extraHumid3': 'humid3',
'extraHumid4': 'humid4', 'extraHumid5': 'humid5', 'extraHumid6':
'humid6', 'extraHumid7': 'humid7', 'extraHumid8': 'humid8',
'extraTemp1': 'temp1', 'extraTemp2': 'temp2', 'extraTemp3':
'temp3', 'extraTemp4': 'temp4', 'extraTemp5': 'temp5',
'extraTemp6': 'temp6', 'extraTemp7': 'temp7', 'extraTemp8':
'temp8', 'heatindex': 'heatindex', 'hourRain': 'rainhour',
'inHumidity': 'inhumid', 'inTemp': 'intemp', 'leak1': 'leak1',
'leak2': 'leak2', 'leak3': 'leak3', 'leak4': 'leak4',
'lightning_distance': 'lightningdist', 'lightning_last_det_time':
'lightningdettime', 'lightning_strike_count':
'lightning_strike_count', 'luminosity': 'light', 'monthRain':
'rainmonth', 'outHumidity': 'outhumid', 'outTemp': 'outtemp',
'pm2_5': 'pm251', 'pm2_51_24hav': 'pm251_24hav', 'pm2_52':
'pm252', 'pm2_52_24hav': 'pm252_24hav', 'pm2_53': 'pm253',
'pm2_53_24hav': 'pm253_24hav', 'pm2_54': 'pm254', 'pm2_54_24hav':
'pm254_24hav', 'pressure': 'absbarometer', 'rain': 'rain',
'rainEvent': 'rainevent', 'rainRate': 'rainrate', 'relbarometer':
'relbarometer', 'soilMoist1': 'soilmoist1', 'soilMoist2':
'soilmoist2', 'soilMoist3': 'soilmoist3', 'soilMoist4':
'soilmoist4', 'soilMoist5': 'soilmoist5', 'soilMoist6':
'soilmoist6', 'soilMoist7': 'soilmoist7', 'soilMoist8':
'soilmoist8', 'soilMoist9': 'soilmoist9', 'soilMoist10':
'soilmoist10', 'soilMoist11': 'soilmoist11', 'soilMoist12':
'soilmoist12', 'soilMoist13': 'soilmoist13', 'soilMoist14':
'soilmoist14', 'soilMoist15': 'soilmoist15', 'soilMoist16':
'soilmoist16', 'soilTemp1': 'soiltemp1', 'soilTemp2': 'soiltemp2',
'soilTemp3': 'soiltemp3', 'soilTemp4': 'soiltemp4', 'soilTemp5':
'soiltemp5', 'soilTemp6': 'soiltemp6', 'soilTemp7': 'soiltemp7',
'soilTemp8': 'soiltemp8', 'soilTemp9': 'soiltemp9', 'soilTemp10':
'soiltemp10', 'soilTemp11': 'soiltemp11', 'soilTemp12':
'soiltemp12', 'soilTemp13': 'soiltemp13', 'soilTemp14':
'soiltemp14', 'soilTemp15': 'soiltemp15', 'soilTemp16':
'soiltemp16', 'totalRain': 'raintotals', 'uvradiation': 'uv',
'weekRain': 'rainweek', 'wh25_batt': 'wh25_batt', 'wh26_batt':
'wh26_batt', 'wh31_ch1_batt': 'wh31_ch1_batt', 'wh31_ch2_batt':
'wh31_ch2_batt', 'wh31_ch3_batt': 'wh31_ch3_batt',
'wh31_ch4_batt': 'wh31_ch4_batt', 'wh31_ch5_batt':
'wh31_ch5_batt', 'wh31_ch6_batt': 'wh31_ch6_batt',
'wh31_ch7_batt': 'wh31_ch7_batt', 'wh31_ch8_batt':
'wh31_ch8_batt', 'wh40_batt': 'wh40_batt', 'wh41_ch1_batt':
'wh41_ch1_batt', 'wh41_ch2_batt': 'wh41_ch2_batt',
'wh41_ch3_batt': 'wh41_ch3_batt', 'wh41_ch4_batt':
'wh41_ch4_batt', 'wh51_ch1_batt': 'wh

Fwd: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

2021-01-01 Thread Rainer Lang


@ (not only) weatherlist

If you had copied the list completely,  😉

See below - bold by me.

(but possibly a SSD comes cheaper than the higher capacity SLC micro SD 
cards - still may need an enclosure with USB (best 3) interface; not too 
expensive either)


.

Meteobridge enforces the use of one of the following industrial SLC cards:

..

 * Western Digital/SanDisk SDSDQED-00*8G*-XI, SDSDQED-0*16G*-XI,
   SDSDQED-0*32G*-XI, SDSDQED-064G-XI (microSD Card, 8-*64* GB, SLC Flash)
 * Greenliant GLS93MP008G1-I-BZ801 (microSD Card, *8 GB*, SLC Flash)

On 01.01.2021 20:44, Michael Form wrote:
As someone has previously suggested, you can boot and run a Raspberry 
Pi off of a SSD. These are a lot more reliable than most SD cards and 
are available with huge capacities. Unless you are buying a 1 TB or 2 
TB SSD, they are also relatively inexpensive. I am running several 
Pis, both models 3 and 4, on some 500 GB and 250 GB SSDs with no 
problems. You can also use a MSATA or M2 drive as well.


Although there are off the shelf solutions to do this (check out 
Geekworm), the easiest way is to buy an inexpensive SATA, MSATA or M2 
to USB external interface and plug it into the Pi's USB port. If you 
use a Pi4, then you can run it as a USB3 device, which is faster.


Mike

On 1/1/2021 2:21 PM, steeple...@gmail.com wrote:


There are more SLC cards available from Mouser and other distributors 
with much lager capacities. Those quoted below would struggle to 
contain an operating system, WeeWX and data.


Sent from Mail  for 
Windows 10


*From: *weather list 
*Sent: *01 January 2021 17:32
*To: *weewx-user@googlegroups.com 
*Subject: *Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 
months of data?


The Meteobridge builder requires a high endurance microSD card for 
their NANO SD unit; I haven’t investigated to see if they come in 
higher capacities though it seems likely they would.


*Choice of microSD Card *

To avoid lots of system fails caused by worn out consumer microSD 
cards we restrict microSD cards that can be used in the NANO to 1GB 
and 2GB industrial SLC cards. These are world-wide available from 
Mouser and other electronic distributors. We decided to enforce use 
of these high endurance cards to avoid having tons of unnecessary 
support requests and not to harm the reputation of the NANO SD by 
failed cards. Please trust in our experience with flash storage 
issues that there is simply no reasonable way to avoid buying of 
high-price, high-endurance SLC storage. These are the currently 
supported microSD cards:


swissbit SFSD1024N1BM1TO-I-DF-221-STD (microSD Card, 1 GB, SLC Flash, 
-40°C - 85°C)
swissbit SFSD2048N1BM1MT-I-ME-221-STD (microSD Card, 2 GB, SLC Flash, 
-40°C - 85°C)


swissbit SFSD2048N1BM1MT-E-ME-221-STD (microSD Card, 2 GB, SLC Flash, 
-25°C - 85°C)

ATP AF2GUDI (microSD Card, 2 GB, SLC Flash, -40°C – 80°C)
Cactus KS2GRIT-803M (microSD Card, 2 GB, SLC Flash, -45°C – 90°C)

Panasonic SMSC02DA1 (microSD Card, 2 GB, SLC Flash, -40°C - 85°C)

Apacer MSD02GIDI-T (microSD Card, 2 GB, SLC Flash)





On 1 Jan, 2021, at 08:52, Joe mailto:my.droid.phone.1...@gmail.com>> wrote:

Sandisk extreme with the red and brown two tone color.
Unfortuantely, I did not have one of these in the PI at the
time.  Though I do now.  I've never had one fail .

On Monday, December 28, 2020 at 7:23:04 PM UTC-6
robcr...@gmail.com  wrote:

With all this talk about "good quality" SD cards, can anyone
share a recommendation?

I have an SSD that I run my main WeeWX/HomeAssistant server
on, but I have several others that I play around with, and
need to get some new SD cards for that purpose, so I figure I
may as well get some "good" ones.

Thanks for any suggestions.

On Monday, December 28, 2020 at 4:36:23 AM UTC-8 Joe wrote:

Ok I will get a look at it in about a week after a needed
vacation.

On Sunday, December 27, 2020 at 8:38:26 PM UTC-6
graha...@gmail.com wrote:

the .html timestamps are all current (assuming Dec 27
19:50 is current).

the .png timestamps are current until middle of the
month images, then all old → stopping part way
through image generation.

some of the .png timestamps are very late in the 5
minute reporting period → maybe not finishing one
report before starting the next.

you will need to look at (post here) the detailed log
showing from before the start of report generation
until past the end of completion of report generation
to see if there is overlap.

or maybe the image generator is crashing part-wa

[weewx-user] Re: weewx crashed - issue with gw1000.py when Ecowitt WH45 5-in-1 combo sensor gets activated (5= T&H&CO2+PM2.5+PM10) [2b]

2021-01-01 Thread Rainer Lang

As for me, the code of the new driver (0.2.1b1) works fine as far as I
can tell.

All data arrives and can be addressed, and the application doesn't crash
anymore.
It can be archived (some assignment needed as not all fields are part of
the extended database schema),

and it can be used in the reports.

And the order in the field map is:

...

'pm2_5': 'pm251', # =WH41/43 #1
'pm2_52': 'pm252', # =WH41/43 #2
'pm2_53': 'pm253', # =WH41/43 #3
'pm2_54': 'pm254', # = WH41/43 #4
'pm2_55': 'pm255', # = WH45 PM2.5
'pm10': 'pm10', # = WH45 PM10
'co2': 'co2', # =WH45 CO2

...

Temperature and Humidity are sorted into the extraTemperature 'section'
as #17

Here I don't really understand George's request regarding sequence/order
either.

"
Please note that even though the raw data coming from this new sensor is
for the PM10 to come first and then the PM2.5 that is not the order that
we would typically refer to the sensor as ...it is /*called the PM2.5,
PM10, CO2 sensor in that order*/. Looking at the GW1000 API
documentation it baffles me why the engineers decided to send PM10 data
first. Also on the GW1000 mobile app (WS View) and on Ecowitt.net the
order is also PM2.5 first and then PM10. /*I fee therefore that WeeWX
should keep the order as PM2.5 first and then PM10.*/"

@George: maybe you explain more in detail what exactly you mean, where
some sequence (order) is not maintained and why this is important 😎.

At least in the field map (in my terms/language: the weewx GW1000 driver
interface record declaration [but we may have different wording here,
depending on our
programming language history]) exactly this sequence (order) is
maintained. Where else is this order missing ?

At the end of the day, e.g. in the WSView app, it's a matter of
presentation. And which sequence/order you choose for showing this data
in the reports (e.g. Seasons skin)
is up to you. There is no preset report for the WH45 data (yet), afaik,
but my knowledge may not be complete.

On 01.01.2021 22:20, Paul Ward wrote:
Gary I have a WH45 on order so subject to shipping delays I’m happy to
test the code too in couple of weeks when I get it, if you don’t
release beforehand.

On Friday, January 1, 2021 at 1:26:45 AM UTC gjr80 wrote:

WH45 support was coded some time ago though of course not tested
with an actual device. Have had a number of other features I was
working on to add at the same time which delayed release of the
WH45 compatible version of the driver. Rainer now has a copy of a
compatible version of the driver to test and once he confirms it
works I will shortly afterwards release the WH45 compatible version.

As an aside, and on a technical note, this did highlight that I
need to change the approach the driver uses to dealing with sensor
data from the GW1000. Ideally adding an new sensor type should not
cause a driver that does not know about that new sensor type to
crash; rather the driver should continue to operate but just not
provide data for the (to it) unknown sensor. This will be
something to work on for the next version of the driver,
fortunately Ecowitt is not releasing new sensors that often.

Gary

--
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/afcd4401-6b46-421f-a25c-e74aa235e870n%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/2497c1c8-8489-ecd5-2d72-df0364321d93%40gmail.com.

Re: [weewx-user] Re: New to weewx, AW WS-2000

2021-01-02 Thread Rainer Lang

It works with all Ambient Weather sensors which are clones of Fine
Offset sensors.

(Ambient also sells non-Fine Offset clone sensors and weather stations)

What sensors these are, you can see at

https://www.wxforum.net/index.php?topic=40730.0

On 02.01.2021 21:34, George Morgan wrote:

Does the GW1000 work with all the AW sensors?

On Sat, Jan 2, 2021, 11:41 AM galfert > wrote:

Well there is a way to get from WS-2000 AW protocol to WeeWX...but
you need a translator. You can use FOSHKplugin and that will
convert AW protocol to Ecowitt protocol and then you can use the
WeeWX Interceptor driver.

On Saturday, January 2, 2021 at 2:17:39 PM UTC-5 gm@gmail.com
wrote:

Is there an effort to support the AW protocol for the WS-2000
server? As a developer I would be interested in working on
this if it is documented (and maybe even if it is not). My
WS-2000 has the latest wifi and base firmware installed.

I will also look into the GW-1000 and RTL SDR options.

On Sat, Jan 2, 2021, 9:58 AM galfert wrote:

The best way is to buy the GW1000 and then it will pick up
al your WS-2000 sensors. Then you install WeeWX with the
GW1000 API driver.
https://github.com/gjr80/weewx-gw1000

There is not telnet with the WS-2000. The Interceptor
driver will not pick up all your sensorsif you have
added optional sensors. Besides with the WS-2000 it is too
convoluted to get the Interceptor working because there is
no "Customized" server option with the supported protocol
for the Interceptor driver. The WS-2000 newly gained
"Customized" server upload option but it is Ambient
protocol which is different than what the Interceptor expects.

On Saturday, January 2, 2021 at 10:29:32 AM UTC-5
gm@gmail.com wrote:

Hi All,

I received a weather station for Christmas and
realized really quickly that I want / need something
like weewx to make it much more capable.

I saw in the list archives that others are using weewx
with the WS-2000, intercepting WU data. Is there
another method where weewx polls the WS-2000 or
receives data directly from the WS-2000? I noticed
the telnet protocol info on the AW website but haven't
figured out which port the WS-2000 is using for this
communication? If I am barking up the wrong tree,
please let me know.

BTW, I have a background in computer networking,
software development (day job), system administration
(day job), and have been doing automation for many years.

Please let me know if this is a more appropriate
question for the dev list.

Happy New Year!

--
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/a4f2febd-177e-4160-aef2-23d0f3a064d3n%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/26ac7b65-73ef-4991-856e-7e3b979d3e9bn%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/CAJ%2B0VHzg5APMmRJnbV6ubLfG%3DvpJFWsk9vwLwR%3DrfAz0-V0Lrg%40mail.gmail.com
.

--
You received this message because you are subscribed

[weewx-user] Re: New to weewx, AW WS-2000

2021-01-04 Thread Rainer Lang

Correct, for power only. You can use any phone charger, USB hub etc. to 
keep it running. Even plug it into a USB port of a Raspberry Pi if you 
have one ...
A good idea will be to have the power source connected to a UPS, as well 
as your weather computer :-), or have it connected to a power-bank which 
you keep on charging - many possibilities.

On 04.01.2021 17:38, George Morgan wrote:
Well I ordered a GW1000.  Now I'm thinking about how to power it.  The 
USB connector is only used for power, right?


On Sun, Jan 3, 2021, 7:52 PM galfert <mailto:galf...@gmail.com>> wrote:


I meant to say water leak not water lead sensor.


On Sunday, January 3, 2021 at 10:51:34 PM UTC-5 galfert wrote:

The WS-2000 does not support more sensors than the GW1000. Its
the other way around. The GW1000 supports every single sensor
that the WS-2000 support, plus it supports sensors from
Ecowitt that Ambient doesn't sell, WH32-EP, WH31-EP, WH45 to
name a few, and Ecowitt is working on some sensors that they
will have before Ambient gets them (new soil moisture with
temperature). The GW1000 also had support for water lead and
lightning many months before the WS-2000.



On Sunday, January 3, 2021 at 8:42:57 PM UTC-5
gm@gmail.com wrote:

Thanks for the link to the chart...I need to look at it
closer but I think my WS-2000 supports more sensors than
the GW1000 so I may be looking at integrating FOSHK
plug-in into weewx directly...unless I'm missing something...

I also need to look at the license for FOSHK plug-in as
that may make this impossible (legally, that is)

On Sat, Jan 2, 2021, 12:40 PM Rainer Lang
 wrote:

It works with all Ambient Weather sensors which are
clones of Fine Offset sensors.

(Ambient also sells non-Fine Offset clone sensors and
weather stations)

What sensors these are, you can see at

https://www.wxforum.net/index.php?topic=40730.0
<https://www.wxforum.net/index.php?topic=40730.0>


On 02.01.2021 21:34, George Morgan wrote:

Does the GW1000 work with all the AW sensors?

On Sat, Jan 2, 2021, 11:41 AM galfert
 wrote:

Well there is a way to get from WS-2000 AW
protocol to WeeWX...but you need a translator.
You can use FOSHKplugin and that will convert AW
protocol to Ecowitt protocol and then you can use
the WeeWX Interceptor driver.


On Saturday, January 2, 2021 at 2:17:39 PM UTC-5
gm@gmail.com wrote:

Is there an effort to support the AW protocol
for the WS-2000 server?  As a developer I
would be interested in working on this if it
is documented (and maybe even if it is not). 
My WS-2000 has the latest wifi and base
firmware installed.

I will also look into the GW-1000 and RTL SDR
options.

On Sat, Jan 2, 2021, 9:58 AM galfert
 wrote:

The best way is to buy the GW1000 and
then it will pick up al your WS-2000
sensors. Then you install WeeWX with the
GW1000 API driver.
https://github.com/gjr80/weewx-gw1000
<https://github.com/gjr80/weewx-gw1000>

There is not telnet with the WS-2000. The
Interceptor driver will not pick up all
your sensorsif you have added
optional sensors. Besides with the
WS-2000 it is too convoluted to get the
Interceptor working because there is no
"Customized" server option with the
supported protocol for the Interceptor
driver. The WS-2000 newly gained
"Customized" server upload option but it
is Ambient protocol which is different
than what the Interceptor expects.


On Saturday, January 2, 2021 at 10:29:32
AM UTC-5 gm@gmail.com wrote:

Hi All,

I received a weather station for
Christmas and realized really quickly

[weewx-user] weewx and Klimalogg Pro - looking for advice

2021-01-04 Thread Rainer Lang

I'm running weewx on Raspberry Pi with my Klimalogg Pro (KLP) and the KL 
extension/skin.


At the first start it reads all the existing data records from the 
Klimalogg Pro (52,000+) and stores them in the database.

Great!

Now I observed that when the connection for some reason gets lost - or 
the RPi shut down longer than the archive window -
and weewx restarts (or I restart weewx), it seems to to check the 
records stored in the KLP, but skips them all and continues
to store new records only from the new startup date/time and ignores the 
records collected by the KLP in between. Out of this

obviously data storage gaps occur.

Anyone has any idea how to make/force weewx continue storing the missing 
data, i.e. reading them from the KLP and store them based on the last 
timestamp in the database at restart before it continue storing new data ?


Feedback appreciated.

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ee5873e8-b915-d27c-ad22-1ad9a31fa11a%40gmail.com.

Re: [weewx-user] Re: weewx and Klimalogg Pro - looking for advice

2021-01-04 Thread Rainer Lang

not very long (except for the initial check - here are 51,330 records to 
be covered)


- the story is (I meanwhile checked the data base content and the 
syslog) that weewx continues writing (empty) records when it isn't 
connected to the console.
I think that's the reason for not reading the missed records as the is a 
record (though empty) for the respective timestamps (archiving window = 
1 minute).


Weewx should stop writing (empty records) into the database until it 
receives the signal from the console again. Then check (like at the 
initial start)
which historical records are missing, i.e. exist in the console memory 
but not yet in the weewx database, retrieve and store them
and then continue with business as usual (archiving in the interval, 
writing summary records, print charts ...)


below the relevant syslog excerpts:

I had weewx starting from scratch again - empty database - it was then 
reading all available historical records in the console and stored 
(archived) them

see below


Jan  4 14:20:50 raspberrypi weewx[29188] INFO user.kl: 
handleHistoryData: records cached=1766, records skipped=7, next=38341.0
Jan  4 14:20:50 raspberrypi weewx[29188] INFO user.kl: 
handleHistoryData: records cached=1772, records skipped=7, next=38347.0
Jan  4 14:20:51 raspberrypi weewx[29188] INFO user.kl: 
handleHistoryData: records cached=1778, records skipped=7, next=38353.0
Jan  4 14:20:51 raspberrypi weewx[29188] INFO user.kl: 
handleHistoryData: records cached=1784, records skipped=7, next=38359.0
Jan  4 14:20:51 raspberrypi weewx[29188] INFO user.kl: 
handleHistoryData: records cached=1790, records skipped=7, next=38365.0
Jan  4 14:20:52 raspberrypi weewx[29188] INFO user.kl: 
handleHistoryData: records cached=1796, records skipped=7, next=38371.0

Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Records scanned: 1800
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Found 1799 
historical records
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle record 
46801: 2021-01-01 11:00:00 CET (1609495200)
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle record 
46802: 2021-01-01 11:01:00 CET (1609495260)
Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-01 11:01:00 CET (1609495260) to database 'weewx-kl.sdb'
Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-01 11:01:00 CET (1609495260) to daily summary in 
'weewx-kl.sdb'
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle record 
46803: 2021-01-01 11:02:00 CET (1609495320)
Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-01 11:02:00 CET (1609495320) to database 'weewx-kl.sdb'
Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-01 11:02:00 CET (1609495320) to daily summary in 
'weewx-kl.sdb'
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle record 
46804: 2021-01-01 11:03:00 CET (1609495380)


.

now the loading comes to an end and weewx runs in normal mode (i.e. 
reading not history but actual data)


.

Jan  4 14:33:50 raspberrypi weewx[29188] INFO user.kl: Handle record 
51329: 2021-01-04 14:31:00 CET (1609767060)
Jan  4 14:33:50 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-04 14:31:00 CET (1609767060) to database 'weewx-kl.sdb'
Jan  4 14:33:50 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-04 14:31:00 CET (1609767060) to daily summary in 
'weewx-kl.sdb'
Jan  4 14:33:50 raspberrypi weewx[29188] INFO user.kl: *Handle record 
51330:* 2021-01-04 14:32:00 CET (1609767120)
Jan  4 14:33:50 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-04 14:32:00 CET (1609767120) to database 'weewx-kl.sdb'
Jan  4 14:33:50 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-04 14:32:00 CET (1609767120) to daily summary in 
'weewx-kl.sdb'
Jan  4 14:33:50 raspberrypi weewx[29188] INFO user.kl: *Saved 929 
historical records; ts last saved record 2021-01-04 14:32:00 CET 
(1609767120)*
Jan  4 14:33:50 raspberrypi weewx[29188] INFO /*weewx.engine: Starting 
main packet loop.*/
Jan  4 14:34:20 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-04 14:34:00 CET (1609767240) to database 'weewx-kl.sdb'
Jan  4 14:34:20 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-04 14:34:00 CET (1609767240) to daily summary in 
'weewx-kl.sdb'
Jan  4 14:34:20 raspberrypi weewx[29188] INFO weewx.cheetahgenerator: 
Generated 1 files for report kl in 0.28 seconds
Jan  4 14:34:29 raspberrypi weewx[29188] INFO weewx.imagegenerator: 
Generated 33 images for report kl in 8.42 seconds
Jan  4 14:35:30 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-04 14:35:00 CET (1609767300) to database 'weewx-kl.sdb'
Jan  4 14:35:30 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-04 14:35:00 CET (1609767300) to daily summary in 
'weewx-kl.

Re: [weewx-user] Re: weewx and Klimalogg Pro - looking for advice

2021-01-04 Thread Rainer Lang



On 04.01.2021 22:50, vince wrote:

So you're saying:

  * periodically loses connection to the station
*/rather rarely - but at times (1-5 times in a year, usually due
to maintenance - see below)/**/
/**/it also technically happens during a reboot or a short time
shut down of the RPi
/*/(before, when I had it run on Windows, reboots for update would
interrupt the connection,
and once a power cut)/*/
the hardware - a USB transceiver, is pretty reliable
/*
  * yet when that happens it keeps writing out empty (your words)
records every archive period
/*correct - I guess that's the main issue*/
  * and when you press the button to reconnect to the station, you
expect weewx to grab any historical records ?
/*wouldn't that make sense ??  Or after a reboot or so */

The first one sounds like a hardware issue.  The second one is a 
possible bug.  The third is a feature request.
/*I think 2 and 3 are more or less interconnected - the KLP has this 
memory capacity to allow for disconnections of the software*//*
*//*But then the software should also do it i.e. pick up missed data - 
the Windows version of the software does this by the way, and does it 
properly*/
/*If this could be handled by some simple options, entries in e.g. 
weewx.conf, that would be the advice I'm looking for - I don't know if 
such a thing exists,
hence the question. If the developers of the extension still exist and 
were ready to fix that, this would be even greater.*/


That sound correct to you ? -/*with the addenda in bold italics, yes*/

(I don't have a KLP so I can't speculate on how to fix your periodic 
loss of connectivity thing that starts the avalanche of issues, but I 
wanted to ask if I'm reading the problem description correctly)



On Monday, January 4, 2021 at 1:26:03 PM UTC-8 lang@googlemail.com 
wrote:


not very long (except for the initial check - here are 51,330
records to be covered)

- the story is (I meanwhile checked the data base content and the
syslog) that weewx continues writing (empty) records when it isn't
connected to the console.
I think that's the reason for not reading the missed records as
the is a record (though empty) for the respective timestamps
(archiving window = 1 minute).

Weewx should stop writing (empty records) into the database until
it receives the signal from the console again. Then check (like at
the initial start)
which historical records are missing, i.e. exist in the console
memory but not yet in the weewx database, retrieve and store them
and then continue with business as usual (archiving in the
interval, writing summary records, print charts ...)

below the relevant syslog excerpts:

I had weewx starting from scratch again - empty database - it was
then reading all available historical records in the console and
stored (archived) them
see below


Jan  4 14:20:50 raspberrypi weewx[29188] INFO user.kl:
handleHistoryData: records cached=1766, records skipped=7,
next=38341.0
Jan  4 14:20:50 raspberrypi weewx[29188] INFO user.kl:
handleHistoryData: records cached=1772, records skipped=7,
next=38347.0
Jan  4 14:20:51 raspberrypi weewx[29188] INFO user.kl:
handleHistoryData: records cached=1778, records skipped=7,
next=38353.0
Jan  4 14:20:51 raspberrypi weewx[29188] INFO user.kl:
handleHistoryData: records cached=1784, records skipped=7,
next=38359.0
Jan  4 14:20:51 raspberrypi weewx[29188] INFO user.kl:
handleHistoryData: records cached=1790, records skipped=7,
next=38365.0
Jan  4 14:20:52 raspberrypi weewx[29188] INFO user.kl:
handleHistoryData: records cached=1796, records skipped=7,
next=38371.0
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Records
scanned: 1800
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Found 1799
historical records
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle
record 46801: 2021-01-01 11:00:00 CET (1609495200)
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle
record 46802: 2021-01-01 11:01:00 CET (1609495260)
Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added
record 2021-01-01 11:01:00 CET (1609495260) to database 'weewx-kl.sdb'
Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added
record 2021-01-01 11:01:00 CET (1609495260) to daily summary in
'weewx-kl.sdb'
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle
record 46803: 2021-01-01 11:02:00 CET (1609495320)
Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added
record 2021-01-01 11:02:00 CET (1609495320) to database 'weewx-kl.sdb'
Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added
record 2021-01-01 11:02:00 CET (1609495320) to daily summary in
'weewx-kl.sdb'
Jan  4 14:21:01 raspberry

Re: [weewx-user] Re: GW1000 driver v0.2.0 release

2021-01-09 Thread Rainer Lang

Hi Vince,
as far as I can tell there is no gap between WSView app (FW 1.6.3) and
the data provided by the new driver.

I already had a pre-release version installed as my weewx installation
crashed with my new WH45 sensors.
(That's the last line in the wiki update by Gary - the program shouldn't
crash when meeting a sensor it doesn't know).

And the pre-release worked fine. Haven't tried the final release yet.

On 09.01.2021 20:44, vince wrote:

Works great here, thanks. Also liked the wiki pages.

I noted the new (?) _sig values in --live-data
Mine all show a value of 4
I'm assuming the values are 0-4 where 4 is best (???)

What else is now available that was previously only in the WS View app ?

unrelated - I have a minimalist skin for EcoWitt
at https://github.com/vinceskahan/weewx-ecowitt-skin if anybody is
interested...

On Saturday, January 9, 2021 at 3:47:59 AM UTC-8 gjr80 wrote:

I have released v0.2.0 on GitHub
.

This main feature of this release is support for the WH45 Indoor
CO2 PM2.5 PM10 Temperature and Humidity 5-in-1 Air Quality Sensor.
If you have a WH45 sensor and it has been linked to your GW1000
v0.2.0 of the driver should automatically pick up and emit the
WH45 sensor data.

v0.2.0 also sees changes in the naming of the 24 hour average
particulate concentration fields. Unfortunately this will mean
anyone that is using these fields will need to make one or more
changes to their WeeWX installation. I have outlined the changes
and which users need to make changes and how to make the necessary
changes in a wiki article Changes to 24 hour average particulate
concentration field names

.
If you have a WH41, WH43 or WH45 sensor and use the 24 hour
average particulate concentration fields in any way I strongly
suggest you thoroughly read the linked wiki article.

The majority of the other changes in v0.2.0 relate to running the
driver directly, in particular displaying the GW1000 and sensor
configuration information currently only available through the WS
View app.

Those that installed v0.1.0 via wee_extension can upgrade to
v0.2.0 as follows:

$ wget -P /var/tmp

https://github.com/gjr80/weewx-gw1000/releases/download/v0.2.0/gw1000-0.2.0.tar.gz

$ wee_extension --install=/var/tmp/gw1000-0.2.0.tar.gz

Note: wee_extension may require the use of sudo the path to
wee_extension as applicable.

Gary

--
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/12972026-34e3-4f8f-ab50-e9309c706fa7n%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/4c7ed1b5-b82a-874b-3fd5-11af4eb4bd5b%40gmail.com.

Re: [weewx-user] Re: New to weewx, AW WS-2000

2021-01-12 Thread Rainer Lang


A few more thing - some might sound sort of a bit stupid, but ...

are the sensors you are missing activated in the WSView app ?

The best way to test is
a) look into the WSView app (Device list --> GW1000 --> More --> SensorIDs)
the sensor should be active and a (hexadecimal) sensor ID should be 
visible together with a reception indicator.


b) take your WH31 sensors and put them 1-2 meters (yards) away from the 
GW1000 and check again.

Then there shouldn't be any interference.

the following is just for the principle, to make the check list complete 
- I read from your post that the console receives your WH31 sensors.


(If you have more than one, make sure they send on different channels. 
The display shows what channel you use (there are DIP switches for that 
- on the newer ones the meaning is printed inside; if not, check the 
manual :-) ).
Check the batteries. Check what the WH31 display shows. If you don't see 
anything on the display, there is a power problem. Exchange the 
batteries resp. verify if you have put them according to the needed 
polarity.)


That the WH32B of the WS2000/5000 console can't be read by the GW1000, 
galfert has already said.


By the way - you can also already power up (i.e. put the batteries into) 
your sensor array. It should show next to the array symbol on the very 
top in the WSView app.


And one more, maybe too trivial thing. When you come from the device 
list to the live data, you cannot see the WH31 sensors at first glance.

You have to page down in order to see them.



On 12.01.2021 18:24, galfert wrote:
The only sensor that will not work with the GW1000 is the WH32Band 
there is no need for it. Because the GW1000 already has this sensor 
built in. If you are having problems picking up the WH31, then that 
would be a distance/interference issue. But compared to the WS-2000 
the GW1000 is actually capable of detecting sensors further away.



On Tuesday, January 12, 2021 at 2:41:27 AM UTC-5 gm@gmail.com wrote:

Yes, I was able to view the live data page but it only shows the
sensors directly attached to the GW1000 so I figure it is getting
too much RF interference to pick up my T&H (WH-31?) and THP
(WH-32B) sensors.  I still haven't decided where to mount the main
sensor array from the WS-2000...I really need to put up a comms
mast but that will take much more planning and time.  My home has
primarily a hip roof which presents very little unobstructed
opportunities for mounting.  I do know which channels they show up
on from the WS-2000 console...

    On Mon, Jan 11, 2021, 3:14 PM 'Rainer Lang' via weewx-user
 wrote:

Whether the GW1000 picks up your sensors or not, you can very
simply verify by choosing your GW1000 from the WSView Device
list. One entry will read GW1000-WIFI. That's the one to
press. As a result you will see the live data of the connected
sensors.



Am 11. Januar 2021, um 16:45, schrieb George Morgan
:


Yes, I used ws view on Android from the Play Store.  After a
little while the app asked if I wanted to update the firmware
to 1.6.3 and I did. That seemed to work fine.

The GW1000 is joined to my network but I don't think it is
picking up any sensors yet.

On Sun, Jan 10, 2021, 11:16 PM Bill Arthur 
wrote:

The GW1000 is configured with the WS View app. Are you
using it?

On Monday, January 11, 2021 at 12:54:01 AM UTC-6
gm@gmail.com wrote:

I finally received my GW1000 last night.  Got it
powered up and connected to my network but I'm having
some difficulty configuring the sensors.

The sensor ID page seems to have all sensors enabled
and I only have the inside sensor (THP) and one TH
sensor deployed so far.  I tried looking at the sensor
ID page from the WS-2000 console and manually pick the
channels detected on that screen but not sure if the
GW1000 is picking them up or not.  I still need to get
the GW1000 on a USB extension.  I have it plugged into
a banana pi m1 USB port right now for power. (I plan
to install weewx on the banana pi m1 soon...need a few
more pieces of hardware before I can finish getting
that set up)

Hopefully when I get the GW1000 on a USB extension
cable it will be able to pick up the sensors.  Or I
may have to find a different power source / location
for it.

On Mon, Jan 4, 2021, 10:25 AM Bill Arthur
 wrote:

I use a three foot USB extension cord on the
GW1000. I had one instance whe

Re: [weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

2021-01-16 Thread Rainer Lang

I don't think you properly understood what galfert was saying resp. what
he wanted to say:

what he meant was that an _additional_ Ecowitt GW1000 displayless
console (+/- 36 USD) would do the best job. If you don't know the piece,
I recommend to look it up at ecowitt.com. It's a matchbox size USB port
powered console.

With it you can receive (and process in weewx) all the sensors of your
WH2900 sensor array plus all extra sensors Ecowitt or Ambient or other
Fine Offset clone resellers offer

if you decide to purchase them by the help of the weewx GW1000 API driver.

WH2910 indicates to me that it is not an Ambient but an Ecowitt or other
FIne Offset clone device you are talking about/own.
Then you could (but that's rather old fashioned and has got several
caveats) also use the weewx Interceptor driver and the customized server
push data functionality of your WH2910 console.

On 16.01.2021 20:54, S R wrote:

actually, mine is equivalent to the WH2910 - it is not a case of
getting, i already have

On Saturday, January 16, 2021 at 4:42:53 PM UTC+1 galfert wrote:

You have dug up quite an old thread. A lot has changed since. The
recommendation now is to just acquire the Ecowitt GW1000 and use
the WeeWX GW1000 API driver. The GW1000 will directly pick up your
sensor data (it doesn't talk to the display console...as it is its
own console). You'll get a much nicer experience with the GW1000,
which will also let you add extra sensors.
https://github.com/gjr80/weewx-gw1000

On Saturday, January 16, 2021 at 2:43:44 AM UTC-5
sjr4...@gmail.com wrote:

were you able to get this to work in the end. can you share
the weewx details please

On Saturday, April 1, 2017 at 4:37:01 PM UTC+2
44085w...@gmail.com wrote:

I see that weewx is said to support the FINE OFFSET WH2900
, I was wondering if anyone could share with me the
protocol and port information that is in the driver? I

--
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/853cc4c5-709d-491f-97b8-3fec2a1548d9n%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/5197005a-48fd-9c65-dcd3-bb932cf98df8%40gmail.com.

Re: [weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

2021-01-17 Thread Rainer Lang

As a workaround I would remove / replace your suspects - change 
"Umlaute", if any, from Ä -> AE, Ö -->OE, Ü --> UE, accents just omit 
them and leave the vowels without them.
They will anyway only appear in temporary graphs. Then figure out your 
UTF-8 issue and fix it, while your weewx could already run and archive data.


On 17.01.2021 19:59, S R wrote:
thanks for the clarification. i will switch the protocol to ecowitt, 
but the more immediate problem is the UTF-8 error which is now 
preventing weewx from starting.


On Sunday, January 17, 2021 at 4:30:38 PM UTC+1 galfert wrote:

This thread started with the discussion being around the Ambient
WS-2902 and that is totally different despite looking like the
same unit. This is because Ambient is the only Fine Offset clone
reseller that changes the firmware and they limit options. The
Ambient version does not let you upload to custom server address.
The confusion here is that my response was because I thought you
had and Ambient branded unit. Since you don't have an Ambient
branded unit you do have the option to send to a custom server
using both WU and Ecowitt protocols. The WU protocol is limited
and only sends the basic set of sensors. The Ecowitt protocol
allows you to send a lot more optional sensors like PM2.5, soil
moisture, extra temp/hum sensorsetc. But still you'll have to
configure the Interceptor driver to match the protocol type that
you set in you WH2900C for uploading to your custom server.

The GW1000 though is still a more elegant and newer solution.

* The newest Ambient WS-2902 firmware finally after many years
does gain the ability to send to a custom serverBUT it is not
WU protocol and it is not Ecowitt protocolit is
Ambientweather.net protocol and enough significant differences
that the Interceptor driver will not work. This newest firmware is
not yet officially supported by Ambient. They haven't yet release
the updated awnet mobile app to enable turning and configuring
this option. All of these complexities and changing nature of the
situation makes it difficult to explain the situation to cover all
possible scenarios...what model you have and whom it is from and
what firmware version you are running and all the different
supporting protocols that are possible.

Using pfsense to capture and forward packets is really unnecessary
for anyone with a non-Ambient WH2900Cas it has a built in
simple to configure "Customized" server upload feature.



On Sunday, January 17, 2021 at 7:32:03 AM UTC-5 sjr4...@gmail.com
wrote:

For the record, mine is a Chinese Mi-Sol WH2900C. It is a copy
of the Fine Offset WH2900 or the Ecowitt WS2950. Indeed, the
unit requires a connection to Ecowitt to set the Time/Date and
automatically downloaded the EasyWeather 1.56 firmware update
from Ecowitt.

I haven't got the outdoor setup done yet, while i play with
getting the unit up and running. but Ecowitt, shows my indoor
temperature and pressure on the home page. I use pfsense so
can run a packet capture if it helps. Since editing the
weewx.conf file, i am getting the utf-8 problem. I guess this
is related to me using European accented characters in my
editors which are UTF-8. So that leaves me with two questions;
1) how to have it accept the UTF-8 characters
2) you mentioned not getting all the sensor data, unless using
Ecowitt. In view, that i am. Can you tell me what additional
parameters i need in the config file please.



On Sunday, January 17, 2021 at 9:21:33 AM UTC+1 S R wrote:

almost there, but now

/usr/local/share/weewx # ./bin/wee_reports

Traceback (most recent call last):
  File "./bin/wee_reports", line 103, in 
    main()
  File "./bin/wee_reports", line 51, in main
    config_path, config_dict =
weecfg.read_config(options.config_path, args)
  File "/usr/local/share/weewx/bin/weecfg/__init__.py",
line 180, in read_config
    default_encoding='utf-8')
  File
"/usr/local/lib/python3.7/site-packages/configobj.py",
line 1229, in __init__
    self._load(infile, configspec)
  File
"/usr/local/lib/python3.7/site-packages/configobj.py",
line 1287, in _load
    content = self._handle_bom(content)

On Saturday, January 16, 2021 at 11:30:28 PM UTC+1 galfert
wrote:

Yes the best method when using the Interceptor is to
use the Customized server settings. The path doesn't
matter. But in some firmware versions it just couldn't
be left blank or it wouldn't send. So just put i

Re: [weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

2021-01-18 Thread Rainer Lang

I suggest that you first get weewx running with the interceptor driver 
in a simple "normal" test environment.
e.g. weewx host and console in the same subnet, no other fancy network 
and virtualization constructions.


Once that works, start changing step by step the test environment 
towards your finally planned setup and
work out the issues on the path. Imho only such a systematic approach 
will lead you to the goal.


Many of your questions seem to come from your complex environment, and 
as long as you don' find anyone
who completely understands your architecture (who would probably need a 
scheme, description, picture),
the components used, their impact etc., you will most likely not get the 
proper answers.


I suggest moving from simple to complex.
epair0b is obviously a freenas speciality ...

On 18.01.2021 12:00, S R wrote:

I see in interceptor.py the default interface is DEFAULT_IFACE = 'eth0'
if i do ifconfig in the shell to the jail, the interface is 'epair0b'

should i be changing the interface?
still can't the debug to work.

On Monday, January 18, 2021 at 8:55:28 AM UTC+1 S R wrote:

i figured out the utf-8 issue. weewx.conf has to be in utf, but i
made the mistake of editing in the shell with edit. once i used
geany and change the encoding back to utf-8 it came good.

current status is;
- console updates both ecowitt and wunderground online every minute.
- config using ecowitt protocol with custom config pointing to
local freenas jail / weewx server - path = index.php?
- using seasons default report
- weewx is not upating and pfsense is showing me below with a
packet capture, but no rules are blocking.
- i have tcp options enabled on both rules (WEEWX and WH2900C are
on different VLANs)

22    2.968670    WH2900C    WEEWX    TCP    58    20150 → 8080
[SYN] Seq=0 Win=5840 Len=0 MSS=1460
23    2.969709    WEEWX    WH2900C TCP    54    8080 → 20150 [RST,
ACK] Seq=1 Ack=1 Win=0 Len=0


On Sunday, January 17, 2021 at 8:54:36 PM UTC+1
lang@googlemail.com wrote:

As a workaround I would remove / replace your suspects -
change "Umlaute", if any, from Ä -> AE, Ö -->OE, Ü --> UE,
accents just omit them and leave the vowels without them.
They will anyway only appear in temporary graphs. Then figure
out your UTF-8 issue and fix it, while your weewx could
already run and archive data.

On 17.01.2021 19:59, S R wrote:

thanks for the clarification. i will switch the protocol to
ecowitt, but the more immediate problem is the UTF-8 error
which is now preventing weewx from starting.

On Sunday, January 17, 2021 at 4:30:38 PM UTC+1 galfert wrote:

This thread started with the discussion being around the
Ambient WS-2902 and that is totally different despite
looking like the same unit. This is because Ambient is
the only Fine Offset clone reseller that changes the
firmware and they limit options. The Ambient version does
not let you upload to custom server address. The
confusion here is that my response was because I thought
you had and Ambient branded unit. Since you don't have an
Ambient branded unit you do have the option to send to a
custom server using both WU and Ecowitt protocols. The WU
protocol is limited and only sends the basic set of
sensors. The Ecowitt protocol allows you to send a lot
more optional sensors like PM2.5, soil moisture, extra
temp/hum sensorsetc. But still you'll have to
configure the Interceptor driver to match the protocol
type that you set in you WH2900C for uploading to your
custom server.

The GW1000 though is still a more elegant and newer
solution.

* The newest Ambient WS-2902 firmware finally after many
years does gain the ability to send to a custom
serverBUT it is not WU protocol and it is not Ecowitt
protocolit is Ambientweather.net protocol and enough
significant differences that the Interceptor driver will
not work. This newest firmware is not yet officially
supported by Ambient. They haven't yet release the
updated awnet mobile app to enable turning and
configuring this option. All of these complexities and
changing nature of the situation makes it difficult to
explain the situation to cover all possible
scenarios...what model you have and whom it is from and
what firmware version you are running and all the
different supporting protocols that are possible.

Using pfsense to capture and forward packets is really
unnecessary for anyone with a non-Ambient WH2900Cas
it

Re: [weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

2021-01-19 Thread Rainer Lang


1. can you send us the system log from the time on that weewx started

otherwise difficult to say what's going on in your system

2. also add your weewx.conf

3. Have you created a temporary file system for the pictures and html 
files ?
If not (yet - that's to protect your SD card but not necessary right 
now), could you also include the content of

/var/www/html/weewx ?

that could give us some ideas wrong you are still missing


On 19.01.2021 15:14, S R wrote:

so, i connected the station on the same segment as the weewx server 
(using the linux desktop for proof of concept).


I am successfully sending / receiving on Port 8000.
Example HTTP/1.1 that is sent.

HTML Form URL Encoded: application/x-www-form-urlencoded
    Form item: "PASSKEY" = "xxx"
    Form item: "stationtype" = "EasyWeatherV1.5.6"
    Form item: "dateutc" = "2021-01-19 14:07:31"
    Form item: "tempinf" = "77.2"
    Form item: "humidityin" = "41"
    Form item: "baromrelin" = "29.537"
    Form item: "baromabsin" = "29.315"
    Form item: "freq" = "433M"
    Form item: "model" = "WS2900C_V2.01.10"

But using the seasons skin, i am not seeing any updates in the data.




On Monday, January 18, 2021 at 4:02:31 PM UTC+1 S R wrote:

i put in the network network, but i can't get the interceptor.py
debug to run. keeps falling over on the driver import line


On Monday, January 18, 2021 at 12:14:07 PM UTC+1
lang@googlemail.com wrote:

I suggest that you first get weewx running with the
interceptor driver in a simple "normal" test environment.
e.g. weewx host and console in the same subnet, no other fancy
network and virtualization constructions.

Once that works, start changing step by step the test
environment towards your finally planned setup and
work out the issues on the path. Imho only such a systematic
approach will lead you to the goal.

Many of your questions seem to come from your complex
environment, and as long as you don' find anyone
who completely understands your architecture (who would
probably need a scheme, description, picture),
the components used, their impact etc., you will most likely
not get the proper answers.

I suggest moving from simple to complex.
epair0b is obviously a freenas speciality ...

On 18.01.2021 12:00, S R wrote:

I see in interceptor.py the default interface is
DEFAULT_IFACE = 'eth0'
if i do ifconfig in the shell to the jail, the interface is 
'epair0b'

should i be changing the interface?
still can't the debug to work.

On Monday, January 18, 2021 at 8:55:28 AM UTC+1 S R wrote:

i figured out the utf-8 issue. weewx.conf has to be in
utf, but i made the mistake of editing in the shell with
edit. once i used geany and change the encoding back to
utf-8 it came good.

current status is;
- console updates both ecowitt and wunderground online
every minute.
- config using ecowitt protocol with custom config
pointing to local freenas jail / weewx server - path =
index.php?
- using seasons default report
- weewx is not upating and pfsense is showing me below
with a packet capture, but no rules are blocking.
- i have tcp options enabled on both rules (WEEWX and
WH2900C are on different VLANs)

22    2.968670    WH2900C    WEEWX    TCP    58 20150 →
8080 [SYN] Seq=0 Win=5840 Len=0 MSS=1460
23    2.969709    WEEWX WH2900C    TCP    54    8080 →
20150 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0


On Sunday, January 17, 2021 at 8:54:36 PM UTC+1
lang@googlemail.com wrote:

As a workaround I would remove / replace your
suspects - change "Umlaute", if any, from Ä -> AE, Ö
-->OE, Ü --> UE, accents just omit them and leave the
vowels without them.
They will anyway only appear in temporary graphs.
Then figure out your UTF-8 issue and fix it, while
your weewx could already run and archive data.

On 17.01.2021 19:59, S R wrote:

thanks for the clarification. i will switch the
protocol to ecowitt, but the more immediate problem
is the UTF-8 error which is now preventing weewx
from starting.

On Sunday, January 17, 2021 at 4:30:38 PM UTC+1
galfert wrote:

This thread started with the discussion being
around the Ambient WS-2902 and that is totally
different despite looking like the same unit.
This is because Ambient is the only Fine Offset
clone reselle

Re: [weewx-user] ecowitt ws80

2021-01-21 Thread Rainer Lang

That's definitely not a feature.
However, did you have below 0°C/32°F temperatures ?
And do you have the inbuilt heater connected and powered ?

What works with others who had the phenomenon - and no heater activated
- was, taking it down, drying it inside/indoors and it worked again.
Mine has its heater activated since recently and went through a minus
centigrade degree period followed by temperatures up to 10°C.

and - no issues.
Once activated by the inbuilt thermostat starts the heating when the
temperature drops below 0°C and keeps on running until the temperature
goes above 10°C/50°F.
That seems to avoid not only the freezing but also the condensation
water inside.

I guess a replacement you can only ask for, if you have the heating
implemented (what quite some people don't seem to do, wanting to save on
the rather expensive power supply for it

[a decicated power supply unit]).
On 21.01.2021 03:59, Graham Eddy wrote:
the top of my ecowitt ws80 (the light sensor) has partly filled with
condensation and stopped working. the rest of the ws80 is still
working. is this ‘expected’ of an exposed ws80 (how else to get UV?)
or is it a fault (demand a replacement)?

*Graham Eddy*

--
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/18eef889-d0fa-3bf0-024f-e912de256998%40gmail.com.

Re: [weewx-user] Re: PM10 in ecowitt WH41 sensor?

2021-01-24 Thread Rainer Lang

the GW1000 doesn't receive (or at least doesn't process) any pm10 data
from the WH41, even though that one may send out such data.
If you want clarity, send an email to Lucy (supp...@ecowitt.com) and ask
your below question.

Would be interesting to know what they have to say.

The WH0290 is only a display for PM2.5 data from a WH41 or WH43.

On 23.01.2021 18:44, gjr80 wrote:
Not via the GW1000 API there isn’t. It does not show in any of the raw
sensor data that is returned from the GW1000.

Gary

On Saturday, 23 January 2021 at 23:30:14 UTC+10 graha...@gmail.com wrote:

fiddling with SDR trying to find some other sensor, i notice the
following from rtl_433:

time : 2021-01-24 00:02:08
model : Fineoffset-WH0290 ID : 4
2.5um Fine Particulate Matter: 8 ug/m3 10um Coarse
Particulate Matter: 9 ug/m3
Integrity : CRC

which clearly says the ecowitt WH41 is transmitting PM10 value as
well as PM2.5

i don't see the PM10 value appearing in WH41 ‘manual’, nor in
gary’s gw1000 driver. is there some way to extract this PM10 value
other than via SDR?

--
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/e230ac95-954b-4eab-bfc5-c600f92e4823n%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/3bac056c-ded6-024b-ead1-03a465c2288e%40gmail.com.

[weewx-user] Re: error in generated file in simple template

2021-01-24 Thread Rainer Lang


Would you please share your file /etc/weewx/skins/simple/index.html.tmpl ?
The error log seems to point at an error contained in this file. 
Something missing or too much or at the wrong place.


Without seeing it, no further conclusion possible.

Thanks and regards

On 24.01.2021 21:52, sc.lep...@gmail.com wrote:
not exactly when I activated this extension , but when 
cheetahgenerator ;)



Le dimanche 24 janvier 2021 à 21:46:47 UTC+1, sc.lep...@gmail.com a 
écrit :


Hello

I used the simple template  from
https://github.com/matthewwall/weewx-simple


My platform
Debian10 / Python 3 /last Weewx (4.3.0)

When I activate simple template  I ve this error  :

Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR
weewx.cheetahgenerator: Generate failed with exception ''
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR
weewx.cheetahgenerator:  Ignoring template
/etc/weewx/skins/simple/index.html.tmpl
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR
weewx.cheetahgenerator:  Reason: '>' not supported between
instances of 'str' and 'int'
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR
weewx.cheetahgenerator:   Traceback (most recent call last):
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR
weewx.cheetahgenerator:     File
"/usr/share/weewx/weewx/cheetahgenerator.py", line 323, in generate
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR
weewx.cheetahgenerator:       unicode_string =
compiled_template.respond()
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR
weewx.cheetahgenerator:     File

"cheetah__etc_weewx_skins_simple_index_html_tmpl_1611519616_295277_76818.py",
line 1554, in respond
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR
weewx.cheetahgenerator:   TypeError: '>' not supported between
instances of 'str' and 'int'
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] INFO
weewx.cheetahgenerator: Generated 0 files for report simple in
0.08 seconds

Can someone help me  ?

Thanks
Stéphane

--
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/37b0fa01-a932-4949-9239-ebc1be534da2n%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/ebd06ff2-a3cf-14e3-4b88-b0e757465e07%40gmail.com.

Re: [weewx-user] error in generated file in simple template

2021-01-24 Thread Rainer Lang

So it appears - just tested and saw that under Python 2.7.16 the skin 
runs without problems. Weewx is 4.3.0


On 24.01.2021 22:08, John Kline wrote:

It seems weewx-simple does not (yet) support Python 3.

On Jan 24, 2021, at 12:46 PM, sc.lep...@gmail.com 
 wrote:


Hello

I used the simple template 
from https://github.com/matthewwall/weewx-simple


My platform
Debian10 / Python 3 /last Weewx (4.3.0)

When I activate simple template  I ve this error  :

Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR 
weewx.cheetahgenerator: Generate failed with exception ''TypeError'>'
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR 
weewx.cheetahgenerator:  Ignoring template 
/etc/weewx/skins/simple/index.html.tmpl
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR 
weewx.cheetahgenerator:  Reason: '>' not supported between 
instances of 'str' and 'int'
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR 
weewx.cheetahgenerator:   Traceback (most recent call last):
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR 
weewx.cheetahgenerator:     File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 323, in generate
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR 
weewx.cheetahgenerator:       unicode_string = 
compiled_template.respond()
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR 
weewx.cheetahgenerator:     File 
"cheetah__etc_weewx_skins_simple_index_html_tmpl_1611519616_295277_76818.py", 
line 1554, in respond
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR 
weewx.cheetahgenerator:   TypeError: '>' not supported between 
instances of 'str' and 'int'
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] INFO 
weewx.cheetahgenerator: Generated 0 files for report simple in 0.08 
seconds


Can someone help me  ?

Thanks
Stéphane
--
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/c48a3315-cee6-41ae-9218-c7c6a6926b67n%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/A2A61D1E-0E00-4470-A971-9676C9C0084A%40johnkline.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/3a7cc055-6a77-2dc8-088e-bf0865b84481%40gmail.com.

Re: [weewx-user] SDR --Fineoffset WH65B Sensor Map?

2021-01-24 Thread Rainer Lang


Hi William

In my understanding the WH65 is the FineOffset/Ecowitt 7-in-1 sensor array.
What console are you using ? WH2320E ? GW1000 ? HP2551 ?

I don't think you need a special field map for the WH65 sensor array.
But somehow your sensor data have to make their way into weewx - that's 
usually via a console.


On 24.01.2021 22:09, William Lucid wrote:

Does anyone have a working sensor map for the "Fineoffset WH65B?"

I do not have a working sensor map; only one that I modified from a 
different Fineoffset model.; at 72 Years of age, I am very much a 
newbie at this kind of modifications and trying to make weewx work.


REgards,
William
--
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/bd1764d4-4f92-40fc-8247-8252078ca20cn%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/f580f92b-0c2b-da7f-ac06-2161b46b9038%40gmail.com.

Re: [weewx-user] error in generated file in simple template

2021-01-24 Thread Rainer Lang


I think, if you also install python2 (they can be both on the same machine)
and change in /etc/default/weewx
the WEEWX_PYTHON entry into

WEEWX_PYTHON=python2

and then restart weewx, it should work.

Once the skin has been updated and tested for Python3, you can change it 
back to python3 again.


On 24.01.2021 22:29, Rainer Lang wrote:


So it appears - just tested and saw that under Python 2.7.16 the skin 
runs without problems. Weewx is 4.3.0


On 24.01.2021 22:08, John Kline wrote:

It seems weewx-simple does not (yet) support Python 3.

On Jan 24, 2021, at 12:46 PM, sc.lep...@gmail.com 
 wrote:


Hello

I used the simple template  from 
https://github.com/matthewwall/weewx-simple


My platform
Debian10 / Python 3 /last Weewx (4.3.0)

When I activate simple template  I ve this error  :

Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR 
weewx.cheetahgenerator: Generate failed with exception ''TypeError'>'
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR 
weewx.cheetahgenerator:  Ignoring template 
/etc/weewx/skins/simple/index.html.tmpl
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR 
weewx.cheetahgenerator:  Reason: '>' not supported between 
instances of 'str' and 'int'
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR 
weewx.cheetahgenerator:   Traceback (most recent call last):
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR 
weewx.cheetahgenerator:     File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 323, in generate
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR 
weewx.cheetahgenerator:       unicode_string = 
compiled_template.respond()
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR 
weewx.cheetahgenerator:     File 
"cheetah__etc_weewx_skins_simple_index_html_tmpl_1611519616_295277_76818.py", 
line 1554, in respond
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] ERROR 
weewx.cheetahgenerator:   TypeError: '>' not supported between 
instances of 'str' and 'int'
Jan 24 21:20:16 debian-weewx weewx-WMR200[13641] INFO 
weewx.cheetahgenerator: Generated 0 files for report simple in 0.08 
seconds


Can someone help me  ?

Thanks
Stéphane
--
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 
<mailto:weewx-user+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c48a3315-cee6-41ae-9218-c7c6a6926b67n%40googlegroups.com 
<https://groups.google.com/d/msgid/weewx-user/c48a3315-cee6-41ae-9218-c7c6a6926b67n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
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 
<mailto:weewx-user+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/A2A61D1E-0E00-4470-A971-9676C9C0084A%40johnkline.com 
<https://groups.google.com/d/msgid/weewx-user/A2A61D1E-0E00-4470-A971-9676C9C0084A%40johnkline.com?utm_medium=email&utm_source=footer>.


--
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/5545bbf8-9100-83e3-648c-992edc32b0e1%40gmail.com.

Re: [weewx-user] Re: Multiple stations on one host

2021-02-03 Thread Rainer Lang

I had the some question some time ago  - where is the directory util 
- until I realized that this path seems to refer to a location on GitHUB.
You can find there the whole script text, mark it, copy it into the 
clipboard and then create a new file with the name weewx-multi and copy 
the clipboard content into it and save it.
Then you have the weewx-multi script. Where you place in the beginning 
it is your choice - you are supposed to overwrite the weex script in 
/etc/init.d with the weewx-multi
(1. rename the existing /etc/init.d/weewx: sudo mv /etc/init.d/weewx 
/etc/init.d/weewx-old
2. assuming you have created the weewx-multi script in /home/pi you 
would then rename and move it to /etc/init.d as weewx: sudo mv 
/home/pi/weewx-multi /etc/init.d/weewx)
If you saved the weewx-multi script somewhere else you have to take that 
path as your source for the mv command.


On 03.02.2021 22:26, michael.k...@gmx.at wrote:


Thank you for the reply, Gary. I probably did something wrong with the 
weewx-multi init script. On a raspian, where is:

util/init.d/weewx-multi
?
I didn't copy it from it's installation path, I made a new file and 
pasted it into notepad++ and uploaded it with winscp. And by writing 
this, I think this is what my problem is all about: \r\n linebreaks in 
the init script file instead of \n...

gjr80 schrieb am Dienstag, 2. Februar 2021 um 22:18:15 UTC+1:

weewx-multi works fine under WeeWX 4. I am am running a dual
instance under raspberry Pi OS and have had no problems at all.

Gary

On Wednesday, 3 February 2021 at 06:27:55 UTC+10
michael.k...@gmx.at wrote:

I have the same question: is the script still valid with weewx4?

When I try to run weewx-multi following the guide at
https://github.com/weewx/weewx/wiki/weewx-multi
 I get:

Feb 02 21:25:22 raspberrypi3B systemd[1]: Starting LSB:
weewx-multi...
-- Subject: A start job for unit weewx.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support

--
-- A start job for unit weewx.service has begun execution.
--
-- The job identifier is 1362.
Feb 02 21:25:22 raspberrypi3B systemd[3728]: weewx.service:
Failed to execute command: No such file or directory
Feb 02 21:25:22 raspberrypi3B systemd[3728]: weewx.service:
Failed at step EXEC spawning /etc/init.d/weewx: No such file
or directory
-- Subject: Process /etc/init.d/weewx could not be executed
-- Defined-By: systemd
-- Support: https://www.debian.org/support

--
-- The process /etc/init.d/weewx could not be executed and failed.
--
-- The error number returned by this process is ERRNO.
Feb 02 21:25:22 raspberrypi3B systemd[1]: weewx.service:
Control process exited, code=exited, status=203/EXEC
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support

--
-- An ExecStart= process belonging to unit weewx.service has
exited.
--
-- The process' exit code is 'exited' and its exit status is 203.
Feb 02 21:25:22 raspberrypi3B systemd[1]: weewx.service:
Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support

--
-- The unit weewx.service has entered the 'failed' state with
result 'exit-code'.
Feb 02 21:25:22 raspberrypi3B systemd[1]: Failed to start LSB:
weewx-multi.
-- Subject: A start job for unit weewx.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support

--
-- A start job for unit weewx.service has finished with a failure.
--
-- The job identifier is 1362 and the job result is failed.


gert.a...@gmail.com schrieb am Mittwoch, 13. Mai 2020 um
10:50:24 UTC+2:

Hi
Is this script still valid using Weewx 4?

Basically , I want to have 3 WeeWx instances pointing to 3
different domains on 1 computer, each domain with
different configuration. All 3 instances should read from
the same mqtt subscription port and using Interceptor. Can
all 3 Interceptor extensions listen to the same port or
must Interceptor  listen to a unique ports, say 8001, 8002
and 8003.

I'll be using Belchertown and mqtt for all 3 domains. More
or less the same question here with Mosquitto. Can I use
the  same ports(1883 for mq

Re: [weewx-user] Having trouble installing on Mac

2021-02-05 Thread Rainer Lang


Hi

when you want to get the data from the HP2551 console (that's the 
console of the HP2553 package), you can only do this by the help of the 
interceptor driver.


Get it and install it - then verify what I wrote below

You have to choose there / put in weewx.conf

[station]
station_type = Interceptor

[Interceptor]
device_type = ecowitt-client
port 8000
iface = eth0  (or wlan0 depending on your network interface)

(sometimes this latter entry  is needed to be added here - no harm 
having it )


and in the WSView app you choose the Customized option for Weather networks,
enable Ecowitt protocol
Server IP is the IP of your MAC
path leave empty
port 8000
interval 16

Otherwise follow the Interceptor driver installation instruction at GitHUB

Some of the entries the install script will already do.

Good luck

On 05.02.2021 11:16, PAK wrote:

Hi all,

I am very new and am struggling with a lot of this but hopefully this 
makes sense.


I have a Mac, with an Ecowitt HP2553. I am trying to get a handle on 
this before I purchase the GW1000 and maybe a Raspberry Pi.


The second time I tried to install Weewx it went really well until the 
last command. Here's the log: -


pak@Peters-iMac weewx % python3 ./bin/weewxd weewx.conf

Traceback (most recent call last):

  File 
"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/config.py", 
line 563, in configure


    handler = self.configure_handler(handlers[name])

  File 
"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/config.py", 
line 744, in configure_handler


    result = factory(**kwargs)

  File 
"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/handlers.py", 
line 148, in __init__


    BaseRotatingHandler.__init__(self, filename, mode, encoding, delay)

  File 
"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/handlers.py", 
line 55, in __init__


    logging.FileHandler.__init__(self, filename, mode, encoding, delay)

  File 
"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/__init__.py", 
line 1143, in __init__


    StreamHandler.__init__(self, self._open())

  File 
"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/__init__.py", 
line 1172, in _open


    return open(self.baseFilename, self.mode, encoding=self.encoding)

PermissionError: [Errno 13] Permission denied: '/var/log/weewx.log'


The above exception was the direct cause of the following exception:


Traceback (most recent call last):

  File "./bin/weewxd", line 264, in 

    main()

  File "./bin/weewxd", line 81, in main

    weeutil.logger.setup(options.log_label, {})

  File "/Users/Shared/weewx/bin/weeutil/logger.py", line 187, in setup

    logging.config.dictConfig(log_dict)

  File 
"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/config.py", 
line 808, in dictConfig


    dictConfigClass(config).configure()

  File 
"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/config.py", 
line 570, in configure


    raise ValueError('Unable to configure handler '

ValueError: Unable to configure handler 'rotate'

pak@Peters-iMac weewx %


I am wondering if the driver is the problem. I think I need to install 
an interceptor somehow? It might all be too much for me and could be 
easier to go back to Davis hehe. All I really want are daily, weekly 
and yearly reports like I'm used to with WeatherLink.


Thanks for any help,
Peter.
--
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/62969bcb-fadf-4d05-8671-b164a0ed9390n%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/fedf9e26-4e75-c71e-4121-be2c295a3d2d%40gmail.com.

Re: [weewx-user] Froggit WH2600SE

2021-02-08 Thread Rainer Lang

On 08.02.2021 09:08, Renato Brigger wrote:

Hallo Renato,

Zunächst müssen wir mal klären, was genau diese WH2600SE ist ?
Ist das die Froggit WH2600SE Pro WiFi (Fine Offset WH2650 WiFi) oder
die uralte "ObserverIP" WH2600.
Sehen beide auf den ersten Blick gleich aus, unterscheiden sich aber bei
genauem Hinsehen.

Hilfreich sind hier meine Posts:

https://www.wxforum.net/index.php?topic=40730.0
und
https://www.wxforum.net/index.php?topic=40970.0

Dann können wir nämlich sehen, welche weewx Treiber am Besten passen

entweder der Interceptor Driver oder der GW1000 API Driver.
(Der Interceptor geht immer, ist aber nicht so "schön" und unterstützt
nicht alle Sensoren (und ist hier und da schon mal etwas störanfällig)).

Falls es die Froggit WH2600SE Pro ist, dann ist es ein funktionieller
GW1000, die mächtigste Fine Offset (clone) Konsole, die z.Zt. auf dem
Markt ist.

Allerdings ist die Treiber Installation ggf. etwas trickreich.

Es kommt auch auf dein Sensor-Array an (eine WH65 oder WS80 + WH40), was
ggf. alles eingestellt werden muss.
(Der WH65 - der I- oder Y-geformte 7-in-1 Sammel-Sensor ist am
einfachsten, aber die kleine Konsole kann viel mehr, was Froggit
dummerweise nicht verrät)

Nach Rückantwort kann ich gerne weitere Details geben - es ist
eigentlich relativ einfach, auch für "Linux-Novizen", der ich bis vor 2
Monaten selbst war.

Es gibt dazu auch funktionierende Anleitungen im "Netz" - allerdings
alles auf Englisch.

Gruß

Rainer

Hallo
Ich mochte meine WH2600 in Weewx einbinden. Da ich Linux Neuling bin
komme ich leider nicht weiter.

Folgendes wurde von mir erledigt:

- Weex installiert.
- Interceptor Treiber installiert.
- FTP konfigruiert.

Geräte sind wie folgt angeschlossen:

Router (192.168.4.1)
Raspbeery (WeeWX) an Router (192.168.4.124)
Wetterstation an Router (192.168.4.105)

Leider weiss ich nicht wie der Treiber konfigruiert werden muss. Weewx
auf Treiber Interceptor gestellt.

Treiber auf "observer"

Leider bekomme ich mit der Einstellung "observer" keine Daten.

Meldung vom Treiber: queue empty

Bin für jede Hilfe dankbar.
Renato
--
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/d96aae4d-6f6d-458a-9e4c-1191abdf6784n%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/b898beb9-ce80-2dc7-654b-ed38f0cf6e5e%40gmail.com.

Re: [weewx-user] Having trouble installing on Mac

2021-02-08 Thread Rainer Lang


sudo weewxd /etc/weewx/weewx.conf

On 08.02.2021 12:48, PAK wrote:
Thanks for the advice. I have googled but still not sure I'm doing it 
correctly as getting same error. How do i run bin/weewxd as root?


On Friday, February 5, 2021 at 9:07:02 PM UTC+10 graha...@gmail.com wrote:

did you run bin/weewxd as root, to have needed permissions for
creating /var/log/weewx.log?

as an aside, you are thinking of moving weewx from mac to rpi. _do
it_. macos continues to diverge from its linux roots into strange
lands opaque to mere mortals e.g. i found daemons via launchd
becoming impossible through successive macos releases without
arcane knowledge, and abandoned macos 6 months ago. my mac mini
now runs ubuntu in a DMZ and weewx runs wonderfully on an rpi 4B
using raspian os. and i got a gw1000 to run as a service in
parallel with my vp2 on same weewx instance
(my macos laptops are still great - i just recommend against macos
for server)


On 5 Feb 2021, at 9:16 pm, PAK  wrote:

Hi all,

I am very new and am struggling with a lot of this but hopefully
this makes sense.

I have a Mac, with an Ecowitt HP2553. I am trying to get a handle
on this before I purchase the GW1000 and maybe a Raspberry Pi.

The second time I tried to install Weewx it went really well
until the last command. Here's the log: -

pak@Peters-iMac weewx % python3 ./bin/weewxd weewx.conf

Traceback (most recent call last):

  File

"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/config.py",
line 563, in configure

    handler = self.configure_handler(handlers[name])

  File

"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/config.py",
line 744, in configure_handler

    result = factory(**kwargs)

  File

"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/handlers.py",
line 148, in __init__

    BaseRotatingHandler.__init__(self, filename, mode, encoding,
delay)

  File

"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/handlers.py",
line 55, in __init__

    logging.FileHandler.__init__(self, filename, mode, encoding,
delay)

  File

"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/__init__.py",
line 1143, in __init__

    StreamHandler.__init__(self, self._open())

  File

"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/__init__.py",
line 1172, in _open

    return open(self.baseFilename, self.mode, encoding=self.encoding)

PermissionError: [Errno 13] Permission denied: '/var/log/weewx.log'


The above exception was the direct cause of the following exception:


Traceback (most recent call last):

  File "./bin/weewxd", line 264, in 

    main()

  File "./bin/weewxd", line 81, in main

    weeutil.logger.setup(options.log_label, {})

  File "/Users/Shared/weewx/bin/weeutil/logger.py", line 187, in
setup

    logging.config.dictConfig(log_dict)

  File

"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/config.py",
line 808, in dictConfig

    dictConfigClass(config).configure()

  File

"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/config.py",
line 570, in configure

    raise ValueError('Unable to configure handler '

ValueError: Unable to configure handler 'rotate'

pak@Peters-iMac weewx %


I am wondering if the driver is the problem. I think I need to
install an interceptor somehow? It might all be too much for me
and could be easier to go back to Davis hehe. All I really want
are daily, weekly and yearly reports like I'm used to with
WeatherLink.

Thanks for any help,
Peter.

-- 
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/62969bcb-fadf-4d05-8671-b164a0ed9390n%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 vie

Re: [weewx-user] Re: Sky Cover data to pwsweather.com

2021-02-18 Thread Rainer Lang

I think, the crucial information we are looking for is hidden here: "You 
can find more details here.  "

I suppose there was a link which wasn't copied over with the text.
Would you mind providing this link ?

Thanks

On 18.02.2021 11:41, bchap...@gmail.com wrote:
You can find more details here. 


--
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/e38e672f-893d-a2d6-01cb-5032fcc2fbc5%40gmail.com.

Re: [weewx-user] Re: Sky Cover data to pwsweather.com

2021-02-18 Thread Rainer Lang

That would imho be rather stupid. Why would they "sell" a link which 
leads to applying for a PWS/aeris account as detailed information to an 
existing user ?

What added value would an existing user get by applying again ???
Maybe there's still something more to it.

@Bruce: can you provide the link that was in their mail so we can at 
least see if it's something useful or rather useless.


On 18.02.2021 17:42, Karen K wrote:
I would also think, that the link is general information about 
contributor plan or something, 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/be6fff1c-4ea7-4d61-9814-766b85dbc776n%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/bcfb48f4-d974-3e1e-aab9-4e468e720171%40gmail.com.

Re: [weewx-user] Running Klimalogg and Fine Offset in one weewx session?

2021-02-22 Thread Rainer Lang

the Klimalogg Pro database consists of two databases (default names:
weewx.sdb and weewx-kl.sdb) - they will have of course be located in a
different directory from your standard weewx installation if you keep
the database names.
The installation will not run with the weewx-kl.sdb only - even though
the archived data will be in weewx-kl.sdb.
I found that out the hard way thinking for a restore only the
weewx-kl.sdb was necessary. Luckily the KLP has a 50,000 record internal
storage which could be reloaded when starting from scratch again.

You will have to run two separate instances of weewx and for each your
SQLITE_ROOT should be different - (if for you session = instance, then
not one session).

As they are/will be located in different directories fed by two separate
weewx instances (with their own weewx.conf - e.g. fineoffset.conf and
klp.conf), you don't need to rename the databases - but you can.
maybe for a better recognition you should do this. (The weewx multi
description uses the rename approach, see below)

If in your wording session = one weewx installation on one server, then
you are correct.

By the way - I'm running both myself (weewx with GW1000 and weewx with
Klimalogg Pro) - so far still on two separate RPi4s, but one of my next
activities will be to move them onto one RPi4.

There is a setup description on GitHub for running two stations and two
weewx instances on one server - recently updated.

https://github.com/weewx/weewx/wiki/weewx-multi

On 22.02.2021 17:17, Maarten Weerman wrote:

Hi all,

I have weewx 4.4.0 already running with a Fine Offset Station and it
works fine. I also have a TFA Klimalogg station with two external
sensors. I've read out that it is possible to get data with a weewx
Klimalogg driver and that it is also possible two run two stations in
one weewx session.

I have some questions: I've read that the table structure of the
klimalogg database is different from the "normal" weewx.sdb database.
Does that have any effect when running two stations in one weewx?

And regarding the existing weewx.sdb table, do i have to rename it in
e.g. "fineoffset.sdb" or can i keep the current name weewx.sdb? I
still want to use my existing weewx.sdb database table for data from
my Fine Offset Station and just add the "Klimalogg.sdb" database for
the Klimalogg Pro.

Best regards

Georg

--
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/CAKEu0RNRcUiT%2B-bNQbsPnaMtZEisjuXDcHm9T0eju1L%2BnTDXcA%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/24a63a77-b826-1784-513c-0e3d775bb720%40gmail.com.

Re: [weewx-user] Re: Changing my PWS hardware...

2021-03-02 Thread Rainer Lang

Hi Ted
weewx can't catch the sensor array data via the interceptor driver as
the WH2902C is an Ambient modified piece.
It cannot send to a customized server using the Ecowitt protocol. Maybe
it works with the WU protocol, but
haven't heard of it. If it were a non-Anbient Fine Offset clone, it
would work with the Ecowitt protocol/custom server.

But, honestly, as Bill suggested, investing some 30 USD in an Ecowitt
GW1000 console is many times worth the money.
Also, if/when later, you want to extend your sensor "fleet". Just make
sure to get the model compatible with your sensor frequency

- I assume 915 MHz.
The weewx GW1000 API driver is a proven piece which works flawlessly
(when installed properly 😉, but that's always so ...)

If you don't know it yet, there's a lot on Wxforum.net about it, e.g.
https://www.wxforum.net/index.php?topic=40730.0
https://www.wxforum.net/index.php?topic=40970.0

On 02.03.2021 18:20, Bill Arthur wrote:
I think you'll find the best way is to purchase a Ecowitt GW1000. I
listens to the 2902 array on 915MHz and puts the data on your WiFi.

I use the GW1000 extension and it works flawlessly.
https://github.com/gjr80/weewx-gw1000

On Monday, March 1, 2021 at 5:21:11 PM UTC-6 ted...@gmail.com wrote:

I have a 2902c. Where you able to get WeeWx to work?

On Saturday, November 28, 2020 at 12:51:26 PM UTC-5 vince wrote:

http://weewx.com/docs/utilities.htm#wee_config_utility

--
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/3d64c8cb-a4ec-4518-ba2f-96e44e7ad5f3n%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/8e1656ec-cf5f-8e9d-3750-28bd2249bfea%40gmail.com.

[weewx-user] Re: Klimalogg skin shows strange number format and no units under Python3 [2]

2021-03-10 Thread Rainer Lang


Hi Gary, thanks for he hint

I was digging a bit more - and found an earlier post of yours, which I 
had already used before as I wanted dewpoint and heatindex to be 
displayed beyond only sensor 1-4:


https://groups.google.com/g/weewx-user/c/svov51heFp8?pli=1

I did a complete reinstall again with Python2

and found that in the earlier reinstall (P3) my old extensions.py got 
"lost", overwritten, who knows what.
After creating the respective entries in extensions.py (which I now 
saved externally), all is back again - to Python2 so far.


The other SD card with the Python3 install will be the next step - and 
test. So far I only confirmed my old status on P2.


Meanwhile I did the restart with my other SD card (P3 install) - all 
works fine with sensor map + unit declarations in extensions.py.
Looks like that got lost (as mentioned before) during a backup/new 
install with P3 - hence the (meanwhile proven wrong) suspicion,

that is was due to P3.

*I suggest to have the gist from your above mail included in the 
Klimalogg Pro readme of Matthew. (see below)
*[I took the liberty to complete the sensor map for all 
dewpoint/heatindex values - the original post had it only for 1-4]


As this is already a 4-year old post, I'm not sure if and how Matthew is 
available to add this - but it's important information if someone wants 
heatindex and dewpoint shown and/or is using more than 4 sensors (up to 
8 possible). Maybe to be added to the weewx wiki on GitHub under 
Klimalogg Pro ...


I will add a respective post in the WXforum in the weewx section



it appears that the default setup is that heatindex and dewpoint are not 
calculated unless you specify them in the a [[sensor_map]] stanza in 
weewx.conf (preferred) or modify the driver(not advisable). Try adding 
something like the following to the [KlimaLogg] section of weewx.conf:


|
[[sensor_map]]
    temp0 =Temp0
    humidity0 =Humidity0
    heatindex0 =heatindex0
    dewpoint0 =dewpoint0
    temp1 =Temp1
    humidity1 =Humidity1
    heatindex1 =heatindex1
    dewpoint2 =dewpoint1
    temp2 =Temp2
    humidity2 =Humidity2
    heatindex2 =heatindex2
    dewpoint2 =dewpoint2
    temp3 =Temp3
    humidity3 =Humidity3
    heatindex3 =heatindex3
    dewpoint3 =dewpoint3
    temp4 =Temp4
    humidity4 =Humidity4
    heatindex4 =heatindex4
    dewpoint4 =dewpoint4
|temp5 =Temp5
    humidity5 =Humidity5
    heatindex5 =heatindex5
    dewpoint5 =dewpoint4|5
||temp6 =Temp6
    humidity6 =Humidity6
    heatindex6 =heatindex6
    dewpoint6 =dewpoint6||
|temp7 =Temp4
    humidity7 =Humidity7
    heatindex7 =heatindex7
    dewpoint7 =dewpoint7|
||temp8 =Temp8
    humidity8 =Humidity8
    heatindex8 =heatindex8
    dewpoint8 =dewpoint8||
   rxCheckPercent =SignalQuality
    batteryStatus0 =BatteryStatus0
    batteryStatus1 =BatteryStatus1
    batteryStatus2 =BatteryStatus2
    batteryStatus3 =BatteryStatus3
    batteryStatus4 =BatteryStatus4
    batteryStatus5 =BatteryStatus5
    batteryStatus6 =BatteryStatus6
    batteryStatus7 =BatteryStatus7
    batteryStatus8 =BatteryStatus8


|
# to be added to extensions.py in /usr/share/weewx/user
# setup units to support custom Klimalogg sensor map
fromweewx.units importobs_group_dict
obs_group_dict['temp0']='group_temperature'
obs_group_dict['temp1']='group_temperature'
obs_group_dict['temp2']='group_temperature'
obs_group_dict['temp3']='group_temperature'
obs_group_dict['temp4']='group_temperature'
obs_group_dict['temp5']='group_temperature'
obs_group_dict['temp6']='group_temperature'
obs_group_dict['temp7']='group_temperature'
obs_group_dict['temp8']='group_temperature'
obs_group_dict['humidity0']='group_percent'
obs_group_dict['humidity1']='group_percent'
obs_group_dict['humidity2']='group_percent'
obs_group_dict['humidity3']='group_percent'
obs_group_dict['humidity4']='group_percent'
obs_group_dict['humidity5']='group_percent'
obs_group_dict['humidity6']='group_percent'
obs_group_dict['humidity7']='group_percent'
obs_group_dict['humidity8']='group_percent'
obs_group_dict['dewpoint0']='group_temperature'
obs_group_dict['dewpoint1']='group_temperature'
obs_group_dict['dewpoint2']='group_temperature'
obs_group_dict['dewpoint3']='group_temperature'
obs_group_dict['dewpoint4']='group_temperature'
obs_group_dict['dewpoint5']='group_temperature'
obs_group_dict['dewpoint6']='group_temperature'
obs_group_dict['dewpoint7']='group_temperature'
obs_group_dict['dewpoint8']='group_temperature'
obs_group_dict['heatindex0']='group_temperature'
obs_group_dict['heatindex1']='group_temperature'
obs_group_dict['heatindex2']='group_temperature'
obs_group_dict['heatindex3']='group_temperature'
obs_group_dict['heatindex4']='group_temperature'
obs_group_dict['heatindex5']='group_temperature'
obs_group_dict['heatindex6']='group_temperature'
obs_group_dict['heatindex7']='group_temperature'
obs_group_dict['heatindex8']='group_temperature'
obs_group_dict['rxCheckPercent']='group_percent'
obs_group_dict['batteryStatus0']='group_count'
obs

[weewx-user] WH2650 clone problems

2021-03-21 Thread Rainer Lang

You can go through the instructions/suggestions posted at
https://www.wxforum.net/index.php?topic=41575.0
this works in 99.5% of all cases so far. 😁
From what I read, your main issue might be
that you probably use the wrong app (probably wrongly stated in the
reseller manual) - you have to use the WSView app - WS Tools won't work
for that purpose

On 21.03.2021 13:37, Auchtermuchty Weather wrote:
PS I've tried a reset just now, no idea at what point in the flashing
I should let the button go but again I have both sensors connected but
it's not connecting to the WiFi

On Sunday, 21 March 2021 at 12:25:13 UTC Auchtermuchty Weather wrote:

GW1000 - the tiny little thing with blue LEDs. Certainly not a
console.
On Sunday, 21 March 2021 at 12:18:10 UTC steep...@gmail.com wrote:

Do you have a gateway device GW1000 or a console?

On Sun, 21 Mar 2021 at 12:03, Auchtermuchty Weather
wrote:

So my WH2650 clone eventually arrived and is installed in
the garden. However can't get the base station to
connect to my router. I've plugged it in, it's connected
to indoor & outdoor sensors but the WiFi light continues
to flash rapidly. I've turned off the 5GHz Wifi, I've got
the WS Tool app. And the App won't let me put the SSID in
either. If just has ''.

However I see what is meant by better sensors etc.

Should have done this bit before I turned off the old one.

--
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/73707865-d69c-4a18-8709-02142dae07dbn%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/8a2e3a7e-399d-41e4-8dbc-9cbcedea100dn%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/ed4ae52b-5657-1424-374c-175484f159e2%40gmail.com.

[weewx-user] WH2650 clone problems

2021-03-21 Thread Rainer Lang


Congratulations !
It is how it is  - and, unless you do a factory reset, you won't 
have to do this again.


For "general" FineOffset clone issues etc., WXforum is afaik the main 
(in the sense most substantial) forum - for weewx there are some helpful 
posts, too - but here is the main weewx user forum.


With the GW1000/WH2650

in weewx.conf you will have to add the line
-- start weewx.conf excerpt --
[StdCalibrate]

    [[Corrections]]
    # For each type, an arbitrary calibration expression can be given.
    # It should be in the units defined in the StdConvert section.
    # Example:
    foo = foo + 0.2

*radiation = luminosity/126.7 if luminosity is not None else None*
 end weewx.conf excerpt

otherwise you won't get data from a solar sensor displayed
Good luck - and have fun !

On 21.03.2021 14:48, Auchtermuchty Weather wrote:
Thanks, I knew I'd seen something about this but forgot about the 
other forum.


That worked, but what a horrible method!  A better way (in my view) 
would be it picks up the network itself and has an inbuilt HTTP server 
for any further configuration.  I guess the prevalence of mobile 
devices is affecting things, adversely IMHO - a mobile device is 
perfectly capable of picking up data from an IP address...


I've given it a static IP, cycled the power and it's back on the 
network with the right static IP.  The new IP also shows in WS View 
and on looking though the screens in WS View it looks like I have some 
new data to play with, plus humidity looks about right so I imagine 
the dew point will be.


Now to implement connecting to it from WeeWx...

On Sunday, 21 March 2021 at 13:12:59 UTC lang@googlemail.com wrote:

You can go through the instructions/suggestions posted at
https://www.wxforum.net/index.php?topic=41575.0

this works in 99.5% of all cases so far. 😁
From what I read, your main issue might be
that you probably use the wrong app (probably wrongly stated in
the reseller manual) - you have to use the WSView app - WS Tools
won't work for that purpose
On 21.03.2021 13:37, Auchtermuchty Weather wrote:

PS I've tried a reset just now, no idea at what point in the
flashing I should let the button go but again I have both sensors
connected but it's not connecting to the WiFi

On Sunday, 21 March 2021 at 12:25:13 UTC Auchtermuchty Weather wrote:


GW1000 - the tiny little thing with blue LEDs. Certainly not
a console.
On Sunday, 21 March 2021 at 12:18:10 UTC steep...@gmail.com
wrote:

Do you have a gateway device GW1000 or a console?

On Sun, 21 Mar 2021 at 12:03, Auchtermuchty Weather
 wrote:

So my WH2650 clone eventually arrived and is
installed in the garden.  However  can't get the base
station to connect to my router. I've plugged it in,
it's connected to indoor & outdoor sensors but the
WiFi light continues to flash rapidly.  I've turned
off the 5GHz Wifi, I've got the WS Tool app.  And the
App won't let me put the SSID in either. If just has
''.

However I see what is meant by better sensors etc.

Should have done this bit before I turned off the old
one.

-- 
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/73707865-d69c-4a18-8709-02142dae07dbn%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/8a2e3a7e-399d-41e4-8dbc-9cbcedea100dn%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

[weewx-user] Parsing Ecowitt WH31, WN34L and WH57 [2]

2021-12-22 Thread Rainer Lang


Matthew's Interceptor driver doesn't handle that (yet ?).
As you seem to be living in Germany resp. speaking German, have a look at
https://www.pc-wetterstation.de/forum/viewtopic.php?f=26&t=10333&sid=bf68867d7a6c245e55636c156d07330b
where a modified Interceptor driver is described (and downloadable) 
which covers all recent sensors from the Ecowitt ecosystem. And it's 
working ! 😎

best regards
Rainer

On 22.12.2021 23:39, jszit...@gmail.com wrote:
I am running Weewx 4.5.1 using Matthew's Interceptor driver in 
ecowitt-client mode to parse data from an Ecowitt GW1000. I recently 
supplemented my Ecowitt setup with a few additional sensors and cannot 
seem to get them to parse properly.


A few rounds of the syslog:
Dec 22 16:20:54 Gugelhupf weewx[20166] DEBUG weewx.manager: Daily 
summary version is 1.0
Dec 22 16:20:55 Gugelhupf weewx[20166] DEBUG weewx.manager: Daily 
summary version is 1.0
Dec 22 16:20:56 Gugelhupf weewx[20166] DEBUG weewx.manager: Daily 
summary version is 4.0
Dec 22 16:20:58 Gugelhupf weewx[20166] INFO weewx.imagegenerator: 
Generated 16 images for report StandardReport in 7.17 seconds
Dec 22 16:20:58 Gugelhupf weewx[20166] INFO weewx.reportengine: Copied 
9 files to /var/www/html/weewx
Dec 22 16:20:58 Gugelhupf weewx[20166] DEBUG weewx.reportengine: 
Running report 'cmon'
Dec 22 16:20:58 Gugelhupf weewx[20166] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/cmon/skin.conf for report 'cmon'
Dec 22 16:20:58 Gugelhupf weewx[20166] DEBUG weewx.cheetahgenerator: 
Using search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.JSONHelpers']
Dec 22 16:20:58 Gugelhupf weewx[20166] DEBUG weewx.manager: Daily 
summary version is 4.0
Dec 22 16:20:58 Gugelhupf weewx[20166] INFO weewx.cheetahgenerator: 
Generated 1 files for report cmon in 0.20 seconds
Dec 22 16:20:58 Gugelhupf weewx[20166] DEBUG weewx.manager: Daily 
summary version is 4.0
Dec 22 16:20:58 Gugelhupf weewx[20166] DEBUG PIL.PngImagePlugin: 
STREAM 'IHDR' 16 13
Dec 22 16:20:58 Gugelhupf weewx[20166] DEBUG PIL.PngImagePlugin: 
STREAM 'IDAT' 41 1216

Dec 22 16:21:04 Gugelhupf weewx[20166] DEBUG user.interceptor: empty queue
Dec 22 16:21:10 Gugelhupf weewx[20166] DEBUG user.interceptor: POST: 
PASSKEY=&stationtype=GW1000B_V1.6.8&dateutc=2021-12-22+22:21:10&tempinf=71.6&humidityin=53&baromrelin=29.406&baromabsin=29.406&tempf=74.1&humidity=50&winddir=149&windspeedmph=1.57&windgustmph=4.47&maxdailygust=5.82&solarradiation=21.16&uv=0&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.110&monthlyrainin=1.091&yearlyrainin=50.925&totalrainin=50.925&temp2f=71.60&humidity2=55&lightning_time=1639936192&lightning_num=0&lightning=14&tf_ch1=58.8&wh65batt=0&batt2=0&wh57batt=4&tf_batt1=1.40&freq=915M&model=GW1000_Pro
Dec 22 16:21:11 Gugelhupf weewx[20166] DEBUG user.interceptor: raw 
data: 
PASSKEY=3190878978C9C58F9A8EE5E46324353B&stationtype=GW1000B_V1.6.8&dateutc=2021-12-22+22:21:10&tempinf=71.6&humidityin=53&baromrelin=29.406&baromabsin=29.406&tempf=74.1&humidity=50&winddir=149&windspeedmph=1.57&windgustmph=4.47&maxdailygust=5.82&solarradiation=21.16&uv=0&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.110&monthlyrainin=1.091&yearlyrainin=50.925&totalrainin=50.925&temp2f=71.60&humidity2=55&lightning_time=1639936192&lightning_num=0&lightning=14&tf_ch1=58.8&wh65batt=0&batt2=0&wh57batt=4&tf_batt1=1.40&freq=915M&model=GW1000_Pro
Dec 22 16:21:11 Gugelhupf weewx[20166] DEBUG user.interceptor: ignored 
parameter eventrainin=0.000
Dec 22 16:21:11 Gugelhupf weewx[20166] DEBUG user.interceptor: ignored 
parameter baromrelin=29.406
Dec 22 16:21:11 Gugelhupf weewx[20166] DEBUG user.interceptor: ignored 
parameter maxdailygust=5.82
Dec 22 16:21:11 Gugelhupf weewx[20166] INFO user.interceptor: 
unrecognized parameter lightning_time=1639936192
Dec 22 16:21:11 Gugelhupf weewx[20166] DEBUG user.interceptor: ignored 
parameter monthlyrainin=1.091
Dec 22 16:21:11 Gugelhupf weewx[20166] DEBUG user.interceptor: ignored 
parameter PASSKEY=
Dec 22 16:21:11 Gugelhupf weewx[20166] INFO user.interceptor: 
unrecognized parameter tf_ch1=58.8
Dec 22 16:21:11 Gugelhupf weewx[20166] INFO user.interceptor: 
unrecognized parameter lightning_num=0
Dec 22 16:21:11 Gugelhupf weewx[20166] DEBUG user.interceptor: ignored 
parameter hourlyrainin=0.000
Dec 22 16:21:11 Gugelhupf weewx[20166] DEBUG user.interceptor: ignored 
parameter freq=915M
Dec 22 16:21:11 Gugelhupf weewx[20166] INFO user.interceptor: 
unrecognized parameter tf_batt1=1.40
Dec 22 16:21:11 Gugelhupf weewx[20166] DEBUG user.interceptor: ignored 
parameter model=GW1000_Pro
Dec 22 16:21:11 Gugelhupf weewx[20166] DEBUG user.interceptor: ignored 
parameter yearlyrainin=50.925
Dec 22 16:21:11 Gugelhupf weewx[20166]

[weewx-user] Parsing Ecowitt WH31, WN34L and WH57 [3]

2021-12-27 Thread Rainer Lang

Werner's interceptor driver is mainly meant for FOSHK clone consoles 
like the HP350x or HP2551 which do not have an API which can be actively 
queried by weewx. It interpretes the http posts of these consoles using 
the custom server functionality


As for the GW1x00, WH2650, WN19x0 and the GW2000 consoles who possess an 
(the same) API, Gary's GW1000 API driver is the better choice.


You need the respective [GW1000] entries in weewx.conf and the entry 
station_type = GW1000 in the [Station] section. see below


As the GW1000 can only receive a dynamic IP address, it is recommended 
to make an IP address binding in your router, i.e. associate the IP 
address with the MAC address (--> WS View Device List) of the GW1000.
This makes sure that after a reboot of the GW1000 (e.g. firmware 
updated, power loss) or of the router,

the IP address doesn't change and weewx won't find it anymore.

[GW1000]
    driver = user.gw1000
    ip_address = your-GW1000-ip-address
    poll_interval = 10

    [[field_map_extensions]]
    # WeeWX field name = GW1000 field name
    rainEvent = rainevent
    #WH45 5-in-1 sensor data
    pm10 = pm10
    co2 = co2
    pm2_55 = pm255
    pm2_55_24hav = pm255_24hav
    pm10_24hav = pm10_24_hav
    co2_24hav = co2_24hav
    wh45_batt = wh45_batt
    wh45_sig = wh45_sig

in [StdCalibrate] [[Corrections]] you need an extra entry for solar 
radiation due to the way the GW1000 reads radiation observations from 
the sensors


[StdCalibrate]

    [[Corrections]]
    # For each type, an arbitrary calibration expression can be given.
    # It should be in the units defined in the StdConvert section.
    # Example:
    foo = foo + 0.2
    radiation = luminosity/126.7 if luminosity is not None else None

Your [Accumulator] section should look like below
# Options for extension 'GW1000'
[Accumulator]
    [[outTemp]]
    extractor = max
    [[radiation]]
    extractor = max
    [[wh65_batt]]
    extractor = last
    [[wh51_ch8_batt]]
    extractor = last
    [[wh31_ch1_batt]]
    extractor = last
    [[pm2_52_24hav]]
    extractor = last
    [[pm2_51_24hav]]
    extractor = last
    [[totalRain]]
    extractor = last
    # *
    [[rainEvent]]
    extractor = last
    # *
    [[wh51_ch1_batt]]
    extractor = last
    [[wh31_ch3_batt]]
    extractor = last
    [[wh55_ch4_batt]]
    extractor = last
    [[wh51_ch3_batt]]
    extractor = last
    [[yearRain]]
    extractor = last
    [[pm2_53_24hav]]
    extractor = last
    [[wh41_ch3_batt]]
    extractor = last
    [[wh51_ch16_batt]]
    extractor = last
    [[pm2_54_24hav]]
    extractor = last
    [[wh51_ch4_batt]]
    extractor = last
    [[wh57_batt]]
    extractor = last
    [[wh41_ch1_batt]]
    extractor = last
    [[lightning_strike_count]]
    extractor = sum
    [[wh40_batt]]
    extractor = last
    [[wh25_batt]]
    extractor = last
    [[daymaxwind]]
    extractor = last
    [[wh31_ch7_batt]]
    extractor = last
    [[dayRain]]
    extractor = last
    [[wh31_ch5_batt]]
    extractor = last
    [[wh31_ch8_batt]]
    extractor = last
    [[wh51_ch15_batt]]
    extractor = last
    [[wh31_ch6_batt]]
    extractor = last
    [[wh31_ch2_batt]]
    extractor = last
    [[wh51_ch14_batt]]
    extractor = last
    [[wh31_ch4_batt]]
    extractor = last
    [[monthRain]]
    extractor = last
    [[ws80_batt]]
    extractor = last
    [[stormRain]]
    extractor = last
    [[wh55_ch3_batt]]
    extractor = last
    [[weekRain]]
    extractor = last
    [[wh51_ch6_batt]]
    extractor = last
    [[hourRain]]
    extractor = last
    [[wh51_ch10_batt]]
    extractor = last
    [[wh51_ch13_batt]]
    extractor = last
    [[wh41_ch4_batt]]
    extractor = last
    [[wh68_batt]]
    extractor = last
    [[lightning_distance]]
    extractor = last
    [[wh51_ch11_batt]]
    extractor = last
    [[wh51_ch7_batt]]
    extractor = last
    [[wh51_ch2_batt]]
    extractor = last
    [[wh26_batt]]
    extractor = last
    [[wh55_ch1_batt]]
    extractor = last
    [[wh55_ch2_batt]]
    extractor = last
    [[wh51_ch12_batt]]
    extractor = last
    [[wh51_ch5_batt]]
    extractor = last
    [[wh51_ch9_batt]]
    extractor = last
    [[lightning_last_det_time]]
    extractor = last
    [[wh41_ch2_batt]]
    extractor = last
    [[24havpm255]]
    extractor = last
    [[wh45_batt]]
    extractor = last
    [[wh45_sig]]
    extractor = last
    [[lightningcount]]
    extractor = last
    [[pm2_51_24h_avg]]
    extractor = last
    [[pm2_52_24h_avg]]
    extractor = last
    [[pm2_53_24h_avg]]
    extractor = last
    [[pm2_54_24h_avg]]
    extractor = last
    [[pm2_55_24h_avg]]
    extr

Re: [weewx-user] Advice on replacement WxStn

2021-12-28 Thread Rainer Lang

Hi Nick
If you want to go with the FOSHK/Ecowitt ecosystem, have a look at their
offers

(www.ecowitt.com) and what can be combined/extended with what
(https://www.wxforum.net/index.php?topic=40730.0) and what a different
brands of the same stations

- you need to register in order to see pictures.
In the UK stations are sold via https://www.amazon.co.uk and
https://weatherspares.co.uk/, also via

https://www.nevadaradio.co.uk/ (Watson 8686)

On 28.12.2021 11:08, nickg...@gmail.com wrote:
horrible but ...>

Afternoon to all the collective wisdom here,

The current WxStn (a WH3080 - by froggit, but seems ot be a fine offset)
is playing silly beggars!

The console is not displaying temp/humidity not wind, but is showing luc
& UV and Weewx reckons it is either not there or disconnected

ERROR weewx.drivers.fousb: get_observations failed: [Errno 19] No such
device (it may have been disconnected)

and/or

INFO weewx.drivers.fousb: station status {'unknown': 0,
'lost_connection': 64, 'rain_overflow': 0} (64)

The usual dance of power cycling the console results in no change.

A couple of week ago it did it and I went on the roof and changed the
batteries, pressed reset and it sill did not work, so back up - take it
all down, dry (it was not really wet) clean with alcohol and put back -
still nothing.

I then gave up, powered down the console & stopped Weewx, about 24hrs
later restarted everything and it worked ...

I've just repeated the dance and nothing ...

Thus the questions

a) any ideas?

b) replace but with what? Thought about a GW1000 based like

Thoughts, ideas, suggestions ...

Many thanks

Happy seasonal things etc. & stay safe

Nick
M0HGU

--
Mrs. Nugent was the Johnson's next door neighbour, and known to be
unreasonable on subjects like Madonna played at full volume at 3 a.m.

(Johnny and the Dead) Tue 10346 Sep 10:00:01 GMT 1993
10:00:01 up 15 days, 23:28, 6 users, load average: 0.79, 0.71, 0.69

--
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/34532f77-e080-46b8-9b64-594d0ac5fa6dn%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/3c25c56f-22aa-7b14-3141-1fcf3c07ba13%40gmail.com.

Re: [weewx-user] Interceptor driver "cannot assign requested address" - noob here - thoughts?

2022-01-12 Thread Rainer Lang

1. choosing port 80 for the custom server to send/post to is not a smart 
choice as this port is already used by the local (RPi) web server 
(nginx, apache2, ...). You must choose a unique port e.g. 8000, 8080, ...


2. in weewx.conf you must not assign the port along with the ip address.
the entry should be:
ip_address = 192.168.0.29
only, no colon or port added - it's, however, not needed

below a working [Interceptor] section

# -- start weewx.conf excerpt 
[Interceptor]
    # This section is for the network traffic interceptor driver.

    # The driver to use:
    driver = user.interceptor

    # Specify the hardware device to capture.  Options include:
    #   acurite-bridge - acurite internet bridge, smarthub, or access
    #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
    #   lw30x - oregon scientific LW301/LW302
    #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
    #   ecowitt-client - any hardware that uses the ecowitt protocol
    #   wu-client - any hardware that uses the weather underground protocol
    device_type = observer
*port = 8000*
    iface = eth0
 # -- end excerpt weewx.conf 
if you use the WLAN interface of the RPi ("WiFi"), then use: iface = 
wlan0 instead of iface = eth0

(the last character is a zero !!)
You don't need to enter your IP address here, it's obviously the one of 
the RPi


the port (*8000*) should also be the same in the WS View / awnet app 
(customized server)

You can of course choose another number, however not 80 !
there (WS View, awnet) the IP address of your RPi has to be entered (NO 
http:// in front of the address !! - only the address)
the path has to show at least "/" - an empty path will keep the console 
from posting


good luck
On 12.01.2022 04:55, Kruse Ludington wrote:
I have an Ambient WS-2902C with a console publishing to four places 
specified in the awnet app: 1. AmbientWeather.net; 2. Wunderground; 3. 
Weathercloud; and 4; Customized - to  
on port 80 (both on the same network internal network) but the PI is 
having trouble loading the interceptor driver with weird error 
messages (probably something simple as I am a noob). As per the 
Interceptor installation instructions for this model state I should 
use device-type=observer and listen (as I am not intercepting), these 
are the error messages I am running into from the log -


sudo /etc/init.d/weewx start

then here's the log info:

Jan 11 21:53:24 kruse-pi weewx[4814] INFO __main__: Initializing weewx 
version 4.5.1
Jan 11 21:53:24 kruse-pi weewx[4814] INFO __main__: Using Python 3.9.2 
(default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
Jan 11 21:53:24 kruse-pi weewx[4814] INFO __main__: Platform 
Linux-5.10.63-v7l+-armv7l-with-glibc2.31
Jan 11 21:53:24 kruse-pi weewx[4814] INFO __main__: Locale is 
'en_US.UTF-8'
Jan 11 21:53:24 kruse-pi weewx[4814] INFO __main__: PID file is 
/var/run/weewx.pid
Jan 11 21:53:24 kruse-pi weewx[4818] INFO __main__: Using 
configuration file /etc/weewx/weewx.conf

Jan 11 21:53:24 kruse-pi weewx[4818] INFO __main__: Debug is 1
Jan 11 21:53:24 kruse-pi weewx[4818] DEBUG __main__: Initializing engine
Jan 11 21:53:24 kruse-pi weewx[4818] INFO weewx.engine: Loading 
station type Interceptor (user.interceptor)
Jan 11 21:53:24 kruse-pi weewx[4802]: Starting weewx weather system: 
weewx.
Jan 11 21:53:24 kruse-pi weewx[4818] INFO user.interceptor: driver 
version is 0.53
Jan 11 21:53:24 kruse-pi weewx[4818] INFO user.interceptor: device 
type: observer

Jan 11 21:53:24 kruse-pi weewx[4818] INFO user.interceptor: mode is listen
Jan 11 21:53:24 kruse-pi weewx[4818] INFO user.interceptor: listen on 
192.168.0.29:80
Jan 11 21:53:24 kruse-pi weewx[4818] ERROR weewx.engine: Import of 
driver failed: [Errno 99] Cannot assign requested address ('OSError'>)
Jan 11 21:53:24 kruse-pi weewx[4818] CRITICAL weewx.engine:    
 Traceback (most recent call last):
Jan 11 21:53:24 kruse-pi weewx[4818] CRITICAL weewx.engine:      
 File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
Jan 11 21:53:24 kruse-pi weewx[4818] CRITICAL weewx.engine:        
 self.console = loader_function(config_dict, self)
Jan 11 21:53:24 kruse-pi weewx[4818] CRITICAL weewx.engine:      
 File "/usr/share/weewx/user/interceptor.py", line 315, in loader
Jan 11 21:53:24 kruse-pi weewx[4818] CRITICAL weewx.engine:        
 return InterceptorDriver(**config_dict[DRIVER_NAME])
Jan 11 21:53:24 kruse-pi weewx[4818] CRITICAL weewx.engine:      
 File "/usr/share/weewx/user/interceptor.py", line 2522, in __init__
Jan 11 21:53:24 kruse-pi weewx[4818] CRITICAL weewx.engine:        
 self._device = self.DEVICE_TYPES.get(self._device_type)(**stn_dict)
Jan 11 21:53:24 kruse-pi weewx[4818] CRITICAL weewx.engine:      
 File "/usr/share/weewx/user/interceptor.py", line 1284, in __init__
Jan 11 21:53:24 kruse-pi weewx[4818] CRITICAL weewx.engine:        
 super(Observer, self).__init__(
Jan 11 21:5

[weewx-user] Re: weewx-interceptor and Python3 on Raspbian 10 buster? [2]

2022-01-16 Thread Rainer Lang

I'm also using the interceptor driver on Python 3.9.2 on Raspbian 11 -
no issue

BUT
the interceptor driver is most of the time used in listen mode and not
in sniffing mode.
In listen mode you instruct your console to post directly to your server
(single IP address and port) where the interceptor driver is listening.

In sniffing mode the console sends a broadcast and the interceptor
driver tries to "fish", sniff these messages from the network traffic
and interpret them.

That's what Vince is looking for.
However, if you have a sniffing use case running on Debian 10, you are
most welcome to share your configuration.

On 16.01.2022 07:17, Francesco wrote:
I'm using the interceptor driver and weewx on Debian 10 with python 3
without any issues. If you give me some time I can check my
configuration and installed packages and let you know

Il giorno sabato 15 gennaio 2022 alle 23:11:38 UTC+1 vince ha scritto:

I asked the same question in another thread last week. I got
nowhere trying to get the pypcap stuff going on debian11 or
debian10 with python3, but since it was a nice-to-have only, I
basically gave up trying.

--
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/e5e746bd-18c2-49b4-be8b-1c4ff55e769bn%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/4453e27d-2c3a-60b2-3b73-8ce52590a3d0%40gmail.com.

Re: [weewx-user] WS2900

2022-01-16 Thread Rainer Lang



it all depends on what you mean by a WS2900.
Have a look at the following thread and then tell us the Ecowitt name of 
the station you are talking about (provided that station is a Fine 
Offset clone):

https://www.wxforum.net/index.php?PHPSESSID=d3v98lhd7t2jolfnpft99hbqrs&topic=40730.0
(you need to register at the forum (free !) in order to see the 
important pictures)

On 16.01.2022 14:18, Jens-Jørgen Kjærgaard wrote:

I have for many years used the WH1080 weather stations.
However, it has become increasingly difficult to get spare parts, so 
now I am considering switching to WS2900. However, I can find only the 
WH2900 in the hardware list.

Any opinions on the WS2900?
--
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/838f546a-c6ef-4687-9844-eca389b7164an%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/9d892a31-2070-0591-f84c-e232d8622f52%40gmail.com.

Re: [weewx-user] Re: Ftp upload

2022-03-10 Thread Rainer Lang

I doubt that "it" or "everything" works.
Clicking on your link only provides a general page of your web hoster.
Something is still "fishy" - locally, on your web host or with both.

On 10.03.2022 16:19, Kalli Gøtze wrote:

Hi all,
Today i install weewx new and it works. www.kalligotze.org
Thanks for your help :)

best regards Karl

tke...@gmail.com schrieb am Donnerstag, 10. März 2022 um 14:49:42 UTC+1:

In a private email, Kalli noted that the value for "path" is

[[FTP]]
...
path = /home/weewx/public_html
...

Two things to note:

* "path" is the /destination/ directory. This is usually
something like "/var/www/html" or "/weewx".
* "HTML_ROOT" is the /source/ directory, usually set to
"/home/weewx/public_html" if you used the setup.py install
method (which you did).

You did not say what destination directory you expect, but it is
probably not "/home/weewx/public_html". Think about where you want
the files to go, and set "path" to that. Whatever it is set to,
you must have write permission for the user name you supplied.
Another complication is that for some FTP servers the path must be
an absolute path, for others it is relative to the home directory
of the supplied user. Experiment.

On the other hand, maybe you did want "/home/weewx/public_html".
If so, let us know and we'll go to the next step.

-tk

On Wed, Mar 9, 2022 at 12:23 PM Tom Keffer wrote:

We have seen this error before and it's very misleading.
Despite the message, it can be caused by problems either
locally or remotely.

1. Make sure the FTP username has write permissions on the
server for the path you specified.
2. Make sure the password is correct. Does it include special
characters? If so, be sure to quote the password.
3. Does your server require FTPS?
4. Try different variations for the path option for [FTP].

If you are still stuck, post your [FTP] section, but be sure
to obfuscate your password first.

-tk

On Wed, Mar 9, 2022 at 11:28 AM vince wrote:

Possibly, but why would weewx try to upload a file that is
not there on the weewx system ?
Or is that what that #FTPlast file does ?

https://groups.google.com/g/weewx-user/c/XwQqsslGKfA
suggests removing that file which should cause weewx to
upload everything it finds.

On Wednesday, March 9, 2022 at 10:11:51 AM UTC-8
kk44...@gmail.com wrote:

kalli...@gmail.com schrieb am Mittwoch, 9. März 2022
um 18:27:38 UTC+1:

Reason: '550 /home/weewx/public_html/monthhum.png:
No such file or directory'

I would have listened to that error message and guess,
the local file is missing.

--
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/70edd677-2765-4bb2-8088-60e0cf5c09a0n%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/5c916353-6bf2-421c-a380-6cf9443831e1n%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/b7b70499-5f42-fe40-443d-6e2e448d1e47%40gmail.com.

[weewx-user] Re: want to have /home/weewx/public_html in a ramdisk

2022-03-13 Thread Rainer Lang

There are only two ways to be really safe:
1. boot your RPi3+ from a (n external) HDD/SSD - instructions how to
make this work can be found in the internet
2. use an industrial standard SLC microSD card - it will hold for at
least 10 years.

(and make regular (!) backups of your important weewx files like
weewx.sdb and weewx.conf - and your skin files if you have made
adaptations and maybe your crontab and fstab files if you made
modifications there)

I'm using a 16 GB SanDisk/WDSDSDQED-016G-XI micro SD card. Cost me about
27 EUR/30 USD those days (1 1/2 years ago).
Nowadays prices have gone up and there are still big delays in delivery
due to the "chip crisis". (26 weeks right now)

You need to buy them from special stores like mouser.com or arrow.com -
you won't get them in normal, consumer stores.
e.g.
https://www.mouser.com/ProductDetail/SanDisk/SDSDQED-016G-XI?qs=gZXFycFWdANR2bR%2Fc%252B7h0w%3D%3D

Don't let yourself be fooled by product names like High Endurance, Max
Endurance - they are only good for video stream recordings.
Weewx (and other applications with high database activity) will wear
them down fast.

On 12.03.2022 22:46, Eric K wrote:

Hi Peter.

Correct, extending the life of the SD card is my goal.

I am currently rebuilding my weewx Raspberry Pi system because of a
suspected SD card failure.
I had 2 local Linux users tell me that the symptoms are consistent
with an SD card corruption.

The card is only 9 months old, and it's not bottom-of-the barrel quality!
I reached out for help 2 weeks ago and got zero responses.
see:
https://forums.raspberrypi.com/viewtopic.php?p=1979221&hilit=kernel+panic#p1979221

On Saturday, March 12, 2022 at 3:35:06 PM UTC-6 peterq...@gmail.com wrote:

If you're wanting a ramdisk because SD cards are unreliable, I
wouldn't bother. There is plenty of history of people running
Weewx on Raspberry Pis for many years without a problem with
corrupted SD cards.

On Sat, Mar 12, 2022 at 12:55 PM vince wrote:

I would try 'mkdir /home/weewx/public_html/forecast' so the
parent directory exists when weewx tries to write it.

I'd also add that doing it your way means your NOAA files will
be recreated every time it boots, which could take ages if you
have many years of info like many of us do.

One way would be to put something in your rc.local which runs
after things mount ala:

if [ -d /home/weewx/public_html ]
then
# prepopulate things here
mkdir /home/weewx/public_html/forecast
else
logger "error - rc.local could not mkdir for weewx"
fi

You might run into timing issues if you do too much this way
since rc.local tends to run toward the end of the startup
sequence, but a quick mkdir should work.

On Saturday, March 12, 2022 at 12:40:49 PM UTC-8 Eric K wrote:

Currently running weewx 4.5.1 in a Raspberry Pi 3B+ with
the Bullseye version of Raspberry Pi OS.
For a Raspberry Pi (using a microSD card as the OS system
drive) I want to create a ramdisk for
the /home/weewx/public_html directory.
I followed examples from various webpages on the ramdisk
topic.
What I've tried thus far doesn't fully work.
How are others implementing this?

I started by renaming my /home/weewx/public_html directory
to /home/weewx/public_html_backup, so there would be no
conflict when the ramdisk was created at bootup.
Then, I put this line in the /etc/fstab file and rebooted.
tmpfs /home/weewx/public_html tmpfs
defaults,noatime,size=100M 0 0
I tested it with sudo mount -a and the new partition was
visible by using the df command.

After a reboot, a /home/weewx/public_html directory was
created as a tmpfs volume.
To test the functionality, I manually ran wee_reports to
force the webpage to be created.
When wee_reports ran, the process crashed with errors,
because some of the files don't exist from previous runs
of wee_reports.

pi@rpi3b:/home/weewx $ sudo bin/wee_reports
Using configuration file /home/weewx/weewx.conf
Generating for all time
Traceback (most recent call last):
File "/home/weewx/bin/user/belchertown.py", line 1390,
in get_extension_list
with open(forecast_file, "wb+") as file:
FileNotFoundError: [Errno 2] No such file or directory:
'/home/weewx/public_html/json/forecast.json'

During handling of the above exception, another exception
occurred:

Traceback (most recent call last):
File "/home/weewx/bin/weewx/reportengin

Re: [weewx-user] Re: Sainlogic Weather Station

2022-04-12 Thread Rainer Lang


The Sainlogic SC008 is definitely NOT a Fine Offset /ecowitt clone model !
Still the interceptor might work - will depend on the SC008 console 
functionality.

On 12.04.2022 09:44, ian...@kinnon.org wrote:
The image on Amazon looks like one of the generic Ecowitt clones, so 
the interceptor client will probably work


On Tuesday, 12 April 2022 at 03:51:03 UTC+1 john.t...@talipsky.com wrote:

Is anyone using WEEWX or developing for Sainlogic Weather station,
particularly Sainlogic Model SC088 ??     Any help/comments
appreciated

--
You received this message because you are subscribed to the Google 
Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/20d0bc1a-a7d1-4bd8-9ebb-88ce57f2d4b4n%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/754dc70e-695a-69b0-88ab-77f9099e3cd9%40gmail.com.

Re: [weewx-user] Re: Changed weather station and cant get observer to work

2022-04-12 Thread Rainer Lang


Please answer the before asked questions ...
What's your weather station (console) model ?
what's your Raspi model ?
an adaptation of your weewx.conf may be needed.
At first glance I suspect a port issue.

then we can take it from there 

it is always helpful when you copy the FULL syslog from start up 
covering at least one better two archive cycle(s), with debug option = 1 
set in weewx conf !!!



On 12.04.2022 11:22, Dan Wheaton wrote:

Runing interceptor on its own, i get this.
Doesnt seem to matter what device option i use


PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/user/interceptor.py --device=observer --mode=listen 
--port=80 --debug
raw data: 
ID=ISYDNEY467&PASSWORD=&indoortempf=73.6&indoorhumidity=64&tempf=63.1&humidity=82&dewptf=57.5&windchillf=63.1&absbaromin=29.39&baromin=29.93&windspeedmph=0.0&windgustmph=0.7&winddir=171&windspdmph_avg2m=0.2&winddir_avg2m=83&windgustmph_10m=0.4&windgustdir_10m=123&rainin=0.0&dailyrainin=0.63&weeklyrainin=0.63&monthlyrainin=0.63&solarradiation=0.0&UV=0&dateutc=2022-4-12%208:10:51&action=updateraw&realtime=1&rtfreq=5&

No handlers could be found for logger "__main__"
raw packet: {}
mapped packet: {}



On Tuesday, April 12, 2022 at 6:44:08 PM UTC+10 Dan Wheaton wrote:

Interceptor config:

[Interceptor]
    # This section is for the network traffic interceptor driver.

    # The driver to use:
    driver = user.interceptor

    # Specify the hardware device to capture.  Options include:
    #   acurite-bridge - acurite internet bridge
    #   observer - fine offset WH2600/HP1000/HP1003, aka 'observer'
    #   lw30x - oregon scientific LW301/LW302
    #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
    device_type = observer

On Tuesday, April 12, 2022 at 6:37:49 PM UTC+10 Dan Wheaton wrote:

More log info:
syslog:
Apr 12 18:32:39 raspberrypi weewx[1773] DEBUG weewx.engine:
Finished loading service weewx.engine.StdCalibrate
Apr 12 18:32:39 raspberrypi weewx[1773] DEBUG weewx.engine:
Loading service weewx.engine.StdQC
Apr 12 18:32:39 raspberrypi weewx[1773] DEBUG weewx.engine:
Finished loading service weewx.engine.StdQC
Apr 12 18:32:39 raspberrypi weewx[1773] DEBUG weewx.engine:
Loading service weewx.wxservices.StdWXCalculate
Apr 12 18:32:39 raspberrypi weewx[1773] INFO weewx.wxservices:
StdWXCalculate will use data binding wx_binding
Apr 12 18:32:39 raspberrypi weewx[1773] DEBUG weewx.manager:
Daily summary version is 2.0
Apr 12 18:32:39 raspberrypi weewx[1773] INFO weewx.manager:
Daily summaries at V2.0. Patching to V4.0
Apr 12 18:32:39 raspberrypi weewx[1773] INFO weewx.manager:
recalculate_weights: Using database 'weewx.sdb'
Apr 12 18:32:39 raspberrypi weewx[1773] DEBUG weewx.manager:
recalculate_weights: Tranche size 100
Apr 12 18:33:44 raspberrypi weewx[1773] DEBUG
user.interceptor: GET:

ID=&PASSWORD=&indoortempf=73.6&indoorhumidity=64&tempf=63.1&humidity=82&dewptf=57.5&windchillf=63.1&absbaromin=29.39&baromin=29.93&windspeedmph=0.0&windgustmph=0.7&winddir=171&windspdmph_avg2m=0.2&winddir_avg2m=83&windgustmph_10m=0.4&windgustdir_10m=123&rainin=0.0&dailyrainin=0.63&weeklyrainin=0.63&monthlyrainin=0.63&solarradiation=0.0&UV=0&dateutc=2022-4-12%208:10:51&action=updateraw&realtime=1&rtfreq=5&

messages:
Apr 12 18:32:39 raspberrypi weewx[1773] INFO weewx.engine:
Loading station type Interceptor (user.interceptor)
Apr 12 18:32:39 raspberrypi weewx[1773] INFO user.interceptor:
driver version is 0.53
Apr 12 18:32:39 raspberrypi weewx[1773] INFO user.interceptor:
device type: observer
Apr 12 18:32:39 raspberrypi weewx[1773] INFO user.interceptor:
mode is listen
Apr 12 18:32:39 raspberrypi weewx[1773] INFO user.interceptor:
listen on :80
Apr 12 18:32:39 raspberrypi weewx[1773] INFO user.interceptor:
sensor map: {'extraTemp2': 'temperature_2', 'pm2_5': 'pm2_5',
'soilTemp1': 'soil_temperature_1', 'soilTemp2':
'soil_temperature_2', 'soilTemp3': 'soil_temperature_3',
'soilTemp4': 'soil_temperature_4', 'txBatteryStatus':
'battery', 'outTemp': 'temperature_out', 'windSpeed':
'wind_speed', 'windGust': 'wind_gust', 'outHumidity':
'humidity_out', 'windDir': 'wind_dir', 'radiation':
'solar_radiation', 'inTemp': 'temperature_in', 'windGustDir':
'wind_gust_dir', 'barometer': 'barometer', 'windchill':
'windchill', 'dewpoint': 'dewpoint', 'rain': 'rain',
'extraHumid6': 'humidity_6', 'pressure': 'pressure',
'extraHumid4': 'humidity_4', 'extraHumid5': 'humidity_5',
'extraHumid2': 'humidity_2', 'extraHumid3': 'humidity_3',
'extraTemp8': 'temperature_8', 'extraHumid1': 'humidity_1',
'extraTemp6': 'tempe

Re: [weewx-user] Re: Changed weather station and cant get observer to work

2022-04-12 Thread Rainer Lang


What's your weather station (console) model ?
what's your Raspi model ?
an adaptation of your weewx.conf may be needed.
At first glance I suspect a port issue.
On 12.04.2022 10:44, Dan Wheaton wrote:

Interceptor config:

[Interceptor]
    # This section is for the network traffic interceptor driver.

    # The driver to use:
    driver = user.interceptor

    # Specify the hardware device to capture.  Options include:
    #   acurite-bridge - acurite internet bridge
    #   observer - fine offset WH2600/HP1000/HP1003, aka 'observer'
    #   lw30x - oregon scientific LW301/LW302
    #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
    device_type = observer

On Tuesday, April 12, 2022 at 6:37:49 PM UTC+10 Dan Wheaton wrote:

More log info:
syslog:
Apr 12 18:32:39 raspberrypi weewx[1773] DEBUG weewx.engine:
Finished loading service weewx.engine.StdCalibrate
Apr 12 18:32:39 raspberrypi weewx[1773] DEBUG weewx.engine:
Loading service weewx.engine.StdQC
Apr 12 18:32:39 raspberrypi weewx[1773] DEBUG weewx.engine:
Finished loading service weewx.engine.StdQC
Apr 12 18:32:39 raspberrypi weewx[1773] DEBUG weewx.engine:
Loading service weewx.wxservices.StdWXCalculate
Apr 12 18:32:39 raspberrypi weewx[1773] INFO weewx.wxservices:
StdWXCalculate will use data binding wx_binding
Apr 12 18:32:39 raspberrypi weewx[1773] DEBUG weewx.manager: Daily
summary version is 2.0
Apr 12 18:32:39 raspberrypi weewx[1773] INFO weewx.manager: Daily
summaries at V2.0. Patching to V4.0
Apr 12 18:32:39 raspberrypi weewx[1773] INFO weewx.manager:
recalculate_weights: Using database 'weewx.sdb'
Apr 12 18:32:39 raspberrypi weewx[1773] DEBUG weewx.manager:
recalculate_weights: Tranche size 100
Apr 12 18:33:44 raspberrypi weewx[1773] DEBUG user.interceptor:
GET:

ID=&PASSWORD=&indoortempf=73.6&indoorhumidity=64&tempf=63.1&humidity=82&dewptf=57.5&windchillf=63.1&absbaromin=29.39&baromin=29.93&windspeedmph=0.0&windgustmph=0.7&winddir=171&windspdmph_avg2m=0.2&winddir_avg2m=83&windgustmph_10m=0.4&windgustdir_10m=123&rainin=0.0&dailyrainin=0.63&weeklyrainin=0.63&monthlyrainin=0.63&solarradiation=0.0&UV=0&dateutc=2022-4-12%208:10:51&action=updateraw&realtime=1&rtfreq=5&

messages:
Apr 12 18:32:39 raspberrypi weewx[1773] INFO weewx.engine: Loading
station type Interceptor (user.interceptor)
Apr 12 18:32:39 raspberrypi weewx[1773] INFO user.interceptor:
driver version is 0.53
Apr 12 18:32:39 raspberrypi weewx[1773] INFO user.interceptor:
device type: observer
Apr 12 18:32:39 raspberrypi weewx[1773] INFO user.interceptor:
mode is listen
Apr 12 18:32:39 raspberrypi weewx[1773] INFO user.interceptor:
listen on :80
Apr 12 18:32:39 raspberrypi weewx[1773] INFO user.interceptor:
sensor map: {'extraTemp2': 'temperature_2', 'pm2_5': 'pm2_5',
'soilTemp1': 'soil_temperature_1', 'soilTemp2':
'soil_temperature_2', 'soilTemp3': 'soil_temperature_3',
'soilTemp4': 'soil_temperature_4', 'txBatteryStatus': 'battery',
'outTemp': 'temperature_out', 'windSpeed': 'wind_speed',
'windGust': 'wind_gust', 'outHumidity': 'humidity_out', 'windDir':
'wind_dir', 'radiation': 'solar_radiation', 'inTemp':
'temperature_in', 'windGustDir': 'wind_gust_dir', 'barometer':
'barometer', 'windchill': 'windchill', 'dewpoint': 'dewpoint',
'rain': 'rain', 'extraHumid6': 'humidity_6', 'pressure':
'pressure', 'extraHumid4': 'humidity_4', 'extraHumid5':
'humidity_5', 'extraHumid2': 'humidity_2', 'extraHumid3':
'humidity_3', 'extraTemp8': 'temperature_8', 'extraHumid1':
'humidity_1', 'extraTemp6': 'temperature_6', 'extraTemp7':
'temperature_7', 'extraTemp4': 'temperature_4', 'extraTemp5':
'temperature_5', 'rainRate': 'rain_rate', 'extraTemp3':
'temperature_3', 'extraHumid8': 'humidity_8', 'extraTemp1':
'temperature_1', 'leafWet1': 'leafwetness_1', 'leafWet2':
'leafwetness_2', 'extraHumid7': 'humidity_7', 'UV': 'uv',
'soilMoist3': 'soil_moisture_3', 'soilMoist2': 'soil_moisture_2',
'soilMoist1': 'soil_moisture_1', 'inHumidity': 'humidity_in',
'soilMoist4': 'soil_moisture_4'}
Apr 12 18:32:39 raspberrypi weewx[1773] INFO weewx.engine:
StdConvert target unit is 0x1
Apr 12 18:32:39 raspberrypi weewx[1773] INFO weewx.wxservices:
StdWXCalculate will use data binding wx_binding
Apr 12 18:32:39 raspberrypi weewx[1773] INFO weewx.manager: Daily
summaries at V2.0. Patching to V4.0
Apr 12 18:32:39 raspberrypi weewx[1773] INFO weewx.manager:
recalculate_weights: Using database 'weewx.sdb'



On Tuesday, April 12, 2022 at 4:13:24 PM UTC+10 Dan Wheaton wrote:

Hi all.
My WS died, so i have replaced it with a similar model, but
for the life of me just cannot get the observer to pick up data.

I am  using DNS spoofing to rtupdate.wunderground.com
. Weewx sees

Re: [weewx-user] Re: EcoWitt GW2000 - anyone working on a driver?

2022-04-18 Thread Rainer Lang

That's only a possibility if the GW2000 is the only console you have. If 
your FOSHKplugin is already fed by another console ...

Want to install a second instance of FOSHKplugin ? Not trivial.
Also, the custom server doesn't provide you the same loop data which you 
can get from the GW1000 driver.
But it's an alternative, if the GW2000 is the only console you have/use 
with FOSHKplugin.


Not sure why you were struggling, I use the GW1000 driver for a few 
weewx instances and the interceptor for one - no issues which couldn't 
be solved in a short time (and were usually due to a bad system setup or 
not knowing your system (server) well enough).


On 18.04.2022 21:54, Zsolt Máté wrote:
Install FOSHKplugin and all your headaches are gone. I was struggling 
with the drivers, interceptors, observers, whatnot, but ever since 
I've installed it everything is back to normal.


On Monday, April 18, 2022 at 4:41:05 AM UTC+12 xzei...@googlemail.com 
wrote:


My modified driver from Gary (now named gw2000.py) supports the
GW2000 and GW1100 with Firmware V2.1.3 (piezo_rain)
https://www.pc-wetterstation.de/weewx/gw2000.zip
The piezo_gain_values are at the moment not supported.
The hour piezo rain and hour rain aren't right, the pdf-docu isn't
here correct, seems this values are gain factors
I use the hail database value for  piezo rain (WS90)
    [[field_map_extensions]]
        rain_piezo = rain_piezo
        erain_piezo = erain_piezo
        rrain_piezo = rrain_piezo
        hrain_piezo = hrain_piezo
        drain_piezo = drain_piezo
        wrain_piezo = wrain_piezo
        mrain_piezo = mrain_piezo
        yrain_piezo = yrain_piezo

        hail = rain_piezo
        hailrate = rrain_piezo
stephen...@gmail.com schrieb am Sonntag, 17. April 2022 um
06:46:23 UTC+2:

Hi Gary,

I have abused my credit card and ordered a WH40 rainfall
sensor (along with the AQ & lightning sensior), so that
readings from both it & the piezo sensor can be compared. Will
let you know when it turns up and is installed.

On Sun, 17 Apr 2022 at 13:52, Stephen Hocking
 wrote:

Hi Gary,

I've just set up weewx with the gw1000 driver, and it
appears to have picked up the gw2000 just fine - I'm
getting observations coming in. I'm reassured, as a recent
git pull of the rtl_433 code doesn't decode anything from
the sensors at all, and while going down that rabbit hole
of banging on the code would be entertaining, I'm pretty
sure that more talented minds than mine are already on it.

I currently have the WittBoy (with the aforementioned
piezo rain detector) only at the moment, although I'm
planning on ordering the indoor & outdoor air quality
sensors, as well as the lightning one. This thing seems to
be head & shoulders over the AcuRite Atlas I was using
with the SDR driver (plus scraping pressure off the
webpage on the Atlas hub).

Please let me know if I can test any code for you.

On Sun, 17 Apr 2022 at 11:05, gjr80 
wrote:

The current GW1000 driver will speak to a GW2000 and
should return all obs except for WS90 rain and WS90
signal/battery states. I am working on the v0.5.0
driver but the behaviour of the GW2000 API with
various combinations of the 'traditional' and 'piezo'
rain gauges (Ecowitt's terms) is not very clearly
defined. I will likely need some assistance from
GW2000 users with various rain gauge combinations to
tie this down. WS90 signal and battery states are
already working in the v0.5.0 driver.

Not sure how long the piece of string is.

Gary
On Sunday, 17 April 2022 at 02:08:31 UTC+10 vince wrote:

A little searching here seems to indicate the
gw1000 driver should possibly work for you.  Give
it a try

On Friday, April 15, 2022 at 11:10:06 PM UTC-7
stephen...@gmail.com wrote:

From the web page the device serves up, it
appears you can tell it to upload data  in
ecowitt or wunderground format to your own
server/port.


image.png
-- 


   "I and the public know
   what all schoolchildren learn
   Those to whom evil is done
   Do evil in return"  W.H. Auden, "September 1, 
1939"

-- 
You received this me

[weewx-user] Request for assistance - GW2000/WS90

2022-04-21 Thread Rainer Lang

Hi Gary,
I have a WH40 and WS90 connected to my GW2000.
The 0x57 command returns
FF-FF-57-00-54-0E-00-00-10-00-00-00-00-11-00-00-00-00-12-00-00-02-F2-13-00-00-0B-93-0D-00-00-0F-00-64-80-00-00-83-00-00-00-00-84-00-00-00-00-85-00-00-01-DE-86-00-00-0B-F2-81-00-00-87-00-64-00-64-00-64-00-64-00-64-00-64-00-64-00-64-00-64-00-64-88-00-00-00-F7

which contains the correct data (monthly and yearly totals only as no
rainfall recently - coming Sunday some forecast) for both rain gauges,

traditional 0E, 10 thru 13, 0D,0F and piezo 80-88

symptomatically the 82 marker is missing and the 81 marker is/seems to
be sorted out of sequence between 86 and 87.

Looks the others show the same pattern.
I have already started a request with Ecowitt to get this behaviour of
the GW2000 explained.

Waiting for response.

MY GW2000 is also connected via eth0 and wlan0, weewx via wlan0 (for
some time also via eth0), now CumulusMX via eth0.
The network interfaces show some messy behaviour when more than one
application connects (e.g. weewx and WSView+ or WebUI) via the same
interface (eth0, wlan0).
This often results in the whole network access (in/out) freezing. Only
reboot helps.

Issue also reported to Ecowitt and still with their technicians.

cheers
Rainer

On 21.04.2022 11:09, gjr80 wrote:
Thanks Jon and Stephen, exactly what I was looking for. One question I
did forget to add in my original post was how is your GW2000
connected; via Ethernet (cable), WiFi or both? Also Jon, would you by
chance have a second Ecowitt (non-WS90) rain gauge on your system?

Gary
--
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/206f1d1d-e76f-489a-9fd4-734472471a75n%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/8c3e1af3-523f-cbd5-7c65-c9af665a5371%40gmail.com.

[weewx-user] EcoWitt GW2000 - anyone working on a driver? [2]

2022-04-25 Thread Rainer Lang


Hallo Werner
Die API Doku enthält z.Zt. noch Fehler. In Kürze sollte eine korrigierte 
Version erscheinen.
nachstehend die gültige und korrekte Fassung des CMD_READ_RAIN Befehls 
und der "WiFi" (besser API) Rückmeldung


CMD_READ_RAIN 0x57 und die dazugehörige WiFi response (es gibt darin 
keinen hourly rain - dies[er] wurde in Rain Gain umbenannt für den 
WH40/WS69 Anteil [0F] bei Anmeldung von traditional und piezo am GW2000 
[oder auch mitterweile GW1000 und GW1100 und WH2650 mit Firmware 
1.6.9/1.7.0) - piezo hourly gibt es ebenfalls (noch) nicht



#define ITEM_RAINRATE



0x0E//Rain Rate (mm/h)



2

#define ITEM_RAINDAY



0x10//Rain Day (mm)



2

#define ITEM_RAINWEEK



0x11//Rain Week (mm)



2

#define ITEM_RAINMONTH



0x12//Rain Month (mm)



4

#define ITEM_RAINYEAR



0x13//Rain Year (mm)



4

#define ITEM_RAINEVENT  0x0D//Rain Event (mm)   2
#define ITEM_RAIN_Gain  0x0F//Rain Gain 2

#define ITEM_Piezo_Rain_Rate 0x80//                                      2
#define ITEM_Piezo_Event_Rain 0x81//                        2
#define ITEM_Piezo_Hourly_Rain 0x82//                          2     
reserved, not used

#define ITEM_Piezo_Daily_Rain 0x83//                          4
#define ITEM_Piezo_Weekly_Rain 0x84//                        4
#define ITEM_Piezo_Monthly_Rain 0x85//                        4
#define ITEM_Piezo_yearly_Rain 0x86//                        4
#define ITEM_Piezo_Gain10 0x87//                          2*10
#define ITEM_RST_RainTime            0x88//                             
         3


Gruß
Rainer
On 17.04.2022 18:41, 'Werner Krenn' via weewx-user wrote:
My modified driver from Gary (now named gw2000.py) supports the GW2000 
and GW1100 with Firmware V2.1.3 (piezo_rain)

https://www.pc-wetterstation.de/weewx/gw2000.zip
The piezo_gain_values are at the moment not supported.
The hour piezo rain and hour rain aren't right, the pdf-docu isn't 
here correct, seems this values are gain factors

I use the hail database value for  piezo rain (WS90)
    [[field_map_extensions]]
        rain_piezo = rain_piezo
        erain_piezo = erain_piezo
        rrain_piezo = rrain_piezo
        hrain_piezo = hrain_piezo
        drain_piezo = drain_piezo
        wrain_piezo = wrain_piezo
        mrain_piezo = mrain_piezo
        yrain_piezo = yrain_piezo

        hail = rain_piezo
        hailrate = rrain_piezo
stephen...@gmail.com schrieb am Sonntag, 17. April 2022 um 06:46:23 UTC+2:

Hi Gary,

I have abused my credit card and ordered a WH40 rainfall sensor
(along with the AQ & lightning sensior), so that readings from
both it & the piezo sensor can be compared. Will let you know when
it turns up and is installed.

On Sun, 17 Apr 2022 at 13:52, Stephen Hocking
 wrote:

Hi Gary,

I've just set up weewx with the gw1000 driver, and it appears
to have picked up the gw2000 just fine - I'm getting
observations coming in. I'm reassured, as a recent git pull of
the rtl_433 code doesn't decode anything from the sensors at
all, and while going down that rabbit hole of banging on the
code would be entertaining, I'm pretty sure that more
talented minds than mine are already on it.

I currently have the WittBoy (with the aforementioned piezo
rain detector) only at the moment, although I'm planning on
ordering the indoor & outdoor air quality sensors, as well as
the lightning one. This thing seems to be head & shoulders
over the AcuRite Atlas I was using with the SDR driver (plus
scraping pressure off the webpage on the Atlas hub).

Please let me know if I can test any code for you.

On Sun, 17 Apr 2022 at 11:05, gjr80  wrote:

The current GW1000 driver will speak to a GW2000 and
should return all obs except for WS90 rain and WS90
signal/battery states. I am working on the v0.5.0 driver
but the behaviour of the GW2000 API with various
combinations of the 'traditional' and 'piezo' rain gauges
(Ecowitt's terms) is not very clearly defined. I will
likely need some assistance from GW2000 users with various
rain gauge combinations to tie this down. WS90 signal and
battery states are already working in the v0.5.0 driver.

Not sure how long the piece of string is.

Gary
On Sunday, 17 April 2022 at 02:08:31 UTC+10 vince wrote:

A little searching here seems to indicate the gw1000
driver should possibly work for you.  Give it a try

On Friday, April 15, 2022 at 11:10:06 PM UTC-7
stephen...@gmail.com wrote:

From the web page the device serves up, it appears
you can tell it to upload data  in ecowitt or
wundergrou

[weewx-user] Request for assistance - GW2000/WS90

2022-04-29 Thread Rainer Lang


You can only buy it from Ecowitt (ecowitt.com) so far.
If you want the console/gateway only, you will have to send a mail to 
supp...@ecowitt.com.
However, there are delays right now as they have run out of stock with 
their kickstarter campaign

for the GW2001 station (GW2000 + WS90 outdoor array).
That's why you don't find prices for the GW2000 on the ecowitt.net web 
site yet.


The LAN port is great and the power connection is less bulky than with 
the GW1x00 gateways.
Design is always a matter of taste, but you can fix it to wall. It comes 
with a wall mount.


On 29.04.2022 07:23, Graham Eddy wrote:

anyone in australia know how i can order a GW2000 from here at present?
i want the ethernet port and sane power supply



--
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/8d7bf07c-1cb7-a8ed-3cb7-74dcfa409fba%40gmail.com.

Re: [weewx-user] Ecowitt Gateway (formerly GW1000) driver v0.5.0b4 release [5]

2022-05-02 Thread Rainer Lang

ne:
Copied 0 files to /var/weewx/reports
May  2 00:56:11 raspberrypi weewx[7904] INFO
weewx.cheetahgenerator: Generated 6 files for report
SmartphoneReport in 0.06 seconds
May  2 00:56:11 raspberrypi weewx[7904] INFO weewx.imagegenerator:
Generated 6 images for report SmartphoneReport in 0.24 seconds
May  2 00:56:11 raspberrypi weewx[7904] INFO weewx.reportengine:
Copied 0 files to /var/weewx/reports/smart
May  2 00:56:12 raspberrypi weewx[7904] INFO
weewx.cheetahgenerator: Generated 1 files for report simple in
0.15 seconds
May  2 00:56:12 raspberrypi weewx[7904] INFO weewx.imagegenerator:
Generated 16 images for report simple in 0.54 seconds
May  2 00:56:35 raspberrypi weewx[7904] INFO weewx.reportengine:
ftpgenerator: Ftp'd 79 files in 23.34 seconds
May  2 00:56:38 raspberrypi weewx[3016] DEBUG __main__: Sending
packet 'FF FF 26 03 29' to '192.168.1.46:45000
<http://192.168.1.46:45000>'
May  2 00:56:38 raspberrypi weewx[3016] DEBUG __main__: Received
response 'FF FF 26 09 94 3C C6 44 B5 EF AD'
May  2 00:56:38 raspberrypi weewx[3016] DEBUG __main__: Sending
packet 'FF FF 50 03 53' to '192.168.1.46:45000
<http://192.168.1.46:45000>'
May  2 00:56:38 raspberrypi weewx[3016] DEBUG __main__: Received
response 'FF FF 50 12 0E 47 57 32 30 30 30 41 5F 56 32 2E 31 2E 34 B9'
May  2 00:56:38 raspberrypi weewx[3016] DEBUG __main__: Sending
packet 'FF FF 30 03 33' to '192.168.1.46:45000
<http://192.168.1.46:45000>'
May  2 00:56:38 raspberrypi weewx[3016] DEBUG __main__: Received
response 'FF FF 30 0B 01 01 62 6F 2C 45 27 01 A7'
May  2 00:56:38 raspberrypi weewx[3016] DEBUG __main__: Sending
packet 'FF FF 57 03 5A' to '192.168.1.46:45000
<http://192.168.1.46:45000>'
May  2 00:56:38 raspberrypi weewx[3016] DEBUG __main__: Received
response 'FF FF 57 00 54 0E 00 00 10 00 00 00 00 11 00 00 00 00 12
00 00 00 00 13 00 00 0C 11 0D 00 00 0F 00 64 80 00 00 83 00 00 00
00 84 00 00 00 00 85 00 00 00 00 86 00 00 0C 72 81 00 00 87 00 64
00 64 00 64 00 64 00 64 00 64 00 64 00 64 00 64 00 64 88 00 00 00 24'
May  2 00:56:38 raspberrypi weewx[3016] DEBUG __main__: Unknown
field address '00' detected. Remaining data '00 12 00 00 00 00 13
00 00 0C 11 0D 00 00 0F 00 64 80 00 00 83 00 00 00 00 84 00 00 00
00 85 00 00 00 00 86 00 00 0C 72 81 00 00 87 00 64 00 64 00 64 00
64 00 64 00 64 00 64 00 64 00 64 00 64 88 00 00 00' ignored.

Am 02.05.2022 um 00:47 schrieb gjr80:

Yes, very convenient providing the same data in different
commands in different formats, though it is clear if you read the
documentation (well as clear as the API documentation is).

I have published b3
<https://github.com/gjr80/weewx-gw1000/releases> that should fix
the issue, though with out a traditional rainfall gauge I cannot
test all aspects.

Gary

On Monday, 2 May 2022 at 07:28:42 UTC+10 lang@googlemail.com
wrote:

it seems as if 0x10 in the 0x57 (CMD_READ_RAIN) call return
has a 4 byte length whereas in the CMD_GW1000_LIVEDATA call
it has a 2 byte length
you may need a separate data structure for the 0x0E-0x13
(plus 0x80-0x88) IDs contained in the 0x57 call and can't use
the one you use for LIVEDATA
Brian from WD ran into the same/a similar issue ...

Am 01.05.2022 um 23:11 schrieb Rainer Lang:


Is it possible that your rain_day traditional in the 0x57
call is too short ? should be 4 bytes after the 0x10 ID.

Am 01.05.2022 um 22:55 schrieb Rainer Lang:


Here you go

May  1 22:21:07 raspberrypi weewx[29246] DEBUG __main__:
Sending packet 'FF FF 26 03 29' to '192.168.1.46:45000
<http://192.168.1.46:45000>'
May  1 22:21:07 raspberrypi weewx[29246] DEBUG __main__:
Received response 'FF FF 26 09 94 3C C6 44 B5 EF AD'
May  1 22:21:07 raspberrypi weewx[29246] DEBUG __main__:
Sending packet 'FF FF 50 03 53' to '192.168.1.46:45000
<http://192.168.1.46:45000>'
May  1 22:21:07 raspberrypi weewx[29246] DEBUG __main__:
Received response 'FF FF 50 12 0E 47 57 32 30 30 30 41 5F
56 32 2E 31 2E 34 B9'
May  1 22:21:07 raspberrypi weewx[29246] DEBUG __main__:
Sending packet 'FF FF 30 03 33' to '192.168.1.46:45000
<http://192.168.1.46:45000>'
May  1 22:21:07 raspberrypi weewx[29246] DEBUG __main__:
Received response 'FF FF 30 0B 01 01 62 6F 07 D2 27 01 0F'
May  1 22:21:07 raspberrypi weewx[29246] DEBUG __main__:
Sending packet 'FF

Re: [weewx-user] issue when trying to depict rain data from different weewx databases in Seasons skin (current and High/Low)

2022-07-06 Thread Rainer Lang

Great, Tom, thank you - the proposed (1st) solution looks quite smart 
and is TESTED NOW - and works as expected.
Looks as if I have to enlarge my Python and Cheetah generator knowledge 
significantly.


The 2nd will be helpful to implement that into my neowx-material skin 
which was already parameterized before the Seasons skin was 
"rejuvenated" into its new also parameterized coding.
When I have some more time, I'll also be looking into migrating my 
Seasons skin ...


And I take it, that if I want to include more data-bindings, I just 
enlarge the $archive_data array by more elements ... (1st solution)


thanks again
cheers
Rainer

On 06.07.2022 01:42, Tom Keffer wrote:
It looks like you are using an older version of Seasons (before it was 
parameterized). The variable $archive[1] is the result of evaluating 
$day, which makes it an instance of weewx.tags.TimespanBinder, built 
using default values in the initializer. At this point, it's too late 
to ask it to be built using a custom value for data_binding.


What to do? You could introduce a new set of timespans, this time 
including your custom binding. It would look like (NOT TESTED):


#set $archive_data = [('day', $day, 
$day(data_binding='rpi24-binding')), ('week', $week, 
$week(data_binding='rpi24-binding')), ('month', $month, 
$month(data_binding='rpi24-binding')), ('year', $year, 
$year(data_binding='rpi24-binding')), ('rainyear', $rainyear, 
$rainyear(data_binding='rpi24-binding'))]


then use that when necessary:


      
        $archive[2].rainRate.max.format(add_label=False)
     

Another approach would be to update to the parameterized version of 
Seasons, which does its evaluation of TimespanBinder later, allowing 
it to be modified in a more straightforward way:


 
       
       $getVar('%s.%s(data_binding='rpi24-binding')' % ($timespan, 
$x)).max.format(add_label=False)

     

-tk


On Tue, Jul 5, 2022 at 2:57 PM 'Rainer Lang' via weewx-user 
 wrote:


After some more digging I have advanced:

my 2nd issue, that the monthly and weekly data is not shown seems
to be solved:
while in the imagegenerator the week/month means 7 days back and
30 days back from the current date,
$week and $month seem to mean the calender week and calender month
- a few tests with fake rain data in the database confirmed that

remains the issue how to show the values from the remote database
in the High/Low portion of the High/Low table

at http://www.weewx.com/docs/customizing.htm#Using_multiple_bindings
the example goes:

  Inside Temperature,
Vantage $current.inTemp 
 Inside Temperature, WMR100 $latest/*($data_binding='wmr100_binding')*/.inTemp
 

this translated into my hilo.inc code

    $obs.label.rain
    #for $archive in $archive_data
    
$archive[1].rain.sum.format(add_label=False)
    #end for
    $unit.label.rain
 
 
    $obs.label.rainRate
    #for $archive in $archive_data
    
  
$archive[1].rainRate.max.format(add_label=False)
    
    #end for
    $unit.label.rainRate


should in my understanding then be:

/*

*/$archive[1]/*($data_binding='rpi24-binding')*/.rain.sum.format(add_label=False)
resp.


  

$archive[1]/*($data_binding='rpi24-binding')*/.rainRate.max.format(add_label=False)


where "rpi24-binding" is my database binding of the remote database

however, this produces a Cheetah Syntax error

Jul  5 23:26:15 raspberrypi weewx[31166] ERROR
weewx.cheetahgenerator: Evaluation of template
/etc/weewx/skins/Seasons/index.html.tmpl failed with exception
''
Jul  5 23:26:15 raspberrypi weewx[31166] ERROR
weewx.cheetahgenerator:  Ignoring template
/etc/weewx/skins/Seasons/index.html.tmpl
Jul  5 23:26:15 raspberrypi weewx[31166] ERROR
weewx.cheetahgenerator:  Reason: keyword can't be an
expression (, line 1)
Jul  5 23:26:15 raspberrypi weewx[31166] ERROR
weewx.cheetahgenerator:   Traceback (most recent call last):
Jul  5 23:26:15 raspberrypi weewx[31166] ERROR
weewx.cheetahgenerator:     File
"/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in generate
Jul  5 23:26:15 raspberrypi weewx[31166] ERROR
weewx.cheetahgenerator:   unicode_string =
compiled_template.respond()
Jul  5 23:26:15 raspberrypi weewx[31166] ERROR
weewx.cheetahgenerator:     File

"cheetah__etc_weewx_skins_Seasons_index_html_tmpl_1657056374_3328836_74907.py",
line 287, in respond
Jul  5 23:26:15 raspberrypi weewx[31166] ERROR
weewx.cheetahgenerator:     File
"/usr/lib/python3/dist-packag

Re: [weewx-user] send data to ecowitt.net

2022-07-10 Thread Rainer Lang

As far as I know weewx doesn't provide uploads to ecowitt.net - the WiKi
shows uploads to many weather services but not to ecowitt.net - at least
I couldn't find it.
In order for data to be sent to ecowitt.net, your console (its MAC
address) needs to be registered with ecowitt.net. Once this is the case,
the console can post itself to ecowitt.net. So the question is: why
would you want weewx to to post to ecowitt.net instead of having the
console already doing this ?

If I knew more about your use case/scenario, I could give you some hints
of how to post indirectly to ecowitt.net.
If you want to do some sensor remapping of the console data before the
posting, there are existing tools which can do this - no need having
weewx doing this.

Please explain further.

On 10.07.2022 19:48, enu...@gmail.com wrote:

I don't see in stdrestful any way to send data to ecowitt. Is there a way?
--
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/f2c80904-e9ba-4f3b-b7ba-fdde7cbbed56n%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/de9ee261-2b6b-5b84-6e66-6c4ca51f33f9%40gmail.com.

Re: [weewx-user] is PCE-FWS 20N a re-badged fine offset device?

2022-07-12 Thread Rainer Lang

This looks like a clone of the old Fine Offset WH1080 weather station
which is no longer sold by Ecowitt due to old technology.
Console connectivity is USB only, no WiFi, no connection to the weather
networks. No solar sensor either. (a solar panel for running the outdoor
array, yes).
The outdoor array is likely to be not compatible to the modern WiFi
consoles and gateways like GW1000/GW1100/GW2000 due to using a different
modulation for the sensor signal transmission. This is also true vice
versa - the WH1080 console cannot receive any of the modern
FineOffset/Ecowitt sensors.

On 12.07.2022 18:57, Peter Wilkinson wrote:

Certainly looks like it might be but would appreciate confirmation.

Full skinny here:

https://www.pce-instruments.com/english/index.htm?id=google-uk&_artnr=5933243&_p=159.6&_pmode=0&_pbexkey=37&_date=20220711011313&_pbhash=3d8b84805bd95306b3a50a774dd67505122ac3489016cd2c6f36fdfad65bdb14&gclid=CjwKCAjwt7SWBhAnEiwAx8ZLatQOmma6jcmlAcX4VrmK6PGwtHcBqai4WNgA6a3U6YK5dAVj_OUZZBoCo5IQAvD_BwE
--
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/fa97e9d4-7f56-4b64-8f81-59ab915b0519n%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/b8403e7e-4d20-5d6d-6498-e06ac4d1c350%40gmail.com.

Re: [weewx-user] is PCE-FWS 20N a re-badged fine offset device?

2022-07-13 Thread Rainer Lang


Now, this depends on various factors:
a) what does "modestly priced" mean for you ? (price range - upper limit)
b) what do you mean exactly by "raw data" - what is it supposed to look 
like ?
c) is USB a must or just "having used so far" ? could it also be WiFi or 
LAN (via a WiFi router/access point) ?

d) what's your use case/scenario ?
e) any plans for extension/expansion (e.g. wanting to use more, 
different sensors) ?
f) do you need a display console or is viewing live data on a smartphone 
or old tablet enough/acceptable ?
g) what's your "processing infrastructure" ? e.g. a RaspberryPi (models 
3 or 4B)
h) do you want a more "integrated" solution (outdoor sensor array) or a 
more distributed solution (separate sensors and locations) ?


Depending on the answers to these questions, a +/- tailored 
proposal/suggestion could be made based on FineOffset/Ecowitt weather 
station/sensor combinations and maybe some additional tools like weewx 
and even some more



There are many (more) modern Fine Offset / Ecowitt (clone) solutions 
available, which can also be nicely handled by weewx.


If you want to know what can be combined (console with sensors) in the 
FineOffset/Ecowitt ecosystem, have a look at
https://www.wxforum.net/index.php?topic=40730.0 (free of charge 
registration required to see pictures)


P.S. if you don't want to go public with the answers to a) thru h), 
reply to my mail address only



On 13.07.2022 09:05, Peter Wilkinson wrote:

Thanks for full and helpful information.

Sounds ideal, actually. I need USB connection for further processing 
locally and I can handle upload to e.g. Met office Wow myself.


Hard to find a modestly priced system that supports local output of 
mor e-or-less raw data. Recommendations for alternative, more modern, 
setups that permit this would be welcome.


Peter

On Wed, 13 Jul 2022, 07:37 Rainer Lang,  wrote:

This looks like a clone of the old Fine Offset WH1080 weather
station which is no longer sold by Ecowitt due to old technology.
Console connectivity is USB only, no WiFi, no connection to the
weather networks. No solar sensor either. (a solar panel for
running the outdoor array, yes).
The outdoor array is likely to be not compatible to the modern
WiFi consoles and gateways like GW1000/GW1100/GW2000 due to using
a different modulation for the sensor signal transmission. This is
also true vice versa - the WH1080 console cannot receive any of
the modern FineOffset/Ecowitt sensors.

On 12.07.2022 18:57, Peter Wilkinson wrote:

Certainly looks like it might be but would appreciate confirmation.

Full skinny here:


https://www.pce-instruments.com/english/index.htm?id=google-uk&_artnr=5933243&_p=159.6&_pmode=0&_pbexkey=37&_date=20220711011313&_pbhash=3d8b84805bd95306b3a50a774dd67505122ac3489016cd2c6f36fdfad65bdb14&gclid=CjwKCAjwt7SWBhAnEiwAx8ZLatQOmma6jcmlAcX4VrmK6PGwtHcBqai4WNgA6a3U6YK5dAVj_OUZZBoCo5IQAvD_BwE

<https://www.pce-instruments.com/english/index.htm?id=google-uk&_artnr=5933243&_p=159.6&_pmode=0&_pbexkey=37&_date=20220711011313&_pbhash=3d8b84805bd95306b3a50a774dd67505122ac3489016cd2c6f36fdfad65bdb14&gclid=CjwKCAjwt7SWBhAnEiwAx8ZLatQOmma6jcmlAcX4VrmK6PGwtHcBqai4WNgA6a3U6YK5dAVj_OUZZBoCo5IQAvD_BwE>
-- 
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/fa97e9d4-7f56-4b64-8f81-59ab915b0519n%40googlegroups.com

<https://groups.google.com/d/msgid/weewx-user/fa97e9d4-7f56-4b64-8f81-59ab915b0519n%40googlegroups.com?utm_medium=email&utm_source=footer>.



-- 
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/Vpqj61ff-SI/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/b8403e7e-4d20-5d6d-6498-e06ac4d1c350%40gmail.com

<https://groups.google.com/d/msgid/weewx-user/b8403e7e-4d20-5d6d-6498-e06ac4d1c350%40gmail.com?utm_medium=email&utm_source=footer>.

--
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/CADMzL2%2BRdeb6ON-%3DuxniFpe7y7vq8WYtkeZWknHvsUYh0

Re: [weewx-user] WeeWx and Ecowitt HP2553

2022-08-01 Thread Rainer Lang

You can use the weewx interceptor driver - station_type = ecowitt-client
and have your HP2551 console post via custom server to the server where
your weewx runs. path must contain a "/" (without ""), server/IP is IP
address only (no http:// in front) - port has to be the same where the
interceptor driver listens to - e.g. 8000. (port = 80 won't work as your
web server usually already uses this port)

If you use more than the standard sensors, you will an expanded version
of the Ecowitt driver some forum members have developed based on Matthew
Wall's original version which considers the whole Ecowitt sensor "fleet".

A mere HP2553 (WS80 + WH40 outdoor sensors) should be covered by the
original M.Wall interceptor driver from GitHub.

On 01.08.2022 15:07, Martin Davies wrote:
Hi - I was looking for some guidance on how to send data from an
Ecowitt HP2553 weather station to WeeWx. Looking at the WeeWx
documentation I can't find any specific guidance. I believe that there
isn't a standard WeeWx configuration for HP2553? I understand you may
need to configure a custom interface using 'HTTP Post' etc? Many
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/d05b662b-c2e1-474a-83d1-fd3d28707cd3n%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/8e2fed44-ad2d-95af-ebf5-276925b2676f%40gmail.com.

[weewx-user] integrating a TFA RH100 in weewx [2]

2020-12-17 Thread Rainer Lang

I guess the TFA R100 is the predecessor model of the TFA KLIMALOGG PRO
30.3039.

TFA Dostmann don't have it in the catalogue anymore.

Did you check https://github.com/matthewwall/weewx-klimalogg ?

Maybe this works for you.

On 17.12.2020 12:43, 'G.-U. M' via weewx-user wrote:

Hello,
please excuse my bad english and i'm sorry if i didn't find the answer
to my question here before asking.or

Setup:
-Raspberry Pi (3B+) with Raspbian Buster and WeeWx (Raspberry Pi runs
without any trouble since last year, weewx is installed since 3 days).
- TFA Dostmann RH100 (Temperature and Humidity Logger) with a
USB-Stick for transmitting data to the windows software "KlimaLogg
Pro". I remember that the stick identifies itself as a "LaCrosse"-Product.

Target:
Retrieving the data from the Logger into Weewx. After reading the user
guide my problem started: What kind of device and model should i set?
Setting it to "LaCrosse" leads to exceptions when running "wee_device"
again.

Questions: Is it possible to integrate my logger in WeeWx? What kind
of device do i need to assign? How can i assign the device now?

Thank your for helping a newbee.

Greetings

gumeyer
--
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/676bd524-18d4-4fd0-a524-3dc76e66a915n%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/e24ed58d-5005-4e3b-5e64-932da3399cbf%40gmail.com.

[weewx-user] how to archive (write into the DB) unmapped GW1000 API sensor fields to unused database fields in the extended schema

2020-12-21 Thread Rainer Lang

I have several sensors which in my observation do not have a counterpart
in the extended weewx database schema.

But I still want them stored in the weewx database and have them and
their history displayed in the web interface under http://IP-address/weewx

E.g. there seems to be only one (1) field for PM2.5 sensors, however
I've got two of the WH41 sensors and the GW1000 provides values for both.
I already managed to get one of them displayed in the current conditions
and daily chart page (and also making them show on the weekly, monthly,
yearly pages is now just a matter a

I suspect that the second simply gets lost as there is no standard field
in the database to accommodate them.

In a post in the WXforum Gary mentions several approaches how to store
("archive" in weewx terminology) such sensor values ("observations") in
the weewx database.

https://www.wxforum.net/index.php?topic=34857.0

"So in summary the following approaches (in order of complexity) are
available:

1. utilise existing but unused database fields
2. use a customised database schema by adding to the existing schema
3. use a customised database schema by creating a new schema
4. use a second database"

I want to go for number 1 but didn't find instructions how (and where)
to do so.

Can anyone provide guidance here please ?

Thanks and regards

Rainer

--
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/bf603cb8-33e7-208d-e88c-41a3395e475c%40gmail.com.

[weewx-user] updating missing data fields in the weewx database - can I use wee_import ?

2020-12-23 Thread Rainer Lang

Hi,

I'm about to close gaps in my data history (due to system downtime and
also historical data from my pre-weewx times).
Adding missing records is nicely described and looks rather simple and
straightforward.

However, I don't know how to handle the update of already existing records.
E.g. due to missing information my radiation data in the DB are missing
while all other sensor data are already stored.

Can I use wee_import the same way I do for importing new records ?

If so, what data do I have to provide ? Only the content of the
to-be-updated fields or the whole record (i.e. values for all fields).

Or, does it not work with wee_import and I have to do it differently ?
If so, how ?

Another question indirectly related to the import of history data.

How do I display earlier years (in day, week, month, year aggregation
like in the current year ?) beyond the scarce reports to be chosen in
the "upper right corner" ?

Will I have to create a sort of history skin where I can select date,
week, month, year and based on this selection the picture generator will
provide the graphics ?

Or does some such"piece" already exist (fully, partially, ...) ?

Please advise.

Thanks
Rainer

--
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/974a328a-d3e2-ee1c-c216-b90f0cc6653e%40gmail.com.

Re: [weewx-user] Ecowitt WH2320E compatible?

2021-03-25 Thread Rainer Lang

The WH2320E data can be processed by weewx with the interceptor driver,
device_type = ecowitt-client,

using the customized server function in the WH2320E (set up via WSView app).

On 25.03.2021 21:36, Fraoch wrote:
This looks a lot like a Fine Offset WH2900, at least the sensor
assembly does. Also like the Fine Offset HP2550. Is it compatible with
weewx?

My old National Geographic NG-265NC (Fine Offset 109x) is crumbling to
pieces. Last year the moisture sensor would only report very high, now
it doesn't report at all. Just before winter my anemometer cups broke off.

Now that I'm on the market again, prices have risen and availability
here in Canada is as dismal as ever. It's either this or an AcuRite
0264M, which is specifically listed as compatible.

The Ecowitt adds a UV sensor which the AcuRite doesn't have and which
I've never had before.

I guess I can't complain much, my first weewx data goes back to May 9,
2014. That's almost 7 years. Guess it doesn't owe me anything.

Any comments?

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/493ed3f5-d062-4f71-8786-a2692a08fc91n%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/43782aea-c6ee-41a9-cab8-89f8a4b7c4e1%40gmail.com.

Re: [weewx-user] interceptor driver current version

2021-03-31 Thread Rainer Lang


The driver on GitHub is up to date.
Works with a WH2900.
Just recently (a few days ago) helped someone to get it up and running 
on their RPi.


The following recipe will work:

in WSView app:
Customized server
protocol Ecowitt
Port 8000 (or your choice - has to match the entry in weewx.conf)
some path entry MUST be in WSView (even though it is ignored by weewx) 
i.e. e.g. /data


in weewx.conf
in the [Interceptor] section
--- start weewx.conf excerpt --
[Interceptor]
    # This section is for the network traffic interceptor driver.

    # The driver to use:
    driver = user.interceptor

    # Specify the hardware device to capture.  Options include:
    #   acurite-bridge - acurite internet bridge, smarthub, or access
    #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
    #   lw30x - oregon scientific LW301/LW302
    #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
    #   ecowitt-client - any hardware that uses the ecowitt protocol
    #   wu-client - any hardware that uses the weather underground protocol
    device_type = ecowitt-client
    port = 8000
    iface = eth0   # (or wlan0, depending on the network interfasce you 
use) [without the iface entry you may get stuck]


--- end of weewx.conf excerpt 
-


good luck.

On 31.03.2021 16:19, Alex Slaets wrote:

just a quick question before I start hacking.

CONFIG:
Hardware: Alecto WS-5500  (=Fine Offset WH2900) .
LAMP server - raspberry Pi 4
WeeWX version 4.4.0 from raspbian repositories
python defaults set to python3
AWS is running and reporting to the Met Office WOW.
weewx is up and running with the simulation driver
Will use interceptor driver in listening mode using either ecowitt or 
wu protocol, both are supported.


QUESTION:
Want to doublecheck before starting to hack away:
CHECK: is github matthewwall/wee-wx-interceptor the correct repo ?
Do I pull the latest master ? Which is the commit b29de05 
 on 
22 Feb 2020


REASON:
The readme mentions that Matthew intends to merge the functionality in 
weewx, and the latest release mentioned in github is 0.28 from 2017 - 
which makes me a bit weary.


Thank you.



--
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/f48f2079-b693-47dc-9175-a1607dd9c6f0n%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/230b9d06-fdd7-9473-78e1-915704bd0d38%40gmail.com.

Re: [weewx-user] WH57(lighning detection) and GW1000 send daily summary on every records

2021-04-11 Thread Rainer Lang

we recommend NOT to use the intereptor driver for a GW1000/WH2650 
console but to use the meanwhile existing
GW1000 API driver instead - otherwise you tend to run into multiple 
issues (and unnecessarily use the
console's "Customized"server option which exists only once) due to the 
many extra sensors being released.


The GW1000 API driver covers all existing FineOffset/Ecowitt (clone) 
sensors and is very stable.

Gary did an excellent job here.
https://github.com/gjr80/weewx-gw1000

On 11.04.2021 15:36, Johann Destombes wrote:

Yes I'm agree. This is the driver part of my weewx.conf:
/
/
/###
[Interceptor]
    driver = user.interceptor
    device_type = ecowitt-client
    port = 8000

    [[sensor_map_extensions]]
    lightning_strike_count = lightning_num
    lightning_distance = lightning
 ### /

I followed this link: 
https://github.com/matthewwall/weewx-interceptor/issues/69 
 to 
modifie interceptor.py.

So this is the ecowitt-client part of my interceptor.py:

Row 2306 to 2459.
/...
class EcowittClient(Consumer):
    """Use the ecowitt protocol (not WU protocol) to capture data"""

    def __init__(self, **stn_dict):
    super(EcowittClient, self).__init__(
    EcowittClient.Parser(), handler=EcowittClient.Handler, 
**stn_dict)


    class Handler(Consumer.Handler):

    def get_response(self):
    return '{"errcode":"0","errmsg":"ok","UTC_offset":"-18000"}'

    class Parser(Consumer.Parser):

    # map labels to observation names
    LABEL_MAP = {
    'baromabsin': 'pressure',
    'humidity': 'humidity_out',
    'humidityin': 'humidity_in',
    'tempf': 'temperature_out',
    'tempinf': 'temperature_in',
    'temp1f': 'temperature_1',
    'temp2f': 'temperature_2',
    'temp3f': 'temperature_3',
    'temp4f': 'temperature_4',
    'temp5f': 'temperature_5',
    'temp6f': 'temperature_6',
    'temp7f': 'temperature_7',
    'temp8f': 'temperature_8',
    'humidity1': 'humidity_1',
    'humidity2': 'humidity_2',
    'humidity3': 'humidity_3',
    'humidity4': 'humidity_4',
    'humidity5': 'humidity_5',
    'humidity6': 'humidity_6',
    'humidity7': 'humidity_7',
    'humidity8': 'humidity_8',
    'batt1': 'battery_1',
    'batt2': 'battery_2',
    'batt3': 'battery_3',
    'batt4': 'battery_4',
    'batt5': 'battery_5',
    'batt6': 'battery_6',
    'batt7': 'battery_7',
    'batt8': 'battery_8',
    'soilmoisture1': 'soil_moisture_1',
    'soilmoisture2': 'soil_moisture_2',
    'soilmoisture3': 'soil_moisture_3',
    'soilmoisture4': 'soil_moisture_4',
    'soilmoisture5': 'soil_moisture_5',
    'soilmoisture6': 'soil_moisture_6',
    'soilmoisture7': 'soil_moisture_7',
    'soilmoisture8': 'soil_moisture_8',
    'soilbatt1': 'soil_battery_1',
    'soilbatt2': 'soil_battery_2',
    'soilbatt3': 'soil_battery_3',
    'soilbatt4': 'soil_battery_4',
    'soilbatt5': 'soil_battery_5',
    'soilbatt6': 'soil_battery_6',
    'soilbatt7': 'soil_battery_7',
    'soilbatt8': 'soil_battery_8',
    'windspeedmph': 'wind_speed',
    'windgustmph': 'wind_gust',
    'winddir': 'wind_dir',
    'solarradiation': 'solar_radiation',
    'uv': 'uv',
    'totalrainin': 'rain_total',
    'rainratein': 'rain_rate',
    'wh25batt': 'wh25_battery',
    'wh26batt': 'wh26_battery',
    'wh40batt': 'wh40_battery',
    'wh65batt': 'wh65_battery',
     'pm25_ch1': 'pm2_5',
    'pm25batt1': 'pm25_battery',
    'lightning': 'lightning',
    'lightning_time': 'lightning_time',
    'lightning_num': 'lightning_num',
    'wh57batt': 'wh57_battery',
    'leak_ch1': 'leak_1',
    'leak_ch2': 'leak_2',
    'leak_ch3': 'leak_3',
    'leak_ch4': 'leak_4',
    'leakbatt1': 'leak_battery_1',
    'leakbatt2': 'leak_battery_2',
    'leakbatt3': 'leak_battery_3',
    'leakbatt4': 'leak_battery_4',
    }

    IGNORED_LABELS = [
    'PASSKEY', 'dateutc', 'stationtype', 'model', 'freq', 
'baromrelin',

    'maxdailygust', 'eventrainin', 'hourlyrainin', 'dailyrainin',
    'weeklyrainin', 'monthlyrainin', 'yearlyrainin',
    'pm25_avg_24h_ch1', 'winddir_avg10m', 'windspdmph_avg10m',
    ]

    def __init__(self):
    self._last_rain = None
    self._rain_mapping_confirmed = False

    def parse(self, s):
    pkt = dict()
    try:
    data = _cgi_to_

Re: [weewx-user] WH57(lighning detection) and GW1000 send daily summary on every records

2021-04-13 Thread Rainer Lang

While the GW1000 API driver provides you all the fields you can see in 
the field map (--> wiki, https://github.com/gjr80/weewx-gw1000/wiki), 
weewx archives/stores/writes to the database only the fields which are 
contained in its database schema.


If you started with weewx 4.x.x that's most likely the wview_extended 
schema (what you have you can see in your weewx.conf

in [DataBindings]     [[wx_binding]].
It resides (under Debian/Raspbian) at /usr/share/weewx/schemas as 
wview_extended.py


If your schema is still the old wview schema because you created your 
database with weewx V3.x.x or earlier, you will have to change that (see 
wiki [https://github.com/weewx/weewx/wiki] and customization guide 
[http://www.weewx.com/docs/customizing.htm]).


If the driver provides fields for processing which are not in the 
database schema, they will not be archived.


There a several ways how to change that:
- repurposing existing but not used fields
- extending you database schema ... (also wview_extended can be further 
extended 😉)


There is a good, brief description of the options to be found at
https://www.wxforum.net/index.php?topic=34857.msg355511#msg355511

I personally went for the re-purposing method (even though I acknowledge 
that extending the DB schema is more elegant)
to accommodate my WH41, WH51 and WH45 data in the database. But the same 
applies for the battery status data etc.



e
On 12.04.2021 22:40, Johann Destombes wrote:
Thanks, I just install gw1000 driver and it's works great, I just need 
a storm to see if everything is well record.


When I read the GW1000driver wiki I understand that the driver record 
somewhere more extended data like wh57 battery level or timestamp of 
last lightning strike .
In my case Weewx record archive data in a mysql database but I was not 
able to find where these data are stored. Are they somewhere in the 
archive database or are they just loop data ?


Le dimanche 11 avril 2021 à 23:17:37 UTC+2, lang@googlemail.com a 
écrit :


we recommend NOT to use the intereptor driver for a GW1000/WH2650
console but to use the meanwhile existing
GW1000 API driver instead - otherwise you tend to run into
multiple issues (and unnecessarily use the
console's "Customized"server option which exists only once) due to
the many extra sensors being released.

The GW1000 API driver covers all existing FineOffset/Ecowitt
(clone) sensors and is very stable.
Gary did an excellent job here.
https://github.com/gjr80/weewx-gw1000


On 11.04.2021 15:36, Johann Destombes wrote:

Yes I'm agree. This is the driver part of my weewx.conf:
/
/
/###
[Interceptor]
    driver = user.interceptor
    device_type = ecowitt-client
    port = 8000

    [[sensor_map_extensions]]
    lightning_strike_count = lightning_num
    lightning_distance = lightning
 ### /

I followed this link:
https://github.com/matthewwall/weewx-interceptor/issues/69
 to
modifie interceptor.py.
So this is the ecowitt-client part of my interceptor.py:

Row 2306 to 2459.
/...
class EcowittClient(Consumer):
    """Use the ecowitt protocol (not WU protocol) to capture data"""

    def __init__(self, **stn_dict):
    super(EcowittClient, self).__init__(
    EcowittClient.Parser(),
handler=EcowittClient.Handler, **stn_dict)

    class Handler(Consumer.Handler):

    def get_response(self):
    return
'{"errcode":"0","errmsg":"ok","UTC_offset":"-18000"}'

    class Parser(Consumer.Parser):

    # map labels to observation names
    LABEL_MAP = {
    'baromabsin': 'pressure',
    'humidity': 'humidity_out',
    'humidityin': 'humidity_in',
    'tempf': 'temperature_out',
    'tempinf': 'temperature_in',
    'temp1f': 'temperature_1',
    'temp2f': 'temperature_2',
    'temp3f': 'temperature_3',
    'temp4f': 'temperature_4',
    'temp5f': 'temperature_5',
    'temp6f': 'temperature_6',
    'temp7f': 'temperature_7',
    'temp8f': 'temperature_8',
    'humidity1': 'humidity_1',
    'humidity2': 'humidity_2',
    'humidity3': 'humidity_3',
    'humidity4': 'humidity_4',
    'humidity5': 'humidity_5',
    'humidity6': 'humidity_6',
    'humidity7': 'humidity_7',
    'humidity8': 'humidity_8',
    'batt1': 'battery_1',
    'batt2': 'battery_2',
    'batt3': 'battery_3',
    'batt4': 'battery_4',
    'batt5': 'battery_5',
    'batt6': 'battery_6',

Re: [weewx-user] Re: Best air quality sensor for weewx

2021-04-23 Thread Rainer Lang

In combination with a Weather station, or just with a console (GW1000)
you can check e.g. the sensors and sensor-combos offered by FineOffset
via Ecowitt and resellers.
You will find a lot of info regarding this in the WXforum (not limited
to FineOffset (clones)). All supported by weewx.
As for FineOffset an overview would be
https://www.wxforum.net/index.php?topic=40730.0

and there's a lot of discussion and exchange about it/them.

"Best options" depend on your use case, your priorities
(indoor/outdoor/both), your situation/location (e.g. forest or near
chemical plant, busy highway, ...)

I'd say, you first define for yourself your needs (use case), and then
look out for what may serve your information needs (and budget
situation) best.
At the end of the day you can use/add/combine many different sensors
with (several instances of) weewx and can create a highly sophisticated
metereological reporting.

On 23.04.2021 13:33, sbar...@gmail.com wrote:

Hi,

sds011, with usb is supported by weewx. And sensebox.de has hardware
kits and diy info to make some that will survive outdoor. Do not know
if there is an all-in-one solution for all the compounds you listed.

Regards,

On Friday, April 23, 2021 at 1:27:14 PM UTC+2 xsli...@gmail.com wrote:

That looks great Karen :) but do we have something also for
outdoor placement?

Dne pátek 23. dubna 2021 v 11:36:52 UTC+2 uživatel
kk44...@gmail.com napsal:

airQ

xsli...@gmail.com schrieb am Freitag, 23. April 2021 um
08:04:22 UTC+2:

Hello,

I'd like to ask those who already use some air quality
sensors connected with weewx what is the best option these
days. When I check commercial weather webs I usually see
values PM2.5, PM10, CO, O3, SO2, NO2. Do we have some
all-in-box solution for these values already? Or it's
necessary to build it from modules? I saw Arduino has many
modules which can be plugged but not sure if I have enough
time to play with that :)

Thanks for hints

--
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/61fdec55-635b-4de5-9151-f5327dd92934n%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/ae8f20a7-9564-4250-a792-ffb7675dc6a9%40gmail.com.

Re: [weewx-user] Re: Publish Seasons Skin to webserver

2021-05-06 Thread Rainer Lang


I had the same/a similar issue.
What finally worked was:
1. uploading the whole /var/www/html/weex directory manually (1st time) 
with e.g. FileZilla

then also only the tables would show
2. activate FTP in [StdReport] - restart weewx
with the next archiving circle also the pictures were shown ..

On 06.05.2021 15:13, Karen K wrote:

Try removing the file #FTP.last and wait one report cycle.

PeterGill schrieb am Donnerstag, 6. Mai 2021 um 14:37:49 UTC+2:

I believe you are on to something. I have restarted Weewx and
waited for a number cycles. It´s clear that some files are missing
on the webserver. I have verified that through the webserver file
manager. For instance, the font library on the webserver is empty,
also seasons.css and seasons.js is not present on the webserver
but in the local /var/www/html/weewx library they are. This
applies to other files as well. It seems FTP only uploads files
that has changed despite the restart of weewx. Is there any way to
restart Ftp and/or make it run an all file upload?

On Thursday, May 6, 2021 at 12:24:00 PM UTC+2 gjr80 wrote:

Looks like the Seasons skin html and plot files are being
uploaded but the css and maybe fonts etc are not. The css,
fonts and other static files should be copied to
/var/www/html/weewx during the first time the Seasons skin is
‘run’ after a WeeWX restart and then uploaded to your web
server when the FTP skin is ‘run’. Let’s take a punt and
restart WeeWX, monitor the log and wait for the first report
cycle to complete (ie Seasons and FTP skins have been
processed) and then try browsing to your web server. If it
doesn’t display correctly try clearing your browser cache. If
still no luck post a log extract from when you started WeeWX
just now through until a couple of report cycles are complete.

Gary

On Thursday, 6 May 2021 at 20:08:48 UTC+10 PeterGill wrote:

This is the web server view


2021-05-06 12_03_03-Sigtuna, Sweden.jpg


And this is the view of the local index.html

2021-05-06 12_02_17-Homeserver (Homeserver) - VNC Viewer.jpg






On Thursday, May 6, 2021 at 11:58:54 AM UTC+2 gjr80 wrote:

All looks fine to me. Don’t understand  what you mean
by “the webserver shows Ftp skin”. The FTP skin does
not generate files; it simply copies some other skins
files via FTP. What happens when you enter your
website address in a browser, does it display the
Season skin main page or something else?

Gary
On Thursday, 6 May 2021 at 19:49:30 UTC+10 PeterGill
wrote:

The funny thing is that the local file
/var/www/html/weewx /index.html shows the Season
skin but the webserver shows Ftp skin. My set up
is below as well as an extraction from syslog at
the bottom. In syslog you can see that
/var/www/html/weewx /index.html is successfully
sent to the webserver. Strange. The only thing
that differs from standard setup is path is set to
/ instead of /weather

Again, help is really appreciated

    [[SeasonsReport]]
        # The SeasonsReport uses the 'Seasons'
skin, which contains the
        # images, templates and plots for the report.
        skin = Seasons
        enable = true
    [[SmartphoneReport]]
        # The SmartphoneReport uses the
'Smartphone' skin, and the images and
        # files are placed in a dedicated
subdirectory.
        skin = Smartphone
        enable = false
        HTML_ROOT = /var/www/html/weewx/smartphone
    [[MobileReport]]
        # The MobileReport uses the 'Mobile' skin,
and the images and files
        # are placed in a dedicated subdirectory.
        skin = Mobile
        enable = false
        HTML_ROOT = /var/www/html/weewx/mobile
    [[StandardReport]]
        # This is the old "Standard" skin. By
default, it is not enabled.
        skin = Standard
        enable = false
    [[FTP]]
        # FTP'ing the results to a webserver is
treated as just another report,
        # alb

Re: [weewx-user] overloading gw1000?

2021-05-09 Thread Rainer Lang

I don't think that that's a phenomenon to be generalized.
My GW1000s (s !) are running with weewx (API) and Meteobridge (API)
being polled every 10 seconds without getting stuck.

There must be another reason for this behavior, maybe an instability in
the power grid (if it's not buffered by a proper UPS for the GW1000),
maybe an older firmware (actual is 1.6.6), maybe something in your local
network or router (it may get stuck if it cannot synchronize with
ecowitt.net) - or you got a Friday model - not to be excluded, this also
happens or something else.
But I doubt that an overload from the weewx end is the reason for this
behavior.

Did you check the FineOffset clone board on wxforum.net ?
https://www.wxforum.net/index.php?board=111.0
There are many posts already there in this regard. Some search is
required though.

Or open a post there ? The issue is likely not to be weewx related.

On 09.05.2021 01:21, Graham Eddy wrote:

every 24 hours or so recently my gw1000 has become unresponsive and required a
power cycle.
i am not only polling it every 20 secs in production weewx instance, i am also
polling it every 20 secs in two more test weewx instances → i think i am
overloading it. just because the api is there doesn’t mean it can be hammered
continuously...

--
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/7ac0e725-24b7-b0bf-e3ac-cfd0d2b90fdb%40gmail.com.

Re: [weewx-user] Recovery from 3 month outage

2021-05-25 Thread Rainer Lang

Searching helps 😎
As per that link (review) the 01536 can save records for two weeks
(don't say based on what interval)

https://weatherstationexpert.com/acurite-01536/

On 25.05.2021 05:45, Jeff Carpenter wrote:

Hello

I just discovered that my weewx installation has not been collecting
data from my Acurite weather station for about 3 months, even though
it appears the Raspberry Pi where weewx is running has been up - I
haven't restarted that Pi in probably over a year. I rebooted the PI
and weewx is now collecting new data.

From the documentation it sounds like weewx will go back and collect
historical data from the Acurite, is this correct? How much of that
historical data should I expect to recover?

I've attached output of wee_debug command.

Thanks
Jeff
--
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/c25e420d-2778-48d9-9622-7cea63fee08cn%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/c208b952-cf5d-006f-a61b-4ea3012f7aa8%40gmail.com.

[weewx-user] weewx.com down ??

2021-05-27 Thread Rainer Lang


Can't reach the weewx.com site 
Anyone else has the same observation ??

--
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/3776bd7a-71da-06f5-258e-ca6c4f4c7147%40gmail.com.

Fwd: [weewx-user] Re: weewx.com down ??

2021-05-27 Thread Rainer Lang

 Forwarded Message 
Subject:Re: [weewx-user] Re: weewx.com down ??
Date:   Thu, 27 May 2021 11:22:41 +0200
From:   Rainer Lang 
To: Karen K 

That was not the question ...
@Karen:
can you connect with your browser ? A positive or negative reply would 
be helpful.

I tried to connect all the time via https
all browsers provide the same reply - can't connect (https)
the tracert was just an example
but it shows that the route goes through until Seattle where the site is 
hosted.

On 27.05.2021 11:17, Karen K wrote:

The website is displayed with https. The maps page does not work only.

lang@googlemail.com schrieb am Donnerstag, 27. Mai 2021 um 
11:14:55 UTC+2:

Can't reach the weewx.com <http://weewx.com> site 
Anyone else has the same observation ??

--
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 
<mailto:weewx-user+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e9f274f4-91e6-4e7a-bd0e-d314903c5025n%40googlegroups.com 
<https://groups.google.com/d/msgid/weewx-user/e9f274f4-91e6-4e7a-bd0e-d314903c5025n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
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/53cd75be-fc63-2d6f-0db4-bf01162f733b%40gmail.com.

Re: [weewx-user] Re: no connection to the web server

2021-05-29 Thread Rainer Lang


@OP: don't give up too early, too fast 😉

As per his OP, it looks as if he is using Apache2, however, if the web 
server is configured properly and configured to display the html files 
created under /home/weewx/public_html (and if it's running at all) is a 
different question.


Weewx seems to run properly, saves every 5 minutes data to the database 
and the pictures and the html page of the Seasons skin are created - the 
issue is that they are not displayed in the browser.


So it appears to be web server configuration question

Afaik, by default, apache2 expects files to be read from outside via 
http/https to be located in /var/www/html and subdirectories.
If another directory / path is being used (e.g. 
/home/weewx/public_html), Apache needs to be told (and needs to have 
read rights for this directory).


maybe for an inexperienced user (we don't know the experience level of 
the OP) our explanations need to be more explicit


first of all, as stupid as it may sound, apache needs to run:
check via: *service apache2 status*
then
see what several posts/replies suggest:
---
... have the file "weewx.conf" in "/etc/apache2/conf-enabled/" folder?

this file (weewx.conf) is NOT the weewx.conf from /etc/weewx used to 
start weewx
but a file with the same name (i.e. weewx.conf) and it should have the 
content which is shown below, starting with "Alias /weewx " (without "")


*Alias /weewx /home/weewx/public_html*
**
*    Options FollowSymlinks*
*    AllowOverride None*
*    Require all granted*
**
---
if it exists, check if the content matches the bold text above
if it doesn't exist, create a text file weewx.conf with the above 
content in bold - save !


apache2 needs to be restarted after changes made (or creation) of/to 
(the Apache specific file) weewx.conf

with
|sudo /etc/init.d/apache2 restart|

then in principle the Seasons skin should be visible in the web browser

Another test could be to copy the content of /home/weewx/public_html
to /var/www/html/weewx
(create the folder weewx if not existing with sudo mkdir 
/var/www/html/weewx)

allow apache to read it
sudo chmod -R 755 /var/www/html/weewx
and then check in the browser:
http://ip-address/weewx

if this works, apache2 is running properly and also hasn't been told 
where to pick up the weewx index.html



On 29.05.2021 15:40, Tom Keffer wrote:
He may not be using Apache. Indeed, he may not have a webserver at 
all --- we don't know.


On Sat, May 29, 2021 at 5:52 AM storm...@gmail.com 
 > wrote:


Check to see if the weewx.conf  is also in 
/etc/apache2/conf-available folder.

On Saturday, May 29, 2021 at 4:25:05 AM UTC-4
eckha...@googlemail.com  wrote:

i reinstalled all of them ... then i checked the folders on
the spot and checked their contents. without success! I give up.

vince schrieb am Samstag, 29. Mai 2021 um 03:45:52 UTC+2:


See if the FAQ
 
helps
any.

You've established weewx is generating files. You haven't
pinned down whether weewx+apache are in agreement on where
the web pages are, nor if apache is running at all.


On Friday, May 28, 2021 at 6:22:18 PM UTC-7
storm...@gmail.com wrote:

Do you have the file "weewx.conf" in
"/etc/apache2/conf-enabled/" folder?


Alias /weewx /home/weewx/public_html

    Options FollowSymlinks
    AllowOverride None
    Require all granted


If not, add the file and restart apache2

On Friday, May 28, 2021 at 9:08:58 PM UTC-4
tke...@gmail.com wrote:

Everything looks totally normal to me. Did you
browse to file:///home/weewx/public_html/?

Or, did you tell your webserver to look there?

On Fri, May 28, 2021 at 5:40 PM
'eckha...@googlemail.com' via weewx-user
 wrote:


index.PNG


the funny thing is there is also data in the
file but i can't call it up


eckha...@googlemail.com schrieb am Samstag,
29. Mai 2021 um 02:34:30 UTC+2:

Unbenannt.PNG

eckha...@googlemail.com schrieb am
Samstag, 29. Mai 2021 um 02:33:35 UTC+2:



weewx.PNG
tke...@gmail.com schrieb am Samstag,
29. Mai 2021 um 02:15:55 UTC+2:

Weewx seems to be running normally.

Re: [weewx-user] Re: WeeWX Interceptor: Rain not registering

2021-06-02 Thread Rainer Lang


One side remark regarding the dialogue below:
A Ventus830 (a FineOffset/Ecowitt WH2910 clone) cannot be updated with 
the WSTool app, even though this is sometimes written like that in the 
manual - you need the WSView app (latest version 😁) - when a firmware 
newer than what you have is available, the WSView app will tell you and 
offer the upgrade.


I can provide you with a working weewx with a WH2310E (also Froggit 
WH4000SE) and the interceptor driver on a RPi4.
The used WiFi-firmware of the WH2320E console and of the WH2910 console 
(Ventus 830) are the same and you will be using the customized server 
option in the console which is handled by the WIFi firmware. Setup via 
WSView app.


There is no big example, just straightforward.

In the WSView app you have to enter the IP address of your server (RPi, 
), a path (it doesn't matter which path, but a path has to be there 
- otherwise the console will not send data - so /data is ok)
a port: 8000 is a good choice (has to be a port which is not used by 
another application on your server, hence 80 is not advisable)
and and posting interval - can be anything between 16 seconds and 
several minutes - I use 16 seconds)


your [Interceptor] section in weewx conf has to match these entries:

#-- start weewx.conf excerpt 
[Interceptor]

    # This section is for the network traffic interceptor driver.

    # The driver to use:
    driver = user.interceptor

    # Specify the hardware device to capture.  Options include:
    #   acurite-bridge - acurite internet bridge, smarthub, or access
    #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
    #   lw30x - oregon scientific LW301/LW302
    #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
    #   ecowitt-client - any hardware that uses the ecowitt protocol
    #   wu-client - any hardware that uses the weather underground protocol
    device_type = ecowitt-client
    port = 8000
    iface = eth0
# -- end weewx.conf excerpt 

- if you use your WLAN interface ("WiFi"), the line must be "iface 
=wlan0" (without "")
- not using the interface option can lead to difficulties on certain 
servers,
- using WLAN on a Raspberry Pi is not very stable for the interceptor 
driver (feedback from several users)

that's not a weewx issue but a RPi issue
=> (at least on a RPi, Ethernet cable connection recommended)

to verify if you receive data you can run weewx directly in console mode:

sudo weewxd /etc/weewx/weewx.conf

(or whereever your weewx.conf is located - might be 
/home/weewx/weewx.conf depending on your weewx installation)


you should get a console output like:
LOOP:   2021-06-02 11:33:03 CEST (1622626383) altimeter: 
30.040055564887226, appTemp: 77.23757274365485, barometer: 
30.002845135685217, cloudbase: 5485.357712782114, dateTime: 1622626383, 
dewpoint: 55.90748098068117, heatindex: 75.54, humidex: 
81.21588779667552, inDewpoint: 53.130015237966376, inHumidity: 43.0, 
inTemp: 77.4, maxSolarRad: None, outHumidity: 50.0, outTemp: 75.9, 
pressure: 29.03, radiation: 903.58, rain: None, rainRate: 0.0, usUnits: 
1, UV: 8.0, windchill: 75.9, windDir: 53.0, windGust: 2.2, windSpeed: 0.9


Good luck !

On 02.06.2021 00:06, Eelco de Graaff wrote:


Does someone a working example of the interceptor for the Ventus W830 
would be nice.


Op zondag 7 juli 2019 om 15:51:48 UTC+2 schreef manfred:

hi Jan,

I'm planning to get a Ventus w830 as well; can you let us know how
well it worked for you (including any success in upgrading to
latest firmware)?
I'm also interested to learn how frequent the intervals are that
you get updates from the station, as one of my usecases involves
closing a suncover if there's sudden wind or rain.

thanks in advance!
Manfred


Op zaterdag 13 januari 2018 14:26:18 UTC+1 schreef jan hallink:

Hello Maarten
I tried several times to upgrade my station from 1.1.2 to
1.1.4 firmware through the ws tool app, But I didn't
succeeded, I got the message download fails.
So I cannot give you at this moment an answer if WOW works
directly.
But with the weewx coupled to my station it is working with WOW

--
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/38119453-cdd6-490f-b2f4-1fb78136b3ffn%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 emai

Re: [weewx-user] recommend IP cameras that are easy to grab a single frame from?

2021-07-04 Thread Rainer Lang

I use three different cameras, one Chinese brand PTZ PoE camera (H.View) 
and two German products (Lupus).
They all save a pic every 60 seconds (as part of their security camera 
feature) to my NAS - the PTZ via NFS, the others via FTP.

On the NAS the (files of the) latest pictures (showing an in-picture 
time stamp) are converted into a common file name like camera1.jpg, 
camera2.jpg, camera3.jpg
and then sent, copied via FTP to the weather sites where the picture(s) 
are to be displayed (as the display programs cannot handle changing file 
names).

It works perfectly.

So per picture it's a little batch job which converts the file name into 
a generic copy and then sends it via ftp to the destination site.
it's a Windows batch job with separate ftp inputs for each picture/site 
- run every minute via Windows Scheduler
(could of course also be a Linux shell script doing the same job and 
then run via CRONTAB)
One of my weather templates shows all three pictures in a row giving a 
270° sky and ground view.

As for weewx skins, the pictures can be used like any other picture to 
be displayed in a skin.
For one template (Meteotemplate) I use the live camera feed picking up 
the http stream from the camera.

You can look the result(s) up at http://meshka.eu 
the 270° pictures are with the pwsWD template
the live camera with the Meteotemplate

So far I don't display a picture in a weewx skin (still to come)

So, in my solution, the camera model doesn't really matter - it's the 
camera features which matter

- sufficient resolution 😁
- ability to save snapshots in a common graphic format (jpg, png, ...) 
every (to be customized:) 1-3600 seconds to a (NAS) server

(- reasonable price 😉 )

On 04.07.2021 01:05, Greg from Oz wrote:

I use this command on a generic webcam:
ffmpeg -i "rtsp://admin:123456@192.168.0.201:554/mpeg4" -vf fps=1/60 
-s 960x480 -strftime 1 
$WEBCAMFILES/$DATEFOLDER/tmp/"%Y%m%d-%H%M%S.jpg" -hide_banner &

It runs in the background and generates a still every 60 seconds and I 
use those pictures to make a time plase.

I use a program called inoticoming that you can set up to do things 
when a file is created in a folder.

For example:
inoticoming  $WEBCAMFILES/$DATEFOLDER/tmp/ --suffix .jpg 
/usr/local/sbin/weather-realtime.sh {} \;

The above says if a picture is created then run 
/usr/local/sbin/weather-realtime.sh and use the generated photo as a 
parameter.

I create a webm movie so if you are viewing on an iphone it won't work.

https://weather.ubeaut.work/webcam.html

On Sunday, 4 July 2021 at 05:30:33 UTC+10 dvdhns wrote:

To grab single frames, this is what I use. I haven't had a problem
with having to wait 10 seconds to get the image. It seems
immediate. I'm using a cheap Jidetech IP Cam with POE. I wouldn't
recommend it as it seems to lose network connectivity occasionally.

/Applications/ffmpeg -i "rtsp://192.168.0.185:554/1/h264major
" -frames:v 1 img.jpg

On Friday, July 2, 2021 at 9:48:33 PM UTC-6 Eric K wrote:

Long ago I played with a dlink camera and as was able to
figure out a
URL that would get a single frame.

Me too!  I had a Dlink DCS-900 and I could get a single camera
image from the URL line.
But, I bricked it trying to update its firmware.
Oh well, it was early-2000s vintage and had a pretty crappy
image sensor, compared to what's on the market today.
I'm looking for a modern, functional replacement for it.

I would not be surprised if you can find into for your camera
on the web
someplace.

The camera with rtsp streaming that I was playing with can
only deliver an rtsp stream via it's Ethernet port (no wifi).
I know because it is made by the company I work in.
I asked some of our software people about grabbing a single
image for a webpage, and they said, nope, only rtsp via the
Ethernet port.
It's primary function is to create full motion video for video
conferencing, so delivering still frames for webpages was not
on the required features list.

Eric

On Friday, July 2, 2021 at 5:52:03 PM UTC-5 Greg Troxel wrote:

Eric K  writes:

> Based on first hand experience, can people recommend
various IP cameras
> (ideally an Ethernet or wifi camera) with a focus
towards ease of grabbing
> a single frame from a Linux command line?
> I'd like to be able to grab single frames to use in the
weewx webpage.
>
> I've tested am Ethernet-connected camera that puts out
an rtsp stream. I
> successfully used an ffmpeg command line to start the
stream, wait 10
> seconds and then grab a frame. Sometimes 10 seconds
isn't enough and I

Re: [weewx-user] Re: Lightning Readings

2021-07-18 Thread Rainer Lang

Did you compare to the readings the GW1000 posts to ecowitt.net (in case 
you have it do so - if not, do it and check the next events) ?
In my case weewx reports the same readings as what is posted by the 
consoles (several GW1000) to Ecowitt.net and to a template using the 
customized server option.



On 18.07.2021 16:26, purch...@maladomini.com wrote:


That is a good question. I am not much up on databases and stuff. I 
found this statement to display the contents of the field for count 
readings”


mysql> select * from archive_day_lightning_strike_count;

++--++--++--+---+---+-+

| dateTime   | min  | mintime    | max  | maxtime    | sum  | count | 
wsum  | sumtime |


++--++--++--+---+---+-+

| 1617429600 |    0 | 1617498307 |    0 | 1617498307 |    0 |   291 
| 0 |   17460 |


| 1617516000 |    0 | 1617516004 |    0 | 1617516004 |    0 |  1254 
| 0 |   75240 |


| 1617602400 |    0 | 1617602410 |    0 | 1617602410 |    0 |  1437 
| 0 |   86220 |


| 1617688800 |    0 | 1617688814 |    0 | 1617688814 |    0 |  1434 
|     0 |   86040 |


| 1617775200 |    0 | 1617775213 |    0 | 1617775213 |    0 |  1440 
| 0 |   86400 |


| 1617861600 |    0 | 1617861611 |    0 | 1617861611 |    0 |  1438 
| 0 |   86280 |


| 1617948000 |    0 | 1617948008 |    0 | 1617948008 |    0 |  1440 
| 0 |   86400 |


| 1618034400 |    0 | 1618034407 |    0 | 1618034407 |    0 |  1440 
| 0 |   86400 |


| 1618120800 |    0 | 1618120817 |    0 | 1618120817 |    0 |  1440 
| 0 |   86400 |


| 1618207200 |    0 | 1618207220 |    0 | 1618207220 |    0 |  1411 
| 0 |   84660 |


| 1618293600 |    0 | 1618293617 |    0 | 1618293617 |    0 |  1431 
| 0 |   85860 |


| 161838 |    0 | 1618380009 |    0 | 1618380009 |    0 |  1432 
| 0 |   85920 |


| 1618466400 |    0 | 1618466419 |    0 | 1618466419 |    0 |  1396 
| 0 |   83760 |


| 1618552800 |    0 | 1618552821 |    0 | 1618552821 |    0 |  1440 
| 0 |   86400 |


| 1618639200 |    0 | 1618639209 |    0 | 1618639209 |    0 |  1433 
| 0 |   85980 |


| 1618725600 |    0 | 1618725614 |    0 | 1618725614 |    0 |  1440 
| 0 |   86400 |


| 1618812000 |    0 | 1618812009 |    0 | 1618812009 |    0 |  1440 
| 0 |   86400 |


| 1618898400 |    0 | 1618898401 |    0 | 1618898401 |    0 |  1438 
| 0 |   86280 |


| 1618984800 |    0 | 1618984820 |    0 | 1618984820 |    0 |  1421 
| 0 |   85260 |


| 1619071200 |    0 | 1619071220 |    0 | 1619071220 |    0 |  1440 
| 0 |   86400 |


| 1619157600 |    0 | 1619157607 |    0 | 1619157607 |    0 |  1198 
| 0 |   71880 |


| 1619244000 |    0 | 1619244007 |    0 | 1619244007 |    0 |  1440 
| 0 |   86400 |


| 1619330400 |    0 | 1619330401 |    0 | 1619330401 |    0 |  1440 
| 0 |   86400 |


| 1619416800 |    0 | 1619416814 |    0 | 1619416814 |    0 |  1437 
| 0 |   86220 |


| 1619503200 |    0 | 1619503202 |    0 | 1619503202 |    0 |  1440 
| 0 |   86400 |


| 1619589600 |    0 | 1619589601 |    0 | 1619589601 |    0 |  1431 
| 0 |   85860 |


| 1619676000 |    0 | 1619676014 |    0 | 1619676014 |    0 |  1440 
| 0 |   86400 |


| 1619762400 |    0 | 1619762411 |    0 | 1619762411 |    0 |  1440 
| 0 |   86400 |


| 1619848800 |    0 | 1619848805 |    0 | 1619848805 |    0 |  1440 
| 0 |   86400 |


| 1619935200 |    0 | 1619935214 |    0 | 1619935214 |    0 |  1439 
| 0 |   86340 |


| 1620021600 |    0 | 1620021614 |    5 | 1620084300 |  124 |  1438 |  
7440 |   86280 |


| 1620108000 |    0 | 1620108005 |    0 | 1620108005 |    0 |  1440 
|     0 |   86400 |


| 1620194400 |    0 | 1620194420 |    0 | 1620194420 |    0 |  1436 
| 0 |   86160 |


| 1620280800 |    0 | 1620280818 |    0 | 1620280818 |    0 |  1440 
| 0 |   86400 |


| 1620367200 |    0 | 1620367203 |    1 | 1620433715 |    1 |  1440 
|    60 |   86400 |


| 1620453600 |    0 | 1620453615 |    0 | 1620453615 |    0 |  1439 
| 0 |   86340 |


| 162054 |    0 | 1620540003 |    0 | 1620540003 |    0 |  1438 
| 0 |   86280 |


| 1620626400 |    0 | 1620626417 |    1 | 1620668023 |    1 |  1440 
|    60 |   86400 |


| 1620712800 |    0 | 1620712813 |    1 | 1620724087 |    6 |  1404 
|   360 |   84240 |


| 1620799200 |    0 | 1620799219 |    0 | 1620799219 |    0 |  1369 
| 0 |   82140 |


| 1620885600 |    0 | 1620907460 |    0 | 1620907460 |    0 |   770 
| 0 |   56280 |


| 1620972000 |    0 | 1620972018 |    7 | 1621048320 |   43 |  1114 |  
2580 |   83160 |


| 1621058400 |    0 | 1621058403 |    2 | 1621123200 |   39 |  1425 |  
2340 |   85500 |


| 1621144800 |    0 | 1621144806 |    0 | 1621144806 |    0 |  1433 
| 0 |   85980 |


| 1621231200 |    0 | 1621231202 |    0 | 1621231202 |    0 |  1440 
| 0 |   86400 |


| 1621317600 |    0 | 1621317609 |    1 | 1621382991 |    1 |  1432

[weewx-user] Compatibiliy of WS980 WIFI weather station [2]

2021-07-25 Thread Rainer Lang


It can be used by weewx with the Interceptor driver.
https://github.com/matthewwall/weewx-interceptor
The custom server option of the station (it's a Ecowitt WS2320E/WS2350 
clone) will be used to send in Ecowitt protocoll to the server (e.g. a RPi).

helpful link: https://www.wxforum.net/index.php?topic=40730.0
I use the same station with weewx
in the weewx.conf in the Interceptor section you need to have the below 
entries

##

[Interceptor]
    # This section is for the network traffic interceptor driver.

    # The driver to use:
    driver = user.interceptor

    # Specify the hardware device to capture.  Options include:
    #   acurite-bridge - acurite internet bridge, smarthub, or access
    #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
    #   lw30x - oregon scientific LW301/LW302
    #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
    #   ecowitt-client - any hardware that uses the ecowitt protocol
    #   wu-client - any hardware that uses the weather underground protocol
    device_type = ecowitt-client
   port = 8000
    iface = eth0
# iface = wlan0 if you use a WLAN connection and no Ethernet


In the WSView app for customized server your entries should be: (tap on 
your device in the WSView device lsit)

protocol: Ecowitt
host: your server's IP
path: /   (there must be at least a "/" even though weewx doesn't care - 
but if there's no path, the station won't send)
port: 8000 (has to correspond to the weewx.conf entry, can be any port 
but should be a port which is not used by any other application on your 
server)

update interval: 16
press save and wait for the "success" message

that's it - Good luck
If you have more questions, you can PM me - also in German 😉

On 24.07.2021 22:01, webm...@luftfahrtverein-gruenstadt.de wrote:


Hi all,
during an EM special I bought a wifi weather station of type WS980WIFI 
(https://de.elv.com/elv-wifi-wetterstation-ws980wifi-inkl-funk-aussensensor-868-mhz-app-pc-auswertesoftware-250408)


Is there any way of using weewx with this station? There is the 
possibility of defining an "own" server when configuring the station 
where I can provide an IP, the protocol (Wunderground or ecowitt), 
ports, etc.
Also I found out that it uses the WS23xx protocol, for what an weewx 
extension exsists I think.


Thank you for your help!

Best,,
Sebastian


--
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/c41ea8a9-a08a-4b6f-8366-b26fe71c7cbfn%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/3dbcc544-febb-c367-f438-8b954fd34b77%40gmail.com.

[weewx-user] Re: Pulling my hair - one weird issue after the other [2]

2021-08-02 Thread Rainer Lang


On a RPi you have to add the following line to your weewx.conf
device_type = ecowitt-client
port = 8000

iface = eth0   #if you are using the Ethernet port
    #or
iface = wlan0 #if you are using the WiFi of the RPi
# only one of them 😉

you also have to make sure that no other application on the RPi uses 
port 8000


you can try 8001 or 8777 (on both ends - weewx.conf and WSView 
app/console) - maybe port 8000 is used 



On 02.08.2021 12:22, gjr80 wrote:
When you just ran the interceptor driver directly there should have 
been output to the console as well as log output in the WeeWX log, not 
sure what log file it will be in as I am not a Centos user. Can you 
please post the log output exactly as it appears in the log.


Gary

On Monday, 2 August 2021 at 19:17:12 UTC+10 Konrad Skeri Ekblad wrote:

I did a complete reinstallation of the server with Centos 8. Fresh
install of WeeWX from repository using yum as described on web
page. Installed interceptor driver according to set up instructions.
Running PYTHONPATH=/usr/share/weewx python3 user/interceptor.py
--debug --port=8000 --device=ecowitt-client for almost an hour
only gives the following output:

raw data:
raw packet: {'dateTime': 1627891880, 'usUnits': 1}
mapped packet: {'dateTime': 1627891880, 'usUnits': 1}

Using Wireshark to monitor the network traffic I notice this:
Weatherstation to WeeWX server:
POST  HTTP/1.1
HOST: 192.168.129.10
Connection: Close
Content-Type: application/x-www-form-urlencoded
Content-Length: 415

PASSKEY=**replaced**&stationtype=EasyWeatherV1.6.0&dateutc=2021-08-02+08:11:21&tempinf=77.5&humidityin=42&baromrelin=29.894&baromabsin=29.374&tempf=59.9&humidity=76&winddir=25&windspeedmph=2.7&windgustmph=3.4&maxdailygust=6.9&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.000&monthlyrainin=0.000&totalrainin=53.673&solarradiation=355.26&uv=3&model=WS2900

Response from WeeWX server:
http://www.w3.org/TR/html4/strict.dtd
">

    
        
        Error response
    
    
        Error response
        Error code: 400
        Message: Bad HTTP/0.9 request type ('POST').
        Error code explanation: HTTPStatus.BAD_REQUEST - Bad
request syntax or unsupported method.
    


According to WireShark there is this communication about once each
minute, but I have only one entry in the terminal.
onsdag 28 juli 2021 kl. 02:24:31 UTC+2 skrev gjr80:

You have changed many things in your setup and even though you
appear to have reverted to your original working configuration
I would be starting from scratch as per the interceptor drive
readme.I would be running the driver directly and then making
sure you use the —debug command line option. Post the console
output here. Let’s see where that gets us.

Gary
On Wednesday, 28 July 2021 at 08:20:26 UTC+10 Konrad Skeri
Ekblad wrote:

I have been using weewx on a Raspberry Pi for about two
years now. After my old Fine Offset died soon after I
moved from pywws I bought a Eurochron WS2900 which I got
running using the interceptor driver, and that worked fine
until the weather station stopped giving temperature
readings this winter. I was able to fix that last week
(bad connector on the cable from the temperature sensor to
the circuit board in the sensor array) but when I
reconnected it to weewx I started to experience various
odd things. The unit shows correct data on its display and
sends data to weewx, and the webpages rendered by weewx
are correct (e.g. temperature ranging between 16°C and
28°C the other day) but the temperatures sent to Windy
(and others) by weewx varies from -2°C to 21°C for the
same day. Thinking that there might be some API change or
something during the half year my station was offline, and
that I for some time have had thoughts of moving it to a
virtual server on my ESXi station anyway, I set up a
Centos 8 machine and installed weewx on it. Simulator
works fine, but using the same interceptor settings as on
my Raspberry Pi I don't get any data (IP updated in the
weather station settings).

Using
PYTHONPATH=/usr/share/weewx python3 -m user.interceptor
--debug --mode=listen --port=8000 --device=ecowitt-client
I was able to once capture this after listening maybe one
hour:
raw data:
raw packet: {'dateTime': 1627416663, 'usUnits': 1}
mapped packet: {'dateTime': 1627416663, 'usUnits': 1}
Yay! A timestamp!

Fwd: [weewx-user] Re: Pulling my hair - one weird issue after the other [3]

2021-08-02 Thread Rainer Lang

By mistake I sent this reply only to the OPer - now forward also to the 
group for information and documentation


It's a common mistake when using the custom server function of a Fine 
Offset (clone) console in ecowitt protocol

to leave the path entry in the WSView app empty.
Even though weewx (the interceptor driver) doesn't care about any path, 
the console still does.


If there is no entry at all, the console will not post !!!

Therefore at least "/" without "" has to be entered into the path field 
in the WSView app.


This is for weewx.

When posting via custom server function to a web site, the path has to 
be meaningful and point to the HTML or www root of the server 
respectively the path from there where the posting will be picked up 
e.g. by some index.php file.


The posting in Ecowitt protocol will always look like

http://IP-or-URL/path-from-wsview-app/index.php&PASSKEY=xx&stationtype= 
.


the interceptor driver filters out the PASSKEY, stationtype and other 
not observation related parts of the posted string and takes only the 
observation related portions e.g. windgustmph=5.82




 Forwarded Message 
Subject: 	[weewx-user] Re: Pulling my hair - one weird issue after the 
other [3]

Date:   Mon, 2 Aug 2021 16:05:30 +0200
From:   Rainer Lang 
To: Konrad Skeri Ekblad 



Did you enter a path in the WSView app ?
There must be at least a "/" - even though weewx doesn't care, the 
console does.

If there is no path entered, it doesn't post via the custom server function.

On 02.08.2021 14:55, Konrad Skeri Ekblad wrote:

Running WeeWX directly instead the output in /var/log/messages is this:

Aug  2 14:36:59 localhost systemd[1]: Starting SYSV: start and stop 
the weewx weather system...
Aug  2 14:36:59 localhost journal[2697]: weewx[2697] INFO __main__: 
Initializing weewx version 4.5.1
Aug  2 14:36:59 localhost journal[2697]: weewx[2697] INFO __main__: 
Using Python 3.6.8 (default, Mar 19 2021, 05:13:41) #012[GCC 8.4.1 
20200928 (Red Hat 8.4.1-1)]
Aug  2 14:36:59 localhost journal[2697]: weewx[2697] INFO __main__: 
Platform Linux-4.18.0-305.10.2.el8_4.x86_64-x86_64-with-centos-8.4.2105
Aug  2 14:36:59 localhost journal[2697]: weewx[2697] INFO __main__: 
Locale is 'sv_SE.UTF-8'
Aug  2 14:36:59 localhost journal[2697]: weewx[2697] INFO __main__: 
PID file is /var/run/weewx.pid
Aug  2 14:36:59 localhost journal[2701]: weewx[2701] INFO __main__: 
Using configuration file /etc/weewx/weewx.conf
Aug  2 14:36:59 localhost journal[2701]: weewx[2701] INFO __main__: 
Debug is 1

Aug  2 14:36:59 localhost weewx[2688]: Starting weewx: [     OK     ]
Aug  2 14:36:59 localhost journal[2701]: weewx[2701] INFO 
weewx.engine: Loading station type Interceptor (user.interceptor)
Aug  2 14:36:59 localhost systemd[1]: Started SYSV: start and stop the 
weewx weather system.
Aug  2 14:36:59 localhost journal[2701]: weewx[2701] INFO 
user.interceptor: driver version is 0.53
Aug  2 14:36:59 localhost journal[2701]: weewx[2701] INFO 
user.interceptor: device type: ecowitt-client
Aug  2 14:36:59 localhost journal[2701]: weewx[2701] INFO 
user.interceptor: mode is listen
Aug  2 14:36:59 localhost journal[2701]: weewx[2701] INFO 
user.interceptor: listen on :8000
Aug  2 14:36:59 localhost journal[2701]: weewx[2701] INFO 
user.interceptor: sensor map: {'pressure': 'pressure', 'barometer': 
'barometer', 'outHumidity': 'humidity_out', 'inHumidity': 
'humidity_in', 'outTemp': 'temperature_out', 'inTemp': 
'temperature_in', 'windSpeed': 'wind_speed', 'windGust': 'wind_gust', 
'windDir': 'wind_dir', 'windGustDir': 'wind_gust_dir', 'radiation': 
'solar_radiation', 'dewpoint': 'dewpoint', 'windchill': 'windchill', 
'rain': 'rain', 'rainRate': 'rain_rate', 'UV': 'uv', 
'txBatteryStatus': 'battery', 'extraTemp1': 'temperature_1', 
'extraTemp2': 'temperature_2', 'extraTemp3': 'temperature_3', 
'extraHumid1': 'humidity_1', 'extraHumid2': 'humidity_2', 'soilTemp1': 
'soil_temperature_1', 'soilTemp2': 'soil_temperature_2', 'soilMoist1': 
'soil_moisture_1', 'soilMoist2': 'soil_moisture_2', 'soilMoist3': 
'soil_moisture_3', 'soilMoist4': 'soil_moisture_4', 'leafWet1': 
'leafwetness_1', 'leafWet2': 'leafwetness_2', 'pm2_5': 'pm2_5', 
'extraTemp4': 'temperature_4', 'extraTemp5': 'temperature_5&

Fwd: [weewx-user] Re: Pulling my hair - one weird issue after the other [4]

2021-08-03 Thread Rainer Lang

 Forwarded Message 
Subject: 	[weewx-user] Re: Pulling my hair - one weird issue after the 
other [4]

Date:   Tue, 3 Aug 2021 14:28:28 +0200
From:   Rainer Lang 
To: Konrad Skeri Ekblad 

I think this side effect is due to a recent change of Interceptor.py to 
show also the hardware name in the "about this weather station" section 
- the change fell somewhat too short. I had already been searching 
myself for a solution, but gave up due to lack of time and decided to 
bear with this message before every archiving cycle.

If you want to get rid of this log message, you would have to walk 
through the Interceptor.py coding and add some additional filtering.
Without that hardware name change the PASSKEY info was filtered out. Now 
the program flow is different.
It will probably have to be filtered out a 2nd time or only at some 
other place now.

On 03.08.2021 10:55, Konrad Skeri Ekblad wrote:
Actually, the console tries to post even without a path entered, it 
just doesn't specify a request-URI in the HTTP POST header causing an 
error 400 on the server side.
I never changed the path setting from when it was working, so it must 
have been a side effect from a firmware update done during the months 
my WeeWX was down. Good thing to know for people having the same 
trouble in the future. I also changed the path from /path? as 
suggested in the GitHub discussion I found to just / and that works as 
well. However, in both cases I get the following line in the message 
log every time the station sends an update:

Aug  3 10:51:33 localhost journal[2825]: weewx[2825] INFO 
user.interceptor: unrecognized parameter b'PASSKEY=9879…

While not interfering with function it clutters up the log making it 
harder to read. Guess that's a topic for the GitHub issue tracker though.

Konrad

tisdag 3 augusti 2021 kl. 01:35:43 UTC+2 skrev lang@googlemail.com:

By mistake I sent this reply only to the OPer - now forward also
to the group for information and documentation

It's a common mistake when using the custom server function of a
Fine Offset (clone) console in ecowitt protocol
to leave the path entry in the WSView app empty.
Even though weewx (the interceptor driver) doesn't care about any
path, the console still does.

If there is no entry at all, the console will not post !!!

Therefore at least "/" without "" has to be entered into the path
field in the WSView app.

This is for weewx.

When posting via custom server function to a web site, the path
has to be meaningful and point to the HTML or www root of the
server respectively the path from there where the posting will be
picked up e.g. by some index.php file.

The posting in Ecowitt protocol will always look like

http://IP-or-URL/path-from-wsview-app/index.php&PASSKEY=xx&stationtype=

<http://IP-or-URL/path-from-wsview-app/index.php&PASSKEY=xx&stationtype=>
.

the interceptor driver filters out the PASSKEY, stationtype and
other not observation related parts of the posted string and takes
only the observation related portions e.g. windgustmph=5.82

 Forwarded Message 
Subject:[weewx-user] Re: Pulling my hair - one weird issue after
the other [3]
Date:   Mon, 2 Aug 2021 16:05:30 +0200
From:   Rainer Lang 
To: Konrad Skeri Ekblad 

Did you enter a path in the WSView app ?
There must be at least a "/" - even though weewx doesn't care, the
console does.
If there is no path entered, it doesn't post via the custom server
function.

On 02.08.2021 14:55, Konrad Skeri Ekblad wrote:

Running WeeWX directly instead the output in /var/log/messages is
this:

Aug  2 14:36:59 localhost systemd[1]: Starting SYSV: start and
stop the weewx weather system...
Aug  2 14:36:59 localhost journal[2697]: weewx[2697] INFO
__main__: Initializing weewx version 4.5.1
Aug  2 14:36:59 localhost journal[2697]: weewx[2697] INFO
__main__: Using Python 3.6.8 (default, Mar 19 2021, 05:13:41)
#012[GCC 8.4.1 20200928 (Red Hat 8.4.1-1)]
Aug  2 14:36:59 localhost journal[2697]: weewx[2697] INFO
__main__: Platform
Linux-4.18.0-305.10.2.el8_4.x86_64-x86_64-with-centos-8.4.2105
Aug  2 14:36:59 localhost journal[2697]: weewx[2697] INFO
__main__: Locale is 'sv_SE.UTF-8'
Aug  2 14:36:59 localhost journal[2697]: weewx[2697] INFO
__main__: PID file is /var/run/weewx.pid
Aug  2 14:36:59 localhost journal[2701]: weewx[2701] INFO
__main__: Using configuration file /etc/weewx/weewx.conf
Aug  2 14:36:59 localhost journal[2701]: weewx[2701] INFO
__main__: Debug is 1
Aug  2 14:36:59 localhost weewx[2688]: Starting weewx: [     OK     ]
Aug  2 14:36:59 localhost journal[2701]: weewx[2701] INFO

[weewx-user] Newbie Here - Need help with display [2]

2021-08-04 Thread Rainer Lang


On 03.08.2021 22:57, Clifford Snow wrote:
Hi Clifford, see below inline

I have weewx working. I can see reports for all my devices except for 
the EcoWitt WH0290 air quality monitor. Plus I'm getting empty reports 
on devices I don't have such as wind speed, direction and rain 
measurements.


First how do I remove the charts for devices I currently don't have. 
(At some point in the future when the budget allows, I'll be 
purchasing more devices.)
Assuming you are using the Seasons skin, the pictures are defined in 
skin.conf (where you can comment out the ones you don't want) and the 
display of the picture on the skin (WebUI) is defined in index.html.tmpl 
- here, too, you can comment out the lines for the display you don't want
(both files in the /etc/weewx/skins/Seasons directory - if you installed 
weewx with the setup.py method, the path will be different - see weewx 
documentation)


Second, I have the EcoWitt WH0290 air quality device configured on my 
GW1000 device. However, I'm not seeing any graphs. How do I add those 
reports. The EcoWitt site does report air quality numbers so I know 
the device is working.
The WH0290 cannot be configured in the GW1000. What can be configured is 
the WH41 or WH43 PM2.5 sensor.
(this may sound like splitting hairs, but the WH0290 is a minimalistic 
console and not a sensor).


The GW1000 should recognize the WH41/43 - and the weewx database field 
name is pm2_5



in weewx.conf in the

[StdReport]
  [[Default]]
 [[[Labels]]]
    Generic  # stanza you can give it a name e.g. PM2.5 
indoor or PM2.5 outdoor

 ..
 inTemp = Inside Temperature
 outHumidity = outside Humidity
 .
 pm2_5 = PM2.5 indoor


in skin.conf you will have to add under

[ImageGenerator]
 [[day_image]]
..
 [[[daytempdew]]]
    outTemp
    dewpoint
..
  [[[daypm25]]]i
 yscale = None, None, 0.5
  pm2_5

you will also have to add entries for

[[week_image]]

  [[[weekpm25]]]
 yscale = None, None, 0.5
 pm2_5
 .

[[month_image]]

[[year_image]]

-

in index.html.tmpl you will have to add



    #if $day.inTemp.has_data
    
    #end if
    #if $day.inHumidity.has_data
    
    #end if


    #if $day.pm2_5.has_data or $day.pm1_0.has_data
    
    #end if



similarly for week, month and year

Good luck and have fun !



Thanks in advance and thanks to the developers for a fun project.
Clifford
--
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/25cc1d1d-519c-48d3-b02b-3d27bee703a2n%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/c192748e-6e68-7a02-2e84-55bd4e54929b%40gmail.com.

[weewx-user] Re: Ambient WS-2000 Clarification

2021-09-05 Thread Rainer Lang

The WS-2000 with its outdoor array only is supported by the weewx
Interceptor driver (and the console custom server feature for WU protocol).
However, when it comes to more and extra sensors like WH31-type,
lightning, PM2.5, Soil Moisture etc.,
the interceptor driver will not process this info neither will the
console send it.
Then the simplest, cheapest and most reliable way is to get yourself an
Ecowitt GW1000/GW1100 (915 MHz) and have weewx read the data from there
via the GW1000 API driver.

On 05.09.2021 19:48, Bill Arthur wrote:
The Ambient Weather WS-2000 is manufactured by Fine Offset, as is the
GW1100 (available on Amazon)
There may be ways to use the WS-2000 without a GW-1100, but I doubt it
would be worth the effort.
The GW1000/GW1100 driver for WeeWx is so utterly reliable it makes the
$35 investment the best money spent.

On Sunday, September 5, 2021 at 12:37:04 PM UTC-5 vince wrote:

A quick google search pointed me to (this
)
link on wxforum.net saying the weewx-sdr
driver (link) will
work, but you'll need the antenna and receiver dongle for that.

My setup (link )
from this time last year is no longer available it seems, but it
cost about $35 when I bought mine a while back and worked great
with weewx in quick testing. There are lots of similar ones in
the $ 40-45 range with one example (here

)
but I don't know if there are particular models that are good or
bad these days.

On Sunday, September 5, 2021 at 8:35:56 AM UTC-7
mysqls...@gmail.com wrote:

Hi,
I have an Ambient Weather WS-2000 and understand it's not
well-supported, if at all. Are there simple docs available
that explain
the setup process?

I've seen references in the archive to a "GW1000" and the
"Fine Offset"
sensors, but don't fully understand what that all means.

Is it necessary to purchase additional equipment to make the
WS-2000
work properly? Is there a firmware update involved?

Thanks,
Alex

--
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/e1ab5c82-8021-43a5-97a2-5efd7ed67166n%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/2c034d1f-20f2-49cb-9e3c-427504784077%40gmail.com.

[weewx-user] Re: weewx and apache WS [2]

2021-09-07 Thread Rainer Lang



weewx puts the index.html and related include files (*.inc) and pictures 
into the directory which is defined in weewx.conf by HTML_ROOT=

in the [StdReport] section
If weewx is installed on the same server as apache2, the default 
directory would be /var/www/html/weewx where the apache web server
would pick up the index.html when requested by a http(s) call - e.g. 
http://URL/weewx or http://IP-address/weewx
(depending on your weewx installation method the paths maybe be 
different from the above example - see weewx installation guide)


If your web site is different from the weewx server, some web server 
(e.g. apache2) will have to run on this web site and it will also have a 
HTML root directory, often /www/... or /public_html/...


If you create a directory under your web server root directory (not the 
server root but the web server root !) e.g. ./weewx, you have to copy 
the files generated by weewx into the local HTML_ROOT/weewx directory 
into the remote web site server's directory e.g. /public_html/weewx

this could than be read by a browser with http://your-web-site-URL/weewx

Usually this is done via FTP. You can use the [[FTP]] section in 
[StdReport] of weewx.conf to post/copy/upload (all synonyms here) to 
your web site

see below
at each archiving cycle (default 300 seconds = 5 min) the files for e.g. 
the Seasons skin will then be sent to your web site

(provided you use the Seasons skin)
the [[FTP]] either uses as source the default HTML_ROOT directly under 
[StdReport]] or an extra HTML_ROOT which you define in the [[FTP]] stanza.


# excerpt from weewx.conf start **
[StdReport]
    # Where the skins reside, relative to WEEWX_ROOT
    SKIN_ROOT = /etc/weewx/skins

    # Where the generated reports should go, relative to WEEWX_ROOT
    HTML_ROOT = your-default-html-root-on-your-weewx-server

    # The database binding indicates which data should be used in reports.
    data_binding = wx_binding

    # Whether to log a successful operation
    log_success = True

    # Whether to log an unsuccessful operation
    log_failure = True

    # Each of the following subsections defines a report that will be run.
    # See the customizing guide to change the units, plot types and line
    # colors, modify the fonts, display additional sensor data, and other
    # customizations. Many of those changes can be made here by overriding
    # parameters, or by modifying templates within the skin itself.

    [[SeasonsReport]]
    # The SeasonsReport uses the 'Seasons' skin, which contains the
    # images, templates and plots for the report.
    skin = Seasons
    enable = true
# .
# .

[[FTP]]
    # FTP'ing the results to a webserver is treated as just another 
report,

    # albeit one with an unusual report generator!
    skin = Ftp

    # If you wish to use FTP, set "enable" to "true", then
    # fill out the next four lines.
    # Use quotes around passwords to guard against parsing errors.

    enable = true
    user = your-(ftp)user-name at your web site
    password = your-password-at-your-web-site
    server =    # fhe ftp server name, e.g, www.myserver.org
    path =    # The destination directory, e.g., /weather , or 
/weewx or /www/weewx depending on your hosting site


    # Set to True for an FTP over TLS (FTPS) connection. Not all 
servers

    # support this.
    secure_ftp = False

    # To upload files from something other than what HTML_ROOT is 
set directly under [StdReport]

    # to above, specify a different HTML_ROOT here.
    HTML_ROOT = 
your-html-root-on-your-weewx-server-from-where-you-want-to-upload-our 
files-to-your-web-site

    # e.g. /var/www/html/weewx
    # where the cheetah generator puts all the html, *.png etc. files

# excerpt from weewx.conf end **

On 07.09.2021 15:36, Eric Gammeter wrote:

WEEWX INDEX html page.

On Tuesday, September 7, 2021 at 9:35:54 AM UTC-4 Eric Gammeter wrote:

OK-  I would like to see my WEEWX HTML web page on my LAN-  not
have to go to the internet.  Thanks for your input Tom and Vince!
/Eric G.

On Thursday, September 2, 2021 at 7:51:39 AM UTC-4 t...@tom.org wrote:

In addition to using a web server on the same "machine"
(whether actual or virtual), one can also use secure FTP or
rsync via weewx.conf to have weewx stick the HTML in a
specific directory on an existing web server. I use this
technique ot use one web server and virtual hosts to serve
weewx HTML for five stations.

So, a couple of ways to do what it sounds like what you're
looking for, but as Vice says, it would be good to know more
about what you're looking to do.

On Wednesday, September 1, 2021 at 1:31:02 PM UTC-4 vince wrote:

Not understanding what you're asking, but

[weewx-user] Re: Multiple stations on one host [2]

2021-10-04 Thread Rainer Lang

You have probably not disabled the belchertown skin completely for the 
Cheetah Generator.


What you have to make sure with two (or more) instances on the same 
server is:


with two weewx instances on one and the same server you need two 
different weewx.conf

e.g. tempest.conf and 2ndstation.conf
and possibly also two different skin directories with a dedicated 
skin.conf (if both instances are using the same skin - one instance can 
use different skins at the same time, but when two instances share the 
same skin.conf everything must be identical).


You will need to have a separate (sub-)directory for your html output 
(HTML_ROOT) for each instance (and each skin used by the instance) and 
you better have two separate directories for your databases (in case 
both use a database with the same name - or you rename one of them).


Your issue looks to me that you may have not thoroughly and consequently 
assigned different names (and paths/directories) to the HTML_ROOTs, 
database bindings,databases etc.


When both instances run properly on both servers, there's no reason why 
they shouldn't run properly together on one server.


I have separated in my installation the skins directory (i.e. created 
one for each instance - now each instance has its own, independent 
skin.conf for each skin it uses - e.g. /etc/weewx/inst1/skins and 
/etc/weewx/inst2/skins) and have the HTML_ROOT of each instance's 
weewx.conf point to there, and my databases carry the names of the 
instance in its name (even though that is not necessary if you separate 
them with directories, but with such a naming "convention" you sort of 
implicitly document where they belong to )


If in your use case both of your instances need a forecast.sdb then you 
have to rename at least one of them - or place them in a different 
directory) - if you include the name of your instance, it could be 
forecast-inst1.sdb and forecast-inst2.sdb and they can both remain/stay 
in /var/lib/weewx. Then it's also easy to tell who/what belongs to where.



On 04.10.2021 11:00, Chotechai Piyavongsiri wrote:
Even I disabled forecast from the bechertown skin (latest version), it 
still produces the error
Oct  4 15:53:05 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
weewx.manager: Daily summary version is 4.0
Oct  4 15:53:16 bthoven-AP34-PRO weewx-tempest[20798] INFO 
weewx.restx: MQTT: Published record 2021-10-04 15:53:12 +07 (167592)
Oct  4 15:55:16 bthoven-AP34-PRO weewx-tempest[20798] INFO 
weewx.restx: MQTT: Published record 2021-10-04 15:55:12 +07 (167712)
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] INFO 
weewx.restx: MQTT: Published record 2021-10-04 15:56:12 +07 (167772)
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] INFO 
weewx.manager: Added record 2021-10-04 15:55:00 +07 (167700) to 
database 'tempest.sdb'
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] INFO 
weewx.manager: Added record 2021-10-04 15:55:00 +07 (167700) to 
daily summary in 'tempest.sdb'
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
weewx.reportengine: Running reports for latest time in the database.
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
weewx.reportengine: Report 'SeasonsReport' not enabled. Skipping.
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
weewx.reportengine: Report 'SmartphoneReport' not enabled. Skipping.
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
weewx.reportengine: Report 'MobileReport' not enabled. Skipping.
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
weewx.reportengine: Report 'StandardReport' not enabled. Skipping.
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
weewx.reportengine: Running report 'Belchertown'
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
weewx.reportengine: Found configuration file 
/etc/weewx/skins/Belchertown/skin.conf for report 'Belchertown'
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] INFO 
weewx.restx: MQTT: Published record 2021-10-04 15:55:00 +07 (167700)
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
weewx.cheetahgenerator: Using search list 
['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
'weewx.cheetahgenerator.JSONHelpers', u'user.belchertown.getData']
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
weewx.manager: Daily summary version is 4.0
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] ERROR 
weewx.reportengine: Caught unrecoverable exception in generator 
'weewx.cheetahgenerator.CheetahGenerator'
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] ERROR 
weewx.reportengine:           No JSON object could be decoded
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] ERROR 
weewx.reportengine:           Traceback (most recent call last):
Oct  4 15:56:16 bthoven-AP34-PRO

[weewx-user] Re: Multiple stations on one host [3]

2021-10-05 Thread Rainer Lang

When both your instances have/use identical skin.conf, index.html.tmpl 
etc. settings for the Belchertown skin, they don't need to be separated. 
But if you want to "individualize" the skins for each instance, then 
each one would need their own one.


On 05.10.2021 05:15, Chotechai Piyavongsiri wrote:

Thank you for your detailed explanation.

I have two configs (weewx.conf, tempest.conf), two separated database 
(weewx.sdb, tempest.sdb) in /var/lib/weewx, two separated HTML roots 
(/var/html/weewx, var/html/tempest). I saw the second instance write 
somethings in the /var/html/tempest directory; but not completed 
because of errors along the process. However I have only one 
forecast.sdb. Could you tell me more how to identify a specific 
forecast_tempest.sdb in the weewx config?


For belchertown skin, I'm not sure why we need two separated skins 
because I understand that both instances are supposed to "read" the 
skin only?


On Monday, 4 October 2021 at 17:39:24 UTC+7 lang@googlemail.com wrote:

You have probably not disabled the belchertown skin completely for
the Cheetah Generator.

What you have to make sure with two (or more) instances on the
same server is:

with two weewx instances on one and the same server you need two
different weewx.conf
e.g. tempest.conf and 2ndstation.conf
and possibly also two different skin directories with a dedicated
skin.conf (if both instances are using the same skin - one
instance can use different skins at the same time, but when two
instances share the same skin.conf everything must be identical).

You will need to have a separate (sub-)directory for your html
output (HTML_ROOT) for each instance (and each skin used by the
instance) and you better have two separate directories for your
databases (in case both use a database with the same name - or you
rename one of them).

Your issue looks to me that you may have not thoroughly and
consequently assigned different names (and paths/directories) to
the HTML_ROOTs, database bindings,databases etc.

When both instances run properly on both servers, there's no
reason why they shouldn't run properly together on one server.

I have separated in my installation the skins directory (i.e.
created one for each instance - now each instance has its own,
independent skin.conf for each skin it uses - e.g.
/etc/weewx/inst1/skins and /etc/weewx/inst2/skins) and have the
HTML_ROOT of each instance's weewx.conf point to there, and my
databases carry the names of the instance in its name (even though
that is not necessary if you separate them with directories, but
with such a naming "convention" you sort of implicitly document
where they belong to )

If in your use case both of your instances need a forecast.sdb
then you have to rename at least one of them - or place them in a
different directory) - if you include the name of your instance,
it could be forecast-inst1.sdb and forecast-inst2.sdb and they can
both remain/stay in /var/lib/weewx. Then it's also easy to tell
who/what belongs to where.


On 04.10.2021 11:00, Chotechai Piyavongsiri wrote:

Even I disabled forecast from the bechertown skin (latest
version), it still produces the error
Oct  4 15:53:05 bthoven-AP34-PRO weewx-tempest[20798] DEBUG
weewx.manager: Daily summary version is 4.0
Oct  4 15:53:16 bthoven-AP34-PRO weewx-tempest[20798] INFO
weewx.restx: MQTT: Published record 2021-10-04 15:53:12 +07
(167592)
Oct  4 15:55:16 bthoven-AP34-PRO weewx-tempest[20798] INFO
weewx.restx: MQTT: Published record 2021-10-04 15:55:12 +07
(167712)
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] INFO
weewx.restx: MQTT: Published record 2021-10-04 15:56:12 +07
(167772)
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] INFO
weewx.manager: Added record 2021-10-04 15:55:00 +07 (167700)
to database 'tempest.sdb'
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] INFO
weewx.manager: Added record 2021-10-04 15:55:00 +07 (167700)
to daily summary in 'tempest.sdb'
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG
weewx.reportengine: Running reports for latest time in the database.
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG
weewx.reportengine: Report 'SeasonsReport' not enabled. Skipping.
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG
weewx.reportengine: Report 'SmartphoneReport' not enabled. Skipping.
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG
weewx.reportengine: Report 'MobileReport' not enabled. Skipping.
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG
weewx.reportengine: Report 'StandardReport' not enabled. Skipping.
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG
weewx.reportengine: Running report 'Belchertow

[weewx-user] rain rate is 0 [2]

2021-11-02 Thread Rainer Lang


Could you please provide the following information
1. which Froggit model are you using
2. which weewx driver are you using
3. set debug = 3 in weewx.conf and restart weewx,
then provide the complete (!) syslog from the weewx start until at least 
the first archiving interval (usually 300 seconds = 5 minutes) - if you 
have passwords shown in the log you can overwrite them with 


then we could have some idea what your situation is.
Thanks

On 01.11.2021 19:50, hajsek...@gmail.com wrote:
I use weewx 4.5.1 and all work until I have changed my weather 
station, because some sensors goes bad.  now I have froggit weather 
station and rain rate is all the time 0.

I  think there must be something in settings. Any idea?
--
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/3a6a9ee7-7e9e-4a82-a595-932f561e9fe3n%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/5599b853-2e27-c229-27d5-fa88209721bc%40gmail.com.

[weewx-user] Apache2 webserver [2]

2021-11-18 Thread Rainer Lang

Did you create a symbolic link redirecting the Apache default web folder
to yours ?

And did you allow Apache to access your report folder ?

1. Create symbolic link to point webserver to the reports
1. *sudo ln -s /var/weewx/reports /var/www/html/weewx*
2. Give the web server the ability to read from the directory
1. *sudo chmod -R 755 /var/www/html/weewx*

Did you define the HTML_ROOT for your reports properly in weewx.conf in
the [StdReport] section ?

*HTML_ROOT = /var/weewx/reports*

On 18.11.2021 10:34, Samuel Kirby-Bray wrote:

Hello,

Just installed weewx 4.5.1 on Rpi with bullseye and working fine - I
can see the reports. I installed Apache web-server following the
instructions and can now see its landing page. However the reports
don't seem to be saving to the correct folder:
file:///var/weewx/reports/index.html. Whereas the apache index page is
here: /var/www/html

I can link the reports on the browser but would like to setup the
website for external viewing. Its worked fine before, so not sure what
i'm doing wrong. Do I need to configure something in the config file
to sort this? Apologies for the novice Q!

Any ideas?
--
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/1157f3cb-05af-4200-b57c-75ed0bd78c64n%40googlegroups.com
.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/e001c812-bff7-315e-09a0-582d89e6fbbc%40gmail.com.

Re: [weewx-user] Hardware Interface needed? Really???

2021-12-01 Thread Rainer Lang


Hi Ralf
the Ventus W830 is a clone of the Ecowitt WH2910C console/station and 
weewx supports it via the interceptor driver.
Have a look at 
https://www.wxforum.net/index.php?topic=40730.msg417956#msg417956

and
https://www.wetterstationsforum.info/wiki/doku.php?id=wiki:wetterstationen:ecowitt-stationen
resp.
https://www.pc-wetterstation.de/forum/viewtopic.php?f=26&t=10333

You need to configure the custom server function of the console in WS 
View, install the weewx interceptor driver from GitHuband make sure, 
your weewx.conf has the following entries:
(make sure that in WS View custom server the server entry has NO http:// 
or https:// - just the domain name or IP address, and that the path 
entry is at least "/" - no entry there = no transmission by the console)

e.g.
# WS View custom server configuratio ---
server/IP: 192.168.1.77
path: /
port: 8000  (must be the same as in weewx.conf [Interceptor] section)
interval: 16

# start of weewx.conf excerpt 
[Interceptor]
    # This section is for the network traffic interceptor driver.

    # The driver to use:
    driver = user.interceptor

    # Specify the hardware device to capture.  Options include:
    #   acurite-bridge - acurite internet bridge, smarthub, or access
    #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
    #   lw30x - oregon scientific LW301/LW302
    #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
    #   ecowitt-client - any hardware that uses the ecowitt protocol
    #   wu-client - any hardware that uses the weather underground protocol
    device_type = ecowitt-client  # don't choose "observer" for the 
modern WiFi Ecowitt/Ambient stations

    port = 8000   #same as chosen in WS View
    iface = eth0   # or iface = wlan0 if you use a WLAN interface ("WiFi")
#- end of weewx.conf excerpt ---
any more questions, send me a PM
cheers
Rainer

On 01.12.2021 09:31, 'Ralf Jahns' via weewx-user wrote:


Hello,

I looked through the documentation but couldn't find much about how to 
connect the weather station to weewx.


I own a weather station, that exactly looks like a FineOffset but has 
no USB (it is a Ventus W830).
I'm sursprised, that it seems to be the usual way, to use a hardware 
connection to the weather station.


On my station, I can configure to send the data to e.g. weather 
underground but also to a specific URL/IP. So I filled in the IP of a 
local computer and looked with netcat (or so) and received a data 
record in clear text with all the current weather data. I hoped it 
would be possible to use this kind of interface with weewx. (The 
netcat test only works once after connection is established, probably 
the weather stations requires some kind of protocol.)


So, is it possible to connect my weather station to weewx by network 
socket interface?


Regards
Ralf
--
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/267b418e-760f-4452-a1cb-4b96092d270en%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/894b2004-68df-6335-7758-d6e8b3b6618c%40gmail.com.

[weewx-user] Hardware Interface needed? Really??? [2]

2021-12-01 Thread Rainer Lang


Forgot to add:
in WS View you have to choose "Ecowitt protocol" 😎
On 01.12.2021 10:23, Rainer Lang wrote:

Hi Ralf
the Ventus W830 is a clone of the Ecowitt WH2910C console/station and 
weewx supports it via the interceptor driver.
Have a look at 
https://www.wxforum.net/index.php?topic=40730.msg417956#msg417956

and
https://www.wetterstationsforum.info/wiki/doku.php?id=wiki:wetterstationen:ecowitt-stationen
resp.
https://www.pc-wetterstation.de/forum/viewtopic.php?f=26&t=10333

1. You need to configure the custom server function of the console in 
WS View,
(make sure that in WS View custom server the server entry has NO 
http:// or https:// - just the domain name or IP address, and that the 
path entry is at least "/" - no entry there = no transmission by the 
console)

e.g.
# WS View custom server configuration ---
server/IP: 192.168.1.77
path: /
port: 8000  (must be the same as in weewx.conf [Interceptor] section)
interval: 16


2. install the weewx interceptor driver from GitHub 
(https://github.com/matthewwall/weewx-interceptor) and make sure, your 
weewx.conf has the following entries:

# start of weewx.conf excerpt 
[Interceptor]
    # This section is for the network traffic interceptor driver.

    # The driver to use:
    driver = user.interceptor

    # Specify the hardware device to capture.  Options include:
    #   acurite-bridge - acurite internet bridge, smarthub, or access
    #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
    #   lw30x - oregon scientific LW301/LW302
    #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
    #   ecowitt-client - any hardware that uses the ecowitt protocol
    #   wu-client - any hardware that uses the weather underground 
protocol
    device_type = ecowitt-client  # don't choose "observer" for the 
modern WiFi Ecowitt/Ambient stations

    port = 8000   #same as chosen in WS View
    iface = eth0   # or iface = wlan0 if you use a WLAN interface ("WiFi")
#- end of weewx.conf excerpt ---
any more questions, send me a PM
cheers
Rainer

On 01.12.2021 09:31, 'Ralf Jahns' via weewx-user wrote:


Hello,

I looked through the documentation but couldn't find much about how 
to connect the weather station to weewx.


I own a weather station, that exactly looks like a FineOffset but has 
no USB (it is a Ventus W830).
I'm sursprised, that it seems to be the usual way, to use a hardware 
connection to the weather station.


On my station, I can configure to send the data to e.g. weather 
underground but also to a specific URL/IP. So I filled in the IP of a 
local computer and looked with netcat (or so) and received a data 
record in clear text with all the current weather data. I hoped it 
would be possible to use this kind of interface with weewx. (The 
netcat test only works once after connection is established, probably 
the weather stations requires some kind of protocol.)


So, is it possible to connect my weather station to weewx by network 
socket interface?


Regards
Ralf
--
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/267b418e-760f-4452-a1cb-4b96092d270en%40googlegroups.com 
<https://groups.google.com/d/msgid/weewx-user/267b418e-760f-4452-a1cb-4b96092d270en%40googlegroups.com?utm_medium=email&utm_source=footer>.





--
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/1cb5e34b-14ee-0f50-3420-4186c01a7b32%40gmail.com.

Re: [weewx-user] new install on RPi4 with PI OS

2021-12-02 Thread Rainer Lang


The "error" is not an error but a warning - and it just means what it says
that apt-key will no longer be used in linux installations but will/can 
be replaced

by trusted.gpd.d.
This will become effective 2022-April.

It has nothing to do with the weewx version you are installing (except 
for the instructions)


The documentation for weewx downloads should be updated accordingly.

On 02.12.2021 18:36, sali...@gmail.com wrote:

hi,
I am installing weewx on my RPi of test with PI OS, but I have this error
wget -qO - https://weewx.com/keys.html | sudo apt-key add -
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d 
instead (see apt-key(8)).

OK

an idea, I think install beta version 4.6.0b7

Patrick
--
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/15ecd586-261c-42c4-b94f-4713b559de0fn%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/c65d142e-770a-4d3e-2544-1c8928642058%40gmail.com.

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

2021-12-07 Thread Rainer Lang

If the installation is correctly done, just copying your weewx.sdb to 
the new folder (/var/lib/weewx) will do.
The corresponding entries have to be in weewx.conf in the 
[DatabaseTypes] section:

[DatabaseTypes]

    # Defaults for SQLite databases
    [[SQLite]]
    driver = weedb.sqlite
    # Directory in which the database files are located
    SQLITE_ROOT = /var/lib/weewx

Wenn die Installation nach Debian/Raspi Stil erfolgreich war, kann man 
getrost die weewx.sdb ins
/var/lib/weewx Verzeichnis kopieren - muss eben in weewx.conf in der 
[DatabaseTypes] Sektion

als SQLITE_ROOT so definiert sein

On 07.12.2021 12:11, Günther Wrana wrote:

Or do I just have to update my Raspberry for weewx?
Thank you Günther

Oder muss ich auf meinem Raspberry einfach nur ein Update für weewx 
durchführen?


Danke Günther

Günther Wrana schrieb am Dienstag, 7. Dezember 2021 um 12:00:35 UTC+1:

Hello Edwin, since I have installed weewx on my Raspberry
according to this system up to now WeeWX: Installation using
setup.py but now I would do this installation WeeWX: Installation
on Debian-based systems. Can I then simply copy my previous
database to this path / var / lib / weewx / after installation or
is that a problem? Thank you Günther


Hallo Edwin, da ich bis jetzt weewx auf meinem Raspberry nach
diesem System installiert habe WeeWX: Installation using setup.py
ich nun aber diese Installation durchführen würde WeeWX:
Installation on Debian-based systems.
Kann ich dann meine bisherige Datenbank einfach nach der
Installation auf diesen Pfad /var/lib/weewx/ kopieren oder ist das
ein Problem?
Danke Günther

EdwinZ schrieb am Sonntag, 5. Dezember 2021 um 17:30:41 UTC+1:

Hi Guenther, indeed I'm running the latest WeeWX (4.5.1) with
Python 3 (3.7) and my wh23xx replacement on my system. Note
that I made some minor documentation updates in my README
file, as I had to re-install my Raspberry Pi (corrupt SD card)
which is connected to the weather station.

On Wednesday, December 1, 2021 at 8:14:53 AM UTC+1
kawa...@gmail.com wrote:

Hi there, So you've updated weewx to version 4 and you're
running the program? Then I should try that with myself,
too. Until now I didn't dare to do it because I didn't
know if the whole thing would still work. Well then, thank
you. Greetings Günther Here is my website where the whole
thing is visible. www.guentherwrana.ddns.net/weewx



Hallo,

du hast also weewx auf die Version 4 upgedatet und das
Programm läuft bei dir? Dann sollte ich das ganz woll auch
bei mir versuchen. Den bis jetzt habe ich mir das nicht
getraut weil ich nicht wusste ob dann das ganze noch
funktioiert.

Na dann danke schön.
Grüße Günther

Hier meine Webseite wo das ganze sichtbar ist.
www.guentherwrana.ddns.net/weewx


EdwinZ schrieb am Donnerstag, 4. November 2021 um 18:20:56
UTC+1:

Not sure if this helps you, but I ported the Python 2
wh23xx module to Python 3:
https://github.com/EdwinGH/weewx-wh23xx
I'm using it on RPi Model 3 with Renkforce WH2315
weather station.

Edwin
On Thursday, May 6, 2021 at 9:55:51 AM UTC+2
kawa...@gmail.com wrote:

Hi Guys!
I just wanted to ask if there are already drivers
that work under Python3 for small groups of users
of this weather station?
My weather station under Python 2 with weewx 3.9.2
works and everything is fine. I would only be
interested in whether there is someone who tries
to get this data from the weather station under
weewx 4.5.1.
Or I have to come to terms with the fact that
version 3.9.2 will remain.

 I thank you and wish you a nice day.
Günther


Hallo Leute!

Ich wollte nur einmal nachfragen ob es schon
Treiber die unter Python3 funktionieren für kleine
Gruppe der User dieser Wetterstation gibt?
Meine Wetterstation unter Python 2 mit weewx 
3.9.2 funktioniert und alles ist gut.
Nur würde mich interessieren ob es jemanden gibt
der es versucht diese Daten auch unter weewx 4.5.1
aus Wetterstation zu holen.
Oder ich mich damit abfinden muss das es bei der

Re: [weewx-user] Re: Recommends for new station under 300

2022-08-25 Thread Rainer Lang

The HP25x0 consoles do not have an API and cannot be queried via the 
GW1000 API/Ecowitt Gateway driver.
You either use a GW1x00/GW2000 instead (receive the same sensors in 
parallel) with the Ecowtt Gateway (GW1000) driver,
or you will have to use the weewx Interceptor driver with the HP25x0 
console custom server functionality
The interceptor driver as available on GitHub from M. Wall covers only 
the basic sensors (T/H indoor, outdoor, rain, wind, solar).
If you have more sensors, you need to use a modified interceptor driver. 
Some users here have developed an extended version which covers all 
recent Ecowitt sensors.

The communiation from HP25x0 and GWyx00 console goes via WiFi into the 
local LAN.
Weewx will pick up the data via local LAN (LAN or WLAN) depending on the 
server on which weewx runs and its network interfaces.

There is no USB connection between consoles and weewx
The USB port on the GW1x00 consoles/gateways is for power supply only. 
The USB port of the HP25x0 consoles is for factory use initial device 
firmware only.

On 25.08.2022 19:00, ewhain...@gmail.com wrote:
The IS a USB port on the drawing. I found the manual here: 
https://www.ecowitt.com/shop/goodsDetail/1#

Manual & Software tab, Page 7 in the manual, however it also states it 
is for firmware updates only...

On Thursday, August 25, 2022 at 9:55:10 AM UTC-4 axelle@gmail.com 
wrote:

>The GW1100 is included with a number of display-less stations. As I
>understand it, there's a local API and the driver is just talking to
>that API and injecting to weewx.

Right. And the GW1100 is plugged by USB to the weewx server,
right? or can weewx read GW1100 over wifi?

>it looks like there is the equivalent of the GW1100 inside the
console,
>because it says it uploads to similar places

I have the feeling the protocol will be the same too. Same reason
as you.

The main issue that might occur is whether weewx GW1000 driver is
able to operate via wifi too or not? Looks like the HP2551 console
does not have a USB port (not sure though, couldn't find a photo).
And I wasn't able to find any info on Wifi connection on
https://github.com/gjr80/weewx-gw1000 nor about support for HP2551
or HP2552 or HP2553.

Anybody from GW1000 driver can answer?

Thanks,
On Thursday, August 25, 2022 at 12:38:46 PM UTC+2 Greg Troxel wrote:

Invisible Man  writes:

> I'm considering the purchase of a EcoWitt HP2551 : it has a
console + a
> 7-in-1 sensor. Just not totally sure how to integrate it
with Weewx.
> People said here to use the Ecowitt GW-1100 driver, right?
But EcoWitt
> HP2551 does not have that GW1100 gateway. Will the driver work
> nevertheless?
> Basically, I'm not sure the EcoWitt HP2551 (or 2552, or
2553) has a USB
> cable. So how would I connect it to the RPi on which Weewx
runs?

I am unclear on details but am heading down the path of
figuring out
which EcoWitt station someone else should get. I lean to EcoWitt
because it seems to be reasonable quality at very low prices
and they
seem to be open-source and local-access no-cloud-required
friendly. So
many things are cloud-only which I consider a total fail -- the
interceptor driver is an impressive hack but it's a bad
situation that
it's necesary.

The GW1100 is included with a number of display-less stations.
As I
understand it, there's a local API and the driver is just
talking to
that API and injecting to weewx. Thus it should work if the
internet is
down (or if the GW1100 is firewalled to keep the data from
being sent to
their cloud), but I'm not 100% sure as sometimes devices have
code that
phones home and stops if that doesn't work.

Reading

https://shop.ecowitt.com/products/hp2551

it looks like there is the equivalent of the GW1100 inside the
console,
because it says it uploads to similar places, and there is a
list of
optional sensors that seems to match. It would be sane to
offer the
same API and for them to reuse their code and circuit design,
just
sharing the case/etc. -- and doing so would be consistent with my
impression of EcoWitt's approach.

However, skimming the driver github site I don't see direct
confirmation
that the HP2551 is wire-protocol compatible. With any luck
someone will
post that they've used the driver.

--
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 
http

Re: [weewx-user] Re: Recommends for new station under 300

2022-08-26 Thread Rainer Lang

the Ecowitt Gateway driver works on a pull procedure, i.e. requests the 
data from the GWyx00 console, whereas the interceptor driver works with 
data pushed by the console via the custom server functionality.
In both cases the consoles communicate via WiFi/WLAN into the local 
network, and weewx requests/pulls (GW1000 API) or  catches (interceptor) 
via the network. (in case of a GW2000 this can be completely LAN based 
without WLAN).
For the Ecowitt Gateway driver the IP of the console is entered into 
weewx.conf [GW1000]
for the interceptor driver the IP of the weewx server is entered into 
the console for the custom server.


the interceptor doesn't need to be "placed" somewhere - that's a strange 
wording imho. It's just installed with weewx.
If you want to see a picture how this works - and get also some more 
understanding of your EW console hardware,
read through https://www.wxforum.net/index.php?topic=40730.0 (chapter 7. 
data flow, but all chapters are worth reading)


On 26.08.2022 09:12, Invisible Man wrote:

From the GW-1000 weewx driver README.md, I read:
"/The Ecowitt Gateway driver utilises the Ecowitt LAN/Wi-Fi Gateway 
API thus using a pull methodology for obtaining data from the gateway 
device rather than the push methodology used by other drivers/".


So, if I understand correctly, the GWyx00 does not talk to the 
Weewx.*It's the other way round: the Weewx communicates with the 
GWyx00 gateway*. I suppose we configure in the weewx driver the IP 
address of the GWxy00 and it questions it to get weather data.


Later the README.md says:
"/Note: If necessary you can specify the device IP address and port 
using the --ip-address and --port command line options./"


Not sure whether this is the IP address of the GWyx00 console, or the 
IP address of the Weewx host. The former, I think.


If so, that answers the second question of my previous post :)

On Friday, August 26, 2022 at 8:49:20 AM UTC+2 Invisible Man wrote:

Woaw, thanks this is extremely helpful!

The *interceptor* driver
(https://github.com/matthewwall/weewx-interceptor) looks cool.
Except that /I suppose the interceptor needs to be placed where it
can read all wifi packets/ (from the wifi the weather station
uses), right?
That's not very convenient in my case because the WiFi is created
by the Internet box. The Internet box is from my ISP. I don't have
any control on it, /can't install a weewx driver on it/ for
instance ;-)
Or can the interceptor be placed on *any machine on the same wifi
as the weather station* ?

So, let's investigate the option where I get a *GWyx00* console:

>The communiation from HP25x0 and GWyx00 console goes via WiFi
into the local LAN.

Ok, so you said that the USB connector on the GWyx00 console was
for power only. Then, the data from GWyx00 is emitted on WiFi.
My weewx host (a Rapsberry Pi) is on the LAN. They can ping each
other and communicate if they wish, no problem.
But will the GWyx00 directly send data to the weewx host: is that
configurable? /Can I configure the GWxy00 console to communicate
with a given IP address?/ I fear that the GWyx00 console will
rather directly send its data to an external Internet weather
server. Then, same issue, my weewx host can't "intercept" the data.

Thanks very much for your help!
On Thursday, August 25, 2022 at 7:10:33 PM UTC+2
lang@googlemail.com wrote:

The HP25x0 consoles do not have an API and cannot be queried
via the GW1000 API/Ecowitt Gateway driver.
You either use a GW1x00/GW2000 instead (receive the same
sensors in parallel) with the Ecowtt Gateway (GW1000) driver,
or you will have to use the weewx Interceptor driver with the
HP25x0 console custom server functionality
The interceptor driver as available on GitHub from M. Wall
covers only the basic sensors (T/H indoor, outdoor, rain,
wind, solar).
If you have more sensors, you need to use a modified
interceptor driver. Some users here have developed an extended
version which covers all recent Ecowitt sensors.

The communiation from HP25x0 and GWyx00 console goes via WiFi
into the local LAN.
Weewx will pick up the data via local LAN (LAN or WLAN)
depending on the server on which weewx runs and its network
interfaces.

There is no USB connection between consoles and weewx
The USB port on the GW1x00 consoles/gateways is for power
supply only. The USB port of the HP25x0 consoles is for
factory use initial device firmware only.

On 25.08.2022 19:00, ewhain...@gmail.com wrote:

The IS a USB port on the drawing. I found the manual here:
https://www.ecowitt.com/shop/goodsDetail/1#

Manual & Software tab, Page 7 in the manual, however it also
states it is for firmware updates only...

On T

Re: [weewx-user] Re: Recommends for new station under 300

2022-08-27 Thread Rainer Lang

1. the GW1000, GW1100, WH2650, GW2000, WN19x0 consoles all share the
same APi - the Ecowitt Gateway API aka GW1000 API
the Wittboy = GW2001 station = GW2000 console/gateway + WS90 7-in-1
sensor array
The WS90 outdoor array can be connected to any of the above mentioned
consoles with Ecowitt Gateway API (latest firmware needed)

The haptic rain sensor of the WS90 can be calibrated on five tiers
depending on rain rate.
It has also already undergone several firmware updates to fix issues of
rain rate, rain+wind, dew, non-rainfall "touches" etc. and its accuracy
is growing.
In my case the WS90 readings are between a WH40 and a WS69 rain gauge
readings.
It will need a larger number of different rain events to fine tune the
calibration. It's not out-of-the box accurate yet (for rain), but looks
much better than the "children's diseases" of the Tempest. It doesn't
need a permanent AI based crowd calibration.
One of the strong features of the WS90 is its stability, robustness and
it doesn't have any moveable parts.
The GW2000 console can be connected via WiFi or via Ethernet (LAN cable)
while all other recent Ecowitt consoles are WiFi only.

The above mentioned consoles GWyx00, WN191x, WH2650 can receive all
existing recent Ecowitt sensors/arrays.
My GW1000, GW1100, GW2000 etc. can all receive the WS90 - so can the
HP25x0 consoles (only they don't have an API) - alone or in parallel
You can factually combine +/- all consoles with all sensors - for model
limitations see https://www.wxforum.net/index.php?topic=40730.0

Also beyond the offered packages/stations.

On 27.08.2022 12:29, Greg Troxel wrote:

vince writes:

Agree - a wiki article on this would be great to see.

The one detail I can find is (here)
which
mentions the URL to fake out, but my recollection from back then is there's
also a ntp server it needs to hit periodically to prove Internet
connectivity (or else the watchdog reboots it). The original problem
report mentioning ntp is (here)
as well
in that long thread on wxforum.net.

Thanks; that's useful.

Two questions for the list:

1) Have people used the Wittboy/GW2000 combination, and:

does it work with the gw1000 driver?

does it actualy work, in terms of accurate rain measurements? (I
dimly remember that the weatherflow tempest needed some cloud-based AI
to get valid measurements.)

From looking, it seems the GW1101 is the one to get for budget-conscious
people, as it doesn't have a separate rain gauge that needs new
batteries (no solar) as in the GW1102 and GW1103 and doesn't have the
ultrasonic anemometer that needs power to work in the winter
(freezeups).

2) It seems one could get a wifi weather station and also a GW1100, to
be able to have a display and local access. This seems to be the
sensor suite in the GW1101 and I don't see why the GW1100 wouldn't
receive it:

https://shop.ecowitt.com/products/ws2910

has anyone used a WS-series station and added a GW1100?
Or is the interceptor easy enough to deal with that there's no real
reason?

--
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/9c37bf88-38d9-d5c8-5a3a-cdd8df9b38e7%40gmail.com.

Re: [weewx-user] Re: How to upgrade using a NEW Raspeberry Pi ?

2022-09-27 Thread Rainer Lang

The Rpi4B has nothing to do with it (ca n'en a rien à voir - rien du tout !)

Just do the following things:
1. save your old .../skins/Seasons directory and its content
2. save your old weewx.conf
3. save your old weewx.sdb
e.g. on a USB stick
4. now do a complete new install on the new RPi (doesn't matter if RPi2,
RPi3, RPi4B, just do it !) with the simulator driver

5. make sure you have a webserver installed (apache2 or nginx)
6. if you use an extension or special driver, install that driver/extension
7. once everything works with the Simulator driver and the Seasons skin,
then
copy the files from your USB stick back
a) .../skins/Seasons and content to your new ../skins directory either
/etc/weewx/skins or /home/weewx/skins
b) weewx.conf to your new weewx directory (either /etc/weewx or
/home/weewx depending on your installation method
c) weewx.sdb to your new weewx database directory: either /var/lib/weewx
or /home/weewx/archive

start weewx - and it should just run normally using your old skin
definitions, your old weewx.conf and your old weewx database

then you have upgraded your weewx and have at the same time kept your
configuration and history

On 27.09.2022 23:29, Yves Martin wrote:

Hi Vince,

Yes but it is not working for me.

This is not just an upgrade, I've replaced the Raspberry PI by a new
version (4b) and a new distribution of Debian, including a fresh
install of Python.

When I try to upgrade, it ask me like it was a new install, and do not
consider my "weewx.conf" file.

What did I miss?

Le mardi 27 septembre 2022 à 12 h 40 min 26 s UTC-4, vince a écrit :

You asked the same question on Sept-12 and Sept-25th and several
people tried to help you both times. On Sept-12 Tom pointed you
to the Upgrade Guide (link)
which
has the procedure.

On Tuesday, September 27, 2022 at 8:55:50 AM UTC-7 Yves Martin wrote:

Hi,

I have an old version of weewx : 3.9.2 and I want to upgrade
and in the same time change the hardware by something more
recent (rpi 4b), with a new version of Python...

Is there somewhere a "step by step" manual or indications to
be able to do that?

I follow instructions in the documentation, copying all files,
but it does not work, my "weewx.conf" is not recognized when I
start the upgrade ... like it was a fresh one.

Thanks!

YMartin.com/meteo

--
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/69516126-d693-4c81-aa14-76b3a74e75ddn%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/b5622137-7754-0a9a-e49d-600d298c351a%40gmail.com.

Re: [weewx-user] Re: Pi4 to Pi3 weewx migration

2022-10-09 Thread Rainer Lang

I would use the following approach:
1. take a (new) SD card and put a bootable OS image for a RPi3 on it
2. try to start up /boot your RPi3
3. if it doesn't boot, look up via Google the topic: creating an OS
image for RPi3 and get your RPi3 up and running

4. Once your RPi3 boots and runs, do a new weewx install
5. once weewx runs with the Simulator driver - shut weewx down, copy
your old weewx.conf, your skin files and the old weewx.database

over to the RPi3 and restart weewx. It should then run.

On 09.10.2022 22:46, vince wrote:
This isn't a 'pi' forum. You might have better luck on reddit in
/r/raspberrypi for general pi questions.

On Sunday, October 9, 2022 at 11:36:07 AM UTC-7 blaise@gmail.com
wrote:

Yes, I was not explicit enough, sorry.
The pi3 did not boot.

Le 09-10-22 à 20:31, vince a écrit :

Which "it" did not work ? Did the pi3 boot ? Did weewx not
work after it booted ?

We can't help without more information and also seeing some logs
(if it is weewx you are asking about).

See https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem

On Sunday, October 9, 2022 at 2:53:55 AM UTC-7
blaise@gmail.com wrote:

Hello,

I would like to migrate weewx from a Pi4 to a Pi3. I tried to
simply put the SD card and it did not, of course, work.
Not being an expert Linux, can you tell me a procedure?
weewx 4.8.0 and MySQL

Thanks in advance !

--
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/gb55x4xQN9E/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to weewx-user+...@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/weewx-user/80582939-1127-45e2-9ef9-dd867eb671b4n%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/5b14fc46-263e-41e1-82c6-611cfc1b28e3n%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/0142c077-1fbc-c662-1f9a-11f864a31ebb%40gmail.com.

Re: [weewx-user] Weewx Interceptor Unrecognized parameter / Ignored parameter

2022-10-14 Thread Rainer Lang

yes, this is normal in the sense that the interceptor driver only 
handles the classic observations and the ones shown in your log are out 
of the normal (for the standard interceptor).


Most of these messages (ignored parameter) only appear in the syslog 
when you have debug = 1 activated in weewx.conf


The driver knows "stationtype" and is supposed to ignore it - see 
interceptor.py line 2371 IGNORED_LABELS
It should recognize "PASSKEY" though. Why it doesn't do this and writes 
an error messages is to be figured out but only a "beauty thing". The 
driver will still work properly and provide your console data to weewx.


regarding baromrelin (= rel pressure in inches), weewx calculates the 
relative air pressure from the absolute air pressure using the 12-hour 
average of outdoor temperature and your station elevation - so no 
worries here. maydailygust will be determined by weewx from the recorded 
gust values.


the interceptor driver doesn't know the rather new "runtime" variable in 
the Ecowitt protocol yet - you can edit/add it to the ignored label list 
in line 2371 of the interceptor.py file
(you have to put the to be added parameters into ' ', i.e. 'runtime' and 
not just runtime - and also add a comma e.g. " 'runtime', " [without 
""]; the position in the list doesn't matter)



On 14.10.2022 09:28, Invisible Man wrote:

Hi,
I am using the Interceptor to process packets from an EcoWitt HP2551 
weather station (I do not have the GW1000 gateway).
The logs of weewx show a few anomalies I'd like to check if it is 
normal / solution.


1- PASSKEY

Oct 14 09:18:09 vegan python3[28665]: weewx[28665] DEBUG 
user.interceptor: raw data: 
b'PASSKEY=CENSORED&stationtype=EasyWeatherPro_V5.0.6&runtime=496678&dateutc=2022-10-
Oct 14 09:18:09 vegan python3[28665]: weewx[28665] INFO 
user.interceptor: unrecognized parameter b'PASSKEY=CENSORED


I suppose this passkey is specific to the EcoWitt protocol and it's 
normal the interceptor does not recognize it?


2- Station type

14+07:18:09&tempinf=72.9&humidityin=63&baromrelin=29.734&baromabsin=29.734&tempf=60.8&humidity=90&winddir=226&windspeedmph=0.00&windgustmph=2.24&maxdailygust=3.36&solarradiation=59.51&uv=0&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=1.122&monthlyrainin=1.449&yearlyrainin=1.449&wh65batt=0&wh25batt=0&freq=868M&model=HP2551AE_Pro_V1.8.0'
Oct 14 09:18:09 vegan python3[28665]: weewx[28665] DEBUG 
user.interceptor: ignored parameter stationtype=EasyWeatherPro_V5.0.6


It does not know either about "stationtype". This is perhaps normal 
too. But checking.


3- baromrelin, maxdailygust,

There are many other ignored parameters. Is this normal?

Oct 14 09:18:09 vegan python3[28665]: weewx[28665] INFO 
user.interceptor: unrecognized parameter runtime=496678
Oct 14 09:18:09 vegan python3[28665]: weewx[28665] DEBUG 
user.interceptor: ignored parameter baromrelin=29.734
Oct 14 09:18:09 vegan python3[28665]: weewx[28665] DEBUG 
user.interceptor: ignored parameter maxdailygust=3.36
Oct 14 09:18:09 vegan python3[28665]: weewx[28665] DEBUG 
user.interceptor: ignored parameter eventrainin=0.000
Oct 14 09:18:09 vegan python3[28665]: weewx[28665] DEBUG 
user.interceptor: ignored parameter hourlyrainin=0.000
Oct 14 09:18:09 vegan python3[28665]: weewx[28665] DEBUG 
user.interceptor: ignored parameter dailyrainin=0.000
Oct 14 09:18:09 vegan python3[28665]: weewx[28665] DEBUG 
user.interceptor: ignored parameter weeklyrainin=1.122
Oct 14 09:18:09 vegan python3[28665]: weewx[28665] DEBUG 
user.interceptor: ignored parameter monthlyrainin=1.449
Oct 14 09:18:09 vegan python3[28665]: weewx[28665] DEBUG 
user.interceptor: ignored parameter freq=868M
Oct 14 09:18:09 vegan python3[28665]: weewx[28665] DEBUG 
user.interceptor: ignored parameter model=HP2551AE_Pro_V1.8.0'


Thanks,

Axelle.
--
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/b09540d8-27b7-4131-b59b-7ac159b6a611n%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/baa12bd6-177b-1299-f2c1-ca5afe040832%40gmail.com.

[weewx-user] accumulated 24h - rain in Seasons skin - how to instruct the imagegenerator

2022-10-21 Thread Rainer Lang


Hi guys,

the weewx standard depiction of rain in the Seasons skin is accumulated 
rain per hour as a box plot in the skin.conf  [[[dayrain]]] stanza


how can I make the imagegenerator create a plot where the rain is shown 
as accumulated rain by


1) a line
2) a line as top delimiter and the area below filled with some color

By accumulated I mean that the actual sum of rainfall in the reporting 
interval (300 s) is plotted over a 24 h period
each new rainfall adding to the value before (result: an ascending 
"line" or "staircase")


e.g. 0.0,0.0,0.2,0.4,0.5,0.8,1.2,1.5 etc.

2nd question and alternative depiction:

how can I have the before mentioned and create a reset at midnight

thanks for helping me out

--
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/6557cd6d-fb13-cf2a-eaeb-af6a8a0566ae%40gmail.com.

Re: [weewx-user] accumulated 24h - rain in Seasons skin - how to instruct the imagegenerator

2022-10-21 Thread Rainer Lang


@chuck:
- thanks for the "cumulative" key word - hadn't found that so far - 
works perfectly
- as for the Phenology Extension, I'm using that for one of my stations 
already for quite some time - that's where my fill question came from
but I can see that with plot_type = bar and aggregate_interval = 300 and 
width = 2  the area under the curve is also fully filled 😎

even with the default weewx image generator


what remains open is the question about how to reset the cumulative 
graph to 0 at midnight



On 21.10.2022 18:54, Chuck Rhode wrote:


On Fri, 21 Oct 2022 11:16:31 +0200
Rainer Lang  wrote:

> how can I make the imagegenerator create a plot where the rain is
> shown as accumulated rain by ... a line as top delimiter and the
> area below filled with some color

It's trivial to generate a cumulative bar plot.

>  [[[dayrain]]]
>  yscale = None, None, 0.02
>  plot_type = bar
>  rain
>  aggregate_type = cumulative
>  aggregate_interval = 900  # 15 minutes
>  label = Rain (hourly accumulation)

It is not so trivial to replace the WeeWX Image Generator with mine
that I ship with my Phenology Extension.  This adds support for the
fill_curve option ... among a great many other things.

>  [[[dayrain]]]
>  yscale = None, None, 0.02
>  plot_type = line
>  fill_curve = True
>  fill_color = "#72b2c420"
>  rain
>  aggregate_type = cumulative
>  aggregate_interval = 900  # 15 minutes
>  label = Rain (hourly accumulation)

Which produces the following screenshot seen here dressed in my
"Sperry 1100" theme:

o https://lacusveris.com/Screenshot%20from%202022-10-21%2011-23-42.png

"How to" details may be found at:

o https://lacusveris.com/Phenology/weewx_extension.shtml

One might say, though, that this approach is overkill in every sense.
Not only is installation and use of the Phenology Extension a fraught
process, but the Phenology Image Generator itself operates at somewhat
below peak efficiency.  And I note from the above screenshot that I
have not stretched the curve fill to include the ramp-up from the last
missing value on the left.  Oh, well 




--
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/9f8fca5e-558e-4f6f-8a66-d507b7982e12%40gmail.com.

Re: [weewx-user] Re: first user - a lot of issues

2022-11-04 Thread Rainer Lang

When you want to use weewx under WSL (which works perfectly by the way -
at least with the Interceptor and the Ecowitt Gateway driver),
you need to make sure that the connectivity between the virtual machine
in which WSL is running and the local network the WSL host computer is
running in

has been established.
There are recipes for that - Google is your friend - they describe
Windows Powershell commands to be applied for this to work.

That's not a weewx specific issue - it applies to any application
running in WSL (Windows Subsystem for Linux) and needing to
contact/communicate

with the local network of the host computer.

On 04.11.2022 19:47, vince wrote:

We really need more information on your setup.

It 'seems' like you are trying to run a rather unusual configuration.

I noticed this in your errors.txt file:

* "Linux-5.10.102.1-microsoft-standard-WSL2-x86_64-with-glibc2.29"

==> are you trying to run weewx under Windows WSL perhaps ?

I also see the following:

* Message: 'Socket error while opening port %d to ethernet host %s.'
Arguments: (2, '192.168.0.248') --- Logging error ---
Traceback (most recent call last): File
"/usr/share/weewx/weewx/drivers/vantage.py", line 338, in openPort
self.socket.connect((self.host, self.port)) OSError: [Errno 113]
No route to host

==> this is a networking issue in your setup

We can't try to duplicate the problem(s) without knowing more about
your setup.

--
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/19a056c8-8f87-4460-b31c-feb78448ccbbn%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/fef7077b-712b-cc8e-9aa2-02c9e91e260f%40gmail.com.

Re: [weewx-user] Re: first user - a lot of issues

2022-11-04 Thread Rainer Lang


maybe we are talking cross-purpose:
what you describe below is exactly the installation of WSL (exactly 
speaking WSL2) under Windows 11.
Also with Win 11 you have to create the connection between the Windows 
11 installation and the VM if some application or device in the local 
network

wants to connect with an application inside the VM (here weewx).
Ubuntu on WSL2 doesn't contain by default certain services like systemd 
or rsyslogd. They need to be installed by you manually.
Again, there is plenty of documentation for this. Especially for 
installing systemd under WSL2.

e.g. for the network integration and firewall
https://stackoverflow.com/questions/61002681/connecting-to-wsl2-server-via-local-network
If you use such environments, you need to know their "shortcoming" and 
needs. 😎


On 05.11.2022 03:31, Alex Vanuxem wrote:

hey,

It was under wsl.
*but now i installed under windows 11, hyper-v and installed an ubuntu 
latest version under a virtual machine, i have the full program;*

now i'm struggling again;
again no syslog, it says its installed, but cant start it
i can invoke ./bin/weewxd , i see a lot of data coming in in my 
terminal, but no reports to var/www/html/ weewx,

i guess it something to do with permissions? or am i just dumb
thank you for your time,






Op vr 4 nov. 2022 om 22:24 schreef Rainer Lang :

When you want to use weewx under WSL (which works perfectly by the
way - at least with the Interceptor and the Ecowitt Gateway driver),
you need to make sure that the connectivity between the virtual
machine in which WSL is running and the local network the WSL host
computer is running in
has been established.
There are recipes for that - Google is your friend - they describe
Windows Powershell commands to be applied for this to work.

That's not a weewx specific issue - it applies to any application
running in WSL (Windows Subsystem for Linux) and needing to
contact/communicate
with the local network of the host computer.

On 04.11.2022 19:47, vince wrote:

We really need more information on your setup.

It 'seems' like you are trying to run a rather unusual configuration.

I noticed this in your errors.txt file:

  * "Linux-5.10.102.1-microsoft-standard-WSL2-x86_64-with-glibc2.29"

           ==> are you trying to run weewx under Windows WSL
perhaps ?

I also see the following:

  * Message: 'Socket error while opening port %d to ethernet host
%s.' Arguments: (2, '192.168.0.248') --- Logging error
--- Traceback (most recent call last): File
"/usr/share/weewx/weewx/drivers/vantage.py", line 338, in
openPort self.socket.connect((self.host, self.port)) OSError:
[Errno 113] No route to host

             ==> this is a networking issue in your setup

We can't try to duplicate the problem(s) without knowing more
about your setup.

-- 
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/19a056c8-8f87-4460-b31c-feb78448ccbbn%40googlegroups.com

<https://groups.google.com/d/msgid/weewx-user/19a056c8-8f87-4460-b31c-feb78448ccbbn%40googlegroups.com?utm_medium=email&utm_source=footer>.



-- 
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/fef7077b-712b-cc8e-9aa2-02c9e91e260f%40gmail.com

<https://groups.google.com/d/msgid/weewx-user/fef7077b-712b-cc8e-9aa2-02c9e91e260f%40gmail.com?utm_medium=email&utm_source=footer>.

--
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/CAHaYyo%2BUxKKd55E8VixmNnARUgsF-bEzqZvNQbjjD8UGxDNjLA%40mail.gmail.com 
<https://groups.google.com/d/msgid/weewx-user/CAHaYyo%2BUxKKd55E8VixmNnARUgsF-bEzqZvNQbjjD8UGxDNjLA%40mail.gmail.com?utm_medium=email&utm_source=footer>.


--
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/e3988bd8-1bed-f6fb-d831-7477153766c5%40gmail.com.

[weewx-user] Re: first user - a lot of issues [2]

2022-11-05 Thread Rainer Lang


one more thing:
first of all you have to check if systemd is installed in your ubuntu 
installation - if not you need to install it (or something equivalent)

how to find out ?
run
sudo /service --status-all
(or when you are the root user without the "sudo")
/
If systemd is not installed, have a look at/
/
e.g. https://github.com/DamionGans/ubuntu-wsl2-systemd-script

with the below commands you can install systemd under ubuntu on WSL2

|sudo apt install git
git clone https://github.com/DamionGans/ubuntu-wsl2-systemd-script.git
cd ubuntu-wsl2-systemd-script/
bash ubuntu-wsl2-systemd-script.sh
# Enter your password and wait until the script has finished
systemctl|

||


|You also have to look if the rsyslog service is installed/running (see 
above command service --status-all)

if not, you can try|
|sudo apt-get install rsyslog||
|

||

On 05.11.2022 07:33, Rainer Lang wrote:

maybe we are talking cross-purpose:
what you describe below is exactly the installation of WSL (exactly 
speaking WSL2) under Windows 11.
Also with Win 11 you have to create the connection between the Windows 
11 installation and the VM if some application or device in the local 
network

wants to connect with an application inside the VM (here weewx).
Ubuntu on WSL2 doesn't contain by default certain services like 
systemd or rsyslogd. They need to be installed by you manually.
Again, there is plenty of documentation for this. Especially for 
installing systemd under WSL2.

e.g. for the network integration and firewall
https://stackoverflow.com/questions/61002681/connecting-to-wsl2-server-via-local-network
If you use such environments, you need to know their "shortcoming" and 
needs. 😎


On 05.11.2022 03:31, Alex Vanuxem wrote:

hey,

It was under wsl.
*but now i installed under windows 11, hyper-v and installed an 
ubuntu latest version under a virtual machine, i have the full program;*

now i'm struggling again;
again no syslog, it says its installed, but cant start it
i can invoke ./bin/weewxd , i see a lot of data coming in in my 
terminal, but no reports to var/www/html/ weewx,

i guess it something to do with permissions? or am i just dumb
thank you for your time,






Op vr 4 nov. 2022 om 22:24 schreef Rainer Lang :

When you want to use weewx under WSL (which works perfectly by
the way - at least with the Interceptor and the Ecowitt Gateway
driver),
you need to make sure that the connectivity between the virtual
machine in which WSL is running and the local network the WSL
host computer is running in
has been established.
There are recipes for that - Google is your friend - they
describe Windows Powershell commands to be applied for this to work.

That's not a weewx specific issue - it applies to any application
running in WSL (Windows Subsystem for Linux) and needing to
contact/communicate
with the local network of the host computer.

On 04.11.2022 19:47, vince wrote:

We really need more information on your setup.

It 'seems' like you are trying to run a rather unusual
configuration.

I noticed this in your errors.txt file:

  * "Linux-5.10.102.1-microsoft-standard-WSL2-x86_64-with-glibc2.29"

           ==> are you trying to run weewx under Windows WSL
perhaps ?

I also see the following:

  * Message: 'Socket error while opening port %d to ethernet
host %s.' Arguments: (2, '192.168.0.248') --- Logging
error --- Traceback (most recent call last): File
"/usr/share/weewx/weewx/drivers/vantage.py", line 338, in
openPort self.socket.connect((self.host, self.port))
OSError: [Errno 113] No route to host

             ==> this is a networking issue in your setup

We can't try to duplicate the problem(s) without knowing more
about your setup.

-- 
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/19a056c8-8f87-4460-b31c-feb78448ccbbn%40googlegroups.com

<https://groups.google.com/d/msgid/weewx-user/19a056c8-8f87-4460-b31c-feb78448ccbbn%40googlegroups.com?utm_medium=email&utm_source=footer>.



-- 
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/fef7077b-712b-cc8e-9aa2-02c9e91e260f%40gmail.com

<https://groups.google.com/d/msgid/weewx-user/fef7077b-712b-cc8e-9aa2-02c9e91e260f%40gmail.co

[weewx-user] Re: first user - a lot of issues [2]

2022-11-07 Thread Rainer Lang

this log doesn't say anything regarding weewx except that weewx wrote 
two records to its database which is already (at least a partial) success.

Such clipped logfiles are not very helpful.
Otherwise I cannot see any weewx related error.
You have to add debug = 1 to your weewx.conf (at the top of weewx.conf - 
change debug = 0 to debug =1),

save and restart weewx.
And then provide the COMPLETE syslog entries from weewx start until at 
least one, better two, archiving cycles.
One cycle starts usually every 5 minutes (depending on your settings in 
weewx.conf).

Without that we can only poke in the dark.


On 06.11.2022 23:43, Alex Vanuxem wrote:

thx man;

so where I am at:
installed hyper-v on windows 11
installed an ubuntu virtual machine
tried to instal weewx
got a syslog see attachment
got data in, but with errors, see log
still need to connect the virtual machine with windows, struggling 
with that

still need to install system.d struggling with that too





Op za 5 nov. 2022 om 09:23 schreef Rainer Lang :

one more thing:
first of all you have to check if systemd is installed in your
ubuntu installation - if not you need to install it (or something
equivalent)
how to find out ?
run
sudo /service --status-all
(or when you are the root user without the "sudo")
/
If systemd is not installed, have a look at/
/
e.g. https://github.com/DamionGans/ubuntu-wsl2-systemd-script

with the below commands you can install systemd under ubuntu on WSL2

|sudo apt install git
git clone
https://github.com/DamionGans/ubuntu-wsl2-systemd-script.git
cd ubuntu-wsl2-systemd-script/
bash ubuntu-wsl2-systemd-script.sh
# Enter your password and wait until the script has finished
systemctl|

||


|You also have to look if the rsyslog service is installed/running
(see above command service --status-all)
if not, you can try|
|sudo apt-get install rsyslog||
|

||

On 05.11.2022 07:33, Rainer Lang wrote:

maybe we are talking cross-purpose:
what you describe below is exactly the installation of WSL
(exactly speaking WSL2) under Windows 11.
Also with Win 11 you have to create the connection between the
Windows 11 installation and the VM if some application or device
in the local network
wants to connect with an application inside the VM (here weewx).
Ubuntu on WSL2 doesn't contain by default certain services like
systemd or rsyslogd. They need to be installed by you manually.
Again, there is plenty of documentation for this. Especially for
installing systemd under WSL2.
e.g. for the network integration and firewall

https://stackoverflow.com/questions/61002681/connecting-to-wsl2-server-via-local-network
If you use such environments, you need to know their
"shortcoming" and needs. 😎

On 05.11.2022 03:31, Alex Vanuxem wrote:

hey,

It was under wsl.
*but now i installed under windows 11, hyper-v and installed an
ubuntu latest version under a virtual machine, i have the full
program;*
now i'm struggling again;
again no syslog, it says its installed, but cant start it
i can invoke ./bin/weewxd , i see a lot of data coming in in my
terminal, but no reports to var/www/html/ weewx,
i guess it something to do with permissions? or am i just dumb
thank you for your time,






Op vr 4 nov. 2022 om 22:24 schreef Rainer Lang
:

When you want to use weewx under WSL (which works perfectly
by the way - at least with the Interceptor and the Ecowitt
Gateway driver),
you need to make sure that the connectivity between the
virtual machine in which WSL is running and the local
network the WSL host computer is running in
has been established.
There are recipes for that - Google is your friend - they
describe Windows Powershell commands to be applied for this
to work.

That's not a weewx specific issue - it applies to any
application running in WSL (Windows Subsystem for Linux) and
needing to contact/communicate
with the local network of the host computer.

On 04.11.2022 19:47, vince wrote:

We really need more information on your setup.

It 'seems' like you are trying to run a rather unusual
configuration.

I noticed this in your errors.txt file:

  * "Linux-5.10.102.1-microsoft-standard-WSL2-x86_64-with-glibc2.29"

           ==> are you trying to run weewx under Windows
WSL perhaps ?

I also see the following:

  * Message: 'Socket error while opening port %d to
ethernet host %s.' Arguments: (2, '192.168.0.248')
--- Logging error --- Traceback (most recent call
last): File
"/usr/share/weewx/wee

Re: [weewx-user] Weewx does not update website with new data.

2022-11-18 Thread Rainer Lang

What I would do first is assigning one of your WH31 sensors (also) to 
the outdoor T/H sensor

in weewx.conf
[StdCalibrate]
[[Corrections]] add the lines
outTemp = extraTemp1
outHumidity = extraHumid1
(as an example - you can take whichever of your WH31 you prefer, 
extraTemp1, 2, 3, 4 ...))
As a result, weewx will save these WH31 values also as 
outTemp/outHumidity, so you missing tempf issue might disappear.

Try that and see what it gives
On 17.11.2022 22:31, Bob Rose wrote:
After running weewx with a ecowitt gw1000 for about 2 years I decided 
to build a new server. The initial install of 4.9.1 and “simulator” 
test went well. I used the "Deb" install method. Ubuntu server. weewx 
updated the new website with simulated data. I went ahead and 
installed the GW1000 driver. Weewx is now not updating the website. 
The old simulator data remains.  It is collecting data and seems to be 
parsing the generated files in the “website”/ecowitt/ directory. Well 
at least they appear and disappear. I did uses the sqlite file from 
the old install. nothing else. Note this station does not have an 
outside temperature sensor. I am using 3 Wh31s sensors in places 
outdoors. I did set debug to 1 trying to gain info from the logs. I 
did note that "tempf" seems to trigger the fault. see second log output.

From one of the files in /ecowitt/
Array
(
    [PASSKEY] => “a bunch of hex stuff”
    [stationtype] => GW1000B_V1.7.5
    [runtime] => 1033890
    [dateutc] => 2022-11-17 20:51:06
    [tempinf] => 69.08
    [humidityin] => 38
    [baromrelin] => 30.127
    [baromabsin] => 27.569
    [winddir] => 65
    [windspeedmph] => 2.91
    [windgustmph] => 4.47
    [maxdailygust] => 17.22
    [solarradiation] => 56.27
    [uv] => 0
    [rainratein] => 0.000
    [eventrainin] => 0.000
    [hourlyrainin] => 0.000
    [dailyrainin] => 0.000
    [weeklyrainin] => 0.000
    [monthlyrainin] => 0.000
    [yearlyrainin] => 5.346
    [totalrainin] => 5.346
    [temp1f] => 71.06
    [humidity1] => 20
    [temp2f] => 69.80
    [humidity2] => 20
    [temp3f] => 74.30
    [humidity3] => 18
    [soilmoisture1] => 48
    [soilmoisture2] => 27
    [lightning_num] => 8
    [lightning] => 14
    [lightning_time] => 1668699860
    [wh68batt] => 1.62
    [batt1] => 0
    [batt2] => 0
    [batt3] => 0
    [soilbatt1] => 1.3
    [soilbatt2] => 1.3
    [wh57batt] => 3
    [freq] => 915M
    [model] => GW1000B_Pro
)


From systemlog. Note it is bottom to top. Newest at top. Just after a 
restart of weewx.


Nov 17 14:00:58 ubuntserver weewx[552308] INFO user.gw1000: Skipping 
lightning count of 8: no last count
Nov 17 14:00:58 ubuntserver weewx[552308] INFO user.gw1000: skipping 
rain measurement of 135.8: no last rain
Nov 17 14:00:58 ubuntserver weewx[552308] INFO user.gw1000: Using 
't_rainyear' for rain total
Nov 17 14:00:58 ubuntserver weewx[552308] DEBUG user.gw1000: Next 
update in 60 seconds
Nov 17 14:00:58 ubuntserver weewx[552308] DEBUG user.gw1000: Unknown 
field address '7B' detected. Remaining data '00' ignored.
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.engine: Starting 
main packet loop.
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.manager: Daily 
summaries up to date
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.manager: Starting 
backfill of daily summaries
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.engine: Using 
binding 'wx_binding' to database 'weewx.sdb'
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Station 
does not support reading the time
Nov 17 14:00:57 ubuntserver weewx[552308] INFO __main__: Starting up 
weewx version 4.9.1
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Finished 
loading service weewx.engine.StdReport
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.engine: 'pyephem' 
not detected, extended almanac data is not available
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Loading 
service weewx.engine.StdReport
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Finished 
loading service weewx.engine.StdPrint
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Loading 
service weewx.engine.StdPrint
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Finished 
loading service weewx.restx.StdAWEKAS
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.restx: AWEKAS: 
Posting not enabled.
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Loading 
service weewx.restx.StdAWEKAS
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Finished 
loading service weewx.restx.StdWOW
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.restx: WOW: 
Posting not enabled.
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Loading 
service weewx.restx.StdWOW
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Finished 
loading service weewx.restx.StdCWOP
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.restx: CWOP: 
Posting not enabled.
Nov 17 14:00:57 ubuntserver weewx[552308

Re: [weewx-user] Weewx does not update website with new data.

2022-11-18 Thread Rainer Lang

I'm only realizing now - after having read Gary's mail which came in 
late due to internet issues - that you seem to use two different 
drivers/services in parallel in one weewx instance, which is likely to 
be the cause for unpredictable behaviour.
You better choose only one of them - and by experience, I'd prefer the 
Ecowitt Gateway (GW1000) driver and remove this AddEcowittData thing
which probably was once written to cover for a those days not yet 
existing GW-GW driver.
Gary's EW-GW driver is very stable and covers all sensors of the these 
days Ecowitt (sensor) universe.

On 18.11.2022 10:11, Rainer Lang wrote:
What I would do first is assigning one of your WH31 sensors (also) to 
the outdoor T/H sensor

in weewx.conf
[StdCalibrate]
[[Corrections]] add the lines
outTemp = extraTemp1
outHumidity = extraHumid1
(as an example - you can take whichever of your WH31 you prefer, 
extraTemp1, 2, 3, 4 ...))
As a result, weewx will save these WH31 values also as 
outTemp/outHumidity, so you missing tempf issue might disappear.

Try that and see what it gives
On 17.11.2022 22:31, Bob Rose wrote:
After running weewx with a ecowitt gw1000 for about 2 years I decided 
to build a new server. The initial install of 4.9.1 and “simulator” 
test went well. I used the "Deb" install method. Ubuntu server. weewx 
updated the new website with simulated data. I went ahead and 
installed the GW1000 driver. Weewx is now not updating the website. 
The old simulator data remains.  It is collecting data and seems to 
be parsing the generated files in the “website”/ecowitt/ directory. 
Well at least they appear and disappear. I did uses the sqlite file 
from the old install. nothing else. Note this station does not have 
an outside temperature sensor. I am using 3 Wh31s sensors in places 
outdoors. I did set debug to 1 trying to gain info from the logs. I 
did note that "tempf" seems to trigger the fault. see second log output.

From one of the files in /ecowitt/
Array
(
    [PASSKEY] => “a bunch of hex stuff”
    [stationtype] => GW1000B_V1.7.5
    [runtime] => 1033890
    [dateutc] => 2022-11-17 20:51:06
    [tempinf] => 69.08
    [humidityin] => 38
    [baromrelin] => 30.127
    [baromabsin] => 27.569
    [winddir] => 65
    [windspeedmph] => 2.91
    [windgustmph] => 4.47
    [maxdailygust] => 17.22
    [solarradiation] => 56.27
    [uv] => 0
    [rainratein] => 0.000
    [eventrainin] => 0.000
    [hourlyrainin] => 0.000
    [dailyrainin] => 0.000
    [weeklyrainin] => 0.000
    [monthlyrainin] => 0.000
    [yearlyrainin] => 5.346
    [totalrainin] => 5.346
    [temp1f] => 71.06
    [humidity1] => 20
    [temp2f] => 69.80
    [humidity2] => 20
    [temp3f] => 74.30
    [humidity3] => 18
    [soilmoisture1] => 48
    [soilmoisture2] => 27
    [lightning_num] => 8
    [lightning] => 14
    [lightning_time] => 1668699860
    [wh68batt] => 1.62
    [batt1] => 0
    [batt2] => 0
    [batt3] => 0
    [soilbatt1] => 1.3
    [soilbatt2] => 1.3
    [wh57batt] => 3
    [freq] => 915M
    [model] => GW1000B_Pro
)


From systemlog. Note it is bottom to top. Newest at top. Just after a 
restart of weewx.


Nov 17 14:00:58 ubuntserver weewx[552308] INFO user.gw1000: Skipping 
lightning count of 8: no last count
Nov 17 14:00:58 ubuntserver weewx[552308] INFO user.gw1000: skipping 
rain measurement of 135.8: no last rain
Nov 17 14:00:58 ubuntserver weewx[552308] INFO user.gw1000: Using 
't_rainyear' for rain total
Nov 17 14:00:58 ubuntserver weewx[552308] DEBUG user.gw1000: Next 
update in 60 seconds
Nov 17 14:00:58 ubuntserver weewx[552308] DEBUG user.gw1000: Unknown 
field address '7B' detected. Remaining data '00' ignored.
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.engine: Starting 
main packet loop.
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.manager: Daily 
summaries up to date
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.manager: 
Starting backfill of daily summaries
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.engine: Using 
binding 'wx_binding' to database 'weewx.sdb'
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Station 
does not support reading the time
Nov 17 14:00:57 ubuntserver weewx[552308] INFO __main__: Starting up 
weewx version 4.9.1
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: 
Finished loading service weewx.engine.StdReport
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.engine: 
'pyephem' not detected, extended almanac data is not available
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Loading 
service weewx.engine.StdReport
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: 
Finished loading service weewx.engine.StdPrint
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Loading 
se

1 2 3 >

1 - 100 of 256 matches

Mail list logo