Update
The below flowcard has been bugfixed
- When you set a new/first flowcard for a device.capability, the duration would be based on the current moment. It will now check when the capability of the device was set, and if the condition is true, then the moment of triggering would be based on the moment the capability was last set.
Meaning: If you set a flowcard for a duration for f.i. a minute, and the capability meets the condition and was last set more then one minute ago, the trigger will be activated directly after saving the flow. - When setting the card for the first time for a new device and/or capability, it would not always validate the condition correct and thus not be set correctly and would only get active after the capability changed.
- When a flowcard would be deleted (and there was no other flowcard for that device.capability, and a new flowcard would be set for the same device.capability, the moment when the card would be triggered would be wrong.
- When the app was updated or restarted, and any of the flowcards would be updated (meaning saved or flow en-/disabled), it could be wrongly triggered or not triggered.
Update to 2.14.0 to resolve these issues.
