Maximilian Leith
Maximilian Leith
Yep, you have to start at 1. That should be the solution. For reference: https://github.com/homebridge/HAP-NodeJS/issues/644
> once I changed to ActiveIdentifiers 1...4, the get and set become consistent, and correspond to input1...4. So the configured names are now shown reliably in the setup process or...
> Interesting topic. I do (optionally) expose TV accessories from my Homebridge ZP plugin, to select Sonos favourites as TV inputs. I don't think I currently expose _Configured Name_ on...
> So I checked with my test home, without a home hub. Both main service name and input sources show correctly, as defined through the Display Name values provided by...
> I don't think this is related, but Homebridge v2.0.0-beta.21 is bitching about an invalid character (+) in Configured Name of one of the inputs. In my opinion this is...
> Depending on how much work you want to put into a workaround to an Apple bug, you might heuristically detect that the names are changed during pairing, and ignore...
> @Kazbah still waiting for homebridge 2.0 to be released. If you're not on a beta branch, the latest release should continue to work, it's OK to disregard any potential...
It is already homebridge 2.0 compliant
Yes, because the plugin dev has not specifically marked the plugin as compatible. But that does not mean it is not compatible. Two different things. Release notes show that it...
> your end users I want to make clear that I am not the plugin developer.