[APP][Pro] DataVista

Hi @Erikvl87

I found a website with FA icons

Do you have a list which you can share?

I used F014 and F1f8

Rogier

1 Like

Ah got it. I initially misunderstood the reasoning behind your question. I’ll look into the possibilities, but I can’t make any promises yet.

Unfortunately Homey does not yet give us developers the ability to make complex widget settings.

The hard part is that some widget settings are tied to a single visualization; take for example the setting to overwrite the name. I’ll either have to copy each setting 5 times or make something newly configurable via flows.

Ill put this on the wishlist and I’ll report back when I have an update to share.

1 Like

As mentioned in the docs at Toggle switch | DataVista, these are indeed FontAwesome icons:

1 Like

@Erikvl87 - just wanted to give you some creds for your awesome widgets, really appreciated! It’s easy to see that you pay attentions to details and like design :slight_smile: Well done!!

2 Likes

Such a shame we need to create logic in homey itself to display a value just because the default device card is 80% covered by a useless icon. A datavista progress bar or logic value should do the job perfectly.

1 Like

Version 0.5.0 of DataVista is now available in the live channel, which contains the following changes:

  • :tada: The DataVista Progress Bar widget now supports DataVista ranges, enabling you to visualize metrics beyond percentages!
  • :triangular_ruler: You can now set a unit of measurement in the DataVista Range flow card, which will be displayed before or after your value in both the progress bar and Advanced Gauge widgets.

The progress bar widget requires a range to function. This means you’ll need to create a flow to set the range and update its value whenever the variable you’d like to display changes. Simply create a flow and use the DataVista Range action card to define your range and update its value. After that, you can now select the range as a datasource in the widget.

DataVista-0-5-0

When using a percentage as the data source, the progress var displays the standard visualization. However, when selecting a range, the value can represent any metric, so it is displayed inside the bar to provide more space for your data. The value color automatically adjusts to maintain contrast and ensure readability.

2 Likes

Absolutely! In an upcoming release, I hope to add new widgets for displaying single values, like numbers, booleans, dates, or strings. If you have specific ideas on how these should look, I’d love to hear them—feel free to share!

Hopefully the 0.5.0 release is already giving you some new possibilities to display your data :wink:.

2 Likes

It onyl works when you set ranges in a flow? And the progress bar won’t display the min and max right? I’d rather wait to the point I can just select the capability ‘temperature’ of my sensor, set a min and max setting and let it do it’s work :-). Setting stuff in flows seems a workaround to me.

About the single value widgets I think the value itself should be centralized. Maybe with a configurable gradient so e.g. for temperature the number can be from blue to red.

Another feedback thing is to use the same view for both bars. Now I have humidity below temperature. Temperature needs to be done with a flow / advanced bar as humidity is a capability. So I have a tiny bar below a big one.

Being able to use all the other capabilities like temperature makes it les independent from cards other developers put into their apps. E.g. my temperature sensor has a 'temperature has changed’card with which I can feed a bar. But it does not have a ‘humidity has changed’ card. Meaning I can’t update the humidity bar from a flow unless I pick temperature as trigger which isnt always the case.

The “eenheid” doesn’t work?

Not too bad:

@Dirk_vdM Thanks for all the quick feedback.

I’ll look into making it possible with just widget configuration, but like mentioned before, Homey is not giving us developers that much control over widget settings. This is currently making it hard to implement or the widget hard to understand. I would love to revisit this when Athom would allow us to create conditional widget fields.

For example, I’ll have to add lots of optional fields that clutter the widget:

  • Add 2 optional number input fields (start value and end value), both not applicable when selecting a value that’s already expressed as a percentage
  • Add 2 checkbox fields to indicate if any of the numbers are negative, since we’re not yet allowed to enter negative values in number fields)
  • Add another setting for the unit of measurement, since that is not always available
  • Add another setting to indicate if the unit of measurement needs to be before or after the value

I have to fall back on a bigger visualization because I can’t predict the values and unit of measurements being used by the users. The existing visualization is showing the percentages on the left, which is not enough space for most other data. Take for example, euro, minute or mhz where both the data as the unit of measurement takes way to much space to be presentable on the left of the bar.

But, as a solution, you should be able to use the DataVista percentage card instead and that should render the minimalistic widget visualization. Or, like you already did, visualize everything with the range cards rendering everything with the bigger visualization. The widget itself shouldn’t be heigher.

I totally understand. Currently, the only solution to this issue would be to create a flow that runs every x seconds/minutes and calls one of the DataVista cards to update the value. That’ll at least unblock you for the time being. I will try to come up with something better in the future.

You should remove the last part of the action card that’s overwriting the value with a label. That’s now overwriting the complete visualization (and number increment animation) with that value. You could use that for example in a progress bar or gauge, to show “Low/Medium/High” instead of the actual numbers. In your case you don’t need it and you should leave it empty instead.

Got it.
As for the unity. If I get rid of the label and out °C as value, my temperature had 2 decimals instead of 1 all of a sudden :smiley:

Thanks for the hard work sofar, very usefull.

Maybe one little feedback addition: The colouring of the bar is a little weird.
If I pick green to red it comes out in the middle with an orange/brown something.
Isn’t it posible to fill the progress bar with the gradient instead of filling it with the calculated colour in full?

Like this:

The 2 decimals should’ve been the maximum precision so I consider that a bug if the given value only had a single decimal precision. I’ll make sure to fix that in the next release.

I agree that a gradient could fix the strange colors you may end up with. I’ll look into this.

1 Like

Yes, I think at least regular, if not bold. It’s not a secondary label in my case. I get it if you want to include a title for the widget. So a choice would be optimal I guess.

Thank you very much for the quick adjustment!, I think the percentage visualization is nicer, but the functionality of the new one is great. A question: Is it basically possible to significantly reduce the space between the ads?


Definitely. Soon ™️!

datavista-reduced-height

4 Likes

Nice app!

I have tested some old tablets for my dashboard.
My 8 years old Samsung tab 10.1, seems to work, except with the simple gauge.
The simple gauge keeps trying to load forever, this works fine with an old Apple iPad.
I guess the Samsung is just too old and doesn’t have enough GPU power for this purpose, and that there is nothing to do about it?

Hello Olex! I’m sorry to hear that the gauge isn’t functioning correctly on your tablet. I’d be happy to explore potential solutions or determine if the tablet’s age and processing power might be limiting its compatibility with Homey dashboards and the gauge widget (and we may have the accept the fact that the tablet is just to old).

The next release will include more detailed logs. Following that, I will contact you again with instructions on how to provide those logs.

1 Like

:rocket: Version 0.6.1 of DataVista is now available in the live channel, which contains the following changes:

  • :capital_abcd: For the Progress bar and Toggle switch widgets the display name color now matches the default text color.
  • :heavy_plus_sign: For the Progress bar widget the datasource now also accepts capabilities out of the box that have a min and max value. This should allow for out of the box support for, amongst others, the capabilities dim, volume, light temperature and thermostat target temperature.
  • :straight_ruler: For the Progress bar and Toggle switch widgets the heights and margins are reduced. This allows for a better visualization when stacking widgets.
  • :put_litter_in_its_place: For the Progress bar and Toggle switch widgets the “transparent background” option is removed. Due to their reduced size, they are now always transparent.
  • :hammer_and_wrench: Fixed an issue in the Progress bar and Toggle switch widgets that caused some capability/device icons not properly centering.
  • :hammer_and_wrench: Fixed an issue in the Progress bar that caused a change in number precisions.
  • :hammer_and_wrench: Fixed an issue in the Progress bar widget that caused percentage capabilities not showing the minimal visualization.
  • :mag_right: In the Simple gauge widget, added some temporary additional logs for debugging purposes.
6 Likes

Hi Olex,

Are you familiar with sending a crash report? Could you follow these steps?

  1. Make sure to update DataVista to the 0.6.1 test version
  2. Close and re-open the dashboard with the simple gauge that is stuck in the loading spinner
  3. Make a note of the exact date and time you opened it up
  4. Directly after, create a crash report for the DataVista app
    You can do this in Homey → More → Apps → DataVista → :gear: → Make diagnostic report
  5. Send me the crash report ID and the timestamp you noted in step 3

Hopefully there’s some useful information inside the logs that help us determine the cause of the widget stuck at the loading spinner.