Thanks seems to work great! Maybe one thing, would it be possible to allow for decimal values for the duration? For my dimming example 1 second feels a bit slow and I would like to be able to fire the timer every 0.5 seconds.
@BasMilius I am thinking about using this app to monitor whether a device is reporting or not.
I have two different approaches:
- Every time the device reports (e.g. temperature) is sets a State in a Set. Once a day I check the Set if every State is set. Or even; if not all states active for the Set, notify.
- Restart a timer everytime the device reports. If timer finishes notify.
What do you think of my ideas? Are any (both) of them heavy on Homey?
Is restarting a timer every second for say 20 devices (i.e. 20 timers) too heavy?
Why I want to do this is due to many devices should report their battery level but fails to do so.
@Anders_Gregow Hmm, I think the sets feature is more suitable for this case and you can then at a given interval check each state or the entire set. I did test FlowBits with around 50 timers, which went ok, but the app also received a few timer related updates since then. I should test it again 
Some background information about how timers are implemented:
- The app finds your timers and calculates when certain updates should happen, this happens at startup and when a timer updates.
- The update that should happen first (or multiple) is scheduled, so the app does not keep track of later updates at this point.
- Set timer for 10 seconds.
- Timer reaches 5 seconds. ← This update is scheduled.
- Timer finishes. ← This update is not yet scheduled.
Timers have one scheduler, so it does not matter if you have 1 or 10 timers, there’s still one scheduled update.
Hi, the app-support is great, but before I start changing all my flows I have an honest question.
Why should I use this app to keep certain states. I now have boolean variables defined like:
- Alarm Enabled
- Alarm Enabled Partially
- Alarm Enabled Total
- ItIsLight
- ItIsDark
I am very curious.
Kind regards,
Peter.
I had the same question recently. See my post above and the developer’s response.
1 Like
I think Sets are better for this case too.
Is “Set State for a duration” implemented the same way as for timers?
I asked myself the same question. Although it does not always make sense, I would say there are use cases when Flowbits has an added value:
I would say:
- Use Flags when you want to visualize and/or update the boolean value from a dashboard widget
- Use Sets when you want to
- Check if one of multiple boolean variable is set
- Allow only one of multiple boolean variables to be set
1 Like
@Anders_Gregow Yes, sets also has a single scheduler for the entire feature
@Peter_Hendrix Valid question, and some of the features are doable without FlowBits. The Flags feature is basically just variables with some easy flow cards and two widgets. I have a cleaning flag that my partner can activate from our wall-mounted iPad, which she finds easier to do. Explaining what “boolean variables” are was a bit too much
But for your alarm variables, that might work well with the Sets feature of the app. Every alarm is a state in a generalized set. You can check if the set is inactive, partially active or fully active. That could potentially make your flows smaller and easier to understand.
1 Like
@staeff Sorry, forgot to reply to you! I think it should be possible, but I think that we need to set a minimum of for example 0,1 second. There are a lot of cards that have the duration + unit combo. Need to test with other features also…
Edit: I just saw your pull request, nice, I’ll test tomorrow!
Version 1.17.0 (and .1) is now live with repeating timers.
Hi @BasMilius, I’ve been following the development of this app for quite some time and have already replaced a few of my flows with some FlowBits functions.
What I’m missing is a When… flow card for the “Sequence” function, like the one that exists for the built-in logic flow cards: Sequence “name” has changed
Would it be possible to add this flow card?
@DirkG Yeah sure, can you create an issue on GitHub?
1 Like
Of course. Thanks in advance!
1 Like
FlowBits 1.18.0
- This update adds milliseconds as a timing unit for everything time-related, thanks @staeff!
- The Set states widget now has an opt-in setting to allow toggling states from the widget.
1 Like
Hi @BasMilius
Again, I love your app, use it for a lot of things 
Still, for some reason I don’t get sliders to work. I’m having 2 receivers at home controlled via HEOS which have a volume range from 0-100. I tried setting up the flows to control the receivers but i’m getting stuck.
You have any advice if these are correctly build?
Hope you (or anyone else) can point me in the right direction
Your flow will only finish when the volume is exactly 20%. Try losing the AND-cards and use the volume-tag in the THEN-card ‘stel slider volume Denon in op -volume-tag-Denon-‘
1 Like
Mind that percentage values in tags (in Logica cards) almost always work with a range of 0 - 1 instead of 0 - 100.
Using 20 is out of range.
1 Like
Thank you for the suggestions @Peter_Kawa and @Wim_Post . I’ll look into it 
1 Like
Just a heads up for everyone running FlowBits on their Homey running experimental release 12.13.0-rc.3; I receive a lot of crash reports since this update, something probably changed internally and I’m going to investigate tonight. All crash reports are coming from flow cards that have autocomplete in them.
2 Likes
