IoT Management

From IoT with AME
Revision as of 11:13, 17 July 2017 by Ctreber (talk | contribs) (Created page with "Home =Management - How to manage an IoT installation= Something that I noticed (even) at home: Once you deployed a number of IoT devices, some questions ari...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Home

Management - How to manage an IoT installation

Something that I noticed (even) at home: Once you deployed a number of IoT devices, some questions arise:

  • Does a device have a problem?
  • What devices are actually deployed?
  • What software versions are in use (devices, IoT framework, capabilities)?
  • What topics are in use? Who is publishing, who is subscribing? What is being published? How often?
  • Security - currently I rely on the privacy of my WLAN, but I guess message exchange via SSL would be "really nice" (and require a reworking of my infrastructure)

Ingredients to the solution are


Status

All may devices are reporting their status under topic "<mqttID>/status". Subscribing to "+/status" gives me an overview about what devices are deployed, and how they are doing connection-wise.


Network

Similarly, they report their IP and MAC addresses. Once devices are able to connect to more than one WLAN, they should report the SSID in use as well.


Software

My devices report the software version of the device, of each capability, and the underlying IoT framework. This allows me to find devices which need to be or could be updated.


Location

With enough devices, the MQTT-ID may or may not tell you enough to find out where the device is physically located (maybe it even moves?).

Home