Skip to main content
SmartLock PRO - Network Requirements

In this article, we'll be going through the requirements to connect a SmartLock Pro (SLP) to a Wi-Fi enabled network.

Updated over 10 months ago

The lists below show the technical requirements before connecting SLP to a network.

Wi-Fi Requirements

  1. SLP can only connect to Wi-Fi channels 1 to 11.

  2. SLP can only connect to a 2.4Ghz Network. To extend the SLP's battery endurance, the 5Ghz is unsupported as it consumes much more power.

  3. SLP supports WPA and WPA2 but doesn't support WPA3.

  4. Wi-Fi MAC filter or any other kind of filtering should be disabled.

  5. The signal strength should be above -70dBm for smooth communication. The locks use ultra-low-power Wi-Fi chips, which require strong signals to operate properly.


Note

  1. You can find the MAC Address under the WIFi Section from Spaces App > Access the room > 3 dot section > "Wi-Fi."

  2. For the network to not switch between 2.4 GHz and 5 GHz, the band shifting setting needs to be turned off.


Other Network Requirements

To let the SLP communicate with the Goki servers, please ensure the network configurations suit the following requirements:

  1. Allow Goki Server Access: The smart locks communicate on the 4999 TCP port. Make sure the port is open on the firewall.

  2. Access To the Internet: The smart locks should be able to access the Internet without authenticating on any authentication server.

  3. Public and Private IP Addressing: As smart locks use private IP addresses within the local network, configure NAT to map these private addresses to a single public IP address when communicating with external servers or cloud services. The “IP Load Balancing” feature and “Asymmetric Routing” problem on firewalls are relevant to this requirement.

  4. Address Reservation: Reserve IP addresses for smart locks in the DHCP server configuration. This ensures that each smart lock receives the same IP address upon renewal.

  5. Lease Duration: Adjust DHCP lease durations to match the expected connectivity patterns of smart locks. Longer lease durations can reduce network traffic associated with frequent address renewals.

  6. Separate Subnets: Consider placing smart locks on a separate subnet using VLANs. This can help logically isolate smart lock traffic and simplify DHCP management for that specific subnet.

  7. QoS Policies: The QoS policies configuration may prevent the smart locks traffic from passing through the network effectively. We advise implementing QoS policies to prioritize the smart lock traffic, ensuring that it receives sufficient bandwidth and low latency to operate effectively.

  8. DoS Protection Policies: The DoS protection policies possibly mark Goki server traffic as a threat. Ensure there are no such policies.


Did this answer your question?