Getting Started

Configuring Clever Logger

Using Clever Logger

Common Problems

Information for your IT people

On most networks, Clever Logger is super easy to set up. However, some bigger organisations will have more rigid controls on what can access their networks. Here is some info your IT people may need to make things work.

Clever Logger will ‘just work’ on most networks, however on some corporate networks, you may need to get your I.T. team to configure some settings to allow it to work through the firewall.

The below information should help, or they can call or email us if they have any other questions.

Firewall Considerations

  • Clever Logger Gateways need HTTPS access to the Clever Logger servers, as well as NTP access to accurately get the time. Please refer to the table below for a list of domains that need to be accessible. You can use the ‘Run Connectivity Test’ functionality of the Clever Logger app if you are having issues getting the Gateway connected to the internet.
  • Note: it is preferable that you use a domain name for a firewall rule, not a specific IP address, as the IP addresses associated with these domains will change dynamically. We provide no guarantee that IP addresses will remain the same. If this is an issue for your environment, please contact us to discuss alternatives.
  • Some firewalls and other network security devices implement HTTPS inspection – aka SSL inspection, TLS inspection, TLS break and inspect, HTTPS interception, and Deep Packet Inspection (DPI). Clever Logger gateways do not work if SSL inspection is enabled, as they can’t securely connect to the Clever Logger cloud. Please disable SSL inspection in your firewall to allow the gateway to connect correctly.

MAC Address

  • The WiFi and Ethernet MAC addresses of your Gateway can be found via the Clever Logger web app, in the Gateway details screen, or via the mobile app


  • 100Base-T and Gigabit
  • Power Over Ethernet (POE) adaptor is available to purchase here


  • Frequencies: 2.4GHz and 5GHz 802.11.b/g/n/ac
  • Protocols: WPA and WPA2 (WEP, WPA-Enterprise, and hidden networks are not supported.)
Note: Wi-Fi is probably the most challenging aspect of rolling Clever Logger out across so many sites. We currently support about 99% of sites without any issues. For the occasional 1%, we can make two offers:
1. We will have a software developer work with you to make the gateway work with your Wi-Fi. In some cases this has taken a while to work out what was the issue on site and to develop a solution. Once we fix the issue it becomes part of the standard product.
2. We refund your money. 

DHCP / Static IPs

  • The Clever Logger Gateway requires DHCP. It does not currently support static IP addresses.
  • If you would like to have the gateway on a static IP, and you have DHCP available on your network, your router may allow you to set a ‘DHCP IP Reservation’. Please consult the manual for your router for more information.


  • The Clever Logger Gateway requires NTP to sync the time. It will first attempt to use your own local NTP servers (information supplied via DHCP), and if that fails it will attempt to contact the NTP domain listed below.
  • Ensure that your NTP is available to the gateway. In some sites the NTP was behind the firewall and blocked to the gateway.


Following are the list of domains that Clever Logger currently needs access to.

Domain Details
HTTPS - TCP Port 443
HTTPS - TCP Port 443
TCP port 80 (HTTP)
UDP port 123 (NTP)
TCP port 80 (HTTP)
UDP port 123 (NTP)
TCP port 80 (HTTP)
UDP port 123 (NTP)

Legacy Domains

Some older gateways which haven’t auto-updated to the latest firmware need to whitelist the below legacy domains. You only need to do this if instructed by Clever Logger support

Domain Details
HTTPS - TCP Port 443
HTTPS - TCP Port 443

Firmware updates

The loggers (the actual devices in the fridges) do not have OTA upgradable firmware and can not be updated.

The gateway can be upgraded automatically by us. We target which gateways will be upgraded. Our rollout process is typically in stages:

– roll out to our beta test sites to ensure stability

– progressively rollout to all sites over a number of days (or weeks) to ensure that any problems are picked up before a full rollout


We have an article specifically on the security aspect of Clever Logger here.


  • Only temperature data is transmitted from our loggers to the gateway via BLE. This poses no security risk to your network.
  • Only temperature data is transmitted from our gateway to our cloud based server, and configuration data such as sampling rate is sent from the server to the gateway, and uses HTTPS.
  • Using options like a VLAN allow you to totally isolate our gateways if required.

Data Security FAQ


Clever Logger uses various international cloud providers, including Amazon Web Services and Google Cloud Platform.

There are two types of Clever Logger users: Organisation-wide and Site-specific. As the names suggest, Organsiation-wide users have access to everything in an Organisation, while Site-specific users can only see sites that have been assigned to them.

Users can be assigned different roles, such as ‘Admin’ or ‘Viewer’. Read more here.

Data is backed up to separate physical media. This is stored offsite in an access-controlled environment.

Yes. All development is done on a dedicated testing server so customers’ data is protected.


You're going to love Clever Logger

To prove it, we’ll send you a Starter Kit to try out for a whole month.

Set it up, have a play, explore the features – obligation free.

If you love it, just let us know.

If not, just send it back.

Other "How To" articles

Frequently Asked Questions