Apple Home device doesn't show up in Hubitat

🛎️ Get Help Devices
1

I have a Fibaro FGBHMS-001 with a UPC of 8 5793400534 8. I was able to include it into my Apple Home device, but it refuses to show up in Hubitat's devices list (so I can use it in automatons). How do I get such a device to be exposed in Hubitat?

Thanks,
Jeff

2

Fibaro FGBHMS-001 is a Bluetooth motion sensor that supports Apple HomeKit protocol.

There is no way to pair it directly to Hubitat, but you could use a HE virtual switch exposed to HomeKit, and make an automation in Apple Home - when motion is detected, turn the HE virtual switch on, etc..

3 Likes
3

Thanks for your input. Can you please advise on the specific method of creating and using that “HE Virtual Switch”? Is that configured in HomeKit or in Hubitat, etc?

Sincerely,

Jeff

4

Create a virtual device on Hubitat: Add Device | Hubitat Documentation

Make it a virtual Switch.

Then you will need to setup the HomeKit integration: HomeKit Integration | Hubitat Documentation

Share the virtual switch to your Apple Home via that app.

Create an automation in Apple Home to turn the switch on and off based on motion detected,

Once that is done you can use the switch to trigger other rules in HE.

3 Likes
5

Thanks.

OK, I've set up the virtual device on Hubitat and added the Matter/Homekit multisensor to the integration. When the sensor sees motion it does notify this on the Home app, but NOT in the log of the Hubitat.

So I also need to go in the other direction -- get a homekit multisensor to send its readings to Hubitat. Any ideas?

6

Which Matter/HomeKit sensor?

The sensor you linked to doesn't support Matter at all. It is a HomeKit device that is meant to be used with a Home hub. It will not work with any Matter controller, including Hubitat.

HomeKit and Matter are distinct protocols. They are only related insofar as Apple being a founding CSA member (along with Google and Amazon).

7

Have you setup an Apple Home automation? You need two Apple automations:

  1. Fibaro motion active turns on the virtual switch from Hubitat

  2. Fibaro motion inactive turns off the virtual switch from Hubitat.

This will cause the switch turning on and off to mirror the state of the Fibaro sensor. Hubitat will see the logging of the switch which you can use in your Hubitat automation. However, you need Apple Home automation to also turn the switch on and off based on motion from the Fibaro.

8

OK, as this is my first use of a device connected to Apple Home (rather than directly to Hubitat) I may have my terminology wrong. To try and be more specific, I have an Aeotec Multisensor 6 "Homekit" version which apparently does not speak z-wave and so cannot connect directly to Hubitat. I connected it to Apple Home and it shows up and indicates motion within Apple Home. However, I want to be able to use that motion as a trigger for Hubitat.

Re: JB10's suggestion, I am TRYING to get the Multisensor that is connected to Apple Home to just that -- trigger the virtual multisensor device in Hubitat -- bit it does not seem to be doingn so...

9

That's not what @JB10 suggested. Or what @kkossev and @jtp10181 suggested.

Their suggestion was to use motion as a trigger to change the state of a virtual switch exported from Hubitat to Apple Home.

The automation suggested by @JB10/@kkossev /@jtp10181 will work as long as you have an Apple Home hub. Like an Apple TV4, HomePod, or HomePod Mini.

Note that other types of events sensed by your bluetooth HomeKit sensor (such as temperature and light intensity) cannot be passed back to Hubitat. If you don't have a Home hub, you should consider replacing the Bluetooth HomeKit device with a Matter/z-wave/zigbee device that will work directly with Hubitat.

2 Likes
10

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.