https://redmine.graphics-muse.org/https://redmine.graphics-muse.org/favicon.ico?16278048512018-04-06T22:25:27ZGraphics Muse Issue Trackerpiboxd - Feature #582: Add support for IoT messageshttps://redmine.graphics-muse.org/issues/582?journal_id=21902018-04-06T22:25:27ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>30</i></li></ul><p>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 <a href="http://redmine.graphics-muse.org/projects/ironman/wiki/MVP_#Jarvis-Processing" class="external">Jarvis Process</a> in the IronMan project wiki).</p>
<p>These changes will need to be tested against an updated sensor (the <a href="https://gitlab.com/xarduino/lightsw" class="external">lightsw</a> device, which is a real device instead of the prototyped <a href="https://gitlab.com/xarduino/iotdevice" class="external">ESP8266 project</a>). See the updated <a href="http://redmine.graphics-muse.org/projects/ironman/wiki/MVP_#Jarvis-Processing" class="external">communications protocol</a> in the IronMan wiki.</p> piboxd - Feature #582: Add support for IoT messageshttps://redmine.graphics-muse.org/issues/582?journal_id=22542018-07-13T21:15:01ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>30</i> to <i>100</i></li></ul><p>This is no longer required in Piboxd. IoT messages pass through the imrest REST API. Piboxd just handles multicast discovery responses.</p>
<p>Closing issue.</p>