Integration no longer working #144
Comments
|
Could you provide me some logs? |
|
I am also struggling with similar issue. It was working in my main ha instance 5 or 6 releases earlier but due to probably the map updates / delays it was slowing down my ha instance, so I disabled it. Then I tried some updated releases but it just failed to properly initialize. I then created a separate ha instance just to test this integration and it has failed to go past the setup. It is able to login to my roborock account (as I get notification on my roborock app that a new login has been made to my account) but the integration never initializes properly. I have tried the 2022.12.9 and 2022.6.7 ha versions with same results. I get the below errors. Is it possible that roborock has blocked my account to login from any thing other than the official roborock app. The errors that I see are... |
This is all it shows: then i get this error screen in the pop up
Happy to run or pull whatever you need, but it can't get past that first part and the logs are pretty light. I did have it up and working a few days ago tho, if that is helpful. Home Assistant 2023.1.4 UPDATE |
|
The integration is still working for me, but I get the same exceptions about once or twice every hour. This is "new" since the last 2 updates. |
|
updated little after 16 and its been unstable after that. All the white is unavailable. When i woke up i reloaded the integration.
|
@humbertogontijo https://forum.netgate.com/topic/177133/pfsense-blocking-roborock-app/30 @jmbrown79 by chance are you running pfSense or OPNsense? |
|
@dochodges Just read through your thread on pfsense - seems very strange. Some questions I had:
My setup still seems to be working but I'm running Sophos XG (router/firewall) with an S7 MaxV on a separate VLAN. I have an explicit firewall rule that allows the S7 to access only DNS, HTTPS, MQTT and NTP services. Roborock S7 MaxV firmware: 02.56.02 |
|
also having an issue with the last few updates. I'm not sure when it worked last but now my logs are showing: Logger: homeassistant.config_entries Error setting up entry [removed email] for roborock |
Since the issue started the vacuum is also no longer connected to the network so it does not have an IP address when trying to use roborock app. Currently I cannot even log into the roborock app to do anything as I am greeted with a network error just trying to login. There was never any Vlans setup or rules for the robot at all. It was/is about as basic of a setup as you can make. I have a 2.4ghz SSID configured for IOT devices but neither the phone nor PC will connect to roborock servers to even log in no matter which network I connect to and the PC is hardwired not wifi. Mi Home works just fine and I have robot connected and running via that app without any issues at all. Its something specific to the roborock app. |
Hm, that's odd the DHCP service isn't even assigning a local IP address to the device. I mean, nothing is going to work at that point. Have you tried maybe assigning a static IP address through the DHCP service in pfSense? I'm assuming you've tried a factory reset on the Roborock? I'm wondering if maybe there's something weird with the network configuration on the device itself. Definitely a weird issue considering it was working previously... 😕 Edit: I believe the apps work slightly different. One thing I noticed is the Mi Home app connects using both their servers and locally to the device whereas the Roborock app connects to the device through their cloud MQTT service on port 8883 (in addition to TCP connections on 443). I don't believe the Mi Home app ever used MQTT since I explicitly had to allow that on my firewall to get the Roborock app to work. I haven't used pfSense or OPNsense for a while but I wonder if there's something weird when it comes to MQTT? I also noticed my Sophos XG logs shows the MQTT connections with the Roborock MQTT broker as "SSL Traffic over Non-SSL Ports". |
|
Well one thing that has me stumped is really the vacuum itself has nothing to do with the equation. Without the vacuum I should still be able to log into my account via the app or connect my account via this integration. That said the MQTT broker does sound like a promising path and the difference between the app could identify where freebsd is causing it to fail and block connection. Thats very interesting. I wish I knew more about the ins and outs of routing as that seems like something that could be fixed if I knew how haha |
|
@dochodges Starting with the basics. Is your router resolving DNS euiot.roborock.com? (Which is the default base url to discover the real api to be used based on your account country). And, if your account from US, is it also solving usiot.roborock.com ? |
Thank you for the reply! We are definitely on the right track here. Euiot resolved but usiot did not. Switching to lte boom both resolved. Not quite sure what this means but I think we at least narrowed down the culprit! Edit: I did a dns lookup and it does seem to get resolved but when I type the EUiot into a web browser I get a white page and when I type the USIot I get a network error page |
|
this is what I get when searching both the US and EU addresses |
|
@dochodges I can only suggest you to use another DNS server other than the one you are using |
Sorry I misspoke before according to the dns lookup the dns is resolving properly but if you check the link above the usiot gives a server stopped responding error while the EU does not. On LTE however the usiot is reachable. I’m still learning all the lingo and took that as not resolving but technically it is according to the dns lookup. |
here are the results of the dns lookup |
|
Oh, yes. The lookup looks correct. |
No VPN and actually reverted everything to a clean install so base configuration of pfsense. Also tried installing opnsense on for the same results. Something with the FreeBSD doesn’t like something but can figure out what yet. |
|
This is just a regular HTTP request, it intrigues me that a router can be affecting it other than a dns or vpn issue. Any chance that the router have access to the internet but the lan don't? |
|
Unfortuantely, I am not. I am running just 2 unifi nanohds and the USG 3p, but have turned off all firewalls and security. I tried difference devices with same issue as well as this integration. i even booted up an old iphone 11 with a much older version of the RR app and it still won't connect. The unifi equipment seems to be the issue for me but i don't get why because i had running for years and i don't see any updates to me unifi equipment. Could RR servers possibly be blocking us at a hardware level after this integration due to seeing and it connect from abnormal place? I am grasping at straws here trying to resolve this because i walked in one day and saw the integration was offline and my map was gone then never was able to get back into my app on my wifi. Reading thru your comments, it sounds like we have same issue acting the same way which is strange and makes me think RR servers are blocking us. I am not a network guy but is there a way to see if the app and router are actually sending out the call to the RR servers vs it being an issue with network settings or internal hardware blocking something? |
|
Like jmbrown79, i think its Roborock who are blocking us. |
|
same issue here, I found ver.0.0.23 could create a huge amount of mqtt connections to RR server, then I been blocked for a few hours. I can reproduce this by:
after upgrading to ver.0.0.26 this issue was gone. |
|
The one thing leaving me confused is why when I swap routers does it all of a sudden allow me to connect. If we are IP banned, mac address banned or hwid banned wouldn’t that not be the case? Edit: now that I think of it if the ban is linked to the hwid or max address of the router itself then this could very well be the case and everything begins to make sense. The question then becomes how do we get unbanned? Luckily a new pc to run pfsense is only like $100 so cheaper than the $1200 robot |
|
I have the same issue, roborock app is not working anymore buth i now use the xihome app. Edit; roborock app is working again, think it was a ban for a day or somthing |
Unfortunately mine has been this way for near a week now. |
|
So looks like I came home today to try out swapping NICs to see if it was a MAC address ban or force a different IP and it’s resolved. I can now log into the app no problem. Looks like we were banned from roborock after all. Knowing this can we confirm it’s safe to use the integration and the excess calls to the server are resolved? It appears so based on the post above but want to confirm |
|
So did you have to change the NIC/Mac to resolve it or the ban was temporary and therefore got lifted on its own? yes, it is important to know that the integration would not keep repeatedly trying the Roborock servers and get us locked out or worse have the complete integration locked out. |
The Ban was lifted on its own. I got home from work and was planning to make the change but tried it first and it was just working. |
|
If that's true, it's concerning. I myself have never had such a "ban". I suggest removing any automation that reloads the integration (which will fetch the home data for each reload) |
|
I can confirm that mine came back online today and i can access via the app with no issues. This has to be RR block things at a hardware level. It seems that like @timbotetsu mentions it very likely the huge amount of api call via mqtt may be blocking blocking us. I too want to make sure this is resolved before reinstalling this (which I LOVED BTW). @humbertogontijo is there any way you may be able to verify this isnt generating the high volume of calls it was doing in previous versions? Thanks for you awesome work BTW, I know we've all be quick to talk about the issues but wanted to make sure we also show some love as well. |
|
Also, just a note to possibly help with troubleshooting in the future with this issue would be to have the error message call out that the issue is with the server not responding or something related to that so when it pops up we can provide some better help to you for troubleshoot what cause the integration failing. |
@humbertogontijo I did not have any automations setup with mine yet. I only loaded a lovelace card into my dashboard. Is there any way to see if its making a lot of calls so i can check it over the next week or so and avoid doing whatever it driving it? Thanks for your continued support and development!! |
How did you see this? I would like to monitor mine to make sure. @nijhawank @dochodges @Senater have you tried reloading the integration without any further issues? Thanks! |
|
I still have the issue with 0.0.27. I disabled the integration yesterday and I'm still blocked today (I disabled it again, will wait more). |
Have you been blocked since previous versions? If so, what version did it start with? |
|
If you can provide logs, it would help with troubleshooting. You’ll need to enable debug logging for the integration to get more detailed information by adding this to your Home Assistant configuration.yaml: logger:
default: info
logs:
custom_components.roborock: debugIt might also help to provide some additional information like what type of vacuum you have, how many, are they shared devices or directly added to the Roborock app, anything that should be noted for your setup, etc. |
I have added that to my config, but not enabled the integration yet. I am running 2 s7's and a s7 maxv ultra. They were all added to the RR app directly, but i do share then with my wife on her phone which also runs the RR app. Not sure what other info is relevant, but I only had it enabled via the integration and the loaded 2 of the maps via the lovelace card on ym dashboard. Actually during that time i didn't even run the vacuums via the app or the HA integration. I had no automations, or anything. I came home one day and saw there was an error on the dashboard and tried to fix, reloaded, reinstalled etc then posted here. I found out later that day that i couldnt use the app at all unless i turned off the wifi. I home that is helpful @shred86 If there is anything else i can post (besides the logs) I am happy to do so. I will try reloading the app to see if it works again with the log enables and if I get locked out again i can share those logs. |
|
I have the same issue. When i reload the intergration it will stay working for about 2 minutes after which the connection seems to timeout and won't come back again.
`custom_components.roborock.api.exceptions.RoborockException: Failed to connect. The above exception was the direct cause of the following exception: Traceback (most recent call last): |
|
Removing offline devices from the roborock app seems to fix the issue |
|
Problem is seemingly resolved - closing for now. |
The integration has stopped working over the last 2 updates (0.0.24 and 0.0.25). It gets stuck at initializing when reloading thru the HA integration UI screen and if you remove and try to reinstall it never makes it past where you enter you email address on the first step. Have tried reloading HA and can login to me RR account and use the app with no issues.
The text was updated successfully, but these errors were encountered: