Firmware 1.62

[Harald Rupp]

Hi All,

thanks for Firmware 1.62 which allows now to organize Nodes into Groups.

1. I just wanted to ask, if in a next Version this Group Membership could be also retrieved via the RestAPI?

Within the last FW Update, it was possible to add some Tags for every Node like Serial, Product ID a.s.o which was very helpful to support a automated way to create and sync a little Database in our SCADA System, because those Tags could be retrieved via the RestAPI!

2. Next Question, is it planned to have some Configruation Item on the AEP lets call it “Action URL”, which is been fired on a external System (to start an Pull Request) when a Node has been updated his State, this will help us to reduce Traffic and not running unneeded queries when nothing has been changed in the Lora Node Network.

Thanks for some Feedback

Harald

[Jason Reiss]

1. Everything seen in the UI is available through the RestAPI.

POST|GET|DELETE /api/lora/groups

2. Do you mean uplink/downlink from the end-device actions? Anything changing in the end-device from the network server will be sent in a downlink. Anything changed at the end-device will be seen in an uplink.

[Harald Rupp]

Hi Jason,

1. This is working for me – Many Thanks!

2. Hmmm…. i think its not related to uplink/downlink. With a NodeRed App, when a Lora Package hits the AEP i could simple trigger a EXTERNAL WebService to pull some seconds later all informations from remote.

We just need some Hook or Semaphor like in a File System, when a File is been retrieved then the remote System will start loading and parsing the file. In this case the AEP should simple Trigger a remote WebAPI, lets say is calls a function with.. hey there is something new, start pulling now.

At the moment with our Broker we call every 1 Minute the AEP to sync, in the night times we have less updates then over the Day, so it would be better when we could use a Trigger in the AEP, which triggers a external device or alert system with “Hey there is something new.

Hopefully this becomes more clear.

Many Thanks

Harald

[Jason Reiss]

What is the origin of the lora package?

[Harald Rupp]

Hi Jason,

the origin of the Lora Packet comes from Nodes hosted in a private Lora Network using the Conduit Box.

There are no NodeRed or other Applications running on the Conduit.

We want to use the Conduit as a Blackbox, as we do it with several other Gateways we support with our Middleware.

E.g Lupus Alert System, when a Sensor is changing the State, then the Lupus Gateway allows to run a external URL, which triggers our Middleware to reload
the States of all connected sensors on that Gateway.

The Nodes sending Events e.g on Door or Window open/closed, the last status update is been maintained and visualized in our SCADA System.

At the moment we pull the Conduit Box every minute, which is in our opinion not a good solution, the Idea is to work more “Event Driven” it would be fine when a Node updates his state, that the Conduit Box could trigger an external URL.

Thanks

Harald

[Jason Reiss]

Use node-red lora-in node or MQTT in an application in node.js, python or c++.

http://www.multitech.net/developer/software/lora/lora-network-server/mqtt-messages/

[Author]

Posts