Page 1 of 1
Graph Y range
Posted: Saturday 01 November 2025 15:37
by EskildP
Which setting determine the Y range in a graph?
I have two different domoticz servers, one is showing the daily graph of temperature and percentage with the lower Y value determined by the min value of the data whereas the other always is relative to 0 (zero).
Would be nice if anyone could tell how to get control of this

Re: Graph Y range
Posted: Sunday 02 November 2025 1:20
by waltervl
Perhaps you are looking at the humidity graph of a combined temperature +Humidity device?
Re: Graph Y range
Posted: Sunday 02 November 2025 11:09
by EskildP
No, this is type General, Percentage. It is actually the charge % for mye EV.
But I observe the same behavior for type Temp, LaCrosseTX3 and for type General, Custom Sensor.
I think this comes from a global setting, but can't find which setting.
Re: Graph Y range
Posted: Sunday 02 November 2025 22:51
by waltervl
Ah, I misread your question.
This is probably because you clicked on the Y-axis label. It then switches between 0 to highest value range and optimal band range. There is no global setting for it.
And perhaps the implementation for percentage is not the same as for temperatures....
But it also looks like you have 2 versions of Domoticz running. Filled in graphs is new in 2025.2. Or it is a browser cache issue. Perhaps look are the same Domoticz instance with the browser in incognito/private mode.
Re: Graph Y range
Posted: Monday 03 November 2025 19:48
by EskildP
First server is 2025.1 build 16672
Second server is 2025.1 build 16712
Learned the trick about klicking on the y-axis label, thank you
First server acts as you described, second is always based on 0

Re: Graph Y range
Posted: Monday 03 November 2025 19:56
by waltervl
Ah, both are beta versions so indeed can behave differently. Better put them on the same build version, use stable 2025.2 for this.
Re: Graph Y range
Posted: Monday 03 November 2025 22:39
by EskildP
Both servers now on 2025.2 build 16818 (Docker domoticz/domoticz:stable).
Same behavior on both servers, behaves just as you described.
Problem solved, thank you

