1.3.0 (pre-release)
This beta fixes telnet/SSH setup, which was broken for everyone, and gets the 800 series working. It's a pre-release because it has only been tested against a simulator so far. Please try it and report back, especially if you have an 800 series unit.
Fixed
- #75: Telnet and SSH setup failed for everyone with "Failed to connect", caused by an incompatible scrapli 2 release.
- #66, #55: 800 series units couldn't connect over telnet, and outlet names containing spaces were cut off.
- #67: A WB-700 with wrong credentials appeared to set up successfully, with no outlets and broken entity IDs. It's now rejected at setup.
- #56: An 800 series unit set up as HTTP failed with a bare 401. It now tells you to use telnet.
Setup and UI
- Setup errors now show the actual reason, such as a rejected login or a wrong connection type, instead of a generic "Failed to connect".
- The connection type is saved with the entry, so telnet or SSH on a non-standard port now works. Existing entries keep working unchanged.
- A wrong password now opens Home Assistant's re-authentication prompt instead of retrying forever.
- Adding a WattBox that's already configured no longer shows "Unexpected error".
- Failed switch and button actions show an error, and a failed switch flips back to its real state.
- New Download diagnostics option, with credentials, host and serial number redacted.
Other improvements
- Outlet changes made on the device or in OvrC show up in Home Assistant immediately, without waiting for the next poll.
- Dropped connections are detected and re-established automatically.
- Connections are closed properly on reload and shutdown. The 800 series limits concurrent sessions, so restarts no longer leave a session stuck open.
- Firmware that doesn't support some requests (hostname, UPS status, per-outlet power) no longer breaks polling.
Upgrading
No migration is needed. Entity IDs, unique IDs and energy history carry over. The minimum Home Assistant version is still 2025.10.0.
Under the hood
The integration no longer depends on pywattbox. It now has its own small WattBox client, which talks to the device directly over telnet, SSH or HTTP. All of the bugs above traced back to pywattbox, which is no longer maintained and was built on a screen-scraping library that broke when that library's next major version came out. The WattBox protocol is simple line-based text, so a dedicated client is smaller, easier to test and no longer at the mercy of upstream releases. The integration's dependencies drop from six packages to two (asyncssh and getmac).
Thanks
Thank you to everyone who reported these issues and shared logs and wire captures. That data is what made it possible to fix these without the hardware: @ajguerre1, @seadillpicklerooster, @dave453, @javman12