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/5c2334b3-fe64-4866-a04b-47d1f89c0a46n%40googlegroups.com.
