>
> I ended up going with John's fork for the publish

Since I renamed the extensiom to avoid confusion, and so the extension I
forked from can live harmoniously you will need to change [MQTTPublish] to
[MQTTPublisV2] if/when you install a newer version.

On Wed, 8 Jul 2026 at 22:36, [email protected] <[email protected]> wrote:

> Hey guys I think I figured everything out.  I ended up going with John's
> fork for the publish and got it working.  I also installed his aggregator
> extension but haven't ventured into it yet.  Thanks for all your help
> gentleman.
>
> On Wednesday, July 8, 2026 at 7:45:42 a.m. UTC-4 [email protected] wrote:
>
>> Calculating aggregates was a poor example. If one needs to do that I
>> would recommend using your extension and either MQTTPublish or Matthew’s
>> MQTT extension to publish to MQTT.
>> But, I do see a potential need to not publish as frequently for some MQTT
>> clients….
>> rich
>>
>> On Tuesday, 7 July 2026 at 14:43:24 UTC-4 John Smith wrote:
>>
>>> I am looking at adding an option to publish once per day, week, month.
>>>> This could be useful for expensive, rarely changing computations.
>>>
>>>
>>> Or you could do what I did, calc once and then cache to both ram and the
>>> storage, until and update is needed and only re-calc what needs to be
>>> re-calced...
>>>
>>> On Wed, 8 Jul 2026 at 01:13, [email protected] <[email protected]>
>>> wrote:
>>>
>>>> As John noted, he has an extension to perform aggregates that can be
>>>> used in tandem with this. Or you could use the built-in aggregate function
>>>> of MQTTPublish.
>>>> I am looking at adding an option to publish once per day, week, month.
>>>> This could be useful for expensive, rarely changing computations.
>>>> rich
>>>>
>>>>
>>>> On Tuesday, 7 July 2026 at 10:17:26 UTC-4 [email protected] wrote:
>>>>
>>>>> Appreciate it thanks.  So you mean I have to include every variable in
>>>>> the stanza and then toggle the ignore flag for each one, or can I just
>>>>> include the values I want?  I'm posting individual archive entries and 
>>>>> will
>>>>> probably want the aggregate ones for day/week/month/year kind of thing.  
>>>>> Is
>>>>> that possible?
>>>>>
>>>>> On Tuesday, July 7, 2026 at 9:42:34 a.m. UTC-4 John Smith wrote:
>>>>>
>>>>>> I posted a working snippet when I made a PR
>>>>>>
>>>>>>
>>>>>> https://github.com/weewx-mqtt/publish/pull/15/changes/90f1473887deef1459cd647e3aaae129a6caf5f1
>>>>>>
>>>>>> However I realised how inefficient it was trying to include or
>>>>>> exclude things like that and have since come up with a fork that loops in
>>>>>> the python script instead of repeating the same things lots and lots of
>>>>>> times as seen at that link
>>>>>>
>>>>>> My fork can be found here:
>>>>>> https://github.com/evilbunny2008/MQTTPublish
>>>>>>
>>>>>> Here's an example stanza for that extension
>>>>>> https://github.com/evilbunny2008/MQTTPublish/blob/main/weewx-sample.conf
>>>>>>
>>>>>> However I shifted all the aggregate functionality into it's own
>>>>>> extension so that values could be calculated once per archive interval 
>>>>>> and
>>>>>> then all other extensions could access the values
>>>>>>
>>>>>> That extension can be found here
>>>>>> https://github.com/evilbunny2008/AggregatedValues
>>>>>>
>>>>>> I'm half way through migrating the Inigo plugin to use the values
>>>>>> calculated and so when the work on the Inigo plugin is complete both it 
>>>>>> and
>>>>>> the MQTTPublish extension will do almost no DB lookups and I'm already
>>>>>> seeing a significant reduction in the time to generate multiple reports.
>>>>>>
>>>>>> On Tue, 7 Jul 2026 at 23:13, [email protected] <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>>> I'm having a heck of a time even finding an example of how to format
>>>>>>> the stanza to publish topics under the [[MQTT]] section under the
>>>>>>> [StdRESTful] section.
>>>>>>>
>>>>>>> I have successfully installed this service and I see it load on
>>>>>>> startup:
>>>>>>> https://github.com/weewx-mqtt/publish
>>>>>>>
>>>>>>> I just wish there was a sample config to follow but that seems to be
>>>>>>> non-existent.  I don't know where to nest things.  I'm posting 
>>>>>>> individual
>>>>>>> topics so can someone post an example that works?
>>>>>>>
>>>>>>> --
>>>>>>> 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/c3cc4816-4fbc-46c7-b793-33f89b48b53an%40googlegroups.com
>>>>>>> <https://groups.google.com/d/msgid/weewx-user/c3cc4816-4fbc-46c7-b793-33f89b48b53an%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/f4c519b4-6de3-4632-9a6d-96af828fac46n%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/weewx-user/f4c519b4-6de3-4632-9a6d-96af828fac46n%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/b57991e9-e7c4-4487-a750-b4b1cc8c18d7n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/b57991e9-e7c4-4487-a750-b4b1cc8c18d7n%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/CAGTinV6mZaLTxbV54f%2BcD_M-zDsAhau1eN84Awn3%2BdCtycgk9g%40mail.gmail.com.

Reply via email to