-
EDIT NOTE: This is not the answer to solving this - the issue persisted. I am tracking two binary sensors, a fan and a motion sensor for a pet toileting area.
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
Noted another person having issues with fixedrange and noted they had additional range values in the mix. This prompted me to give the range directive a try with upper and lower values of on and off in top down order on the graph. These values need to be in the correct order in order to display as expected.
|
Beta Was this translation helpful? Give feedback.
-
No, I’m starting to ignore it because it’s frustrated me. Not the best way to help point out an ongoing issue - but that’s where I’m at with it.On 13 May 2025, at 7:16 pm, Tom Matheussen ***@***.***> wrote:
Does this solution still work for you? I can't to get this to work, it just takes over the first values it sees from the entities
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Try with this: layout:
yaxis:
categoryorder: array
categoryarray: ['off', 'on']
|
Beta Was this translation helpful? Give feedback.
Noted another person having issues with fixedrange and noted they had additional range values in the mix. This prompted me to give the range directive a try with upper and lower values of on and off in top down order on the graph.
These values need to be in the correct order in order to display as expected.