Many thanks for taking the time to help me get this mess ironed out :)
Indeed I forgot to mention that a problem with the wind sensor is ruled out
since I can read the values on the GW2000 module direct web interface (and
the normal non gust values were indeed looped and recorded fine, just gust
missing). The main station is indeed the ecoWitt GW2000 (I have no console,
this GW2000 is the only radio collection point for the wind/rain/outdoor
temps).The second station (WMR100) I only use for indoor temperatures, its
wind and rain sensors are permenantly disconnected, but really need those
indoor temps because they are used to control my pellet stove heating...
I think I tried all possible combinations, and in the end the only way to
get the gust speed and dir recorded in the database is to use the weewx
GW1000 class in "driver" mode (as oppsosed to a "service" together with
the WMR100 as "driver"). This works with the original code in the current
git master, no hacking required.
So in the end I have solved this issue by otping for a dual weewx daemon,
one for each station both in "driver" modes. The WMR100 daemon just records
the "in" temperatures to its archive and nothing else, the GW1000 records
all the ecoWitt sensors and also generates the reports.
The alternative would have been to extend the WMR100 class to include a
"service" mode, which given the apparent simplicity of the code might be
doable. But given the unreliability of the USB WMR100 feed, I'll just get
some more ecoWitt temp sensors and in due time retire the WMR alltogether.
[issue solved]
Alltogether great code by the way, kudos ! Even got so far as to convince
me Python does have some neat advantages over the other scripting languages
I tend to use :)
Kind regards
On Wednesday, 23 November 2022 at 21:58:40 UTC+1 lang....@googlemail.com
wrote:
> I suggest a systematic step-by-step error detecting approach here
> including a few question beforehand:
>
> - what do the GW2000 WebUI/WS View Plus app and ecowitt.net show for wind
> observations ?
> - what do you see if you run the Ecowitt Gateway driver (GW1000 API) alone
> without the USB weewx.drivers.wmr100 (with an unmodified GW1000.py) ?
>
> also, your terminology is not clear - a GW2000 station (by definition:
> station = console + sensors) does not exist
> there is a GW2000 console (gateway), there is a GW2001 station (=GW2000
> console + WS90 sensor array)
>
> what you seem to have is a GW2000 console/gateway with a WS68 outdoor
> sensor array, a WH32 outdoor T/H sensor and a WH40 rain gauge connected
> (from your syslog)
> So, to repeat the question from above - what does the WS68 report to the
> console/gateway ? (--> WSView Plus app/GW2000 WebUI)
> What does it report to the Ecowitt cloud (assuming you have an account
> with ecowitt.net and have your GW2000 registered there) ?
>
> If the phenomenon occurred after/during a strong wind event, the WS68
> array may need a reset.
> The GW2000 console may need a reset (center button 5-9 seconds presed
> down).
>
> I would first check all this before starting fiddling with the weewx
> driver software.
> Before we look into the software, we have to make sure the hardware is
> working properly.
> if the hardware works fine, have a look into the original (not modified)
> drivers alone and see what it gives (=what weewx shows/saves into the DB
> and shows in the Seasons skin).
>
> If the single components work properly alone, then look into your
> modifications.
> Make modifications one by one - otherwise you won't be able to tell what's
> the cause of unwanted behavior.
> Always keep backup copies of your original configuration files
> (weewx.conf, skin.conf, index.html.tmpl + .inc files) - for comparison and
> for replacement if necessary.
>
> Right now things look sort of messed up so imho only a systematic approach
> will help here (or a lucky shot into the blue).
>
>
>
> On 23.11.2022 19:36, Pascal Hingamp wrote:
>
> In order to test if the issue is with the GW1000 driver or the weewx
> configuration, I modified the gw1000.py driver to internally create a
> windGustDir key/value pair each time a windDir key/value appears in a loop
> (copying the windDir value).
>
> From the log below, this moded driver results in the windGustDir now
> appearing in the mapped data. But the windGust and windGustDir are still
> not being stored in the database records.
>
> Am I correct in assuming this means the issue lies in the weewx.conf
> configurations, which somehow I must have broken in a such a way that wind
> gust values are no longer recorded, even when both Speed and Dir are
> present in LOOP packets. I'm attaching my full weewx.conf file.
>
> Nov 23 19:15:42 raspi weewx[7769] INFO user.gw1000: GatewayService:
> Processing loop packet: 2022-11-23 19:15:42 CET (1669227342) {'dateTime':
> '1669227342', 'extraBatteryStatus0': '1', 'extraHumid0': '41.0',
> 'extraTemp0': '25.8', 'usUnits': '16'}
> Nov 23 19:15:42 raspi weewx[7769] INFO user.gw1000: GatewayService:
> Received queued *sensor data*: 2022-11-23 19:15:27 CET (1669227327)
> {'absbarometer': '968.0', 'annual_reset': '0', 'datetime': '1669227327',
> 'day_reset': '0', 'daymaxwind': '10.7', '*gustspeed*': '5.1', 'inhumid':
> '81', 'intemp': '10.6', 'light': '0.0', 'outhumid': '85', 'outtemp':
> '10.0', 'rain_source': '1', 'relbarometer': '968.0', 'soilmoist1': '27',
> 'soilmoist2': '50', 't_rainday': '0.0', 't_rainevent': '0.0', 't_rainhour':
> '10.0', 't_rainmonth': '7.5', 't_rainrate': '0.0', 't_rainweek': '5.4',
> 't_rainyear': '7.5', 'uv': '0.0', 'uvi': '0', 'week_reset': '0',
> 'wh32_batt': '0', 'wh32_sig': '4', 'wh40_batt': '1.45', 'wh40_sig': '4',
> 'wh51_ch1_batt': '1.6', 'wh51_ch1_sig': '4', 'wh51_ch2_batt': '1.5',
> 'wh51_ch2_sig': '4', 'wh68_batt': '1.84', 'wh68_sig': '4', '*winddir*':
> '284', '*windspeed*': '2.9'}
> Nov 23 19:15:42 raspi weewx[7769] DEBUG weewx.manager: Daily summary
> version is 4.0
> Nov 23 19:15:42 raspi weewx[7769] INFO user.gw1000: GatewayService: No
> queued items to process
> Nov 23 19:15:42 raspi weewx[7769] INFO user.gw1000: GatewayService: *Mapped
> GW2000 data*: {'batteryStatus3': '1.6', 'batteryStatus4': '1.5',
> 'daymaxwind': '10.7', 'dayRain': '0.0', 'extraHumid3': '81', 'extraTemp3':
> '10.6', 'luminosity': '0.0', 'monthRain': '7.5', 'outHumidity': '85',
> 'outTemp': '10.0', 'outTempBatteryStatus': '0', 'pressure': '968.0',
> 'rain': '0.0', 'rainBatteryStatus': '1.45', 'rainRate': '0.0',
> 'relbarometer': '968.0', 'signal1': '4', 'signal2': '4', 'signal3': '4',
> 'signal4': '4', 'signal5': '4', 'soilMoist1': '27', 'soilMoist2': '50',
> 'stormRain': '0.0', 'usUnits': '17', 'UV': '0', 'uvradiation': '0.0',
> 'weekRain': '5.4', 'windBatteryStatus': '1.84', '*windDir*': '284', '
> *windGust*': '5.1', '*windGustDir*': '284', 'windSpeed': '2.9',
> 'yearRain': '7.5'}
> Nov 23 19:15:42 raspi weewx[7769] INFO user.gw1000: GatewayService:
> Mapped data will be used to augment loop packet(2022-11-23 19:15:42 CET
> (1669227342))
> Nov 23 19:15:42 raspi weewx[7769] INFO user.gw1000: GatewayService:
> *Converted
> GW2000 data*: {'batteryStatus3': '1.6', 'batteryStatus4': '1.5',
> 'daymaxwind': '10.7', 'dayRain': '0.0', 'extraHumid3': '81', 'extraTemp3':
> '10.6', 'luminosity': '0.0', 'monthRain': '0.75', 'outHumidity': '85',
> 'outTemp': '10.0', 'outTempBatteryStatus': '0', 'pressure': '968.0',
> 'rain': '0.0', 'rainBatteryStatus': '1.45', 'rainRate': '0.0',
> 'relbarometer': '968.0', 'signal1': '4', 'signal2': '4', 'signal3': '4',
> 'signal4': '4', 'signal5': '4', 'soilMoist1': '27', 'soilMoist2': '50',
> 'stormRain': '0.0', 'UV': '0', 'uvradiation': '0.0', 'weekRain': '5.4',
> 'windBatteryStatus': '1.84', '*windDir*': '284', '*windGust*': '18.36', '
> *windGustDir*': '284', 'windSpeed': '10.44', 'yearRain': '0.75'}
> Nov 23 19:15:42 raspi weewx[7769] INFO user.gw1000: *GatewayService:
> Augmented packet*: 2022-11-23 19:15:42 CET (1669227342)
> {'batteryStatus3': '1.6', 'batteryStatus4': '1.5', 'dateTime':
> '1669227342', 'daymaxwind': '10.7', 'dayRain': '0.0',
> 'extraBatteryStatus0': '1', 'extraHumid0': '41.0', 'extraHumid3': '81',
> 'extraTemp0': '25.8', 'extraTemp3': '10.6', 'luminosity': '0.0',
> 'monthRain': '0.75', 'outHumidity': '85', 'outTemp': '10.0',
> 'outTempBatteryStatus': '0', 'pressure': '968.0', 'rain': '0.0',
> 'rainBatteryStatus': '1.45', 'rainRate': '0.0', 'relbarometer': '968.0',
> 'signal1': '4', 'signal2': '4', 'signal3': '4', 'signal4': '4', 'signal5':
> '4', 'soilMoist1': '27', 'soilMoist2': '50', 'stormRain': '0.0', 'usUnits':
> '16', 'UV': '0', 'uvradiation': '0.0', 'weekRain': '5.4',
> 'windBatteryStatus': '1.84', '*windDir*': '284', '*windGust*': '18.36', '
> *windGustDir*': '284', 'windSpeed': '10.44', 'yearRain': '0.75'}
> Nov 23 19:15:43 raspi weewx[7769] DEBUG user.gw1000: Next update in 15
> seconds
>
> --
> 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/f45a0e44-6cd3-47b1-8a97-51e01ccd887en%40googlegroups.com
>
> <https://groups.google.com/d/msgid/weewx-user/f45a0e44-6cd3-47b1-8a97-51e01ccd887en%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/0a295511-11fd-45b8-b0f1-14a0b10733a1n%40googlegroups.com.
