EnOcean releases several updates per year of the SmartServer IoT software to add new functionality, enhance performance, and fix reported problems. Due to high demand, the SmartServer IoT hardware is built in large production runs. As a result, when you purchase a SmartServer IoT, it may not come with the latest version of the SmartServer software. This page describes and provides download links for all the available SmartServer IoT software releases, with the most recent release at the top. If you receive a new SmartServer IoT, you can compare the software version in your SmartServer IoT to the latest software release identified below. To ensure you get the best performance and most stable operation, always update to the latest version of the SmartServer software. See Determining SmartServer Software Version Compatibility before updating to verify compatibility for your update.

Release Summary:

License

The SmartServer software is subject to the terms and conditions described in the license available at Embedded Software License Agreement.

Certain components of the SmartServer software are subject to the terms and conditions described in the open source and third-party licenses available at Open Source and Third-Party License Terms.

Example software for the SmartServer is subject to the terms and conditions described in the license available at github.com/izot/smartserver-iot/blob/master/LICENSE.md.

Current Stable Release

Downloads for the current stable release (SmartServer IoT 3.5 Update 2) are available here:

Descriptions and direct links for the current and previous releases are available in the following sections.

SmartServer IoT 4.0

Release Date: May 23, 2023

Versions:

SmartServer IoT Software: 4.00.029
SmartServer Remote CMS (beta): 4.00.029
IzoT Net Export Utility: 1.60.001
IOX: 2.30.005
Platform
- Ubuntu Linux: 20.04
- Ubuntu kernel: 5.4
- Node.js: 14
- Java VM: 11
- Python: 3.8
- PHP: 8.0
- Karaf: 4.2.16
- Log4j: 2.17.1
- Jetty Web Server: 9.4.43
- NginX: 1.20.2
- PostgreSQL: 12.9
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revision F (Quad Core ARM Processor) or later

Downloads:

Changes:

Create sustainable systems with EnOcean device support. EnOcean devices provide sensor data for the Internet of Things (IoT) with resource-saving energy harvesting technology. EnOcean devices include maintenance-free wireless switches and sensors, which gain their energy from their surroundings – from movement, light, or temperature. No batteries or cables are required.
Leverage long-range, low-power, and wide-area wireless LoRaWAN devices to create smart city, smart building, and agricultural applications.
Use the Modbus FC16 function code to write a block of contiguous registers in a Modbus device. (AP-10579)
Improve device identification by specifying product names and descriptions when you are using the SmartServer BACnet Server. (AP-10321)
Use higher-resolution latitude and longitude entry to get accurate placement of devices on the SmartServer map. (AP-10607, LUM-9756)
Accelerate application downloads when using LON power line repeating. (AP-10450)
Improve security with the following security enhancements:
- Provide single sign-on support for your users with SAML support for the Remote CMS. (AP-10622, AP-10628)
- Simplify password management in systems using the Remote CMS and multiple SmartServers. The Remote CMS now synchronizes the SmartServers attached to it when you change the CMS access password. (AP-10618)
- Use an HTTP proxy for outgoing HTTP connections. (AP-10208, LUM-9841)
- Recover from certificate renewal failures due to a temporary loss of Internet connectivity. (AP-10521)
The following problems have been fixed:
- LON device polling was disrupted for 15 minutes if the network cable was removed and re-connected on the LAN or WAN port. (AP-10724)
- Passwords starting with a “$” character failed. (LUM-9849)
- License downloads sometimes failed. (AP-10107)

Warnings:

The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Backing Up, Restoring, and Cloning the SmartServer.
The SmartServer 4.0 software will not run on SmartServer hardware with a dual core processor. You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that may not be compatible with this release.
You can downgrade a SmartServer running SmartServer 4.0 to an earlier release if the earlier release is compatible with your SmartServer hardware. However, due to security improvements in SmartServer 4.0, you must run the prep_for_3.x.sh script before or after you re-image your SmartServer. See step 3 here here for more information. (AP-11274)
In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)
With the factory configuration, you cannot send a Service message from a SmartServer to an IP-852 channel when you press a Service/Connect or Send button on the Configuration page LON tab. To enable the SmartServer to send a Service message on an IP-852 channel, add an outdoing rule in the SmartServer firewall as described here. (AP-11241)
If you update a datapoint using the CMS Datapoints widget, there may be up to a six second delay before the datapoint is updated due to throttling in the SmartServer. (AP-11182)
The column sort buttons do not work in the CMS Datapoints widget. (AP-11189)
We have added regions as a new type of context in the CMS. The new feature is not fully implemented yet. As a result, you cannot assign devices to regions. (AP-11349)
In some cases, a combination of certain datapoint property settings and alarm configuration can result in the SmartServer logging more alarms than expected in the Alarms widget. (AP-11328)
You cannot set the latitude and longitude for a SmartServer by typing new values in the Devices widget. To change the latitude and longitude for a SmartServer, you can either drag the SmartServer icon to a new location on the map in the Devices widget, or you can enter new values in the Planning widget. (AP-11085)
In some cases, if you delete a discovered device and later re-discover the device, the device will be shown with a gray icon in the CMS Devices widget. The gray state indicates the device is not fully defined. (AP-11310)
In some cases, if you provision a LON device in the CMS Devices widget, you may see yellow notification messages reporting communication failures. If the device icon changes to green, the provisioning succeeded. (AP-10794)
In some cases, the CMS Sequencing widget may get stuck with an Adding Flows to Workspace message. Restart the SmartServer to eliminate the message. (AP-11279)
In some cases, connections with many destinations may fail to update all destinations. If you have any connections with many destinations, test them to verify all destinations are updated as expected. If you observe any failed updates, break up the connection into multiple connections with fewer destinations per connection. (AP-9259)
In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned. You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)
You cannot delete a device that has any datapoints in a calendar event. To recover after deleting such a device, add back the device, delete its datapoints in any calendar events, and then delete the device again. (LUM-9443)

SmartServer IoT 3.6 Update 5

Release Date: May 30, 2023

Versions:

SmartServer IoT Software: 3.65.001
SmartServer Remote CMS (beta): 3.65.001
IzoT Net Export Utility: 1.60.001
IOX: 2.30.005
Platform
- Ubuntu Linux: 20.04
- Ubuntu kernel: 5.4
- Node.js: 14
- Java VM: 11
- Python: 3.8
- PHP: 8.0
- Karaf: 4.2.16
- Log4j: 2.17.1
- Jetty Web Server: 9.4.43
- NginX: 1.20.2
- PostgreSQL: 12.9
SmartServer hardware compatibility: Model 72201R-240 or 72201R-248, Hardware Revision F (Quad Core ARM Processor) or later
U70 compatibility: U70 Firmware 1.0 or 2.0

Downloads:

Changes:

The following problem has been fixed:
- In some cases, the U70 LON PL-20 USB Network Interface stopped functioning and required a reset to become operational. The fix requires U70 Firmware 2.0 or later as described in https://enoceanwiki.atlassian.net/wiki/spaces/IEC/pages/170492006. (AP-11255)

Warnings:

You can update an installed SmartServer running an earlier release of the SmartServer software to the SmartServer 3.6 Update 5 software. However, after you have installed the SmartServer 3.6 Update 5 software you cannot go back to an earlier release without either restoring a full system backup with the earlier release, or re-imaging your SmartServer with an earlier release. Always backup your SmartServer prior to updating it to the SmartServer 3.6 Update 5 software. To go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page. Links to prior releases are available on this page. (LUM-8271)
The SmartServer 3.6 Update 5 software will not run on SmartServer hardware with a dual core processor. You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that may not be compatible with this release.
IzoT CT 4.2 or a newer version, or IzoT Net Server 4.2 or a newer version, is required to use the IzoT Net Export Utility.
In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
In some cases, connections with many destinations may fail to update all destinations. If you have any connections with many destinations, test them to verify all destinations are updated as expected. If you observe any failed updates, break up the connection into multiple connections with fewer destinations per connection. (AP-9259)
In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned. You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)
You cannot delete a device that has any datapoints in a calendar event. To recover after deleting such a device, add back the device, delete its datapoints in any calendar events, and then delete the device again. (LUM-9443)

SmartServer IoT 3.6 Update 4

Release Date: March 15, 2023

Versions:

SmartServer IoT Software: 3.64.001
SmartServer Remote CMS (beta): 3.64.001
IzoT Net Export Utility: 1.60.001
IOX: 2.30.005
Platform
- Ubuntu Linux: 20.04
- Ubuntu kernel: 5.4
- Node.js: 14
- Java VM: 11
- Python: 3.8
- PHP: 8.0
- Karaf: 4.2.16
- Log4j: 2.17.1
- Jetty Web Server: 9.4.43
- NginX: 1.20.2
- PostgreSQL: 12.9
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revision F (Quad Core ARM Processor) or later

Downloads:

Changes:

The following problems have been fixed:
- In some cases, the latitude and longitude of the SmartServer was incorrectly reset to 0, 0. (AP-10835)

Warnings:

You can update an installed SmartServer running an earlier release of the SmartServer software to the SmartServer 3.6 Update 4 software. However, after you have installed the SmartServer 3.6 Update 4 software you cannot go back to an earlier release without either restoring a full system backup with the earlier release, or re-imaging your SmartServer with an earlier release. Always backup your SmartServer prior to updating it to the SmartServer 3.6 Update 4 software. To go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page. Links to prior releases are available on this page. (LUM-8271)
The SmartServer 3.6 Update 4 software will not run on SmartServer hardware with a dual core processor. You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that may not be compatible with this release.
IzoT CT 4.2 or a newer version, or IzoT Net Server 4.2 or a newer version, is required to use the IzoT Net Export Utility.
In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
In some cases, connections with many destinations may fail to update all destinations. If you have any connections with many destinations, test them to verify all destinations are updated as expected. If you observe any failed updates, break up the connection into multiple connections with fewer destinations per connection. (AP-9259)
In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned. You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)
You cannot delete a device that has any datapoints in a calendar event. To recover after deleting such a device, add back the device, delete its datapoints in any calendar events, and then delete the device again. (LUM-9443)

SmartServer IoT 3.6 Update 3

Release Date: February 13, 2023

Versions:

SmartServer IoT Software: 3.63.001
SmartServer Remote CMS (beta): 3.63.001
IzoT Net Export Utility: 1.60.001
IOX: 2.30.005
Platform
- Ubuntu Linux: 20.04
- Ubuntu kernel: 5.4
- Node.js: 14
- Java VM: 11
- Python: 3.8
- PHP: 8.0
- Karaf: 4.2.16
- Log4j: 2.17.1
- Jetty Web Server: 9.4.43
- NginX: 1.20.2
- PostgreSQL: 12.9
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revision F (Quad Core ARM Processor) or later

Downloads:

Changes:

The following problems have been fixed:
- A default SNTP server was not specified. The default is now pool.ntp.org. (LUM-9853)
- The following special characters were not supported in strong passwords: “$”, “/”, “^”, and “&”. (LUM-9910)
- In some cases, datapoint updates failed after adding schedule events with the same datapoints. (AP-10478)
- Responses to BACnet broadcast messages sometimes failed. (AP-10532)
- Connections to IOX datapoints sometimes failed. (AP-10548)

Warnings:

You can update an installed SmartServer running an earlier release of the SmartServer software to the SmartServer 3.6 Update 3 software. However, after you have installed the SmartServer 3.6 Update 3 software you cannot go back to an earlier release without either restoring a full system backup with the earlier release, or re-imaging your SmartServer with an earlier release. Always backup your SmartServer prior to updating it to the SmartServer 3.6 Update 3 software. To go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page. Links to prior releases are available on this page. (LUM-8271)
The SmartServer 3.6 Update 3 software will not run on SmartServer hardware with a dual core processor. You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that may not be compatible with this release.
IzoT CT 4.2 or a newer version, or IzoT Net Server 4.2 or a newer version, is required to use the IzoT Net Export Utility.
In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
In some cases, connections with many destinations may fail to update all destinations. If you have any connections with many destinations, test them to verify all destinations are updated as expected. If you observe any failed updates, break up the connection into multiple connections with fewer destinations per connection. (AP-9259)
In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned. You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)
You cannot delete a device that has any datapoints in a calendar event. To recover after deleting such a device, add back the device, delete its datapoints in any calendar events, and then delete the device again. (LUM-9443)

SmartServer IoT 3.6 Update 2

Release Date: January 11, 2023

Versions:

SmartServer IoT Software: 3.62.001
SmartServer Remote CMS (beta): 3.62.001
IzoT Net Export Utility: 1.60.001
IOX: 2.30.005
Platform
- Ubuntu Linux: 20.04
- Ubuntu kernel: 5.4
- Node.js: 14
- Java VM: 11
- Python: 3.8
- PHP: 8.0
- Karaf: 4.2.16
- Log4j: 2.17.1
- Jetty Web Server: 9.4.43
- NginX: 1.20.2
- PostgreSQL: 12.9
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revision F (Quad Core ARM Processor) or later

Downloads:

Changes:

The following problems have been fixed:
- In some cases, when using LON power line repeating, LON devices were deleted on startup. (AP-10397)
- Loading an image to multiple devices sometimes failed. (AP-10437)

Warnings:

You can update an installed SmartServer running an earlier release of the SmartServer software to the SmartServer 3.6 Update 2 software. However, after you have installed the SmartServer 3.6 Update 2 software you cannot go back to an earlier release without either restoring a full system backup with the earlier release, or re-imaging your SmartServer with an earlier release. Always backup your SmartServer prior to updating it to the SmartServer 3.6 Update 2 software. To go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page. Links to prior releases are available on this page. (LUM-8271)
The SmartServer 3.6 Update 2 software will not run on SmartServer hardware with a dual core processor. You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that may not be compatible with this release.
IzoT CT 4.2 or a newer version, or IzoT Net Server 4.2 or a newer version, is required to use the IzoT Net Export Utility.
In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
In some cases, connections with many destinations may fail to update all destinations. If you have any connections with many destinations, test them to verify all destinations are updated as expected. If you observe any failed updates, break up the connection into multiple connections with fewer destinations per connection. (AP-9259)
In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned. You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)
You cannot delete a device that has any datapoints in a calendar event. To recover after deleting such a device, add back the device, delete its datapoints in any calendar events, and then delete the device again. (LUM-9443)

SmartServer IoT 3.6

Release Date: December 29, 2022

Versions:

SmartServer IoT Software: 3.60.016
SmartServer Remote CMS (beta): 3.60.016
IzoT Net Export Utility: 1.60.001
IOX: 2.30.005
Platform
- Ubuntu Linux: 20.04
- Ubuntu kernel: 5.4
- Node.js: 14
- Java VM: 11
- Python: 3.8
- PHP: 8.0
- Karaf: 4.2.16
- Log4j: 2.17.1
- Jetty Web Server: 9.4.43
- NginX: 1.20.2
- PostgreSQL: 12.9
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revision F (Quad Core ARM Processor) or later

Downloads:

Changes:

Add custom tags to datapoints by device type to simplify interfaces with AI, building analytics, and other applications. Device-type-specific datapoint tags can save you hundreds of hours of integration time. You can create your own tags so that you can use your favorite ontology such as Haystack or Google Digital Building Ontology.
Use a common set of contexts in the Remote CMS across multiple SmartServers. Using shared contexts, you can have high-level contexts such as sites and buildings that contain multiple SmartServers, and low-level contexts such as floors and rooms that are each managed by a single SmartServer.
Enhance Remote CMS security with the new wired IEEE-802.1X network access control and alternate ACMEv2 PKI system support options. The Remote CMS uses LetsEncrypt by default. With the new alternate PKI option, you can use other ACMEv2-compatible PKI systems such as KeyFactor.
Get control of log sizes with the new data and event log pruning interfaces.
Find what you need with new negative filters. Use the new “Not” option to define a display filter that only shows items that do not match the criteria you specify.
Increase productivity with faster BACnet device discovery.
The following problems have been fixed:
- Increased frequency of certificate renewal tests from weekly to daily. (AP-10384)
- In some cases, connections for LON power line devices were deleted and recreated after the SmartServer restarted. (AP-10302, LUM-9794)
- In some cases, time and time zone changes failed. (AP-10215, AP-10218, LUM-9474, LUM-9490, LUM-9784)
- In some cases, datapoint updates were not correctly logged. (AP-10328, LUM-9780)
- Google maps sometimes fail to display correctly. (LUM-9574)
- Writing a Null value to the priority array sometimes fails. (AP-9783)
- BACnet discovery failed to discover BACnet devices with duplicate product names but different program IDs. (LUM-9364)
- In some cases, BACnet datapoints could not be updated. (AP-10252)
- The BACnet router sometimes failed when the LAN or WAN connection was removed. (AP-9750)
- Device type package (DTP) files including DLA files sometimes failed on import. (LUM-9665)

Warnings:

You can update an installed SmartServer running an earlier release of the SmartServer software to the SmartServer 3.6 software. However, after you have installed the SmartServer 3.6 software you cannot go back to an earlier release without either restoring a full system backup with the earlier release, or re-imaging your SmartServer with an earlier release. Always backup your SmartServer prior to updating it to the SmartServer 3.6 software. To go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page. Links to prior releases are available on this page. (LUM-8271)
The SmartServer 3.6 software will not run on SmartServer hardware with a dual core processor. You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that may not be compatible with this release.
IzoT CT 4.2 or a newer version, or IzoT Net Server 4.2 or a newer version, is required to use the IzoT Net Export Utility.
In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
In some cases, connections with many destinations may fail to update all destinations. If you have any connections with many destinations, test them to verify all destinations are updated as expected. If you observe any failed updates, break up the connection into multiple connections with fewer destinations per connection. (AP-9259)
In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned. You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)
You cannot delete a device that has any datapoints in a calendar event. To recover after deleting such a device, add back the device, delete its datapoints in any calendar events, and then delete the device again. (LUM-9443)

SmartServer IoT 3.5 Update 2

Release Date: November 20, 2022

Versions:

SmartServer IoT Software: 3.52.003
SmartServer Remote CMS (beta): 3.52.003
IzoT Net Export Utility: 1.60.001
IOX: 2.30.005
Platform
- Ubuntu Linux: 20.04
- Ubuntu kernel: 5.4
- Node.js: 14
- Java VM: 11
- Python: 3.8
- PHP: 8.0
- Karaf: 4.2.16
- Log4j: 2.17.1
- Jetty Web Server: 9.4.43
- NginX: 1.20.2
- PostgreSQL: 12.9
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revision F (Quad Core ARM Processor) or later

Downloads:

Changes:

Provision, manage, monitor, and control devices provisioned onto multiple SmartServers using a single interface with the new beta SmartServer Remote CMS. When you set up a new SmartServer you now have the choice of setting up a Local CMS, which is the CMS available in previous releases, or setting up the new beta Remote CMS. You install the Remote CMS on a host computer that you provide, and then set it up to work with multiple SmartServers in one seamless and cohesive system. See Local CMS vs. Remote CMS for more information.
Multiple security enhancements including the following: (LUM-9586, LUM-9587, LUM-9588, LUM-9589, LUM-9591)
- A larger optional security banner for the login dialog. See Adding an Access Warning Banner for details.
- Enhanced security audit events. See Monitoring System Audit Events for details.
- An updated version of Karaf with an updated version of Apache Log4j.
- An expanded SmartServer security hardening guide.
The following problems have been fixed:
- In some cases, connections for LON power line devices were sometimes removed. (LUM-9557, LUM-9562)
- Some of the files included in a device type package (DTP) file were not being imported. (LUM-9665)
- In some cases, the source IP address reported for a logon event was incorrect. (AP-10238)

Warnings:

You can update an installed SmartServer running an earlier release of the SmartServer software to the SmartServer 3.5 Update 2 software. However, after you have installed the SmartServer 3.5 Update 2 software you cannot go back to an earlier release without either restoring a full system backup with the earlier release, or re-imaging your SmartServer with an earlier release. Always backup your SmartServer prior to updating it to the SmartServer 3.5 Update 2 software. To go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page. Links to prior releases are available on this page. (LUM-8271)
The SmartServer 3.5 software will not run on SmartServer hardware with a dual core processor. You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that may not be compatible with this release.
IzoT CT 4.2 or a newer version, or IzoT Net Server 4.2 or a newer version, is required to use the IzoT Net Export Utility.
In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
In some cases, connections with many destinations may fail to update all destinations. If you have any connections with many destinations, test them to verify all destinations are updated as expected. If you observe any failed updates, break up the connection into multiple connections with fewer destinations per connection. (AP-9259)
You cannot update IAP output datapoints (which are the same as BACnet input datapoints) from calendar events. You can update IAP input datapoints (which are the same as BACnet output datapoints). This includes writes to BACnet inputs such as BACnet AI and BI objects. (LUM-7839)
In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned. You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)

SmartServer IoT 3.5 Update 1

Release Date: October 31, 2022

Versions:

SmartServer IoT Software: 3.51.002
IzoT Net Export Utility: 1.60.001
IOX: 2.30.005
Platform
- Ubuntu Linux: 20.04
- Ubuntu kernel: 5.4
- Node.js: 14
- Java VM: 11
- Python: 3.8
- PHP: 8.0
- Karaf: 4.2.13
- Jetty Web Server: 9.4.43
- NginX: 1.20.2
- PostgreSQL: 12.9
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revision F (Quad Core ARM Processor) or later

Downloads:

Changes:

The following problems have been fixed:
- Notifications from the SmartServer to a web browser client were sometimes lost when multiple clients access the SmartServer at the same time. (LUM-9509)
- The web browser used to access the SmartServer Remote CMS would sometimes crash when creating a system with more than 4000 devices due to excessive memory usage. (LUM-9505)
- Importing datapoint properties for more than 4000 devices to the SmartServer Remote CMS would sometimes cause the SmartServers to be temporarily reported in an error condition. (LUM-9507)
- Bulk creation of devices sometimes failed. (LUM-9518, LUM-9296, LUM-9444, LUM-9495)

Warnings:

You can update an installed SmartServer running an earlier release of the SmartServer software to the SmartServer 3.5 Update 1 software. However, after you have installed the SmartServer 3.5 Update 1 software you cannot go back to an earlier release without either restoring a full system backup with the earlier release, or re-imaging your SmartServer with an earlier release. Always backup your SmartServer prior to updating it to the SmartServer 3.5 Update software. To go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page. Links to prior releases are available on this page. (LUM-8271)
The SmartServer 3.5 Update 1 software will not run on SmartServer hardware with a dual core processor. You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that may not be compatible with this release.
IzoT CT 4.2 or a newer version, or IzoT Net Server 4.2 or a newer version, is required to use the IzoT Net Export Utility.
In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
In some cases, connections with many destinations may fail to update all destinations. If you have any connections with many destinations, test them to verify all destinations are updated as expected. If you observe any failed updates, break up the connection into multiple connections with fewer destinations per connection. (AP-9259)
You cannot update IAP output datapoints (which are the same as BACnet input datapoints) from calendar events. You can update IAP input datapoints (which are the same as BACnet output datapoints). This includes writes to BACnet inputs such as BACnet AI and BI objects. (LUM-7839)
In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned. You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)

SmartServer IoT 3.5

Release Date: September 30, 2022

Versions:

SmartServer IoT Software: 3.50.026
IzoT Net Export Utility: 1.60.001
IOX: 2.30.005
Platform
- Ubuntu Linux: 20.04
- Ubuntu kernel: 5.4
- Node.js: 14
- Java VM: 11
- Python: 3.8
- PHP: 8.0
- Karaf: 4.2.13
- Jetty Web Server: 9.4.43
- NginX: 1.20.2
- PostgreSQL: 12.9
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revision F (Quad Core ARM Processor) or later

Downloads:

Changes:

Multiple security enhancements including the following: (AP-8849)
- A new Enhanced Security option is available. The option enables strong password enforcement (14 character minimum with a minimum of one uppercase, one lowercase, and one punctuation character) and disables the Secure Copy Protocol (SCP). The option is enabled by default for a new or re-imaged SmartServer. The option is disabled by default if you update a SmartServer with a software release prior to 3.5. See Enhancing Security for more information. (AP-9635, AP-9711, AP-9984, AP-10023)
- Support for a secure MQTT link using TLS between the SmartServer and the SmartServer Remote CMS has been added. TLS 1.3 is supported. (AP-6430, AP-9745, LUM-9147)
- A new capability to view login and logout events in the Alarms and Events widget is available. See Monitoring System Audit Events for details. (LUM-9068, LUM-9134)
- Duplicate HTTP strict transport security (HSTS) headers have been eliminated and a missing preload directive has been added to the HTTPS headers. (AP-8839, LUM-9069)
- The Nginx library has been updated to release 1.20.2. (AP-8836)
- The Linux apparmor and aide packages have been added. (AP-9433)
- Source routed packets, ICMP redirects, broadcast ICMP requests, and IPv6 router advertisements are now rejected. (AP-9436)
- Reverse path filtering is now enabled. (AP-9436)
- IPv4 and IPv6 loopback traffic is configured for ufw. (AP-9437)
- The capability to mount cramfs, freevxfs, jffs2, jfs, fjsplus, and udf filesystems has been disabled in the Linux kernel configuration. (AP-9433)
- The /tmp directory has been configured and the noexec option is set on the /dev/shm partition in the Linux fstab. (AP-9433)
- The rsync service, telnet client, and iptables-persistant option for Linux ufw are not installed. (AP-9433)
- New TLS protocol selections are available for SMTP. See Configure Your SmartServer for details. (LUM-9135)
- The SmartServer security hardening guide has been expanded.
You can now enable or disable LON domain ID discovery. A new Enable Domain ID Discovery option is available on the LON tab of the SmartServer Configuration page. The option is disabled by default. When enabled, the SmartServer searches for configured devices in all one-byte domains. The SmartServer stops the search when a configured device is found in any of the one-byte domains. The search may take up to one hour. See (Optional) Add a LON Interface for details. (AP-9482)
You can now provision, reprovision, and deprovision devices when you are using LON IMM. (LUM-9109)
A new simplified interface is available for file import, export, backup, restore, and update. You can open the new interface from a new import/export button at the top of your SmartServer CMS dashboard. See Importing and Exporting SmartServer Configuration Files for more information. (LUM-9073, LUM-9074, LUM-9108)
You can now add property datapoints for BACnet and Modbus devices. You can set the value for a property datapoint prior to physically installing the device containing the property datapoint. The SmartServer writes the last value you specify for a property datapoint when you provision the device and when you restart the SmartServer. To specify a datapoint as a property datapoint, add a “Property” column to the XIF file and enter “yes” in the Property column for the datapoint. (AP-7118)
You can now specify a custom port number for Modbus TCP devices. Previously, that SmartServer only supported Modbus TCP devices using the Modbus standard 502 port. (AP-8774)
You can now specify Modbus register addresses in Modicon format in a Modbus XIF file. To specify a Modbus register address in Modicon format, enter the address as a five- or six-digit number. (AP-9113)
The link from the SmartServer Configuration page to the SmartServer CMS now uses the secure HTTPS protocol. (AP-8833)
The SmartServer now uses the same apollo user credentials for the SmartServer Configuration page, the SmartServer Local CMS, local MQTT broker, and Linux. The synchronization is managed by the SmartServer Configuration page. You can no longer change the apollo user credentials in the Local CMS. (AP-9845, LUM-9271)
When defining rooms, you can now specify rooms that overlap. (LUM-8638)
The Alarms widget has been expanded to include alarms and events generated by IAP/MQ services and drivers. The widget has been renamed to be the Alarms and Events widget. (LUM-8916, LUM-9166)
A new IAP/REST endpoint is available to get sunrise and sunset times for a specified day. The times are returned as UTC and local times. (LUM-8624)
New IAP/REST endpoints are available to import and export files. (LUM-9074, LUM-9075)
The following problems have been fixed:
- Signed certificate renewal sometimes failed. (AP-9054, AP-9728)
- Communication with LON devices was sometimes lost if an Ethernet cable was removed from the SmartServer. (AP-8727)
- BACnet device discovery sometimes failed with BACnet devices including any BACnet notification class objects like the Trend IQ4E. (AP-9649)
- BACnet device discovery failed for sites with more than 200 BACnet devices. (AP-9724, LUM-9364)
- Filtering based on datapoint direction (input or output) sometimes failed for BACnet datapoints. (AP-9710)
- Modbus device discovery sometimes failed. (AP-9802)
- Device actions were not accessible from floorplan views. (LUM-9083, LUM-9084, LUM-9151)
- IAP Output nodes did not work in Node-RED if you did not have any IAP Input nodes. (LUM-9094)
- You could not edit structured datapoint values based on user types. (LUM-9100)
- You could not delete the UID for a LON device. (LUM-8944)
- SMTP settings were sometime not saved correctly. (LUM-9116)
- The initial value and write initial value setting were sometimes lost when updating the datapoint properties for a datapoint. (AP-8509)

Warnings:

You can update an installed SmartServer running an earlier release of the SmartServer software to the SmartServer 3.5 software. However, after you have installed the SmartServer 3.5 software you cannot go back to an earlier release without either restoring a full system backup with the earlier release, or re-imaging your SmartServer with an earlier release. Always backup your SmartServer prior to updating it to the SmartServer 3.5 software. If you have to go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page. Links to prior releases are available on this page. (LUM-8271)
The SmartServer 3.5 software will not run on SmartServer hardware with a dual core processor. You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that may not be compatible with this release.
IzoT CT 4.2 or a newer version, or IzoT Net Server 4.2 or a newer version, is required to use the IzoT Net Export Utility.
In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
In some cases, connections with many destinations may fail to update all destinations. If you have any connections with many destinations, test them to verify all destinations are updated as expected. If you observe any failed updates, break up the connection into multiple connections with fewer destinations per connection. (AP-9259)
You cannot update IAP output datapoints (which are the same as BACnet input datapoints) from calendar events. You can update IAP input datapoints (which are the same as BACnet output datapoints). This includes writes to BACnet inputs such as BACnet AI and BI objects. (LUM-7839)
In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned. You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)

SmartServer IoT 3.4

Release Date: May 19, 2022

Versions:

SmartServer IoT Software: 3.40.021
IzoT Net Export Utility: 1.50.016
IOX: 2.21.001
Platform
- Ubuntu Linux: 20.04
- Ubuntu kernel: 5.4
- Node.js: 14
- Java VM: 11
- Python: 3.8
- PHP: 8.0
- Karaf: 4.2.13
- Jetty Web Server: 9.4.43
- NginX: 1.18.0
- PostgreSQL: 12.9
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revision F (Quad Core ARM Processor) or later

Downloads:

Changes:

You can now configure the SmartServer to discover the domain ID for an existing LON network. See the LON Domain ID Settings section in (Optional) Add a LON Interface for more information. (AP-6300)
You can now manage your SmartServer from a new Segment Controllers tab in the SmartServer CMS Devices widget. This feature makes it easier for you to find and manage your SmartServer in the CMS. See Discovering, Defining, or Importing Devices for more information.
We have made it easier for developers to create custom drivers for new protocols and devices with proprietary interfaces. We did this by creating a new open source SmartServer driver template project on Github at github.com/izot/smartserver-driver-template. The project includes a makefile that generates a SmartServer update file containing your custom driver that you can load on your SmartServer using the Segment Controllers tab of the new Devices widget. We also updated the IAP driver API to improve support for reading and writing datapoints, and to add support for datapoints on your devices using any IAP datapoint types including structured and string types. See the README document in the project for instructions on how to create a new driver.
The Modbus driver now supports the Modbus UTF8 (CHAR8 and CHAR8_2) and UTF16 (CHAR16) string datatypes. (AP-8081)
The Apache Karaf runtime has been updated to version 4.2.13, and the Eclipse Jetty web server has been updated to version 9.4.43. (AP-8837)
The following problem has been fixed: OPC UA client connections to the SmartServer OPC UA Server sometimes failed when the SmartServer restarted. (AP-9358)

Warnings:

You can update an installed SmartServer running an earlier release of the SmartServer software to the SmartServer 3.4 software. However, after you have installed the SmartServer 3.4 software you cannot go back to an earlier release without either restoring a full system backup with the earlier release, or re-imaging your SmartServer with an earlier release. Always backup your SmartServer prior to updating it to the SmartServer 3.4 software. If you have to go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page. Links to prior releases are available on this page. (LUM-8271)
In some cases, the SmartServer 3.4 software will fail to run on SmartServer hardware with a dual core processor. You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that may not be compatible with this release.
IzoT CT 4.2 or a newer version, or IzoT Net Server 4.2 or a newer version, is required to use the IzoT Net Export Utility.
If you setup datapoint value alarm notifications, in rare cases the notifications may fail due to missing SMTP settings. To workaround, manually edit the SMTP settings in the com.echelon.cms.core.mail.cfg file. (LUM-9116)
When using signed security certificates, in some cases the automatic renewal of expired certificates will fail. If you have any expired signed certificates in your SmartServer, you can open a console interface and enter the following commands to renew them: (AP-9054)

/sbin/dehydrated -c
systemctl restart nginx

In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.
In some cases, connections with many destinations may fail to update all destinations. If you have any connections with many destinations, test them to verify all destinations are updated as expected. If you observe any failed updates, break up the connection into multiple connections with fewer destinations per connection. (AP-9259)
You cannot update IAP output datapoints (which are the same as BACnet input datapoints) from calendar events. You can update IAP input datapoints (which are the same as BACnet output datapoints). This includes writes to BACnet inputs such as BACnet AI and BI objects. (LUM-7839)
In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned. You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)

SmartServer IoT 3.3

Release Date: March 14, 2022

Versions:

SmartServer IoT Software: 3.30.057
IzoT Net Export Utility: 1.50.016
Platform
- Ubuntu Linux: 20.04
- Ubuntu kernel: 5.4
- Node.js: 14
- Java VM: 11
- Python: 3.8
- PHP: 8.0
- NginX: 1.18.0
- PostgreSQL: 12.9
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revision F (Quad Core ARM Processor) or later

Downloads:

Changes:

A new Connections widget has been added to simplify creating datapoint connections that enable changes to one or more source datapoints to be propagated to one or more destination datapoints. See Setting Up Datapoint Connections for more information.
A new incremental export capability is now available in the IzoT Net Export tool. This capability makes it easier to export LON devices from an LNS network or IzoT CT to the SmartServer. See Importing LON Devices from an LNS Network for details.
License management has been added. See Manage Licenses for more information.
You can now specify an override priority when updating the IAP Output Node in a Node-RED flow created in the Sequencing widget. (LUM-7681)
PostgreSQL was updated to version 12.9 to address a security vulnerability in PostgreSQL 12.6. (AP-8838)
The following problems have been fixed:
- The SmartServer did not read the priority array for a BACnet device when reading the present value of a BACnet object. (AP-8319)
- The SmartServer sometimes rejected BACnet XIF files (.BAC extension) that contained a Unicode byte order mark (BOM). The BACnet XIF file parser now correctly ignores the Unicode BOM character. (AP-8577)
- Exporting a LON network with the IzoT Net Export utility that included any devices or routers that were not online sometimes failed. (AP-8429, AP-8570, AP-8590)
- On a SmartServer with internal LON datapoints, the datapoint values were sometimes reported incorrectly after a SmartServer restart. (AP-7954)
- In some cases, the SmartServer would not detect and report an incorrect LON program ID when the program ID in a LON device did not match the expected program ID for the device. (AP-8589)
- The SmartServer OPC UA Server sometimes failed to correctly handle localized datapoint values. For example, if a localization transform was specified to convert a Celsius datapoint value to Fahrenheit, the transformation did not occur correctly. (LUM-8285)
- The SmartServer OPC UA Server sometimes failed to run when an edge device was deleted. (AP-8482)
- Multi-day all-day schedule events failed. (LUM-8815)
- Data log extraction failed after 24-hours. (LUM-8275)
- High and low limit alarm condition detection sometimes failed. (AP-8816)
- Connecting the SmartServer to a LAN or WAN channel after the initial power-up sometimes caused operational errors. (AP-8722)
- Updating a datapoint with a preset-value sometimes caused a warning-message to be displayed even though the update was successful. (AP-8715)

Warnings:

You can update an installed SmartServer running an earlier release of the SmartServer software to the SmartServer 3.3 software. However, after you have installed the SmartServer 3.3 software you cannot go back to an earlier release without either restoring a full system backup with the earlier release, or re-imaging your SmartServer with an earlier release. Always backup your SmartServer prior to updating it to the SmartServer 3.3 software. If you have to go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page. Links to prior releases are available on this page. (LUM-8271)
In some cases, the SmartServer 3.3 software will fail to run on SmartServer hardware with a dual core processor. You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that may not be compatible with this release.
In some cases, if you update an earlier version of the SmartServer software with more than 40 provisioned devices to the SmartServer 3.3 release, you may lose communication with some of your devices if any of your devices have a program ID that specifies the device supports changeable interfaces.
IzoT CT 4.2 or a newer version, or IzoT Net Server 4.2 or a newer version, is required to use the IzoT Net Export Utility.
Your Licensing Customer ID will not be displayed if you re-image a SmartServer with any licenses activated. Your licenses will continue to work after you re-image your SmartServer. To recover your Licensing Customer ID after re-imaging your SmartServer, transfer all your licenses to the cloud, download your licenses from the cloud, and reactivate your licenses. (LUM-9019)
When using signed security certificates, in some cases the automatic renewal of expired certificates will fail. If you have any expired signed certificates in your SmartServer, you can open a console interface and enter the following commands to renew them: (AP-9054)

/sbin/dehydrated -c
systemctl restart nginx

In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)
Under some conditions, if you use the SmartServer to discover BACnet devices, some of your BACnet devices may not be discovered. If you are missing any devices after a discovery operation, repeat the discover and your missing devices will be added. (AP-9272)
To set the SmartServer time from a BACnet client such as a BACnet workstation, first disable the network time protocol with the following console command: timedatectl set-ntp false (AP-9352)
You cannot update IAP output datapoints (which are the same as BACnet input datapoints) from calendar events. You can update IAP input datapoints (which are the same as BACnet output datapoints). This includes writes to BACnet inputs such as BACnet AI and BI objects. (LUM-7839)
In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned. You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)
Backup and restore may fail if any configuration files have spaces in their names. To prevent failure, do not use spaces in the filenames for any of the SmartServer configuration files. (AP-9325)
OPC UA client connections to the SmartServer OPC UA Server may fail after the SmartServer is restarted. To prevent failure, edit the etc/sysctl.conf file, add the following line, and then restart the SmartServer. (AP-9358)

net.ipv4.ip_local_port_range = 32768 47700

The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.

SmartServer IoT 3.2 Update 4

Release Date: December 15, 2021

Versions:

SmartServer IoT Software: 3.26.002
IzoT Net Export Utility: 1.30.335
Platform
- Ubuntu Linux: 20.04
- Ubuntu kernel: 5.4
- Node.js: 14
- Java VM: 11
- Python: 3.8
- PHP: 8.0
- NginX: 1.18.0
- PostgreSQL: 12.6
Hardware Compatibility: Model 72201R-240 or 72201R-248, Quad or Dual Core ARM Processor with NXP PMIC

Downloads:

Changes:

An Apache Log4j vulnerability was addressed. See Apache Log4j Vulnerability Guidance | CISA for a description of the vulnerability.

Warnings:

See the SmartServer IoT 3.2 Update 3 warnings.

SmartServer IoT 3.2 Update 3

Release Date: November 24, 2021

Versions:

SmartServer IoT Software: 3.26.001
IzoT Net Export Utility: 1.30.335
Platform
- Ubuntu Linux: 20.04
- Ubuntu kernel: 5.4
- Node.js: 14
- Java VM: 11
- Python: 3.8
- PHP: 8.0
- NginX: 1.18.0
- PostgreSQL: 12.6
Hardware Compatibility: Model 72201R-240 or 72201R-248, Quad or Dual Core ARM Processor with NXP PMIC

Downloads:

Changes:

The following problems have been fixed:
- The OPC UA Server did not use any localization transformations specified in the the Datapoint Properties Widget. For example, if you specified a localization transformation to convert a Celsius temperature value to a Fahrenheit temperature value, the OPC UA Server always reported the temperature value in Celsius. (LUM-8668)
- The SmartServer LON interface sometimes failed if you powered up the SmartServer without a connection on the LAN or WAN interface. (AP-8831)
- When you updated a datapoint in the Datapoint Browser, in some cases the SmartServer updated the datapoint with a stale value instead of the value you entered. (LUM-8664)
- Certain alarm conditions including many LON device communication errors caused alarm reporting errors. (AP-8830)

Warnings:

You can update an installed SmartServer running an earlier release of the SmartServer software to the 3.2 Update 3 release. However, after you have installed 3.2 Update 3 you cannot go back to an earlier release prior to 3.2 Update 2 without first clearing all devices out of the SmartServer. If you attempt to load an earlier version of the SmartServer software on a SmartServer with 3.2 Update 3 and provisioned devices, the earlier software is not compatible with the 3.2 Update 3 database and will fail to run. Always backup your SmartServer prior to updating it to the 3.2 Update 3 software. If you have to go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page. Links to prior releases are available on this page. (LUM-8271)
In some cases, the SmartServer 3.2 Update 3 software will fail to run on SmartServer hardware with a dual core processor. You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that may not be compatible with this release.
IzoT CT 4.2 or a newer version, or IzoT Net Server 4.2 or a newer version, is required to use the IzoT Net Export Utility.
If you use the Datapoint Browser with a structured datapoint, such as a SNVT_switch datapoint with state and value fields, and you have assigned presets to the datapoint in the Datapoint Properties widget, you will only be able to specify preset values in the Datapoint Browser. This issue does not affect Modbus or BACnet datapoints since they do not use structured datapoints. (LUM-8832)
The SmartServer may fail to communicate with LON devices when using LON independent management mode (IMM) and changing a SmartServer network interface after importing an IzoT Net Server or LNS database. If you lose communication with LON devices in IMM after changing a network interface, backup your SmartServer and then reset your databases as described in Resetting the SmartServer to Factory Defaults. (AP-8563)
If your SmartServer has any BACnet devices with a discovered device interface (XIF) and you export your device types using the Settings button or the Devices Widget Export action, your discovered BACnet XIF will not be included in the export. You can get a copy of the discovered XIF in the /var/apollo/data/bacnetrouter/res directory on your SmartServer. (LUM-8265)
You cannot include leading zeros in the device unique ID (UID) and the BACnet object instance numbers that you specify in the BACnet XIF (BAC) file. The CMS will accept the definitions, but some operations will fail due to the leading zeros. (AP-8018)
You cannot update IAP output datapoints (which are the same as BACnet input datapoints) from calendar events. You can update IAP input datapoints (which are the same as BACnet output datapoints). This includes writes to BACnet inputs such as BACnet AI and BI objects. (LUM-7839)
In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned. You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)
In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.

SmartServer IoT 3.2 Update 2

Release Date: August 26, 2021

Versions:

SmartServer IoT Software: 3.25.014
IzoT Net Export Utility: 1.30.335
Platform
- Ubuntu Linux: 20.04
- Ubuntu kernel: 5.4
- Node.js: 14
- Java VM: 11
- Python: 3.8
- PHP: 8.0
- NginX: 1.18.0
- PostgreSQL: 12.6
Hardware Compatibility: Model 72201R-240 or 72201R-248, Quad or Dual Core ARM Processor with NXP PMIC

Downloads:

Changes:

The following problems have been fixed:
- Extracting data logs using a web socket sometimes failed after 24 hours. (LUM-8275)
- Exporting an IzoT Net Server or LNS network with the IzoT Net Export utility sometimes failed if any IP-852 routers were defined in the network that were not available online at the time of the export. (AP-8429)
- Exporting an IzoT Net Server or LNS network with the IzoT Net Export utility failed for any network variables with changeable types if the type had been changed. The SmartServer CMS now creates a unique device type for each unique combination of network variable types on a device with changeable type network variables. (AP-8030)
- Creating LON dynamic network variables on the SmartServer from IzoT CT failed if the dynamic network variables used a user-defined type. (AP-8370)

Warnings:

You can update an installed SmartServer running an earlier release of the SmartServer software to the 3.2 Update 2 release. However, you cannot go back without clearing all devices out of the SmartServer. If you attempt to load an earlier version of the SmartServer software on a SmartServer with 3.2 Update 2 and provisioned devices, the earlier software is not compatible with the 3.2 Update 2 database and will fail to run. Always backup your SmartServer prior to updating it to the 3.2 Update 2 software. If you have to go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page. Links to prior releases are available on this page. (LUM-8271)
In some cases, the SmartServer 3.2 Update 2 software will fail to run on SmartServer hardware with a dual core processor. You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that may not be compatible with this release.
IzoT CT 4.2 or a newer version, or IzoT Net Server 4.2 or a newer version, is required to use the IzoT Net Export Utility.
The SmartServer may fail to communicate with LON devices when using LON independent management mode (IMM) and changing a SmartServer network interface after importing an IzoT Net Server or LNS database. If you lose communication with LON devices in IMM after changing a network interface, backup your SmartServer and then reset your databases as described in Resetting the SmartServer to Factory Defaults. (AP-8563)
If your SmartServer has any BACnet devices with a discovered device interface (XIF) and you export your device types using the Settings button or the Devices Widget Export action, your discovered BACnet XIF will not be included in the export. You can get a copy of the discovered XIF in the BACnet XIF file with a BAC extension in the /var/apollo/data/bacnetrouter/res directory on your SmartServer. (LUM-8265)
You cannot include leading zeros in the device unique ID (UID) and the BACnet object instance numbers that you specify in the BACnet XIF (BAC) file. The CMS will accept the definitions, but some operations will fail due to the leading zeros. (AP-8018)
You cannot update IAP output datapoints (which are the same as BACnet input datapoints) from calendar events. You can update IAP input datapoints (which are the same as BACnet output datapoints). This includes writes to BACnet inputs such as BACnet AI and BI objects. (LUM-7839)
In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned. You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)
In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.

SmartServer IoT 3.2 Update 1

Release Date: May 26, 2021

Versions:

SmartServer IoT Software: 3.20.121
IzoT Net Export Utility: 1.30.335
Platform
- Ubuntu Linux: 20.04
- Ubuntu kernel: 5.4
- Node.js: 14
- Java VM: 11
- Python: 3.8
- PHP: 8.0
- NginX: 1.18.0
- PostgreSQL: 12.6
Hardware Compatibility: Model 72201R-240 or 72201R-248, Quad or Dual Core ARM Processor with NXP PMIC

Downloads:

Changes:

The LON IP-852 router sometimes failed to route large network variables. This problem has been fixed. (AP-8426)

Warnings:

Limited testing has been completed for this release. The fix for routing 222-byte LON NVs has been verified, but there has been no regression testing completed for this update. If you are looking for a fully tested stable release, use SmartServer 3.2.
You can update an installed SmartServer running an earlier release of the SmartServer software to the 3.2 release. However, you cannot go back without clearing all devices out of the SmartServer. If you attempt to load an earlier version of the SmartServer software on a SmartServer with 3.2 and provisioned devices, the earlier software is not compatible with the 3.2 database and will fail to run. Always backup your SmartServer prior to updating it to the 3.2 software. If you have to go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page. Links to prior releases are available on this page. (LUM-8271)
In some cases, the SmartServer 3.2 Update 1 software will fail to run on SmartServer hardware with a dual core processor. You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that may not be compatible with this release.
The source of datapoint names has changed with this release to make the names easier to understand and recognize. If you update a SmartServer with a prior release, the datapoint names may change for any new devices you install, whereas they will stay the same for devices you installed with the previous release. Both sets of names will appear in the CMS Datapoint Properties widget, but only the new names will work for any new devices you install. To simplify system maintenance, redefine your datapoint properties, calendar events, and Sequencing widget flows to use the new datapoint names.
You cannot use the apollo-reset command from the SmartServer console. The command is available from the console, but if you enter the command your SmartServer may fail or become corrupted. To reset the SmartServer database, or to return a SmartServer to factory defaults, follow the procedure at Resetting the SmartServer to Factory Defaults. (AP-8427)
You cannot view logged data in the CMS Datapoint Browser. Logged data is available to custom applications and web pages that use IAP/REST or IAP/WS to view the data log contents. (LUM-8529)
You cannot include leading zeros in the device unique ID (UID) and the BACnet object instance numbers that you specify in the BACnet XIF (BAC) file. The CMS will accept the definitions, but some operations will fail due to the leading zeros. (AP-8018)
You cannot update IAP output datapoints (which are the same as BACnet input datapoints) from calendar events. You can update IAP input datapoints (which are the same as BACnet output datapoints). This includes writes to BACnet inputs such as BACnet AI and BI objects. (LUM-7839)
If you create a calendar event with a sunset or sunrise time, in some cases you will not be able to edit the event after you create it. If you cannot change an event that requires a change, delete the event and create a new one with your desired changes. (LUM-8268)
In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned. You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)
If your SmartServer has any BACnet devices with a discovered device interface (XIF) and you export your device types using the Settings button or the Devices Widget Export action, your discovered BACnet XIF will not be included in the export. You can get a copy of the discovered XIF in the /var/apollo/data/bacnetrouter/res directory on your SmartServer. (LUM-8265)
In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.

SmartServer IoT 3.2

Release Date: May 19, 2021

Versions:

SmartServer IoT Software: 3.20.119
IzoT Net Export Utility: 1.30.335
Platform
- Ubuntu Linux: 20.04
- Ubuntu kernel: 5.4
- Node.js: 14
- Java VM: 11
- Python: 3.8
- PHP: 8.0
- NginX: 1.18.0
- PostgreSQL: 12.6
Hardware Compatibility: Model 72201R-240 or 72201R-248, Quad or Dual Core ARM Processor with NXP PMIC

Downloads:

Changes:

The Ubuntu Linux operating system on the SmartServer has been updated to version 20.04. Several platform components such as the Node.js, Java VM, Python, and PHP components have also been updated. The Release Notes now list the key platform component version numbers. (AP-8056 and AP-8057)
You can now discover BACnet devices without first creating a BACnet device interface (XIF) file. When the SmartServer discovers a BACnet device, if a BACnet XIF file does not already exist for the device, the SmartServer automatically uploads the BACnet XIF definition from the BACnet device. (AP-5210 and AP-7550)
You can now modify a device interface (XIF) definition that you have created for a BACnet or Modbus device. For example, you can change or delete a block or datapoint on a provisioned device to correct or enhance the original device interface definition. (AP-8067)
Datapoint naming in the user interface and programming APIs has been updated to improve consistency and usability. (LUM-7848)
Errors generated and reported by the SmartServer CMS are now included in the CMS Alarms widget to provide a single interface for viewing summary alarm status and for viewing and clearing alarms. (LUM-7870 and LUM-7877)
You can now disable IP-852 checksums to provide compatibility with third-party IP-852 routers and devices that do not correctly implement IP-852 checksums. (AP-7766)
The SmartServer uses the Ready LED to provide a visual indicator that the CMS is ready after initial startup. (AP-8061)
You can now load applications into LON devices where the application has a different program ID than the application already loaded in the device. (AP-8026)

Warnings:

You can update an installed SmartServer running an earlier release of the SmartServer software to the 3.2 release. However, you cannot go back without clearing all devices out of the SmartServer. If you attempt to load an earlier version of the SmartServer software on a SmartServer with 3.2 and provisioned devices, the earlier software is not compatible with the 3.2 database and will fail to run. Always backup your SmartServer prior to updating it to the 3.2 software. If you have to go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page. Links to prior releases are available on this page. (LUM-8271)
In some cases, the SmartServer 3.2 software will fail to run on SmartServer hardware with a dual core processor. You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that may not be compatible with this release.
The source of datapoint names has changed with this release to make the names easier to understand and recognize. If you update a SmartServer with a prior release, the datapoint names may change for any new devices you install, whereas they will stay the same for devices you installed with the previous release. Both sets of names will appear in the CMS Datapoint Properties widget, but only the new names will work for any new devices you install. To simplify system maintenance, redefine your datapoint properties, calendar events, and Sequencing widget flows to use the new datapoint names.
You cannot use the apollo-reset command from the SmartServer console. The command is available from the console, but if you enter the command your SmartServer may fail or become corrupted. To reset the SmartServer database, or to return a SmartServer to factory defaults, follow the procedure at Resetting the SmartServer to Factory Defaults. (AP-8427)
You cannot view logged data in the CMS Datapoint Browser. Logged data is available to custom applications and web pages that use IAP/REST or IAP/WS to view the data log contents. (LUM-8529)
You cannot include leading zeros in the device unique ID (UID) and the BACnet object instance numbers that you specify in the BACnet XIF (BAC) file. The CMS will accept the definitions, but some operations will fail due to the leading zeros. (AP-8018)
The SmartServer LON IP-852 router will not work with LON datapoints with a size larger than 198 bytes. (AP-8426)
You cannot update IAP output datapoints (which are the same as BACnet input datapoints) from calendar events. You can update IAP input datapoints (which are the same as BACnet output datapoints). This includes writes to BACnet inputs such as BACnet AI and BI objects. (LUM-7839)
If you create a calendar event with a sunset or sunrise time, in some cases you will not be able to edit the event after you create it. If you cannot change an event that requires a change, delete the event and create a new one with your desired changes. (LUM-8268)
In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned. You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)
If your SmartServer has any BACnet devices with a discovered device interface (XIF) and you export your device types using the Settings button or the Devices Widget Export action, your discovered BACnet XIF will not be included in the export. You can get a copy of the discovered XIF in the /var/apollo/data/bacnetrouter/res directory on your SmartServer. (LUM-8265)
In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.

SmartServer IoT 3.1 Update 3 Beta

Release Date: March 9, 2021 (beta release)

Versions:

SmartServer IoT Software: 3.14.004
IzoT Net Export Utility: 1.30.335
Hardware Compatibility: Model 72201R-240 or 72201R-248, Quad or Dual Core ARM Processor with NXP PMIC

Downloads:

Changes:

Added configuration option to disable IP-852 CRC checking for compatibility with IP-852 devices and routers that do not implement IP-852 CRC checking such as devices based on the Niagra platform. (AP-7776, AP-8115)
Added Linux kernel support required for OpenVPN installation. (AP-8135)
Bug fixes and performance improvements, including the following:
- Improved detection of device failure and reporting of devices that recover from failure. (AP-8035, AP-8141, AP-8142, AP-8155, AP-8159, AP-8160, AP-8171, AP-8173, AP-8184, AP-8192)
- Fixed problems with provisioning and monitoring LON PL device devices when PL repeating is enabled. (AP-8023, AP-8048, AP-8058, AP-8073, AP-8127, AP-8139, AP-8152, AP-8161, AP-8182)
- Improved BACnet COV performance. (AP-8027)
- Improved IOX configuration from the CMS Datapoint Browser (LUM-8001)
- Node-RED nodes were sometimes deleted when updating the SmartServer software (AP-8153)
- In some cases, calendar events could not be created that ended at midnight or were less than one hour. (LUM-7890, LUM-7891, LUM-7894)

Warnings:

You cannot include leading zeros in the device unique ID (UID) and the BACnet object instance numbers that you specify in the BACnet XIF (BAC) file. The CMS will accept the definitions, but some operations will fail due to the leading zeros. (AP-8018)
Automatic application image loading for field devices may fail if you use the manual option to create the device and the program ID in the device does not match the program ID specified for the device interface. You can use automatic application image loading with guided device discovery. (AP-8026)
You cannot update IAP output datapoints (which are the same as BACnet input datapoints) from calendar events. You can update IAP input datapoints (which are the same as BACnet output datapoints). This includes writes to BACnet inputs such as BACnet AI and BI objects. (LUM-7839)
Historical data logs may contain adjacent duplicate entries when you specify the option to only log values after a change in value. (LUM-7831)
In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7107, LUM-7104, LUM-7145, AP-7677)
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.

SmartServer IoT 3.1

Release Date: December 23, 2020

Versions:

SmartServer IoT Software: 3.10.011
IzoT Net Export Utility: 1.30.335
Hardware Compatibility: Model 72201R-240 or 72201R-248, Quad or Dual Core ARM Processor with NXP PMIC

Downloads:

Changes:

Added beta support for event-driven monitoring of BACnet devices using BACnet COV.
Added beta support for event-driven updates from the SmartServer BACnet Server to BACnet workstations and other BACnet clients.
Added Docker support. (AP-7848)
Added support for custom names for BACnet datapoints defined in the BACnet XIF (BAC) file.
Bug fixes and performance improvements, including the following:
- Provisioning a Modbus device with incorrect Modbus register specifications sometimes caused a cryptic error message to be reported to the user. (AP-7924)
- Importing a LON XIF file with an integer XIF version number failed. (AP-7915)

Warnings:

If you use the beta BACnet COV support in the SmartServer BACnet Server to subscribe to a SmartServer BACnet Server datapoint from a BACnet workstation, COV updates may be delayed by up to one minute, (AP-8027)
You cannot include leading zeros in the device unique ID (UID) and the BACnet object instance numbers that you specify in the BACnet XIF (BAC) file. The CMS will accept the definitions, but some operations will fail due to the leading zeros. (AP-8018)
Automatic application image loading for field devices may fail if you use the manual option to create the device and the program ID in the device does not match the program ID specified for the device interface. You can use automatic application image loading with guided device discovery. (AP-8026)
You cannot update IAP output datapoints (which are the same as BACnet input datapoints) from schedule events. You can update IAP input datapoints (which are the same as BACnet output datapoints). This includes writes to BACnet inputs such as BACnet AI and BI objects. (LUM-7839)
Historical data logs may contain adjacent duplicate entries when you specify the option to only log values after a change in value. (LUM-7831)
In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7107, LUM-7104, LUM-7145, AP-7677)
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.
You cannot install more than a total of five network interfaces (U60 or U70) and IOX modules in a single SmartServer. If you have five total, or if you have four and require a spare USB port, use a powered USB 3.0 compliant hub and plug all the U60 and U70 network interfaces into the hub. Always plug any IOX modules directly into the SmartServer and do not plug them into a hub.

SmartServer IoT 3.0

Release Date: November 25, 2020

Versions:

SmartServer IoT Software: 3.00.025
IzoT Net Export Utility: 1.30.335
Hardware Compatibility: Model 72201R-240 or 72201R-248, Quad or Dual Core ARM Processor with NXP PMIC

Downloads:

Changes:

BACnet support enhancements and fixes
- Device discovery for the BACnet Client
- Multi-state object support for the BACnet Server
- Scheduler and Calendar object support for the BACnet Server
- Intrinsic reporting for the BACnet Server
- IAP block naming for the BACnet Client
- Multi-protocol support for connections with BACnet datapoints
OPC UA override support
Simplified custom driver support with a new IAP Driver Library (IDL)
STIG compliance improvements
OAuth authentication support
The following beta features have been released and are no longer in beta:
- BACnet client for interfacing with BACnet/IP devices
- IOX I/O Expansion Module support for adding digital I/O, relay outputs, and metering inputs to the SmartServer
- CMS Sequencing widget

Warnings:

If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.
You cannot install more than a total of five network interfaces (U60 or U70) and IOX modules in a single SmartServer. If you have five total, or if you have four and require a spare USB port, use a powered USB 3.0 compliant hub and plug all the U60 and U70 network interfaces into the hub. Always plug any IOX modules directly into the SmartServer and do not plug them into a hub.
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
In some cases, the CMS displays stale data after you make a change. If a datapoint value, context, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). (LUM-7107, LUM-7104, AP-7677)
When you edit a preset value in the CMS Datapoint Properties with a localization rule, the CMS may save a slightly different value than the value you entered. For example, if you enter 35 for a preset value, the CMS may store 35.1 instead of 35. (LUM-7315)

SmartServer IoT 2.9

Release Date: August 28, 2020

Versions:

SmartServer IoT Software: 2.90.009
IzoT Net Export Utility: 1.30.335
Hardware Compatibility: Model 72201R-240 or 72201R-248, Quad or Dual Core ARM Processor with NXP PMIC

Downloads:

Changes:

Quad core support! Starting with Revision F of the SmartServer IoT, all SmartServer IoTs now include a quad core ARM processor. Earlier SmartServer IoTs included a dual core processor. The result is better performance at the same price. You can now monitor up to 40 events per second with the new quad core hardware–the dual core hardware was limited to 20 events per second. You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed just under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor. Starting with SmartServer 2.9 software, the software supports both the dual core and quad core versions. Older versions of the SmartServer software will not work on the quad core hardware.
The performance warning threshold in the CMS Datapoint Properties has been increased from 20 events per second to 40 events per second due to the higher performance of the quad core SmartServer.
The following beta features introduced in previous releases are still in beta:
- BACnet client for interfacing with BACnet/IP devices.
- IOX I/O Expansion Module support for adding digital I/O, relay outputs, and metering inputs to the SmartServer.
- CMS Sequencing widget
Bug fixes and performance improvements, including the following:
- Changing the SmartServer hostname sometimes resulted in an unexpected This Site Can't be Reached error message. (AP-7470)
- Secure browsing sometimes failed when you enabled signed security certificates. (LUM-7437)
- Updates sometimes failed if you have a large amount of data log data on your SD card. (LUM-6493)
- On-demand monitoring sometimes failed with BACnet devices. (AP-7568)
- Datapoints were not consistently sorted in the CMS Datapoint Properties. (LUM-7376)
- Datapoint value localization was sometimes disabled when it should have been enabled. (LUM-7370)
- The CMS Devices Test command sometimes returned an incorrect result for BACnet or Modbus devices. (AP-6239)

Warnings:

If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.
You cannot install more than a total of five network interfaces (U60 or U70) and IOX modules in a single SmartServer. If you have five total, or if you have four and require a spare USB port, use a powered USB 3.0 compliant hub and plug all the U60 and U70 network interfaces into the hub. Always plug any IOX modules directly into the SmartServer and do not plug them into a hub.
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
In some cases, the CMS displays stale datapoint values and context information. If a datapoint value or context is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). (LUM-7107, LUM-7104)
If all the widgets in the CMS disappear from your CMS dashboard, click any widget name in the list of widgets on the left side of the dashboard. (LUM-7324)
When you edit a preset value in the CMS Datapoint Properties with a localization rule, the CMS may save a slightly different value than the value you entered. For example, if you enter 35 for a preset value, the CMS may store 35.1 instead of 35. (LUM-7315)
When you modify a preset value or localization rule in the Datapoint Properties, click the Refresh button in the upper right of the Datapoint Browser to activate the change. (LUM-7145)
In some cases, connections to BACnet devices do not function correctly. (AP-5906)

SmartServer IoT 2.8

Release Date: July 20, 2020

Versions:

SmartServer IoT Software: 2.80.042
IzoT Net Export Utility: 1.30.335
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revisions A – E (Dual Core ARM Processor)

Downloads:

Changes:

Modbus device discovery has been added. To discover a Modbus device, you must have a Modbus XIF file with markers that identify fixed datapoints that the SmartServer can use to identify the device.
A new Planning widget has been added that simplifies organization of large systems by allowing you to define campus, building, area, and room contexts.
You can now set an override priority when updating a datapoint value in the CMS Datapoint Browser. If you update a datapoint on a BACnet device, the SmartServer updates the priority array on the device if the device has a writable priority array. (AP-7221)
The connection (CON) file format has changed. Leave the Area Scope, and Zone Scope fields blank in when specifying a Device Name.
Defining monitoring for a datapoint in either the Datapoint Properties widget or the Datapoint Properties (DLA) file has been simplified with a new Monitored property. (LUM-7054)
You can now specify the polling interval from the Datapoint Properties widget or a Datapoint Properties (DLA) file using the same method for BACnet, LON, and Modbus devices. Previously, the polling interval for a BACnet device had to be specified in the BACnet XIF (BAC) file. (AP-5769)
Documentation has been added for using web sockets in custom web pages.
The following new beta features are available with this release:
- Sequencing and Web Page Builder – a new Sequencing widget is available in the CMS that you can use to build sequences of operation using the built-in Node-RED flow editing and web page design tool
- Presets – you can now define and use presets. A preset is a normalized value for a datapoint that you can use for scheduling, alarming, logging, displaying, and sequencing datapoint values from datapoints on devices with different data types, potentially using incompatible data types or using different transformation rules for the data types.
- Datapoint Localization – you can now define datapoint localization transformation to convert the SI units used by the SmartServer into Imperial units. For example, you can use a localization rule to convert a temperature value reported in Celsius to a temperature value reported in Fahrenheit.
The following beta features have been released and are no longer in beta:
- OPC UA server for interfacing with OPC UA clients such as Wonderware InTouch – the number of datapoint subscriptions supported by the SmartServer OPC UA Server has been increased from 1000 datapoints to 10,000 datapoints. (AP-6824)
- U70 PL support for interfacing with LON power line devices using the U70 PL interface with 3-phase PL coupler and power supply (the optional U70 PL USB Network Interface module is required)
- CMS Calendar widget for scheduling events
The following beta features introduced in previous releases are still in beta:
- BACnet client for interfacing with BACnet/IP devices
- IOX I/O Expansion Module support for adding digital I/O, relay outputs, and metering inputs to the SmartServer
Bug fixes and performance improvements have been implemented for the BACnet Server, alarm management, and scheduling.

Warnings:

You cannot change the host name for a SmartServer from the default. Each SmartServer has a unique hostname printed on the bottom label. Some operations will fail if you change the host name. (AP-6914, AP-7470)
The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB. For optimal performance, keep logged data below 100 MB. The SmartServer includes a 32 GB SD card. You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB. The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration. You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance. If required, you can free up space on the SD card by deleting backups. To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)
If you update your SmartServer from the CMS, the update may fail if you have a large amount of data log data on your SD card. Back up your SmartServer before doing an update. If the update fails, re-image your SmartServer from the console interface as described in Updating with the SmartServer Console. (LUM-6493)
The Devices widget Test command may sometimes return an incorrect result for BACnet or Modbus devices. (AP-6239)
The order of datapoints in the Datapoint Browser sometimes changes. Verify you have the correct datapoint before changing a datapoint value. (LUM-7376)
In some cases, the CMS displays stale datapoint values and context information. If a datapoint value or context is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). (LUM-7370, LUM-7107, LUM-7104)
If all the widgets in the CMS disappear from you CMS dashboard, click any widget name in the list of widgets on the left side of the dashboard. (LUM-7324)
When you edit a preset value in Datapoint Properties with a localization rule, the saved value may be slightly different than the value you entered. For example, if you enter 35 for a preset value, the saved value may be 35.1. (LUM-7315)
When you modify a preset value or localization rule in the Datapoint Properties, click the Refresh button in the upper right of the Datapoint Browser to activate the change. (LUM-7145)
In some cases, connections to BACnet devices do not function correctly. (AP-5906)

SmartServer IoT 2.7 Update 1

Release Date: March 31, 2020

Versions:

SmartServer IoT Software: 2.75.020
IzoT Net Export Utility: 1.30.335
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revisions A – E (Dual Core ARM Processor)

Downloads:

Changes:

A new beta feature is available that simplifies replicating a SmartServer image to multiple SmartServers. You can use this feature to create a golden image that you deploy to many SmartServers.
Added support for power line LON devices, including support for power line devices with repeating functionality using the Enhanced LonTalk Proxy Protocol. Peer-to-peer connections are not supported with Enhanced LonTalk Proxy Protocol repeating enabled.
The default datapoint priority for events in the Calendar widget has been changed to the Normal priority. This is the same priority used by the Datapoint Browser widget so you can override a scheduled event from the Datapoint Browser, and the next scheduled event will overwrite the override. You can create override events in the Calendar by assigning a priority from 1 to 16. You cannot override these higher priority events from the Datapoint Browser.
The following changes were implemented for the IzoT Net Export Utility:
- Support for both 32-bit and 64-bit Windows.
- Support for IzoT Net networks with multiple SmartServers. An exported subsystem can only contain one SmartServer.
- Subnet and node IDs are now exported from the IzoT Net database to the SmartServer.
- Virtual devices hosted on the SmartServer can now be placed in any subsystem in IzoT CT.
- Export time has been reduced in some cases.
Bug fixes and performance improvements, including fixes and improvements for the following:
- The Reset to Defaults command on the SmartServer Configuration System webpage would corrupt the SmartServer if you entered the wrong password.
- You could not change the filename of a previously imported BACnet, LON, or Modbus XIF file.
- You could not modify a previously defined connection.
- The BACnet client driver did not respond to on-demand poll requests.
- External BACnet clients could not update datapoints published by the SmartServer.
- Modbus device polling would fail if the device was was disconnected and re-connected.
- Modbus devices would sometimes be reported as offline when they were online.

Warnings:

You cannot change the host name for a SmartServer from the default. Each SmartServer has a unique hostname printed on the bottom label. Some operations will fail if you change the host name. (AP-6914)
You can only enter an integer alarm limit as an integer value. For example, you can enter 85 as a temperature alarm value, but you cannot enter 85.00. You can enter a fractional value as a fractional value. For example, you can enter 85.5 as a temperature alarm value. (LUM-6679)
The OPC UA Server is limited to 1000 datapoints. (AP-6824)
XIF file and device type names are case sensitive. Do not create two XIF files or two device types with the same name but different case. (LUM-6554)
Meta data in type files cannot contain spaces. (LUM-6312)
In some cases, if you specify a stagger value in a Calendar event definition, the stagger will not be implemented. (AP-6546)
In some cases, connections to BACnet devices do not function correctly. (AP-5906)
Re-provisioning a de-provisioned BACnet device does not work sometimes. (AP-5742)
The BACnet Server trending service is disabled.
The BACnet Server scheduling service is read-only.
You may see an unrecoverable error if you unplug an IOX device less than 15 seconds after powering it up. To prevent this problem, always wait at least 15 seconds before unplugging an IOX. (AP-4986)

SmartServer IoT 2.7

Release Date: December 1, 2019

Versions:

SmartServer IoT Software: 2.70.015
IzoT Net Export Utility: 1.20.280
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revisions A – E (Dual Core ARM Processor)

Downloads:

Changes:

Maximum sustained throughput has been improved by 250% – sustained throughput is now 40 events per second
Device capacity has been increased to 1000 devices
Released the Calendar widget introduced as a beta in 2.6; added support for scheduling based on sunrise and sunset
Added LON device discovery to simplify provisioning of existing LON networks
Added a pause/resume button to the Devices widget to temporarily pause background polling to reduce overhead during system provisioning
Bug fixes and performance improvements, including the following:
- IP-852 communication stopped when IP network communication was temporarily disrupted.
- IP-852 port value was limited to 1500-1700.
- CSV file metadata formatting was inconsistent.
- The Expected Interval value for a datapoint had to be set to a non-zero value to enable logging.

Warnings:

The BACnet Server trending service is disabled.
The BACnet Server scheduling service is read-only.
CSV file metadata tags must be in a separate cell from the metadata values. For example, the metadata tag to specify the file type for a file is #filetype, without quotes. The metadata value to specify a Modbus XIF file is Modbus_xif, without quotes. The metadata tag and the metadata value must be separated by a command. For example, the complete metadata entry for a Modbus XIF file embedded in a CSV file is #filetype,Modbus_xif, with no quotes. If you open the file in Excel, the tag and value will appear in two adjacent cells. Be sure not to combine the two cells into one. Some of the example CSV files from earlier releases incorrectly used quotes and must be updated for the 2.7 release.

SmartServer IoT 2.6 Update 1

Release Date: November 1, 2019

Versions:

SmartServer IoT Software: 2.61.005
IzoT Net Export Utility: 1.20.280
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revisions A – E (Dual Core ARM Processor)

Downloads:

Changes:

SmartServer startup would fail if a custom application created a large number of IAP/MQ requests immediately at startup. With this fix, it is still a good idea for custom applications, services, and drivers to throttle traffic during the first 5 minutes after startup.
The beta BACnet logger service caused logins to be locked out because it was using a fixed password of "ea888". The beta BACnet logger has been disabled for this release to prevent lockouts.

Warnings:

Connection file (CON extension) imports, as described in Defining Datapoint Connections (Release 2.9) , may fail if you update your SmartServer software as described in Updating the SmartServer Software, or if you reset your image to factory defaults as described in Resetting the SmartServer to Factory Defaults. To prevent the error, follow the steps for resetting the databases in the Resetting the SmartServer to Factory Defaults section.

SmartServer IoT 2.6

Release Date: October 14, 2019

Versions:

SmartServer IoT Software: 2.60.025
IzoT Net Export Utility: 1.20.147
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revisions A – E (Dual Core ARM Processor)

Changes:

Added event-driven monitoring support for LON devices, in both the DMM and IMM LON management modes.
Added CMS and IAP/REST support for Zones and Groups.
The outgoing SMTP server used for alarm notifications is now configurable. To use e-mail notification, you must first configure the SMTP server IP address and credentials.
Added the following new beta features:
- BACnet client for interfacing with BACnet/IP devices
- OPC UA server for interfacing with OPC UA clients such as Wonderware InTouch
- U70 PL support for interfacing with LON power line devices using the U70 PL interface with 3-phase PL coupler and power supply
- CMS Calendar widget for scheduling events
- IOX I/O Expansion Module support for adding digital I/O, relay outputs, and metering inputs to the SmartServer
Bug fixes and performance improvements, including fixes for the following problems:
- The Schneider PM5563, Schneider PM820, AMIK201 and WattNode Modbus definition files had an off-by-one error in the register numbers.
- Problems could occur when polling multiple BACnet virtual devices.
- Datapoint updates from the CMS Datapoint Browser did not work for a device exported by the IzoT Net Export utility if the device had Neuron firmware version 16 or older.
- The device count would sometimes be incorrect if you imported devices exported by the IzoT Net Export utility multiple times,
- The CMS password was not changed if you changed the password from the Configuration web page.
- Datapoint properties were not correctly updated if a DLA file was imported after Importing a device type package without the DLA file.

SmartServer IoT 2.5 Update 2

Release Date: August 30, 2019

Versions:

SmartServer IoT Software: 2.52.002
IzoT Net Export Utility: 1.20.147
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revisions A – E (Dual Core ARM Processor)

Downloads:

Changes:

Added support for SmartServer updates to images with missing security certificates
Corrected power factor reporting for Schneider PM5563 meters
Bug fixes and performance improvements

SmartServer IoT 2.5 Update 1

Release Date: July 30, 2019

Versions:

SmartServer IoT Software: 2.51.001
IzoT Net Export Utility: 1.20.147
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revisions A – E (Dual Core ARM Processor)

Downloads:

Changes:

Fixed MQTT broker connection error

SmartServer IoT 2.5

Release Date: July 12, 2019

Versions:

SmartServer IoT Software: 2.50.019
IzoT Net Export Utility: 1.20.094
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revisions A – E (Dual Core ARM Processor)

Downloads:

Changes:

Added a BACnet Server to provide a BACnet compliant interface to the SmartServer IoT
Added a BACnet Router to route BACnet communications from BACnet FT devices to BACnet/IP over Ethernet
Added an IAP edge device messaging interface
Simplified device definition with a new CMS Devices widget
Simplified device type definition with a new CMS Device Properties widget
Added a CMS Datapoint Browser widget to view and update datapoints on your edge devices
Bug fixes and performance improvements

SmartServer IoT 2.4

Release Date: May 17, 2019

Versions:

SmartServer IoT Software: 2.41.003 (CMS 2.41.001)
IzoT Net Export Utility: 1.20.094
Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revisions A – E (Dual Core ARM Processor)

Downloads:

Changes:

Initial release

EnOcean Edge Portal

SmartServer IoT Release Notes

License

Current Stable Release

SmartServer IoT 4.0

SmartServer IoT 3.6 Update 5

SmartServer IoT 3.6 Update 4

SmartServer IoT 3.6 Update 3

SmartServer IoT 3.6 Update 2

SmartServer IoT 3.6

SmartServer IoT 3.5 Update 2

SmartServer IoT 3.5 Update 1

SmartServer IoT 3.5

SmartServer IoT 3.4

SmartServer IoT 3.3

SmartServer IoT 3.2 Update 4

SmartServer IoT 3.2 Update 3

SmartServer IoT 3.2 Update 2

SmartServer IoT 3.2 Update 1

SmartServer IoT 3.2

SmartServer IoT 3.1 Update 3 Beta

SmartServer IoT 3.1

SmartServer IoT 3.0

SmartServer IoT 2.9

SmartServer IoT 2.8

SmartServer IoT 2.7 Update 1

SmartServer IoT 2.7

SmartServer IoT 2.6 Update 1

SmartServer IoT 2.6

SmartServer IoT 2.5 Update 2

SmartServer IoT 2.5 Update 1

SmartServer IoT 2.5

SmartServer IoT 2.4

SmartServer IoT Release Notes

License.css-779anb{display:inline;outline:none;background-color:transparent;border:none;color:var(--ds-icon, #42526E);cursor:pointer;right:0;}

Current Stable Release

SmartServer IoT 4.0

SmartServer IoT 3.6 Update 5

SmartServer IoT 3.6 Update 4

SmartServer IoT 3.6 Update 3

SmartServer IoT 3.6 Update 2

SmartServer IoT 3.6

SmartServer IoT 3.5 Update 2

SmartServer IoT 3.5 Update 1

SmartServer IoT 3.5

SmartServer IoT 3.4

SmartServer IoT 3.3

SmartServer IoT 3.2 Update 4

SmartServer IoT 3.2 Update 3

SmartServer IoT 3.2 Update 2

SmartServer IoT 3.2 Update 1

SmartServer IoT 3.2

SmartServer IoT 3.1 Update 3 Beta

SmartServer IoT 3.1

SmartServer IoT 3.0

SmartServer IoT 2.9

SmartServer IoT 2.8

SmartServer IoT 2.7 Update 1

SmartServer IoT 2.7

SmartServer IoT 2.6 Update 1

SmartServer IoT 2.6

SmartServer IoT 2.5 Update 2

SmartServer IoT 2.5 Update 1

SmartServer IoT 2.5

SmartServer IoT 2.4

License