Are You Adding or Editing a Location?
If you are adding a new location to your Clever Logger account – you are in the right place!
If you are simply wanting to edit an existing location and its alerts please read “Editing a Clever Logger Location“.
Step 1 - Adding a new location
From your Clever Logger portal, Locations in the menu.
You will see a list of all locations currently in the system.
Press the “Add A Location” button at the top right of the screen.
If you can not see the button, then you do not have sufficient security privileges for the site. See the section on permissions for more information.
Step 2 - Select a device
You will be shown a list of loggers that have been identified at the site but not assigned to a location.
Normally there should be only one device in the list. If you can’t see the device in the list, make sure it is turned on.
The timer in the top right corner indicates when the list will automatically refresh. You may need to wait 30 seconds for the logger to appear in the list.
Press “Select Device” to continue to the next screen
Step 3 - Presets
Presets are aimed to help the majority of our customers quickly set up a new logger without having to know everything.
If the type of device you are trying to monitor is in the list then press “Select Preset“.
If you don’t see the type of device in the list, or you want to customise the settings then select custom.
Step 4 - Location Information
Name: The name of the logger is anything that you will find useful for identifying it in the list and in reports. Examples of names may include:
- The room number
- The brand of the fridge
- The size of the fridge
- The shelf
- The vehicle registration number
Description: The description is just there for you to use for anything you like. You won’t see it in most of the screens or in reports. It’s useful for storing information like when you purchased the logger or fridge, and any other comments you may want others to know about in the future.
The logger interval is how often the temperature will be stored in the database. It is important that you get this reasonably right.
If you sample too slowly,
- you may miss a critical event. For example, if you sample once every 12 hours then it is possible for your fridge to warm up, be too hot for 10 hours, and cool down again without you knowing.
- you can’t accurately work out how long a problem lasted. For example, if you sample once an hour and you have one high reading, you don’t know if it lasted 5 minutes or 1 hour and 55 minutes. All you know is 1 hour ago it was good and one hour later it was good again. That’s 2 hours apart!
If you sample too quickly then
1. your reports fill up with a huge amount of data. It’s not the end of the world, but is a bit overwhelming. It also uses more data but it’s not like we are streaming video 24/7.
2. you will just see the same temperature being repeated because temperature really doesn’t change that fast.
We generally recommend once every 5 minutes.
Some people make the mistake of thinking they are replacing a twice daily min/max thermometer with a logger and set the sample rate to 12 hours. This is NOT how loggers work. You need to set the sample rate to something useful like 5 minutes. I can’t stress this enough.
The lowest we would recommend setting it would be 15 minutes. I know someone who set it to 1 hour but they literally said “I don’t care what the temperature is, I just need to show the boss a reading once an hour”.
Step 4 - Set temperature alerts
You will see the following screen twice – once for the low temperature alert and once for the high temperature alert. For humidity loggers you will see it for low and high humidity alarms.
If you don’t want to be notified if the temperature gets too low or high then turn the “Alarms Enabled” off.
The threshold is the temperature at which the alarm will be generated.
For vaccine fridges the temperature range is typically 2°C to 8°C. (NOTE: That is 2°C and not -2°C).
For food fridges the temperature range is typically 0°C to 5°C. The food standards are written around 5°C for potentially hazardous foods.
To avoid false alarms, it is possible to specify a delay before an alarm is generated. If the temperature returns back to normal within that delay period then no alarm is created.
This is useful for where a fridge may be regularly opened and is continually nudging the upper limit. You won’t have numerous alarms, but if the fridge fails, or the door left open then you will be notified.
A 10 to 15 minute delay is recommended for most applications.
The notification group is who will be notified in the event of the alarm occurring.
Depending upon the number of notification groups in the system, you may see a list of all notification groups, or the list of only the ones assigned to the location at the moment.
A notification group is a collection of users. By default, the first notification group will contain all users for the system. For many users, there will only be the one person (you) in the notification group. For larger sites you can have a site manager in each notification group, or possibly a site manager and regional manager.
Notification groups also support two settings:
– Delay: This is how long after the alarm was created that the notification group will start to be notified. This is useful for escalating the alarm. For example, you can have one notification group that is immediately notified, and another group that is notified if there is no response after an hour. This gives the first person an hour to respond, and then starts to annoy other people. NOTE: If the alarm is acknowledged within the delay period, the notification group will NOT be notified.
TIP: You can have people being notified via email without being notified on their phone. This is a handy way to notify them without interrupting them.
– Repeat interval: If the alarm is not acknowledged within the repeat interval, the notification group will be notified again. This is our “muted” or “nag” feature. The system will continue to try and contact you until the alarm is acknowledged. For critical things like the temperature alarm, the interval should be reasonably frequent (e.g. hourly), but for less critical alarms like low battery it can be daily or slower.
TIP: Acknowledging the alarm will stop the escalation. The temperature does not have to return to normal. We are just trying to make sure someone knows about it.
Step 5 - Low battery alarm
The low battery alarm is effectively the same as a temperature alarm in regards to notification groups.
We strongly recommend that you have a repeat interval somewhere between 1 day and 1 week.
Step 7 - Offline Alarm
Set the Delay Before Offline Alarms.
This is the time the system will wait between when the Logger loses contact with the Gateway and when the first alert is sent out.
Setting a delay here will help prevent false positives if something temporarily blocks the signal between the Logger and the Gateway.
Select an already created Notification Group to be alerted about Offline and Battery issues, or create a new group.
Press Save to continue.
Step 7 - Review and Confirm
Review the settings you have chosen and hit the Create button to save your Location.
Device = Logger = Location (sort of)
It can be helpful to understand that the terms Device, Logger and Location are very similar.
A Device is any device that can be seen by the Gateway. (At present, this is always a Logger.) We use this term for an item in the Devices list.
A Logger is what we call the actual physical tag that goes into the fridge.
A Location is a configuration. This includes the identification of a Logger. Locations appear in the Locations page.