If this happens, please:

1. Make sure LaMetric Time supports your network.

LaMetric Time device supports 802.11 b/g/n 2.4 GHz networks.

2. Make sure LaMetric Time supports your network security.

LaMetric Time supports 
  • Open Wi-Fi networks
  • Closed Wi-Fi networks with WEP or WPA/WPA2 security. (WEP is supported since firmware 1.1.0)
  • Hidden Wi-Fi networks (since firmware 1.1.0, iOS client 1.1.0, Android client 1.0.8).
  • Closed Wi-Fi networks with WPA/WPA2-Enterprise security (since firmware 2.0.16, iOS client 2.3.1, Android client 2.3.1) - currently only Protected Extensible Authentication Protocol (PEAP) with EAP Password (EAP-PWD) authentication method is supported.
LaMetric Time doesn't support
  • Web page logins

3. Make sure your router doesn't block LaMetric Time by MAC address.
In some cases, you need to add LaMetric Time device's mac address to your router's filter for LaMetric Time to be able to connect to the access point. Due to a bug in 1.0.23 firmware mac address that you see during setup and actual mac address that you need to add to your router's settings differs. In this case, update LaMetric's firmware over USB to the latest version (>= 1.0.24) and try again.

4. Make sure time and date on the phone are configured properly.
In other cases, LaMetric Time is unable to connect to the Internet due to a bad time or date set by the mobile application during the first setup. This may prevent LaMetric Time from using secure SSL connections with backend as well as a mobile client. Fixing date/time and re-connecting LaMetric Time to Wi-Fi hotspot fixes date/time configuration.

5. Make sure the firewall doesn't block NTP (Network Time Protocol) *.pool.ntp.org services.
During its work LaMetric Time can adjust it's time to be accurate. But due to firewall settings on the router it may be unable to do so. This may cause time on the LaMetric Time to drift or get reset after the reboot and as a result, mobile client will not be able to communicate with LaMetric Time. Also, please make sure UDP traffic is not blocked for port 123.

6. Make sure the firewall doesn't block PING (ICMP) packets.

LaMetric Time refuses to connect to Wi-Fi hotspot if the latter has no Internet available. The Internet availability check is done by sending PING (ICMP) requests to DNS servers it has received from the router. Router/Firewall can sometimes trick LaMetric Time to think there is no Internet connection by blocking PING requests inside a network. Check your router's security settings. Sometimes lowering the security level to "low" may solve the problem.

7. Make sure AP Isolation (client isolation, guest network) option is disabled on your router.
Access point isolation is a security feature of your router that prevents connected devices to "see" each other. If it is enabled mobile client will not be able to communicate with LaMetric Time. 

8. Make sure UPnP and SSDP are enabled on your network
Some routers may have UPnP/SSDP (Universal Plug and Play/Simple Service Discovery Protocol) feature disabled. It is required by Android and iOS clients to properly discover your LaMetric Time in the local network. Usually to enable that you should check UPnP/SSDP option in the router's settings. Sometimes this feature may have a name like "XBox Compatible" or similar.   

9. Reboot your router
In some cases, the router stops accepting new connections after some time of its work. At the same time, existing connections can work without any issues. In this case rebooting the router may help.