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

**URL:** <https://discourse.nodered.org/t/alarms-management-using-node-red-contrib-xstate-machine/90309>\
**Category:** General\
**Created:** [21 August 2024 10:11 UTC](https://discourse.nodered.org/t/alarms-management-using-node-red-contrib-xstate-machine/90309 "2024-08-21T10:11:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vtgav](https://avatars.discourse-cdn.com/v4/letter/v/f0a364/32.png) [@vtgav](https://discourse.nodered.org/u/vtgav)\
**Post date:** [21 August 2024 10:11 UTC](https://discourse.nodered.org/t/alarms-management-using-node-red-contrib-xstate-machine/90309/1 "2024-08-21T10:11:39Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [19 November 2024 10:12 UTC](https://discourse.nodered.org/t/alarms-management-using-node-red-contrib-xstate-machine/90309/2 "2024-11-19T10:12:06Z")

</div>

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