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
{{ message }}
Repository navigation
Bug: alternative dpi results in wrong resolution, incomplete display namingΒ #199
Describe the bug
Display sensors showing incorrect resolution. I have 3 monitors 1920x1080 and a 4k TV (3840x2160) attached to my PC. I'm using both the GPU and onboard graphics for one of the monitors. The sensors are showing 3 displays at 1920x1080 and 1 display at 1280x720.
The names are all DISPLAY# so I'm not sure which one is which. I'm wondering what method is used to get the display info and if it's possible to get the display name
Expected behavior
Ideally show proper resolution per display
Having the display name show up in attributes would be helpful
Screenshots
Misc info (please complete the following information):
I switched the display scale from 300% to 100% which now shows DISPLAY3 with the correct resolution. Curious why the scaling was making it think it was 720p as the content played on the TV still looked 4K with the scaling. So I suppose now this is more of a feature request for proper display names
changed the title [-]Bug: Incorrect display information[/-][+]Bug: alternative dpi results in wrong resolution, incomplete display naming[/+]on Oct 27, 2022
Activity
ITensEI commentedon Oct 26, 2022
I switched the display scale from 300% to 100% which now shows DISPLAY3 with the correct resolution. Curious why the scaling was making it think it was 720p as the content played on the TV still looked 4K with the scaling. So I suppose now this is more of a feature request for proper display names
LAB02-Admin commentedon Oct 27, 2022
That's very interesting, I'll look into it, thanks: [hassagent-165]
[-]Bug: Incorrect display information[/-][+]Bug: alternative dpi results in wrong resolution, incomplete display naming[/+]LAB02-Admin commentedon Nov 9, 2022
Should be fixed in the latest beta if you want to test:
https://github.com/LAB02-Research/HASS.Agent/releases/tag/2022.14.0-beta1
LAB02-Admin commentedon Nov 12, 2022
Fix in latest release: https://github.com/LAB02-Research/HASS.Agent/releases/tag/2022.14.0