com.swttt.homekit icon indicating copy to clipboard operation
com.swttt.homekit copied to clipboard

Randomly Devices are Added to Homeykit

Open BBEHannes opened this issue 7 years ago • 16 comments

I have been seeing this lately where in Settings, devices that i specifically unchecked from showing up in Homekit are added again after a while. This is ok as long as there is no restart of Homey or the App since these changes are not enforced until restart but afterwards it costs a lot of time (since i have a lot of devices) to get them set properly again.

BBEHannes avatar Jun 30 '18 09:06 BBEHannes

Strange, I have about 25 devices in total that Homeykit can manage, and I've never had an issue with devices suddenly changing their "exposed" status.

It's especially strange that the device state as shown on the settings page doesn't reflect the actual status of the device (because, like you say, the device is being shown as exposed, but until a reboot/restart it isn't treated as such).

For now, I don't have a clue how this might happen.

Do you use the Homey desktop app, or a browser? If so, it might be worthwhile to open the developer tools to check if there are any errors happening when you change the state of a device. Perhaps the frontend is having issues syncing the device status with the backend, for some reason.

robertklep avatar Jun 30 '18 11:06 robertklep

I agree with everything Robert :). I use the homey desktop App. Haven't played around with the developer tools yet as of now. It is very inconsistent behavior and does not occur all the time. is there anything i can do to help you provide logs at times of the behavior? if so, please let me know

BBEHannes avatar Jun 30 '18 12:06 BBEHannes

Too bad the behaviour is seemingly random, that means the devtools are of limited use I think.

Have you tried changing the state of a device on the settings page when it has reverted back to being exposed (while it shouldn't)?

An additional complication is that the device state, whether it should be shown or not, is not handled by the Homey app directly but by the underlying hap-nodejs module.

@nhassink @swttt have you ever had to deal with this problem?

robertklep avatar Jun 30 '18 12:06 robertklep

It MIGHT change when adding new devices to Homey. I am thinking about the conditions and I believe that it happens when I have added new physical devices. Cannot confirm it yet though.

Indeed, what I do when this occurs is set the state back to what it is supposed to be.

BBEHannes avatar Jun 30 '18 13:06 BBEHannes

If you add a new physical device to homey it will automatically appear in HomeKit / home app. Might this be the behavior you’re experiencing?

nhassink avatar Jun 30 '18 16:06 nhassink

Thanks hassink. It is the exact behavior I mentioned in my initial comment and verified by Robert. All devices show as “DELETE” under their name. This is wrong info as most of them should not be added to HomeKit view. And they are not, until you restart the app or homey.

BBEHannes avatar Jun 30 '18 18:06 BBEHannes

I might have found a possible reason why this happens, but only if there's something wrong with some core Homey code.

However, I'll try and cut a beta release tomorrow or on monday to see if that solves your problem.

robertklep avatar Jun 30 '18 19:06 robertklep

Rockstar! Looking forward seeing the results

BBEHannes avatar Jun 30 '18 20:06 BBEHannes

Friendly reminder on this.

BBEHannes avatar Jul 09 '18 17:07 BBEHannes

@swttt can you publish a new beta? Should be v2.1.2

robertklep avatar Jul 09 '18 17:07 robertklep

This is still somewhat of an issue. When restarting homey without first shutting down HomeyKit app, some of my devices are lost and I need to re-add them to homeykit after restart.

BBEHannes avatar Dec 22 '18 09:12 BBEHannes

This should be fixed in an upcoming release (probably v3.0.7)

robertklep avatar Feb 07 '19 11:02 robertklep

Don't see this happening in v3.07 anymore, @BBEHannes pls check this beta. ;)

FrankRinkens avatar Feb 26 '19 11:02 FrankRinkens

Still running 3.06 but it happens there (intermittently, not 100% of the time) still.

BBEHannes avatar Feb 26 '19 12:02 BBEHannes

@BBEHannes it was (hopefully) fixed in 3.0.7, not 3.0.6.

robertklep avatar Feb 26 '19 12:02 robertklep

Updated to the beta... will keep you posted.

BBEHannes avatar Feb 26 '19 12:02 BBEHannes