Refer to earlier posts, like:
1 Like
I did read a lot of posts before asking this, but didn’t see them.
Thanks for your attention to it.
I recently installed your data vista app. I think it’s a really great app for the charts which support two lines.—thank you for that. However, I do have a couple of small issues. In dark mode, the color of the text on the axes is very dark, which makes it hard for me to read.
The popup showing the values for a point in the chart is also really useful, but I can’t manage to read the small text. Could this be made larger?
I hope this feedback is helpful to you.
1 Like
Hi @Erikvl87, I have been trying out the flowcard to configure the colors of the progress bar. This works great. I have a question / possible feature request.
The current flowcard uses a color picker, in which I (manually) select the color. Is there a way to - in addition to a manual selection - set the colors based on a variable/tag that I can set programmatically? If not, is that something you are planning for a future release?
The usecase is that I want to give the progress bar a single color that depends on something else. E.g. show a green bar in case the CO2 level is OK, a yellow bar when at medium level, etc.
DataVista v1.0.0 is now available in the test channel!
This version includes a minor new feature:
Added rolling period support to line chart widget. It displays the last 24h/7d/31d/365d based on selected timeframe. You can select it in the period settings of the widget.
Bumped DataVista to v1.0.0! It doesn’t mean anything but felt like the right time to do so 
I’ve been pretty quiet lately as I was on holiday and needed to focus on some personal stuff. Thanks for your patience. Hope you enjoy the new rolling period feature.
As always, let me know if you run into any issues or have suggestions.
5 Likes
Thanks for reporting, I’ll try to reproduce and see if I can improve the contrast for the colors and increase the popover text or make this adjustable.
1 Like
Hi @SunBeech! Ideally this would be solved at the Homey level. It would be awesome if the Homey color picker natively supported variables/tags.
For now, a not-so-elegant workaround would be to check your variable’s value first, then redirect to different progress bar configuration flow cards with a pre-defined single color based on the result. I assume you might already have something like this in place.
Would some kind of advanced color update card be an acceptable solution? No promises yet, I don’t want to clutter the app too much.
That’s a great suggestion! I hadn’t thought of that 
. Thanks.
1 Like
Great work. It must feel like a complete product now.
I like this app and use the graphs in all my dashboards because the are better end nicer then de Insight graphs from Homey.
Thank you!
1 Like
Hi everyone,
I’m thinking about changing the way the rolling periods introduced in 1.0.0 are implemented. Instead of having “rolling period” as an option in the period settings, I’d remove that and add ‘60m’, ‘24h’, ‘7d’, ‘31d’, and ‘365d’ to the timeframe options.
This would let you compare the current rolling period with a previous rolling period in an overlapping view. Something that isn’t possible right now.
What do you think?
3 Likes
Sounds good and is for me quite an improvement compared to Athoms stats.
1 Like
When using a gauge to show the current value of a %-slider, the value shown is between 0 and 1, not 0 and 100. This is a device from the Virtual Devices app. Is this a bug, or can I work around it somehow?
No, this unfortunately is “as is”.
Homey recalculates the (internal used) 0 - 1 values as 0 - 100% values in the user interface.
When you’d like to see 0 - 100% values in the gauche, you’ll have to add a Y * 100 calculation yourself.
I stumbled across your app when looking for a way to display multiple lines on a graph in the dashboard. The new ‘rolling’ feature works well and was just what I was looking for. Many thanks for your work on this. FWIW I’ve no need to compare data across periods so your implementation using ‘rolling’ works well for me.
The two lines I’m showing are temperature and humidity. The are labelled as °C and % so it’s clear what each line represents. I therefore don’t need the legend below the graph which takes a lot of space. It would be good if I could remove it; perhaps an ‘Overwrite name’ of None?
Thanks again,
Andy
1 Like
Thanks for reply - I assumed as the gauge apparently detects it is a percent display (it displays percent sign after number) it could/would do this. Anyway, I figured out how to do it in Advanced Flow with the Advanced Gauge and Logic, works great.
(Adding a Multiplier option to Simple Gauge would make this use case easier for others).
Maybe the dev Erik can shed a light on why having a “auto multiplier” or not on the % gauge widgets.
Hi Andy! Glad to hear you like the app! I’ll soon release an option to hide the legend/controls, as you’re not the first to request this feature.
Hi Peter & @clindh,
From the top of my mind, the data Homey is giving my app contains, amongst others, the properties min, max, unit and value.
For percentages, it would be great if Homey would return 0, 100, [value] but it seems it (sometimes?) returns 0 and 1 as its range.
I’ll certainly be able to scale them 0 to 100 but I’ll first have to look if it really makes sense for me to apply such change to the data, instead of changing the properties manually like @Peter_Kawa suggested. I’ll get back on this!
1 Like
Hi Erik!
FWIK the “internal” dim values are (always?) in the 0-1 range, but,
those values get multiplied by Homey with a factor 100, in “dashboard / display purposes”, and in flowcards with a slider as value input.
A bit of a mess 
Hello Erik,
i’m using youre DataVista app a lot, great app!
yesterday i made some label widgets on the dashboard. and i noticed the overwrith name is not very nice to see on a samsung a9+ tab, i don’t know how it happens ore maby it is a setting on my side?
but i tought lets mention it. if it is not a setting problem from my side and it is a small effort to adjust then that wil be nice but only for the aesthetic, but it works so if it is a big rewrite in code i sould leave it the way it is.
This is how i looks on the tab a9+
And this is how i looks on my phone, i’m guessing that is the intended way
1 Like
