I started down a very similar path, but gave it for a couple of reasons.
1) My station supports hardware generation of the archive.  By 
MQTTSubscribe relying on the loop data, the result is software generation. 
So I wasn’t really ‘replicating’ the data.
2) If something went down, for example the MQTT publisher, there would be a 
gap in the data. 

I experimented/coded up something for 1, but for me 2 was a show stopper 
(my station has a logger - and it has saved me a few times). Just 
somethings to think about.

With the caveats above, I do think only publishing the loop data is what 
you want.
rich

On Tuesday, 9 February 2021 at 13:26:44 UTC-5 Michael wrote:

> Hi Rich,
>
> I think it is now time to describe my goal in more detail.
> There are 2 raspis at 2 different locations in the house that collect 
> data. One raspi has 2 instances and fetches data from a station and via 
> SDR. The other raspi only collects data via SDR. The archive interval is 5 
> minutes.
> Now I want to collect all the data on a separate, somewhat more powerful 
> system and store it in a mysql database. The archive interval should be 60 
> seconds. On this system, 2-3 different skins should be displayed. 
> So I thought it would be a clever solution to collect all data via MQTT 
> and write all data into one database. The first tests worked well until the 
> first rain came and I was missing data.
>
> You have correctly recognised that all instances transmit the data via 
> MQTT, but so far only one instance is received.
> You also correctly recognised that I need the MQTT extension from 
> https://github.com/matthewwall/weewx-mqtt
> for sending. 
> I use the option binding = archive, loop
> I don't remember why I entered this at the time (a few months ago). I 
> think binding = loop should be the right setting for my purpose.
> I tried archive_delay=25 for one day. After I had an entry for rain (1.4mm 
> instead of 0.7mm) in the test database and I understood you to say that 
> this entry only makes sense for archive records, I removed it again.
> I will now take a closer look at Matthew's weewx-mqtt and observe the 
> overall behaviour of my configuration.
>
> Michael
>
>

-- 
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/272df930-47e2-4801-9a93-56b3361f51e4n%40googlegroups.com.

Reply via email to