1 minute read

We’ve had an iRobot Roomba 625 roving the house doing the vacuuming now for over two years and have been happy with having it around. It definitely helps keeping up the vacuuming, but it doesn’t do anything else.

Obviously it’s been integrated in Home Assistant, but I haven’t done much with it. It’s controllable without relying on the cloud that way though most of the time we start it using the iRobot app.

Enter now a sibling from another parental company: Xiaomi Roborock S7. This one is a “smarter” version of the previous one, with unfortunately some more cloud dependencies. Not a fan, but we can remediate that to some level.

Integrating it with Home Assistant means figuring out how to get the cloud token out of the cloud account, which can be done using Piotr Machowski’s Xiaomi Cloud Token Extractor. Using that tool to get the info, and configuring it manually in Home Assistant.

When adding the Xiaomi Miio integration, you need to enter your cloud username & password, check the right server, and definitely check the “Configure Manually” checkbox. Xiaomi Mii Integration

In the second screen you can then add the IP address of the robot, as well as it’s cloud token.

Xiaomi Mii Integration

Now, if like me you have your IoT devices on their own VLAN (heavily locked down), you’re gonna hit a snag here: Home Assistant will complain it can’t configure the device. Some searching easily came up with the reason: the robot won’t respond to UDP packets coming from outside it’s subnet.

What you’ll need to do is add some additional configuration in your router/switch/… (wherever you configure your VLANs). For me that is my OPNsense box in which I had to configure some additional NAT rules:

Under Firewall → NAT → Outbound, add a rule with this configuration:

Parameter Value
Interface IoT (your IoT network vlan interface)
TCP version IPv4
Protocol UDP
Source Address <your home assistant IP / alias>
Source Port Any
Destination Address <your robot IP / alias>
Destination Port 54321
Translation / target IoT address

and that’s it. Afterwards your Home Assistant should be able to query the robot, and off you go to build some automations!

Recommended reads:

Comments

You May Also Enjoy

SSH’ing to Unifi equipment with Fedora 37

1 minute read

Connecting to Unifi equipment (Switch 8/AP AC Pro) from Fedora37 fails out of the box with a very useful error Bad server host key: Invalid key length. This is because the dropbear used on these devices is woefully out of date, and still requires the use of ssh-rsa (with SHA1), which has been deprecated by OpenSSH in 2021,

Now using less external services!

less than 1 minute read

So back in 2019 I moved the site from WordPress to Jekyll (using Minimal Mistakes), and from Gandi to AWS Serverless.

Lenovo Thinkpad T14s Gen3 (AMD)

3 minute read

10 years ago I bought a Dell XPS13 L322x ultrabook as a replacement for my white Macbook 2,1. This week I replaced the Dell with something newer: a Lenovo Thinkpad T14s Gen3 (AMD).