It seems like zones in 2022.9 now have a unit_of_measurement of “People home” for the zone state showing how many people are in the zone. Besides being the wrong name for the unit (since most zones aren’t “home”), this makes history graphs showing zone occupancy into line graphs, instead of the shaded bars they were prior to 2022.9.
The graph is not nearly as easy to read as it was before; it used to have a bar for each location with a differently-shaded section for how many people were in each location. Plus, a line graph has fractions. You can’t have 1.5 people in a location!
Same applies when looking at the history of a single location. Here’s a graph for a location that is not home:
Can we please have this fixed (i.e. remove the unit_of_measurement) and have the state just be a bare value again?
A workaround would be if I could force a history graph card to ignore the unit_of_measurement, but that would only work in the dashboard; individual zone entities would still show the bogus “People home” unit and fractional values.
I know what the answer will likely be since I doubt they will remove the UOM - “build a template sensor for the zone without the UOM”. That’s the answer to most of these types of things.
But the “People Home” for zones that aren’t “Home” thing really needs to get fixed.
Having to work around it by essentially duplicating the sensors is annoying. The UOM’s forcing the history graph into a line chart is a huge regression in usability.
Besides the nonexistent fractional values, it is a lot harder to see the start-end times for occupancy. That is, with the bar graph I could hover anywhere over a shaded spot and see a tooltip that shows when the zone state went to a certain value and when it stopped having that value. So it was easy to see how long somebody was at a certain location. Now I have to hover over the exact spot on the right line to find the start time, then go to a different spot to find the end time. And since the lines overlap it is even harder to find the zone I want.
