When I search for a device using the search function and then add it to HomeKit using the sliders, everything works as expected. However, sometimes I encounter the problem that when I clear the search query using the cross and then enter a new search query, all devices previously connected to HomeKit suddenly appear to be disconnected. This does not seem to be intended.
I have resolved the issues you mentioned. Could you please check and provide feedback?
As far as I have been able to test it now, it works well.
v2.1.0
Improved HomeKit accessory information and bridge management.
Added an advanced option to generate a new HomeKit setup code for the bridge.
Normal bridge reset now keeps the existing HomeKit code.
Improved firmware handling for HomeKit accessories.
Improved reliability when quickly enabling multiple devices from the settings screen.
Fixed a settings search issue where previously enabled devices could appear disabled after clearing and re-entering a search query.
Minor stability and settings UI improvements.
I’m having a similar problem to another user earlier in this discussion thread. I have a number of Dreo products that I would like to pull into Homekit. But, I can’t get the bridge into Homekit.
Here is a snapshot, and the error code.
2ad1d9c0-835c-48eb-a295-cace0460c9f7
I’m sure it’s user error on my part, kindly point me in the correct path. I have over 40 Homekit products and I have tried to add this one via the instructions above. But, when I add the 8 digit code, it merely rturns to the accessory add page on my phone. I do see a Homey Bridge C93F available, but, I think this is HomeKitty.
Thanks for the log. This does not look like user error. The bridge was publishing correctly, but the Dreo climate devices were reporting Fahrenheit temperature ranges, and those values were being exposed to HomeKit as if they were Celsius. That caused invalid HomeKit temperature characteristics and may prevent pairing from completing.
Please update the app, restart it, make sure at least one device is enabled for HomeKit, then add the HomeKit Device Bridge again using the setup code shown in the app settings.
Thanks for the very quick reply!
I did add the bridge finally, so that part seems okay. I did update the app to the latest test version 2.1.1. So, we’re all good there. I’m attaching some screenshots from my iPhone showing what the device looks like in the Apple Home app (3 photos), then finally what it looks like in the Dreo app on the iPhone. The biggest discrepancy seems to be the current temperature. I also can’t control the set temperature.
error code dd974e2a-2009-42db-944f-8b603096dba3
Update the test version again. If HomeKit continues to show outdated cached values, please restart the application and uninstall and then re-add the Dreo accessory.
Excellent! It all works as expected.
I am trying out the app, but when I add a speaker it says not supported in Apple Home. Does anyone else have this issue? Or is it user error? 
Hello, unfortunately, if the speakers don’t support AirPlay, you won’t be able to stream via HomeKit. That’s why they’ll appear as unsupported devices.
Ah, I understand, thank you. I was hoping to just be able to control volume. Thanks again!
I see that the problem has not yet been solved with the released updates.
In your previous message, you said the problem had been resolved and that it was working well.
The problem with the search function has been resolved.
The problem below has not yet been resolved
The data is being sent, 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 understand. I’ll double-check it and send you a test version; I’d appreciate it if you could review it and get back to me.
@Kasper_Douma Hello, I’ve made the change. Could you please review it and provide feedback again?
I checked various apps. The data is coming through correctly now.
Thanks.
V 1.2.9
Changelog
- Improved HomeKit bridge publishing reliability.
- Added fallback handling for mDNS socket announcement failures.
- If
ciaopublishing fails with socket errors, the bridge now cleans up and retries using the next available mDNS strategy. - Reduced the chance of HomeKit bridge pairing/publishing failures caused by unstable or unavailable network interfaces.
V 2.1.11
- Fixed “Unresponsive Devices” Bug: Resolved a major core issue (stale device references) where devices would silently fail to respond to HomeKit commands after reconnecting or refreshing in the background. This improves stability across all accessories (Lights, Switches, Outlets, Thermostats, Locks, TVs, Fans, Humidifiers).
- Improved Responsiveness: Fixed a timing bug causing “No Response” errors in HomeKit for some Fan and Climate devices during state changes.
- Security Enhancements: Improved HomeKit Setup PIN generation algorithm for better security and proper avoidance of forbidden PIN codes.
- Garage Door Sync: Fixed an issue where the garage door state could become out-of-sync with HomeKit.
- Settings UI Improvements: Added missing device icons (Garage Door, Humidifier, Siren) and fixed modal dialogs to properly respect dark mode.
- Under-the-hood: Major code refactoring, eliminated race conditions during capability registrations, and enhanced overall app stability.
https://homey.app/en-tr/app/com.homekit.devicebridge/HomeKit-Device-Bridge/test/
