Cool
Will give it try
But i was looking for the status widget earlier but its the test version!
That’s why I asko how hahaha
Just a hint for everyone, it’s very easy to translate text on screenshots or pictures/drawings with:
2 Likes
Luckily I’m Dutch!
1 Like
Thanks Peter for this tip!
Just wondering: is there an easy way to just change the Homey interface language on a per device basis (phone/tablet mobile app, web browser, etc.)? As far is I know you can only switch the language for all devices/interfaces and that requires a restart of Homey.
Ahh, I didn’t think of that 
. Indeed the status badge is only available in the test version.
Yes, the web app can be translated by your browser!
At least Chrome & Firefox can.
Default:
Translated to Dutch:
Unfortunately Homey has to be restarted after changing the common generic interface language.
With a busy (older) Homey, it can take up to 45 mins.
Version 0.9.4 of DataVista is now available in the live channel. This means everyone can now use the new status widget 
!
Here are the release notes:
Version 0.9.2
Added the DataVista status settings to the DataVista app settings page
Version 0.9.3
Added a fallback mechanism to prevent the widget from getting stuck if an error occurs while retrieving a capability icon
Temporarily fixed the progress bar height to avoid it getting stuck on the loading screen when the name is hidden. This will be reverted to the dynamic height when Athom released a change to adjust the minimum allowed widget height.- Added native
fetchsupport with a fallback tonode-fetch, resolving issues on Homey devices running Node.js versions other than v18 (e.g., Homey Pro Early 2023) when widgets with icons were used. This ensures compatibility across all supported Homey platforms. - Added a fallback to 0 for invalid or corrupt percentage values in the advanced gauge widget, ensuring proper display and functionality.
- Updated dependencies and other minor changes
Version 0.9.4
- Updated the status widget preview image according to Athom’s guidelines
Test version 0.9.5:
Fixed an issue for the label widget by calculating the animation speed based on the label length, ensuring consistent animation speed regardless of text length. (@Kai_Engvik does this resolve your issue?)
3 Likes
That’s indeed how the advanced gauge can be used. Addtionally, you could add the gauge configuration card after both to adjust the color scale accordingly. It’ll ask for an identifier that you can select in the advanced gauge widget settings.
2 Likes
Sorry for the late response,
It is on ipad, iphone and an lenovo 7 inch android tablet. All have the icon cut off.
(Using the status widget now, works briljantly! thank!)
Great job. Love the widgets. Apart from the gauges I am using the Status Badge.
Just enquiring if it might be possible to have a half Bar style. So the same width as a Bullet but the same style as the Bar. The colour bar is important to me and the colour dot you get with the bullet style is not quite big enough. I would like to be ble to get two bars across the page in the space one bar takes up currently.
This could be done as an additional style or as a parameter I guess.
1 Like
I try to use the widget label. Is there a way to configure title and colour background through a flow? That would be awesome.
I tried to use the datavista flowcards but I have no succes. Where Can I find or set the identifier?
I do not understand at all.
How does the flowcard refer to a datavista widget? Usually a widget has an identifier as property and one uses this identifier in a flowcard. But this is not how datavista is working?
When creating the label widget, you need to select a data source (‘databron’). That source is the identifier that is linked to / updated by the flowcard indicated:
The result of the flowcard is then shown in the label widget:
Aha, thnx a lot. I can see results in the app configuration and then it becomes available in the data source.
I begin to understand.
I have made two progress bars, but they lay out differently with same settings. one slim and one fat. I want both slim to save space and look uniform. Why do they differ?
Any data source that does not represent a native percentage will be displayed larger to accommodate both the value and its unit. The smaller variant may lack sufficient space to present this information effectively in the same position on the left.
You could make the top widget larger by using the ‘DataVista set range’ card and use that as a datasource instead. You’ll then manually set it to a range of 0 to 100 and update its value on every change of the EQC SoC percentage. This however does not yet support icons.
Hello,
I use the module on an old ipad, mainly for posters, it’s the best module in terms of functionality.
but when we put more than 3 it becomes very difficult to read the values. is it possible to have a display with an “adjustable” font size? and the top will be just a value/text display (large enough) and that we can choose an icon (for decoration).
thanks and happy new year to all
