Version 1.1.0

This release contains BREAKING CHANGES and you will have to re-define most of your settings in the UI and in automations after installation.

Upgrade Instructions

Due to the many changes and entities that have been removed and replaced, we recommend the following process to upgrade from an earlier Beta or from an earlier release:

• Upgrade the Integration files, either through HACS (Recommended) or by copying the files manually to your custom_components/securityspy directory.
• Restart Home Assistant
• Remove the SecuritySpy Integration by going to the Integrations page, click the 3 dots in the lower right corner of the SecuritySpy Integration and select Delete
• While still on this page, click the + ADD INTEGRATION button in the lower right corner, search for SecuritySpy, and start the installation, supplying your credentials.

Changes

• NEW: Added a new Binary Sensor for each Camera showing if the Camera is updated. This sensor is event driven, so as soon as SecuritySpy flags it as Offline the sensor will update and vice versa.

• NEW: Added configuration url for each camera on the Devices page, so that you can go directly from here to the Camera Settings page in SecuritySpy

• NEW: Added partial support for PTZ. If a camera has PTZ capabilities, the following buttons will be created:

  • Left button. When pressing this button the camera will start a left movement.
  • Right button. When pressing this button the camera will start a right movement.
  • Up button. When pressing this button the camera will start an upwards movement.
  • Down button. When pressing this button the camera will start a downwardst movement.
  • Stop button. When pressing this button the camera will stop any movement currently in progress.
  • Presets buttons. For each Preset defined in SecuritySpy, a button will be created to activate that preset.

• CHANGED: Removed the online attribute from the Camera Entity, as this is now replaced with the Binary Online sensor.

• CHANGED: All entities have been updated to follow a more up to date coding practice for Home Assistant Integrations.

• FIXED: Ensuring the Websocket is properly closed before a restart of the Integration.

• FIXED: Deprecation warning about device_state_attributes start showing up in Home Assistant 2021.12. This is now corrected and moved to the correct type.

Version 1.1.0-beta.2

• FIXED: Ensuring the Websocket is properly closed before a restart of the Integration.
• NEW: Added a new Binary Sensor for each Camera showing if the Camera is updated. This sensor is event driven, so as soon as SecuritySpy flags it as Offline the sensor will update and vice versa.
• CHANGED: All entities have been updated to follow a more up to date coding practice for Home Assistant Integrations.

Version 1.1.0-beta.1

• NEW: Added partial support for PTZ. If a camera has PTZ capabilities, the following buttons will be created:

  • Left button. When pressing this button the camera will start a left movement.
  • Right button. When pressing this button the camera will start a right movement.
  • Up button. When pressing this button the camera will start an upwards movement.
  • Down button. When pressing this button the camera will start a downwardst movement.
  • Stop button. When pressing this button the camera will stop any movement currently in progress.
  • Presets buttons. For each Preset defined in SecuritySpy, a button will be created to activate that preset.

• FIXED: Deprecation warning about device_state_attributes start showing up in Home Assistant 2021.12. This is now corrected and moved to the correct type.

• NEW: Added configuration url for each camera on the Devices page, so that you can go directly from here to the Camera Settings page in SecuritySpy

• NEW: Breaking Change As part of Home Assistant 2021.11 a new Entity Category is introduced. This makes it possible to classify an entity as either config or diagnostic. A config entity is used for entities that can change the configuration of a device and a diagnostic entity is used for devices that report status, but does not allow changes. These to entity categories have been applied to selected entities in this Integration.
  
  Entities which have the entity_category set:

  • Are not included in a service call targetting a whole device or area.
  • Are, by default, not exposed to Google Assistant or Alexa. This might be a Breaking Change
  • Are shown on a separate card on the device configuration page.
  • Do not show up on the automatically generated Lovelace Dashboards. This might be a Breaking Change

Release 1.0.7

• FIX: Issue #24. Allow requesting a custom snapshot width and height, to support 2021.9 release
• CHANGED: Ben from Bensoftware made a change I asked for, so it is now possible to optimize the Binary Motion Sensor, so that we don't need to wait for a file to be written. The sensor now turns on and off much faster, and we don't need specific Capture settings. It requires minimum V5.3.4b3 of SecuritySpy for this work.

Version 1.0.4

• FIX: If SecuritySpy had only 1 camera attached, the Integration would fail during setup. Issue #21
• ADDED: The CLASSIFY event is now also added to the Event Stream, so that this, in combination with the TRIGGER_M event, will ensure we record if a Human or Vehicle is detected. Requires that the Motion Capture AI Trigger threshold is set to a value larger than 0 on the Triggers Settings tab in SecuritySpy. See the README.md file for an example of how to make an automation based on this.

Version 1.0.3

• CHANGE: Modified several files to ensure compatability with 2021.5.x releases
• CHANGE: Added iot_class to manifest.json as per Home Assistant 2021.5 requirements.

Version 1.0.2

• FIXED: Issues #13 and #14 are fixed with this release. Specific Cameras and switches went off and on, without any actions by the user
• CHANGE: Removed all code that would refresh sensors as per a specific timeinterval. All changes are now purely push based.

Version 1.0.2 Beta 1

Trying to fix issue #14

Version 1.0.1

• ADDED: If you don't need Audio in the Live Stream, you can remove most of the latency in the stream, by not using the rtsp feed from the Camera. In order to do that, there is now an option in the Config Flow, to Disable RTSP. If this box is marked the stream will not use RTSP for streaming - and Audio will not work. If you already have configured the Integration, go to the Integrations page, and click OPTIONS on the SecuritySpy widget, then you will have the possibility to change this setting.
• FIXED: If there were no Schedule Presets defined on the SecuritySpy Server, the Integration would not install. Fixing issue #16
• FIXED: If authentication failed during setup or startup of the Integration it did not return the proper boolean, and did not close the session properly.

Version 1.0.0

I believe this is now stable enough, and has the basic services to be called a version 1.0 release.