HomeKit Vacuum Entity Support

excited-planning-gif-by-northwest-motorsport

Saw on FB that someone added a SwichBot Vacuum to homekit via Matter and it exposed as a Vacuum. See the screenshots i added.
We’re all waiting to expose our Vacuum Switches as Vacuums via HA :smile::smile:


It’s happening with iOS 18.4 beta. I hope we’ll have an HA update to expose our vacuum :innocent:

Check this

4 Likes

Nice :smiley: can’t wait.

If there is a need, I am on 18.4, I can help test :slight_smile:

Any news on this?

3 Likes

Doesn’t seem to be implemented yet. I just tried addend my Neato Vacuum and it showed up as a switch in HomeKit

Apple iOS 18.4 rolled out yesterday which supports vacuum accessories in Apple Home (the ecosystem) connected via Matter control protocol. They have only basic start/stop and scheduling functionality per the Matter 1.2 spec.

Technically “HomeKit” is a control protocol which still has no vacuum support, so don’t expect the HA HomeKit bridge to export unsupported entities. The Apple Home ecosystem supports both HomeKit and Matter control protocols, but only vacuums via Matter.

HA does not include a Matter protocol bridge (i.e. it does not present devices to other ecosystems via Matter), it is only a HomeKit protocol bridge. You could try to export your existing HA vacuums to Apple Home (the ecosystem) using the Matter Bridge add-on, but I haven’t checked whether it also supports vacuums.

1 Like

I tried to make the matter bridge in HA. Then add the matter qr code generated from the matter-hub addon. Only Start, pause, return to dock I can choose in Apple Home.


How did you expose the vacuum entity?
My vacuum only exposes the switches. (Via Matter Bridge)
Edit: Fixed it. This is the correct addon GitHub - t0bst4r/home-assistant-matter-hub: Publish your Home-Assistant Instance using Matter.

Hello to you, after I paired my Roborock S8 MaxV via HomeKit without any problems and I also linked the pairing code to Home Assistant Matter, I see some entities…

Only for me a ‘cleaning’ is labelled as ‘error’ and the entity ‘operating status’ is permanently set to ‘unknown’.

Does anyone else have this problem or similar values?


  • Core: 2025.4.1
  • Supervisor: 2025.03.4
  • Operating System: 15.1
  • Frontend: 20250404.0