Set mode without trigger fails

[Jan Hjørdie]

When I try use the set mode, and no trigger, it’s actually fire the trigger

‌

[arie]

Ill take a look at it.

[Jan Hjørdie]

Thanks

[arie]

Isn’t it just that you need the other trigger card?

When you use

it will not get triggered by:

‌

[Jan Hjørdie]

Sorry, I can’t understand the text on your cards.

I have another trigger, ex. my heatpump, when it is turned on. Then I need to set my virtual switch to on, but without trigger the switch.
So that’s why I use the card “set mode on, no trigger”

But when I use that card, it trigger the trigger

[arie]

There are two “duplicated” When cards:

When Turned On. Will always trigger.

When Modus turned On, will only trigger when not using your card.

‌

The same goes for the Off.

‌

So, you need to use the other When cards.

‌

          "en": "Mode is on",
          "nl": "Modus wordt aangezet",
          "de": "Modus ist anheschaltet",
          "no": "Modus er på"

‌

‌

and off

          "en": "Mode is off",
          "nl": "Modus wordt uitgezet",
          "de": "Modus is ausgeschaltet",
          "no": "Modus er av"

‌

‌

‌

‌

[Jan Hjørdie]

I’m using the “Then… Card”

Maybe I’m reading the cards wrong. But based on the title, I was sure I was able to set a mode without the trigger the trigger

‌

‌

‌

[arie]

It’s not about the Then Card, but the When card you use somewhere.

You have a flow that is triggered right?

Show me that Whenflowcard.

[Jan Hjørdie]

‌

‌

[arie]

Okay, if the Then cards are activated? What happends then?

i thought that there than was another flow that was started?

[Jan Hjørdie]

When the no trigger Then cards is activated, they actually fire the trigger.
And the card should only set the variable. Nothing else

[arie]

“they actually fire the trigger.”

Which trigger? Show me the trigger that get’s triggered please.

[Jan Hjørdie]

I only have one switch. When I use the When cards in the lower right, they trigger the switch. So the “no trigger” do actually trigger

‌

‌

[arie]

Card number 1, right-click-replace-with Mode turned On.

Card number 2, right-click-replace-with Mode turned Off.

‌

(LEFT cards, not the right Then cards)

[Jan Hjørdie]

I think you are misunderstand my flow

When my heatpump is idle, I want the switch’s mode to be set to off. So I can see the disabled switch on my dashboard that the heat is off.

Since I use ex. “Set mode on, no trigger” Then card, it should NOT trigger the “Turned on” When card.

That should only be triggered if I used the “Turn on” Then card

‌

[arie]

Please, change your WHEN CARDS, the Is Turned On card is a Athom/Homey card i cannot control, that is why there are other WHEN Cards. See my image above.

Replace your WHEN/IF cards please.

‌

[arie]

1st card: Is Turned On

2ndcard: Is Turned Off

[arie]

Replace them both with Mode is turned On/Off.

It does the exact same thing, only it will not be triggered by your flowcards.

[Jan Hjørdie]

Well, I actually need 1 and 2 to be triggered individual. Not from the “no trigger” cards, but I have an another flow, where I use the “Turn on” card, and then I can’t trigger the “Turned On” card.

I’m a developer, and been fullstack deveioper for +20 years, and don’t understand some of the cards in your great app.
I have used Homey for 2 years, and built many flows. It’s only your “no trigger” card that don’t make any sense.

But let’s just leave it here. I will find another way to do my events

Thanks for your help

Thanks
Jan

[arie]

Hey Jan,

‌

I agree, i don think the card makes much sence perse, but, not sure if you know this, i only took over the maintanaince of this app a few weeks ago.

I didn’t design it like this ;)

You want a really good virtual device, take a look at the Advanced Virtual Devices from the Device Capabilities App.

‌

But, back to your card issue:

I'' explain it in another way.

The “Turned On” and “Turned Off” cards are default Homey/Athom cards that are automaticly added by Athom/Homey whenever a device has a OnOff capability.
These two Homey cards are ALWAYS triggered when the capabilityvalue changes. So, howevery i/you would change the value (through the device itself or the flowcards) these default-athom-cards-that-are-out-of-an-app-developer-control will be triggered by Athom/Homey.

‌

Sorry about that ;)

‌

That is why there are two more customly made by the previous developer, flowcards that you can use as When cards.

They will trigger when you push the button on the device and the will also(!) be triggered when you use the (Again default Homey/Athom flowcards) THEN cards “Turn On”.

The “Turn On/Off” default Athom/Homey flowcards will trigger the “Mode turned On” card!

The “Turn Modus On/Off, no trigger” customcard will not trigger the “Mode turned On” card. ← THIS is what you want.

The “Turn On/Off” default Athom/Homey flowcards will trigger the default “Turned On” card!

The “Turn Modus On/Off, no trigger” customcard will trigger the “Turned On” card.

‌

[arie]

‌

This is based on this flow, sorry for dutch: Aangezet means turned on, Uitgezet means turned Off:

‌