Avlytics SA has released version 7.25.12 !!
Below is an explanation on what new features are available and how to introduce these features to your device.
Ai Containers :
A new scheduling mechanism has been introduced to cater for loadshedding.
The device will now use the Time Period in the Hub Rules as its "Active Time".
If the device is following a schedule it will be armed or disarmed and display either "armed" or "disarmed" in any status requests.
If the device is armed or disarmed outside of the schedule period , it is seen as an override arm or disarm and the status will be displayed as either "armed_override" or "disarmed_override"
We have introduced this new facility to cater for loadshedding , where if a device is disarmed and is supposed to arm at 8pm
but the device is off due to loadshedding, When the device comes back online at for example 9:45pm
the device will look at the rules and see that it is supposed to be armed, and it will arm itself.
How the previous version worked is, the device had a arm command or disarm command, if the device was off when it was supposed to send its arm signal it would not send the arm and if it came back on at 9:45pm it would remain disarmed.
To get the new firmware, please request that one of the support technicians upgrade your device.
Edge Bot Comms Module:
1) Maintenance Logic
The Comms module handles telegram requests and control room software integration.
We have introduced some maintenance logic to suppress maintenance messages between a predefined maintenance interval.
Example. If camera 1 loses connection to the Avlytics device, a stream_timeout ( STO ) message is generated and sent to the various platforms ( Telegram , Control Room Software ). The purpose of this message is to notify the controllers that a connection on site has been lost and needs to be investigated. This message will continue to be relayed to the control room until the root cause is rectified, the message will repeat every 1 minute unless the new maintenance suppression logic is activated. To enable maintenance suppression , simply add a maintenance interval and the device will send one notification then suppress all alerts of the same type for the maintenance interval , and then it will repeat the message once and suppress again for the maintenance interval until rectified. This ensures that the control room is notified of any failures but not overloaded with multiple notification's for the same maintenance event.
Maintenance messages with no suppression.
2) Walktest Facility.
We have introduced a walktest facility whereby a user can send a /walktest request on telegram, which will remove all of the exclude tags for a specific channel , arm the channel and send alerts for all tag types until the walktest has ended.
Once the user issues a /endwalktest command on telegram, all tags that were previously in the excludes will be returned to the excludes and that particular channel will be disarmed.
3) Calibrate Facility.
We have also introduced a calibrate function which allows the installer to issue a /calibrate command on telegram which will instruct the device to start recording on a particular channel for 2 minutes.
This produces a "testing" video clip that can be used to verify the devices training accuracy and validate that the correct prediction's are made on an object. To use the video to validate the device training , edit the rtsp url on the Hub for the channel that needs testing. copy the original url "rtsp://........ " and save it in a safe place, then type in the calibration image location.
/var/lib/ame/calibration_channel1.mp4 The Url is the same for each channel , only the channel(1) number is edited for calibration video clips from other channels.
4) Set Keys.
We have introduced a quick password changing feature by simply sending a /setkeys_changetothis command on telegram , the user can easily update the Web interface password for the device to the new password, the text that is typed in place of (changetothis) will be the new password.
5) Telegram Maintenance.
The New version also allows the user to receive the same maintenance notifications that are sent to control room software, directly to telegram App. This facility should not be used if the device is already reporting to a control room package.
6) Checklist Passing - Settle Logic
The latest firmware is not as aggressive in sending maintenance messages as it has additional logic that ensures that the maintenance alerts are not due to a software issue, with the new version the device is constantly self evaluating and ensuring that it is healthy.
If the device experiences a Tamper , Stream Timeout or other maintenance event, the device is able to identify if the event was due to a stability issue or if it was in fact a tamper or stream
Tamper :
We have introduced a new tamper facility whereby all channels are monitored for tampering.
If the image structure changes to beyond a specific threshold, a tamper signal is generated and sent to the control room.
To configure the tamper's, please follow our tamper config guide and explanation at the following link : https://avlytics.freshdesk.com/a/solutions/articles/43000661960
Tamper image visualization.
Edge Interface :
1) Training Page Improvements.
The edge device web interface has a few upgrades.
When selecting Training Inspection from the left side menu.
Select Channel then Feedback received then Filter.
The training page has been split into pages of 10 alerts per category.
At the top of the Training Inspection page a list of all training for that specific channel is populated after clicking on the Filter Button, this gives the user a quick display of how many samples have been submitted for each category.
While still allowing the user to page through the pages and view each image that is stored in the system as a training sample. Because the Dataset is split into pages of 10 , the page loads and displays images more efficiently on slower internet connections.
2) Control Room package integrations.
Avlytics is now integrated into the following packages:
Listener | Watchmanager | Patriot | Synapse | Bvigilant | Signaltower | Autonetics | Sentinel
Monitored_events or Maintenance Tab on the Hub :
We have introduced a new Tab in the Hub in which the user can select ( tick ) which event types should report to the control room.
This function is available on the SeeingAme Hub for each channel. 
3) View Cropping.
A view cropping option is available on the Device web interface, this feature allows the user to crop out objects or obstructions in the peripheral view of the camera. This feature is only available in a rectangular form, which mean's the user must clip parts off of the image in either a left , right , up or down direction.
4) Inbound API
A new inbound api has been configured on the device's to allow remote arming | disarming or status checking on public infrastructure. To send the command to the device, please type the command into a chrome web browser.
To view the device's status please issue the following command replacing <url> with your device's VPN IP Address
http://isd.dyndns.org:10000/api/status/<url>
To arm a channel , please issue the below command replacing the <url> and the <camera> with the channel you would like to arm. example : http://isd.dyndns.org:10000/api/arm/172.29.194.3/channel1
http://isd.dyndns.org:10000/api/arm/<url>/<camera>
To disarm a channel , please issue the below command replacing the <url> and the <camera> with the channel you would like to disarm. example : http://isd.dyndns.org:10000/api/disarm/172.29.194.3/channel1
http://isd.dyndns.org:10000/api/disarm/<url>/<camera>
Network Problem detection and avoidance.
The latest firmware has a network probe facility that pings the local gateway/router.
If the router fails to respond after 3 consecutive pings , the device will reboot in an attempt to restore a network connection to the router