2.2.0: the device list and device page, the profile editor, the Commands tab and the device log
2.2.0 is out, and most of what I worked on this cycle is in it.
The device list and the device page. Devices has a new list, and each device has a page. The page’s own tabs are always there; the others appear when their module is on, you have the permission and they apply to the device’s profile. The alarm screens came with this release too. The device page header now shows the device’s last IP address. See The Devices list and the device page.
Device profiles got their own screens: a list and an editor. Device profiles goes through the tabs.
The Commands tab. Pick a command, send it, and follow it until the device answers. Each command keeps its state (Queued, Sent, Delivered, then Successful, Failed, Timed out and so on) and you can open it for the request and the response. Sending commands to devices.
The device log. The Log tab shows every change to a device, with who made it, in the same timeline as its connects and disconnects. Connection status and activity lists what is recorded.
Is the IP address what the device reports about itself, or what you see? Most of ours sit behind a 4G router.
What we see: the address of the newest connection. For HTTP and polled devices, which don’t hold a connection, it’s the address of the newest activity. Behind your router you’ll see the public address the connection comes from (the router’s, or the mobile operator’s NAT address if it puts one in front), not the 192.168 one the device has.
Good that Timed out is worded as “outcome unknown” and not as failed. On a weak cell link our boards often run the relay command and the reply is what gets lost.
That’s why it reads that way. One thing for the firmware side while you’re at it: a command can arrive twice, so remember at least the last 32 request ids for 10 minutes and don’t run the same id again.
How far back does the Log tab go? One of our sites drops off a couple of nights a week and I want to line it up with the router’s own logs.
Connection history is kept for 30 days, and Load more goes further back within that. Devices whose profile uses Last seen only write no connect and disconnect rows, so check the profile’s online rule if the tab looks empty.
Used the Log tab yesterday for a pump controller that kept flipping online and offline. Every few minutes it said “Taken over by a new session”. Turned out two units had been flashed with the same credential. Would have taken me a day without it.
- You must be logged in to reply to this topic.
Join the conversation
Sign in to ask and answer, like helpful posts and mark the reply that solved your problem. Every contribution earns points and levels.

