Express Post guarantee temporarily suspended – Australia Post announce Express Post may not always meet the next business day delivery standard. Read more
rocket

Getting Started

cogs

Configuring Clever Logger

graph

Using Clever Logger

clouds

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.
IT-department

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

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

Ethernet

  • 100Base-T and Gigabit
  • Power Over Ethernet (POE) adaptor is available on request. The device does not directly support POE. The external adaptor is relatively small and compact, and was the most cost effective way of providing POE. An inbuilt POE option was considered but was much more expensive and added to the size of the gateway.

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 currently 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. 

NTP

  • 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.

Domains

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

Domain Details Notes
api.cleverlogger.com
HTTPS - TCP Port 443
Will be made redundant soon
mender.cleverlogger.com
HTTPS - TCP Port 443
Will be made redundant soon
mender-s3.cleverlogger.com
HTTPS - TCP Port 443
Will be made redundant soon
timehtp.cleverlogger.com
TCP port 80 (HTTP)
UDP port 123 (NTP)
Will be made redundant soon
gateway.prod.temperatureapi.com
HTTPS - TCP Port 443
updates.prod.temperatureapi.com
HTTPS - TCP Port 443
downloads.prod.temperatureapi.com
HTTPS - TCP Port 443
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)

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

It is possible to remove a site from the automatic upgrade cycle, but our preference is to have all gateways running on the latest version of firmware. 

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 VPN allow you to totally isolate our gateways if required.

Other "How To" articles

Frequently Asked Questions