Drop predictions, fix time formatting, fix unit of measurement

The predictions as json was not useful so removed. Fix a couple of small issues to improve the display of sensor attributes.

Expose predictions as json

The full predictions from Deepstack are returned in the predictions attribute as json in a standardised format. This makes it easy to access any of the predictions data using a template sensor. Additionally the box coordinates and the box center (centroid) are returned, meaning an automation can be used to determine whether an object falls within a defined region-of-interest (ROI). This can be useful to include/exclude objects by their location in the image.

Note: In the case that a unique object is present in an image (e.g. a single person or single car) then the direction of travel of the object can in principle be determined by comparing centroids in adjacent image captures. This tracking functionality is not implemented yet in Home Assistant.

Example prediction output:

[{'confidence': 85.0,
  'label': 'person',
  'box': [0.148, 0.307, 0.817, 0.47],
  'centroid': [0.388, 0.482]},
.
.
]

The box is defined by the tuple (y_min, x_min, y_max, x_max) (equivalent to image top, left, bottom, right) where the coordinates are floats in the range [0.0, 1.0] and relative to the width and height of the image.

The centroid is in (x,y) coordinates where (0,0) is the top left hand corner of the image and (1,1) is the bottom right corner of the image.

Adds last detection attribute

The time of the last detection of the target is now displayed as an attribute

Fix timeout config

Merge pull request #53 from robmarkcole/fix-config

Fixes timeout config

Fix manifest.json

Fixes a missing requirement

v1.4 Adds API key

Adds the ability to use an API key to secure deepstack, just add -e API-KEY="Mysecretkey" when you run deepstack. Note that you need to use this key even if you restart deepstack, unless you reset it using -e API-KEY="" . You can now also set the timeout on requests to deepstack, default 10 seconds.

Filters object_detected on confidence

object_detected events are now only fired it objects are above the configured confidence threshold. This should reduce the number of events fired by the component

Makes confidence configurable

Allows setting the confidence threshold for detections of target, with a default of 80%.
The confidence is now displayed on the saved image:

Splits out face into separate repo

To better support HACS this release splits out face into the repo https://github.com/robmarkcole/HASS-Deepstack-face

Fix bounding boxes

Bounding boxes are now much clearer

Note there is nothing particularly special about this 1.0 release, but I regard the functionality to be basically complete