SmartServer Release Notes

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 current stable release followed by 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 current stable release identified below.  To ensure you get the best performance and most stable operation, always update to the current stable release of the SmartServer software. See Determining SmartServer Software Version Compatibility before updating to verify compatibility for your update. See Warnings in the release notes in this section and in SmartServer Troubleshooting for additional use-case specific warnings.


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 4.4 Update 2 for the SmartServer IoT and SmartServer 4.4 for SmartServer Pi and Remote CMS) are available here:

Descriptions and direct links for the current and previous releases are available in the following sections. Prior releases do not support all functionality of the current release. See Frequently Asked Questions for version-specific warnings for prior releases.

SmartServer 4.4 Update 2

Release Date: October 7, 2024

Versions:

  • SmartServer IoT Software: 4.42.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

    • Log4j: 2.17.1

    • Jetty Web Server: 9.4.43

    • NginX: 1.20.2

    • PostgreSQL: 16.05

  • Hardware Compatibility: Model 72201R-240 or 72201R-248, Hardware Revision F (Quad Core ARM Processor) or later

Downloads: 

Changes: 

  • Use Modbus devices with 64-bit or 32-bit floating point datapoints.

  • Compliance with BACnet scheduling requirements has been improved. (AP-13557)

  • Reliability and stability of device discovery has been impoved. (AP-13810, AP-13827)

  • Full system import reliability has been improved. (AP-13812)

Warnings: 

  • In some cases, if you click the CMS link in the SmartServer Configuration page, or if you enter the <IP address or hostname>/cms address for the SmartServer CMS in a web browser, you will see a Not Found error. If this happens, enter the following address in a web browser to open the CMS: <IP address or hostname>/cms/#/dashboard. (AP-13801)

  • See Warnings for SmartServer 4.3 Update 1.

SmartServer 4.4

Release Date: July 8, 2024

Versions:

  • SmartServer IoT Software: 4.40.027

  • SmartServer Pi Software: 4.40.027

  • SmartServer Remote CMS (beta): 4.40.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

    • 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: 

Warnings: 

  • TBD

  • For additional warnings, see SmartServer 4.3 Update 1.

SmartServer 4.4 Beta

Release Date: May 31, 2024

Versions:

  • SmartServer IoT Software: 4.40.022

  • SmartServer Pi Software: 4.40.022

  • SmartServer Remote CMS (beta): N/A

  • 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: 

  • TBD

Warnings: 

  • EnOcean has completed limited quality assurance (QA) testing of this update. Only use this update if you need any of the fixes addressed by this release.

  • For additional warnings, see SmartServer 4.3 Update 1.

SmartServer 4.3 Update 2

Release Date: July 15, 2024

Versions:

  • SmartServer IoT Software: 4.32.002

  • SmartServer Pi Software: 4.32.002

  • SmartServer Remote CMS (beta): 4.32.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.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 problem has been fixed:

    • Valid licenses sometimes failed. (AP-13755, AP-12956)

Warnings: 

  • See SmartServer 4.3 Update 1 warnings.

SmartServer 4.3 Update 1

Release Date: May 19, 2024

Versions:

  • SmartServer IoT Software: 4.31.003

  • SmartServer Pi Software: 4.31.003

  • SmartServer Remote CMS (beta): 4.31.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: 

  • The following problems have been fixed:

    • Importing a valid EnOcean or LoRaWAN Device Interface (XIF) definition sometimes failed in SmartServer 4.3. (AP-13616)

    • In some cases, the LON driver did not work in SmartServer 4.3. (AP-13573, AP-13627, AP-13653)

Warnings: 

  • EnOcean has completed limited quality assurance (QA) testing of this update. Only use this update if you need any of the fixes addressed by this release.

  • When you access trend reports with many logged datapoint values, CMS web page updates may be slow. Close any trend reports to restore normal performance. (AP-11847)

  • 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 400 MB. The SmartServer requires a minimum of 8 GB free space on the SD card for normal operation. For optimal performance, always keep 8 GB of free space on the SD card and keep logged data below 100 MB.    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.  If required, you can free up space on the SD card by reducing the frequency and retention period for logged data and by deleting backups.  To delete backups from the SD card, see Backing Up, Restoring, and Cloning the SmartServer.

  • The SmartServer 4.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 is not compatible with this release. 

  • 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 Datapoints widget, you can click the Refresh button in the upper right corner of the widget. (LUM-7145)

  • 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, 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, the CMS Sequencing widget may get stuck with an Adding Flows to Workspace message. Restart the SmartServer to eliminate the message. (AP-11297)

  • 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 4.3

Release Date: May 19, 2024

Versions:

  • SmartServer IoT Software: 4.30.022

  • SmartServer Pi Software: 4.30.022

  • SmartServer Remote CMS (beta): 4.30.022

  • 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: 

  • Use the SmartServer with large EnOcean networks with the new EnOcean Remote driver for the SmartServer. The EnOcean Remote driver for the SmartServer uses EnOcean’s IoT Connector (IoTC) to integrate with EnOcean devices communicating with EnOcean radios in Aruba and Cisco access points. This solution leverages the large building scalability offered by Aruba and Cisco access points and enables you to integrate the SmartServer with all the EnOcean devices that can be accessed by the access points in a building. (AP-12043)

  • Get support for more types of EnOcean devices with added support for EnOcean EDRPU, EMCS, ETHS, and STM550 devices. (AP-12108)

  • Get information on non-BACnet devices that are down when you access them from a BACnet workstation through the SmartServer BACnet Server. (AP-10558)

  • Use the SmartServer Pi software introduced in the 4.2 release with LON devices. Using SmartServer Pi software on your own Pi-compatible hardware you can now integrate with LON devices in addition to BACnet/IP, Modbus TCP, and Modbus RTU devices. (AP-12823)

  • The following problems have been fixed:

    • Viewing large data logs in the CMS Datapoints widget sometimes failed. (AP-12807)

    • Renewal of signed security certificates sometimes failed. (AP-12413)

    • In some cases, the SmartServer event scheduler would quit working after a change into or out of daylight savings time. (AP-12592)

    • The SmartServer sometimes deleted connections between SmartServer internal applications and LON edge devices on startup or restart. (AP-12511 and AP-12332)

    • LON datapoints using user-defined datapoint types could not be selected when creating a schedule event in the Calendar widget. (AP-12287)

    • In some cases, the SmartServer did not set the BACnet Current Command Priority property for a BACnet object after updating the Present Value and Priority for the object. (AP-12418)

    • IAP updates to a BACnet datapoint without a specified priority used priority 16. They now use normal priority which in IAP is encoded as priority 17. (AP-12475)

    • The SmartServer BACnet Router did not forward all qualifying BACnet messages. (AP-12417)

    • The SmartServer BACnet Router sent valid reject messages to the incorrect destination. (AP-12416)

    • When you enable BACnet on a SmartServer Pi, you will receive a new notification to open the required IP ports on your Pi. (AP-12963)

    • BACnet routing has been enhanced to prevent looping errors in unusual configurations. (AP-12795)

    • Performance and reliability of BACnet trend logs and schedules have been improved. (AP-11257 and AP-11258)

    • Logging from Node-RED has been reduced to prevent informational events from filling the flash drive on the SmartServer. (AP-12964)

    • In some cases, the SmartServer displayed an error message when you enabled Modbus RTU for one of the RS-485 ports. (AP-12081)

  • Advanced Intrusion Detection Environment (AIDE) is disabled by default. If your system security policy requires running AIDE, then you can enable this process to run once a day using the SmartServer System Configuration page. Enabling AIDE to run a daily cron job places a heavy demand on the CPU and filesystem that can impact system performance. See Configuring Advanced Intrusion Detection Environment (AIDE). This feature is not available for SmartServer Pi. (AP-11975)

Warnings: 

  • LON RNI may fail with this release. Use a different release if you required LON RNI. (AP-13627)

  • In some cases, importing a valid EnOcean or LoRaWAN Device Interface (XIF) definition may fail. Use a newer release if you need EnOcean or LoRaWAN support. (AP-13616)

  • When you access trend reports with many logged datapoint values, CMS web page updates may be slow. Close any trend reports to restore normal performance. (AP-11847)

  • 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 400 MB. The SmartServer requires a minimum of 8 GB free space on the SD card for normal operation. For optimal performance, always keep 8 GB of free space on the SD card and keep logged data below 100 MB.    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.  If required, you can free up space on the SD card by reducing the frequency and retention period for logged data and by deleting backups.  To delete backups from the SD card, see Backing Up, Restoring, and Cloning the SmartServer.

  • The SmartServer 4.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 is not compatible with this release. 

  • 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 Datapoints widget, you can click the Refresh button in the upper right corner of the widget. (LUM-7145)

  • 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, 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, the CMS Sequencing widget may get stuck with an Adding Flows to Workspace message. Restart the SmartServer to eliminate the message. (AP-11297)

  • 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 4.2 Update 1

Release Date: July 15, 2024

Versions:

  • SmartServer IoT Software: 4.22.002

  • SmartServer Pi Software: 4.22.002

  • SmartServer Remote CMS (beta): 4.22.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.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 problem has been fixed:

    • Valid licenses sometimes failed. (AP-13755, AP-12956)

Warnings: 

  • See SmartServer 4.2 warnings.

SmartServer 4.2

Release Date: January 2, 2024

Versions:

  • SmartServer IoT Software: 4.20.016

  • SmartServer Pi Software: 4.20.016

  • SmartServer Remote CMS (beta): 4.20.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: 

  • Try the beta release of EnOcean IoTC support. Using IoTC with the SmartServer, you can use the SmartServer to monitor EnOcean sensors communicating through an Aruba or Cisco Wi-Fi access point infrastructure. (AP-12042)

  • Use the SmartServer software on your own hardware with the new SmartServer Pi release. With SmartServer Pi, you can get the same notable features you have on a SmartServer IoT while running the software on a Raspberry Pi 4 or other hardware based on the Raspberry Pi Compute Module 4 (CM4). You will need a new SmartServer Core License plus a SmartServer Capacity license to activate the SmartServer software. (AP-11361)

  • Simplify integration with AI, energy usage optimization, and data analytics applications with custom device and datapoint tags that are automatically included with datapoint monitoring event messages. (AP-10905, AP-11987)

  • Complete your initial SmartServer setup using the new SmartServer Configuration page with a sleek new, modern, and fresh layout. (AP-11543)

  • Use the new region contexts to associate devices with geographical regions. (AP-11349)

  • Use BACnet workstations with the SmartServer to see all online and offline devices reported by the SmartServer BACnet server. In previous releases, the SmartServer BACnet Server did not report on offline devices. (AP-11666)

  • Accelerate your LoRaWAN deployments with one-touch installation of the SmartServer LoRaWAN Network Server (LNS) and LoRaWAN driver. (AP-11449)

  • Simplify Modbus device interface definition with support for Modicon addresses. (AP-11915)

  • Simplify integration with LON commissioning tools with SmartServer LON MAC ID reporting. (AP-11389)

  • The following problems have been fixed:

    • In some cases, connections including SmartServer internal datapoints and LON external datapoints were deleted and recreated on every startup. (AP-12332, AP-12511)

    • Security certificate renewal sometimes fails. (AP-12413)

    • In some cases, after upgrading to SmartServer 4.2 from a prior release or after restarting the SmartServer, some operational devices were marked down and shown with a red icon in the CMS Devices widget. (AP-11618, AP-11634)

    • In some cases, including upgrading to SmartServer 4.2 from a prior release, the Notification button in the CMS dashboard became disabled which disables all CMS warning and error notifications. (AP-11442)

    • In some cases, the SmartServer BACnet Server did not respond with the expected duplicate entry response for a schedule request with a duplicate entry. (AP-11261)

    • In some cases, the SmartServer BACnet Server responded with a value out-of-range error for a valid schedule request. (AP-11260)

    • Resetting the SmartServer databases sometimes failed. (AP-10959)

    • In some cases, when you deployed a connection template the SmartServer became non-responsive. (AP-11529)

    • Multi-select sometimes failed in the CMS Devices widget. (AP-12187)

Warnings: 

  • If you re-imaged or upgraded your SmartServer IoT to release 4.2, and LoRaWAN is not working, then perform the following steps to check if the LoRaWAN (lorawan) service failed to start, and if so, to restart the service:

  1. Open a terminal connection to the SmartServer IoT.

  2. Check if the lorawan service failed to start by entering the following command:

    sudo smartserverctl status lorawan

    If the lorawan service shows failed, then continue with the next step.

  3. Stop the lorawan service by entering the following command:

    sudo smartserverctl stop lorawan
  4. Start the lorawan service by entering the following command:

    sudo smartserverctl start lorawan
  5. Reboot the SmartServer by entering the following command:

    (AP-13651)

  • 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 400 MB. The SmartServer requires a minimum of 8 GB free space on the SD card for normal operation. For optimal performance, always keep 8 GB of free space on the SD card and keep logged data below 100 MB.    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.  If required, you can free up space on the SD card by reducing the frequency and retention period for logged data and by deleting backups.  To delete backups from the SD card, see Backing Up, Restoring, and Cloning the SmartServer.

  • In some cases, if you use the CMS Datapoints widget to browse a data log file with more than 100 MB of logged data, you may see a “Something Went Wrong” error. This is due to a timeout that is calculated based on the Rows per Page value. If you see this error, change the Rows per Page value to a larger size such as 50. (AP-12807)

  • The SmartServer 4.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 is not compatible with this release. 

  • 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 Datapoints widget, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)

  • 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, 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, the CMS Sequencing widget may get stuck with an Adding Flows to Workspace message. Restart the SmartServer to eliminate the message.

  • 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)

  • Updates to BACnet datapoints defined in the SmartServer BACnet Server occur at datapoint priority 16. This can prevent updates to the same datapoints from an internal SmartServer application using Normal priority. The workaround is to write the datapoints at priority 16 from any internal SmartServer applications. (AP-12475)

  • Advanced Intrusion Detection Environment (AIDE) is enabled by default. This process runs a daily cron job that creates a significant load on the CPU and filesystem. In cases where this process impacts system performance, you can disable AIDE manually through an SSH console session. See Configuring Advanced Intrusion Detection Environment (AIDE).

SmartServer IoT 4.1 Beta

Release Date: October 3, 2023

Versions:

  • SmartServer IoT Software (beta): 4.10.022

  • SmartServer Remote CMS (beta): 4.10.022

  • 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: 

  • Take control of security settings with new widget and context access controls, and a configurable session timeout, per user. (AP-10975, AP-10974, and AP-11252)

  • Simplify BACnet server configuration replication with BACnet type map export. All of your BACnet type map (BTM) files are now exported when you export SmartServer settings. (LUM-8875)

  • Access more BACnet Multi-State Input (MSI) objects with a new higher limit of 2500 MSI objects. (AP-11095)

  • Accelerate LoRaWAN device integration with auto-provision. The SmartServer now automatically provisions LoRaWAN devices when notified about a new LoRaWAN device by the LoRaWAN Network Server (LNS). (AP-10747)

  • Get more clarity on local time for the CMS host with CMS host local time display in the CMS dashboard. (AP-11060)

  • The following problems have been fixed:

    • When using Enhanced Security, you could not send a Service message from a SmartServer to an IP-852 channel when you pressed a Service/Connect or Send button on the Configuration page LON tab. (AP-11241)

    • If you updated a datapoint using the CMS Datapoints widget, in some cases there was up to a six second delay before the datapoint was updated due to throttling in the SmartServer. (AP-11182)

    • In some cases, if you deleted a discovered device and later re-discovered the device, the device would be shown with a gray icon in the CMS Devices widget. The gray state indicated the device is not fully defined. (AP-11310)

    • In some cases, if you provisioned a LON device in the CMS Devices widget, you would see yellow notification messages reporting communication failures. (AP-10794)

    • The column sort buttons did not work in the CMS Datapoints widget. (AP-11189)

    • In some cases, self-signed security certificates were not updated correctly. (AP-10988)

    • In some cases, deployed connections could not be removed. (AP-10957)

    • Down devices were not visible from BACnet workstations when using the SmartServer BACnet Server. (AP-11666)

    • In some cases, updating exception schedule for BACnet Scheduler objects failed. (AP-10387)

    • In some cases, local BACnet broadcasts were not correctly forwarded to BBMDs. (AP-11069)

    • In some cases, the BACnet Server returned the wrong datapoint with the BACnet Trend Log object. (AP-11259)

    • When creating a connection, in some cases the default direction for a datapoint in a connection template was not appropriate for the datapoint. (AP-11054)

    • Some resource types were not processed correctly. (AP-11839)

Warnings: 

  • If you operate the 4.1 beta release at a sustained rate of 20 events per second (EPS) or higher, your SmartServer may reboot every week. This is one half of the 40 EPS sustained rate expected for production releases. To prevent reboots, keep the sustained EPS below 20 EPS. This is the reason 4.1 has been released only as a beta. If you require less than 20 EPS sustained performance, you can use the 4.1 release for production systems.

  • 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 SmartServer requires a minimum of 8 GB free space on the SD card for normal operation. For optimal performance, always keep 8 GB of free space on the SD card and keep logged data below 100 MB.    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.  If required, you can free up space on the SD card by reducing the frequency and retention period for logged data and by deleting backups.  To delete backups from the SD card, see Backing Up, Restoring, and Cloning the SmartServer.

  • The SmartServer 4.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 is not compatible with this release. 

  • In some cases, after upgrading to SmartServer 4.1 from a prior release or after restarting the SmartServer, some operational devices will be marked down and shown with a red icon in the CMS Devices widget. You can mark a device incorrectly shown as down as up with a green icon by testing the device in the CMS Devices widget. (AP-11618, AP-11634)

  • In some cases, including upgrading to SmartServer 4.1 from a prior release, the Notification button in the CMS dashboard can become disabled which will disable all CMS warning and error notifications. To re-enable notifications, click the Notifications button. (AP-11442)

  • When defining a Modbus XIF with 5-digit addresses, the address may be misinterpreted as a Modicon address. To work around, encode the address as a Modicon address by adding one to the address and putting a prefix of 0 (FC00),1 (FC01), 3 (FC04) or 4 (FC03) onto the address and omit the separate function code. (AP-11915)

  • Multi-select sometimes fails in the CMS Devices widget due to system events cancelling your selection. (AP-12187)

  • 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 Datapoints widget, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)

  • 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, when you deploy a connection template the SmartServer may become non-responsive. Restart the SmartServer to recover. (AP-11529)

  • 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, the CMS Sequencing widget may get stuck with an Adding Flows to Workspace message. Restart the SmartServer to eliminate the message.

  • 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)

  • Advanced Intrusion Detection Environment (AIDE) is enabled by default. This process runs a daily cron job that creates a significant load on the CPU and filesystem. In cases where this process impacts system performance, you can disable AIDE manually through an SSH console session. See Configuring Advanced Intrusion Detection Environment (AIDE).

SmartServer IoT 4.0 Update 1

Release Date: July 16, 2024

Versions:

  • SmartServer IoT Software: 4.01.002

  • SmartServer Remote CMS (beta): 4.01.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.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 problem has been fixed:

    • Valid licenses sometimes failed. (AP-13755, AP-12956)

Warnings: 

  • See SmartServer 4.0 warnings.

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)

  • Enjoy improved system stability with the systemd system and service manager. We have replaced Supervisor (Supervisor Introduction) with Systemd (systemd Introduction) Supervisor as the system and service manager for the SmartServer. Custom applications and services for the SmartServer that used the supervisorctl interface to supervisord must be updated to use the new smartserverctl interface to systemd. See System and Service Management for details.

  • 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 is not compatible with this release. 

  • 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, disable Enhanced Security as described in Enhancing Security . (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)

  • Advanced Intrusion Detection Environment (AIDE) is enabled by default. This process runs a daily cron job that creates a significant load on the CPU and filesystem. In cases where this process impacts system performance, you can disable AIDE manually through an SSH console session. See Configuring Advanced Intrusion Detection Environment (AIDE).

SmartServer IoT 3.6 Update 6

Release Date: July 15, 2024

Versions:

  • SmartServer IoT Software: 3.66.002

  • SmartServer Remote CMS (beta): 3.66.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.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:

    • Valid licenses sometimes failed. (AP-13755, AP-12956)

Warnings: 

  • See SmartServer 3.6 Update 5 warnings.

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 causing a CENELEC protocol error message to be displayed on the Configuration page LON tab and required a reset to become operational. The fix requires U70 Firmware 2.0 or later as described in U70 Firmware Release Notes. (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 is not 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 a