If you are using a foldable smartphone, we suggest trying to BlinkUp from a different phone to see if the issue persists.
When BlinkUp fails to complete successfully, or hardware that once connected falls offline, the diagnostic LED on Kisi hardware may flash one of several different patterns to provide more context.
Below are more details around the codes and how to resolve them.
Invalid Wireless Setup
"Searching for WiFi Network" or "Joining WiFi Network" pattern
1. Verify the SSID (network name) is correct. SSIDs are case sensitive. Be careful not to add spaces to an SSID accidentally when entering the network name into the mobile app, especially at the end of an SSID.
2. Verify the password is correct. Network passwords are case sensitive.
It is easiest to remove Kisi from the equation and check that the network name and password are useable outside of the app; you can use a laptop or phone to confirm that you can connect to the wireless network with the provided credentials.
If the network requires you to open a browser to accept terms and initiate the session, then that network is not suitable for use with BlinkUp. Networks using a web-based login page cannot be used for Kisi connectivity.
Valid credentials with wireless connection that drops randomly
In an area with many wireless networks, interference may occur when multiple networks are on the same or nearby channels.
To remediate wireless congestion, you can use free mobile apps to survey the wireless use in area, and then configure the router or access point to utilize a less congested channel for wireless.
"Getting IP address" pattern
Kisi hardware dynamically takes the first available IP address from the total address pool in the network gets connected to. If the network has no more addresses to assign, or is not assigning addresses to the controller or reader, then the Kisi hardware cannot connect or communicate. Network administrators have a few options to address the problem:
Locate Kisi hardware by MAC address and assign IP address.
Kisi MAC addresses for wifi and ethernet can be located on the device ID sticker. Network administrators can use this information to assign an address to the hardware to allow it to communicate locally on the network.
Reduce the address lease time to return unused address to the pool faster
This is a popular option for situations like wireless networks in coworking spaces where they may have many devices moving in and out of a building throughout the week. This will not help if you don't have devices moving on/off the network fairly frequently.
Add additional IP addresses to the pool
The simplest way to do this is to check any static DHCP assignments (or reserved ranges of IPs) to make sure they are current and remove any outdated/unused/unneeded assignments releasing those IP addresses back into the pool.
Remove devices from the pool
More addresses can be made available by reducing the number of devices requesting addresses. Old or unused devices can be removed from the network, and if the pool is shared by both wired and wireless devices, ensure that a device isn't requesting an address on both at the same time (allowing one device to take up two IP addresses from the pool).
Disabled Ethernet switch port
"Waiting for Ethernet" pattern
The Kisi Reader and Controller both support a wired ethernet connection that is for the most part plug-and-play. When connected to an available switch or router with available addressing and an active connection to the internet, the hardware will begin communicating to Kisi within a few minutes. However, simply connecting the cable to an open or available port does not guarantee that setup is finalized. In some cases, the ports themselves have to be first enabled on the switch or router to allow addressing to function and traffic to flow.
"Resolving server name" or "Connecting to server" patterns
Kisi hardware communicates over several outbound ports that can be found here. If BlinkUp is not able to be completed successfully, ensure all required ports are opened in your firewall.