Hi, Thx a lot for node-red-contrib-ctrlx-automation Node-RED nodes. I develop currently on ctrlX core a monitoring app (using node-red) for DC drives on a customer machine. The architecture is so that the ctrlX core is added to the machine config within its subnet and it reads DL data from drives (e.g. data available via Drive Connect App) and writes them on a db reachable via second eth in IT/office network. We know that there is a Device Bridge or IoT Gateway (not on ctrlX) or we can develop e.g., python app (probably we also do so) in a form of a snap but for now we wanted to do this using node-red and already existing solutions which can be also shown to the customer and potentially developed by him internally. I have 2 topics that maybe you would like to address with the next releases (I use currently version: 1.8.19) of the nodes: 1) Do you think that this would be a potential benefit if for the DL subscribe node we would have the property "path" as optional input e.g. msg.path (used to set the path to the Data Layer node which shall be subscribed to.) In a form of an array probably? Currently I would be happy to use it cause in my projects now I do SSE calls to REST/API interface from node-red where I have a full control what and when is subscribed. I had to ditch the subscribe node when I started to have error described in issue 2 Using the DL subscription node I have to (but I would prefer not) to hard code the DL path in the node-configuration via node-red GUI. I would prefer to send it with some payload and be able to catch potential problems afterwards. BTW: I understand that one DL subscribe node on development dashboard of node-red makes one SSE call to the ctrlX DL with a specific keepalive and subscriptions’ times. But at least sending different path (e.g. as array of DL paths) in msg.path to subscribe node would be cool. 2) It happens that when the machine which includes the drives is down/restarted - the corresponding DL paths are not existing anymore (or the DL paths were deleted automatically or due app failure) and ctrlX is still online we got error on the DL subscription node. It is OK I can catch it and at least I am aware. Do you think that adding also e.g. msg.restart = true/false or msg.start =true/false msg.stop =true/false as input options would be a benefit in this case (especially having msg.path from issue 1 implemented) ? In general: I want to subscribe to DL but only after some preparation of the ctrlX DL for this operation - e.g. drives are up, everything is checked and ready to start subscription. All the best, Kookoolinoo
... View more
