Steps to prepare an Axis Devices for connecting to Entryfy

There are a few steps needed to get an Axis Devices ready to connect to Entryfy; these are listed below:

1. Verify that the device has a high enough firmware version.
2. Verify that the device has proper network settings.

We recommend the Axis Device Manager to help with this; you can download it here: https://www.axis.com/support/tools/axis-device-manager.

Firmware

When you log in to the Axis hardware, you will see a landing page that will tell you which firmware version is running on the device; see the picture below:

Entryfy requires the firmware of A1601 to be 1.84.3 or above.

Entryfy requires the firmware of A1001 to be 1.65.4 or above.

If you need to upgrade the firmware, press the Upgrade button after downloading the appropriate firmware from https://www.axis.com/support/firmware.

Network Settings

To connect to the cloud, the Axis Network Door Controller needs to have AVHS set to Always and a proper DNS server set to resolve the domains of Entryfy.

You can browse the device and go to the following URL; replace IP with your local network address: http://IP/admin/tcpip.shtml.

If setting a static IP address, set nameservers so the device can resolve Entryfy cloud service domains. Do this by clicking advanced TCP/Settings and filling out the below fields. 

For best performance, use your router's local DNS servers. These servers will have cached DNS records, increasing performance. 

If you need external nameservers, use 1.1.1.1, which you can read here: https://1.1.1.1/dns/.

Date & Time Settings

The last step before adding the device to Entryfy is to set the correct time and timezone. The form is under the menu Date & Time; see the picture below.

Now, you can enter the Serial number and OAK (Owner Authentication Key) in the Entryfy platform to configure and prepare the device. 

If the device does not come online, check the device's system log by going to http://IP/admin/logs.shtml. 

You should check for messages with the marking of stclient; this should give information about whether it connects to the cloud or is having trouble connecting.