The nuance here is mihec wants to use the Ecowitt temperature as the
primary outTemp yet (seemingly) wants to use the Vue for everything else.
That's a bit unusual.
I think I'd edit the skin(s) that generate the NOAA reports after forking
them to new names. Save the diffs as a patch that can be reapplied to
future updates of whatever skin(s) have the NOAA report templates. I can
only think of Seasons, Standard, and Belchertown (original or new) as skins
that do that.
I use MQTT here but I do 'not' supersede which data is in
outTemp/outHumidity so each instance has its own NOAA data, but here's my
MQTT stanzas for doing that. Setting up a mosquitto MQTT broker on the
weewx box is easy to do.
# the Ecowitt instance publishes
[[MQTT]]
client_id = ecowitt
server_url = mqtt://192.168.1.69:1883/
topic = ecowitt
log_success = false
log_failure = true
enable = true
# the Vantage instance subscribes
[MQTTSubscribeService]
enable = true
host = 192.168.1.69
port = 1883
keepalive = 60
username = None
password = None
binding = loop
[[message_callback]]
type = json
[[topics]]
unit_system = US
ignore_start_time = True
ignore_end_time = True
[[[ecowitt/loop]]]
[[[[outTemp_F]]]] # outside ecowitt
name = extraTemp1 # save ecowitt temp to vantage instance's
extraTemp1
units = degree_F
On Friday, August 14, 2026 at 12:10:49 PM UTC-7 Tom Keffer wrote:
> There are several ways of accomplishing this.
>
> The simplest is just to run two different WeeWX instances, one for the
> Vantage, one for the Ecowitt. This will result in two different databases.
> Then combine them into one report. See the section *Using multiple
> bindings <https://www.weewx.com/docs/5.5/custom/multiple-bindings/>* in
> the documentation.
>
> Another approach is as you say: write a service that extracts what data
> you want from the Ecowitt. This will require running a separate thread that
> does the data acquisition from the Ecowitt so as not to block the main
> thread.
>
> Run two instances and have them both publish to MQTT. Then run a third
> instance that subscribes to the MQTT broker and let it produce the reports.
>
> There are lots of possibilities!
>
> -tk
>
>
> On Fri, Aug 14, 2026 at 3:05 AM mihec <[email protected]> wrote:
>
>> Hi,
>> I have 10+ years database from Davis Vantage Vue which is still working
>> well. I'm going to add a Ecowitt temperature & humidity sensor which will
>> be placed to a more appropriate location (Vue is installed rooftop...).
>> I'd like to log the Ecowitt's temperature as the main temperature
>> (outTemp) and Davis as the extra one. Is this feasible? If not, I can still
>> log Ecowitt as the extraTemp. Then I'd need to change the NOAA reports
>> properly.
>>
>> What would be the right way to access data from Ecowitt? I should
>> probably leave the station as Davis and add a service that reads the
>> Ecowitt's data from a file?
>>
>> Thanks for any hint.
>>
>> --
>> 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/e455744c-29e2-47be-a99f-d9dca8332bb5n%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/weewx-user/e455744c-29e2-47be-a99f-d9dca8332bb5n%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/b60b91ba-f057-4e66-85d9-bb09a0e3309en%40googlegroups.com.
