Loosing accessories with iOS 16.7 and powerloss

[PimV5755]

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.

[Thomas Nemec]

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]

I agree with you about missing getters and such. However , it appears that HomeKit is also self-healing. The problems I had yesterday with pairing were gone this morning and I didn’t change anything… Op do 5 okt. 2023 om 19:56 schreef Thomas Nemec ***@***.***>

…

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... — Reply to this email directly, view it on GitHub <#235 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUKZ5LQZMKNFQTOMYB7KVD3X53YGVAVCNFSM6AAAAAA5Q66VQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBZGM4TENZYGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Thomas Nemec]

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

[PimV5755]

Can all accessories have getters? It appears that some won’t. Op zo 8 okt. 2023 om 14:56 schreef Thomas Nemec ***@***.***>

…

I know - but this is not permanent. I assume it is really the best to hunt that source of the problem down... — Reply to this email directly, view it on GitHub <#235 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUKZ5LX4T7I75HZEBF6KDC3X6KPJRAVCNFSM6AAAAAA5Q66VQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSGAZDCOBTG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Thomas Nemec]

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]

They are also sensitive to WiFi signal. I have a TP- Link Omada netwerk that is living it’s own life. I also have around 20. I build a few specials to control my Denon, BlueSound streamer and Ajax Security. It is a shame that apple does not let you make a loudspeaker or TV. At least the home app is not supporting them. Op do 12 okt. 2023 om 21:47 schreef Thomas Nemec ***@***.***>

…

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... — Reply to this email directly, view it on GitHub <#235 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUKZ5LW25MMHB5BI7KRWVJ3X7BCO5ANCNFSM6AAAAAA5Q66VQ4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Thomas Nemec]

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

[PimV5755]

Good to hear. I sometimes think dat de HomeKit database is selfhealing. I would like to stay in touch with you. Share experiences. Is iMessage an option? ***@***.*** Are you on LinkedIn? I make my own hardware. You too? Op ma 16 okt. 2023 om 07:38 schreef Thomas Nemec ***@***.***>

…

the last trouble making accessory is now behaving as well. I think this is really a question of correct api / getter definitions... — Reply to this email directly, view it on GitHub <#235 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUKZ5LQHOSIFFWLB6W7N2EDX7TB65ANCNFSM6AAAAAA5Q66VQ4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Thomas Nemec]

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

[PimV5755]

Nice. WhatsApp is possible. I don’t do telegram. Op ma 16 okt. 2023 om 13:59 schreef Thomas Nemec ***@***.***>

…

Telegram? Yes, I do make my own hardware... — Reply to this email directly, view it on GitHub <#235 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUKZ5LX3ATLKT5YHJITKIIDX7UORZAVCNFSM6AAAAAA5Q66VQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRUGMYTIOBVHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Thomas Nemec]

Or we simply use mail 😀
You can reach me at
[e-mail]
Cheers
Thomas

[jockethebastard]

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