-
Notifications
You must be signed in to change notification settings - Fork 233
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.
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
I can't pair it with homekit #408
Comments
It says "after restart". What restart? You're not supposed to reboot accessory right after pairing. |
after restart `WiFI ready HomeKit: Starting server |
but no accessory is displayed in the home. When trying to pair again, the accessory was not found because it appears to be paired |
Because of my poor English, my question may have confused you, sorry. When I try to pair I get a |
Disconnection after pair setup is a normal procedure. Controller then reconnects, goes through pair verification and then downloads accessory definition and shows what kind of services accessory provides on the UI. From your log I can't tell what happens after pair setup. |
if I got it right , Kristian says that accessory paired in logs, but never in home iOS app. |
this is all available information and according to it the device seems to be paired but in fact the device is not displayed in the home application due to the shown on photo error |
I noticed that the size of led.bin is 681 kb I think this may be a problem? |
This issue could be triggered by values out of boundaries or improper characteristics defined. I have never received this message. 🤔 |
just following the example i haven't changed anything |
I forgot to specify that I use led example ESP8266_RTOS_SDK |
What causes this error? |
This is out of memory error. |
I get this error also, right after setting up the wifi. Solution seems to be to hard reset the board and try again. It looks the wifi config procedure eats some memory which isn’t freed? |
@peros550 I do not know what is exactly in your case, but wifi_config can cause memory fragmentation (because you run homekit server when wifi_config hasn't fully stopped yet), so it goes like ( <wifi_config> <homekit_server> ), then wifi_config stops and you get ( <homekit_server> ), so memory is fragmented and there might not be enough memory chunks. |
Thanks Maxim. No worries it's not a big issue on my case since a reboot clears the problem. |
@peros550 Yes, you can. Basically, it's the stack size you allocate for your task + some fixed overhead ( + everything your task allocates while running ). |
@Kristian8606 In the past I have seen this problem when not using the newest git submodules. Try to update all submodules, rebuild everything, erase the flash and flash again (maybe some of these steps are not necessary, but it worked for me).
|
I also have the this problem,In debugging,When I find something wrong, the log is:
When there is no problem, the log is:
It seems to have some problem with validation |
@choosegit could you please recompile firmware with HomeKit debug logs enabled and reupload logs |
|
I do have a similar problem, everything work very well and I can pair with Homekit, the problem come if I lose power> 0:30:05.969 -> >>> [ 74] HomeKit: Using existing accessory ID: 66:41:E3:25:57:20 I never get the accessory to work again. the accessories do not response again on Homekit I have to reset, connect to my wifi again delete the accessory from Homekit and re-pair |
worked for me. void remove_all_pairings() { void setup() { void loop() { |
I try to pair the device but always to no avail
after restart
`WiFI ready
The text was updated successfully, but these errors were encountered: