Feature #582

Add support for IoT messages

Added by Hammel almost 4 years ago. Updated almost 3 years ago.

Status:ClosedStart date:28 Jul 2017
Priority:NormalDue date:
Assignee:Hammel% Done:


Target version:PiBox - 2.0 - Harkonnen
Severity:03 - Medium


Part of IronMan project.

Needs to support sensor messages - store to sensor partition on disk, based on sensor naming/config.
Overwrite with latest message in per-sensor file to avoid managing rotating data.

Associated revisions

Revision 0d818ccc
Added by Hammel about 3 years ago

RM #582: As part of IoT support, extend multicast processing to work properly with messages from Jarvis (specifically with Jarvis registration with the monitor), to allow inbound commands to be forwarded to IoT devices.


#1 Updated by Hammel about 3 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 30

This was prototyped last year when I was doing sensor to piboxd registration. However, registration is different now because of how Jarvis is now in the mix. The prototype has been updated and Jarvis registers correctly (see Jarvis Process in the IronMan project wiki).

These changes will need to be tested against an updated sensor (the lightsw device, which is a real device instead of the prototyped ESP8266 project). See the updated communications protocol in the IronMan wiki.

#2 Updated by Hammel almost 3 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 30 to 100

This is no longer required in Piboxd. IoT messages pass through the imrest REST API. Piboxd just handles multicast discovery responses.

Closing issue.

Also available in: Atom PDF