[weewx-user] Re: GW2000/WS90 Piezo & Ecowitt Gateway Driver
Hi Gary, Thanks for your message, much appreciated. Based on the data that I'm getting from the GW2000/WS90 with debug enabled, I've set up the following in weewx.conf. Hoping that on my next rain event I'll get some data. I've not added any other fields to the database; although it would have been nice to have the rain history from the last few days when I set it up. We had some good downpours from the recent Potential Tropical Cyclone #1 as it passed. [GW1000] #p_rain p_stormRain p_rainRate p_dayRain p_weekRain p_monthRain p_yearRain [[field_map_extensions]] rain = p_rain stormRain = p_stormRain dayRain = p_dayRain weekRain = p_weekRain monthRain = p_monthRain yearRain = p_yearRain rainRate = p_rainRate Hopefully this thread will be useful for someone with a new GW2000/WS90 Thanks, Arthur On Saturday, June 4, 2022 at 5:32:58 AM UTC-5 gjr80 wrote: > Arthur, > > There are a few approaches you could use, what works best will depend on > what hardware you have and what you want to achieve. > > If your only rain gauge is the WS90 then the easiest approach is to alter > the Ecowitt Gateway Driver field map to map the WS90 (piezo) rain fields to > the standard WeeWX rain fields. This approach requires no change to the > Seasons skin (other than perhaps some sensor settings if you wish to > display WS90 battery and signal data). You could do as you outlined above > and add additional fields to the WeeWX database and alter the Season skin > to display these new fields, though if the WS90 is your only rain gauge > then that is quite a bit of work for no real benefit. If you have another > rain gauge as well as the WS90 then the standard WeeWx rain fields will > likely be used by the other rain gauge. In that case you have no choice but > to add new fields to the database in which to save the WS90 rain data (and > modify the Seasons skin as you indicated). Note that the week, month and > year fields are not used by the Seasons skin, so there is no real benefit > in adding them to the database. The dayRain field is used by some of the > RESTful uploaders, so there may be benefit in providing that field to WeeWX > (it must be named dayRain though), but there is no need to add it to the > database as only the current value is used. > > Assuming the WS90 is your only rain gauge the following field map > extensions for the driver should be all that is required, something like: > > [GW1000] > > [[field_map_extensions]] > rain = p_rain > stormRain = p_rainevent > dayRain = p_rainday > weekRain = p_rainweek > monthRain = p_rainmonth > yearRain = p_rainyear > rainRate = p_rainrate > > Of the above fields only rain and rainRate will be stored in the database > (WeeWX will automatically store data in fields where (1) the field exists > in the archive record and (2) the archive table in the database has an > identical column name, all other fields are ultimately discarded). This is > fine if the Seasons skin is all you are using as the Seasons skin does not > use any of the other rain related fields. As mentioned above if you are > uploading to WU or PWS then the dayRain field may be of use, though if it > is not available WeeWX will calculate the value from the rain field. So > unless you have some other need stormRain, weekRain, monthRain and > yearRain entries could be omitted without detriment. > > Gary > > On Saturday, 4 June 2022 at 14:26:40 UTC+10 Captain Steubing wrote: > >> Howdy WX Friends, >> >> Recently installed WeeWX pulling data from a GW2000/WS90. System is >> built and receiving data from the GW2000. Trying to figure out how to get >> the "p_rainX" variables into WeeWX. I've pieced together what I think I >> need to do, but want to ensure I'm understanding things correctly. >> >>- Add the p_rainX (p_rain p_stormRain p_rainRate p_dayRain p_weekRain >>p_monthRain p_yearRain) columns to the WeeWX database. >> - Assuming this is the command: wee_database --add-column=p_rain >> etc. >>- Update skin.conf stanzas [DisplayOptions] and [CheetahGenerator] >>adding p_rainX where I see the rainX variables . >> >> Is there a way to map the p_rainX variables to the standard rainX variables >> to avoid having to do all of this manual config? >> >> Thanks for your help. >> >> Thanks, >> Arthur >> > -- 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/24a0910a-329a-46b3-ab78-d41a51301764n%40googlegroups.com.
[weewx-user] Unable to load driver: Unable to wake up Vantage console.
Hello,
I decided to upgrade my Weewx system to a Pi4 from the Pi original and have
hit nothing but hiccups! I've checked my cabling; found a broken wire and
corrected it.
Here is my log file showing the problem:
Jun 4 16:40:17 weewx-pi systemd[1]: Starting weewx weather system...
Jun 4 16:40:17 weewx-pi weewx[1053] INFO __main__: Initializing weewx
version 4.4.0
Jun 4 16:40:17 weewx-pi weewx[1053] INFO __main__: Using Python 3.9.2
(default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
Jun 4 16:40:17 weewx-pi weewx[1053] INFO __main__: Platform
Linux-5.15.32-v7l+-armv7l-with-glibc2.31
Jun 4 16:40:17 weewx-pi weewx[1053] INFO __main__: Locale is 'en_US.UTF-8'
Jun 4 16:40:17 weewx-pi weewx[1053] INFO __main__: PID file is
/var/run/weewx.pid
Jun 4 16:40:17 weewx-pi weewx[1056] INFO __main__: Using configuration
file /home/weewx/weewx.conf
Jun 4 16:40:17 weewx-pi weewx[1056] INFO __main__: Debug is 0
Jun 4 16:40:17 weewx-pi weewx[1056] INFO weewx.engine: Loading station
type Vantage (weewx.drivers.vantage)
Jun 4 16:40:17 weewx-pi systemd[1]: Started weewx weather system.
Jun 4 16:40:22 weewx-pi dhcpcd[472]: wlan0: failed to request information
Jun 4 16:40:33 weewx-pi weewx[1056] ERROR weewx.drivers.vantage: Unable to
wake up console
Jun 4 16:40:33 weewx-pi weewx[1056] ERROR weewx.engine: Import of driver
failed: Unable to wake up Vantage console ()
Jun 4 16:40:33 weewx-pi weewx[1056] CRITICAL weewx.engine:
Traceback (most recent call last):
Jun 4 16:40:33 weewx-pi weewx[1056] CRITICAL weewx.engine:
File "/home/weewx/bin/weewx/engine.py", line 119, in setupStation
Jun 4 16:40:33 weewx-pi weewx[1056] CRITICAL weewx.engine:
self.console = loader_function(config_dict, self)
Jun 4 16:40:33 weewx-pi weewx[1056] CRITICAL weewx.engine:
File "/home/weewx/bin/weewx/drivers/vantage.py", line 39, in loader
Jun 4 16:40:33 weewx-pi weewx[1056] CRITICAL weewx.engine:
return VantageService(engine, config_dict)
Jun 4 16:40:33 weewx-pi weewx[1056] CRITICAL weewx.engine:
File "/home/weewx/bin/weewx/drivers/vantage.py", line 1898, in __init__
Jun 4 16:40:33 weewx-pi weewx[1056] CRITICAL weewx.engine:
Vantage.__init__(self, **config_dict[DRIVER_NAME])
Jun 4 16:40:33 weewx-pi weewx[1056] CRITICAL weewx.engine:
File "/home/weewx/bin/weewx/drivers/vantage.py", line 515, in __init__
Jun 4 16:40:33 weewx-pi weewx[1056] CRITICAL weewx.engine:
self._setup()
Jun 4 16:40:33 weewx-pi weewx[1056] CRITICAL weewx.engine:
File "/home/weewx/bin/weewx/drivers/vantage.py", line 1317, in _setup
Jun 4 16:40:33 weewx-pi weewx[1056] CRITICAL weewx.engine:
self.port.wakeup_console(max_tries=self.max_tries)
Jun 4 16:40:33 weewx-pi weewx[1056] CRITICAL weewx.engine:
File "/home/weewx/bin/weewx/drivers/vantage.py", line 118, in
wakeup_console
Jun 4 16:40:33 weewx-pi weewx[1056] CRITICAL weewx.engine:
raise weewx.WakeupError("Unable to wake up Vantage console")
Jun 4 16:40:33 weewx-pi weewx[1056] CRITICAL weewx.engine:
weewx.WakeupError: Unable to wake up Vantage console
Jun 4 16:40:33 weewx-pi weewx[1056] CRITICAL __main__: Unable to load
driver: Unable to wake up Vantage console
Jun 4 16:40:33 weewx-pi weewx[1056] CRITICAL __main__: Exiting...
Jun 4 16:40:33 weewx-pi systemd[1]: weewx.service: Main process exited,
code=exited, status=4/NOPERMISSION
I've used this as a guide:
https://www.cougar.eu.com/useful-guides/weewx-guides/rasberry-pi/rasberry-pi-install.html
Linux isn't my strong suit, but I usually manage to find my way around.
All I can derive from the log file is that 'sumpin's broke'!
Can anyone point me to a solution?
Kind regards,
Michael
K6MLE
--
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/6e01bab8-b7c1-4f5b-b603-351ace67cec9n%40googlegroups.com.
Re: [weewx-user] Sunshine Database
It is a very good idea to calculate the sunshine duration for each LOOP packet and sum these values to make the final archive sunshine duration. I have modified my script accordingly : https://github.com/Jterrettaz/sunduration. The logic is the following : for each received LOOP packet, the radiation is compared to a calculated threshold. If the radiation is above the threshold value, the sunshine time for the LOOP packet is equal to the time elapsed between the previous loop packet and this packet (most of the time 2 seconds with a Vantage Davis Pro). The final archive sunshine duration is the sum of all the LOOP value within the archive period. Le vendredi 3 juin 2022 à 21:59:36 UTC+2, Peter Fletcher a écrit : > That makes some sense when you are getting data from an 'external' sensor, > though there are (IMHO) simpler ways of doing it. weewx already has access > to the LOOP radiation data from the VP2, so handling the processing and > data storage within weewx makes more sense to me in this case. > > On Friday, June 3, 2022 at 3:24:23 PM UTC-4 vince wrote: > >> On Friday, June 3, 2022 at 11:17:00 AM UTC-7 Meteo Oberwallis wrote: >> >>> if the interval of Weewx and the data logger is set to 10 minutes, I >>> would have liked to read the value of the solar sensor every minute and >>> then write it into a separate .sdb database as possible sunshine. >> >> >> Personally I'd use an external program called via cron and posting a >> message to a MQTT topic. Have weewx subscribe to that topic to get the >> data into your db. >> >> This is how I used to get my DS18b20 temperature sensor data into weewx. >> >> -- 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/50c0897a-0e04-4f6f-b864-1961bbca8124n%40googlegroups.com.
[weewx-user] Re: GW2000/WS90 Piezo & Ecowitt Gateway Driver
Arthur, There are a few approaches you could use, what works best will depend on what hardware you have and what you want to achieve. If your only rain gauge is the WS90 then the easiest approach is to alter the Ecowitt Gateway Driver field map to map the WS90 (piezo) rain fields to the standard WeeWX rain fields. This approach requires no change to the Seasons skin (other than perhaps some sensor settings if you wish to display WS90 battery and signal data). You could do as you outlined above and add additional fields to the WeeWX database and alter the Season skin to display these new fields, though if the WS90 is your only rain gauge then that is quite a bit of work for no real benefit. If you have another rain gauge as well as the WS90 then the standard WeeWx rain fields will likely be used by the other rain gauge. In that case you have no choice but to add new fields to the database in which to save the WS90 rain data (and modify the Seasons skin as you indicated). Note that the week, month and year fields are not used by the Seasons skin, so there is no real benefit in adding them to the database. The dayRain field is used by some of the RESTful uploaders, so there may be benefit in providing that field to WeeWX (it must be named dayRain though), but there is no need to add it to the database as only the current value is used. Assuming the WS90 is your only rain gauge the following field map extensions for the driver should be all that is required, something like: [GW1000] [[field_map_extensions]] rain = p_rain stormRain = p_rainevent dayRain = p_rainday weekRain = p_rainweek monthRain = p_rainmonth yearRain = p_rainyear rainRate = p_rainrate Of the above fields only rain and rainRate will be stored in the database (WeeWX will automatically store data in fields where (1) the field exists in the archive record and (2) the archive table in the database has an identical column name, all other fields are ultimately discarded). This is fine if the Seasons skin is all you are using as the Seasons skin does not use any of the other rain related fields. As mentioned above if you are uploading to WU or PWS then the dayRain field may be of use, though if it is not available WeeWX will calculate the value from the rain field. So unless you have some other need stormRain, weekRain, monthRain and yearRain entries could be omitted without detriment. Gary On Saturday, 4 June 2022 at 14:26:40 UTC+10 Captain Steubing wrote: > Howdy WX Friends, > > Recently installed WeeWX pulling data from a GW2000/WS90. System is built > and receiving data from the GW2000. Trying to figure out how to get the " > p_rainX" variables into WeeWX. I've pieced together what I think I need > to do, but want to ensure I'm understanding things correctly. > >- Add the p_rainX (p_rain p_stormRain p_rainRate p_dayRain p_weekRain >p_monthRain p_yearRain) columns to the WeeWX database. > - Assuming this is the command: wee_database --add-column=p_rain > etc. >- Update skin.conf stanzas [DisplayOptions] and [CheetahGenerator] >adding p_rainX where I see the rainX variables . > > Is there a way to map the p_rainX variables to the standard rainX variables > to avoid having to do all of this manual config? > > Thanks for your help. > > Thanks, > Arthur > -- 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/38168a2f-a9b1-45eb-a918-ce690a455a5dn%40googlegroups.com.
Re: [weewx-user] Re: WDC Skin
*I copied over my up weewx db (data from mid 2020 to present) and it takes about ~180 sec* Like the name of the Skin suggests, you will need a Data Center to run the Skin :D Just kidding, the long generation time is on my list, I will see what I can do about it in the coming weeks. See https://github.com/Daveiano/weewx-wdc/issues/14 *I mean kind of like the "about" page on the fuzzy-archer skin, where one can put custom content in it, as it seems there can be more than 1 additional page and menu entry. I'm not sure how it's done, if the page content is written in the skin config directly or if it somehow embeds an additional html page into the content area(?)* I got you. Sounds like a good addition. One could also provide pictures of the station or extreme weather events or whatever. This would personalize the skin for each user, definitely a good Addition. Also added an Issue for that https://github.com/Daveiano/weewx-wdc/issues/15 *Another great thing would be, if the station/hardware info could somehow be overwritten or complemented with an additional info field, if the driver doesn't pass enough information, as it's the case with an SDR setup or the interceptor driver: It just shows "sdr" or "ecowitt-client" instead of, as an example, "WS80 over SDR" or "WS80 with ecowitt-client / GW1000". It would be sufficient if there would just be an additonal customizable text field below "weewx 4.x.x with ecowitt-client" which would show e.g. "Sensor: WSxx" or "Station hardware: WSxx with GW1100". But it should be able to read it out of the weewx.conf, if it can be defined there somehow, because in a multiple instance weewx setup the skin.conf is the same for all instances. But yeah not sure if this makes sense or if it should rather be adressed by weewx itself, I know it's just a little detail but would be neat :)* Like I said in the first post, I'm new to the weewx ecosystem, so everything I write now is speculation: (without further investigation) this sounds more like a Driver issue? The driver should provide the station data to weewx (and the skin). Not sure about adding this as configuration to weewx.conf. I don't know if weewx would support this out of the box. The Extras Section (https://weewx.com/docs/customizing.htm#Extras) inside the skin.conf would be suitable for this, but then you will need to set this for every weewx-wdc installation. I will keep this in mind and do some investigation. tarob...@gmail.com schrieb am Samstag, 4. Juni 2022 um 01:07:16 UTC+2: > Ran this on my test rpi (simulator mode) with data going back to late Dec > 2021. Took about ~70 secs to generate WdcReport. I copied over my up weewx > db (data from mid 2020 to present) and it takes about ~180 sec to generate > a WdcReport. Any ways to optimize the reports to get the report generation > time down? For comparison, takes less than a sec for SeasonsReport. > > On Friday, June 3, 2022 at 10:38:06 AM UTC-4 f4n...@gmail.com wrote: > >> *Thank you for all these suggestions and feedback! I really like the idea >> of an Classic/Alternative Layout switch, btw :)* >> >> Glad you like my feedback and ideas! This will be a great feature, >> customization is everything imo >> >> *You mean station info/news content as a configurable menu link to let >> the user link to any generated Blog/News/whatever page, right?* >> >> I mean kind of like the "about" page on the fuzzy-archer skin, where one >> can put custom content in it, as it seems there can be more than 1 >> additional page and menu entry. I'm not sure how it's done, if the page >> content is written in the skin config directly or if it somehow embeds an >> additional html page into the content area(?) >> >> Another great thing would be, if the station/hardware info could somehow >> be overwritten or complemented with an additional info field, if the driver >> doesn't pass enough information, as it's the case with an SDR setup or the >> interceptor driver: It just shows "sdr" or "ecowitt-client" instead of, as >> an example, "WS80 over SDR" or "WS80 with ecowitt-client / GW1000". It >> would be sufficient if there would just be an additonal customizable text >> field below "weewx 4.x.x with ecowitt-client" which would show e.g. >> "Sensor: WSxx" or "Station hardware: WSxx with GW1100". But it should be >> able to read it out of the weewx.conf, if it can be defined there somehow, >> because in a multiple instance weewx setup the skin.conf is the same for >> all instances. But yeah not sure if this makes sense or if it should rather >> be adressed by weewx itself, I know it's just a little detail but would be >> neat :) >> >> >> >> david@gmail.com schrieb am Mittwoch, 1. Juni 2022 um 01:08:26 UTC+2: >> >>> *So the spacing can be predefined, but not the graph and font on the >>> cards/tiles size? If so, yeah maybe you can do something with the spacing >>> or the possibility to move "current weather conditions" into the left me
