Depending on the hardware used, there might be some limitations that apply. 
With my setup, I query multiple consoles from a single Instance, also 
specific consoles are queried from multiple instances running on different 
hardware devices.

To be more specific:
- 5 consoles, 2x GW200, 2x GW3000, 1x ws28xx
- Four WeeWX instances on a n100 Platform (ecowitt gateway driver, ws28xx 
driver)
-- 1 Instance querying the two GW2000
-- 1 Instance for GW2000#1
-- 1 Instance for GW2000#2
-- 1 Instance for ws28xx
- Three WeeWX instances in a containerized ubuntu on a QNAP NAS 
(ecowitt_http driver)
-- 1 Instance querying the two GW3000
-- 1 Instance for GW3000#1
-- 1 Instance for GW3000#2

For each instance I could choose whatever interval I'd be happy with. 
Having Terabytes of storage on this devices, that would be running 24/7 
anyway, I'd definitely go for this most straight forward approach, if I had 
the desire to persist my observations in an 1-minute-interval. I wouldn't 
use an 1-minute-interval with a skin(because the chart look kind of ugly 
for some obs_types), especially not a skin with JS-generated charts, 
because having five times the data points massively impacts the rendering 
performance in the front end.
John Smith schrieb am Mittwoch, 19. November 2025 um 09:08:30 UTC+1:

> On Wed, 19 Nov 2025 at 18:01, '[email protected]' via weewx-user <
> [email protected]> wrote:
>
>> If I wanted to have a 1-minute-interval for occasional looking into data 
>> I'd set up an extra WeeWX instance for it that only stores db values, 
>> without an active skin, beside a standard installation with a 
>> 5-minute-interval.
>>
>
> How would that work?
>
> I thought there could only be 1 connection to a console at a time?
>

-- 
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/33ba2b1d-9dec-4638-b311-6ea81d46bbbcn%40googlegroups.com.

Reply via email to