Project

General

Profile

Actions
Copy link

Feature #619

closed

Add support to imwww for storing and imrest for retrieving and returning monitor descriptors

Added by Hammel over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Immediate
Assignee:
Hammel
Category:
Software
Target version:
Iron Man - 0.5.0
Start date:
06 Apr 2018
Due date:
% Done:

100%

Estimated time:
Severity:
01 - Critical

Description

This requires that the imwww service in the www repo in IronMan has been updated to accept descriptors from the user and stored in a well known location or can be queried via the REST API provided by the imrest service.

The well known location will be /etc/monitor/descriptor.

Actions
Copy link
 #1

Updated by Hammel over 6 years ago

  • Project changed from piboxd to Monitor
  • Subject changed from Add support for retrieving and returning monitor descriptors to Add support to imwww for retrieving and returning monitor descriptors
  • Description updated (diff)
  • Category set to Software
  • Target version changed from 0.12.0 to 0.5.0
  • Severity changed from 03 - Medium to 01 - Critical

Moving from piboxd to imrest (in monitor) so piboxd doesn't need to know about ironman data.

Actions
Copy link
 #2

Updated by Hammel over 6 years ago

  • Subject changed from Add support to imwww for retrieving and returning monitor descriptors to Add support to imwww for storing and imrest for retrieving and returning monitor descriptors
  • Description updated (diff)
  • Status changed from New to In Progress
  • % Done changed from 0 to 20

The update to imwww to accept user input for a descriptor (labeled as a Location) when setting up networks is implemented but needs testing.

The update to imrest for returning monitor descriptor to Jarvis is implemented but needs testing.

Actions
Copy link
 #3

Updated by Hammel over 6 years ago

  • % Done changed from 20 to 60

imrest is tested - it returns the descriptor to Jarvis when Jarvis (using AES encryption) when Jarvis asks for it.

Now I just need to test that a real monitor, configured with the imwww interface to set the descriptor, responds the same way.

Actions
Copy link
 #4

Updated by Hammel over 6 years ago

  • % Done changed from 60 to 70

I got back to testing this today. I started the PAIR UI on the Pi and couldn't get it to show up on the smartphone. I ran the interface manually and found I had introduced a bug in the php (a missing semicolon). Fixed that and the UI comes up again.

It's late and need to get some dinner. I'll pick this up again later.

Actions
Copy link
 #5

Updated by Hammel over 6 years ago

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

I brought up a Pi3 using the monitor configuration (I used my Chromebook to configure the networks since this was easier than using my tiny phone). I then was able to register a Jarvis client with the monitor and got back the descriptors!

This required me to make a change to the way the pairing with Jarvis (and later IoT devices) works. If you boot with pair enabled then that is for configuring the network. After doing that and rebooting, you can turn on the pair button again (without rebooting) and Jarvis and IoT devices can pair. When this happens the pair LED will light for three seconds for each registration the monitor receives.

All changes committed and pushed.

This issue can be closed.

Actions
Copy link

Also available in: Atom PDF