Config entry 'Roborock S7 MaxV' for xiaomi_miio integration not ready yet; Retrying in background

[JayRHa]

The problem

I got this error with Xiaomi Miio from one to an other day

Config entry 'Roborock S7 MaxV' for xiaomi_miio integration not ready yet; Retrying in background

What version of Home Assistant Core has the issue?

2023.03.1

What was the last working version of Home Assistant Core?

2023.02

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @rytilahti, @syssi, @starkillerog, mind taking a look at this issue as it has been labeled with an integration (xiaomi_miio) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of xiaomi_miio can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign xiaomi_miio Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

xiaomi_miio documentation xiaomi_miio source _{^{(message by IssueLinks)}}

[maxbrechtel]

I had the same problem with exactly the same error. Turns out my router gave the robot a new ip. Resetting the ip address to the original value and reloading the integration fixed it for me.

[JayRHa]

The device has a fixed IP this could not be the cause. I already removed and added the integration several times

[adamghamel]

I have the same issue, and have had it off and on for about 6 months now. It usually comes back after rebooting everything, including the roborock and charging dock, but sometimes it needs to wait a day or two to come back. I have totally wiped my HA and reinstalled the integration a few times with no change. I am on the latest stable release of everything. I think this all started with a big HA update, and it never really acted the same since.

[JayRHa]

can someone have an look at this topic?

[carvan]

Hi all

wanted to add a comment as I'm experiencing the same issue as well since few days.Already tried to remove and add it back, no luck.

[JayRHa]

@rytilahti, @syssi, @starkillerOG are you aware of this issue and can I support to identify the root cause? Let me know if I can something do here. For me the integration is essential.

[rytilahti]

There is not much we can do when the device is not answering, usually those are related to either network configuration issues, changed IP addresses or simply some devices behaving differently.

Is your homeassistant and the device inside the same /24 network? Is there something special in your network setup? Can you control the device using python-miio's miiocli? If you have rooted your device, you could check if the log file (called rrlog or something, iirc) contains some hints why it would ignore the communications.

[jotheman0303]

I have been having this issue as well for a while now. Thought it was gone for a few days, but it came back. Not sure what is causing this, let me know if there is anything I can troubleshoot. I don't think it is IP-related, think my address leases have not expired and there were no changes there. It worked well for a while before it broke...

[JayRHa]

There is not much we can do when the device is not answering, usually those are related to either network configuration issues, changed IP addresses or simply some devices behaving differently.

Is your homeassistant and the device inside the same /24 network? Is there something special in your network setup? Can you control the device using python-miio's miiocli? If you have rooted your device, you could check if the log file (called rrlog or something, iirc) contains some hints why it would ignore the communications.

The devices is an a segregated VLAN but there is no firewall restriction and it also work bevor 2 weeks and stop working from one to an other day. The IP is the same as always. The device is not rooted this means I am not able to troubleshoot this. For me it looks that it is an general issue for many users since an version change. I am happy to provide you all informations or support you need to troubleshoot and solve this issue.

[JayRHa]

I solved the problem with sudo iptables -t nat -A POSTROUTING -s 192.168.1.2 -d 192.168.20.225 -j MASQUERADE on my USG. To make it perssistant you can follow this guide: https://github.com/unifi-utilities/unifios-utilities/blob/f841ee1ac3c9b27679f35a13bb6dcd424fac7fd1/on-boot-script/README.md