weewx-ecowitt_local_http -- no releases directory

[NotThePainter]

New weewx user here. I'm trying to install the Local HTTP driver to talk to my Ecowitt GW3000, but the releases folder is empty.

Am I looking in the wrong place? The weewx-ecowitt_local_http really looks like the driver I want to use.

Thanks!

[John Smith]

Am I looking in the wrong place?

 

Not a clue, you didn't post a URL...

[vince]

Looks like Ian needs to tag the relocated repo.

Try 'weectl extension install https://github.com/weewx-contrib/weewx-ecowitt_local_http/archive/refs/heads/main.zip' 

[NotThePainter]

On Sunday, 4 January 2026 at 18:36:04 UTC-5 vince wrote:

Looks like Ian needs to tag the relocated repo.

Try 'weectl extension install https://github.com/weewx-contrib/weewx-ecowitt_local_http/archive/refs/heads/main.zip' 

Thanks, that’s perfect. I’ll give it a try tomorrow.

 

[NotThePainter]

I've installed the driver

% weectl extension install https://github.com/weewx-contrib/weewx-ecowitt_local_http/archive/refs/heads/main.zip --config ~/Documents/WeeWX/weewx-data/weewx.conf
Using configuration file /Users/pcezanne/Documents/WeeWX/weewx-data/weewx.conf
Install extension 'https://github.com/weewx-contrib/weewx-ecowitt_local_http/archive/refs/heads/main.zip' (y/n)? y
Extracting from zip archive /var/folders/f_/47j91mxx1lv_h74_c4b829kw0000gn/T/tmpuqrlog2i
Saving installer file to /Users/pcezanne/Documents/WeeWX/weewx-data/bin/user/installer/Ecowitt_HTTP
Saved copy of configuration as /Users/pcezanne/Documents/WeeWX/weewx-data/weewx.conf.20260106172143
Finished installing extension Ecowitt_HTTP from https://github.com/weewx-contrib/weewx-ecowitt_local_http/archive/refs/heads/main.zip

And I go to reconfigure to use it (I created the station with the Simulator)

 % weectl station reconfigure --driver=user.ecowitt_local_http --config ~/Documents/WeeWX/weewx-data/weewx.conf
 
....

Choose a unit system for the reports. Later, you can modify
your choice, or choose a combination of units. Unit systems
include:
  us         (ºF, inHg, in, mph)
  metricwx   (ºC, mbar, mm, m/s)
  metric     (ºC, mbar, cm, km/h)
unit system [us]:
Traceback (most recent call last):
  File "/Users/pcezanne/weewx-venv/bin/weectl", line 7, in <module>
    sys.exit(main())
  File "/Users/pcezanne/weewx-venv/lib/python3.9/site-packages/weectl.py", line 67, in main
    namespace.func(namespace)
  File "/Users/pcezanne/weewx-venv/lib/python3.9/site-packages/weectllib/__init__.py", line 90, in dispatch
    namespace.action_func(config_dict, namespace)
  File "/Users/pcezanne/weewx-venv/lib/python3.9/site-packages/weectllib/station_cmd.py", line 311, in reconfigure_station
    weectllib.station_actions.station_reconfigure(config_dict=config_dict,
  File "/Users/pcezanne/weewx-venv/lib/python3.9/site-packages/weectllib/station_actions.py", line 164, in station_reconfigure
    config_config(config_dict,
  File "/Users/pcezanne/weewx-venv/lib/python3.9/site-packages/weectllib/station_actions.py", line 207, in config_config
    config_driver(config_dict, driver=driver, no_prompt=no_prompt)
  File "/Users/pcezanne/weewx-venv/lib/python3.9/site-packages/weectllib/station_actions.py", line 424, in config_driver
    driver_editor, driver_name, driver_version = weecfg.load_driver_editor(final_driver)
  File "/Users/pcezanne/weewx-venv/lib/python3.9/site-packages/weecfg/__init__.py", line 453, in load_driver_editor
    driver_module = importlib.import_module(driver_module_name)
  File "/usr/local/Cellar/python@3.9/3.9.1_6/Frameworks/Python.framework/Versions/3.9/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 984, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'user.ecowitt_local_http'

I'm missing something. Here's what's installed:

% ls ~/Documents/WeeWX/weewx-data/bin/user/installer                                                          

Ecowitt_HTTP
% ls ~/Documents/WeeWX/weewx-data/bin/user                                                                    

__init__.py __pycache__ ecowitt_http.py extensions.py installer

Thanks for all your help, the station is almost up and running!

[Vince Skahan]

Super-odd paths there so I suspect your venv is incorrect. Looks like it called a brew installed python but I suspect your venv python is using the os version (?).  No reason to not use the os python for the venv on a mac if your os is reasonably current.

[NotThePainter]

OS isn’t current, it is Ventura MacOS13 and I don’t want to upgrade. (I need the machine to upgrade my Garmin GPS and their software doesn’t see my GPS on MacOS14).

I have weewx-data installed in ~/Documents because I want those files backed up to iCloud.

The weewx-venv is installed in "/Users/pcezanne/weewx-venv” because that is NOT an iCloud backed folder. This mac, a laptop, will be operated lid-closed and unattended. I need the weewx-venv to be on a local drive and I need weewx-data to be “backed up” to the cloud.

So yeah, weird, but it makes sense.

As for the python…

(weewx-venv) pcezanne@Pauls-TB-Mac ~ % which python
/Users/pcezanne/weewx-venv/bin/python
(weewx-venv) pcezanne@Pauls-TB-Mac ~ % /Users/pcezanne/weewx-venv/bin/python --version
Python 3.9.1

[Vince Skahan]

Sure, makes sense.  It turns out my mini does have python via homebrew so I recreated your error here.  Once.  Then I decided to start over and deleted weewx-data, recreated it, installed the driver, and your error went away.  Ugh.

When I try to reconfigure the driver, all the queries it asks (hate those) blows up because I have no rain sensor here and it 'really' wants to find one. If I comment out the do_rain( ) call in the driver it gets past that and does reconfigure things.   Unfortunately there is no documentation at all that I can find for this one since Gary went off the net.

Geez that driver is absolutely horrid under the hood.  Like really convoluted.

I'd suggest just running the good'ol simpler and reliable GW1000 driver and skipping the catchup feature the GW3000 supports for now, unless Ian chimes in with a better idea...