Clever Logger Gateway Considerations
Gateway Considerations
Clever Logger gateways will ‘just work’ on most networks, however on some corporate networks, you may need to get your IT 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 DNS, 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 Wi‑Fi 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.
Ethernet
- 100Base-T and Gigabit
- Power Over Ethernet (POE) adapter is available to purchase here
Wi-Fi
- 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 gateways 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 purchase.
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 purchase.
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.
DNS (Domain Name System)
- The Clever Logger gateway requires DNS in order to turn domain names into IP addresses.
- The gateway will first attempt to use the DNS servers that are suggested via DHCP. If this fails, the gateway will attempt to connect to the DNS servers listed in the table below.
NTP (Network Time Protocol)
- 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 servers listed below.
- Please note: older versions of firmware (before April 2023) had issues using NTP servers provided via DHCP. If you’re struggling to get NTP to work, please contact us and we can check the firmware version.
- Ensure that your internal NTP server is available by the gateway. In some sites the NTP server was behind a firewall and blocked to the gateway.
Domains
The following are the domains that the Clever Logger gateway currently needs access to.
| Domain / IP | Details |
|---|---|
|
gateway.prod.temperatureapi.com |
TCP port 443 (HTTPS) |
|
updates.prod.temperatureapi.com |
TCP port 443 (HTTPS) |
|
time.prod.temperatureapi.com |
TCP port 80 (HTTP) UDP port 123 (NTP) |
|
time2.prod.temperatureapi.com |
TCP port 80 (HTTP) UDP port 123 (NTP) |
|
time3.prod.temperatureapi.com |
TCP port 80 (HTTP) UDP port 123 (NTP) |
|
one.one.one.one (1.1.1.1) dns.google (8.8.8.8) |
TCP port 53 (DNS) UDP port 53 (DNS) Optional – see details above about DNS |
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.
Security
We have an article specifically on the security aspect of Clever Logger here.
Basically:
- 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.
