core Shark IQ shows me the wrong room names

The problem

Shark IQ shows me the wrong room names Since the bugfix of the login, I can connect to my Shark. Unfortunately, the room attributes are displayed incorrectly. The rooms displayed are “AZ_4” and “AZ_3”. But I have more than 2 rooms and they are called “kitchen”, “livingroom”, ....

What I have tried so far. updating the integration in Home Assistant reinstall the integration in Home Assistant changing the room names in the app do remapping in the app

Point 4 resulted in only 2 values being displayed for rooms. In addition, these are now called differently, previously they were called “AZ_1”, “AZ_2” and “AZ_x”. Point 3 also resulted in changed names.

The action: “action: sharkiq.clean_room data: rooms:

“AZ_4”

target: entity_id: vacuum.vacu_shark”

Is not possible and gives the following error “Room Az 4 is not available for your vacuum cleaner. Make sure all rooms match the SharkClean app, including case sensitivity.”

When I use the names from the app, I get the same message

Does anyone know the problem and know a solution?

Kind regards

Home Assistant: Core 2025.4.4 Supervisor 2025.04.1 Operating System 15.2 Frontend 20250411.0

What version of Home Assistant Core has the issue?

2025.4.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

sharkiq

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

May 05 '25 20:05 Java112358

Hey there @jeffresc, @funkybunch, mind taking a look at this issue as it has been labeled with an integration (sharkiq) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of sharkiq can trigger bot actions by commenting:

@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign sharkiq Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

sharkiq documentation sharkiq source _{^{(message by IssueLinks)}}

May 05 '25 20:05 home-assistant[bot]

Is there no solution?

May 21 '25 18:05 Java112358

We’re tracking this issue on the sharkiq library repo. This seems to only affect some vacuums so we’ll need help from people with those models.

Jul 15 '25 02:07 funkybunch

What information do you require that I could provide?

Jul 28 '25 08:07 Java112358

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 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Oct 26 '25 08:10 issue-triage-workflows[bot]

Hello, the problem still persist. Please don't close the issue.

Oct 26 '25 15:10 Java112358