Hi @inelint
Following the advice of what @ega mentioned, and to give and example of how you could do it. One way would be to use the device stream node to read from a device resource in a set interval as long as the device is connected. Then with a server event node subscribed to device disconnects you could handle the alarms.
Another way to handle the alarms would be to use the Thinger.io alarms feature. There is a little more information in this link:
However, we understand that the interface from past version regarding error codes and message has changed to be more in line with the way Node-RED expects them to be handled. In this case, error messages are now handled with catch nodes, to which we will add the status code (not currently returned) like so:
As you can see on error the message is printed by the debug catch node, breaking the device read flow on error.
Will try to handle the two bugs you reported today and we’ll let you know when the new version is available