That’s not good. That did not happen during the testing period among the testing users
that should have been 1.10.1
Sure. It would really help if you can send me your dashboard 1.9.4 version file over a PM:
In the “Load from Homey” dialog you can save previous versions:
This is all incredibly impressive. Especially that last item. So you actually went from separate dashboards to a single dashboard solution? I am still working on a special widget that can “teleport” other widgets from different dashboards to solve your problem with creating and changing multiple menu systems over multiple dashboards. Initially, I thought it would also be useful to create dialogs with this widget by teleporting widgets from the same page to another page, but the simpler option of changing the page setting on a group solved this already. Anyway, you are my number one tester. A lot of features came straight from your requests.
Yes, it is in the making. But it is a horrible one for me to test haha! I literally need to break my entire setup to see if it correctly restores
I have to think about this one. I try to make everything as versatile as possible. Maybe I should incorporate an “audio player” as a non-visible widget that is only visible in edit mode and can play audio. It would just trigger when a topic comes in, maybe even a topic with a volume value. This way, a user can make the dashboard play a warning sound from Homey when something needs attention on the dashboard. Also, the buttons would not need an extra option because you could just trigger the click sound via a second output topic using local topics. But what about the sounds? It should be easy to upload them, so maybe I should make a sound browser just like the gallery option. Open for ideas on this one (also others do not by shy to pitch in on other users ideas ) I add it on the list.
Initially, I was afraid that the DS software would have performance issues with 30 pages, so I started putting each page in a separate dashboard. This had significant drawbacks:
reusing objects across multiple pages, such as a global menu
switching between dashboards took longer than switching between screens.
Because performance remained good even with larger numbers of pages, and due to the teleport function, I eventually put everything into a single dashboard. I think a modern, fast tablet is required for these numbers.
For me it is not necessary anymore with all pages in one dash. Now I know how to use mySQL, the maintenance of the menus in multiple dashboards would be less of an issue. Before, when one menu item would change, i had to update that menu for each dash, so 30 times.
To be honest, I don’t see any desire in this forum to have multiple dashboards call each other either. Perhaps a dashboard for a tablet and a derived dashboard for the phone, but they wouldn’t call each other.
That would be nice, and deliver a few default very short and fast clicking sounds, which can be extended by the user. You probably know there is a Homey Soundboard app you can use for inspiration or integration. But judging by your development style, you would rather create a sound library yourself. Pixabay has lots of royalty free clicking sounds
High on my wish list:
“When” card upon page change/load, execute for example an advanced flow option. I use a number of free api licenses that may be called a limited number of times per day or month, so I cannot have this run every x minutes/hours by default.
Currently, I have solved this with Homey scripts, memory variables, and MySQL tables, but there must be a better way.
User-friendly confirmation of execution
Nice to have: glassmorphism options.
Can you tell us a bit more about the features currently under development?
I am working in parallel on a V2 version. But I’m not going to disclose any features yet, besides a hint: as the advanced user you are, you will probably be disappointed.
You can imagine, since some 1.x updates with big new functionality had a small number increase, I now have high expectations when the version number will be 2.x.
I’ve noticed that other users would also like to use the light grid for different purposes. The light grid is a bit of a special widget designed to send multiple values in a single JSON message, making it possible to control individual lights or groups of lights.
If you are looking for more of a list of items that you can activate/deactivate (and/or set specific values for when they are turned on or off), you can use the menu widget instead. However, it doesn’t share the same look as the light grid. Of course, you can easily mimic the design of the “Light grid” by combining a container, switch, label, and icon widget. Just match the styling and duplicate it 10 times (though this approach won’t let you scroll through them). For example, check out this post where I recreated a design another user wanted:
That being said, you’re definitely not the only one who wanted to use the light grid widget for devices other than lights. Maybe I should rename it to “Light / switch grid” or something similar and build in the ability to use the items just like a regular switch.
That should be possible, but wow, that is cramped . A couple of things to keep in mind:
First, there is no specialized weather widget, so you will have to create that yourself using the available widgets. I think a standard “text” widget combined with a HomeyScript that generates a markdown table for it should work just fine.
What a crazy good app. Yes it has a steep learning curve but after that. WOW. Thanks so much.
Because there is always a question, here is mine. I can change the direction of a arrow depending on the Dynamic Binding. That’s great but where is this Binding to be found?
If this is enabled, the flow reverses (and so does the arrow). If you make this setting dynamic by hovering above it until a small chain link appears and clicking that, you can activate this setting based on a dynamic value. You can add a topic inside it (just make up a name for it) and send true, false, 0, or 1 from a Homey flow to enable or disable it. Use this card for that in a flow:
You could also connect the dynamic value directly to some kind of sensor. If you need to invert the value in that case, you can set custom true or false values by clicking the small invert button next to the chain icon:
No, sorry. To be honest, a big part of that decision is to protect the visual style of the dashboard. If a dashboard starts getting filled up with a bunch of different website snippets, it becomes a messy and ugly patchwork. I really think a dashboard in your home should have a nice, clean, professional, and unified look. For example, that weather snippet you put on your current dashboard is exactly what I meant. It completely clashes with the rest of the design. It has a blue gradient background with square corners, while all the other elements have a grey background with rounded corners. It has a different font, different typography, different colors…
As a designer, this is also a personal annoyance of mine with the native Homey dashboard app. Everyone creates nice-looking specialised widgets for it, but every single widget has its own style. While that particular widget may look great on its own, when you combine it with others, it just becomes a big patchwork quilt. And yes, I do understand that this conflicts a bit with the idea that users should be able to do whatever they want. But it’s my app , and while it is still in development, I try to facilitate (uniform) solutions to problems like these that actually match the theme of the whole dashboard.
Anyway, I think it is perfectly doable to create a nice weather “widget” with the exact same data using a Homey script and a text widget. I shall make an example tutorial for you on how to create something like that without butchering the style.