[APP][Pro] Dashboard Studio - A completely free-form dashboard designer

[Amersfoort]

@Satoer

and this happens, when bla bla…

Mockingbird.

This looks like an “anti-bounce” code thingy from 2 months ago.
There is also another variant described below of a button with a local variable. This option, in particular, isn’t that exclusive, though.
Both options worked before 1.8.0, at least.

@Satoer

Left vertical alignment set to bottom with a “3” vertical spacing . Right vertical alignment set to top with a “21” vertical spacing

What are the prerequisites to see the effect of these spacings? With my News table I can’t see any difference. Are images mandatory to see the effect?

[Satoer]

@Georges_IEGER

I think I’ve figured out the problem. My Homey is set to French. I need to force the value to 1 or 0 instead of the value returned by my flow.

Hmmm that should not be a problem at all. We, the Dutch, call the French “chauvinistisch” (ironically a French derived word) , but I do not think the French are that chauvinistic that they even change boolean syntax to French.

You really should be able to send that variable directly to a boolean setting without converting it. What happens if you do this:
Send [ambiance.salon.status] with value [AmbianceON (tag)] to Dashboard ?
(Make sure you add it as a tag, not as just text)
You can see the data coming in in the Dashboard Studio’s "Data stream explorer:

Or you can just dump the value in a text widget to see what is coming in:

Also, you can probably enable this AmbianceONsetting directly in the Dashboard studio settings. If it is a Homey variable, it should be listed under variables. (Dashboard studio settings in Homey)

[Satoer]

@Amersfoort

This looks like an “anti-bounce” code thingy from 2 months ago.
There is also another variant described below of a button with a local variable. This option, in particular, isn’t that exclusive, though.
Both options worked before 1.8.0, at least.

yes, found the problem already. It was related to the optimalisation I did.

@Amersfoort

What are the prerequisites to see the effect of these spacings? With my News table I can’t see any difference. Are images mandatory to see the effect?

Spacing does not influence text inside tables. I shall change that.

[Amersfoort]

@Satoer

yes, found the problem already.

Nice.
Today must be that day that Jupiter aligns with Mars and the room temperature is exactly 12 degrees, I think…

[Georges_IEGER]

You’re right—the French are often chauvinistic, and on top of that, they rely on translation tools (like DeepL) because they’re terrible at languages

So here’s what’s happening:

1. If I link the homey boolean variable directly to the button’s state, I can clearly see False/True in “Data Stream Explorer,” or in TXT field, but it doesn’t work. The button stays in the “off” state color. It’s very strange !

2. If I use the “special” variable (ambiance.salon.state) I created and assign it directly the value of the homey variable, I get the value ‘x’ or “the checkmark,” and it doesn’t work.

But, as I mentioned in my previous message, if I assign 0 or 1 using the test shown in my screenshot, then it works fine!?!

What do you think ? Can you try using a Homey variable on your end ?

[Amersfoort]

Two boolean values:

• Nachtvolume is an advanced flow boolean variabele, showing as “false” in DS
• Nacht: the same variabele but sent via DS flow card, showing as "× in DS
  
  
  
  So, depending on how a variable is sent to DS, a boolean with the value “false” has 2 different representation forms (“true” probably does too).

A boolean has to be 0/1 or false/true, but not × or ✓ (check) in DS. The flow card should send false or true.

EDIT: Homey Dutch version

[Georges_IEGER]

Sure, you also have the “checkmark” or the “X,” but then what’s the problem? A bug?

And when I directly bind the variable that returns a true/false value, it doesn’t update the button’s state.

[Satoer]

@Georges_IEGER

And when I directly bind the variable that returns a true/false value, it doesn’t update the button’s state.

I shall do some deeper investigation. Maybe it is related to the previous discovered bugs in the test version. Which version are you running Georges? The stable 1.7.4 version or the latest 1.8.1 Test development version?

@Amersfoort

• Nachtvolume is an advanced flow boolean variabele, showing as “false” in DS
• Nacht: the same variabele but sent via DS flow card, showing as "× in DS

That is such a weird bug. Wonder how I we did not noticed that before. Don’t think this is related to the optimalization in the 1.8.1 version. Thanks.

[Amersfoort]

Please try this card and execute it (manually type “true”, usually everything in lowercase):

…and use this BooleanTest variable in the Switch/button

For me it works as expected (try the same for “false”).

Other values than 0/1 and false/true do not work. So I would say that the DS card sending a boolean variable but not 0/1/false/true is wrong.

[Georges_IEGER]

I use 1.7.4 version

cdt,
G.IEGER
Envoyé de mon smartphone

[Satoer]

@Amersfoort

Please try this card and execute it (manually type “true”, usually everything in lowercase):

…and use this BooleanTest variable in the Switch/button

Georges did this already (but 0 and 1 which also works) and confirmed this to be working:

@Georges_IEGER

hanks for your answer

[Satoer]

@Bert_Onraedt

new issue has popped up over here when trying out the Calendar-stuff.

One Google Calender : works fine.

2 Google Calendars, however, crashes dashboard Studio at the moment where the ‘Combined Ical Data’ is sent to the Dashboard.

Overlooked that one sorry. (just noticed this message because I wanted to quote someone). Thanks for reporting. I will look into that. That is a serious issue. I never tested parallel downloading of iCal data. But it should work I think. Have you also tested it using serial loading?

@Satoer

[Georges_IEGER]

Yes, I can confirm that it works if I send “true” instead of 1 and “false” instead of 0 with a card like the one in your example

[Satoer]

@Bert_Onraedt

2 Google Calendars, however, crashes dashboard Studio at the moment where the ‘Combined Ical Data’ is sent to the Dashboard.

I have tried it using your parallel loading method, and that seems to work fine. I used Apple ical calendars though. Have you tried both calendars in a single way also?

[Amersfoort]

@Georges_IEGER

Yes, I can confirm that it works if I send “true” instead of 1 and “false” instead of 0 with a card like the one in your example

So, what is the difference between this and…

@Georges_IEGER

If I link the homey boolean variable directly to the button’s state, I can clearly see False/True in “Data Stream Explorer,” or in TXT field, but it doesn’t work

[Georges_IEGER]

Yes, it’s baffling. Let me reiterate: when I connect the Homey variable directly, the button’s status isn’t updated (even when I add a delay).

When I assign the Homey variable to my DS variable, I get a checkmark or an X, and of course that doesn’t work either.

[Satoer]

@Georges_IEGER I have found the “bug” Turns out that when using a Homey Boolean variable inside an edit box it renders it as ✓ / ⨯… Never expected that. The official way is to implement a droptoken field inside the card, but this only accepts tags, and I want to be able to send anything. In the new version it converts the ✓ / ⨯ to just true / false. I just hope there aren’t any other localisation translations.

But the main thing is, and why no one has ever noticed this before. It should not even be necessary to do this since you can connect variables directly.

@Georges_IEGER

Yes, it’s baffling. Let me reiterate: when I connect the Homey variable directly, the button’s status isn’t updated (even when I add a delay).

I honestly do not understand this. Do you have a domotica light like hue? Can you try to check the on / off capability:

And connect that topic to a state setting of a button:

Now when you turn off the light inside your Homey app, does the switch move with it?

[Georges_IEGER]

Yes, it works with a HUE bulb, just as you asked. The switch moves on its own when I turn the light on or off from the Homey app. And the light turns on or off when I click the switch in DS.

Georges IEGER

[Satoer]

Then I am totally in the dark why connecting boolean variables directly does not work. There are more French users here in this topic. @Yann_Liqueur also made a pretty advanced dashboard, Yann, have you notices any problems like Georges mentioned? A boolean value directly connected to a widget Like a button state, that does not seem to follow the boolean state?

[Satoer]

@Olivier67

No in terms of design that’s not the problem, I see that you have to do everything manually, but the dynamic is to display by clicking on “light” the lights that are on, because otherwise you would have to create 30 lights in terms of design to display only the lights on. it has to be a summary.

There is a specialized Light widget inside dashboard studio, that lets you do exactly that. Add as many lights as you want and control them in a group or individually:

You can directly turn them on and off and when you click on the name a popup shows where you can set the color / temperature and brightness.

But, to be honest, I think the need for controlling individual lights is bad home domotica design. Are you honestly going to configure each of your 30 lights one by one? You be way better of by connecting moods to a button. Just a couple of main moods, like cleaning, evening, romantic, disco, whatever. And connect them directly to a button. I have main moods on my dashboard, and below that localised overriding moods. Like “study light”, that just lights up the three spots above the living room table regardless of the mood elsewhere in the room.