Landroid cloud ban

[mmomasters]

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 - xxxxxxxxxx@gmail.com 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

[Phoenix-DH]

Same here, message is the same, but this is kot a ban.
App is fully working.

[DerAutomatiker]

Same here

[MTrab]

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 landroid_cloud@trab.dk - then I can test if it's a local issue or a general issue.

[Phoenix-DH]

You got mail.

Thank you so much.

[MTrab]

Thank you - unfortunately, it seems like it's a local problem, as it works without issues when I test

[Phoenix-DH]

I am wondering what will be the issue.
I did not changed something on my instance.

May some debug logs bring some benefit?

[MTrab]

Not sure it'll contribute much, but yes - you could try enabling debugging for the integration

[Phoenix-DH]

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.

[Phoenix-DH]

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?

[MTrab]

You need to remove the integration and add it again to change password - haven't added that option yet

[Phoenix-DH]

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 😂

[mmomasters]

For me it seems I have been unbanned for now, let’s wait and see

[DerAutomatiker]

same for me. Never had this problem and now it solved itself.

[mmomasters]

Maybe they had issue at the Landroid cloud directly