-
Notifications
You must be signed in to change notification settings - Fork 29
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
Shows _UNKNOWN_APP When using HDMI Source #113
Comments
Is your device actually on HDMI 1? The source should only show as an app when the current source is |
if you are willing to run pyvizio locally you can test what source input pyvizio is seeing. If it is indeed |
It is indeed on HDMI-1, specifically and Apple TV plugged into that input. |
I will give this a shot and see if I can debug further. |
Ok, here is the output of two commands from pyvizio when input is set to HDMI-1 and therefore no app is currently running, the first is from get-current-input:
This seems to accurately indicate that HDMI-1 is the current input selected. When I run get-current-app, here is the result:
This looks like an appropriate error because no app is running. My assumption is that HASS is not using this result properly and showing _UNKNOWN_APP, which while kind of true, isn't the optimal user experience. |
thanks this is really helpful. Vizio has been making a bunch of changes to their API recently, and since this package has been built around reverse engineering, it has been a cat and mouse game. I may need some more info but this is really helpful for now, I will keep this open and reach out if I have any other questions |
Happy to assist, let me know if you need anything else. |
When playing via an HDMI input the UI shows _UNKNOWN_APP instead of the HDMI input name or some other more useful display.
The text was updated successfully, but these errors were encountered: