-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Input source naming convention on V2 of homebridge #735
Comments
Can you share a log example of the issue? The 15 minute time interval sounds like the homebridge instance discovery timer within the plugin |
Thank you for your response. I set up test environment and ran the plugin with v2.0.0-beta.23 of homebridge. Please see the logs below. Note that I disabled network interface codes of the plugin to avoid conflicts with my daily using homebridge instances. I also edited the code to log accessory refreshing of 15 minutes intervals. 'HAP-NodeJS WARNING' looks to be syncing with the interval.
|
Tks, let me dig into this |
This is definitely tied to the plugins internal refresh interval, as it is refreshing the device information every 15 minutes. We are looking at removing this message from HB 2.0. Stay tuned |
Current Situation
Hi @NorthernMan54
Sorry for bothering you, but I have a question.
I'm using input source naming convention of this plugin (i.e., 'Station -') to identify channel or external source of inputs for television accessory since it introduced. This is really useful to select input orally. I also implemented this convention for homebridge-gsh to share the plugin configuration.
However, in my experience, V2 of homebridge complains this convention to remove for future compatibility issue, not only starting time but also periodically of 15 minutes intervals. This is very annoying but unfortunately unavoidable as long as using this feature.
Proposed Change
To be honest, I don't have a solution. Moreover, I don't know my understandings of homebridge and this plugin features are correct. So, firstly, I'd like to confirm that this is really a issue or not, and want to know a way to avoid this dilemma.
If this is really a issue, user configurable prefix (e.g. 'Station' is OK for almost cases) can be a choice from my limited knowledge.
Additional Context
No response
The text was updated successfully, but these errors were encountered: