On Friday, 16 January 2026 at 07:10:16 UTC-5 steepleian wrote:
For this version of the driver which was Gary’s final version, the API key is most definitely not required and is probably why you are having problems with your weewx.conf. Also the backfill only works when the extension is set up as a driver, it does not work when set up as a service. That is good to know, I'd like to get backfill working locally, it just seems like a cleaner way to do it. Until recently, I did *not* have an API key in my conf, but when I run weewxd it crashes looking for an API key. I'm running this version: Ecowitt_HTTP 0.1.0a28 WeeWX driver for devices supporting the Ecowitt local HTTP API. is that the correct one? I'm starting to think that my code just isn't the right code. I got it from https://github.com/weewx-contrib/weewx-ecowitt_local_http/archive/refs/heads/main.zip which should be the latest, but maybe the latest is broken? Is there a chance you can zip up your driver and send it to me? Quickly reading through this thread, unless I have missed it, I cannot see which device you are using. I have only tested it with a GW3000 which is the only one of the GW series of devices that has the on-board logging to a removable SD card, which is required by this version of the driver for backfill to work. GW3000, no SD card, but I can pop over to Staples and get one today real quick. This is my own working weewx.conf snippet which is working perfectly for me, including backfill (see below link). that looks similar to mine. If you do not have a device with onboard logging, I would, as Vince has suggested, use the GW1000 driver. I really want backfill working. -- 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/9871aac8-54da-4ac2-aa50-ae216b5f3c36n%40googlegroups.com.
