You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have switched to ios17. Homekit is stable so far, but I no longer have a remote control in the Control Center.
Under ios16 everything ran fine and now everything is grayed out and nothing is found. Do I have to configure my Television Node differently so that I have access to the Television Service child service again?
Any more details?
No response
Any code or functions to add?
No response
The text was updated successfully, but these errors were encountered:
Hi,
The first thing to check is that your TV Host Type is an Accessory as there seem to be bugs with non-basic services if they are in Bridge mode (since iOS17).
Then should the node be linked or parent, TV is the parent and others are linked.
yes - TV Host is Accessory
yes - TV is parent
yes - all other are in linked mode
I set up a completely new Node Red installation for testing and only installed the Node node-red-contrib-homekit-bridged.
Node Red = v3.1.0
Node.js = v18.17.1
I took the code from the wiki: https://nrchkb.github.io/wiki/service/television/#node-red-code
I pasted it into Node Red.
I can open Apple TV Test in Homekit, on the iphone.
Everything works as expected. I just no longer see the remote control. Is this a new bug or is something wrong with my configuration?
Your Current NRCHKB Plugin Version
1.5.0
Operating System
Raspberry Pi Bullseye
How can we help?
Hello node-red-contrib-homekit-bridged Team,
I have switched to ios17. Homekit is stable so far, but I no longer have a remote control in the Control Center.
Under ios16 everything ran fine and now everything is grayed out and nothing is found. Do I have to configure my Television Node differently so that I have access to the Television Service child service again?
Any more details?
No response
Any code or functions to add?
No response
The text was updated successfully, but these errors were encountered: