Open normen opened 6 years ago
I have the same mistake. I can't solve this problem
Same problem, I guess the problem would be solved if the Apple TV was found, please add a retry function to the Apple TV discovery.
When the AppleTV isn't found during startup HomeKit will remove the associated devices which results in broken scenes and other issues.
The plugin could hold the homebridge startup when AppleTV isn't found or it could simply add the switches for HomeKit anyway and continue to try and connect in the background (this probably ties in with #18) I solved this problem by adding an apple tv to the manual. It works great!
I solved this problem by adding an apple tv to the manual. It works great!
Can you explain this a bit more? What do you mean exactly by "adding an apple tv to the manual"?
I solved this problem by adding an apple tv to the manual. It works great!
Can you explain this a bit more? What do you mean exactly by "adding an apple tv to the manual"?
for manual pairing, use the following: https: / / github.com / edc1591/node-appletv when you get there credentials just paste it into config.js "platforms": [ { "platform": "AppleTV", "name": "Apple TV", "devices": [ { "id": "lounge", "name": "Room", "credentials": ".............." } ], "accessories": [ { "deviceID": "lounge", "name": "Up", "command": "up" } ], "showPairSwitches": false } ] when credentials are received node-appletv can be deleted, it is no longer needed npm r -g node-appletv
Okay, but thats a solution for a different problem :)
This is about when the AppleTV is already paired.
Any solution found on this?
When the AppleTV isn't found during startup HomeKit will remove the associated devices which results in broken scenes and other issues.
The plugin could hold the homebridge startup when AppleTV isn't found or it could simply add the switches for HomeKit anyway and continue to try and connect in the background (this probably ties in with #18)