Fix for inputs disappearing & device just saying "on" without an input.

[iSteve-O]

Describe The Bug:
a lot of times when I open the home app I have to kill it in order for it to display the proper input and allow switching. It will also cause scenes & automations to not work on occasion. it also shows all the inputs as individual devices in the scene & automation builders as well as in the shortcuts app home device picker.

I thought there was a fix for this known issue because all of my "TV" devices used to do this, but now only this one does. Maybe you can look at the code for Yamaha-zone, or braviaTVos or Homebridge-broadlink-rm-pro, as none of them seem to have this issue in the home app. otherwise it's working great.

To Reproduce:
maybe reboot homebridge and then check the app, but I'm not sure that's necessary and maybe just wait.

Expected behavior:
Active input of the device displays properly.

Logs:

No info in the log.

Plugin Config:

        {
            "ip": "192.000.0.00",
            "name": "Yamaha",
            "enablePureDirectSwitch": false,
            "volumeAccessoryEnabled": false,
            "zone2Enabled": false,
            "zone3Enabled": false,
            "zone4Enabled": false,
            "_bridge": {
                "username": "00:00:00:00:00:00",
                "port": 00000
            },
            "platform": "yamaha-avr"
        },

Screenshots:
You can see here that in only happens with inputs for "Yamaha" in the living room but neither my "Bravia" (through BraviaTVos) nor my "Cable Box" or "Yamaha IR" (through Broadlink-rm-pro) have this issue. I know for sure the Bravia plugin used to do this same thing & doesn't anymore).

Environment:

• Plugin Version: Latest
• Homebridge Version: Latest
• Node.js Version: Latest
• NPM Version: Latest
• Operating System: Raspbian / hb-service

Thanks!

[iSteve-O]

I feel like this may or may not be related to the above but whenever I create a scene, automation or shortcut that sets the input of the receiver it always sets the wrong input after a while.

Hopefully you can resolve this issue because without scenes, automations & shortcuts why have it, right?

I'm not 100% sure but I think it may be related to the way the inputs are refreshed. Could be the fix for both these issues.

[ACDR]

it always sets the wrong input after a while.

As in the correct input is switched to via shortcut etc, then it switches back?

[iSteve-O]

it always sets the wrong input after a while.

As in the correct input is switched to via shortcut etc, then it switches back?

For some reason it’s like the scenes forget which input to set after a while (maybe related to Homebridge reboots or input renaming, I don’t know why). I’ll make a scene to set the input to HDMI 1 and it’ll work a few times and then all of a sudden I try to set that scene and for some unknown reason it sets input to HDMI 3 instead.

Sorry to say I’ve removed this plug-in and went to “Yamaha receiver” and it’s been working really well for me. I prefer you as a person though LOL you’re very nice.

[ACDR]

So many Yamaha plugins these days 😅

---

I can't replicate your issue with the input automations & shortcuts, even after what feels like hundreds of Homebridge reboots. I use shortcuts regularly for switching between inputs and have never had an issue.

The only thing I can think of that could cause this is if your receiver is somehow returning the inputs in a different order between reboots - causing the identifier of the automation input to de-sync with the input identifier of the accessory...

No guarantee that's what is happening, but I'll add numeric identifiers for each input to the cache. That should ensure consistency even if the order changes..

..or was this only happening when you hadn't restarted the Home app following a Homebridge restart?
(i.e. when the inputs are showing as "on" devices)

---

Pretty perplexed on this input as "on" device issue. Played around with a lot of different ways of creating these input services and it always does the same thing when Homebridge is rebooted whilst the Home app is open.

I recall it's been a long-standing issue with the Home app & TV accessories (with lots of comments floating around different plugins - mostly ending with "restart the home app"), but will do some more digging...

[iSteve-O]

I think what is happening is my xfinity x1 box is doing its nightly reboot and the input disappears from the receiver for a few minutes because of auto-input naming & crappy CEC from the box. Every time the box resets it plays hell with the inputs causing random switches and causing “logical” inputs to disappear from my LG tv. I don’t know why but this other “hb Yamaha receiver” plug-in seems to handle it better, as I have not had any of these issues while using it. I don’t think I had these issues while using “hb Yamaha-zone” either but that was so long ago I forget.

It is annoying how many plug-ins there are LOL not just for Yamaha. Often I just try them all out and then settle on the one that works best for me. I love it when they’re verified, but that doesn’t always mean stable or working either.

I’m sorry to cause you a pain in the rear.