A couple more thoughts. 1. MQTTSubscribe can be a bit complicated/convulated to configure, so don’t hesitate to reach out with any questions. 2. I do some thing similar to get data into my test environment. Currently if there is a failure (broker down, client down, etc.), data may not make it to the test system. In order to ensure data delivery, I’ve started investigating ‘persistent sessions’ (clean_session = False) and a QOS = 2. I think on the subscribe side it will be that easy - assuming the broker is configured correctly. On the publish side, I’ll probably have to keep track of failed publishes and have some type of retry - not sure I really want to deal with that... -rich
On Tuesday, 2 March 2021 at 13:37:07 UTC-5 [email protected] wrote: > Thanks a lot for the reply, ich will give it a try. > > > I think the best solution ist MQTT an two instances of Weewx. > I´ll come back, if I have more Questions > > Regards > Christian > > [email protected] schrieb am Dienstag, 2. März 2021 um 16:56:32 UTC+1: > >> MQTT on sending side <https://github.com/weewx/weewx/wiki/mqtt> >> MQTT on the receiving side >> <https://github.com/bellrichm/WeeWX-MQTTSubscribe> >> You additionally need an MQTT broker like test.mosquitto.org or you >> install Mosquitto on your Web-Server. The second is the better solution. >> The documentation of the Belchertown skin includes a very good description >> for setting up an MQTT broker >> <https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/>. >> > -- 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/33c8b10d-a067-4e5e-b5d0-f54240330debn%40googlegroups.com.
