So to get back on this, I have no idea where this is coming from. It works here and the crash seems to be caused by an impossible situation where the app does receive arguments back from flow cards. I’ll investigate more…
In the meantime, version 1.18 is now finally released with milliseconds as a timing unit and the ability to toggle states in the set states widget.
Hi @BasMilius. Love the app and have been weaving it into more and more flows as I adjust things and find this is the easiest and neatest way to achieve something. Great work!
One minor feature request: adjust the “Label X changed” trigger flow card so that it doesn’t fire when the Label is cleared (and add a new trigger flow card “Label X cleared”).
Use case: I have speakers in most rooms in my house and an advanced flow which I use to make announcements. I currently have a text variable set up for each speaker and an announcement flow with lots of mini flows like this:
By setting the variable to NONE each time and then testing it’s not exactly NONE when the trigger fires, it still works when the announcement I want to make happens to be the same as the previous one I made to that speaker.
I want to change this to use flowbits labels so that I don’t have lots of variables cluttering up my variables list for this given I never need to refer to these values outside of flows. It would be even neater if I didn’t have to do the test for NONE. I could just trigger using the (adjusted) “Label X changed” card then use the “Clear label X” card when the announcement is done.
Of course this one example is relatively minor and there’s an easy work-around. But I actually find this quite a common design pattern which I use for lots of things so I figured it might be a good use case for flowbits.
@Jonathan_Draper Thanks for liking FlowBits! 
I get what you’re asking and I want to ask if you could create a feature request over at Github. One problem I have with the request is that existing flows that use the “Label X changed” card may not expect this behavior, but I agree with your suggestion. I think the way forward would be to deprecate the existing card and create a v2 version that works like you’re describing, that way existing flows will work as before.
When you created the feature request over at Github, I’ll let Copilot do the work to see how far it gets.
