Gauge card not showing "green", "yellow" or "red" field data in visual editor and is inconsistent with data in code editor.

[chrisuk-web]

trafficstars

Checklist

• [X] I have updated to the latest available Home Assistant version.
• [X] I have cleared the cache of my browser.
• [X] I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

Coded a card as follows:

Code editor has "green" starting at 1 rather than 0 (and graph between 0 and 1 % is blue)

If I save and then go back into an edit, the visual editor does not display field data for "green", "yellow" or "red":

The code editor is unchanged.

Describe the behavior you expected

As above

Steps to reproduce the issue

As above

What version of Home Assistant Core has the issue?

core-2022.5.0b7

What was the last working version of Home Assistant Core?

Unknown. Same issue exists in core-2022.4.7

In which browser are you experiencing the issue with?

Version 100.0.4896.127 (Official Build) (64-bit)

Which operating system are you using to run this browser?

Windows 10.0.19044 Build 19044

State of relevant entities

state_class: measurement
unit_of_measurement: '%'
icon: mdi:cpu-64-bit
friendly_name: Processor use

Problem-relevant frontend configuration

type: gauge
entity: sensor.processor_use_percent
needle: true
severity:
  green: 1
  yellow: 45
  red: 85
min: 0
max: 100
unit: '%'

Javascript errors shown in your browser console/inspector

No response

Additional information

If I code different values, e.g. 10, 20, 30 instead of 1, 45, 85, there is no inconsistency when looking at this data in the code editor, but the fields are still blank if data is saved and then a re-edit is done using the visual editor.

I can manually change green: 1 to green: 0 in the code editor and save that value with no issues.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[yavinmaster]

This issue still persists on 2022.9.1.

[thomaszlow]

This issue still persists in 2022.10.4!