[APP][Pro] HomeKit Device Bridge

Yes. The error came down to the light I had initially added wasn’t set up properly, so deleting that light and re-adding it allowed the rest to kick over and now it’s working well. The only problem I have found now is that my Lutron Caseta ceiling fan switch is binary instead of variable…but that’s the case with everything except the Lutron app apparently.

Thank you!

I’m glad the issue has been resolved. If you send me the diagnostic report, I’ll check to see if I can get the Lutron Caseta ceiling fan switch to work in stages.

Here you are! Thank you for being so active.

5dc0f281-f362-440f-b72a-04c2e170de8f

Thank you for sending the logs. I noticed that the Lutron Caseta fan displays its speed as fixed levels instead of a standard dim/fan_speed value. I’ve added support for fan speeds such as Off, Low, Medium, Medium-High, and High; as a result, it should appear as a variable-speed fan in the next update.

Additionally, I’ve added a safeguard to prevent writing errors in the logs caused by deleted or re-added light IDs in Adaptive Lighting.

I’d like you to install the test version and let me know the results.

Test v2.0.15

Added

  • Added per-device HomeKit type overrides from the settings page.
  • Added per-light Adaptive Lighting control with Auto, On, and Off modes.
  • Added compatibility diagnostics in the settings page to explain classification warnings.

Improved

  • Improved WLED handling by allowing Adaptive Lighting to be disabled without removing the light from HomeKit.
  • Improved watchdog behavior to avoid unnecessary listener recovery in quiet homes.
  • Improved settings page rendering so saved override and Adaptive Lighting selections stay visible after reloads.

Fixed

  • Fixed Adaptive Lighting setting changes causing HomeKit room assignments to reset.
  • Fixed Adaptive Lighting selections reverting to Auto while saving.

Test v2.0.16

Fixed an issue where changing a device’s Expose as type in Settings could update inside the app but not appear correctly in HomeKit.
Added fallback support for button/remote devices manually exposed as Switch or Light.
Button-like devices without a real onoff capability are now exposed as momentary HomeKit switch/light triggers.
Improved Settings live updates so device category lists no longer temporarily disappear after changing Expose as.
Added clearer compatibility warnings for devices exposed as momentary triggers.

Through the Shelly app, I add lights to HomeKit. I’ve noticed that all Shelly devices also appear with a temperature sensor. Is this necessary, since it doesn’t seem to add much value in my opinion, or can it be disabled on a per-device basis?

In addition, I can see information for each device such as the manufacturer, serial number, model, and firmware version. Is it possible to customize these details so that they are clearer and easier to identify?

Current information:

Information via Matter app:

Do the light bulbs you use also have a temperature sensor feature? If so, HomeKit will sync that information as well.

If there is a request, I will try to add an option that prevents unwanted sensor data from being transmitted to Homekit.

Not the lamps themselves, but the module that is placed behind a switch.

Unfortunately, the temperature sensor is not provided with a function via other apps (Matter, HomeKitty, Experimental HomeKit).

I’ve released an update that makes the device information display more clearly and allows you to remove any unwanted features when transferring to HomeKit. I’d appreciate it if you could test it and let me know what you think.

v2.0.17

Wow, that was added quickly. Looks good.
The correct name is not (always) displayed yet for Manufacturer and Model. See the Kaarslicht app, for example.

As for firmware, it is always 0.0. That could also be omitted.

Version information is required by HomeKit; if Homey cannot provide this information, it will inevitably appear as 0.0 there.

v2.0.18

HomeKit accessory information has been improved using Homey driver metadata for manufacturer and model details.
The stability of settings synchronization has been improved when multiple devices or options are changed quickly.
General stability and validation improvements.

I have noticed that there is a difference between Homey and HomeKit. In Homey, I can set the temperature starting from 5°C, but in HomeKit, the lowest adjustable temperature is 10°C. This applies to the Honeywell Home evohome app.

Hello, I’ve applied the fix. Could you test it and let me know the result? If it still shows 10 degrees, you may need to remove the device and add it again.

Looks good.

Were you able to resolve this so that the correct name is displayed?

If you’re asking about the manufacturer and other details listed in the device information section, they should be displayed more clearly. They appeared correctly on the devices I used. But if you test it and let me know, I can check again.

The data is being transmitted, but as you can see in the image, the app is in Dutch while the displayed data is still in English. That does not seem correct to me. The data should be displayed in the same language as the app.

I hadn’t noticed that; I’ll release a fixed version in the next update. Your feedback is valuable to me. Please don’t hesitate to report any issues you find.