after some code inspection (and my understanding of Python) it appears
(see catchup_factory(self) line 4897)
that at weewx startup, if a device with SD card is available under the
IP address from weewx.conf, the EcowittDeviceCatchup class is executed.
If not, provided the API/APP key and MAC address info is available, the
backfill ("catchup") via ecowitt.net is initiated.
So far there is no weewx.conf option available to keep the SD card
backfilling/catchup from being executed.
SD card backfill takes precedence over ecowitt.net backfill.
The ecowitt.net backfill/catchup can be avoided by not providing the
needed info (APP/API keys/MAC).
On 01.07.2025 20:02, Rainer Lang wrote:
the ecowitt.net backfill and the SD card backfill are mutually
exclusive/excluding each other
in addition, the MAC address of the console in question is needed -
also for the SD card download the MAC address is needed
=> a nested setup (as e.g. done in CumulusMX) will make sense
1. activate ecowitt.net by providing MAC, APP and API keys
2. if 1. is activated AND SD card is activated (MAC info available),
then SD card backfill takes priority
=> something like a SD card backfill switch needs to be considered -
more code inspection needed
3. SD card backfill should be possible without providing an APP/API key
also to consider (unless already done --> code inspection):
the ecowitt.net lowest data resolution is 5 minutes, the SD card
resolution (if so chosen) goes down to one minute
=> if you have a 300 second/5 minute archiving interval, the SD card
data might have to run through the loop and accumulation process
for all records whereas from ecowitt.net there is a 1:1 filling of the
loop and archive table ("dictionary").
result: four more switches/options/parameters needed
1. app_key = key
2. api_kep = key
3. mac_address = MAC
4. SD_card = yes/no
On 01.07.2025 18:54, vince wrote:
Quick glance at the code says you need to add "api_key" and "app_key"
to the [EcowittHttp] section in weewx.conf to get around that error
There are also some retries and tunings around line 3944 in the init
routine, but I don't see a setting for "/no catchup vs. this way vs.
that way vs. these multiple ways/" so to speak. There are also debug
settings around line 688 that can be enabled.
But.... if you look around line 3144 it seems to indicate catchup is
not actually in the code at this time. Just the plumbing towards
that goal.
I guess enable all the debugging and do a test and see what happens (?)
--
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/89f016c5-2b15-4f8c-9724-8b580e2d6163n%40googlegroups.com
<https://groups.google.com/d/msgid/weewx-user/89f016c5-2b15-4f8c-9724-8b580e2d6163n%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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/weewx-user/79156d5c-99f1-48fc-96ca-156579ea3c99%40gmail.com.
