core: Xiaomii Miio configuration for Roborock S7 not working anymore
The problem
After a complete reset of the vacuum, I tried to add it again in Home Assistant. When I followed the wizard dedicated to Xiaomii Miio I have the following error
If I do the configuration manually, like proposed in the previous capture, the wizard ends up successfully but the integration is stuck in the initialising state.
The only log I have is this line:
2022-11-03 13:40:16.175 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Alfred' for xiaomi_miio integration not ready yet; Retrying in background
What version of Home Assistant Core has the issue?
2022.11.0
What was the last working version of Home Assistant Core?
Not relevant, it stopped working while using 2022.4.7 with no reason
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Xiaomii Miio
Link to integration documentation on our website
https://www.home-assistant.io/integrations/xiaomi_miio#xiaomi-mi-robot-vacuum
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
Original thread for this issue, closed maybe a bit too fast 😅.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 35 (16 by maintainers)
I have the same Problem, but in my environment all devices are in the same subnet. no vlans. HA Version is 2022.11.2 - Core Version on RPI Roborock S7 is reachable via ping from RPI.
@rytilahti Thanks, your sentence: _"I can only think of two cases where re-adding would be helpful and fix it:
If the IP address has changed and the zeroconf config flow does not update it, e.g., if homeassistant does not receive the updates, or if the advertisement data does not contain the mac address of the device."_
pointed me into the right direction 😃
I’ve recently replaced my ISP’s hardware by my own…so new network same SSID new IP…
just added the old IP to the DHCP reservations ‘et voila’ the whole thing is working again.
In the end (should be in the description of the integration), the integration doesn’t update the device’s IP automatically when it changes. This can be valuable information as it’s not possible to configure a static ip onto the robot and most robot’s receive a non reserved IP address from DHCP.
Perhaps this helps other users with the same issue too.