There are multiple things going on here.
- you have your weewx.conf in an odd place, so every time your run a
weewx command you need to specify --config=/path/to/weewx.conf or equivalent
- there are multiple ecowitt drivers each with different configurations
- (1) the original gw1000 driver is Gary's original one:
- is rehosted at https://github.com/weewx-contrib/weewx-gw1000
- is listed in the wiki as 'gw1000
<https://github.com/Millardiang/weewx-gw1000> - Collect data from
Ecowitt GW1000/GW1100/GW2000'
- does not support any APIs nor keys
- calls itself [GW1000] in weewx.conf
- (2) Gary's later development driver using local http:
- is rehosted
at https://github.com/weewx-contrib/weewx-ecowitt_local_http
- is not listed in the wiki
- does not support any APIs nor keys
- calls itself [EcowittHttp] in weewx.conf
- (3) Werner has an additional driver with a very very manual
procedure to install and configure:
- is listed in the wiki as "ecowitt_http
<https://github.com/WernerKr/Ecowitt-or-DAVIS-stations-and-Season-skin/tree/main/ecowitt_http>
-
Collect data from all Ecowitt gateways/displays which support the http
api.
Can also import data from SDCard (GW3000, WS6210) or from the Ecowitt
Cloud"
- is hosted at
https://github.com/WernerKr/Ecowitt-or-DAVIS-stations-and-Season-skin/tree/main
- DOES need API keys according to its readme file
- unfortunately also calls itself [EcowittHttp] in weewx.conf
stomping on the original one's name yet has much more elaborate
configuration needs
- does not use the extension installer, so I don't know if 'weectl
extension list' or 'weewx station reconfigure' will find i
For a gw3000 gateway:
- you can use the original weewx-gw1000 driver (1) above from Gary and
run without backfill
- or you could use the weewx-ecowitt_local_http driver (2) above
originally from Gary, but I don't know if backfill works or not in that one
- I can't speak to Werner's driver (3) above at all. Personally I find
it so complicated and manual in nature I haven't even tried it. I agree
with you on the API key thing FWIW. The fact that it doesn't use the
extension installer and that it stomps on another driver's name makes it a
no-go for me personally. For me that way lies chaos and confusion.
When you say you tried the weewx-ecowitt_local_http and couldn't get it to
run, you need to provide more data on what you did and what you saw. My
guess is you have junk in your setup from going back and forth.
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.
On Thursday, January 15, 2026 at 9:22:04 AM UTC-8 NotThePainter wrote:
> On Thursday, 15 January 2026 at 09:27:52 UTC-5 Rainer Lang wrote:
>
> I understand what you don't want, but you obviously don't understand what
> that API/APP keys are about.
> It has nothing to do with what you call "your old cloud/push driver",
> probably the Interceptor driver.
>
>
> Anyhow, the 2nd option I mentioned was to have no keys/commented them out.
>
> Maybe you tell us what your station model is 😉.
>
>
>
> Sorry about that, I'm runnig the GW3000 and the get_livedata_info endpoint
> works just fine.
>
> As far as I understand it, the API key is to talk to the Ecowitt server. I
> don't want that at all. My data should stay on my network, I don't need
> somebody elses server. I could be wrong, I'm trying to figure this out and
> it is complicated until it isn't. :- )
>
> Gary's approach seems to be a modern, robust archicture and I'd like to
> use that. The code at
> https://github.com/weewx-contrib/weewx-ecowitt_local_http?tab=readme-ov-file
> seems to be a fork of that. I just can't get it to run.
>
> And I don't have any keys mentioned at all in my conf file, that's what's
> weird.
>
>
--
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/86db2427-9fca-4405-bf45-ea43ed7f3688n%40googlegroups.com.
