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.

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

No longer works correctly with iOS 17 #450

Open
Tombra1889 opened this issue Oct 4, 2023 · 15 comments
Open

No longer works correctly with iOS 17 #450

Tombra1889 opened this issue Oct 4, 2023 · 15 comments

Comments

@Tombra1889
Copy link

Many functions no longer work. Among other things, detailed controls are no longer displayed for individual devices.
IMG_0276
image
image

@Markus-3
Copy link

Markus-3 commented Oct 5, 2023

I can confirm the problem. It's been exactly the same for me as described here since the iPhone Update iOS 17.0.3

@Alex0176
Copy link

Alex0176 commented Oct 6, 2023

exacly the same here ...

@crusader85
Copy link

switches also not working anymore

@unstressable
Copy link

switches also not working anymore

for me, switches work perfectly.
Also my heating thermostats.

I didn't upgrade to the new homekit architecture.
Maybe thats your problem?

@treblada
Copy link

I too lost the whole operability. I tried to remove my home in HomeKit and reinstall it, but it does not work, Yahka as a bridge was not visible.
I renamed the MAC-like user in Yahka and then I could see a bridge, I could tap it and enter the PIN, and HomeKit showed the waiting animation. Then the procedure aborted, with the note that the device were unreachable.
I have iOS 17.1 and Yahka 1.0.3.

@unstressable
Copy link

unstressable commented Oct 31, 2023

I too lost the whole operability. I tried to remove my home in HomeKit and reinstall it, but it does not work, Yahka as a bridge was not visible. I renamed the MAC-like user in Yahka and then I could see a bridge, I could tap it and enter the PIN, and HomeKit showed the waiting animation. Then the procedure aborted, with the note that the device were unreachable. I have iOS 17.1 and Yahka 1.0.3.

There‘s a profile from apple to completely reset Homekit.
Explanation and profile is available at apple forum.

or here:
https://www.reddit.com/r/HomeKit/comments/yy2oy7/apple_has_a_downloadable_profile_to_really_clear/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

@treblada
Copy link

There‘s a profile from apple to completely reset Homekit. Explanation and profile is available at apple forum.

Thank you. I have already found it and it does not work for me. I can "reset" my home configuration, and indeed, afterwards iOS presents the option to upgrade it again, so I assume it worked so far. But I still cannot add the same bridge in HomeKit which I used for over a year.
Oh, an additional change: I recently updated ioBroker from 7.0.1 to 9.0.1. But the logs are free of errors.

@unstressable
Copy link

Shouldn’t be a problem since I got the latest version also.
Try to change the „MAC“ and Password in YAHKA bridge.

there‘s nothing more I could recommend.

@spoeh-man
Copy link

Same her Cameras Working Switches not working all has no answer

@pymiras
Copy link

pymiras commented Jan 5, 2024

Same here. Yahka does no longer work. Reset Apple Home as mentioned above. When adding a new home I get an error "Gerät kann nicht hinzugefügt werden. Gerät ist nicht kompatibel." Tried AVAHI and CIAO advertiser. No Yahka errors in log.
Yahka: 1.0.3, ioBroker: 6.10.4, iOS: 17.1.2, node: v18.17.1, js-controller: 5.0.16

@Markus-3
Copy link

Markus-3 commented Jan 5, 2024 via email

@treblada
Copy link

treblada commented Jan 7, 2024

Changing the MAC does not do anything for me. After entering the pin (which has a different format in iOS than in yahka, xxxx-xxxx vs. xxx-xx-xxx) there is a long waiting period and then an error.
I have monitored the connections on yahka's side: there are no incoming connections using IPv4 to port 8083. However, there are connection attempts using IPv6 to the configured yahka port. I do not even know if yahka listens to IPv6 and on which address (the interface has three: public, site and local). So that might also be a possible reason why yahka stopped working.

Could someone please describe, how yakha works on the network level, i.e. what does it advertise via avahi and to which protocol/addresses does it listen?

@unstressable
Copy link

I think its the mdns protocoll.

the Format of the Pin doesnt matter. You habe to enter it without „-„ (minus)

@treblada
Copy link

treblada commented Jan 7, 2024

@unstressable Of course avahi uses MDNS :) but what information does it advertise? Only IPv4 address or "any"?

@unstressable
Copy link

I dont know, but it seems to be IPv4 only:
IMG_3214

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants