I think I’ve sent you a message but not sure hahah
You did
Hello! I am a VERY new user to Homey - just gone mine yesterday actually! I have a nicely functioning Apple HomeKit setup in my home and I like it, but wanted more functionality. I tried Home Assistant, but it was a disaster - I am not a programmer, HA was just more work than I wanted to put in.
But so far, I am loving Homey! My wife is more than happy with using her iPhone and HomeKit to do things - so I want to be able to control as much as possible in HomeKit, but personally I want to have access to the more advance capabilities in Homey. I heard about the HomeKit Experiment thing, and I heard about HomeKitty. I did a little bit of reading and went with HomeKitty. It seems fine - but later I heard about HomeKit Controller.
I read that HomeKitty was for getting Homey devices INTO HomeKit, and HomeKit Controller was for getting HomeKit devices INTO Homey. I asked about using both at the same time (since it seemed that that would give me the situation I was looking for), but it seems like I might have been misinformed.
So I will ask here - should I be using BOTH Homekitty AND HomeKit Controller at the same time? Or should I just use HomeKit Controller?
I have other questions (MANY other questions, actually), but I will stick with this one for now.
Thanks 
There should be no issue using them both.
BUT, do not pair HomeKitty with Homekit controller that makes no sense, with next update of the controller i will make sure Homekitty will not be listed in available devices.
I have the exact same problem. My FP2 sensor suddenly stopped working the other day, and I haven’t been able to get it working since.
Managed to get to the point where I enter the PIN, but it game me the error “on pair no service found for device”.
If you have an issue like this please report via diagnostic report!
I sent in debug logs.
1 Like
Ok…so it will be obvious here in a second that I am not very smart, so I will just own it - I am a moron. Ok, so now that THATS outta the way…
I keep seeing that I am supposed to connect my IOS IP or something like that… WHAT is the “IP?”
Thanks
Where are you seeing that?
I will be changing the code a bit in the next version. Might be a fix for this.
If I delete a device from HomeKit (so I can add it in HomeKit Controller), then go to Homey and try to add a new device in HomeKit Controller - all I see is a tile that says “HomeKit IP” - if I tap on it, it asks me to connect my HomeKit IP. It even has a nice picture of a device I have never seen before. I have no clue what HomeKit IP is though.
So, if I delete a device from HomeKit - and this HomeKit IP is not what I am supposed to be using or seeing - then where should I be seeing the device I just removed from HomeKit?
Ah okay… Homekit devices can be be connected through an IP (wifi) connection, bluetooth or thread/ matter transport. I currently only support IP transport through Wifi.
So when pairing devices using HK IP it will search for these devices that have advertised themselves on the network and are available for pairing, not connected to another homekit controller
1 Like
Ahh, ok that actually makes sense to me. Once upon a time I was a PC repair tech, so I am pretty much a hardware guy - software is mostly voodoo to me lol! But over the last few years I switched to Mac, and am trying to dip my toe in the software side…very VERY slowly lol!
But I am having a lot of fun with smart home stuff - this weekend is the first chance I have really had to try out Homey. The wife doesn’t really like me messing with things when she is home…but she is on a cruise with her mom, so I have a week to mess around with everything as much as I want!
So, I will probably have more questions…
Ok, so I have been spending the last few hours slowly moving devices from HomeKit into Homey. So far, literally everyone of them has turned out to be a matter device - so it was easy. Now I have run into my first non matter device. It’s a smart plug that is Apple HomeKit enabled.
For matter devices, I simply put the device into pairing mode through HomeKit, copied the code, removed the device, then added it to Homey. But with this plug, I don’t have the option to put it into pairing mode in HomeKit. Not even sure I remember how to put this plug into pairing mode.
Now, I DO have the HomeKit QR code… can you explain to me (remember, I am not very smart) in a detailed way, how I would do this so I can remove it from HomeKit and add it to HomeKit Controller?
What is the brand , model of the plug?
It is a Meross mss110
Was looking at a youtube pairing the MSS110 to HK. Below the qr code there should be 8 digits. That’s the PIN.
Now goto post 1 and follow that.
Ok, so now I think something is wrong. When I go to “add device,” I tap HomeKit Controller. Then I see a tile that says “HomeKit IP.” I tap on that, and a window comes up that says “Connect your HomeKit IP” and a button that says connect. When I tap on the “connect” button it takes me to a window that says “No new devices have been found.”
So, in the HomeKit Controller app, under app settings, there are two icons. One is a yellow “Home” looking icon, and the other is the log. I copied the log and have included it below - any idea what I need to do? I already tried uninstalling/reinstalling the app. If it matters, I have the Homey Pro 2023
undefined2025-04-13T15:16:46.140Z [log] [MyApp] cpu warning
2025-04-13T15:16:42.962Z [err] [ManagerDrivers] [Driver:hapIP] getDeviceFromFQDN No Device found Sharp 7203X 5353._hap._tcp.local
2025-04-13T15:16:42.961Z [log] [ManagerDrivers] [Driver:hapIP] UP for Sharp 7203X 5353._hap._tcp.local service count is 13
2025-04-13T15:16:42.949Z [err] [ManagerDrivers] [Driver:hapIP] getDeviceFromFQDN No Device found TCL G132X 5A27._hap._tcp.local
2025-04-13T15:16:42.948Z [log] [ManagerDrivers] [Driver:hapIP] UP for TCL G132X 5A27._hap._tcp.local service count is 12
2025-04-13T15:16:41.616Z [err] [ManagerDrivers] [Driver:hapIP] getDeviceFromFQDN No Device found MSS110-7a50._hap._tcp.local
2025-04-13T15:16:41.615Z [log] [ManagerDrivers] [Driver:hapIP] UP for MSS110-7a50._hap._tcp.local service count is 11
2025-04-13T15:16:41.613Z [err] [ManagerDrivers] [Driver:hapIP] getDeviceFromFQDN No Device found Camera-E1-3A6E._hap._tcp.local
2025-04-13T15:16:41.612Z [log] [ManagerDrivers] [Driver:hapIP] UP for Camera-E1-3A6E._hap._tcp.local service count is 10
2025-04-13T15:16:41.601Z [err] [ManagerDrivers] [Driver:hapIP] getDeviceFromFQDN No Device found HomePodSensor 538931._hap._tcp.local
2025-04-13T15:16:41.598Z [log] [ManagerDrivers] [Driver:hapIP] UP for HomePodSensor 538931._hap._tcp.local service count is 9
2025-04-13T15:16:41.585Z [err] [ManagerDrivers] [Driver:hapIP] getDeviceFromFQDN No Device found Aqara-Hub-E1-086B._hap._tcp.local
2025-04-13T15:16:41.583Z [log] [ManagerDrivers] [Driver:hapIP] UP for Aqara-Hub-E1-086B._hap._tcp.local service count is 8
2025-04-13T15:16:41.579Z [err] [ManagerDrivers] [Driver:hapIP] getDeviceFromFQDN No Device found Starling Home Hub BAF3._hap._tcp.local
2025-04-13T15:16:41.577Z [log] [ManagerDrivers] [Driver:hapIP] UP for Starling Home Hub BAF3._hap._tcp.local service count is 7
2025-04-13T15:16:41.564Z [err] [ManagerDrivers] [Driver:hapIP] getDeviceFromFQDN No Device found Tapo Power Strip C847._hap._tcp.local
2025-04-13T15:16:41.561Z [log] [ManagerDrivers] [Driver:hapIP] UP for Tapo Power Strip C847._hap._tcp.local service count is 6
2025-04-13T15:16:41.555Z [err] [ManagerDrivers] [Driver:hapIP] getDeviceFromFQDN No Device found Camera-E1-28C5._hap._tcp.local
2025-04-13T15:16:41.551Z [log] [ManagerDrivers] [Driver:hapIP] UP for Camera-E1-28C5._hap._tcp.local service count is 5
2025-04-13T15:16:41.545Z [err] [ManagerDrivers] [Driver:hapIP] getDeviceFromFQDN No Device found MSS425F-7e16._hap._tcp.local
2025-04-13T15:16:41.543Z [log] [ManagerDrivers] [Driver:hapIP] UP for MSS425F-7e16._hap._tcp.local service count is 4
2025-04-13T15:16:41.540Z [err] [ManagerDrivers] [Driver:hapIP] getDeviceFromFQDN No Device found Doorbell Repeater-CEED._hap._tcp.local
2025-04-13T15:16:41.537Z [log] [ManagerDrivers] [Driver:hapIP] UP for Doorbell Repeater-CEED._hap._tcp.local service count is 3
2025-04-13T15:16:41.504Z [err] [ManagerDrivers] [Driver:hapIP] getDeviceFromFQDN No Device found Aqara-Hub-M3-ADC1._hap._tcp.local
2025-04-13T15:16:41.501Z [log] [ManagerDrivers] [Driver:hapIP] UP for Aqara-Hub-M3-ADC1._hap._tcp.local service count is 2
2025-04-13T15:16:41.472Z [err] [ManagerDrivers] [Driver:hapIP] getDeviceFromFQDN No Device found HomeKitty 3C7A._hap._tcp.local
2025-04-13T15:16:41.469Z [log] [ManagerDrivers] [Driver:hapIP] UP for HomeKitty 3C7A._hap._tcp.local service count is 1
2025-04-13T15:16:41.455Z [log] [ManagerDrivers] [Driver:hapIP] discoveredHapBonjour Devices Ready start browsing your network
2025-04-13T15:16:41.452Z [log] [ManagerDrivers] [Driver:hapIP] discoverDevicesBonjour
2025-04-13T15:16:36.449Z [log] [ManagerDrivers] [Driver:hapIP] hapIP driver has been initialized
2025-04-13T15:16:36.146Z [log] [MyApp] Homekit Controller 1.4.2 has been initialized
2025-04-13T15:16:36.145Z [log] capturing stderr
2025-04-13T15:16:36.141Z [log] capturing stdout
I see a number of devices advertising on the network. They should appear, but only when not connected to the Apple Home App. You are absolutely sure that they are removed from the Home app?
The apps I have thus far removed were matter devices. I simply added them into Homey via the built in matter integration, and then HomeKitty put them back in HomeKit for me.
A wild card could be my Starling Hub. It takes Google devices and puts then into HomeKit for me. I have both Google and HomeKit linked with Homey. When I removed a matter device from HomeKit and had HomeKitty put it back for me, sometimes Starling would try and add a duplicate device - but I just went into Starling and deselected said duplicate.
All the matter devices I removed from HomeKit and had HomeKitty put back are working perfectly.
