I have a strong preference for publishing observation packets under a single timestamp. Not only is it more efficient, but they make a natural semantic group, as they all come from the same source.
This is what WeeRT does. -tk On Sun, Aug 7, 2016 at 5:05 AM, mwall <[email protected]> wrote: > On Sunday, August 7, 2016 at 1:25:08 AM UTC-4, Siegfried H. wrote: >> >> >> you'll have to write a driver to talk to the esp8266 >>> >> >> Okay, then I was on the wrong track: I thought because my weather data is >> already published from the esp8266 to the mqtt broker (and from there into >> openHAB) I could simply use the weewx mqtt extension for *inputting* >> this data into weewx. >> But it looks like the weewx mqtt extension is only able to >> *output/publish* data to the mqtt broker (I tried that and it works fine) >> > > siegried, > > i had not considered that approach! an mqtt driver that feeds weewx with > data from any mqtt broker would useful for many use cases. > > i have seen two general approaches: (1) publish each observation, e.g., > /telemetry/outside_temperature with data 32.3, or (2) publish a group of > observations as json data, e.g., /telemetry/weather/loop with data > {'outside_temperature': 32.2, 'outside_humidity': 42, 'pressure': 1011.2} > > what topic structure does openhab expect? > > what other mqtt topic topologies have you seen? > > m > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
