FIRMWARE RELEASE NOTES
                        ======================

Products affected: AXIS A1001

Release date:      2017-07-22

Release type:      Production

Firmware version:  1.60.0

File name:         A1001_1_60_0.bin

Preceding release: 1.57.0.2

Onvif support:     Profile C, Profile A

------------------------------------------------------------------------------

UPGRADE INSTRUCTIONS
====================

Upgrade the firmware with AXIS Camera Management, HTTP, or FTP.
Follow the instructions given in the User Manual, at
http://www.axis.com/support/tecnical-notes/how-to-upgrade,
or howtoupgrade.txt, which is included in the firmware folder.

If in an A1001 controller cluster make sure to upgrade all controllers. 
Either all at a time using ACM or straight after each other using web interface 
or FTP. The entire cluster always needs to be on the same Firmware!

New Features
============

1.60.0:F01
HID Mobile Acceess. An IP-based Mobile Access control using trusted identities
on smartphones for opening doors and locks instead of managing traditional 
printed identity credentials. See user manual for more information.

1.60.0:F02
Additional support for wireless locks with Simons Voss Smart Intego.
A Smart Intego GatewayNode can now be connected to the A1001 over Ethernet 
having it's wireless locks controlled by the acces control rules. 
A1001 can be connected to one Gateway that can communicate with up to 16 
wireless locks. See user manual for more information.

1.60.0:F03
Conformance to Onvif Profile A.


Corrections in 1.60.0 since 1.57.0.2
=================================

1.60.0:C1
In Entry Manager Date & Time Settings you can only input the IP address of the
ntp server, not the DNS name. DNS name of NTP server can be provided by going
into Additional Controller Configuration > System Options > TCP/IP > Advanced >
NTP Configuration.

1.60.0:C2
Fixed critical vulnerability ACV-116267

1.60.0:C3
COM Ports visible after update


Known Bugs/Limitations
======================

1.60.0:L01
It is not possible to delete a big chunk (30, 60, 100) of HID useres from the user interface. 
The user interface will delete the users visually but they remain in the HID cloud.

1.60.0:L02
It is not possible to create action rules with schedules, other than “Always (No Schedule)” 
as well as with additional conditions, when in a controller cluster.

1.60.0:L03
After a firmware update, the web browser cache may need to be cleared to avoid
seeing pages originating from the old firmware.

1.60.0:L04
During start up of the device the web server is reachable earier than in
previous FW, before other sub-systems are operational, possibly resulting in AEM
showing 'Failed to retrieve device info' on its overview page if accessed during
this time. Reloading the page a few seconds later will resolve this issue.

1.60.0:L05
If you have offline controllers in a controller cluster and try to remove one of
the units that is online this requires a majority of all controllers being
online excluding the controller being removed.

1.60.0:L06
To change the recipient of an Action Rule, please click the "Modify..." button
and change there. The drop-down in the Action Rule lists currently does not
work.

1.60.0:L07
If you have a door configured with a door monitor, the lock button in AEM will
not immediately lock the door. It will only set the controller in a locking
state. The door lock will be locked once the door monitor indicates that the
door is closed.

1.60.0:L08
If using a controller cluster and configuring an action rule on one of the
devices to trigger on an event sent by another device in the cluster, the
action rule will not be triggered.