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 am not very sure this is Apple HomeKit related or this plugin related, but when setting a scene for which I specified a specific input for my box (a game), that game won’t start after the console goes on, as configured in the scene itself.
I suspect this is not HomeKit related as I succeed in doing the same with other appliances as TVs and such: the input I select in the scene is honored when the scene takes place.
I gave a look at the logs and I actually can’t see any specific command for input selection after the power on command. Yet, I clearly get input selection logs after the Xbox is on and I manually select any game input in the accessory’s list, aka the input selection correctly works.
Am I overlooking something?
Environment:
homebridge-xbox-tv v3.2.2
HB v1.8.5
UI V4.64.0
Ubuntu Server 22.04.5 LTS VM
Node.js v22.12.0
Various Xboxes Series X 10.0.26100.2910
The text was updated successfully, but these errors were encountered:
I am not very sure this is Apple HomeKit related or this plugin related, but when setting a scene for which I specified a specific input for my box (a game), that game won’t start after the console goes on, as configured in the scene itself.
I suspect this is not HomeKit related as I succeed in doing the same with other appliances as TVs and such: the input I select in the scene is honored when the scene takes place.
I gave a look at the logs and I actually can’t see any specific command for input selection after the power on command. Yet, I clearly get input selection logs after the Xbox is on and I manually select any game input in the accessory’s list, aka the input selection correctly works.
Am I overlooking something?
Environment:
homebridge-xbox-tv v3.2.2
HB v1.8.5
UI V4.64.0
Ubuntu Server 22.04.5 LTS VM
Node.js v22.12.0
Various Xboxes Series X 10.0.26100.2910
The text was updated successfully, but these errors were encountered: