you should use different triggers and action cards then you are doing now (probably).
Trigger (WHEN): “When button ...” and select “has changed”.
Action (THEN): “Set [Button] to [yes/no] and [Nothing else]”. that won’t start the used Trigger
1 Like
Maybe I don’t understand your solution completely. When pressing the button to on or off, the status changes automatically. It’s not necessary to change it manually, as you in your “Then” statement?
To my opinion, your solution doesn’t solve my problem either. If I only wanted to use the button to put the lights on and off, then it works very easy. Its status changes to on and off after each time I press it. And the flows are executed.
But I only want to change its status manually. When I do so using your solution after Then, the lights still go on ( status to yes) and off (status to no).
Do I overlook something?
Please show a printscreen of your flow with the trigger that reacts to the button being pushed?
Becuase that one it probably the default homey card, and you need the special AVD when card.
Ah I got you wrong then 
So you want a status ‘copy’?
Like, when a device is turned on/off, your switch has to turn on/off as well?
I guess @Caseda was right, Roger. But it can be quite complex sometimes.
Take a look at this example. The flow(s) with ‘this switch has turned on’ will not trigger when you turn the switch on and off with “and nothing else” option.
→ only if you manually operate the switch, the flow(s) with ‘this switch has turned on’ will trigger.
If this is not what you’re looking for, I just got you wrong again I guess 
1 Like
As I wrote already, I created a really simple ADC. Just a sensor to show the status of a kind of door sensor (link, sorry only in German language). But I changed the settings of the sensor every now and then and tried things out. And I did a restart of the app, if I remember correctly.
1 Like
Hi @Roger_Gorissen,
as Arie already wrote, please post a screenshot of your flow.
I guess the problem is that you just programmed one way. And that is only from the point of view of the switch, and not from the point of view of the lamp(s).
The way back is probably missing. If at a certain time the x lamps are switched off, then the button must also be switched off.
Switch button on → switch lamp on
Switch button off → switch lamp off
Lamp is switched on (e.g. by time) → button has also be switched on
Lamp is switched off (e.g. by time) → button has also be switched off
However, a generell problem is that you switch several lamps. What happens if only one lamp is switched off/on (e.g. by a time setting or manually), but other lamps remain off/on?
This is a sample where you can control up to 5 dimmable lights, made by @Arie_J_Godschalk. I guess something similar has to be created for your case.
1 Like
You describe it exactly as I mean. Switching lights on using the button is no problem. Lights react as supposed.
Problem arises when lights are switched off by another cause.
The status off command that @Peter_Kawa shows in his flows is exactly how I used it in the flow that switch off the lights on f.e. a fixed time. But strangely, the flow that is connected to the button is also activated, despite the “and nothing else”.
Even when I make a test flow: WHEN this flow is activated THEN status on and nothing else, then the lights are switched on, caused by the flow connected to the button. Seems like something is not working properly.
I don’t understand why I have to share the flow of the trigger when the button is being pushed? That part works okay.
I make a new button and see if that one works as it should be. I’ll take your suggestions and advice into account.
Keep you informed.
1 Like
Yep, once again “confirming” my feeling: somehow the athom-api is connected and doesn’t clear data correctly.
So athom-api apps will then (if so) be influenced by each other.
Because it looks like you use the triggercard from Homey itself: When xxx turned on.
That one will always trigger!
Even with the custom flowcard with “nothing else”.
As trigger, you need the custom AVD triggercard “when xxx is set/changed/pushed”.
That one will not be triggered by the NothingElse card.
Crap, I didn’t know that either.
When I tested my example flow, no timeline msgs appeared.
But the cause was another “fine” feature of Homey: rate limited😑
1 Like
Flow when activated:
Flow when de-activated:
I think I used the right trigger, the one from DeviceCapabilities.
The flow that is started by pushing the button is this one. This is the same flow that starts in the morning to turn on the X-mas lights at 06:30. That’s why I put in the set status at the end of it:
No, sorry, both (de)activating flows use the default Homey Flow cards, that are created because of the Create Flow Cards option.
The device also has a few custom flowcard triggers, al starting with “When” (in AF, in normal flows they all end in set/pushed, and are located as first six flowcards, above al other).
You need that one for the button.
You will only need one (de)activate flow with the correct When card. Then check the value-tag from that flowcard for true or false (logic cards).
Thanks! Didn’t know that, wasn’t aware of it. Now I see and understand what you mean. I created a new button to test, without creating flowcards. Then you can see the difference.
Back to my problem. IT’S BEEN SOLVED 
.
Thanks! That was just my beginning with this beautiful app. Now I have to find my way in its enormous possibilities.
3 Likes
Yeah, i know these different flowcards can be a bit complicated.
But the option Create Flow Cards: it makes the field, like a OnOff, the real deal.
This is needed sometimes, f.i. for Google Home.
But it also creates default Homey flowcards.
Those can be “nice to have” sometimes, but are not controlled by an app developer: whenever and however a field (capability) value changes, default flowcards will be triggered.
2 Likes
Hi,
I am struggling with restarting the app after importing a new icon, .svg.
“Restart the app” , then timeout after 3000ms.
And secondly, how can I get for example degree Celsius (symbol: °C) when making my own app and creating different values that will show temperature.
Try to disable the app and enable it again?
Not sure what you mean here, but have a look at the developer page, it has a lot of info on how to handle Celcius.
I made it work though:
1 Like
