I looked at the code for bin/user/ecowitt_http.py and it definitely wants to see an api_key in your weewx.conf file for its catchup/backfill code. No way around it that I can see if you want to use that driver. Unfortunately it's not documented in the legacy instructions and Gary's wiki was lost to the sands of time when he went dark and deleted all his stuff on github in early June.
If you can live without backfill just use the gw1000 driver. On Thursday, January 15, 2026 at 12:27:34 PM UTC-8 NotThePainter wrote: > On Thursday, 15 January 2026 at 13:08:59 UTC-5 Vince Skahan wrote: > > > If you can do so, I'd basically start over on the station setup: > > - rename your weewx-data directory to move it aside > - run 'weectl station create --noprompt' to create a new one using the > Simulator > - add the driver you want via 'weectl extension install' > - run 'weectl station reconfigure' to pick the added driver > - answer the questions it'll ask you re: the ip address of your > gateway etc. > - test your setup re: the driver's readme file instructions > > Lastly remember your odd location of weewx.conf means you will always need > to specify where to find the config file in any weectl or weewxd commands. > If you don't do that they'll look in the normal locations (which > presumably are not present) and you'll get file-not-found or > module-not-found etc. type errors. > > > I went with option #2, Gary's later development hosted at > https://github.com/weewx-contrib/weewx-ecowitt_local_http > > I also went with your very astute advice, and nuked everything, and paid > very special attention to making sure my strange paths were used. > > % rm -rf ~/weewx-data ~/Documents/WeeWX/weewx-data > % mkdir -p ~/Documents/WeeWX/weewx-data > % cd ~/Documents/WeeWX > % weectl station create ~/Documents/WeeWX/weewx-data > > so far, so good! > > % weectl extension install > https://github.com/weewx-contrib/weewx-ecowitt_local_http/archive/refs/heads/main.zip > > --config ~/Documents/WeeWX/weewx-data/weewx.conf > > The install ran successfully. This was the only configure line to run > without error: > > weectl station reconfigure --driver=user.ecowitt_http --config > ~/Documents/WeeWX/weewx-data/weewx.conf > > Lets list it out. > > % weectl extension list --config ~/Documents/WeeWX/weewx-data/weewx.conf > > Using configuration file > /Users/pcezanne/Documents/WeeWX/weewx-data/weewx.conf > Extension Name Version Description > Ecowitt_HTTP 0.1.0a28 WeeWX driver for devices supporting the > Ecowitt local HTTP API. > > The driver test also worked, giving me live data: > > % python3 ~/Documents/WeeWX/weewx-data/bin/user/ecowitt_http.py > --test-driver --ip-address=10.0.4.37 --config > ~/Documents/WeeWX/weewx-data/weewx.conf > > 2026-01-15 15:22:23 EST (1768508543): dateTime: 1768508543, dewpoint: 0.0, > feelslike: 0.8888888888888896, inHumidity: 74, inTemp: 2.000000000000001, > outHumidity: 94, outTemp: 0.8888888888888896, pressure: 973.2479568438692, > rainRate: 0.0, relbarometer: 973.2479568438692, t_rainday: 4.064, > t_rainevent: 7.365999999999999, t_rainmonth: 17.018, t_rainweek: 9.398, > t_rainyear: 17.018, usUnits: 17, vpd: 0.406366579057983, wh26_batt: 0, > wh26_sig: 4 > > I was feeling pretty good at this point, let's run it! Sadness, it doesn't > run, still wanting that api_key which shouldn't be in play. > > % weewxd --config ~/Documents/WeeWX/weewx-data/weewx.conf > ... > AttributeError: 'EcowittHttpDriver' object has no attribute 'api_key' > > It was a great suggestion, I did find errors in my unusual paths which > surely would have vexed me down the road, but still joy 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/7fc78a05-e240-48e8-a2fc-15668bb935ecn%40googlegroups.com.
