No change, I will only see the long formatted json that I showed in the
initial thread when i set it to aggregation = aggregate
Based on documents:
*aggregation* - How the observations should be grouped. Options are
individual and/or aggregate. When individual is specified, each observation
is sent as a separate MQTT message. When aggregate is specified, all
observations are sent in a single, JSON-formatted message. *Default is
**individual,
aggregate, i.e., send a message for each observation as well as an
aggregate message with all observations.*
Any other ideas? Can anyone confirm if they have individual MQTT working?
That's what I am ultimately trying to accomplish.
I am using the weewx-sdr driver, and with each message it gets from that
driver, it is receiving json strings, so I wonder if the MQTT extension is
expecting the measurements to be individual and not long json strings to
begin with? Otherwise I can see about parsing the json strings, but would
like to avoid that if possible.
On Thursday, March 7, 2019 at 9:23:36 PM UTC-5, Pat wrote:
>
> What happens if you change it to aggregation = aggregate ?
>
> On Thursday, March 7, 2019 at 2:21:21 PM UTC-5, bdf0506 wrote:
>>
>> I'm having an issue getting the MQTT extension to output the correct
>> information when aggregation is set to individual. See below config.
>>
>> [[MQTT]]
>> server_url = mqtt://user:pass@server:1883/
>> topic = weewx
>> aggregation = individual
>> binding = loop
>>
>> When I look at my broker (using mosquitto), it is showing the following:
>>
>> [root@server ~]$ mosquitto_sub -v -t weewx/#
>> weewx/hourRain_in 0.0
>> weewx/rain24_in 0.0
>> weewx/hourRain_in 0.0
>> weewx/hourRain_in 0.0
>> weewx/BatteryStatus 0.0
>> weewx/BatteryStatus 0.0
>> weewx/BatteryStatus 0.0
>>
>> Now, if I comment out the aggregation item in the config, then it shows
>> the following:
>>
>> [root@server ~]$ mosquitto_sub -v -t weewx/#
>> weewx/loop {"rain24_in": "0.0", "hourRain_in": "0.0", "LivingRoomTemp_F":
>> "69.44", "rainRate_inch_per_hour": "0.0", "dateTime": "1551985428.0",
>> "dayRain_in": "0.0", "usUnits": "1.0", "LivingRoomHumidity": "34.0"}
>> weewx/loop {"hourRain_in": "0.0", "rain24_in": "0.0",
>> "rainRate_inch_per_hour": "0.0", "dateTime": "1551985436.0", "dayRain_in":
>> "0.0", "CrawlSpaceHumidity": "41.0", "CrawlSpaceTemp_F": "62.6", "usUnits":
>> "1.0"}
>> weewx/loop {"BatteryStatus": "0.0", "hourRain_in": "0.0",
>> "windSpeed_mph": "0.0", "rain24_in": "0.0", "rainRate_inch_per_hour":
>> "0.0", "dateTime": "1551985441.0", "dayRain_in": "0.0", "rain_in": "0.0",
>> "rain_total": "114.27", "usUnits": "1.0"}
>> weewx/loop {"BatteryStatus": "0.0", "hourRain_in": "0.0",
>> "windSpeed_mph": "0.0", "rain24_in": "0.0", "rainRate_inch_per_hour":
>> "0.0", "dateTime": "1551985441.0", "dayRain_in": "0.0", "rain_in": "0.0",
>> "rain_total": "114.27", "usUnits": "1.0"}
>> weewx/loop {"BatteryStatus": "0.0", "hourRain_in": "0.0",
>> "windSpeed_mph": "0.0", "rain24_in": "0.0", "rainRate_inch_per_hour":
>> "0.0", "dateTime": "1551985441.0", "dayRain_in": "0.0", "rain_in": "0.0",
>> "rain_total": "114.27", "usUnits": "1.0"}
>>
>> So it would appear that the "individual" aggregation is only grabbing the
>> first measurement from the full json string, and not all individual
>> measurements. Is there something that I am doing wrong in the configuration
>> that is causing this to happen? Or is this maybe a bug in the extension?
>>
>> Thanks
>>
>
--
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.
