The topic in the HA section has to exist in the ‘publishing’ section. A HA device can have multiple topics populating the sensors in the device in HA.
MQTTPublish CAN publish. to multiple devices. For example, I have a device with most of my weather sensors and a second device with sensors that monitor indoor air quality, freezer temperature, water sensors, etc. I liked breaking it down this way in HA. No you do not have to create a stanza for each value. On Friday, 10 July 2026 at 16:59:13 UTC-4 [email protected] wrote: > > I think the confusion is, do the topics in both sections have to match? > Also do I create a stanza for each value i want to create an entity in HA? > That seems to not make sense as I understood that this would read every > label and populate HA with entities of each measurement. Is that correct? > On Friday, July 10, 2026 at 3:01:11 p.m. UTC-4 [email protected] wrote: > >> Stripping out all of the comments and extra stuff (which you may or may >> not need). The following “SHOULD” publish the data to REPLACE_ME_TOPIC to a >> broker on your localhost. It should create a device named REPLACE_ME_DEVICE >> in HA. >> >> BUT, I would not start with this. I would start with the template that is >> installed in weewx.conf >> >> >> [MQTTPublish] >> host = localhost >> >> [[topics]] >> [[[REPLACE_ME_TOPIC]]] >> >> >> [[plugins]] >> # The name of the plugin. Do not change >> [[[MQTTHomeAssistantConfig]]] >> # The module to be loaded. Do not change. >> module = user.mqtthaconfig >> >> [[[[devices]]]] >> # The object_id of the device. >> [[[[[REPLACE_ME_DEVICE]]]]] >> >> # The topics for this Device. >> [[[[[[topics]]]]]] >> # The topic name that has the data to be >> published to Home Assistant. >> [[[[[[[REPLACE_ME_TOPIC]]]]]]] >> >> On Friday, 10 July 2026 at 14:32:05 UTC-4 [email protected] wrote: >> >>> I'm definitely struggling with the docs. What do I put in here? I'm >>> using subscribe to populate weather data from my device which publishes to >>> mqtt and the topic is weather/ >>> >>> For this section of the config what do I put in here for the topic? >>> >>> >>> # The topics that source Home Assistant. [[[[[[topics]]]]]] >>> [[[[[[[weather/loop3]]]]]]] # The 'type' of payload. type = individual >>> >>> Am I putting my weather topic in here to input into the HA plugin? >>> On Friday, July 10, 2026 at 2:12:37 p.m. UTC-4 [email protected] wrote: >>> >>>> Sorry. Not surprised…. That is one of the challenges when you make >>>> things highly configurable >>>> That is the default - setting ‘ignore = false’ a the ‘topic level’. >>>> >>>> https://weewx-mqtt.github.io/publish/common-options/topics/topic-name/#ignore >>>> >>>> TLDR: You should not have to do anything. >>>> On Friday, 10 July 2026 at 14:04:57 UTC-4 [email protected] wrote: >>>> >>>>> Quick question. I just want weewx to dump everything into HA to >>>>> create entities. How do I enable the opt-out option with nothing opted >>>>> out? I'm a bit confused on how to do that. >>>>> >>>>> On Friday, July 10, 2026 at 1:42:49 p.m. UTC-4 [email protected] >>>>> wrote: >>>>> >>>>>> >>>>>> I released 1.2.0. This has additional information in the >>>>>> configuration 'template' that hopefully will make it easier for people >>>>>> to >>>>>> under how to configure MQTTPublish. Hopefully after your previous >>>>>> struggles, this should go smoother.After installing my approach would be >>>>>> the following (Unfortunately I don't think running MQTTPublish >>>>>> standalone >>>>>> is ready for use): >>>>>> >>>>>> Enable MQTTPublish and update the MQTT broker for MQTTPublish. >>>>>> Assuming you have a development broker that allows anonymous logins and >>>>>> does not require encryption, you should now be able to publish loop and >>>>>> archive data. Note, I'd update the topic at this time. >>>>>> >>>>>> Restart WeeWX and see if the data is being published. If so, decide >>>>>> if you want to 'opt-in' or 'opt-out'. 'opt-in' means listing the fields >>>>>> that you want to publish. 'opt-out' means listing the fields you don't >>>>>> want >>>>>> to publish. This is your choice. I'd restart WeeWX and make sure every >>>>>> thing is running as expected. >>>>>> >>>>>> Next, I'd move on to getting HA MQTT Device Discovery working. Enable >>>>>> the plugin, provide a device name and the topic to use (this would the >>>>>> one >>>>>> configured above). Restart WeeWX and things should start appearing in >>>>>> Home >>>>>> Assistant. Data "known" to WeeWX should flow in with 'reasonable' >>>>>> configurations. Some of your calculated values might need some >>>>>> additional >>>>>> configuration ( >>>>>> https://weewx-mqtt.github.io/publish/plugins/homeassistantconfig/devices/device-id/component_data/component-id/). >>>>>> >>>>>> We can work through this. >>>>>> >>>>>> Yes, I am slow and methodical. Obviously multiple steps can be done >>>>>> an once and different approaches can be used. >>>>>> If you run into any problems or confusion, let me know. Documentation >>>>>> is far from my strength :) >>>>>> >>>>>> Thanks in advance for your help >>>>>> rich >>>>>> >>>>>> Additional notes: >>>>>> Disclaimer - I am a HA novice >>>>>> If you publish the sensor state data to HA in a json formatted >>>>>> message, HA gets a bit upset if all of the data is not there. >>>>>> MQTTPublish >>>>>> attempts to deal with this, but that might be a problem you run into. >>>>>> I am not a fan of using the retain option. I find it a bit of a pain >>>>>> to reset, especially as one is first getting things working. But, that >>>>>> too >>>>>> is up to you. >>>>>> On Friday, 10 July 2026 at 11:35:04 UTC-4 [email protected] wrote: >>>>>> >>>>>>> That's fantastic Rich, I'll gladly be the guinea pig for this. >>>>>>> >>>>>>> On Friday, July 10, 2026 at 11:33:09 a.m. UTC-4 [email protected] >>>>>>> wrote: >>>>>>> >>>>>>>> I’ve been working on making the ‘configuration template’ more >>>>>>>> explicit - hopefully to make it easier for people to understand how to >>>>>>>> configure. >>>>>>>> Let me create a release with those updates. I’ll post back when it >>>>>>>> is ready to be installed. Shouldn’t take long. >>>>>>>> rich >>>>>>>> >>>>>>>> On Friday, 10 July 2026 at 10:34:19 UTC-4 [email protected] wrote: >>>>>>>> >>>>>>>>> I am interested. I'm trying to get the weewx-home-assistant >>>>>>>>> extension working. It does to some extent but I'm having issues with >>>>>>>>> it >>>>>>>>> not populating certain calculated values. >>>>>>>>> >>>>>>>>> On Wednesday, July 8, 2026 at 3:22:45 p.m. UTC-4 [email protected] >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> I think I now have a handle on some Home Assistant nomenclature >>>>>>>>>> and have created a release of MQTTPublish with beta support for Home >>>>>>>>>> Assistant MQTT Device Discovery. It can be found here, >>>>>>>>>> https://github.com/weewx-mqtt/publish/discussions/24 >>>>>>>>>> >>>>>>>>>> This release is 1.1.0; and can installed via the weectl extension >>>>>>>>>> installer. It also greatly improves the reconnect logic and has some >>>>>>>>>> additional enhancements/fixes to 1.0.1. >>>>>>>>>> >>>>>>>>>> Who might be interested in the Home Assistant Device Discovery? >>>>>>>>>> - Someone knew to integrating Home Assistant and WeeWX. It should >>>>>>>>>> make it easier to get it up and running. Then you can decide to >>>>>>>>>> either dive >>>>>>>>>> deeper into MQTTPublish for more complex configuration options or >>>>>>>>>> switch to >>>>>>>>>> configuring it in Home Assistant. >>>>>>>>>> - Someone who does not enjoy yaml (that would be me). >>>>>>>>>> - Someone that has a robust process to build and version WeeWX >>>>>>>>>> configuration data and doesn't want to create something like that >>>>>>>>>> for >>>>>>>>>> configuring WeeWX sensors in Home Assistant (me again). >>>>>>>>>> >>>>>>>>>> Enjoy >>>>>>>>>> -rich >>>>>>>>>> >>>>>>>>> -- 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/63599900-74bd-4201-a2e7-cf8ff6193bc9n%40googlegroups.com.
