search

homebridge / homebridge

HomeKit support for the impatient.
https://homebridge.io
Apache License 2.0
23.83k stars 1.98k forks source link

HomeKit not working on iOS 11 #1414

Closed cb2206 closed 6 years ago

cb2206 commented 7 years ago

Hi All,

I've installed Homebridge on Raspberry Pi and it's working fine on my wife's iPhone with iOS 10.3.2 and it was working fine on my iPhone with iOS 10.3.2. I upgraded my iPhone to iOS 11 developer beta 4 and now on my iPhone, most devices are showing as "No Response". Only some are still working but it's not consistent. E.g. I have 3 TP-Link Smart Plugs, 2 work, 1 doesn't. (other devices: Hue lamps, TP-Link smart switches, Nest thermostats, garage door, ...)

In one of the other issues, it was mentioned to restart devices. I restarted homebridge (and the whole Raspberry), both iPhones, the 4th Gen Apple TV which I'm using as a hub but that unfortunately didn't change anything.

Does anyone else have similar issues? (= known issue with iOS 11) Anything else I can do to trouble shoot?

Thanks a lot Christian

macjeff commented 7 years ago

I already spoke about this but you need to make sure AppleTV is also upgraded to the latest beta or leave it off for now. And most likely you will have to delete everything from the phone and everything from the whole bridge data folder except for the config.jsn and then set it up again.

I’ve been running fine now for a couple days. I believe the root of the problem is in the AppleTV

Jeff

Sent from my iPhone

On Jul 28, 2017, at 8:53 AM, cb2206 notifications@github.com wrote:

Hi All,

I've installed Homebridge on Raspberry Pi and it's working fine on my wife's iPhone with iOS 10.3.2 and it was working fine on my iPhone with iOS 10.3.2. I upgraded my iPhone to iOS 11 developer beta 4 and now on my iPhone, most devices are showing as "No Response". Only some are still working but it's not consistent. E.g. I have 3 TP-Link Smart Plugs, 2 work, 1 doesn't. (other devices: Hue lamps, TP-Link smart switches, Nest thermostats, garage door, ...)

In one of the other issues, it was mentioned to restart devices. I restarted homebridge (and the whole Raspberry), both iPhones, the 4th Gen Apple TV which I'm using as a hub but that unfortunately didn't change anything.

Does anyone else have similar issues? (= known issue with iOS 11) Anything else I can do to trouble shoot?

Thanks a lot Christian

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

trulyspinach commented 7 years ago

Remove bridge from your home app then re-add helps. But I found that you need to change both the "username" and "pin" in homebridge config file to make HomeKit able to discover it again.

I used this method(I describe above) to make my HomeKit works again once, but about a couple of day after, all my accessories turned to "no response" again. so,, I have to re add it one more. I don't know if there is any bugs in beta 4 or something in homebridge needs to upgrade.

ElphaX commented 7 years ago

Don't mean to sound like an annoyance but it is a beta after all, we should expect these hiccups. Hopefully homebridge and the official release version of iOS11 doesn't have any issues... here's hoping.

cb2206 commented 7 years ago

Thanks, removing and re-adding Homebridge has worked. The beta is indeed very unstable regarding HomeKit so far. Having the same issues with Philips Hue. Thanks again for your responses.

nicwise commented 7 years ago

I've had a few issues, too. I'd love to know how I can provide more info (aside from "see if beta 5 sucks less")

So far, the main one for me is that when I add a new accessory (the bridge), it goes thru all the devices on there, but it'll ALWAYS show one (usually a switch) as "No response". This time, it's my coffee machine's WEMO switch, last time it was another WEMO switch for the heater.

No reason for either - they are both on and functional. Lucky, I can work around both using the WEMO app, so no big deal, but I'd love to know WHY it's "No response" - it can clearly find it, and find all the other things, too (I have 4 WEMO's, and 2 Broadlink RM3 Mini's), it just doesn't get a response from it.

Personally, I don't expect any rushed fixes - it is a beta after all - but if this is going to be something which breaks iOS 11 release, then it'd be good to try to find out whats causing it early in the game.

So far, I have iOS 11 all the things: iPhone 7, iPad, Apple TV.

Are there any device logs etc I can provide which might help tracking any of this down?

ferny18 commented 7 years ago

I'm actually having the same problem as @nicwise. There is always one random switch or light that appears as "No response" and even as "Not supported." I'm hoping someone can help.

nicwise commented 7 years ago

I was talking to a co-worker about it - apparantly, if you remove all the things, then re-setup using and iOS10 device, it's fine. I'm going to try this tonight - not sure how that would work given the AppleTV is iOS11

I only had to re-setup 'cos I moved homebridge into Docker :)

macjeff commented 7 years ago

You are correct that one device shows as not responding.

I tried the OS X 10.12 thing. It works until you open the home a few times and then they all go dead.

Jeff

Sent from my iPhone

On Jul 31, 2017, at 9:56 PM, Nic Wise notifications@github.com wrote:

I was talking to a co-worker about it - apparantly, if you remove all the things, then re-setup using and iOS10 device, it's fine. I'm going to try this tonight - not sure how that would work given the AppleTV is iOS11

I only had to re-setup 'cos I moved homebridge into Docker :)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

coltonshipley commented 7 years ago

I also have the one device is always "Not Supported" iOS11b4 here. It's odd because while you are setting it up once it gets to that it exits out of the setup. (like after you add it it says 1 of x devices and you can set names and types and then move on the the next, once it gets to the "Not Supported" device it exits that and takes you to the home page of the home app.

Giorgiofox commented 7 years ago

beta 5 out there: anyone tried?

coltonshipley commented 7 years ago

I have not yet, I have the new beta installed but I'm at work and haven't made it home yet. I'll probably try when I get there. I didn't see anything much in the change log in the new beta about homekit but that doesn't mean anything.

ferny18 commented 7 years ago

@Giorgiofox I just tried it, still the same for me. :/ One device shows up as "Not Supported." I tried rebooting Homebridge and even changed the config file but nothing seems to fix it.

macjeff commented 7 years ago

I think the fix is in HomeKit and Apple wont help with a bug report because they could care less if it works.

So we just live with it.

Jeff

On Aug 7, 2017, at 5:09 PM, ferny18 notifications@github.com wrote:

@Giorgiofox https://github.com/giorgiofox I just tried it, still the same for me. :/ One device shows up as no response.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nfarina/homebridge/issues/1414#issuecomment-320781298, or mute the thread https://github.com/notifications/unsubscribe-auth/ATbg_n3U3F9zsrBvHi36WqXfa2CMQrVxks5sV30IgaJpZM4OmkSq.

Giorgiofox commented 7 years ago

Umpf. I'm waiting to upgrade because I'm doing an intensive use of HomeKit. Really can't understand why it not work. @ferny18 Do you have also an Apple TV with beta?

DaveLinger commented 7 years ago

I am on beta 5 on my iphone and ipad - changed the homebridge name and pin and was able to pair the hub, but one of my lights shows up as not supported. Same behavior as beta 4. This is happening to one of my switches from smartthings.

ellisandy commented 7 years ago

I'm experiencing the same issue with Wemo switches.

What I did was add all the accessories using the homebridge-wemo-platform plugin, then find the one that was in the "Not Supported State", and added it using homebridge-wemo plugin.

Example:

{
        "bridge": {
                "name": "Home",
                "username": "AA:BB:CC:DD:EE:FF",
                "port": 51826,
                "pin": "123-45-678"
        },
    "platforms": [
           {
           "platform": "BelkinWeMo",
           "name": "WeMo Platform"
           }
    ],
    "accessories": [{
        "accessory": "WeMo",
        "name": "Bedroom Light",
        "wemo_name": "bedroom light"
    }]
}

This is less than ideal, because I have the same swift in the HomeKit app twice, but at least I can control all my devices again.

rlust commented 7 years ago

I have beta 4 IOS 11 and I am getting No Response for all devices

Giorgiofox commented 7 years ago

The same for me. Try beta 5! I've not here my beta device (iPhone 5s)

djstarr commented 7 years ago

I recommend reporting this via the Feedback app on the beta.

macjeff commented 7 years ago

I tried and even lied and said it was a HomeKit device. They asked for SysDiagnose. I sent and they said it is issue with HomeBridge which is not supported.

They closed the bug.

All other HomeKit devices working fine so not much I can say to change their mind.

Jeff

On Aug 9, 2017, at 4:22 PM, djstarr notifications@github.com wrote:

I recommend reporting this via the Feedback app on the beta.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nfarina/homebridge/issues/1414#issuecomment-321370625, or mute the thread https://github.com/notifications/unsubscribe-auth/ATbg_tAHY8j6mSMDXUH44K7IH27W5LVbks5sWhUSgaJpZM4OmkSq.

siavashvj commented 7 years ago

I just went from the latest stable version to the latest public beta on my ATV4, and this issue immediately started. So, it is definitely a problem with the ATV beta.

Anyone knows how to roll back from beta to stable on an ATV?

DaveLinger commented 7 years ago

I wouldn't say it's "definitely" a problem with the ATV beta. I am using an ipad as my homekit hub and have the issues described.

nicwise commented 7 years ago

yeah, you need to get the last 10.x IPA down from the dev portal, plug your AppleTV into your Mac/PC and iTunes, and do a restore from there - same as an iPhone, just more fiddly

Also you lose anything on the device - it's back to factory

On 11 August 2017 at 13:47, siavashvj notifications@github.com wrote:

I just went from the latest stable version to the latest public beta on my ATV4, and this issue immediately started. So, it is definitely a problem with the ATV beta.

Anyone knows how to roll back from beta to stable on an ATV?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nfarina/homebridge/issues/1414#issuecomment-321715982, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHztAg8GCpZSOIpjcA86AFDBN2s2tLlks5sW7KjgaJpZM4OmkSq .

-- Nic Wise t. +64 21 676 418 | @fastchicken b. http://www.fastchicken.co.nz/

ganonp commented 7 years ago

Yeah, I'm on ios 11 beta 5 and all of my devices connected via homebridge show up as "no response" on both my and my girlfriend's phones, but she is actually able to click them and use them while I am not.

siavashvj commented 7 years ago

Alright, rolled back to tvOS 10, and everything works perfectly again.

Siavash Vatanijalal

11 aug. 2017 kl. 05:05 skrev Ganon notifications@github.com:

Yeah, I'm on ios 11 beta 5 and all of my devices connected via homebridge show up as "no response" on both my and my girlfriend's phones, but she is actually able to click them and use them while I am not.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

clearscreen commented 7 years ago

Just a note, this is affecting me as well and I do not have an Apple TV, I just have iOS devices.

macjeff commented 7 years ago

Do you have an iPad set as HomeKit hub?

Jeff

On Aug 12, 2017, at 9:50 PM, chazzzle notifications@github.com wrote:

Just a note, this is affecting me as well and I do not have an Apple TV, I just have iOS devices.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nfarina/homebridge/issues/1414#issuecomment-322016536, or mute the thread https://github.com/notifications/unsubscribe-auth/ATbg_mIYXsbchHMtOGhOoHha0XA8QVNsks5sXlZNgaJpZM4OmkSq.

clearscreen commented 7 years ago

running hubless

clearscreen commented 7 years ago

Updated to Developer Beta 5, was able to add the homebridge but I am having the save behavior as @DoucheBaguette where a random device seems to have appeared as "not supported." I have an identical device to the one that is supposedly 'not supported' that is working just fine.

JotWee commented 7 years ago

I can second this. One random (?) device is blocked by HomeKit, while all others (even devices of the same kind) work perfectly.

trulyspinach commented 7 years ago

For those who have one device "Not Support" after re-add Homebridge: Seems like this issue only occur on "platform", try delete cachedAccessory and restart homebridge(no need for re-add). I do this for my Yeelight platform and it works.

macjeff commented 7 years ago

not for me

On Aug 13, 2017, at 9:47 AM, HaoYan Qi notifications@github.com wrote:

For those who found one device "Not Support" after repair Homebridge: Seems like this issue only occur on "platform", try delete cachedAccessory and restart homebridge(no need for repair). I do this for my Yeelight platform and it works.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nfarina/homebridge/issues/1414#issuecomment-322043242, or mute the thread https://github.com/notifications/unsubscribe-auth/ATbg_s9dgW3_8YrFuZ4PJ3uIYshl1j3Tks5sXv6EgaJpZM4OmkSq.

pdlove commented 7 years ago

I’ve played with this a lot. It looks like one accessory on the bridge will show as “Not Supported” even though the generated accessory provided to HomeKit looks fine. I tested this by copying the same accessory multiple times to provide to HomeKit and only one shows this way. Can anyone else help me out on this... I’ve only ever seen one accessory reported this way even with 40 being passed. All of my tests have shown it to be the 7th Lightbulb parsed. Has anyone seen any device other than a light affected?

JotWee commented 7 years ago

yes, I’ve seen any kind of accessory

pdlove commented 7 years ago

@JotWee Thank you. To be clear, I believe this to be an issue with bridged accessories within IOS and not a HAP-NodeJS or Homebridge issue. Anyone from Apple follow this feed? I'm on Homebridge and can provide examples of why I believe so if anyone who can do anything is listening. I'm also going to get my Macbook from work tomorrow so I can try and look into the debug logs when the file is loaded.

coltonshipley commented 7 years ago

Has anyone tried iOS11b6 . I am at work and can't do it but I will try when I get home.

macjeff commented 7 years ago

Same here. installed it but cant do it yet.

I was told friday by apple they are in crunch to finish the build that will go onto the new iPhones.

I assume this is it.

They said also starting Friday any new bug reports will be in the 11.01 beta 1 not 11.0.

So if beta 6 does not fix it, that could be it. Maybe one more beta but that would be it, but I think this was it for 11.0.0

Jeff

On Aug 14, 2017, at 2:57 PM, neruve notifications@github.com wrote:

Has anyone tried iOS11b6 . I am at work and can't do it but I will try when I get home.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nfarina/homebridge/issues/1414#issuecomment-322277916, or mute the thread https://github.com/notifications/unsubscribe-auth/ATbg_rBMhR-u1jDJh0zjL3B9d1QzzgZUks5sYJidgaJpZM4OmkSq.

kjagiello commented 7 years ago

Just tried the latest beta and it worked for me after following @SPINACHCEO's advice. I changed both username and pin code in the config file and then I was able to pair with homebridge.

coltonshipley commented 7 years ago

How many devices do you have @kjagiello ? Is it more than 7? If so are you getting the "Not Supported" error on one of them?

macjeff commented 7 years ago

I know you asked someone else but I have different instances of homebridge. Smallest # of devices is 3 for one plugin and largest is 96 accessories for another (almost to the 100 device limit?

All of them behave the same way

  1. Before upgraded Apple TV (but iphone was upgraded) all of my devices would work and then turn not supported.

  2. After upgrading the Apple TV only one device for each plugin shows not supported.

  3. I went back to old os on Apple TV and iphone And problem went away until I upgraded again.

  4. I restored my iphone and Apple TV without a backup and same issue (so i have since went back to my backup)

  5. I have real HomeKit devices and they don’t have any issues so it’s a homeBridge big with new OS.

And we might see a beta 7 but they are in process of wrapping things up. I have NOT tested with beta 6 yet. Last test was beta 5.

Jeff

Sent from my iPhone

On Aug 14, 2017, at 3:42 PM, neruve notifications@github.com wrote:

How many devices do you have @kjagiello ? Is it more than 7? If so are you getting the "Not Supported" error on one of them?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

coltonshipley commented 7 years ago

Even if it is an iOS bug and apple doesn't fix it you would think the devs of homebridge could find a workaround...

kjagiello commented 7 years ago

@neruve Just tried exactly 8 devices and yeah, one of them is not responding anymore.

macjeff commented 7 years ago

under beta 5 or 6?

Jeff

On Aug 14, 2017, at 4:24 PM, Krzysztof Jagiełło notifications@github.com wrote:

@neruve https://github.com/neruve Just tried exactly 8 devices and yeah, one of them is not responding anymore.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nfarina/homebridge/issues/1414#issuecomment-322299182, or mute the thread https://github.com/notifications/unsubscribe-auth/ATbg_nwSQ0oZdcUs80kTDCXCvRELUk7Tks5sYKzrgaJpZM4OmkSq.

coltonshipley commented 7 years ago

It kinda sucks but could we work around this by just running seperate homebridge instances with about 5 accessories each? or does the error still occur?

kjagiello commented 7 years ago

@macjeff I have installed the latest public beta two hours ago, so my guess is beta 6. Correct me if I'm wrong.

macjeff commented 7 years ago

Actually I do not think the public beta six is out yet… Developer beta six was pushed out today and the public beta is usually 1 to 2 days behind it.

Here is the bill number if you want to check in it against yours in the settings app under general/about.

15A5354b

Jeff

Sent from my iPhone

On Aug 14, 2017, at 5:07 PM, Krzysztof Jagiełło notifications@github.com wrote:

@macjeff I have installed the latest public beta two hours ago, so my guess is beta 6. Correct me if I'm wrong.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

pdlove commented 7 years ago

I'm going to do some work tonight and tomorrow to get the workaround in place for this. It doesn't looks like beta 6 has resolved it. Even if/when Apple does resolve it, the work around would still work fine anyway. To make everyone aware... the issue is that every device is assigned an Accessory ID (aid) and every service is assigned a Service ID (iid). If any accessory has an aid that equals the bridge's primary iid, that accessory is marked as "Not Supported". The aid must be sequential, so the work around is for the iid on the bridge to be overly inflated. Should be a simple implementation but it needs to be tested in a few situations. If anyone has an IOS 11 implementation that doesn't have one device as Not Supported then I'd be shocked. Does anyone have any hubs with HomeKit? I'm curious if the same thing happens with them.

macjeff commented 7 years ago

By hub, if you just meet at HomeKit hub like the Apple TV or iPad… Yes the problem still exists.

Every one of my Home bridge instances has an unsupported device and I would be glad to Testa’s for you with your beta version of the fix.

Jeff

Sent from my iPhone

On Aug 14, 2017, at 6:25 PM, pdlove notifications@github.com wrote:

I'm going to do some work tonight and tomorrow to get the workaround in place for this. It doesn't looks like beta 6 has resolved it. Even if/when Apple does resolve it, the work around would still work fine anyway. To make everyone aware... the issue is that every device is assigned an Accessory ID (aid) and every service is assigned a Service ID (iid). If any accessory has an aid that equals the bridge's primary iid, that accessory is marked as "Not Supported". The aid must be sequential, so the work around is for the iid on the bridge to be overly inflated. Should be a simple implementation but it needs to be tested in a few situations. If anyone has an IOS 11 implementation that doesn't have one device as Not Supported then I'd be shocked. Does anyone have any hubs with HomeKit? I'm curious if the same thing happens with them.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

cb2206 commented 7 years ago

@pdlove Got home bridge and a Philipps hue bridge. Also willing to be a beta tester

bassrock commented 7 years ago

Having the same issue, I have about 35 devices on Homebridge, mainly using the Wink3 platform and 1 of them is stated as not supported and is a standard light switch that has worked fine before.