MTrab
Landroid cloud ban
Describe the issue
It seems I have been banned from landroid cloud and I can't reconnect
What version of Home Assistant Core has the issue?
core-2025.9.1
What was the last working version of Home Assistant Core?
core-2025.9.1
What version of the Landroid Cloud integration do you have installed
6.0.0
What type of installation are you running?
Home Assistant OS
Which make and model is the mower used for this integration?
Landroid M500
Diagnostics information (NOT log entries!)
I deleted the Landroid so I don't have access to diagnostics data
Relevant log entries
Logger: pyworxcloud.MQTT
Source: /usr/local/lib/python3.13/site-packages/pyworxcloud/utils/mqtt.py:248
First occurred: 3:56:00 PM (1 occurrence)
Last logged: 3:56:00 PM
Failed to connect to MQTT: AWS_ERROR_MQTT_UNEXPECTED_HANGUP: The connection was closed unexpectedly.
Logger: homeassistant.config_entries
Source: config_entries.py:751
First occurred: 3:56:00 PM (1 occurrence)
Last logged: 3:56:00 PM
Error setting up entry Worx - [email protected] for landroid_cloud (email hashed manually)
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/pyworxcloud/utils/mqtt.py", line 230, in connect
connect_result = self._connection_future.result()
File "/usr/local/lib/python3.13/concurrent/futures/_base.py", line 456, in result
return self.__get_result()
~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/concurrent/futures/_base.py", line 401, in __get_result
raise self._exception
awscrt.exceptions.AwsCrtError: AWS_ERROR_MQTT_UNEXPECTED_HANGUP: The connection was closed unexpectedly.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 751, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/landroid_cloud/__init__.py", line 40, in async_setup_entry
result = await _async_setup(hass, entry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/landroid_cloud/__init__.py", line 135, in _async_setup
await hass.async_add_executor_job(cloud.connect)
File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 59, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.13/site-packages/pyworxcloud/__init__.py", line 282, in connect
self.mqtt.connect()
~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/site-packages/pyworxcloud/utils/mqtt.py", line 249, in connect
raise NoConnectionError() from exc
pyworxcloud.exceptions.NoConnectionError
Additional information
No response
Same here, message is the same, but this is kot a ban. App is fully working.
I'm just about to give up - I cannot see why some users get this, while most others (myself included) never sees any issues.
I have no idea how to solve this, unfortunately.
Best idea right now, is for one of you to send me the credentials for your Landroid account, to [email protected] - then I can test if it's a local issue or a general issue.
Thank you - unfortunately, it seems like it's a local problem, as it works without issues when I test
I am wondering what will be the issue. I did not changed something on my instance.
May some debug logs bring some benefit?
Not sure it'll contribute much, but yes - you could try enabling debugging for the integration
Inhave an issue an maybe a dumb question: I will keep the pw I sent to you for now. But how can I change it in the integration?
Never did before.
Crazy, I was not able to get it changed. So I decided to take the old one…
Reload… back working 🤷🏼♂️
Maybe some session caching stuff?
You need to remove the integration and add it again to change password - haven't added that option yet
Ah okay: Tried a sonution with changing config_entry file but without success. Old pw always was written back.
But as mentioned, mine is now back working with the origin pw.
Will have an eye on it.
When that is the solution, maybe the option would be great 😂
Have the same issue had it yesterday afternoon/ evening (eu time) then in the early morning was ok. Now today in the afternoon same problem. I also have issue with the landroid app not updating the status of the mower. Maybe an issue of the amount of the API calls made during the day or simply the landroid szerver has problem everyone afternoon.
Also found this issue in the logs:
Logger: pyworxcloud.MQTT
Source: custom_components/landroid_cloud/switch.py:23 integration: Landroid Cloud (documentation, issues) First occurred: September 12, 2025 at 6:41:04 PM (2 occurrences) Last logged: 6:08:52 PM
Failed to connect to MQTT: AWS_ERROR_MQTT_UNEXPECTED_HANGUP: The connection was closed unexpectedly.
I am wondering how that happened on your ends. I think in my case it was after a reboot, or maybe related to some integration timeouts.
Did that happen during a running system?
Same happened again also to me. Integration was not updating anymore, reload. Same message. App is currently also not working.
I have also the same issue again, during the day it is okay, every evening problem. Looking like more of a worx server problem. I have submitted an issue report to them (no reply yet, probably because of the weekend).
Strange that not more people have that issue. Should we collect similarities?
Like region germany, unify network, adguard…
Im from hungary, tp link Network and no adguard on my side:) so nothing similar. I have a worx landroid s300 (wr130e) and old model
I have no clue what can be relevant for the issue… I have a M700 from 2022.
For me i wasn’t banned today, I was banned like yesterday and the day before and no ban today, let’s wait and see!
App get a kind of reload, battery etc. was changing, manuall reload in the app results still in an connection error.
Same here. For me this started happening after robot got stuck during the night during mowing cycle. The next day I cleared up the error and could no longer connect to it via home assistant
Today I moved my working time. No issue during moving.
The error seems to be occurin arround 07:00pm GMT+2.
For me problem started at 5pm, mower was at the station when it happened. I have restarted my home routers in the mean time as well...