If this has been solved before, please point me in the right direction.
Shelly has once turned the output off (slått av) by itself, when it should have been on.
The state of it was on and should have been on until my flow set’s it to off.
This could be a problem for me and I need to understand why this happened.
You can see the rest of the time it is acting as it should and does what the flow says.
Why is this happening and is there a way to be informed if a device takes it’s own decisions?
What is it controlling/attached to?
I have 3 shelly 1 attached to roller door motors, they are set to turn off after 0.5 seconds, Button type Detached switch. Power on Default is set to Off. There is a lot in Shelly to be got right and it sounds like you may not have yours set to the appropriate button type
To “solve” it, you can counter it’s action by using the Device Capabilities App → Recieve Insights from 0 minutes ago.
It will show you the user/client/app that switches it on/off.
If that is the app itself, switch it back.
It is attached to a control circuit for a charger. The flow has a time limit so the output is only active during those hours. What button type do you think I should use?
Im not sure i understand wat you mean by that.
But here is an example:
You can read this flow through the Templates in the DC App Settings → Templates.
(Press refresh to show, i just created the Template).
Well, you can use the Watch trigger (with the tokens already there from the insights) or use the insights.
I personally would use the normal device trigger card and then recieve the insights.
Not sure why i still prefer that, the watch works correct. But i like as least in the way as possible i guess.
But take a look at the example.
I think you need the token Client, but not sure with Shelly, it could be User sometimes.
Might also be worth hour while going to Shelly facebook support pages, although I really don’t like that they use facebook as a support forum and ask there. They were able to help me figure out why my garage door was opening randomly