HomeKit not working on iOS 11

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

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<EMAIL_ADDRESS>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.

Remove bridge from your home app then re-add it 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 "Not respond" 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.

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.

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.

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.

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

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 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<EMAIL_ADDRESS>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.

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.

beta 5 out there: anyone tried?

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.

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

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<EMAIL_ADDRESS>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.

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?

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.

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.

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

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

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

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<EMAIL_ADDRESS>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.

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?

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.

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<EMAIL_ADDRESS>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/

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.

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

11 aug. 2017 kl. 05:05 skrev Ganon<EMAIL_ADDRESS>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.

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

Do you have an iPad set as HomeKit hub?
Jeff

On Aug 12, 2017, at 9:50 PM, chazzzle<EMAIL_ADDRESS>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.

running hubless

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.

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

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.

not for me

On Aug 13, 2017, at 9:47 AM, HaoYan Qi<EMAIL_ADDRESS>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.

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?

yes, I’ve seen any kind of accessory

@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.

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

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<EMAIL_ADDRESS>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.

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.

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?

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

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

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

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

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

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<EMAIL_ADDRESS>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.

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

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

under beta 5 or 6?
Jeff

On Aug 14, 2017, at 4:24 PM, Krzysztof Jagiełło<EMAIL_ADDRESS>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.

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?

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

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<EMAIL_ADDRESS>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.

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.

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<EMAIL_ADDRESS>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.

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

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.

This issue seems not to be fixed with beta 6

Has anyone raised this with Apple, yet? It seems to be a HomeKit hub issue, with ATV or iPad?

Yes… I already posted that I put in a bug report and they asked for a sys diagnose.  They said my problems are caused by running home bridge and Stop it in and my problems  will go away.
I did not expect anything else because in the eyes of Apple home bridge is illegal since all HomeKit devices require an apple HomeKit chip and that’s how they make their money off devices.   Home bridge emulates this trip so I was not going to help us get it working.
Jeff
Sent from my iPhone

On Aug 15, 2017, at 6:34 AM, Dan Bennett<EMAIL_ADDRESS>wrote:
Has anyone raised this with Apple, yet? It seems to be a HomeKit hub issue, with ATV or iPad?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

If you want to re-add your homebridge (which enabled my bridge to work again on the current IOS11 beta), you don't need to change the username and pin.  Do the following instead

remove the bridge from the Home app
remove the persist directory from homebridge (same directory as your config.json)
restart homebridge
re-add to Home

Did not work for me

Am 15.08.2017 um 16:50 schrieb bkmartin<EMAIL_ADDRESS>If you want to re-add your homebridge (which enabled my bridge to work again on the current IOS11 beta), you don't need to change the username and pin. Do the following instead
remove the bridge from the Home app
remove the persist directory from homebridge (same directory as your config.json)
restart homebridge
re-add to Home
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

This is an issue with iOS 11 and remove/re-add the bridge in iOS won’t fix it. This issue will only occur if you have more than 6 accessories in homebridge. We’ll try to release a workaround if the issue isn’t fixed in future betas.

what about the "No Response" issue? can you do a work around for that?
Homebridge accessories get blocked all the time with iOS 11, I have both iPad and Apple TV4 as hubs, both updated to the latst beta versions.

By the way, I found out that when removing that accessory only (the "Not supported" one) and re-adding it, it will solve the issue with that accessory

I have a Hue bridge with 7 devices in iOS 11, and Homebridge with 7 other devices. And with Hue bridge, everything is working well. But with Homebridge, the 6th device appears as 'Not supported'
So I think this is not a iOS 11 only issue.

Give it a try with Homebridge 0.4.25 which was just updated. This shout resolve the "Not Supported" issue and who knows what else.

It's working! After removing the bridge from Home App, removing accessories an persist folder, and then restarting an adding homebridge, no more 'unsupported' devices. All devices can be configured without any issues.
Thank You!

@pdlove "If anyone has an IOS 11 implementation that doesn't have one device as Not Supported then I'd be shocked."
I'm running iOS 11 on my iPhone and got no devices showing Not Supported. I have to say I'm on a fairly old version of homebridge. I think, I installed it about a year ago and didn't do an update :rofl:
Greet Jacko

@pdlove Yeah, me too. I had that problem the brief moment I was running tvOS 11. But not before, and not now after I've downgraded to tvOS 10 again. I've been running iOS 11 beta on bort my iPad and iPhone since the first iOS 11 beta.

Oh awesome, will update and find out.
Now to shout nicely at the person who added Alexa support to update :-)

Dan,
I've been watching this and am going to update shortly, just waiting for the flurry of change to complete.
Sent from my iPad

On Aug 16, 2017, at 4:26 AM, Dan Bennett<EMAIL_ADDRESS>wrote:
Oh awesome, will update and find out.
Now to shout nicely at the person who added Alexa support to update :-)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@NorthernMan54 - Wonderful! 😄
I'm not home, devices showing as not supported. Updated remotely to the newest Homebridge stock version and now all devices are online and working (without me deleting persist etc...). So I think @pdlove the fix (being the latest HAP) has resolved this issue.

The homebridge update has fixed my issue as well. (on beta 6)

I'm on beta 6. updated to new homebridge release via npm update -g, restarted homebridge. All accessories were still showing as "no response". Remove homebridge and tried to add it again but the scanning functionality didn't recognize the code in the syslog output and also manually entering the code didn't help.
Also tried changing name, username and pin but also without success. I was able to add a Philipps hue bridge successfully.
Any ideas?

Anytime I update to a new release I have to delete the persists and accessories folders in homebridge folder.
Then I have to erase the device.
Then I have to add it again.
Then it works fine.  This happened with .23 and .24 version and will do .25 tonight.
Only bad part is you loose all the rooms!!!
Jeff

On Aug 16, 2017, at 10:49 AM, cb2206<EMAIL_ADDRESS>wrote:
I'm on beta 6. updated to new homebridge release via npm update -g, restarted homebridge. All accessories were still showing as "no response". Remove homebridge and tried to add it again but the scanning functionality didn't recognize the code in the syslog output and also manually entering the code didn't help.
Also tried changing name, username and pin but also without success. I was able to add a Philipps hue bridge successfully.
Any ideas?
—
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-322796465, or mute the thread https://github.com/notifications/unsubscribe-auth/ATbg_vBBNuFf52Bvt8QzqEbtY0O5HB6Jks5sYwGGgaJpZM4OmkSq.

@macjeff Something isn't right with that. I've updated through several revisions without an issue. What plugins are you using?

I have multiple instances.   Each one a separate plugin.
One netatmo
One ISY
One Ecobee
all of them ALL devices go unsupported with each update.
maybe its that I am running it on OS X and not Raspberry Pi.
This has happened since day 1.
And thats why I am waiting to do the newest homebridge update until tonight so I can add everything back in.
Jeff

On Aug 16, 2017, at 11:39 AM, pdlove<EMAIL_ADDRESS>wrote:
@macjeff https://github.com/macjeff Something isn't right with that. I've updated through several revisions without an issue. What plugins are you using?
—
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-322812196, or mute the thread https://github.com/notifications/unsubscribe-auth/ATbg_iIn5tDXJbpmGiDzJ5SyePgKc5Pmks5sYw0jgaJpZM4OmkSq.

deleted persist and accessories folders but no luck so far. :-(

@cb2206 You may have to change the username in homebridge as well.
A little background on what can cause this:
When the phone and homebridge pair, they store their encryption keys based on the remote device's ID. IOS stores it somewhere in the HomeKit database and Homebridge stores it in the persist folder.
If a bad value is sent for a Characteristic (Out of range or wrong data type), IOS will mark the bridge as defunct. Because all the data is stored in persist that let it to this condition you have to delete persist to recover. Changing the username just ensures IOS sees the bridge as a "new" device and begins a new pairing process.
The latest round of updates for HAP-NodeJS perform data validation and try to prevent invalid values from ever getting to IOS.

@pdlove thanks for the quick reply.
I repeated what I did before but this time also changed the username and now getting errors in the log about duplicate characteristics. The HS100 module is for TP-Link smart plugs and I have 3 of those. Could this be a bug in the module?
Aug 16 11:45:29 raspberrypi homebridge[24344]: [8/16/2017, 11:45:29 AM] Adding: TV
Aug 16 11:45:29 raspberrypi homebridge[24344]: /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Service.js:76
Aug 16 11:45:29 raspberrypi homebridge[24344]: throw new Error("Cannot add a Characteristic with the same UUID as another Characteristic in this Service: " + existing.UUID);
Aug 16 11:45:29 raspberrypi homebridge[24344]: ^
Aug 16 11:45:29 raspberrypi homebridge[24344]: Error: Cannot add a Characteristic with the same UUID as another Characteristic in this Service: 00000052-0000-1000-8000-0026BB765291
Aug 16 11:45:29 raspberrypi homebridge[24344]: at Service.AccessoryInformation.Service.addCharacteristic (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Service.js:76:13)
Aug 16 11:45:29 raspberrypi homebridge[24344]: at Hs100Platform.addAccessory (/usr/lib/node_modules/homebridge-hs100/index.js:81:17)
Aug 16 11:45:29 raspberrypi homebridge[24344]: at Client.Hs100Platform.client.on (/usr/lib/node_modules/homebridge-hs100/index.js:50:14)
Aug 16 11:45:29 raspberrypi homebridge[24344]: at emitOne (events.js:96:13)
Aug 16 11:45:29 raspberrypi homebridge[24344]: at Client.emit (events.js:191:7)
Aug 16 11:45:29 raspberrypi homebridge[24344]: at Client. (/usr/lib/node_modules/homebridge-hs100/node_modules/hs100-api/lib/client.js:87:14)
Aug 16 11:45:29 raspberrypi homebridge[24344]: at emitTwo (events.js:106:13)
Aug 16 11:45:29 raspberrypi homebridge[24344]: at Socket.emit (events.js:194:7)
Aug 16 11:45:29 raspberrypi homebridge[24344]: at UDP.onMessage [as onmessage] (dgram.js:544:8)
Aug 16 11:45:29 raspberrypi systemd[1]: homebridge.service: main process exited, code=exited, status=1/FAILURE
Aug 16 11:45:29 raspberrypi systemd[1]: Unit homebridge.service entered failed state.

@cb2206 i had the same issue. My workaround was to limit the accessories exposed to homebridge to just the ones i need. It also seems to work exactly one time after deleting the persist and accessories folder.

@christianbader Was that with the same plugin or a different one?

@pdlove no - i‘m using domoticz with the homebridge-edomoticz plugin and homebridge. Never got this error until i updated homebridge today to .25

I did NPM Update instead of NPN Install and i did not have to redo all my devices.
BUT
the .25 version still had the NOT SUPPORTED until I deleted the devices and set them up from scratch.
Jeff

On Aug 16, 2017, at 8:20 PM, NorthernMan54<EMAIL_ADDRESS>wrote:
@DanBennettUK https://github.com/danbennettuk
I updated my fork of homebridge and HAP-NodeJS to the latest versions. Update again and try it out, your Alexa device should be working with the IOS 11 updates.
—
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-322934677, or mute the thread https://github.com/notifications/unsubscribe-auth/ATbg_iU0R5_p1fhUssatfGo2hl1eYG-Dks5sY4dmgaJpZM4OmkSq.

Found the solution! all is working fine now on ios 10.3.3!  here are the steps i did:
Stop homebridge,
update homebridge  (sudo npm install -g --unsafe-perm homebridge)
Deleted the PERSIST and ACCESSORIES folders in the ~/.homebridge directory
Restart Avahi (sudo systemctl restart avahi-daemon)
Delete homekit house on ios
start homebridge
add to homekit andf it works like a charm!

With beta 7 all problem seem solved !
Il giorno lun 21 ago 2017 alle 20:28 jeroen1973<EMAIL_ADDRESS>ha scritto:

Found the solution! all is working fine now on ios 10.3.3! here are the
steps i did:
Stop homebridge,
update homebridge (sudo npm install -g --unsafe-perm homebridge)
Deleted the PERSIST and ACCESSORIES folders in the ~/.homebridge directory
Restart Avahi (sudo systemctl restart avahi-daemon)
Delete homekit house on ios
start homebridge
add to homekit andf it works like a charm!
—
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-323817622,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsBDwG0JU4i4vM9jiVKJNIlSyxZu-VIks5sacxMgaJpZM4OmkSq
.

--
Giorgio
<EMAIL_ADDRESS>Secure<EMAIL_ADDRESS>

Not here sadly. I’ll refresh the whole thing from scratch and try again...
I have a feeling it’s the Apple TV breaking it still.
Regards,
Dan Bennett

On 21 Aug 2017, at 23:04, Giorgio Campiotti<EMAIL_ADDRESS>wrote:
With beta 7 all problem seem solved !
Il giorno lun 21 ago 2017 alle 20:28 jeroen1973<EMAIL_ADDRESS>ha scritto:

Found the solution! all is working fine now on ios 10.3.3! here are the
steps i did:
Stop homebridge,
update homebridge (sudo npm install -g --unsafe-perm homebridge)
Deleted the PERSIST and ACCESSORIES folders in the ~/.homebridge directory
Restart Avahi (sudo systemctl restart avahi-daemon)
Delete homekit house on ios
start homebridge
add to homekit andf it works like a charm!
—
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-323817622,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsBDwG0JU4i4vM9jiVKJNIlSyxZu-VIks5sacxMgaJpZM4OmkSq
.

--
Giorgio
<EMAIL_ADDRESS>Secure<EMAIL_ADDRESS>—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Strange: also here there are an Apple TV (not upgraded to 7 yet)
Il giorno mar 22 ago 2017 alle 00:29 Dan Bennett<EMAIL_ADDRESS>ha scritto:

Not here sadly. I’ll refresh the whole thing from scratch and try again...
I have a feeling it’s the Apple TV breaking it still.
Regards,
Dan Bennett

On 21 Aug 2017, at 23:04, Giorgio Campiotti<EMAIL_ADDRESS>wrote:
With beta 7 all problem seem solved !
Il giorno lun 21 ago 2017 alle 20:28 jeroen1973 <
<EMAIL_ADDRESS>ha scritto:

Found the solution! all is working fine now on ios 10.3.3! here are the
steps i did:
Stop homebridge,
update homebridge (sudo npm install -g --unsafe-perm homebridge)
Deleted the PERSIST and ACCESSORIES folders in the ~/.homebridge
directory
Restart Avahi (sudo systemctl restart avahi-daemon)
Delete homekit house on ios
start homebridge
add to homekit andf it works like a charm!
—
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-323817622>,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/ABsBDwG0JU4i4vM9jiVKJNIlSyxZu-VIks5sacxMgaJpZM4OmkSq

.

--
Giorgio
<EMAIL_ADDRESS>Secure<EMAIL_ADDRESS>—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

—
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-323869192,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsBD5TS7ULPEUl5ssZlTeWgbyuL-FBJks5sagSsgaJpZM4OmkSq
.

--
Giorgio
<EMAIL_ADDRESS>Secure<EMAIL_ADDRESS>

Finally got  chance to update all the things. My setup is:
iPhone/iPad on 11b7
AppleTV on 11b7
Latest homebridge running on a linux VM in docker
Everything is working. I cleared out all my state (.homebridge folder) and changed the pin and MAC address in the config. Readded everything (yay no "not responding" items!) and setup all the schedules etc.
💯 working.
Thanks so much to those who looked into this and fixed it. <3

This evening after a blackout also for me all devices are not responding... I will try to update

After update to iOS 11 beta 8 all device are not responding again ;(

working fine for me

been working 100% for me since .26 (including .27).  Been 1-2 weeks with zero issues.
Jeff

On Aug 29, 2017, at 6:45 AM, justme-1968<EMAIL_ADDRESS>wrote:
working fine for me
—
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-325626315, or mute the thread https://github.com/notifications/unsubscribe-auth/ATbg_vDHyfk7YzZzuEbX2VByROmCWkZYks5sc-u2gaJpZM4OmkSq.

jeroen1973 Thanks. Your steps fixed my issues.

Updated iPhone 7 Plus to iOS 11 beta 8 (p.b. 7) from 10.3.3. No "not responding" issues. I use iPad mini 2 on iOS 10.3.3 for Home Centre (I don't know that term in English as I use Russian on iOS). After some time I upgraded iPad too. When iPad was on iOS 10.3.3, there was no issues with remote controlling (through iCloud) on iOS 11b8 on iPhone. I only cleared accessories and persist folders, and I also changed MAC, and re-added HomeBridge to HomeKit.
Strage things: my old Home, which I deleted when I was on 11b1 (and then downgraded) appeared with very old accessories o_O.

Just for reference, I just updated my phone to iOS 11 GM from 10.3.3 and everything was not responding.  Updated HomeBridge to the latest version and now everything is working.  My ATV was already running the beta OS.

And also just for reference, I had issues after installing iOS 11 GM (i wasn't beta-testing and I don't own an Apple TV). The solution from @jeroen1973 worked (delete the configuration iOS side and removing ./accessories/ and ./persist/ folders) . The only downside is that I have to reconfigure every devices and scenes now, but that's okay (as long as it works :) ). Thanks guys

Interestingly for me I find that homebridge does not work when the Apple TV is on. When it’s on, there is no response from all devices. When it’s off (or asleep) then they respond...
Regards,
Dan Bennett

On 12 Sep 2017, at 23:53, Florentin Le Moal<EMAIL_ADDRESS>wrote:
And also just for reference, I had issues after installing iOS 11 GM (i wasn't beta-testing and I don't own an Apple TV). The solution from @jeroen1973 worked (delete the configuration iOS side and removing ./accessories/ and ./persist/ folders) . The only downside is that I have to reconfigure every devices and scenes now, but that's okay (as long as it works :) ). Thanks guys
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

One problem I have before was that I have 3 Apple TV 4. 3 home hub was confusing home app! So I turn off 2 and I left only one as home hub

Just upgraded to iOS 11 release version and found all my devices in Home showing as unavailable with the little exclamation mark next to them. However on an iOS 10 device everything was still working as expected.
Mistakenly tried Siri on iOS11 device and it surprisingly worked, then checked and all devices in iOS 11 was now avaialble. Never touched or restarted the RaspberryPi running homebridge.

I just updated to IOS11 and was having all kinds of problems. My home kit wasn't working and then it disappeared all together. heres what I did to get it working:

Updated TVos
deleted all files in my home bridge folder except config.json
edited my config.json

changed my home bridge name
changed the port (don't know if this is necessary)
changed the pin

deleted my home and started fresh on the IOS app

Just did a restart of pi and All is working!
Jeroen van der Wal
Op 20 sep. 2017 om 01:27 heeft JacobRichards<EMAIL_ADDRESS>het volgende geschreven:
I just updated to IOS11 and was having all kinds of problems. My home kit wasn't working and then it disappeared all together. heres what I did to get it working:
Updated TVos
deleted all files in my home bridge folder except config.json
edited my config.json
changed my home bridge name
changed the port (don't know if this is necessary)
changed the pin
deleted my home and started fresh on the IOS app
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

FYI I upgraded everything to iOS11 and TvOS11 and had to remove and re-add homebridge after deleting the persist folder.  Everything came back up but I now have the one pesky "not supported" accessory, which I didn't have before.  So out of all the combinations of tweaks everyone has done, which one addresses that?  Seems like when one changes lots of variables at once it's hard to identify which did the trick.

@lucanaut the one accessory showing "not supported" has been addressed in latest homebridge update. Please update your homebridge.

thank you!

I had an accessory that said “not supported”. I changed the name of it and restarted. It worked fine after that.
Thanks,
Jacob Richards

On Sep 21, 2017, at 12:29 PM, Khaos Tian<EMAIL_ADDRESS>wrote:
@lucanaut the one accessory showing "not supported" has been addressed in latest homebridge update. Please update your homebridge.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Interesting.  I update homebridge, and now I see it but it says "no response" - and it won't let me move it from Default Room.  Or change its name for that matter.  It works as normal from the Wemo app.

@lucanaut can you try reboot your iOS devices?

That didn't seem to work.  I did notice however two things:

in the homebridge terminal window, I am seeing the wemo switch change state whenever I trigger it from the wemo app, so homebridge definitely seems to be picking up its state and every trigger
it still has the original name of the switch before I changed it (since one of my troubleshooting steps was to reset that switch)

@lucanaut Huh interesting, would you mind to repeat the process of remove homebridge from iOS device, wait a few minutes, close homebridge, remove persist folder, pair with homebridge again? Sorry for inconvenience.

I will give that another shot, thought that is what I did earlier.  To confirm, when I remove homebridge and then re-add it, I will need to reset all my automations, room locations etc, correct?  That seemed to be what I had to do earlier.

@lucanaut you don't need to manually reset anything, removal of the bridge will take care of that. Please be sure to wait a few minutes between removal and re-add the bridge. After re-add the bridge, you'll have to manually assign accessory location again.

Sorry, that's what I meant (and didn't say it properly), I will need to set up all my automations again and reassign all 24 accessories...I will try in a little while.  Thank you.

Don’t use more than one Apple TV and iPads as hub! Before I have 3 Apple TV 4s as hub and make my HomeKit not work properly! After i turn off 2 and and use only one and redo all setup now working good.

I only have one ATV...

Good news - I found a fix.
Instead of removing and adding homebridge again, I terminated it homebridge and deleted the cached accessories file in the accessories folder.  I also reset the wemo switch and re-added it to the wemo app.  Then I restarted homebridge which I guess forced it to create a new cachedaccessories file.  So I am guessing the Wemo reset wasn't necessary.  Either way...all good now!

I had a similar problem to @lucanaut, my philips motion sensor wasn't causing a homekit automation trigger to turn on some lights when it detected motion. I deleted and recreated the automation with the 3rd party home app, but it was still not triggering. Using Apple's home app to create the automation solved things for me.

Aaand I spoke to soon. That one accessory went back to not being supported :(

My experience with IOS 11 is as follows:
Upgraded phone and TV to latest OS releases.
Upgraded homebridge
Deleted persist directory and deleted homekit entries on the phone, re-added and all working.  Login in Apple TV - still working, go off network (away from home) all devices appear as not responding, return home to network - still not responding.
Turned homekit off on Apple TV and instead used an ipad as the home hub - all devices responding and working away from home.  So appears to be a TV OS fault.
The issue that remains (aside from Apple TV) is that homekit automations are not being triggered by a  device state change.  Time based automations work fine, but an automation triggered by a homebridge device state change consistently fails.
Can others who have working solutions confirm if a homekit automation triggered by a homebridge device status change is working or not?

I use homebridge with edomoticz on a Raspberry pi 1 model B. With Siri on my Iphone 6 everything was working very well. But after the IOS update to 11.0.1 it was all over.
First, indeed, a accessory was not supported. But also after a few minutes there was no connection, ie no response. After the deletion of the files in directory persist and accessories and a restart I could not get a connection between the Iphone and Homebridge. And that's still the situation. Also the status of Homebridge told me that an other accessory than before was not supported.
Homebridge is still working and gives no errors at all.
Here is the prove of a correct working Homebridge:
pi@raspberrypi:~ $  sudo systemctl status homebridge.service -l
● homebridge.service - HomeBridge Service
Loaded: loaded (/lib/systemd/system/homebridge.service; enabled)
Active: active (running) since Thu 2017-09-28 22:23:39 CEST; 1h 19min ago
Main PID: 602 (homebridge)
CGroup: /system.slice/homebridge.service
└─602 homebridge
Sep 28 22:58:59 raspberrypi homebridge[602]: [9/28/2017, 10:58:59 PM] [eDomoticz] Initializing platform accessory 'Slaapkamer'...
Sep 28 22:58:59 raspberrypi homebridge[602]: [9/28/2017, 10:58:59 PM] [eDomoticz] Initializing platform accessory 'Thermostaat'...
Sep 28 22:58:59 raspberrypi homebridge[602]: [9/28/2017, 10:58:59 PM] [eDomoticz] Initializing platform accessory 'Woonkamer'...
Sep 28 22:58:59 raspberrypi homebridge[602]: [9/28/2017, 10:58:59 PM] [eDomoticz] Initializing platform accessory 'Zijraam'...
Sep 28 22:58:59 raspberrypi homebridge[602]: Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
Sep 28 22:58:59 raspberrypi homebridge[602]: ┌────────────┐
Sep 28 22:58:59 raspberrypi homebridge[602]: │ 031-45-154 │
Sep 28 22:58:59 raspberrypi homebridge[602]: └────────────┘
Sep 28 22:59:00 raspberrypi homebridge[602]: [9/28/2017, 10:59:00 PM] Homebridge is running on port 51826.
Sep 28 22:59:01 raspberrypi homebridge[602]: [9/28/2017, 10:59:01 PM] [eDomoticz] Successfully connected to MQTT broker.
For me the problem is caused by our Apple friends.
I hope there will come a solution in the near future.
Best Regards,
Wallgarden

What’s the version of homebridge you have on your Raspberry Pi?
Sent from my iPhone

On Sep 28, 2017, at 3:02 PM, Jan Walhof<EMAIL_ADDRESS>wrote:
I use homebridge with edomoticz on a Raspberry pi 1 model B. With Siri on my Iphone 6 everything was working very well. But after the IOS update to 11.0.1 it was all over.
First, indeed, a accessory was not supported. But also after a few minutes there was no connection, ie no response. After the deletion of the files in directory persist and accessories and a restart I could not get a connection between the Iphone and Homebridge. And that's still the situation. Also the status of Homebridge told me that an other accessory than before was not supported.
Homebridge is still working and gives no errors at all.
Here is the prove of a correct working Homebridge:
pi@raspberrypi:~ $ sudo systemctl status homebridge.service -l
● homebridge.service - HomeBridge Service
Loaded: loaded (/lib/systemd/system/homebridge.service; enabled)
Active: active (running) since Thu 2017-09-28 22:23:39 CEST; 1h 19min ago
Main PID: 602 (homebridge)
CGroup: /system.slice/homebridge.service
└─602 homebridge
Sep 28 22:58:59 raspberrypi homebridge[602]: [9/28/2017, 10:58:59 PM] [eDomoticz] Initializing platform accessory 'Slaapkamer'...
Sep 28 22:58:59 raspberrypi homebridge[602]: [9/28/2017, 10:58:59 PM] [eDomoticz] Initializing platform accessory 'Thermostaat'...
Sep 28 22:58:59 raspberrypi homebridge[602]: [9/28/2017, 10:58:59 PM] [eDomoticz] Initializing platform accessory 'Woonkamer'...
Sep 28 22:58:59 raspberrypi homebridge[602]: [9/28/2017, 10:58:59 PM] [eDomoticz] Initializing platform accessory 'Zijraam'...
Sep 28 22:58:59 raspberrypi homebridge[602]: Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
Sep 28 22:58:59 raspberrypi homebridge[602]: ┌────────────┐
Sep 28 22:58:59 raspberrypi homebridge[602]: │ 031-45-154 │
Sep 28 22:58:59 raspberrypi homebridge[602]: └────────────┘
Sep 28 22:59:00 raspberrypi homebridge[602]: [9/28/2017, 10:59:00 PM] Homebridge is running on port 51826.
Sep 28 22:59:01 raspberrypi homebridge[602]: [9/28/2017, 10:59:01 PM] [eDomoticz] Successfully connected to MQTT broker.
For me the problem is caused by our Apple friends.
I hope there will come a solution in the near future.
Best Regards,
Wallgarden
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Thank you for your response.
These are the results of version check:
pi@raspberrypi:~ $ homebridge -V
0.4.20
pi@raspberrypi:~ $ npm version
{ npm: '5.0.3',
ares: '1.10.1-DEV',
http_parser: '2.7.0',
icu: '58.2',
modules: '48',
node: '6.11.0',
openssl: '1.0.2k',
uv: '1.11.0',
v8: '5.1.281.102',
zlib: '1.2.11' }
Kind Regards,
Wallgarden

@orgalinq Ah, the support for iOS 11 was added around v0.4.26, anything before that can possibly resulting HomeKit refuse to communicate with the accessory. Please try to upgrade to latest homebridge.

Thank you again for the quick response.
It’s here about 01:00 now. Tomorrow I will update Homebridge to a newer version. After that I will give you the results.
Kind regards,
Wallgarden
(IPhone bericht)

Op 29 sep. 2017 om 00:49 heeft Khaos Tian<EMAIL_ADDRESS>het volgende geschreven:
@orgalinq Ah, the support for iOS 11 was added around v0.4.26, anything before that can possibly resulting HomeKit refuse to communicate with the accessory. Please try to upgrade to latest homebridge.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

This morning my plan was to update Homebridge.
I did this:
sudo systemctl stop homebridge
sudo npm install -g homebridge
and then, at the end, I ran into multiple messages:
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/homebridge/node_modules/ed25519/.node-gyp/6.11.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/homebridge/node_modules/ed25519/.node-gyp"
Thus, a new try with:
pi@raspberrypi:~ $ npm install -g homebridge
npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules
npm ERR! path /usr/local/lib/node_modules
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access
npm ERR! Error: EACCES: permission denied, access '/usr/local/lib/node_modules'
npm ERR!     at Error (native)
npm ERR!  { Error: EACCES: permission denied, access '/usr/local/lib/node_modules'
npm ERR!     at Error (native)
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'access',
npm ERR!   path: '/usr/local/lib/node_modules' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2017-09-29T07_37_50_362Z-debug.log
Again with:
pi@raspberrypi:~ $ sudo npm install -g homebridge
/usr/local/bin/homebridge -> /usr/local/lib/node_modules/homebridge/bin/homebridge

<EMAIL_ADDRESS>updated 1 package in 47.361s

Succes? No!
This is the result:
pi@raspberrypi:~ $ sudo systemctl status homebridge.service –l
● homebridge.service - HomeBridge Service
Loaded: loaded (/lib/systemd/system/homebridge.service; enabled)
Active: failed (Result: exit-code) since Fri 2017-09-29 09:34:46 CEST; 10min ago
Process: 640 ExecStart=/usr/local/lib/node_modules/homebridge/bin/homebridge (code=exited, status=1/FAILURE)
Main PID: 640 (code=exited, status=1/FAILURE)
Sep 29 09:34:46 raspberrypi homebridge[640]: at Module.require (module.js:497:17)
Sep 29 09:34:46 raspberrypi homebridge[640]: at require (internal/module.js:20:19)
Sep 29 09:34:46 raspberrypi homebridge[640]: at Object. (/usr/local/lib/node_modules/homebridge/node_modules/mdns/lib/dns_sd.js:32:22)
Sep 29 09:34:46 raspberrypi homebridge[640]: at Module._compile (module.js:570:32)
Sep 29 09:34:46 raspberrypi homebridge[640]: at Object.Module._extensions..js (module.js:579:10)
Sep 29 09:34:46 raspberrypi homebridge[640]: at Module.load (module.js:487:32)
Sep 29 09:34:46 raspberrypi homebridge[640]: at tryModuleLoad (module.js:446:12)
Sep 29 09:34:46 raspberrypi homebridge[640]: at Function.Module._load (module.js:438:3)
Sep 29 09:34:46 raspberrypi systemd[1]: homebridge.service: main process exited, code=exited, status=1/FAILURE
Sep 29 09:34:46 raspberrypi systemd[1]: Unit homebridge.service entered failed state.
● \xe2\x80\x93l.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
pi@raspberrypi:~ $ sudo homebridge
module.js:471
throw err;
^
Error: Cannot find module '../build/Release/dns_sd_bindings'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/usr/local/lib/node_modules/homebridge/node_modules/mdns/lib/dns_sd.js:32:22)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
What went/is Wrong. Do you have a hint?
Kind Regards,
Wallgarden

@orgalinq it looks like the installation is only partially succeeded which causes some issues. Can you try sudo rm -rf /usr/local/lib/node_modules/homebridge and then sudo npm install -g homebridge see if it fix your issue?

Hi KhaosT,
This is the result. Multiple messages with:
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/homebridge/node_modules/ed25519/.node-gyp/6.11.0"
and
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/homebridge/node_modules/ed25519/.node-gyp"
The same as yesterday.
Kind Regards,
Wallgarden

This is what I see:
pi@raspberrypi:~ $ sudo systemctl status homebridge.service –l
● homebridge.service - HomeBridge Service
Loaded: loaded (/lib/systemd/system/homebridge.service; enabled)
Active: failed (Result: exit-code) since Fri 2017-09-29 16:26:02 CEST; 3h 58min ago
Process: 604 ExecStart=/usr/local/lib/node_modules/homebridge/bin/homebridge (code=exited, status=1/FAILURE)
Main PID: 604 (code=exited, status=1/FAILURE)
Sep 29 16:26:02 raspberrypi homebridge[604]: at Module.require (module.js:497:17)
Sep 29 16:26:02 raspberrypi homebridge[604]: at require (internal/module.js:20:19)
Sep 29 16:26:02 raspberrypi homebridge[604]: at Object. (/usr/local/lib/node_modules/homebridge/node_modules/mdns/lib/dns_sd.js:32:22)
Sep 29 16:26:02 raspberrypi homebridge[604]: at Module._compile (module.js:570:32)
Sep 29 16:26:02 raspberrypi homebridge[604]: at Object.Module._extensions..js (module.js:579:10)
Sep 29 16:26:02 raspberrypi homebridge[604]: at Module.load (module.js:487:32)
Sep 29 16:26:02 raspberrypi homebridge[604]: at tryModuleLoad (module.js:446:12)
Sep 29 16:26:02 raspberrypi homebridge[604]: at Function.Module._load (module.js:438:3)
Sep 29 16:26:02 raspberrypi systemd[1]: homebridge.service: main process exited, code=exited, status=1/FAILURE
Sep 29 16:26:02 raspberrypi systemd[1]: Unit homebridge.service entered failed state.
● \xe2\x80\x93l.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)

and this:
pi@raspberrypi:~ $ sudo homebridge
module.js:471
throw err;
^
Error: Cannot find module '../build/Release/dns_sd_bindings'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/usr/local/lib/node_modules/homebridge/node_modules/mdns/lib/dns_sd.js:32:22)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
Kind Regards,
Wallgarden

@orgalinq ah sorry it should be sudo npm install --unsafe-perm -g homebridge

Hi KhaosT,
Ok, a new try. This is what happens:
pi@raspberrypi:~ $ sudo npm install --unsafe-perm -g homebridge
/usr/local/bin/homebridge -> /usr/local/lib/node_modules/homebridge/bin/homebridge

<EMAIL_ADDRESS>install /usr/local/lib/node_modules/homebridge/node_modules/ed25519
node-gyp rebuild

make: Entering directory '/usr/local/lib/node_modules/homebridge/node_modules/ed25519/build'
CC(target) Release/obj.target/ed25519/src/ed25519/keypair.o
CC(target) Release/obj.target/ed25519/src/ed25519/sign.o
CC(target) Release/obj.target/ed25519/src/ed25519/open.o
CC(target) Release/obj.target/ed25519/src/ed25519/crypto_verify_32.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_double_scalarmult.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_frombytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_scalarmult_base.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_precomp_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p2_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p2_dbl.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_dbl.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_to_p2.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_to_cached.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_madd.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_add.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_msub.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_sub.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p1p1_to_p3.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p1p1_to_p2.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_1.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_cmov.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_copy.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_neg.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_add.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sub.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_mul.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sq.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sq2.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_invert.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_isnegative.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_isnonzero.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_frombytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_pow22523.o
CC(target) Release/obj.target/ed25519/src/ed25519/sc_reduce.o
CC(target) Release/obj.target/ed25519/src/ed25519/sc_muladd.o
CXX(target) Release/obj.target/ed25519/src/ed25519.o
SOLINK_MODULE(target) Release/obj.target/ed25519.node
COPY Release/ed25519.node
make: Leaving directory '/usr/local/lib/node_modules/homebridge/node_modules/ed25519/build'

<EMAIL_ADDRESS>install /usr/local/lib/node_modules/homebridge/node_modules/curve25519-n2
node-gyp rebuild

make: Entering directory '/usr/local/lib/node_modules/homebridge/node_modules/curve25519-n2/build'
CXX(target) Release/obj.target/curve/node_curve.o
SOLINK_MODULE(target) Release/obj.target/curve.node
COPY Release/curve.node
make: Leaving directory '/usr/local/lib/node_modules/homebridge/node_modules/curve25519-n2/build'

<EMAIL_ADDRESS>install /usr/local/lib/node_modules/homebridge/node_modules/mdns
node-gyp rebuild

make: Entering directory '/usr/local/lib/node_modules/homebridge/node_modules/mdns/build'
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_sd.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_browse.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_enumerate_domains.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_get_addr_info.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_process_result.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_ref.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_ref_deallocate.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_ref_sock_fd.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_register.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_resolve.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_update_record.o
CXX(target) Release/obj.target/dns_sd_bindings/src/mdns_utils.o
CXX(target) Release/obj.target/dns_sd_bindings/src/network_interface.o
CXX(target) Release/obj.target/dns_sd_bindings/src/socket_watcher.o
CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_ref.o
CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_create.o
CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_deallocate.o
CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_set_value.o
CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_get_length.o
CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_buffer_to_object.o
SOLINK_MODULE(target) Release/obj.target/dns_sd_bindings.node
COPY Release/dns_sd_bindings.node
make: Leaving directory '/usr/local/lib/node_modules/homebridge/node_modules/mdns/build'

<EMAIL_ADDRESS>added 30 packages in 836.591s

and this is the result. The same as before.
pi@raspberrypi:~ $ sudo systemctl status homebridge.service –l
● homebridge.service - HomeBridge Service
Loaded: loaded (/lib/systemd/system/homebridge.service; enabled)
Active: failed (Result: exit-code) since Fri 2017-09-29 16:26:02 CEST; 4h 33min ago
Process: 604 ExecStart=/usr/local/lib/node_modules/homebridge/bin/homebridge (code=exited, status=1/FAILURE)
Main PID: 604 (code=exited, status=1/FAILURE)
Sep 29 16:26:02 raspberrypi homebridge[604]: at Module.require (module.js:497:17)
Sep 29 16:26:02 raspberrypi homebridge[604]: at require (internal/module.js:20:19)
Sep 29 16:26:02 raspberrypi homebridge[604]: at Object. (/usr/local/lib/node_modules/homebridge/node_modules/mdns/lib/dns_sd.js:32:22)
Sep 29 16:26:02 raspberrypi homebridge[604]: at Module._compile (module.js:570:32)
Sep 29 16:26:02 raspberrypi homebridge[604]: at Object.Module._extensions..js (module.js:579:10)
Sep 29 16:26:02 raspberrypi homebridge[604]: at Module.load (module.js:487:32)
Sep 29 16:26:02 raspberrypi homebridge[604]: at tryModuleLoad (module.js:446:12)
Sep 29 16:26:02 raspberrypi homebridge[604]: at Function.Module._load (module.js:438:3)
Sep 29 16:26:02 raspberrypi systemd[1]: homebridge.service: main process exited, code=exited, status=1/FAILURE
Sep 29 16:26:02 raspberrypi systemd[1]: Unit homebridge.service entered failed state.
● \xe2\x80\x93l.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
after a reboot:
pi@raspberrypi:~ $ sudo systemctl status homebridge.service –l
● homebridge.service - HomeBridge Service
Loaded: loaded (/lib/systemd/system/homebridge.service; enabled)
Active: failed (Result: exit-code) since Fri 2017-09-29 21:01:21 CEST; 43s ag                                                                                o
Process: 640 ExecStart=/usr/local/lib/node_modules/homebridge/bin/homebridge (                                                                                code=exited, status=203/EXEC)
Main PID: 640 (code=exited, status=203/EXEC)
Sep 29 21:01:20 raspberrypi systemd[1]: Starting HomeBridge Service...
Sep 29 21:01:20 raspberrypi systemd[1]: Started HomeBridge Service.
Sep 29 21:01:21 raspberrypi systemd[1]: homebridge.service: main process exi...C
Sep 29 21:01:21 raspberrypi systemd[1]: Unit homebridge.service entered fail....
● \xe2\x80\x93l.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
Hint: Some lines were ellipsized, use -l to show in full.
Kind Regards,
Wallgarden

@orgalinq Did you do sudo rm -rf /usr/lib/node_modules/homebridge/ before the install? Sometime npm get confused if there are leftovers... Sorry for the inconvenience.

This message:  ExecStart=/usr/local/lib/node_modules/homebridge/bin/homebridge (code=exited, status=203/EXEC)
When I look into that homebridge file, it is empty!
That's not good I think.....

@KhaosT @orgalinq As this is no longer about HomeKit working on ios11, I'd like to ask that you take this to another thread as to stop spamming everyone with off-topic support requests.

I'm sorry, but this is about ios11. After the update of ios my good working Homebridge was killed! An update did'nt work.
Sorry that you see this as spam.
Kind Regards,
Wallgarden

@orgalinq let's move to https://github.com/nfarina/homebridge/issues/1521 to discuss the installation problem and update this issue if updating to latest version fixed your issue.
@humanthrope I apologize for spamming everyone 😅

iOS 11 update fix that worked for me...
If you have a lot of stuff in your home, you might want to try this last.

Shutdown homebridge and kill the home app.
Change the user name and pin in the config.json file.
Restart the home app and see if it works. If so, STOP and be happy.
<<<(The next step requires you to re-do all room assignments, zones, and automations!)>>>
Delete the Homebridge from the app. (Details, remove). Kill the app and restart it.
Add the homebridge using the new pin.
For me, it immediately asked me to setup all my devices assigning them back to the rooms.

If that doesn't work, see @jeroen1973 post from Aug 20/13 days ago. His post was the basis for this.

I was able to fix it with @jack-hub answer plus removing persist and accessories folders from ~/.homebridge

Problem solved: https://github.com/B1tMaster/haas-config/issues/54
This is the best way to solve it as it is pretty much guaranteed to work, since you would be installing the homebridge plugin via Docker and your environment, libraries , settings etc will be same regardless of what OS you run.

Folks, in the end I managed to get everything working again. No need to run homebridge in Docker or to install Hass.io. What you need to do is a cleanup of your PI.
I basically removed all the packages (nodejs, npm, node-server, nodered, hap-nodejs, homebridge) and installed everything from scratch following the installing procedures at:

https://github.com/KhaosT/HAP-NodeJS
https://github.com/nfarina/homebridge
Special thanks to the support from @KhaosT and @nfarina while I was trying to troubleshoot their code (in the end their code was just fine :-)).

Before I have a lot problem when I have more then one Apple TV as hub! Now I use only one never have problem again! Just some time when Apple is having problem in the iCloud my gets users can use outside home.

I am pretty sure there is a major problem with Homebridge and Motion Sensors in Homekit. I have set up an ESP8266 based motion sensor that is interfacing with the Homebridge-MotionSensor plugin using HTTP. Everything seems to be working fine with Homebridge but Homekit isn't updating the status of the motion sensor at all. The only way to get Homekit updated is to manually force an update with the Home app. As a result, actions that rely on the motion sensor don't work.

Is this the issue you are seeing?
https://github.com/KhaosT/HAP-NodeJS/issues/418 https://github.com/KhaosT/HAP-NodeJS/issues/418

On Nov 5, 2017, at 8:58 PM, rodhall<EMAIL_ADDRESS>wrote:
I am pretty sure there is a major problem with Homebridge and Motion Sensors in Homekit. I have set up an ESP8266 based motion sensor that is interfacing with the Homebridge-MotionSensor plugin using HTTP. Everything seems to be working fine with Homebridge but Homekit isn't updating the status of the motion sensor at all. The only way to get Homekit updated is to manually force an update with the Home app. As a result, actions that rely on the motion sensor don't work.
—
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-342026825, or mute the thread https://github.com/notifications/unsubscribe-auth/AS5CmEbWfO1xoq3SzE8lUW5ce3n-MRF-ks5szme7gaJpZM4OmkSq.

Hello All, I had this same issue and I solved it today. homebridge was found but all accesoires where 'Not Responding'
I thought it was because of an IOS 11 update first but after completely removing / reinstalling my PI3 with homebridge the issue was still there. I googled a lot and in my case my router (Netgear Orbi) had this multicast feature set to disabled:
Disable IGMP Proxying. IGMP proxying allows a computer on the local area network (LAN) to receive the multicast traffic it is interested in from the Internet.
After enabling this multicast feature and rebooting the router it was completely running fine again!
It's unknown to me why this setting was disabled but now it is working like a charm again :-)
Keep up the good work nfarina! I love homebridge!

@NorthernMan54 I am not sure. I don't get any Motion state detection at all unless I force an app to poll the motion state. That thread you sent sounds like a problem with propagation outside of Wifi. If I could figure out how to implement that fork in Homebridge I would try it just the same though as I do see some Unregister events occurring in Debug mode.

@rodhall One thing to keep in mind, is that creating a motion sensor plugin is quite complex, especially if it is using a remote sensor.  As the sensor needs create an event that gets passed to the plugin, and on to HomeKit.  And most of the plugins don't support this type of behaviour, they simply poll the device for status.  What plugin are you using for the sensor?

they simply poll the device for status

The issue is that most plugins only read the device and update the HomeKit characteristic, when a HomeKit app reads the characteristic.  To update the characteristic spontaneously, the plugin must poll the device regularly, caching the state to detect changes, and update the HomeKit characteristic when the device state had changed.  This is what my homebridge-hue plugin does.
As this introcudes a delay due to polling, it would be better to listen for real-time notifications sent by the device.  It really depends on the device whether and how they support this.  E.g. the Hue bridge doesn’t support this, so it needs to be polled.  The deCONZ gateway sends notifications over a websocket; homebridge-hue listens to this websocket.  Sonos speakers send HTTP notify messages to registered web servers.  My homebridge-zp plugin creates a web server and registers this which each Sonos speaker.

Short Update,
Like i said in previous post siri is working with all accessories. When i am using the home app shows the no response issue on all devices but here comes the real interesting part: When i close the home app and only use the control center home integration then it all works fine. No issues with not responding. I can use the switch button and it all works fine. When i open the home app again then inside the home app and the control center integration it does not work anymore. Again killing the home app and only use the control center shortcuts then it works!.
Its all so strange ;-()

I suspect Not responding is an issue with the app losing connection to the accessory (i.c. homebridge), not necessarily with the accessory.  I’ve had Apple’s Home reporting Not responding while Eve on the same device would get a response.

Now I have problem with HAP-nodejs which doesn't work in iOS 11.2 too. How I use home bridge combined with HAP-nodejs?

Not sure if it's appropriate for this thread but I just got out of "Could not attach device" hell. My problem was that I was trying to add my homebridge setup via my wifi only iPad. It's beginning to look to me like only a cellular device like an iPhone can connect to a homebridge setup because it needs to clear you through the "This is an unapproved device" dialog.
-- csh

Can you provide more details on your setup? With Homebridge, only a single
phone or ipad is allowed to connect at a given time, however, the number of
devices are expandable with an Apple TV or IPad running as a hub.
Also make sure the Ipad is not in Hub mode, I'm not sure if one could run a
hub and a remote device as one. Something you need to explore.
The other thing to note is, deleting the persist files flowed by a reboot
could help with the iPad connectivity.
On Wed, Mar 14, 2018 at 10:03 AM Christopher Hilton <
<EMAIL_ADDRESS>wrote:

Not sure if it's appropriate for this thread but I just got out of "Could
not attach device" hell. My problem was that I was trying to add my
homebridge setup via my wifi only iPad. It's beginning to look to me like
only a cellular device like an iPhone can connect to a homebridge setup
because it needs to clear you through the "This is an unapproved device"
dialog.
-- csh
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nfarina/homebridge/issues/1414#issuecomment-372879811,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIw6wLu-L9FMJ8CT5V7YvD9ON7KDRBAqks5teHpjgaJpZM4OmkSq
.

--
Sent from Iphone Mobile


@conda-forge-admin, please add user @rockdoc-mo

[ ] I read the conda-forge documentation and could not find the solution for my problem there.

Issue:

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @rockdoc-mo in conda-forge/metoffice-afterburner-feedstock#5.


Compute TDR at low FAR

Dear authors,
Thank you very much for providing the code. I found your research very interesting. I would like to compute and hopefully reproduce the results of Table 3 in your paper. Precisely, how can I compute the "true detection rate (TDR) at a low false alarm rate (FAR) of 0.5%"? If you could provide any code would be really appreciated.
I really appreciate any help you can provide.

Hi,
Thank you for your interest in our work. I'm really sorry for not replying to you earlier. Currently, I'm in the process of finding this particular evaluation code. I'll get back to you with the code. If I'm not able to find the code, I'll write a new code and revert back to you. In the meantime, you can get some information at https://anssi-fr.github.io/SecuML/miscellaneous.detection_perf.html . I'll try to get back to you asap. Thank you!

Hi, below is the code for TDR at low FAR:
import numpy as np
import matplotlib
matplotlib.use('Agg')
import matplotlib.pyplot as plt
import os
from sklearn.metrics import roc_curve, auc
from menpo.visualize.viewmatplotlib import sample_colours_from_colourmap
from prettytable import PrettyTable
from pathlib import Path
import warnings
warnings.filterwarnings("ignore")
import csv
def write_result(result_files, save_path, dataset_name, label):
methods = []
scores = []
for file in result_files:
    methods.append(Path(file).parent.stem)
    scores.append(np.load(file))

methods = np.array(methods)
scores = dict(zip(methods, scores))
colours = dict(
    zip(methods, sample_colours_from_colourmap(methods.shape[0], 'Set2')))
#x_labels = [1/(10**x) for x in np.linspace(6, 0, 6)]
x_labels = [10**-6, 10**-5, 10**-4, 10**-3, 10**-2, 10**-1]
tpr_fpr_table = PrettyTable(['Methods'] + [str(x) for x in x_labels])
print(tpr_fpr_table)
fig = plt.figure()
for method in methods:
    fpr, tpr, _ = roc_curve(label, scores[method])
    roc_auc = auc(fpr, tpr)
    fpr = np.flipud(fpr)
    tpr = np.flipud(tpr)  # select largest tpr at same fpr
    plt.plot(fpr,
            tpr,
            color=colours[method],
            lw=1,
            label=('[%s (AUC = %0.4f %%)]' %
                    (method.split('-')[-1], roc_auc * 100)))
    tpr_fpr_row = []
    tpr_fpr_row.append("%s-%s" % (method, dataset_name))
    for fpr_iter in np.arange(len(x_labels)):
        _, min_index = min(
            list(zip(abs(fpr - x_labels[fpr_iter]), range(len(fpr)))))
        #tpr_fpr_row.append('%.4f' % tpr[min_index])
        tpr_fpr_row.append('%.2f' % (tpr[min_index] * 100))
    tpr_fpr_table.add_row(tpr_fpr_row)
plt.xlim([10**-6, 0.1])
plt.ylim([0.3, 1.0])
plt.grid(linestyle='--', linewidth=1)
plt.xticks(x_labels)
plt.yticks(np.linspace(0.3, 1.0, 8, endpoint=True))
plt.xscale('log')
plt.xlabel('False Positive Rate')
plt.ylabel('True Positive Rate')
plt.title('ROC on IJB')
plt.legend(loc="lower right")
#plt.show()
fig.savefig(os.path.join(save_path, 'verification_auc.pdf'))
print(tpr_fpr_table)

# write to csv
result = [tuple(filter(None, map(str.strip, splitline))) for line in str(tpr_fpr_table).splitlines()
                                                         for splitline in [line.split("|")] if len(splitline) > 1]
with open(os.path.join(save_path, 'verification_result.csv'), 'w') as outcsv:
    writer = csv.writer(outcsv)
    writer.writerows(result)

if name == 'main':
label = y_true[0:400]
scores = y_pred[0:400]
np.save("scores.npy", scores)
score_save_file = "./scores.npy"
result_files = [score_save_file]
save_path = './'
dataset_name = 'x'

write_result(result_files, save_path, dataset_name, label)

Hi @vishal3477! Thanks a lot for your quick response; I really appreciate your help. I will check the code and let you know if I have any further questions.


the description of delete/update access config command is incorrect

BUG REPORT

Please describe the issue you observed:
修改管理命令deleteAccessConfig、deleteAccessConfig对应参数：'-b'、'-c'的描述，包含：
1、acl拼写错误：acl写成了cl
2、语法错误：删除时用了：delete...to...

What did you do (The steps to reproduce)?
1、acl拼写错误：cl--->acl
2、delete...to...修改为delete...from...

#2882


3d configurations

Codecov Report
Attention: Patch coverage is 0% with 12 lines in your changes are missing coverage. Please review.

Project coverage is 6%. Comparing base (c5384d5) to head (8f498fb).

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #795     +/-   ##
=======================================
- Coverage      77%     6%    -71%
  Complexity     78     78
=======================================
  Files          87     87
  Lines        3807   3819     +12
  Branches      378    379      +1
=======================================
- Hits         2919    194   -2725
- Misses        690   3606   +2916
+ Partials      198     19    -179

Files
Coverage Δ

...lormap/api/configuration/dev/PopulateTestData.java
0% <ø> (-91%)
:arrow_down:

...ormap/api/persistence/helper/GeoServiceHelper.java
1% <0%> (-76%)
:arrow_down:

... and 78 files with indirect coverage changes


v4.3.7 - Error creating component calendarpicker - Firefox refresh with F5

Hi Olton,
I hope you are well.
Testing a new program I found an issue I can reproduce only with Firefox (77.0.1 (64 bits))
On a page that use calendarpicker component if I reload the page with javascript or by hitting F5 the calendar picker fail to load.
"Error creating component calendarpicker"
"TypeError: aDays[nDay] is undefined"
Works well on others browsers

<input name="date" type="text" id="date"  value="" size="12" maxlength="10" style="height: 35px; font-size: 0.9em;" data-role="calendarpicker" data-locale="fr-FR" data-header-format="%A %e %B" data-format="%d/%m/%Y"/>
If I remove the data-format it works.

https://github.com/olton/Metro-UI-CSS/issues/1506

Thanks, adding autocomplete="false" fix the problem for me.
Great and quick support, thanks again.


Integration into Blazorise?

Hi @aladotnet, I found out about your library from another person's recommendation and I find it really good.
I'm a creator of Blazorise component library, and I think your work would fit into Blazorise. I propose that you become a collaborator on Blazorise and then make Blazorise.FluentValidation is a part of Blazorise extensions. That way, you would be part of a larger community, and your work can reach more people. Our team could also improve the library even further. Not to mention that it will always be on time with the latest version releases.
I would like you to consider it. Please let me know what you think.
PS. Not sure what would happen with the NuGet packages. You have published it with a Blazorise.* prefix, and it is usually reserved for Blazorises official releases. We're also in the process of making it an official reservation.

Hi,
this repository has been created out of a personal need, i appreciate your feedback and i am also open for merging it into the Blazorise extensions and to be as a contributor a part from the community.
due to the Naming, i had no intense of  violating any of your Branding Rights, it just fits in the context of what the Package is implemented for.
so let me know what are the Next steps.

I'm really glad that you have agreed to make it part of Blazorise. I guess the next step would be for you to create a PR on the Blazorise repository. We could do it for you, but it's better that it comes with your name as that way, we could mention you in our release notes as a contributor.
Once the PR is created, we will review it and modify it to be stable enough for production. Hopefully, it will be enough time to make it for v1.1, but we will see.
The project name would be named Blazorise.FluentValidation, and placed under the Source/Extension along the other similar components.
Regarding the existing NuGet package. I'm afraid it would need to be unlisted. Hopefully, it will not cause any problems when we try to publish a new version.

Hi @aladotnet, I have started with Blazorise integration and I have a question.
In the sample project, you're validating two times.

But from what I can see while testing doing the await fluentValidations.ValidateAll() is enough. So PersonValidator.ValidateAsync is not needed. Can you tell me what are the reasons to have it?

https://github.com/Megabit/Blazorise/pull/4068

Hi, sorry that i did not reply that fast, i was very busy the last days, i ll take a look at it tomorrow, if it is ok for you.

Yes your right, there is no reason for calling ValidateAll, i think i just forgot to delete it.

Yes your right, there is no reason for calling ValidateAll, i think i just forgot to delete it.

Great, thank you.

@stsrki  should i take some action or have you already did it all?

I think the actual PR is ready to be merged. I just need a final review from David.
The only thing left would be the NuGet feed. TBH, I don't know if publishing the same-named NuGet package is possible. Blazorise v1.1 is scheduled for Sept 15th, so we will need to figure it out by then.

That sounds great.


problem with jdart

when I test test_foo.jpf in " C:\Users\asus\jdart\src\examples\features\simple" test work right ,but when I add a method call myMethod and I test it with test_myMethod.jpf nothing happen, I also try to make an other class java in the other  repository "C:\Users\asus\jdart\src\examples\features\test" called Testm.java the problem is :
[SEVERE] cannot load application class features.test.Testm
I tried everything without finding any solution [.](url

)
this is my site.properties

jpf-core=C:/Users/asus/git/jpf-core
jpf-jdart=C:/Users/asus/jdart
extensions=${jpf-core},${jpf-symbc}

this is test_myMethod.jpf
@include=./example.jpf
concolic.method=myMethod
this is example.jpf  :
@include=../../config/jdart.jpf
target=features.test.Testm
concolic.method.myMethod=features.test.Testm.myMethod(i:int)
concolic.method.myMethod.config=all_fields_symbolic
this using.jpf  :
@using = jpf-jdart
target=features.test.Testm
method config jdart
concolic.method.myMethod=features.test.Test.myMethod(i:int)
concolic.method=myMethod
jpf config
jvm.insn_factory.class=gov.nasa.jpf.jdart.ConcolicInstructionFactory
peer_packages=gov.nasa.jpf.jdart.peers;
listener=gov.nasa.jpf.jdart.ConcolicListener
perturb.class=gov.nasa.jpf.jdart.ConcolicPerturbator
search.multiple_errors=true
jdart.concolic_explorer_instance=gov.nasa.jpf.jdart.ConcolicExplorer@jdart-explorer
jdart config
symbolic.dp=z3
symbolic.dp.z3.bitvectors=true
logging
log.finest=jdart
log.info=constraints

I get a solution , I must run the command "ant" always before testing to get any modification .

Can you rephrase what the problem is? The error you were initially seeing ("cannot load application class"), is because your target class features.test.Testm is not on the classpath for jpf. Where is that class located?

the problem that when i forget the command "ant" nothing happen because the command "ant" build the project . if you make any modification in the class or in the method you must run the command "ant" and then  /path/to/jpf-core/bin/jpf /path/to/jdart/src/examples/features/simple/test_foo.jpf  for example .

Yes, you need to recompile your system under test if you make any changes to it.

I am working in a project  "automatic annotation for JDart" , I want to know which variables should treat as symbolic  , can someone give me a detailed answer in which situation must the variable treat symbolically

I am working on a project "automatic annotation for JDart" , I want to know
which variables should treat as symbolic , can someone give me a detailed
answer in which situation must the variable treat symbolically
2017-03-12 12:53 GMT+01:00 Kasper Luckow<EMAIL_ADDRESS>
Closed #19 https://github.com/psycopaths/jdart/issues/19.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/psycopaths/jdart/issues/19#event-996303593, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AT-870qsSOCwxwsVzPiXD80CPWxZitY_ks5rk9zFgaJpZM4MZS62
.

can someone help me please ?

I believe I already answered your question in issue #6 : It is up to the user to define which inputs to the program should be treated symbolically.


[Snyk] Upgrade xxhash-wasm from 1.0.1 to 1.0.2

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade xxhash-wasm from 1.0.1 to 1.0.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released a month ago, on 2022-11-02.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Cross-site Request Forgery (CSRF) SNYK-JS-FASTIFY-3136527
496/1000  Why? Recently disclosed, Has a fix available, CVSS 4.2
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: xxhash-wasm

1.0.2 - 2022-11-02
Add support for Typescript's nodenext module resolution (#33)

1.0.1 - 2022-01-19
Export data types separately + fixed bigint data type (#28)

    from xxhash-wasm GitHub release notes

Commit messages

Package name: xxhash-wasm

dbe852d v1.0.2
e785a5e Upgrade yarn to 3.2.4
cb68153 Update Node versions of actions
18c2295 Reword the v1.0.0 release message in the Readme
aad322e Re-run yarn install to fix cache (`.yarn/install-state.gz`)
1986f5c Merge dependabot updates
2900b62 Bump minimist from 1.2.5 to 1.2.7 (#35)
7551801 Upgrade dependencies
95a68f0 Add support for Typescript's `nodenext` module resolution (#33)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@nazarhussain can you please turn off snyk PRs or else configure them to also update yarn.lock?

Also opening PRs with @nazarhussain personal access token is bad optics. Would prefer to be opened with a user related to the bot

@wemeetagain @dapplion The automatic PRs are disabled for Snyk. There were few fix PRs I was creating manually from its UI to tests some configurations.


Is it possible to use linstor-gateway to provide NFS exports?

We are looking to find a solution to #69, we're wondering if it's possible to create a deployment of https://github.com/LINBIT/linstor-gateway which will expose NFS exports.
There doesn't appear to be much documentation on how the gateway is working with NFS, and if it provides any advantages over using a https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner deployment (we have an issue with using this deployment as when the NFS pod is rescheduled NFS exports hang on the same node).
The main use-case for using NFS over linstor is to provide load balancing as well as HA.

It's complicated.
The issue with linstor-gateway in this context is that it is basically a whole different project, which is mainly aimed at running directly on the host. So we would need to wrap it in a container (might be difficult, it strongly depends on systemd), we would need to wrap it with some CSI driver logic. If at all possible I'd like to avoid all that.
I think it would be much better to find out what exactly does not work with the nfs-ganesha project.

@WanzenBug Thanks for considering, I agree that it would be better to find a solution to the nfs-ganesha bug.
I have opened an issue @ https://github.com/nfs-ganesha/nfs-ganesha/issues/825, however at the moment we've hit a brick wall.
If we can create a minimal reproducible scenario, would you be able to independently test it? In order to rule out any issue with our own setup.

Please share the reprocuder if you can, but I can't promise when I'll find the time to verify it.
I had a look through the linked ticket. I'm not really familiar with all the details of the NFS protocol, but:

Have you tried mounting after the fail-over from a completely new node? That way you could verify that the NFS server is starting as expected.
This is something we observed in linstor-gateway, which uses the in-kernel NFS server, so no guarantee this translates to nfs-ganesha: NFS is not a stateless protocol, so in order for the server to fail over it needs also save the connection states. In linstor-gateway this is why there is second volume for NFS exports which I believe is mounted on /var/lib/nfs. I believe the symptoms you are experiencing matches what we saw when that state information is missing. No idea how this is handled in nfs-ganesha though.

Unfortunately I've not had time to work on the reproducer, we're instead creating a controller to force delete the NFS pods and any pods mounting them upon node failure.

Yes, a new pod is able to mount via the rescheduled NFS pod, only pods with the old NFS mount fail to reconnect.
We're using this as the provisioner https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner which stores the configuration in /export which is a piraeus replicated volume, so the state should be persisted.

We have narrowed this down to an issue with cilium when using the kube-proxy-replacement. It works as expected without kube-proxy-replacement. https://github.com/cilium/cilium/issues/21541
I will close this as updates will be in the above issue.


enable startup-test

Here is the pull request to enable the test.

Thanks!

According to our C4.1 process, I promoted you to be a collaborator in this project. This means that you are allowed to merge pull requests from others. Just do not merge your own pull requests or commit to master directly. Welcome on board!

Hi Constantin,
thank you for the promotion. However, I probably won’t have time to contribute substantially to this project.
Kai

Am 18.02.2016 um 03:44 schrieb Constantin Rack<EMAIL_ADDRESS>According to our C4.1 process, I promoted you to be a collaborator in this project. This means that you are allowed to merge pull requests from others. Just do not merge your own pull requests or commit to master directly. Welcome on board!
—
Reply to this email directly or view it on GitHub.


Re-enable faulty data tests

Issue #1179
(Removed tests where the exception the test was expecting did not exist anymore)

Looks good, thanks @dcolligan. I think we need to look a bit at how the code is being called in the production code path, and make sure that we're calling into the same hooks that are being used there.

@jeromekelleher rebased

+1.

Thanks @dcolligan +1!


Show native TensorBoard prompt when user launches TensorBoard from integrated terminal

For https://github.com/microsoft/vscode-python/issues/15007, https://github.com/microsoft/vscode-jupyter/issues/313

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[ ] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).
[ ] The wiki is updated with any design decisions/details.

Codecov Report

Merging #15008 (fa87f41) into main (48d66bd) will increase coverage by 0%.
The diff coverage is 100%.

@@          Coverage Diff           @@
##            main   #15008   +/-   ##
======================================
  Coverage     65%      65%
======================================
  Files        558      559    +1
  Lines      26221    26267   +46
  Branches    3729     3730    +1
======================================
+ Hits       17150    17191   +41
- Misses      8377     8380    +3
- Partials     694      696    +2

Impacted Files
Coverage Δ

src/client/tensorBoard/tensorBoardImportTracker.ts
93% <100%> (+4%)
:arrow_up:

src/client/tensorBoard/tensorBoardPrompt.ts
97% <100%> (ø)

src/client/tensorBoard/helpers.ts
76% <0%> (-6%)
:arrow_down:

src/client/ioc/container.ts
56% <0%> (-4%)
:arrow_down:

src/client/telemetry/index.ts
76% <0%> (-2%)
:arrow_down:

src/client/ioc/serviceManager.ts
39% <0%> (-1%)
:arrow_down:

src/client/ioc/types.ts
100% <0%> (ø)

src/client/telemetry/types.ts
100% <0%> (ø)

src/client/telemetry/importTracker.ts
31% <0%> (ø)

src/client/telemetry/envFileTelemetry.ts
94% <0%> (ø)

... and 1 more


Should not require access_token when not enabled

Currently rollbax refuses to start if an access_token and environment is not given even if it is not actually enabled. This is inconvenient if we want to add rollbax only in the production environment. It is possibly to specify an invalid token and get around this issue, but it feels like that shouldn't be necessary.

I might agree that access_token shouldn't be required when enabled is set to false, but it feels consistent and more friendly to newcomers: they will get an error at early stage, not after production build is ready. I'm afraid that they will run recompilation to apply configuration changes since not everyone at the beginning knows about sys.config file.


confinement: add ConfinedIo

Codecov Report
Base: 76.8% // Head: 76.8% // No change to project coverage :thumbsup:

Coverage data is based on head (d03de14) compared to base (b026752).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@          Coverage Diff           @@
##           master    #215   +/-   ##
======================================
  Coverage    76.8%   76.8%
======================================
  Files           9       9
  Lines         852     852
======================================
  Hits          654     654
  Misses        198     198

Impacted Files
Coverage Δ

src/io_util.rs
0.0% <ø> (ø)

src/lib.rs
85.7% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


COPY TO(remote): External error: Execution error: Cannot execute remote scan with a remote reference

GlareDB (v0.7.0)
Connected to Cloud deployment (TLS enabled): grey
Type \help for help.
> COPY (SELECT * FROM ...) TO './output.csv';
Error: External error: External error: External error: Execution error: Cannot execute remote scan with a remote reference

@greyscaled, this is marked as a regression. What's the last good commit/tag you tried this on? 0.7.0?

@greyscaled, this is marked as a regression. What's the last good commit/tag you tried this on? 0.7.0?

@scsmithr stated in Slack it's a regression. I tried this on 0.7.0 install, yep!

Should be resolved with #2183

We can close this issue.


Add an easy way to use external integrations

Add support for external integrations such as MixPanel
https://segment.com/docs/libraries/ios/#migrating-from-v1-or-v2
https://github.com/segmentio/analytics-ios/wiki/Packaged-Integrations

Hey @talkain ,
Thanks for this library! I am wondering if you have any suggestions on how to use external integrations.
I found https://segment.com/docs/libraries/ios/#bundling-integrations , but it's a bit unclear to me how to use it in combination with this library. Any pointers/tips would be highly appreciated!


fix for experiment schedular not working due to cyclic services depenency and findby() old syntax

This PR resolves #2135

@VivekFitkariwala Please check this: https://www.npmjs.com/package/typeorm


headphones-toolbox: init at 0.0.3

Description of changes

This PR adds the headphones-toolbox package, which is a UI for configuring Ploopy Headphones made with Tauri. Note that this doesn't add the required udev rules which must exist to make it work: https://github.com/george-norton/headphones-toolbox#quickstart-guide
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I fully tested it with my Ploopy headphones and it works great, I tested filters and firmware updates, both of them worked.

Please squash the last three commits, thanks!

Please squash the last three commits, thanks!

Fixed.


After the CRON expression is selected, the style is not consistent with the UI

CRON 表达式选择后，样式与UI不一致
实际结果：

预期结果：

#164 repair edit alert rule select cron style inconsistency