motion-ai

Third time is the charm.

Well, I forgot some parentheses.

We continue to work in both the engine room to improve performance, eliminate bugs, and connect up the new devices on the Lido deck.

On the Lido deck we have improvements in design and decor with more icons, better naming, and more exploitation of images being worth more than 1000 words.

The system now also provides top-level information on system operation, including AI's on-line, Messaging operational, etc..

Notifications now include images and those images are linked to the animated event video; I think it will work through the Nabu Casa and Web interfaces externally, but who goes anywhere these days?

Cameras may now be specified with an entity to watch, e.g. "dog" or "car" on the "interiorgate" camera and corresponding notifications can now be enabled per camera for the designated entity.

Person, Vehicle, and Animal views formerly on the Overview and using masked images has been moved to the Administrator view and unmasked. These views will be used for inspection and selection of new "ground truth" in the training loop.

Apple iOS application integration works properly, including association with Apple watch.

Continue to "cut the grass for the goats to eat" with improvements in the display of information.

Both visitor and administrative users now have overlays for information about the most recent detection and associated person, vehicle, or animals in those detections. These specifciations enable the counting of those entities (person, vehicle, animal) across all cameras; statistics for 1m, 5m, 15m, and 30m are also calculated.

Some additional cleaning and pipe fixing in the engine room to ensure parity of implementation across entities and across cameras.

All devices now emit their LAN IP address as part of their configuration information on MQTT; the IP addresses are collected and made options for interrogating the Motion Classic addon through its REST API; see the SYSTEM view for administrators.

The cameras are now enabled with specific entity detection parameters; all default to 'person' but any entity supported by the YOLO AI may be specified (n.b. tiny only detects 20 entities; the others detect 80); the AI options are dynamic based on the YOLO configuration.

FACE and ALPR continue to lag YOLO w.r.t. UX, but underlying plumbing is highly similar; however, additional integration is required between FACE and Person and ALPR and Vehicle detection.

FWIW: The last "working" version of HA is 0.116.4 w.r.t. the utilization of "non-conformant" REST API calls (e.g. YOLO configuration).

The system has been tested with v0.118.4 and outside of the non-conformant REST API issue, all else appears to work as designed.

Added support for devices running the motion addon to provide their IP address in the MQTT payload.

Updated UX and YAML to process.

The "dashboard" (aka the first view for either administrative or normal accounts) now includes information that should help debug start-up as well as help w/ identifying cameras which go off-line.

The "add-on" referenced is the Motion Classic (motion-video0) add-on in github.com/dcmartin/hassio-addons repository. It has REST API end-points for both its configuration (cgi-bin/config) and status (cgi-bin/status). Those are now captured as REST sensors and used to determine if the addon is configured and running.

The MQTT broker is also being monitored for activity greater-than zero (0) during the previous 1 minute; if no traffic occurs, then MQTT is not connected.

The YOLO (and soon face and alpr) has a configuration REST API, but the current 0.117.6 server is picking up an "upgrade" from the underlying HTTP libraries to find the output invalid (n.b. closed unexpectedly); IDK why, works w/ curl, but it's on the list. Therefore the status for YOLO is currently an MQTT sensor listening for the announcement when the AI starts; however, this sensor does not indicate if it is still running (hence the REST API). However, it should help with start-up.

LMK if you have question or need assistance in installing; best to find help on FB or Slack.

The latest version of Home Assistant (v0.117.6) is working properly for Motion-AI.

More automation for installation and configuration!

Clean-up icons, naming, ... for UX.

Cameras now automatically discovered from Motion Classic addon configuration and from MQTT traffic.

This release automates installation to include the downgrade of Home Assistant core to version 0.116.4 and configuration of default camera as locally attached on /dev/video0 using the same host for MQTT, YOLO, FACE, ALPR, and the Motion Classic addon.

This update is in response to changes in v0.116, but before changes in 0.117.

This software works with v0.116, not v0.115, and not v0.117.

Recommended version of Home Assistant is v0.116.4

MANY CHANGES.

Updates for Home Assistant v0.115 and later versions which deprecate the template platform utilization of entity_id

New functionality exploiting the new (w/ v0.115) Media folder to enable review of previous person, vehicle, and animal detections; generic entity is also supported, but off by default.

This version works in conjunction with the Motion Classic add-on and the same set of AI's (YOLO, FACE, ALPR). Human pose detection is next integration.

The sh/get.hassio.sh script has been improved to include Docker configuration for logging and nVidia container runtime when nvcc is installed on the host.

Updated documentation will be included prior to the final release of this version.

Modifications to support latest releases of Home Assistant, including:

• installation of Home-Assistant supervised for Ubuntu 18 and Rasbian Buster
• cleanup and improvement of documentation
• addition of WIP for overview map

Additional fixes for underlying plumbing; change in display to render the default view to not include any images. New "developer" view provides access for administrators to all underlying components and controls.

Updates to accept additional AI services inputs, including human pose estimation, as well as processing by yolo4motion for videos as well as images.

Fixed bugs with respect to displaying the images and snapshots from cameras. Should be operating correctly.

Fixed MQTT payload processing; should now work with latest Home Assistant (v0.109).

Face detection should be working correctly.

MQTT publishing for events (n.b. homeassistant/automation/motion/publish.yaml) is not working as expected; still publishing a string rather than a JSON object.

Support for basic function of sh/kuiper4motion.sh capabilities has been implemented; not yet processing signal in Home Assistant, but publishing MQTT payloads.

Sensor for cameras detected from device_start MQTT payloads from any device is also not working as expected; data value remains a string rather than JSON object. This artifact appears in the "Settings" view.

Decreased number of entities defined in the system to enable successful operation with numerous cameras.

There are conditions under which Home Assistant 0.107+ exhibits failure; IDK know why. It simply quits.

Updates to accomodate Home Assistant v0.107 with elimination of group as mechanism to control UX.

New UX is handled through lovelace.json which is generated from template. Linked to the ./.storage/lovelace Subsequent rebuilds using make will over-write any changes unless saved as raw YAML. May be modified using standard UX editor; save raw YAML and edit configuration.yaml appropriately.

Additional CGI executables for config, options for add-on and gif and jpg for event and client.

For example, to retrieve the add-on options specified:

curl http://127.0.0.1:7999/cgi-bin/options

To retrieve the GIF that corresponds to the detected event for client camera1:

curl http://127.0.0.1:7999/cgi-bin/gif?event=detected&client=camera1

Documentation updates and minor fixes for internet and intranet monitoring.

This release has refactored the repository to enable utilization as a over-write replacement for the traditional /usr/share/hassio directory, including the default homeassistant/ configuration files (n.b. works best with a fresh installation of Home Assistant).

Add git to your fresh Rasbian/Ubuntu environment, clone this repository, and use the ./sh/get.hassio.sh script to install Docker and other pre-requisites for installation of Home Assistant. See docs/MOTION.md for additional information on installation.

In conjunction with open-horizon v2.0 and hassio-addons v0.1.0