Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Loosing accessories with iOS 16.7 and powerloss #235

Open
PimV5755 opened this issue Oct 3, 2023 · 12 comments
Open

Loosing accessories with iOS 16.7 and powerloss #235

PimV5755 opened this issue Oct 3, 2023 · 12 comments

Comments

@PimV5755
Copy link

PimV5755 commented Oct 3, 2023

I have problems since 16.7. After a powerdown of an accessory the homeapp looses it. It gives "no Reaction".
It appears out of the HomeKit database because if I look for new accessories my old one is there and I can re-pair it.
After the re-pair it shows up agaian but there is still the "old" one. You need to remove that.
Very strange and very frustrative.

I am puzzled. I have more then 20 accessories based on this library.
@thncode
Copy link

thncode commented Oct 5, 2023

are you sure that all your accessories are defined correctly? I had to learn that the hard way, using 20 accessories with very different type and settings intermediatly lost connection because of wrong values, missing getter definitions and so on...
Now I have all defined according the HAP paper and everything is stable...

@PimV5755
Copy link
Author

PimV5755 commented Oct 7, 2023 via email

@thncode
Copy link

thncode commented Oct 8, 2023

I know - but this is not permanent. I assume it is really the best to hunt that source of the problem down...

@PimV5755
Copy link
Author

PimV5755 commented Oct 12, 2023 via email

@thncode
Copy link

thncode commented Oct 12, 2023 •
edited

yes - that seems to be true. It's a pity that this is not documented. I am trying to find out by try&error. Currently I have 20 accessories & bridges in use and just one still makes troubles...
And it is not only getters. Careful watching types and limits is also important. Whenever some value gets out of range homekit neglects to update characteristics. This is IMHO also the reason why sometimes an accessory "lives again"...

@PimV5755
Copy link
Author

PimV5755 commented Oct 15, 2023 via email

@thncode
Copy link

thncode commented Oct 16, 2023

the last trouble making accessory is now behaving as well. I think this is really a question of correct api / getter definitions...

@PimV5755
Copy link
Author

PimV5755 commented Oct 16, 2023 via email

@thncode
Copy link

thncode commented Oct 16, 2023

Telegram?
Yes, I do make my own hardware...

@PimV5755
Copy link
Author

PimV5755 commented Oct 16, 2023 via email

@thncode

This comment was marked as outdated.

Sign in to view
@jockethebastard
Copy link

are you sure that all your accessories are defined correctly? I had to learn that the hard way, using 20 accessories with very different type and settings intermediatly lost connection because of wrong values, missing getter definitions and so on... Now I have all defined according the HAP paper and everything is stable...

Please elaborate on how to define them correctly, I’m having this issue with only one of two accessories, and I can’t get it working more than a couple of hours.

Thanks in advance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@thncode @PimV5755 @jockethebastard