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).
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 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
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 )
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.
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 .