Problem with node

Dario Trione

unread,

Sep 6, 2021, 10:22:58 AM9/6/21

to Unified-RED

Hi, very compliment for the development and the project. I have the problem with button anche another nodes...

1.when I click the button doesn't received a payload output.

2. the alarm table doesn't watch nothing when i trigger a alarm.

I have a question about how i can change the localization (or develop it).

Thank'you very much.

Darryl

unread,

Sep 9, 2021, 7:09:35 AM9/9/21

to Unified-RED

Hi

I have the same problem with the button, no output when the button is pressed

Thanks

Samy Arbid

unread,

Sep 9, 2021, 8:46:04 AM9/9/21

to Unified-RED

Thanks for the feedback. The button issue is a bug and as been resolved in our latest update, 2.0.10.

@dario.trione The alarm console node takes in a very specific payload:

{

severity: string,

name: string,

value: any,

state: boolean,

ackreq: boolean

}

The alarm console node help section has more details about this. If you’re already passing a payload similar to this, can you provide a copy of your flow?

Unfortunately we do not have localization / internationalization implemented yet but as the project grows we will need to develop it. We’re hoping to get help with translations from the open source community.

Dario Trione

unread,

Sep 9, 2021, 4:58:06 PM9/9/21

to Unified-RED

Yes, i have put the "ur_alarm node" and link to "ur_alarm_console" . But in dedicated page doesn't appear nothing

For the localization, if is possible to use a system like node-red.... Is possible for me help you

Darryl

unread,

Sep 10, 2021, 2:58:28 AM9/10/21

to Unified-RED

Hi

I have tried to get the alarm and alarm console to work with a simple flow. I assumed that the alarm node would output a payload in the correct format for the alarm console node

1.) The alarm node outputs a payload similar to the example but the name property is undefined

2.) I have added a change node to add the name property

3.) I have added a topic

4.) I have not altered the Topic Filter in the console node, I assume this is regex to cover most common use.

My simple example flow is below

Thanks

[

{

"id": "963c8c783e91c84a",

"type": "tab",

"label": "Flow 2",

"disabled": false,

"info": ""

},

{

"id": "ccb4e8f31b1bf75f",

"type": "inject",

"z": "963c8c783e91c84a",

"name": "",

"props": [

{

"p": "payload"

},

{

"p": "topic",

"vt": "str"

}

],

"repeat": "",

"crontab": "",

"once": false,

"onceDelay": 0.1,

"topic": "",

"payload": "{\"severity\":\"critical\",\"name\":\"Test1\",\"value\":65,\"state\":true,\"ackreq\":true}",

"payloadType": "json",

"x": 250,

"y": 120,

"wires": [

[

"4ecb532d70f512d0"

]

},

{

"id": "4ecb532d70f512d0",

"type": "ur_alarm_console",

"z": "963c8c783e91c84a",

"name": "",

"topic": "[\"glp/0/+/fb/alarm/#\"]",

"topicType": "json",

"severitycritical": true,

"severityalert": true,

"severitywarning": true,

"severityinfo": true,

"x": 440,

"y": 120,

"wires": [

[

"eb5df97615e9483b"

]

},

{

"id": "eb5df97615e9483b",

"type": "debug",

"z": "963c8c783e91c84a",

"name": "",

"active": true,

"tosidebar": true,

"console": false,

"tostatus": false,

"complete": "false",

"statusVal": "",

"statusType": "auto",

"x": 670,

"y": 120,

"wires": []

},

{

"id": "8bdd4c9cc72fdb47",

"type": "inject",

"z": "963c8c783e91c84a",

"name": "",

"props": [

{

"p": "payload"

},

{

"p": "topic",

"vt": "str"

}

],

"repeat": "",

"crontab": "",

"once": false,

"onceDelay": 0.1,

"topic": "",

"payload": "1",

"payloadType": "num",

"x": 230,

"y": 240,

"wires": [

[

"c2c9b9cfa60aa38e"

]

},

{

"id": "7c67fb7870e23d58",

"type": "inject",

"z": "963c8c783e91c84a",

"name": "",

"props": [

{

"p": "payload"

},

{

"p": "topic",

"vt": "str"

},

{

"p": "payload.name",

"v": "Test1",

"vt": "str"

}

],

"repeat": "",

"crontab": "",

"once": false,

"onceDelay": 0.1,

"topic": "Temperature1",

"payload": "65",

"payloadType": "num",

"x": 240,

"y": 300,

"wires": [

[

"c2c9b9cfa60aa38e",

"dc3cad8123e072db"

]

},

{

"id": "c2c9b9cfa60aa38e",

"type": "ur_alarm",

"z": "963c8c783e91c84a",

"name": "",

"property": "payload",

"propertyType": "msg",

"delayon": "5",

"delayoff": "5",

"rules": {

"critical": [

{

"t": "gt",

"v": "10",

"vt": "num"

}

],

"alert": [

{

"t": "eq",

"v": "",

"vt": "str"

}

],

"warning": [],

"info": []

},

"checkall": "true",

"ackreq": true,

"x": 470,

"y": 260,

"wires": [

[

"b9be55522edb0ddf",

"e972ff93164cf014"

]

},

{

"id": "b9be55522edb0ddf",

"type": "change",

"z": "963c8c783e91c84a",

"name": "",

"rules": [

{

"t": "set",

"p": "payload.name",

"pt": "msg",

"to": "Test1",

"tot": "str"

}

],

"action": "",

"property": "",

"from": "",

"to": "",

"reg": false,

"x": 690,

"y": 220,

"wires": [

[

"17fd0c8a4b33734a",

"4ecb532d70f512d0"

]

},

{

"id": "dc3cad8123e072db",

"type": "debug",

"z": "963c8c783e91c84a",

"name": "",

"active": true,

"tosidebar": true,

"console": false,

"tostatus": false,

"complete": "false",

"statusVal": "",

"statusType": "auto",

"x": 580,

"y": 360,

"wires": []

},

{

"id": "17fd0c8a4b33734a",

"type": "debug",

"z": "963c8c783e91c84a",

"name": "",

"active": true,

"tosidebar": true,

"console": false,

"tostatus": false,

"complete": "false",

"statusVal": "",

"statusType": "auto",

"x": 960,

"y": 220,

"wires": []

},

{

"id": "e972ff93164cf014",

"type": "debug",

"z": "963c8c783e91c84a",

"name": "",

"active": true,

"tosidebar": true,

"console": false,

"tostatus": false,

"complete": "false",

"statusVal": "",

"statusType": "auto",

"x": 760,

"y": 280,

"wires": []

}

]

Samy Arbid

unread,

Sep 10, 2021, 8:48:40 AM9/10/21

to Unified-RED

@darryl.peacock the primary issue is that your topics do not match the the alarm console filter, therefore the alarm console is ignoring the messages. Please make the following changes and it should work:

1. In Alarm Console, change Topic Filter to a string type and set it to “#”. The hash symbol is MQTT’s wildcard character.

2. In the Inject node that is connected directly into the Alarm Console, please set the topic to something, e.g. “test2”.

3. In the Inject payload=1 node, set the topic to “Temperature1”.

Also, regarding the Alarm node name property, it should be set within the Alarm node. If you set it there, you can remove the change node.

Samy Arbid

unread,

Sep 10, 2021, 9:01:42 AM9/10/21

to Unified-RED

@dario.trione yes, this is an open source project so we’re always open to help from the community. To get started you’ll need to clone the GitHub repo. Our contribution guidelines can be found here: https://github.com/waccit/unified-red/blob/master/CONTRIBUTING.md

Also, here’s an updated version of @darryl.peacock's flow. Give it a shot to see how alarms can be used:

[{"id":"963c8c783e91c84a","type":"tab","label":"Flow 2","disabled":false,"info":""},{"id":"ccb4e8f31b1bf75f","type":"inject","z":"963c8c783e91c84a","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"Inject","payload":"{\"severity\":\"critical\",\"name\":\"Test1\",\"value\":65,\"state\":true,\"ackreq\":true}","payloadType":"json","x":210,"y":140,"wires":[["4ecb532d70f512d0"]]},{"id":"4ecb532d70f512d0","type":"ur_alarm_console","z":"963c8c783e91c84a","name":"","topic":"#","topicType":"str","severitycritical":true,"severityalert":true,"severitywarning":true,"severityinfo":true,"x":620,"y":140,"wires":[[]]},{"id":"8bdd4c9cc72fdb47","type":"inject","z":"963c8c783e91c84a","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"Temperature1","payload":"1","payloadType":"num","x":180,"y":200,"wires":[["c2c9b9cfa60aa38e"]]},{"id":"7c67fb7870e23d58","type":"inject","z":"963c8c783e91c84a","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"},{"p":"payload.name","v":"Test1","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"Temperature1","payload":"65","payloadType":"num","x":180,"y":240,"wires":[["c2c9b9cfa60aa38e"]]},{"id":"c2c9b9cfa60aa38e","type":"ur_alarm","z":"963c8c783e91c84a","name":"Test1","property":"payload","propertyType":"msg","delayon":"5","delayoff":"5","rules":{"critical":[{"t":"gt","v":"10","vt":"num"}],"alert":[{"t":"eq","v":"","vt":"str"}],"warning":[],"info":[]},"checkall":"true","ackreq":true,"x":410,"y":220,"wires":[["4ecb532d70f512d0"]]}]

Darryl

unread,

Sep 11, 2021, 12:18:43 PM9/11/21

to Unified-RED

Thank you for the support, the example works fine. Could I suggest some examples similar to this so that new users can get started with the other nodes.

Samy Arbid

unread,

Sep 11, 2021, 1:15:10 PM9/11/21

to Unified-RED

In addition to developing Unified-RED, we design and install control systems with it so we can provide examples from real-world projects. However because we use Dialog’s SmartServer IoT very heavily, the examples will be SmartServer IoT oriented. We’re planning to eventually make a series of training video that should be helpful to new users. It will cover general use cases as well as SmartServer IoT applications.

Attached is a screenshot of an air handler page and flow from a recent project using the SmartServer IoT. This flow is a good example of how to use MQTT, animation, table, form, and schedule nodes. Be sure to also have a look at the help section for each node. There’s a lot good information buried in there. I hope this helps.

Screen Shot 2021-09-11 at 9.55.22 AM.png

flows.json

Darryl

unread,

Sep 12, 2021, 11:20:40 AM9/12/21

to Unified-RED

Thanks for the examples. The possibilities of this are great! I will spend some time going through the help for each node and try to adapt to other hardware

Stephen Schmidt

unread,

Jan 6, 2023, 5:24:58 PM1/6/23

to Unified-RED

Just started playing with Unified-Red. Looks very interesting.

Thanks for the example above. But, I am still a little confused. Loading this sketch, I can click the inject node and it will produce the Message

"Duplicate alarm for Inject". It will continue to output that message every time I click the inject node.

The Node Temperature1:65 will produce the message in the debug console "Duplicate alarm for Temperature1" Only Once. Regardless of how many times I click it. Does it need to be reset? How would you reset it? Is there a setting to allow it to produce the alarm with each press?

I had been looking at this as I have a flow that produce an Info Alarm each time I change speed (value changes). Condition used is != previous value. It, like the example will only produce a single info alarm with the first speed change. Subsequent changes have no effect.

How can I produce the notification with each change?

It may be that I am simply missing something.

Thanks!

Samy Arbid

unread,

Feb 13, 2023, 10:13:43 AM2/13/23

to Unified-RED

Hi Stephen,

There a couple of things to confirm.

First, confirm if the alarm requires acknowledgement. If it does, another alarm from the same source will be discarded unless the alarm is acknowledged.

Second, if the alarm does not require acknowledgement or if the alarm has been acknowledged, confirm that when you send a value that evaluates false on all alarm conditions that the alarm state clears.

Reply all

Reply to author

Forward