How to adjust the bar span only to the right of a data point?
Hourly prices are now off from the data point by a considerable amount (30 min) which is clearly visible in the chart and shows wrong price for half of the time period.
I may have found a bug in apex-charts or something is not quite right. So I have a monthly utility sensor used to capture energy usage from a smart plug. And then I use apex-charts to plot that monthly usage.
But if I use the color option under series, the data from July is not shown in the chart.
I have this simple electricity market price card, and it has price values for today and updates later also for tomorrows prices, I was able to get that dotted line to show current time, but I don’t find a way to show that value above, instead the number above is always the last number of the array of prices.
Is it possible to define somehow what is the “now” value?
Hi, I have a sensor that shows me the electricity consumption of the previous day every day. The sensor changes value every night at 00:30 Is it possible to take this value of the sensor every day at noon to create a graph of monthly consumption?
Question on color_threshold and days shown. My chart looks good for 5 days but as soon as I go to 6days I have a red (high threshold) line showing across the whole range even though it shouldn’t.
With 2023.9 release, weather forecast do not have forecast attributes any longer. Forecast data now are cached and can be retrieved via a service: weather.get_forecast.
I have no idea how to use this service to return data for apex, in my case, to display forecasted temperature in a graph, as well as forecasted rain volume and wind.
Below an example on how to populate a sensor by calling this service. Which I can use to store forecast data in a sensor as its attributes for sure… but this is not elegant nor would take advantage of data being cached. Any idea?
The sensor code only showed half of it (browser issue with me). If you followed the large poll on keeping fc then you see plenty of people wanting to keep it. The technical reasons may all be valid but the end-user (,e/us) are stuck with card that are not up-to-date and apex/plotly that have no solution …and these highly will never have a solution as this is very sensor-specific.I am not sure why you would need / want cached data…I only need access to the data, dot-end, care to elaborate why cache is important to you?
If you have a smart technical solution or an evidence that service/cache cannot be retrieved please share it. We can discuss but personal opinion on breaking change due to 2023.9 is not what I am looking for
I have none and again, I donot see any need for it neither are you presenting a reason for needing cached data…why make it complex if the solution is ‘simple’