Thanks for confirming this.
1.7.2 is released in the Test app store. Both problems are fixed 
A few nice features for your to-do list: Tags for dashboard name and page in the loaded/refreshed trigger card, and new triggers for page change and for closing dashboard (with tags).
Background: I have a few dashboards, one of which has a number of insight graphs on a page. I think updating those graphs is a waste of processor capacity if no one looks at them.
Another feature is: in the past, someone asked for an âeditâ URL parameter. I could really use that too. I do trust my users, but I donât want them to be able to edit without making things difficult for myself. It doesnât prevent sabotage, but it does prevent accidents.
Another suggestion for âthe listâ:
I am trying to use end-user names for settings, also in menus. When I load a page, the menu has to highlight the currently activated capability option of a device with an end-user setting.
There is already a link between end-user name (Label), capability (Output topic) and value (On value).
Now I have to define all kinds of flows for each capability/value combination. Flow below is handling just one capability:
Please let me know if I am overthinking it.
This was already implemented in version 1.6.2:
The dashboard name is already available:
In the future I want to completely split the editor from the viewer. Now the whole editor is loaded in the background. For now it seems to run fine (even on 13 year iPads). But optimising is always good. But that wonât be a short term upgrade. Pretty complicated to split everything.
Does the page change topic also fire (p.e. with page 0) when the dashboard is closed?
I did some tests, I was wondering why you disabled the buttons also but turns out that when you make the state dynamic it is fighting the selection group ID. Lets say I would expect when I set the state of one button to ON, the other buttons state should automatically go to OFF. Anyway, weird things are happening when two things try to control the same setting.
You are basically setting the radio group yourself now, so it is better to remove the selection group ID.
I donât know if I can âfixâ above problem. The topics stay in memory and if you do not set the other topics to false, it will resend all topics âtrueâ, in an unknown order. Maybe it is better to disable the selection group ID option when a user makes the âstateâ dynamic.
Anyhow, since you translating this to Dutch you need to split everything up anyway. There is no quick solution around that I think. Or use a Homeyscript. To be honest, the flow might look bloated, but it is perfectly clear and easy to understand what happening.
When this is fixed, and if you do not need to translate the text, you could theoretically merge this into a couple of flow cards.
No, but I might be able to create a flow card for that. Couple of edge cases to keep in mind. Like should it trigger a close, if one instance of the dashboard is closed (but the same dashboard is still open on another computerâŚ)
Defining Icon colors in a switch doesnât show the Theme option. As you can see, I could use some theme colors, instead of all these different colors.
Suggestions:
- let the color popup screen remember the last chosen option during a session: Used Custom Colors or Theme
- reintroduce typing in the color code; I can type, but nothing seems to be happening
- by default the color sliders are HSL based, even when RGB is selected; let the sliders match with the âcolor systemâ
Your conclusion seems to be the same as mine in post 683.
I think you have the same questions with a page change.
Why? A page change should always trigger an update because something on that page likely needs to refresh. Even if there are multiple instances of the dashboard (like it is open on multiple computers), the active page should definitely update because a user is clearly browsing it. However, when a dashboard closes and the user needs to know about it, itâs usually because they want to stop updating something. The problem is that if another instance of that dashboard is still running, it would stop getting updates too. So itâs probably better to only send the message when the very last instance of that dashboard is closed.
It shows all colors that are somewhere configured in the dashboard. It is probably an older dashboard with all colors still configured in the widget defaults. All these colors are custom colors. Granted, I have not see so many colors 
. Thatâs why you are the Stress Tester 
Just for fun, press this button:
And this button:
(Theme color section) And check again. Should clear most of the custom colors.
The color should be shown when press [enter] ?
Yes, these buttons clear the number of colors, but make a mess of my existing components used in âoldâ DS dash.
Maybe it has to do with the fact, that I only use the first 6 Theme colors on top of the Theme color picker, not related to the functions of these colors (to much differentiation for my usage).
Still wondering why the icon color setup doesnât have a Theme color option:
Indeed, Enter button will do; Tab (which I used) button doesnât.
Trying to use a Toggle Switch. Normally the values or on/off, true/false, 1/0 (even case insensitive). In this case it is Swing and Stop as On and Off, but the switch doesnât respond. When the switch receives Swing, it knows the related value is On.
It seems that I am using de Airco setup as a use case for a lot of other devices.
Is this behaviour as expected? If yes, could this be more flexible without defining flows?
I agree with you but sending a page change to 0 only shows what is happening. The user should decide what to do with it. He/she can track the number of open page xâs when the from page is also included in the trigger. Btw the dashboard name is also needed in all trigger cards.
Haha, love it, Exceptional work, Number One! Please share when it is finished.
How did you create those lines, is this just svg?
The default colors in old dashboards where set in the widget defaults. In the new dashboards they are the theme colors and the widget defaults are linked to the Theme colors. Of course you still can put a custom color in a default widget setting, this wil become a custom color. Thats why old dashboards have lots of custom colors. They donât use the theme colors.
I did not meant that you needed to reset the colors or relink them. It was just a test.
It is just the first release of the color picker, I read all messages and it will improve.
Bug, thanks. Will fix this.
Not sure what you are trying to do here. I assume you are trying to set the state of a button using âSwingâ and âStopâ? No that is not supported. Swing and stop? Never heard about such a boolean value. It just interpreted them both as not zero, so true.
Why? The only (when) card that does not provide this is the â[event name] triggeredâ. In what kind of situation do you need the dashboard name? Can you give me some examples?
Sorry, didnât check.
What Iâm trying to say: could the switch be a bit more flexible; just two values? High and low, left and right, swing and stop⌠One On value and one Off, and the configurator can decide which one is On and which one Off. Or is that technically impossible?
Adding the actual page to the event trigger has the benefit you can perform page dependant actions.
For example a button displayed on multiple pages can do actions for the page it is hit.
Hi Satoer
Iâm still not quite getting it. Iâve attached two screenshots.
Iâve set the symbol to display a scale up to 30 degrees. Then I adjusted the colors of the arc. Now my goal is for the small thermometer in the middle to change color. When the heating is on, it should be red. When the heating is off, it should be blue. But I canât get that to work. Can you help me with this?
Thanks to your help file, I managed to do it. The exact example was included there. Thank you so much, now I can continue.
