Oh shit. 
I donāt have plans for a full versioning system, it feels like overkill. But let this be a lesson to everyone: export and backup your dashboards. 
If you delete the app, your files go with it. If a bug wipes them out, Iād feel terrible knowing you lost all your work because of a fuck-up on my end
Yes, the icon explorer only searches through their actual filenames. Not related tags. If you want a better search to find the icon, you can use:
I shall investigate this. 
Thereās no specific setting for that. Just use a graph with no background, put it in an empty container, and add a label as a separate layer. Thatās kind of the philosophy behind Dashboard Studio, itās more like a drawing program where you can layer everything exactly how you want. Rotating labels is a good idea, though. Iāll add it to the list.
Iām not 100% sure what you mean here. Is the time not fixed in your graphs? Normally, data is in UTC and the graph has to correct it to the local time zone. But for the Homey export insight card, I already converted that data to the local zone. I did this so I could create ātodayā graphs even if future events havenāt happened yet (For this I needed to convert it to local timezone to calculate the right timeframe for this). For any non-Homey graph data with utc time, Iāve added a timezone converter directly in the graph.
I have been waiting for this type of product for a long time, and after exploring it for a few days, I am very impressed. It seems very stable and virtually bug-free so far, although I still have a lot left to test.
I have a question regarding the āArrowsā feature.
I am visualizing the energy flow in my home, and since I have both batteries and solar panels, I have several bidirectional flows. To make the animated flow change direction, I currently switch the Start and End values via Homey. Functionally this works fine, but there is a significant downside.
Because my energy setup is quite complex with many arrows, I need to keep track of all these Start and End configurations in Homey. If you also have a dynamic layout where components are moved or optimized over time, updating all those Start and End values becomes a considerable amount of work.
Is there a simpler way to solve this? Ideally, I would like a flag such as āForwardā / āBackwardā that I can control via Homey without having to swap Start and End.
Well, not entirely bug free if you have read the full topic though , but most of it where just little widget quirks. But the base software has been rock solid. There are over 200 installations and still 0 crashes 
I have also several bi-directional flow animations:
The way I do it is to layer two on each other and hide and show them dynamically with the visibility setting (āWidget infoā section):
This way I can also change remove the flow entirely when there is no flow (like no sunshine) I can also pre-set the color of the flow (good = green, bad = red). Of course you can also change the color dynamic if you wantā¦ there are so many ways to achieve something.
But I like the reverse flow direction option idea. Ill add it to the list.
This chart looks great! Thanks for all your work and time (donation made).
The time in the graph with a Homey Insight as source now works properly.
This confused me: the Insight is already converted to local time, without using the āConvert UTC to local timezoneā.
EDIT
Minor remark: a Group/Container has a type āemptyā in Selected widget dropdown.
Thanks! Appreciate it 
Raw Homey insight data is in UTC time. The DS Flow card converts this to the local time zone inside Homey and then sends it to the DS dashboard. So the Graph widget already receives local time data and does not have to convert it. (so that why it works when the UTC conversion is off). But if another source sends graph data in UTC format, the graph widget needs to convert it to local time. Thatās why there is a convert option.
Ah, yes. Real early versions I named this an empty, but forgot to rename it later on. This whole dropdown needs a bit of overhaul. It is a pain to find something. Usually I just click the widget I want to change, but with layered widgets it is hard to click the back one and then I have to scroll through this list.
With large multi page dashboards there are so many items and makes it hard to find the right one.
My idea:
First sort every item per page, then sort by type of widget (I always know the type of widget I want to change, but I always forget to give the widget a proper name) And then sort by name?
I am also thinking about color coding widgets. So each widget has his own color so it is easier to identify it in the list.
But I am open for ideas. Iāll probably do what I think is best, but someone might influence that 
As the number of options increases, improved searchability is important. In general, I would sort lists alphabetically whenever possible in the application.
I agree with your suggestion to sort āSelected widgetsā: by page, by type, alphabetically.
Although you can search by parts of names, further structuring data sources (for the same reason as widgets) and removing duplicates would also be desirable (duplicate: name AND path with name).
Because I plan to create a large number of pages (~30) in the dashboard, Iām defining each page as a separate dashboard. Could the transition between dashboards in the developer mode be made even simpler/more transparent?
Given the already considerable number of options, assigning colors to different types of components seems undesirable (āchristmas treeā look). Butā¦ you are the graphic designer.
I can not seem to reproduce this problem. I have connected an [ONOFF] capability of a light and a smart plug to the visibility property of a image widget. And the image hides and show just as expected when the light or the smart plug is on or off.
Ok, thank you for trying. I have a device created with Device Capabilities | Homey to combine some values and states in one device. Maybe this app deals differently with it. I just donāt know.
But I am more than happy with using the flowcard to sendan event. This works perfect so I will use that!
