Skip to content

Monitors

A monitor listens to what the gateways say about themselves, with no page open: their connection, battery, network, device, repeaters and readouts. The bench keeps all of it, so the card of each gateway and its Messages are always current, also the next day. A monitor starts again by itself when the bench restarts.

A monitor hears no meter telegram, and it never asks for a readout, so it can watch gateways that another system reads. It sends nothing to a gateway by itself: only the actions you ask for in a gateway's card.

Only an administrator has the Monitors tab.

Adding a monitor

Add a monitor opens a window with three fields.

Name
What the list calls it.
Preset
The broker and its password.
Gateways
Optional. One or more gateway ids, separated by commas. Empty watches every gateway on the broker.

A new monitor starts at once. One gateway is watched by one monitor: a second monitor of the same gateway on the same broker is refused, and so is a second monitor of every gateway.

A preset that a monitor uses cannot be deleted. Delete the monitor first, or give it another preset.

The list

Each row says what the monitor watches, and:

State
Running, No broker connection or Stopped. On No broker connection, move the pointer over it to read why.
Online
How many of its gateways are online now, of how many it has a card for.
Last message
When a gateway last said something.

Press a monitor's row to see its screen. In the row's Actions menu, Stop and Start stop and start it. Change changes its fields, and has Delete. What the gateways said stays when a monitor is deleted.

What a new session is told

A session you open while a monitor runs on the same broker takes what the monitor knows. The gateway shows Online at once, and a readout under way shows as running, until the time it said. Without a running monitor, the session learns this when the gateway next sends a message.

Stop the readout ends such a readout, whoever asked for it. Closing the session does not end it.

Telegrams from before you opened the session are not shown. After a restart of the bench, the monitor knows nothing until each gateway speaks again.

The screen of a monitor

It is the page of a session, with only what a monitor does:

  • a table of the gateways, one row each: its state, when it was last heard, its next connection, the start of its next booked readout, its battery, how long the battery has left, its signal (RSRP), its network and its firmware. A clock before the id says the gateway has something in Queued actions, and its tooltip says what. The clock is grey when all of it was sent and only waits for the gateway to do it. After it, a readout mark is orange when a readout is booked and has not started, and green while a readout runs, whoever asked for it. Its tooltip says when. The bench knows a booked readout only if the monitor was running when it was booked. Next connection and Next readout are red when they are more than five minutes ago: the gateway did not connect, or the readout did not start, when it should have. A readout that is running is not red. Move the pointer over a cell for more. Click a header to order the table by it, and again for the other way. Search shows only the gateways that match any of the values typed, separated by spaces, commas, semicolons or lines: an id, a name, a word of the notes, a firmware, an ICCID or an operator. 11317663;11317579 shows those two gateways. The × in the box empties it. A gateway that has not spoken yet shows what the bench kept for it, and it is not online until the gateway speaks. Columns hides the columns you do not need, and shows Name, Reason, Schedule, Voltage, Lowest voltage, Peak current, Temperature, Network, ICCID, Last error and the counts the gateway keeps, which are hidden at first: Broker connections, Failed broker connections, Messages sent, Messages failed and Messages received since its last restart, and its Restarts. The ICCID opens the SIM in the SIM bench. This browser keeps the choice, and Reset at the bottom of the menu puts back the columns shown at first;
  • click a row to open the gateway's card, with Messages: what the gateway said, in any session, and kept by the bench;
  • select gateways with the box at the start of each row, or all those shown with the box in the header. Schedule connection, Restart and Update the firmware then act on every gateway selected. These buttons stay at the bottom of the window while the table is longer than the window, so no scrolling is needed. On a phone they are in one menu, Actions. A gateway selected and hidden by the search or a filter is not sent anything. Once a command is sent, no gateway is selected any more; a refused command keeps the selection;
  • Queued actions: what a gateway's card asked for and the gateway does not have yet;
  • Gateway raw data: every message the monitor heard since it started, and its Raw data export;
  • Export, then Gateways: the rows the table shows, in its order, as a CSV file, with every column, also the hidden ones. Times are in this browser's time.

The card of a gateway has the actions of a session's card, except the readout's: Restart, Update the firmware, Schedule connection, New battery, Reset the modem, eDRX and Measure again. An action for a gateway that is not connected waits until it connects, also after the bench restarts. Stopping the monitor drops what waits.

There is no Readout panel, no list of meters, no signal map, and no export of telegrams.

Back leaves the monitor running, and the browser's Back button does the same: it shows the Monitors tab. The address of a monitor's screen is a link that an administrator can send to another administrator or open in another tab. A monitor that is stopped has no screen, so its link says so until the monitor is started.

Battery life

The bench keeps one sample of each gateway's battery for each day: the used capacity the gateway counts, and its full capacity. Battery life in the table is how long the battery has left at the use of the last 30 days. Move the pointer over it to see that use, in mAh a day, and the days it is taken from. Click the header to see the batteries that end first at the top.

  • Nothing is shown before a gateway has sent seven days of samples.
  • The estimate assumes the gateway keeps its schedule and its use. A readout, or connections more often, make it shorter. So does cold weather.
  • A gateway on an older firmware does not say its capacity. The bench then computes it from the charge, once the charge is 95 % or less, and the tooltip says so.
  • After a new battery, only the samples of the new battery are read. One low sample between two higher ones is not taken as a new battery.

On the card, Battery history draws the charge day by day, with a dot for each sample; move the pointer over a dot for its date and charge. A grey dashed line marks a restart, and an orange line a firmware update; move the pointer over one to see when, and why the gateway restarted or which versions.

High use, in red in place of the battery life, marks a gateway that used 10 mAh or more on each of its two newest quiet days: days with one connection and no readout, restart or firmware update. A normal quiet day uses 1 to 2.5 mAh. A restart usually ends it. The High use chip on the line Battery shows only these gateways, so you can select them and press Restart. After a restart the mark goes, and it comes back only if the next two quiet days use as much again.

Uptime

Uptime is a column of the table, hidden at first: tick it in Columns. It shows the last 30 days of each gateway, a mark for each day, the oldest on the left. The gateway's window shows the same bar, larger, at the bottom.

Bright green
A readout was booked that day, and the gateway finished it.
Bright red
A readout was booked that day, and the gateway did not finish it.
Light green
No readout was booked, and the gateway connected.
Light red
No readout was booked, and the gateway did not connect.
Grey
Not known: the monitor was not listening, the day is not over, or the gateway had not been heard yet.

Move the pointer over a mark to see its day and what it means. Click the header to see the gateways with the most red days at the top.

  • A day starts at 23:45 the evening before. A gateway scheduled at midnight may connect a few minutes early, and that connection belongs to the next day. Days are in Italian time.
  • A day is known when the monitor was connected to its broker for at least 90% of it. A short restart of the bench does not turn a day grey.
  • Any readout counts, whoever booked it: another system, a logger, or somebody in a session. A booking replaced by a newer one, or stopped before it started, does not count.
  • The days are kept by the bench as the messages arrive, so the bar is ready for thousands of gateways. When the feature was installed, the past days were filled from the messages the bench already kept. For those days the bench could only guess when it was listening.