Yeah, at least using card_mod, it’s possible to change the font size of the header. Obviously, I don’t know what I am doing, I only did try copy the way they did in card_mod forum Unfortunately, the change below would affect all text elements in the header, proportionally. And the “xaxis” somehow affected. At least I achieved the goal, to have a bit smaller texts so they render nicely on my phone!
I have experienced similar “missing” data for some graphs. Setting cache: false solves it (probably at some performance expense that hasn’t been noticeable).
It can be done, but not with the HA implementation of ApexCharts. You would need to have a good working knowledge of HTML and Javascript and know about locahost, plus using Google to search for example code. There are also examples in the ApexCharts documentation.
Once you have written your code to access your data, say by a Text file, Excel or fixed within the ApexCharts, you can access your locahost enviroment by using the HA Webpage card.
Not only that, you have the best of two worlds, direct access by localhost and within HA.
Job done !!
Is there a way to combine/calculate different sensors into a single serie value?
Use case: m3 gas consumption per daily degree day.
Situation 1:
If the user already has a daily degree-day sensor and the gas consumption is known. Both can be pulled from long-term data.
The data generator would in fact do the following:
Pull daily degree day per day from long term stats.
Pull gas consumption per day from long term stats.
Divide the gas consumption with the daily degree day to get the daily m3/DD value.
Situation 2:
In case someone doesn’t even have a daily degree day value but does have temperature stats it should be the following:
Pull outdoor temperature per day from long term stats.
Pull indoor (target) temperature per day from long term stats.
Subtract outdoor temperature from indoor temperature with a minimum of 0 to create the daily degree day value.
Pull gas consumption per day from long term stats.
Divide the gas consumption with the daily degree day value to get the daily m3/DD value.
I know of course that I can create template sensors and work it out like this but there are two downsides from this:
You cannot get data from the past.
It puts a lot more data into the long term stats tables which I feel is not needed.
Hope this is possible and someone could help me with this.
Ok, total noob here and could use some guidance. I’m trying to display values sent over MQTT, serialized with JSON. I followed a few examples above but am clearly doing something wrong.
I know this portion is working correctly, but displaying a single sensor attribute in the ApexChart just isn’t working (several attempts have even caused Home Assistant to hang/crash). The goal will be to overlay water_level values (discrete #) with level_sensor inputs (toggles between ‘wet’ and ‘dry’) but I’d settle for just displaying the water level to start. Any guidance would be most appreciated!
Can someone help with rounding values in the radialBar display value?
The 2 graphs below show battery (delivered already in %) and signal (dBi) I have created a range (Min: -130, Max: -40) As you can however see, when the values come through, this is not rounded, ideally to no decimal places.
sent as attributes in the sensor.reef_controller_ato or how are these displayed in Home Asstant (assuming that this is a MQTT sensor as opposed to binary_sensor?)
If you are purely looking for the wet/dry sensor, you could create an MQTT binary_sensor out of just those 2 attributes?
Correct, they are attributes in the sensor.reef_controller_ato. Good idea to break them all out into their own sensors as you proposed. It would be nice if I could just grab the attribute and compute from there, but whatever works in the end!
this is also how you would configure each of the attributes as an individual sensor if you were configuring the sensor.yaml as opposed to the mqtt.yaml
so as you can see, there are loads of different paths to achieve the same outcome.
You should however just pick one and standardise on that for maintenance purposes moving forward (in case you need to change something du to breaking changes)
personally, if the data point is important enough, i create a dedicated sensor for it…