This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Official
Comments
The app still recieves updates from my devices, even though I do not have any connection via homekit.
Network wise it can't be an issue as i have a Hue Bridge which doesn't lose the connection and is available at times when Homekit (Homey) has lost the connection ... btw the Homey app is still available and responsive as is the web interface, so it isn't Homey either!
One idea is that is has something to do with the amount of data reported from some sensors...?
Anyone else seeing similar patterns?
I will wait a few more days before adding some of my sensors.
Update on problem, I have 2 more units(ipad and one more Iphone) that is using homekit and there it is working, it is only on my phone it is not working ?
No news about this ?
Anyone knows some other way of exposing my Homey-devices to HomeKit (exept the Homey Kit-app)
Rgds Fredrik
@fredrikb - try to update and check
If there is a problem, I need a log.
If I try the other Homekit app, it works every time. There's nothing in the app-logs saying anything about this neither.
What to do?
I have tried to remove some devices and restart the app several times, but I can't get connection to my home app on iOS in any way.
Restarting the app seems to do what it should in the log, se pic attached, but nothing reflects on the phone:
gnrk
@gunnerk Did this happen on 1.2.4? or earlier?
When I installed 1.2.4 everything worked as supposed for some hours before I lost connections to all devices on my iPhone.
Update: The magic lasted only for half an hour or so, now we're back to the usual, no contact with homey devices on th phone. Tried log in from browser, restarting of both the app, phone and homey, no success.....
gnrk
somehow, a couple of versions back it was working flawlessly, now it is broken on 1.2.4... restarting the app solves it for me for now.
@fredrikb - Can you describe in more detail what devices lead to an error?