/
SmartServer Release Notes

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 on this page 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 SmartServer, SmartConnect, and SmartSupervisor 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.6) 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.6

Release Date: June 8, 2025

Versions:

  • SmartServer IoT Software: 4.60.009

  • SmartConnect: 4.60.009

  • SmartSupervisor: 4.60.009

  • SmartServer BACnet Stack (included with SmartServer IoT and SmartConnect): 2.0.60

  • IzoT Net Export Utility: 1.60.001

  • Platform

    • Ubuntu Linux: 24.04

    • Linux kernel: 6.8.12

    • 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.4

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

Downloads: 

Changes: 

  • Improve long-term stability and security with a new version of Ubuntu Linux. Ubuntu has been updated to the 24.04 release, and the Linux kernel has been updated to the 6.8 release. Previously, SmartServer IoT used Linux 20.04 and Linux kernel 5.4. (AP-13037, AP-13985)

  • Improve security with the following additional security enhancements:

    • Several newly reported security vulnerabilities have been fixed. (AP-13992)

    • In some cases, signed security certificates were not enabled after re-imaging a SmartServer. (AP-13981)

    • Changing the SmartServer hostname from the SmartServer Linux console failed if signed certificates were enabled. (AP-14009 and AP-14021)

    • In some cases, SmartConnect login failed after disabling Enhanced Security. (AP-14044)

  • The following problems have been fixed:

    • In some cases, startup failed for SmartConnect 4.5. (AP-13989 and AP-13993)

    • The user was not informed about opening required ports on the SmartConnect host when enabling LON IP-852. (AP-13676)

    • Changing system time from the SmartConnect CMS appeared to work, but failed to update the system time. System time for SmartConnect must be set or changed using the SmartConnect host. System time is now read-only in the SmartConnect CMS. (AP-13033)

    • In some cases, the Configuration page System tab Download Log action failed. (AP-13984)

    • Custom IAP type definitions were not exported by the Device Types widget Export action. (AP-13982)

    • Minor errors in a Sequencing widget Node-RED flow could cause the SmartServer to crash due to excessive logging. (AP-14002)

    • In some cases, datapoints were not displayed correctly for newly created schedule events in the Calendar widget. (AP-13865, AP-13937)

    • In some cases, SmartServer failed or reported an incorrect error when you enabled LON power line repeating or updated a SmartServer with LON power line repeating enabled. (AP-13894, AP-13977, AP-13978, AP-14102)

    • Updates to datapoint values displayed as hex characters in the Datapoints widget failed. (AP-13957)

    • In some cases, CMS failed to start. (AP-13949)

    • CMS scroll bars were sometimes not usable. (AP-13975)

Warnings: 

  • The system time and date displayed in the SmartServer CMS is shown in UTC, not the local time zone. To view the local time, click the time in the CMS, or enter the date command in the SmartServer Linux console. (AP-14132)

  • The AIDE Advanced Intrusion Detection Environment is enabled by default. AIDE requires significant SmartServer resources when it runs, and can cause failures on heavily loaded SmartServers. To prevent failures from AIDE, disable it from the Configuration page System tab. (AP-14134)

  • You cannot view or modify a schedule event from a BACnet Client if the datapoint in the schedule event was derived from a field of a structured datapoint. (AP-14087)

  • The Service button does not work on the Configuration page LON tab. (AP-14138)

  • If you update a datapoint on a Modbus TCP device with no monitored datapoints, the update may fail. To prevent the failure, enable monitoring for any datapoint on the device. (AP-11902)

  • You cannot use accented characters in a connection template name. (AP-13931)

  • You cannot set an alternate time server from the CMS. To add an alternate time server, edit the NTP=0.pool.ntp.org entry in the /etc/systemd/timesyncd.conf file. (AP-13786)

  • In some cases, tags do not work with writable datapoints. (AP-13569)

  • 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 Platform software for the SmartServer IoT requires a quad core processor and will not run on SmartServer IoT hardware with a dual core processor.  You can determine which processor you have by reading the label on the bottom of the SmartServer IoT. 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, if you reprovision a device with a datapoint in a connection with one source and multiple destinations, the datapoint may be removed from the connection. (AP-12003)

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

  • Provisioning a LON device while using LON IMM can corrupt the device. When using LON IMM, only provision devices from your LON management tool. (AP-13927)

SmartServer 4.5 Update 2

Release Date: April 27, 2025

Versions:

  • SmartServer IoT Software: 4.52.002

  • SmartConnect: 4.52.002

  • SmartSupervisor: 4.50.007

  • SmartServer BACnet Stack (included with SmartServer IoT and SmartConnect): 2.0.60

  • IzoT Net Export Utility: 1.60.001

  • 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.4

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

Downloads: 

Changes: 

  • Pause LON device updates with the new LON device management lock.

Warnings: 

  • See Warnings for SmartServer 4.5.

SmartServer 4.5 Update 1

Release Date: April 27, 2025

Versions:

  • SmartServer IoT Software: 4.51.001

  • SmartConnect: 4.51.001

  • SmartSupervisor: 4.50.007

  • SmartServer BACnet Stack (included with SmartServer IoT and SmartConnect): 2.0.60

  • IzoT Net Export Utility: 1.60.001

  • 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.4

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

Downloads: 

Changes: 

  • Manage large deployments of EnOcean devices using the new built-in integration with EnOcean SmartStudio.

Warnings: 

  • See Warnings for SmartServer 4.5.

SmartServer 4.5

Release Date: February 19, 2025

Versions:

  • SmartServer IoT Software: 4.50.009

  • SmartConnect: 4.50.009

  • SmartSupervisor: 4.50.007

  • SmartServer BACnet Stack (included with SmartServer IoT and SmartConnect): 2.0.60

  • IzoT Net Export Utility: 1.60.001

  • 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.4

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

Downloads: 

Changes: 

  • SmartServer 4.5 has successfully achieved BACnet Testing Laboratories (BTL) certification from BACnet International. This certification represents a significant milestone in EnOcean’s commitment to providing reliable, interoperable, and open building automation solutions. See BTL Listing for details.

  • BACnet enhancements in support of BACnet certification by BACnet Testing Laboratories (BTL). (AP-6500, AP-13811, AP-13830, AP-13839, AP-13859, AP-13860, AP-13862, AP-13867, AP-13869, AP-13875)

  • Raspberry Pi 5 compatibility has been added for SmartConnect. (AP-13778)

  • Diagnostic information has been improved when exporting logs from the Configuration page System tab. (AP-13726)

  • Improve security with the following security enhancements:

    • PostgreSQL has been updated to release 16.4. (AP-13743)

    • U-boot has been updated to release 2021.01. (AP-13709)

    • Password auto-completion has been disabled for all password fields. (AP-13745)

    • Expired security certificates are removed after new certificates are installed. (AP-13584)

    • The node-pre-gyp package has been removed. (AP-13733)

  • The following problems have been fixed:

    • Restoration of devices after their restoration from the down state was broken in the 4.0 through 4.4 releases. (AP-13965)

    • Installing a USB flash drive sometimes failed. (AP-13825)

    • Enabling the EnOcean local antenna tunnel sometimes failed. (AP-13729)

    • Changing the hostname in the SmartServer Configuration page caused some SmartServer services to fail. (AP-13873)

    • Unexpected failures occurred when a SmartServer with a missing SD card was re-imaged. (AP-13826)

    • LON power line repeating sometimes failed after power was cycled on a SmartServer. (AP-13954)

    • The U70 LON power line interface sometimes failed. (AP-13781)

Warnings: 

  • If you update a datapoint on a Modbus TCP device with no monitored datapoints, the update may fail. To prevent the failure, enable monitoring for any datapoint on the device. (AP-11902)

  • In some cases, Node-RED flows can log an excessive amount of data and cause the SmartServer to fail. You can prevent the failure by reducing the Node-RED logging level. (AP-14002)

  • You cannot use accented characters in a connection template name. (AP-13931)

  • You cannot set an alternate time server from the CMS. To add an alternate time server, edit the NTP=0.pool.ntp.org entry in the /etc/systemd/timesyncd.conf file. (AP-13786)

  • In some cases, tags do not work with writable datapoints. (AP-13569)

  • 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 software for the SmartServer IoT requires a quad core processor and will not run on SmartServer IoT hardware with a dual core processor.  You can determine which processor you have by reading the label on the bottom of the SmartServer IoT. 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, if you reprovision a device with a datapoint in a connection with one source and multiple destinations, the datapoint may be removed from the connection. (AP-12003)

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

  • Provisioning a LON device while using LON IMM can corrupt the device. When using LON IMM, only provision devices from your LON management tool. (AP-13927)

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.4.

SmartServer 4.4

Release Date: July 8, 2024

Versions:

  • SmartServer IoT Software: 4.40.027

  • SmartConnect Software: 4.40.027

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

  • Accelerate device discovery with a new capability to select the protocols for the SmartServer to use for discovery. By default, the available protocols supporting discovery are BACnet, EnOcean, LON, LoRaWAN, and Modbus. Once you start discovery, you now see a summary of how long discovery has been active for each of your selected protocols, and you can now request the SmartServer to stop waiting for discovery to complete before going on to other tasks. See Discovering, Defining, or Importing Devices for more information. (AP-13036)

  • The Karaf, OSGi, JAX-RS, and Apache Shiro software components have been replaced by the Spring framework to improve SmartServer security. (AP-10881)

  • The OpenJDK, PostgreSQL JDBC, OAuth, and SAML software components have been updated to address security vulnerabilities in the earlier versions. (AP-13188, AP-13499)

  • Simplify datapoint logging setup with new default log parameters. (AP-12779)

  • SmartConnect now notifies you to change firewall configuration of your host when you enable BACnet. (AP-12963)

  • The following problems have been fixed:

    • In some cases, if you provisioned a LON device the provisioning failed if the device was on the far side of a LON router. (AP-13691)

    • In some cases, the CMS restarted multiple times after updating or re-imaging the SmartServer. (AP-13509)

Warnings: 

  • If you update a datapoint on a Modbus TCP device with no monitored datapoints, the update may fail. To prevent the failure, enable monitoring for any datapoint on the device. (AP-11902)

  • In some cases, Node-RED flows can log an excessive amount of data and cause the SmartServer to fail. You can prevent the failure by reducing the Node-RED logging level. (AP-14002)

  • You cannot use accented characters in a connection template name. (AP-13931)

  • Provisioning a LON device while using LON IMM can corrupt the device. When using LON IMM, only provision devices from your LON management tool. (AP-13927)

  • You cannot set an alternate time server from the CMS. To add an alternate time server, edit the NTP=0.pool.ntp.org entry in the /etc/systemd/timesyncd.conf file. (AP-13786)

  • In some cases, tags do not work with writable datapoints. (AP-13569)

  • 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, if you reprovision a device with a datapoint in a connection with one source and multiple destinations, the datapoint may be removed from the connection. (AP-12003)

  • 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.4 Beta

Release Date: May 31, 2024

Versions:

  • SmartServer IoT Software: 4.40.022

  • SmartConnect Software: 4.40.022

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

  • Bug fixes and performance improvements.

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

  • SmartConnect Software: 4.32.002

  • SmartSupervisor (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

  • SmartConnect Software: 4.31.003

  • SmartSupervisor (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

  • SmartConnect Software: 4.30.022

  • SmartSupervisor (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 SmartConnect software introduced in the 4.2 release with LON devices. Using SmartConnect 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 SmartConnect, 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 SmartConnect. (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

  • SmartConnect Software: 4.22.002

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