My Oregon WMR300 is still happily chugging away generating weather data and 
I thought I'd augment it with some air-quality sensors.
The easiest in my situation seemed to be an Ecowitt WH45 CO2/particle 
sensor with a GW1100 gateway, and a WH31 temp/RH sensor thrown in for 
almost nothing.
So my new system reports:
1 x barometer
3 x temperature
3 x humidity
1 each  CO2, PM2.5, PM10.
sundry battery and signal strengths

One of my requirements is to have some plots containing data from both 
systems on the one chart.

There seem to be two choices for driver - the Ecowitt (GW1000) and the 
interceptor. Are there any strong reasons to choose one over the other?

There also seem to be two choices for implementation:
1. using weewx_multi and keep everything separate.  Then use the multiple 
binding technique in one skin to incorporate all data in a single report.
2. use the GW1000 code *as a service* in a single instance of weewx, with a 
single database.

The second method seems in some ways simpler, but am I right in thinking I 
would need to remap many of the names to avoid clashes with data from the 
WMR300?

If I choose weewx_multi  - is there a suitable systemd unit file I can use 
as a template?

Thanks.
Cameron.

-- 
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 on the web visit 
https://groups.google.com/d/msgid/weewx-user/5b5b227f-59e7-4c78-b0a6-7a7906ec7633n%40googlegroups.com.

Reply via email to