[FR]: Kress fleet account

[tieskuh]

Describe the issue

Kress recently removed a lot of functions from the Kress RTK app. These functions are moved to the Kress Fleet app.
So there is one app where you can basically only edit the schedule, and a more advanced Kress Fleet app.

If you want to use the Kress Fleet app, which I think most HA users do, you have to migrate your account to Kress Fleet app upon logging in to the Kress Fleet app. At that point the Kress RTK app stops working. Unfortunatly, so does this integration.

There is no way to have a Kress RTK and a Kress Fleet account simultaniously. As I think more users will migrate to Kress Fleet, I am reporting this as an issue.

If there is anything I can do to provide logs or data, please let me know.

What version of Home Assistant Core has the issue?

2026.3.4

What was the last working version of Home Assistant Core?

No response

What version of the Landroid Cloud integration do you have installed

v7.0.0b4

What type of installation are you running?

Home Assistant OS

What make of mower does this concern?

Kress

Which model is the mower used for this integration?

KR233E

Diagnostics file

Schermafbeelding 2026-03-29 233928.png

If you could not provide diagnostics, explain why

Integration doesn't initialize.

Relevant log entries

2026-03-29 23:28:40.342 INFO (MainThread) [custom_components.landroid_cloud] 
-------------------------------------------------------------------
Landroid Cloud integration

Version: 7.0.0b4
This is a custom integration
If you have any issues with this you need to open an issue here:
https://github.com/mtrab/landroid_cloud/issues
-------------------------------------------------------------------

2026-03-29 23:28:40.342 DEBUG (MainThread) [pyworxcloud] Initializing connector...
2026-03-29 23:28:40.342 DEBUG (MainThread) [pyworxcloud] Try getting correct CloudType from KRESS
2026-03-29 23:28:40.342 DEBUG (MainThread) [pyworxcloud] Found cloud type <class 'pyworxcloud.clouds.CloudType.KRESS'>
2026-03-29 23:28:40.342 DEBUG (MainThread) [pyworxcloud] Initializing the API connector ...
2026-03-29 23:28:40.342 DEBUG (MainThread) [pyworxcloud] Getting logger ...
2026-03-29 23:28:40.342 DEBUG (MainThread) [pyworxcloud] Initializing EventHandler ...
2026-03-29 23:28:40.342 DEBUG (MainThread) [pyworxcloud] Authenticating x@x.x
2026-03-29 23:28:40.826 DEBUG (MainThread) [pyworxcloud] Authentication for x@x.xsuccessful
2026-03-29 23:28:40.826 DEBUG (MainThread) [pyworxcloud] Fetching basic API data
2026-03-29 23:28:40.977 DEBUG (MainThread) [pyworxcloud.Connect] Connect failed; cleaning up partial resources
Traceback (most recent call last):
  File "/usr/local/lib/python3.14/site-packages/pyworxcloud/__init__.py", line 341, in connect
    await self._fetch()
  File "/usr/local/lib/python3.14/site-packages/pyworxcloud/__init__.py", line 552, in _fetch
    self._mowers = await self._api.get_mowers()
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/pyworxcloud/api.py", line 138, in get_mowers
    mowers = await AGET(
             ^^^^^^^^^^^
    ...<3 lines>...
    )
    ^
  File "/usr/local/lib/python3.14/site-packages/pyworxcloud/utils/requests.py", line 134, in AGET
    _raise_http_status(resp.status, Exception(f"HTTP {resp.status}"))
    ~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/pyworxcloud/utils/requests.py", line 76, in _raise_http_status
    raise ForbiddenError()
pyworxcloud.exceptions.ForbiddenError
2026-03-29 23:28:40.978 DEBUG (MainThread) [pyworxcloud.Disconnect] API close completed in 0.000s

Additional information

No response

[MTrab]

See #1053 - also, not at bug, more a feature request.
But a feature request that won't be adde until the fleet API is mature.

For now the recommendations, even from Positec, is the revert to the notmal app, as fleet is an early alpha, API wise

[tieskuh]

Sorry...I didn't see #1053
What a strange approach from Kress to remove features from the current app, and move them to an app that is early alpha.
Reverting to the normal app is not really an option as they removed features I use that are now in the fleet app. I could switch back and forth between the apps.
Thanks!

[MTrab]

At least that's the message I have been given from Positec (the company behind Kress, Worx and LandXcape)
One could hope the move fast on these API changes, so it becomes more stable and ready for use.

Anyway - do not expect Fleet support in the upcoming release, perhaps during the year to come

[tieskuh]

Yes, all clear. For now I will switch between apps. I need the fleet app to select and edit maps. They removed that from the Kress RTK app. You can migrate accounts between the apps so I will just migrate back and forth everytime I need to edit a map or no-go zone.

If I can do anything to help in the future, please let me know.

[MTrab]

At some point, it could be useful to lend access to your Fleet account, as I do not own a Kress device myself, for development reasons.

[tieskuh]

Sure! Just let me know when the time comes.

[MTrab]

Latest update to this - the Fleet API is not realtime yet.
They are working on it, but no ETA on realtime data from Fleet API - yet another reason for not switching to (or integrating) Fleet just yet.

[b772789]

Same problem on Kress Mission RTK600 (KR160E.A), FW 3.38.0+17.

The original "Kress Mission RTK" app started returning a map error, and the only fix Kress support offered was migrating to the Kress Fleet app. The mower itself works fine via Fleet now — but the landroid_cloud integration immediately stopped authenticating after that migration.

Repeating log entry (every 80s with exponential backoff):

Config entry 'Kress - <email>' for landroid_cloud integration
not ready yet: Cloud endpoint rejected setup request;
Retrying in 80 seconds

Looks like the same 403 ForbiddenError others have reported on this issue — the Fleet endpoint rejects the consumer-API auth flow.

Setup:

• HA Core 2026.4.2
• landroid_cloud 7.0.5 (HACS) / pyworxcloud 6.3.6
• Account migrated from "Kress Mission RTK" app → "Kress Fleet" app (forced by Kress support after map_error in the old app)

Happy to provide full HA logs or run pyworxcloud diagnostics against the Fleet endpoint if it helps narrow down the API differences. +1 for Fleet support.