With NuvIoT, you can focus on configuration rather than coding as you build incredibly powerful applications to work with your IoT devices. A big part of how these applications are built is by creating a route that the message will follow to perform different actions on it. From NuvIoT Basics Part Two, Getting the Message, we learned that IoT messages will generally contain both a Message ID and a Device ID. Once a message is received, the first part of the route is to hand the message to the Planner. The Planner will then look at those Message and Device IDs, using that information to plan the route.
What makes the Planner really powerful is that it just works with the Message and Device IDs, it does not care where they came from. When you create a Planner, you add in different options for where it should find the Device and Message IDs and even how it should extract those values using a regular expression, if necessary.
Currently, our Planner supports looking for the Device IDs and Message IDs in the following locations:
- HTTP(s) Headers
- Paths and Query Strings
- Fixed Position
- Message Body
The Planner even supports a combination of different locations. For example, you can look for the Message ID within the path of the HTTP request and the Device ID in the header.
At Software Logistics, we feel strongly that you should not have to change your devices’ firmware to work with an IoT platform. The platform should be flexible enough to work with your devices. And NuvIoT was designed with that flexibility in mind.
Be sure to check out our full NuvIoT Basics series: