Skip to content
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

Wrong Columns height on first y-axis when a second y-axis is defined #669

Closed
4 tasks done
man010 opened this issue Feb 23, 2024 · 4 comments
Closed
4 tasks done

Wrong Columns height on first y-axis when a second y-axis is defined #669

man010 opened this issue Feb 23, 2024 · 4 comments
Labels
bug Something isn't working Stale

Comments

@man010
Copy link

man010 commented Feb 23, 2024

Checklist

  • I updated the card to the latest version available
  • I cleared the cache of my browser
  • I verified that I'm really running the lastest version in my browser console
  • I checked if there is another issue opened with the same problem

Describe the bug
I have defined 6 stacked series on a first y-axis. As I wanted to display an additional information in the header (not in the chart), I have added a second y-axis with the follow series config :
- entity: sensor.conso_electrique_totale
type: line
yaxis_id: second
name: CUMUL JOUR
color: red
group_by:
func: diff
duration: 1d
start_with_last: true
fill: last
show:
in_header: true
in_chart: false

and with this extra series, the height of some of the series on the first axis is wrong. As you see, the series « Buanderie » should have a value of 0.8kWh, while the column value seems to be around 0.2kWh

Here is the code of the y-axis and series (note the the second series is for the workaround of the other bug I reported yesterday, to get the y-axis automatically scaled with all the stacked values and not only the biggest one) :
yaxis:
- id: first
min: 0
max: auto
decimals: 1
apex_config:
tickAmount: 5
- id: second
min: 0
max: auto
show: false
decimals: 1
apex_config:
tickAmount: 5
series:
- entity: sensor.conso_electrique_totale
type: line
yaxis_id: second
name: CUMUL JOUR
color: red
group_by:
func: diff
duration: 1d
start_with_last: true
fill: last
show:
in_header: true
in_chart: false
- entity: sensor.conso_electrique_totale
yaxis_id: first
name: CUMUL JOUR
color: yellow
show:
in_header: false
in_chart: false
- entity: sensor.conso_electrique_buanderie
yaxis_id: first
name: BUANDERIE
color: green
- entity: sensor.prise_congelateur_energy
yaxis_id: first
name: CONGÉLATEUR
color: dodgerblue
- entity: sensor.conso_electrique_multimedia
yaxis_id: first
name: MULTIMÉDIA
color: lime
- entity: sensor.chauffage_sdb_energy
yaxis_id: first
name: CHAUFF. SDB
color: tomato
- entity: sensor.pac_alixan_tank_accumulated_consumption
yaxis_id: first
name: EAU CHAUDE
color: pink
- entity: sensor.pac_alixan_heating_accumulated_consumption
yaxis_id: first
name: CHAUFF. PAC
color: grey

Version of the card
Version:

To Reproduce
This is the configuration I used:

Screenshots
If applicable, add screenshots to help explain your problem.

Expected behavior
A clear and concise description of what you expected to happen.

Desktop (please complete the following information):

  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@man010 man010 added the bug Something isn't working label Feb 23, 2024
@man010
Copy link
Author

man010 commented Feb 24, 2024

I answer to myself. This issue occurs when the series are not configured in the same order as the corresponding yaxis :

WORKING

yaxis :

  • id: first
    yaxis :
  • id: second
    Series :
  • entity: a
    yaxis_id: first
  • entity: b
    yaxis_id: first
  • entity: c
    yaxis_id: second
  • entity: d
    yaxis_id: second

NOT WORKING

yaxis :

  • id: first
    yaxis :
  • id: second
    Series :
  • entity: c
    yaxis_id: second
  • entity: d
    yaxis_id: second
  • entity: a
    yaxis_id: first
  • entity: b
    yaxis_id: first

@stepir
Copy link

stepir commented Mar 7, 2024

Thanks - had exactly the same issue and found this thread

Copy link

github-actions bot commented May 7, 2024

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days.

@github-actions github-actions bot added the Stale label May 7, 2024
Copy link

This issue was closed because it has been stalled for 10 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Stale
Projects
None yet
Development

No branches or pull requests

2 participants