Alarms management using node-red-contrib-xstate-machine

I'm trying to use the xstate node for managing alarm lifecycles. It's really good for handling an individual alarm, but I'm wondering whether I can use this node for multiple alarms - each of the alarms will have the same lifecycle ( as configured into xstate ) but each individual alarm could be in a different state at any time.

So - do I need an xstate node per alarm ? ( that is bad if I have 100 alarms !! ) or can I parameterise a single xstate node ?

Any ideas appreciated !
Gav

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.