Files

T

gronod e12292f316 fix: n95-mqtt-bridge 0.1.2 builds upstream v0.1.2

Pin ha-n95-local-control tag v0.1.2
(7bed99cc4c3222bad648efcddcdfed95652277f7). Health bind failure no
longer takes down 8007/8005/5223 when OTBR owns 8080.

2026-09-24 16:18:51 +00:00

1.2 KiB

Raw Permalink Blame History

Changelog

0.1.2

Build upstream ha-n95-local-control v0.1.2 (7bed99cc4c3222bad648efcddcdfed95652277f7).
Health bind failure is no longer fatal. If 8080 is taken (OpenThread Border Router and other add-ons), lookup 8007, firmware 8005, and XMPP 5223 stay up. Set optional health_port if you still want /healthz.
Upstream logs each successful listen address.

0.1.1

Declare TCP 8007, 8005, 5223, and 8080 in the add-on ports map so Home Assistant OS Supervisor opens those ports on the host firewall. Host networking is unchanged; Docker does not remap the ports.
Potential operational change: after update, the add-on Network tab lists the four listeners. Rebuild/reinstall so HA picks up 0.1.1.

0.1.0

First Home Assistant add-on release
Build the upstream Deebot N95 bridge from the pinned v0.1.0 tag (75354b35180f4cc5e92187b6149322b0b94533ba)
Bind robot-facing lookup, firmware, and XMPP listeners on the Home Assistant host network
Discover Supervisor MQTT connection details automatically with per-field configuration overrides and external-broker support
Expose the complete bridge configuration, with advanced and risky settings hidden under optional configuration by default

1.2 KiB Raw Permalink Blame History

Changelog

0.1.2

0.1.1

0.1.0

1.2 KiB

Raw Permalink Blame History