Flow only starts when triggered manually

Does anybody have an idea as to why one of my flows only starts when triggerede manually? My other other flows work as intended, then a trigger event occurs, the flow is triggered and runs. But my flow I use to start charging my EV will only start when I test the flow. And then it runs perfectly.

I receiver no errors or alerts that can point me in the direction of the problem.

Apps used in the flow: Zaptec and BilligKWH (akin to PBTH).

Trigger event is when lowest price for charging X hours occurs during timeframe.

Everything is updated.

I’m pretty sure that you need to provide a screenshot of the flow, or we are all just guessing

I’m pretty sure you’re absolutely right. I’ve updated my post. Thanks.

You say that you can trigger it manually.
So it’s seems like the tag it not trigger in the beginning

Really don’t know.
The flow looks ok, but are the tag from the app ok? I have never used " Zaptec or BilligKWH"
Also add a notification to timeline in case of error from every flow.

I don’t really understand the first step in the flow, perhaps because I cannot translate it due to my lack of knowledge of the language :sweat_smile: Could you please tell what the steps says ?

Because if you test it manually the flow works we have to find out if the information this flows get is correct.

Could you please add, as @Mike_Nono also mentioned, a notification message (to timeline or message to device) with a clear description after each step. Also add a messages when a step fails. This way you can find out on which step the flow stops.

Also I would suggest to add the variable “Ladetid_Forventet” in the message so you can see the value the flows is working with

The first step says “The cheapest timeframe of [variable] hours between 00:00 and 17:00 starts”.

I will try to add a notification, to see if I get any errors.

I will report back when my EV has to charge again :sweat_smile:

Ok, and what could be the value of this variable and how/by whois this variable been set?

It could be that I am in need of more coffee, but I can’t get it clear for me how this trigger works :upside_down_face:

Well, when a flow works fine when testing it (accirding to TS), only the trigger is the point of failure :wink:
(just meant as information, not smartassing)

@Grumpy

Not all trigger cards take variables as value… this one probably is one of those.

Please test again with a manually entered value.

OR -
the variable value isn’t an ‘integer’ (zero digit number), if so, the card doesn’t recognise it as valid number and doesn’t work.

Unfortunately we can’t test triggercards “on the spot”.

Fair enough. I do also think the issue is in this step, therefore it would be nice to know via a message (timeline or otherwise) if this step works and what the value is of the variable at that point (which could help understanding the issue based on your second half of your previous comment :smile: )

that being said, I do think it is a good way of troubleshooting to have a message after each step, but again perhaps for this case it is a bit much

Thank you very much for your suggestion that the trigger card doesn’t take variables as value. Entering a value fixed the problem. Not as smart as I would like.

Cards should prevent one from entering variables, if they don’t support it.

Great to read you found the solution!

I agree, when it is not allowed to use, it should not be possible to select it.

Perhaps you can give the owner of the app feedback about this. Maybe they can change it in the future or explain why it can’t be changed.

I think this might be more of a Homey OS issue than an app issue. The same applies to many more apps. The strange thing is that sometimes you can use a tag/variable as a parameter and sometimes you cannot, though the tag/variable icon is shown :man_shrugging:.

That could be the case of course, I have no idea what the root cause of this is.

If the app builder cannot fix this, perhaps a request to Athom could be the next step.

Because whatever the cause may be, I still think you should only be able to select the options that should work.