gronod
e12292f316
Pin ha-n95-local-control tag v0.1.2 (7bed99cc4c3222bad648efcddcdfed95652277f7). Health bind failure no longer takes down 8007/8005/5223 when OTBR owns 8080.
59 lines
2.5 KiB
Markdown
59 lines
2.5 KiB
Markdown
# Deebot N95 Local Control
|
|
|
|
<img src="logo.png" alt="Deebot N95 Local Control" width="128" height="128">
|
|
|
|
Redirect an already-provisioned Ecovacs Deebot N95 from its legacy cloud
|
|
bootstrap and XMPP endpoint to a local bridge, packaged as a Home Assistant
|
|
add-on.
|
|
|
|
The bridge publishes each robot through MQTT discovery as a native Home
|
|
Assistant vacuum. Once the LAN DNS redirect is in place, robot control and
|
|
state stay on your local network.
|
|
|
|
## Features
|
|
|
|
* Local HTTP bootstrap and XMPP endpoint for compatible Deebot N95 robots
|
|
* Automatic Home Assistant MQTT vacuum discovery
|
|
* Multiple robots, with separate MQTT clients and topic trees by serial number
|
|
* Vacuum state and control, cleaning modes, movement, schedules, consumable
|
|
lifespan, and diagnostics
|
|
* Automatic Supervisor MQTT broker discovery with per-setting overrides
|
|
* Optional MQTT authentication, TLS, and private CA support
|
|
* Health endpoint for installation checks
|
|
|
|
## Requirements
|
|
|
|
* An already-provisioned Deebot N95 using the `wukong` / class `155` protocol
|
|
* Control of the DNS resolver supplied to the robot by DHCP
|
|
* A stable IPv4 address for the Home Assistant host
|
|
* TCP ports `8005`, `8007`, and `5223` reachable from the robot
|
|
* Home Assistant MQTT configured with discovery enabled, and a reachable broker
|
|
* The correct IANA timezone for the robot's clock and schedules
|
|
|
|
> The robot-facing XMPP connection, including SASL PLAIN authentication, is
|
|
> plaintext. Run this add-on only on a trusted LAN and restrict access to its
|
|
> listener ports. MQTT TLS protects the broker connection, not robot XMPP.
|
|
|
|
## Installation
|
|
|
|
1. Add this repository to Home Assistant
|
|
(**Settings → Add-ons → Add-on Store → ⋮ → Repositories**):
|
|
`https://git.i3omb.com/gronod/ha-gronod-addons`
|
|
2. Install **Deebot N95 Local Control**
|
|
3. Set **Advertised IP address** to the stable LAN IPv4 address of the Home
|
|
Assistant host and select the correct timezone
|
|
4. Configure LAN DNS so `lbo.ecouser.net` resolves to that address
|
|
5. Start the add-on, verify its health and lookup endpoints, then reboot the
|
|
robot so it performs bootstrap again
|
|
|
|
See [DOCS.md](DOCS.md) for the complete network setup, option reference,
|
|
verification procedure, MQTT behavior, security notes, and troubleshooting.
|
|
|
|
## Upstream and license
|
|
|
|
The add-on builds
|
|
[ha-n95-local-control v0.1.2](https://git.i3omb.com/gronod/ha-n95-local-control/src/tag/v0.1.2),
|
|
which also contains standalone Docker and Go instructions. The upstream
|
|
software is licensed under the
|
|
[Apache License 2.0](https://git.i3omb.com/gronod/ha-n95-local-control/src/tag/v0.1.2/LICENCE.md).
|