ninjaef
January 24, 2025, 10:21pm
1
On my Y-axis, left, I expect there to be a scale from 17.0 to 23.0 with steps of 0.5. However this is not happening and I do not understand why.
type: custom:apexcharts-card
header:
show: true
title: Room temperatures
show_states: true
colorize_states: true
graph_span: 72h
series:
- entity: sensor.heating_climatecontrol_room_temperature
yaxis_id: thermostat
name: Thermostat
type: area
curve: smooth
color: gray
opacity: 0.3
stroke_width: 1
float_precision: 1
show:
legend_value: false
in_chart: true
- entity: sensor.meter_plus_da53
yaxis_id: lounge
name: Lounge
type: line
stroke_width: 1
float_precision: 1
show:
legend_value: false
in_chart: true
- entity: sensor.meter_plus_88d5
yaxis_id: kitchen
name: Kitchen
type: line
stroke_width: 1
float_precision: 1
show:
legend_value: false
in_chart: true
- entity: sensor.heating_climatecontrol_leaving_water_temperature
yaxis_id: lwt
name: LWT
type: line
stroke_width: 1
float_precision: 1
show:
legend_value: false
in_chart: true
yaxis:
- id: thermostat
opposite: false
show: true
# HERE ###########
apex_config:
min: 17.0
stepSize: 0.5
max: 23.0
##################
- id: lounge
opposite: false
show: false
# HERE ###########
apex_config:
min: 17.0
stepSize: 0.5
max: 23.0
##################
- id: kitchen
opposite: false
show: false
# HERE ###########
apex_config:
min: 17.0
stepSize: 0.5
max: 23.0
##################
- id: lwt
opposite: true
show: true
Mine works, and I think I went through the same process as you and got it by putting these settings in a general apex_config
(ie. no indentation) rather than under the yaxis.
type: custom:apexcharts-card
apex_config:
yaxis:
opposite: true
min: 17.0
stepSize: 0.5
max: 23.0
thanks
close, but…
other way round,
I want the step size 0.5 on the left with the min,max…and on the right no minimax no step, plotting only LWT
type: custom:apexcharts-card
header:
show: true
title: Room temperatures
show_states: true
colorize_states: true
graph_span: 72h
series:
- entity: sensor.heating_climatecontrol_room_temperature
yaxis_id: thermostat
name: Thermostat
type: area
curve: smooth
color: gray
opacity: 0.3
stroke_width: 1
float_precision: 1
show:
legend_value: false
in_chart: true
- entity: sensor.meter_plus_da53
yaxis_id: lounge
name: Lounge
type: line
stroke_width: 1
float_precision: 1
show:
legend_value: false
in_chart: true
- entity: sensor.meter_plus_88d5
yaxis_id: kitchen
name: Kitchen
type: line
stroke_width: 1
float_precision: 1
show:
legend_value: false
in_chart: true
- entity: sensor.heating_climatecontrol_leaving_water_temperature
yaxis_id: lwt
name: LWT
type: line
stroke_width: 1
float_precision: 1
show:
legend_value: false
in_chart: true
apex_config:
yaxis:
opposite: false
stepSize: 0.5
min: 17
max: 22
yaxis:
- id: thermostat
opposite: false
show: true
apex_config:
min: 17
stepSize: 0.5
max: 23
- id: lounge
opposite: false
show: false
apex_config:
min: 17
stepSize: 0.5
max: 23
- id: kitchen
opposite: false
show: false
apex_config:
min: 17
stepSize: 0.5
max: 23
- id: lwt
opposite: true
The challenge is that if the parameters can be managed on different levels, overwriting/ruling them with apx_config not always works.
Try this
- id: kitchen
opposite: false
show: false
max: 23
min: 17
apex_config:
stepSize: 0.5
Side note: not sure why you defined 3 axis with the same settings, one would be enough
because if I omit any of the “- I’d:” attributes, I get an error for each one, so all four must be defined !
/// apexcharts-card version 2.1.2 /
// yaxis_id: lounge doesn't exist.
If I add lounge but omit kitchen then the above area disappears but it’s replaced by kitchen doesn’t exist error, and so on.
All four must be defined
??
your solution makes no difference sorry thanks for trying
You should refer all 3 series to the single y-axis…and not 3 series to 3 y-axis with the same setup (makes no sense)
and my solution does work but anyhow… you have to play around
ninjaef
January 25, 2025, 10:05am
7
Doesn’t work for me
Maybe it’s something else
what do you mean
“refer all 3 series to the single y-axis”.
how? because I thought that’s what I’m doing with the three IDs under the y-axis attribute