I thought it was about time that I contributed to this awesome community, and today I am happy to announce my first contribution that will let you run WeeWX server as a Home Assistant add-on.
This implemantation comes included with the weewx-interceptor and weewx-home-assistant extensions providing a solution that is able to intercept weather data destined for the cloud and manage it locally, as well as shipping data to home assistant via the MQTT integration.
This integration does require the ability to intercept and rewrite DNS requests within your local network, allowing you to redirect traffic to the add-on. There is a documentation describing installation and configuration in the DOCS.md file.
Do you have the logic in place to add additional third-party WeeWX station drivers in place of weewx-interceptor? (Can the HA add-on architecture receive UDP broadcasts over the network?) How about adding stuff like the Belchertown skin???
The current state of the add-on perserves the config directory of weewx within the addons_config directory and mounts the /share directory as part of the build config so you can share reporting other addons like Caddy or Nginx for example.
For adding reports and extensions etc you will need to use docker exec to either run the weectl commands or create an interactive session within the container.
Currently the container config only exposes a single port for the interceptor, but I can look into how this could be extended in the config of teh add-on.
I must admit I am still learning the advanced container integration stuff in teh addon ecosystem.
Feel free to drop thoughts here or ideally in Github
Are yiou able to ellaborate on this? Keen to understand where the delineation between the two are so that I can describe things correctly going forward.
Executive summary - The 2026.2 HA update changed the nomenclature of what was formerly known as add-ons to now be known as apps. Nothing in the coding of add-ons/apps has changed, AFAIK…
