Release notes
What changed in each version of the device library.
1.4.0
Security
- Over WiFi the device connects only after the server proves it is the MaxwellTrack cloud. The cloud's root certificates are built in, so nothing needs setting up. ESP8266 and Pico W set their clock from the internet first, so their network must allow time requests.
setRootCA()replaces the roots for a private deployment. - Remote updates are signed. A board installs only an image signed by MaxwellTrack and keeps its current code otherwise; the build history shows bad signature. Boards on earlier versions keep receiving updates as before.
New
- Local rules: set up on the device's Controller tab, they run on the board with or without network, including a network-loss rule that puts outputs in a safe state.
- Modbus equipment on an RS-485 port with
useModbus(port, dePin): meters, drives and controllers chosen in the console, reported when they change. - Rules and equipment are kept in flash, so the board keeps running them after a power cut without network.
- Cameras:
sendImage()andonCameraRequest()for ESP32 camera boards, shown in the Image and Video widgets. - Readings sent from the offline buffer carry their age, so the console shows them at the time they were measured.
New boards: Arduino UNO R4 WiFi, UNO R4 Minima and Nano R4. The UNO R4 WiFi, MKR WiFi 1010, Nano 33 IoT and Raspberry Pi Pico W / Pico 2 W connect over WiFi with the same sketch as an ESP32. See Supported boards.
Improvements: Uno and Mega have about 1 KB more flash for your own code. A board that restarts quickly no longer risks a reading being taken for one it already sent. The Uno and Blue Pill are otherwise unchanged.
1.3.1
- Remote updates report their progress to the build history: received, downloading with a percentage, restarting, and the reason when an update cannot be installed.
- Remote updates download faster over WiFi, and no longer fail on ESP8266.
- ESP32 on a cellular modem: a stalled update continues from where it stopped instead of starting over.
- Raspberry Pi Pico and Pico 2 update remotely through their modem.
- Every update is checked against its checksum before the board switches to it.
1.3.0
- One library to install: no separate helper library is needed any more.
- Available in the Arduino IDE Library Manager.
- Removed the old name of
connectionState().
1.2.0
- Update required: earlier versions can no longer connect to the MaxwellTrack IoT Cloud.
MAXWELLTRACK_FW_VERSIONsets the code version shown in the console.- Improved relay control in the ControlFromDashboard example.
1.1.0
New boards: STM32 (F1, F4, G0, H7 and the same CPUs), Raspberry Pi Pico and Pico 2, Arduino Zero and MKR, Arduino Mega and Uno, over a cellular modem. ESP32 Arduino core 2.x as well as 3.x. PlatformIO support.
New calls: onWrite(pin, handler), onConnectionChange(handler), setRootCA(pem), connectionState(), queuedMessages(), droppedMessages(), setQueueSize(), setMaxPayload(), setHeartbeatInterval(). write() accepts every integer type and returns whether the message was accepted.
Improvements:
- The offline buffer is one fixed block of memory, so long offline periods no longer fragment the heap, and messages are always sent in order.
- A message too large to send is refused at once instead of blocking every message behind it.
- Reconnects wait from 2 to 60 seconds with a random spread per device.
- Text values are escaped, so quotes in a value can no longer break a message.
- Log output goes to the same serial port as the sketch.
- A sketch's own
MaxwellTrackClass MaxwellTrack(client);reliably replaces the built-in WiFi instance.
1.0.0
- First release.
Something unclear or out of date on this page? Tell support.
