Closed olskar closed 6 years ago
So I connected the gen2 xiaomi vacuum back to internet and to mi home android app. The earlier version where you can still get token. Had to reboot the vacuum. Felt like the vacuum went into a crashed state due to some reason.
Now I’m home assistant the fan speed is 102%. Which is suppose to be balanced mode. Max is 104. I set the speed from the mihome app and I can see home assistant change
It use to say balanced and max. Now just 102%. Token didn’t change its back online with home assistant and internet blocked off again.
Strange that it kind of went into a crashed mode and couldn’t get back online even the mi home couldn’t detect it until I restarted it.
No idea why the mi home app set the fan speed to 101, 102, 103, 104 Now I’ve rebooted the vacuum again the value reset back to 60% which home assistant tells me it’s balanced mode again.
Anyone with a gen2 has seen this strange behaviour? Are the fan values same from gen 1 to gen 2??? Either way it’s been strange.
After a week of idling. Gen2 vacuum didn’t respond. And when I restarted hass. It was no longer available.
Starting to think whether I need to allow the vacuum to access dns and ntp maybe. For those that have not given internet access to the vacuum has yours been working???
Found a post on the forums saying that the vacuum would only work after allowing dns and ntp?? https://community.home-assistant.io/t/what-are-your-strategies-to-protect-your-network-security-privacy/31569
Has anyone here experienced the same thing? I will try and find out which dns and ntp the vacuum uses and allow it. Will let you all know when I find out.
Sounds like the vacuum retires accessing the internet too much and eventual enters a crashed state.
This is fine. The device doesn't respond sometimes. The second try / retry was successful in your case.
But it's not good if I get these messages up to three times a minute right or am I wrong? https://gist.github.com/tringler/87bd31b43e6cb0955c01a39ee4263b36
I have no problems to call the vacuum cleaner at all. I'm struggling only with these messages all the time. I think [homeassistant.core] Timer got out of sync. Resetting
is also caused by these messages but not 100% sure.
No, that's not definitely good. Did you look at the link @beatmag posted? Do you allow your vacuum to connect to the cloud? If not, do you silently drop the packets or are you rejecting them? The former is known to cause (or at least amplify) the problem.
I jumped from 0.65.0 to 0.65.6 and my first gen robovac is not detected anymore. I reject any attempts of my robovac to communicate with the internet. Worked fine till the update to 0.65.6.
See my commentary on https://github.com/home-assistant/home-assistant/issues/11048#issuecomment-375930041 . If someone is having still issues with this (and none of the listed potential causes apply), feel free to open a new issue & including enough information to debug this.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
Home Assistant release (hass --version): 0.51.2
Python release (python3 --version): 3.4.2
Component/platform: vacuum
Description of problem: I see that #8982 was closed @azogue but I am afraid I still have the same problem. The token is correct and mirobo can communicate without problems, all the times I have tried. As you can see it spawns those errors for more than 20 minutes.