Echelon SmartServer 2.2 ReadMe

Release 4.06.048, October 2013

Copyright © 1998 – 2013 Echelon® Corporation
All Rights Reserved

1      Introduction

This document describes SmartServer 2.2.  The SmartServer 2.2 software is included with SmartServer 2.2 Controllers, and you can apply SmartServer 2.0 Service Pack 4 (SP4) to update previous SmartServer 2.0 installations to the SmartServer 2.2 software.  See the SmartServer 2.2 User’s Guide for installation instructions for installing the SmartServer 2.2 software included with SmartServer 2.2 Controller.  See Installing SmartServer 2.2 for instructions on installing the update and verifying that it has been installed.

Additional information and updates, including service packs and critical updates, may be available at  The latest service packs and updates may not be included with your SmartServer.  See Echelon’s Knowledge Base at for answers to frequently asked questions.

SmartServer 2.2 is compatible with 64-bit and 32-bit versions of Windows 8 and Windows 7, and is also compatible with 32-bit versions of Windows Vista and Windows XP.  To provide full functionality, the SmartServer software must be used with Microsoft Internet Explorer 8 or newer, Mozilla Firefox 9 or newer, Chrome 16 or newer, or iOS 5.1 Safari or newer.  If you are using a SmartServer with an LNS® Server, OpenLNS Server, the LonMaker® Integration Tool, or the OpenLNS Commissioning Tool, you must be using the latest releases of each.

2       Contents

1       Introduction. 1

2       Contents 1

3       Release Identification. 3

4       Installing SmartServer 2.2. 4

5       Changes in SmartServer 2.2. 5

5.1        Changes in SmartServer 2.0 SP4 / SmartServer 2.2. 5

5.1.1    Device Discovery. 5

5.1.2    Device Authentication. 5

5.1.3    Improved Device Image Download Time. 5

5.1.4    SSL Support for LNS Proxy. 5

5.1.5    LonWorks Connections in Standalone Mode. 5

5.1.6    Increased Device and Data Point Limits in Standalone Mode. 6

5.1.7    Maintenance Network Management Mode. 6

5.1.8    Static Repeating Mode. 6

5.1.9    Enhanced XMPP Client 6

5.1.10      OpenLNS Server and OpenLNS Commissioning Tool Support 6

5.1.11      Version 14 Standard Resource File Set 6

5.1.12      Improved Web Page Performance. 6

5.1.13      64-Bit Windows Support 6

5.1.14      Cross Browser Support 6

5.1.15      Additional Language Support 6

5.2        Changes in SmartServer 2.0 SP3. 7

5.2.1    Device Capacity. 7

5.2.2    Web User Interface. 7

5.2.3    Web Browser Compatibility. 7

5.2.4    Standard Resource File Set 7

5.2.5    Modbus Driver 7

5.2.6    XMPP Service. 7

5.2.7    SNMP Service. 7

5.3        Changes in SmartServer 2.0 SR2/SP2. 7

5.3.1    Cinterion MC75 and MC63i Series Modem Support 7

5.3.2    M-Bus Enhancements 7

5.3.3    Enhanced Authentication Security. 8

5.3.4    Internet Explorer 9 Support 8

5.4        Changes in SmartServer 2.0 SP1. 8

5.4.1    Secure Web Binding. 8

5.4.2    Battery Status 8

5.4.3    Rapid Deployment 8

5.4.4    Chinese, Japanese, and Korean Language Support 8

5.4.5    New Data Types 8

5.4.6    Release 4.04 Update. 8

5.4.7    Custom Datapoint Selector 9

5.5        Fixes 9

6       Known Problems and Workarounds 17

6.1        Slow Commissioning for Street Light Networks 17

6.2        Incorrect Offline Reports for Street Light Networks 18

6.3        6-Byte Authentication Keys Fail with the CRD 3000. 18

6.4        Intermediate SSL Certificates not Supported. 18

6.5        Commissioning Devices with Changeable-Type NVs 18

6.6        Persistent Synchronization Error Message. 18

6.7        Misleading Alarm Notifier Error Message. 18

6.8        Analog Functional Block (AFB) Reset Error 19

6.9        Disabled Security Web Page Cannot Be Enabled. 19

6.10     Cellular Carrier Network Incompatibility. 19

6.11     Releasing Neuron ID Strands Devices 19

6.12     Using a Double Quote (“) Character in a Unit String. 19

6.13     Using a Duplicate IP Address Range for Different Interfaces 19

6.14     Misconfigured Heartbeats on Local NVs 20

6.15     Long Exception Names 20

6.16     Internal Turnaround LON Connection Failure in PL Repeating Mode 20

6.17     LON Connection Failure with Uncommissioned iLON App 20

6.18     i.LON 100 Plug-in Launch Failure. 20


3       Release Identification

This document applies to SmartServer 2.2 (Release 4.06.048).  To determine which release of the SmartServer software you have installed on your computer, follow one of the following procedures:

·       For Windows 8, Windows 7, and Windows Vista, click the Start button, type Programs and Features in the Search box, press ENTER to open Programs and Features, and then click Echelon i.LON SmartServer [Release] Software.  If the Version column is not displayed, right click the list header, select More, and then select Version to add the Version column. 

·       For Windows XP, open Add or Remove Programs in Windows Control Panel, and then click Echelon i.LON SmartServer [Release] Software.  Click the Click Here for Support Information link.

To determine which release of the SmartServer firmware you have installed on your SmartServer, see the Firmware Version property in the Setup ‑ System Info Web page as described in the SmartServer 2.2 User’s Guide in Chapter 3, Viewing System Information and Performance, or by typing show in a SmartServer console window. 

The following table summarizes the SmartServer and i.LON 100 e3 plus release history, with SmartServer 2.2 highlighted:




i.LON 100 e3 plus


April 2008

i.LON 100 e3 plus SP1


December 2009



January 2008

SmartServer SR1


March 2008

SmartServer SR2 and SP2


October 2008

SmartServer 2.0


October 2009

SmartServer 2.0 Update 1


January 2010

SmartServer 2.0 SP1


August 2010

SmartServer 2.0 SR2 and SP 2


February 2011

SmartServer 2.0 SR2 and SP2 Update 1


July 2011

SmartServer 2.0 SP3


May 2013

SmartServer 2.1 Firmware (streetlight system use only)


October 2010

SmartServer 2.1 Firmware SR1 (streetlight system use only)


November 2012

SmartServer 2.0 SP4 / SmartServer 2.2


October 2013

4       Installing SmartServer 2.2

You can install the SmartServer 2.2 software from a SmartServer 2.2 download image or DVD, or update any prior release of SmartServer 2.0 to SmartServer 2.2 by installing SmartServer 2.0 SP4.  Prior releases are SmartServer 2.0 with no service packs, SmartServer 2.0 SP1, SmartServer 2.0 SR2, SmartServer 2.0 SP2, and SmartServer 2.0 SP3. 

SmartServer 2.0 SP4 is available as a free download at but can only be installed on a computer with a prior release of the SmartServer 2.0 software.  To upgrade the i.LON 100 e3 Plus or SmartServer 1.0 software, you can purchase a license for the SmartServer 2.2 Software and the software will be provided to you as a software download.  The SmartServer 2.2 software will not run on hardware releases prior to the i.LON 100 e3 Plus due to the smaller memories of the prior releases.

To install the SmartServer 2.2 software, follow these steps:

1.     If you are installing the SmartServer 2.2 software from a SmartServer 2.2 DVD, insert the DVD into your DVD drive.  If your computer does not have a DVD drive, insert the Echelon SmartServer 2.2 DVD on a network accessible computer that has a DVD drive and copy the files on the DVD to a shared network drive.  If the SmartServer 2.2 setup application does not start immediately, open the setup.exe file on the root directory of the Echelon SmartServer 2.2 DVD.

If you are installing SmartServer 2.2 from a file that you downloaded from the Echelon website, double-click the downloaded file in Windows Explorer to extract all the files.  Click OK when all the files are extracted.  The SmartServer 2.2 setup application will start automatically.

2.     The Echelon SmartServer 2.2 setup application main menu appears.

3.     Click Install Products.  The Install Products dialog appears.

4.     Click Echelon SmartServer 2.2 Software.  The Echelon SmartServer 2.2 Software installer appears.

5.     Follow the steps of the installation wizard.  If you have an existing installation of the SmartServe 2.0 software, the installation will automatically update it to SmartServer 2.2.  See Chapter 2 of the SmartServer 2.2 User’s Guide for more information on installing the SmartServer 2.2 software.

6.     Update the firmware in your SmartServers to the SmartServer 2.2 firmware.  See Upgrading the SmartServer Firmware in Chapter 2 of the Echelon Enterprise Services 2.2 User’s Guide for details on how to update the firmware.

5       Changes in SmartServer 2.2

5.1    Changes in SmartServer 2.0 SP4 / SmartServer 2.2

5.1.1     Device Discovery

Scan command for device discovery on repeating channels can now be done for unconfigured devices (NST_UNCONFIGURED) and previously commissioned or preconfigured devices (NST_SELECTED).  In addition, the Scan command can also be used to limit the number of discovered devices per agent and to start predictive device discovery.  (67948, 67951)

5.1.2     Device Authentication

An optional AuthenticationKey property has been added to the LON device property page to provide security during device commissioning.  This optional key is used when a device is added or replaced through the SNM. (67949, 67950)

5.1.3     Improved Device Image Download Time

For improving device image download time, a new LCA_MAINTENANCE mode has been added to the UCPTmgmtMode in the LON_Netowrk_Cfg to suppress sending of heartbeats and poll requests to the network. (57447, 57823, 67967)

5.1.4     SSL Support for LNS Proxy

SmartServer is now able to contact and synchronize with the LNS Proxy in EES through SSL. (68134, 68625)

5.1.5     LonWorks Connections in Standalone Mode

Create peer-to-peer connections in standalone networks with repeating for rapid response to external events.

5.1.6     Increased Device and Data Point Limits in Standalone Mode

Install up to 300 devices and use up to 2000 data points in a standalone network.  The limits may be lower depending on the number of data points and custom apps.

5.1.7     Maintenance Network Management Mode

Rapidly commission networks by disabling data point heartbeats and polling messages.

5.1.8     Static Repeating Mode.

Optimize the performance of power line repeating channels by disabling the periodic verification of repeating paths.

5.1.9     Enhanced XMPP Client

Use real-time bi-directional communication between SmartServers and enterprise applications located behind firewalls.  The SmartServer’s built-in XMPP client now supports connections where the IP address changes because of lease timeouts, and it is  now compatible with Openfire.

5.1.10 OpenLNS Server and OpenLNS Commissioning Tool Support

Integrate the SmartServer in networks managed with an OpenLNS Server.  Use the SmartServer with networks managed with the OpenLNS Commissioning Tool (OpenLNS CT).

5.1.11 Version 14 Standard Resource File Set

The standard resource file set has been updated to Version 14.

5.1.12 Improved Web Page Performance

Performance of built-in and custom Web pages has been improved.

5.1.13 64-Bit Windows Support

SmartServer 2.2 is compatible with 64-bit versions of Windows 8 and Windows 7, in addition to the previously supported 32-bit versions of Windows 8, Windows 7, Windows Vista, and Windows XP.

5.1.14 Cross Browser Support

View SmartServer 2.2 built-in and custom Web pages using Chrome and Safari in addition to previously supported browsers (Internet Explorer and Firefox).  SmartServer 2.2 has been tested with Internet Explorer 8 and 9; Firefox 9, 10, and 11; Chrome 16, 17, and 18; and iOS 5.1 Safari.

5.1.15 Additional Language Support

View SmartServer 2.2 built-in and custom Web pages in Chinese, Korean, and Japanese in addition to previously supported languages (English, French, and German).

5.2    Changes in SmartServer 2.0 SP3

5.2.1     Device Capacity

The device capacity has been increased to 300 from 200.  The limit may be lower depending on the number of data points and custom apps. (63507, 63376, 62947, 63373, 64192)

5.2.2     Web User Interface

Web page performance for built-in and custom Web pages has been improved. (62793, 63669)

Displaying and updating data points has been improved. (50499, 63356, 63444)

5.2.3     Web Browser Compatibility

A Web page timing issue with Firefox 6.0.2 has been fixed. (62965)

Scrolling has been improved with Chrome. (65356)

Data log viewing has been improved and crashes have been addressed in Internet Explorer 9. (59850, 59983)

The message to download the Adobe SVG viewer has been changed. (64332)

5.2.4     Standard Resource File Set

The standard resource file set has been updated to Release 13.10. (63449)

5.2.5     Modbus Driver

A tracing option has been added for the Modbus driver.  The Modbus driver displays bus activity in the console when trace level 2 is selected.  (63519)

5.2.6     XMPP Service

You can now set SASL, SLL, BOSH, and XMPP ping interval options from the Web user interface and via SOAP. (67598)

You can now start and stop the XMPP message service. (67656)

5.2.7     SNMP Service

You can now enable or disable the SNMP service from a built-in Web page. (62147)

5.3    Changes in SmartServer 2.0 SR2/SP2

5.3.1     Cinterion MC75 and MC63i Series Modem Support

Support has been added for the Cinterion MC75 and MC63i series modems. (59478)

5.3.2     M-Bus Enhancements

The retry count can now be specified for M-Bus devices. (59476, 59477)

5.3.3     Enhanced Authentication Security

The hashing algorithm used to verify passwords has been enhanced to use standard SHA-512 hashing. (57978)

5.3.4     Internet Explorer 9 Support

Support has been added for viewing and updating SmartServer Web pages using Internet Explorer 9. (59564)

5.4    Changes in SmartServer 2.0 SP1

5.4.1     Secure Web Binding

You can now create secure Web connections that use SSL encryption.  See Chapter 4 of the SmartServer 2.2 User’s Guide for documentation.  (57043)

5.4.2     Battery Status

A new battery status indicator has been added to the System Information Web page, and a battery status data point has been added that you can use to trigger an alarm when the battery is low.  See Chapter 3, Viewing System Information and Performance in the SmartServer 2.2 User’s Guide for documentation.  (57395)

5.4.3     Rapid Deployment

The EES 2.0 AdminServer no longer stores the standard SmartServer firmware files in the template when you create an i.LON template.  This significantly reduces the time required to create and deploy i.LON templates.  See Rapid SmartServer Deployment in the ReadMe document for the Echelon Enterprise Services for documentation.

The EES 2.0 AdminServer can now be used to create and deploy components to up to 100 SmartServers at a time.  A component is any collection of files that you want to deploy to one or more SmartServers from an AdminServer.  For example, a component may consist of an FPM app, resource files, XIF files, and custom Web pages that you want to deploy to one or many SmartServers.  See Rapid Component Deployment in the ReadMe document for the Echelon Enterprise Services for documentation. (57345)

5.4.4     Chinese, Japanese, and Korean Language Support

Built-in Web pages are now available in Chinese, Japanese, and Korean language versions, in addition to the previous English, French, and German versions. (57186)

5.4.5     New Data Types

New data types have been added to support Modbus timing parameters. (57165)

5.4.6     Release 4.04 Update

The EES 2.0 AdminServer can now update a Release 4.03 SmartServer 2.0 to Release 4.04 (SmartServer 2.0 with SP1). (56858)

5.4.7     Custom Datapoint Selector

The i.LON Vision 2.0 datapoint selector has been enhanced for custom Javascript objects.  See Chapter 5 of the i.LON Vision 2.2 User’s Guide for i.LON Vision for documentation.  (53258)

5.5    Fixes

The following table summarizes problems fixed in the SmartServer 2.1 and 2.0 releases and service packs.  The EPR column lists Echelon internal problem tracking numbers.  The release or service pack that first included the fix is listed in parentheses.




Time sometimes drifted multiple seconds per day. (2.0)


C# SOAP client reported an "underlying connection was closed" error. (2.0)


An extra TAB or click was sometimes required to enter a preset value for a data point.  (2.1 SR1)


The Alarm Notifier: Summary Web page displayed obsolete active alarm entries after comments were changed. (2.0)


Reloading an app rebooted the SmartServer if more than one app was being developed. (2.0)


Calculation of daylight savings time (DST) did not work in the southern hemisphere. (2.0)


You could not write configuration properties when the SmartServer was using OpenLNS and LNS management mode and the OpenLNS or LNS Server was not attached to the network. (2.0)


A resource conflict between an external modem and the Modbus driver was reported, even if no modem was selected. (2.0)


The RS‑485 interface sometimes caused the SmartServer to reboot when Data+ and Data‑ lines were not connected correctly. (2.0)


Disabled SNTP synchronization was not re‑enabled after communication with the SNTP server was restored. (2.0)


Real‑time clock synchronization sometimes failed after switching to the backup SNTP server if the backup SNTP server also failed as well. (2.0)


Writes to Modbus multi-write coil registers sometimes failed. (2.0)


In OpenLNS and LNS management mode, synchronization of a router sometimes caused an endless loop if the channel of the far side was not defined in the LNS Server. (2.0)


If you added a data point that is a bound in a Web connection to an Alarm Generator, the Web connection stopped functioning.  (2.0 SP1)



In an OpenLNS or LNS managed network, if you created external functional blocks and data points on the SmartServer without first creating the parent external device, the external functional blocks and data points would not be synchronized. (2.0 SP1)


Commissioning a device in standalone mode did not disable self‑installation. (2.0 SP1)


Synchronization did not match external data points created in and OpenLNS or LNS Server with existing data points on the SmartServer that have the same name but are marked as deleted. (2.0 SP1)


The Alarm Generator did not properly maintain the alarm condition for a data point when an analog comparison function was used. (2.0 SP1)


Rebooting the SmartServer sometimes caused the Modbus driver to fail. (2.0 SP1)


The following problems sometimes occurred if the computer time was set to a local time zone that has a negative offset from UTC:  SmartServer Web pages may slow down or even fail; you could not create external network variables; and a warning message appeared in the SmartServer Web pages every day in January after a specific time. (2.0 SP1)


In some cases you could not set the SmartServer system time.  (2.0 SP1)


The Data Logger SOAP Read Response message sometimes omitted some data log entries. (2.0 SP1)


The scope of user‑defined network variable types (UNVTs) was sometimes incorrect. (2.0 SP1)


In some cases the Data Logger leaked memory when reading data. (2.0 SP1)


The Edit dialog in the Scheduler application did not always display the correct schedule name after you modified the daily schedules in the Edit Daily Schedules dialog. (2.0 SP1)


In some cases, the Scheduler did not import an exception from the calendar when the UCPTindex property was not specified correctly. (2.0 SP1)


In some cases a network monitor would cause the SmartServer to reboot. (2.0 SP1)


A Modbus template sometimes caused a .NET application to fail. (2.0 SP1)


Invalid time zone offsets in the system time sometimes caused the SmartServer to fail. (2.0 SP1)


The SmartServer had to be rebooted to calculate the current number of internal FPM devices correctly because the SmartServer did not include deleted internal FPM devices in the current count of available devices.  The SmartServer only allows nine internal FPM devices to be created. (2.0 SP1)


Devices created and installed automatically from device templates sometimes did not have correct data point values initially. (2.0 SP1)


The SmartServer Web interface sometimes failed with Firefox 3.6.  (2.0 SP1)


The SmartServer console application did not notify the user if the WebParams.dat file was missing. (2.0 SP1)


You could not programmatically write data point values in raw hex format. (2.0 SP1)


Modbus writes within a short interval were not aggregated. (2.0 SP1)


The Data Logger did not return correct UTF8 alias names in response to a data logger read function. (2.0 SP1)


Some operations were very slow in IE8. (2.0 SP1)


Auto-selected Smart Network Management settings caused current .APB and .XIF files to be overwritten. (2.0 SP1)


You had to clear your browser’s cache after manually uploading .zip files to the SmartServer to update its image.  (2.0 SP1)


The Alarm Notifier’s nviAnEnable data point did not enable or disable the notification and data point update functions. (2.0 SP1)


SMTP messages were sent using small (74 byte) packets, which caused extra overhead in network traffic. (2.0 SP1)


Cinterion modems had incorrect AT commands. (2.0 SP1)


NV indexes were sometimes not updated correctly after the program ID for a device changed. (2.0 SP1)


Deleting a virtual functional block sometimes corrupted references from other functional blocks to datapoints referenced by the virtual functional block. (2.0 SR2/SP2)


When using LNS network management mode with the LonMaker Integration Tool, if you used the SmartServer navigation pane or an LNS plug-in to create a connection to a dynamic NV on the SmartServer, the connection sometimes did not appear on the LonMaker drawing. (2.0 SR2/SP2)


The Device Overview Web page sometimes did not display devices discovered by subsequent scans. (2.0 SR2/SP2)


The Scheduler SOAP Read Response message sometimes did not include events created at midnight. (2.0 SR2/SP2)


A Web Binding Target service could not be added to an LNS Proxy host device in the SmartServer Web interface. (2.0 SR2/SP2)


Creating an Exception Schedule in the Scheduler sometimes caused the SmartServer to reboot. (2.0 SR2/SP2)


The M-Bus driver failed when the SmartServer was rebooted. (2.0 SR2/SP2)


Web connections with file attachments failed with some Web servers for files larger than 4 Kbytes. (2.0 SP2)


The Apps for the SmartServer’s static functional blocks (Digital Input, Digital Output, Pulse Counter, and Real-Time Clock) failed when the SmartServer’s internal i.LON App device was deleted and then re-created. (2.0 SR2/SP2)


Offline Modbus devices sometimes caused a memory leak. (2.0 SP2)


Fields of structured data types within arrays could not be formatted correctly. (2.0 SR2/SP2)


The Edit Value dialog in the Data Point: View Web page could not be used to update the fields of structured data types within arrays. (2.0 SR2/SP2)


The Setup – Security Web page could not be opened sometimes. (2.0 SR2/SP2)


In some cases the Data Logger and Alarm Notifier View Web pages consumed a lot of the SmartServer’s CPU and made many operations seem non-responsive. (2.0 SR2/SP2)


The warning message displayed when there were too many entries to be displayed in the Data Logger and Alarm Notifier View Web pages was confusing. (2.0 SR2/SP2)


The slider button in the Data Logger and Alarm Notifier View Web pages was hard to use when viewing short intervals within a long-term log. (2.0 SR2/SP2)


The SmartServer sometimes queued too many SOAP requests causing excessive SmartServer CPU usage. (2.0 SR2/SP2)


No error was displayed when the SmartServer did not have enough RAM for the deletion of data and alarm log entries. (2.0 SR2/SP2)


Modifying the Smart Network Management commands in the Setup - LON Device Web page immediately after instantiating a device external interface (XIF) file caused duplicate devices to be created. (2.0 SR2/SP2)


The Data Logger did not record data point string values containing the embedded ‘>’ and ‘<’ characters. (2.0 SR2/SP2)


The Alarm Notifier: Summary Web page stopped polling if you navigated away from it. (2.0 SP1)


Opening the Configure – Data Point Web page for some data points caused the SmartServer Web interface to fail.  (2.0 SR2/SP2)


The Alarm Notifier could fail and cause the SmartServer to reboot.  (2.0 SR2/SP2)


The Real Time Clock SOAP Set Request message expired if received before time change and processed thereafter. (2.0 SR2/SP2)


The Data Logger: View Web page displayed only one value once the Web page’s cache overflowed.  (2.0 SR2/SP2)


The Data Logger SOAP Read Response message does not include data from compressed (.gz) log files. (2.0 SR2/SP2)


The SVG trend graphs in the Data Logger and Alarm Notifier View Web pages did not function with Microsoft Internet Explorer 9.


The Data Logger: View Web page did not display all data points for a given Data Logger if that logger was recording multiple data points.  (2.0 SR2/SP2)


The Data Logger SOAP Read Response message did not return data in the frequency specified by the poll rate. (2.0 SR2/SP2)


The Data Logger log files included multiple entries for the same update. (2.0 SR2/SP2)


The SmartServer would sometimes permanently fail to start the SmartServer applications if a power sag occurred during the boot process. (2.0 SR2/SP2)


Dynamic data points required for apps were sometimes deleted after a reboot. (2.0 SR2/SP2)


Devices based on an FT 5000 Smart Transceiver and any devices running Neuron firmware version 19 could not be commissioned by a SmartServer running in standalone mode.  (2.0 SR2/SP2)

48940, 56434

Missing formats could not be added for data points. (2.0 SP3)

52902, 63354

Modbus messaging sometimes failed if there were many Modbus data points. (2.0 SP3)

57385, 63252

Adding an XMPP message service without any credentials or with an empty configuration caused unexpected reboots. (2.0 SP3)

59606, 60541

There was a memory leak during SOAP message processing. (2.0 SP3)


A Calendar did not work without reference to nvoDateEvent. (2.0 SP3)


Adding a Modbus data point sometimes failed. (2.0 SP3)


Discovering and commissioning a new device in standalone mode sometimes caused the SmartServer to crash. (2.0 SP3)


The data server did not properly handle an NV length change of a changeable type NV. (2.0 SP3)

62533, 64191

LON device commissioning failed if the device template had an incorrect subnet. (2.0 SP3)


Deploying a template in LNS mode often resulted in Error 25 Device In Use. (2.0 SP3)


The data point references to the nviEnable, nviClear, nvoLevelAlarm, and nvoStatus data points were missing after adding 1000 data points for logging. (2.0 SP3)


Time zone and daylight savings settings for some regions were incorrect. (2.0 SP3)


A watchdog reset would sometimes cause multiple reboots. (2.0 SP3)

63268, 63706

It was not possible to create a RAW_HEX data point with a length of more than one byte. (2.0 SP3)

63374, 64193

The timeout was too short when starting many apps. (2.0 SP3)


A Data Logger continued to log during reboot when it was disabled. (2.0 SP3)


Menus were sometimes invisible after converting i.LON 100 e3 Web pages. (2.0 SP3)


Setting the time zone sometimes failed. (2.0 SP3)


Deleting and creating apps sometimes caused the data server to fail. (2.0 SP3)


The Pulse Counter output value sometimes incorrectly decreased. (2.0 SP3)

65540, 67430

SmartServer sometimes crashed or stalled when making multiple LON connections using the LonMaker Integration Tool. (SmartServer 2.2)


The system information message service could not be accessed when the XMPP message service was enabled. (2.0 SP3)


The XMPP message service did not reconnect with the XMPP server after a dynamic IP address change. (2.0 SP3)

67357, 67560

The Alarm Generator and Alarm Notifier did not observe set/clear delays. (2.0 SP3)


The SmartServer sometimes crashed when creating many Web connections. (2.0 SP3)


The time to next state field of a SNVT_TOD_event output from a Scheduler was not updated correctly. (2.0 SP3)


Two consecutive single quotes could not be used in a SOAP request. (2.0 SP3)


An empty password could not be specified when configuring the XMPP message service. (2.0 SP3)


Some LON devices were not commissioned after deploying a template with EES. (2.0 SP3)


Sockets were not correctly released after changing the XMPP message service. (2.0 SP3)


Radio buttons for NVL data points were sometimes disabled after converting an i.LON 100 e3 Web page. (2.0 SP3)



The XMPP service did not correctly handle non-default BOSH server paths. (2.0 SP3)


The real time clock was not working after updating the SmartServer image from Release 4.04.119. (2.2)


The Pulse Counter sometimes jumped between two values while polling. (2.2)


The XMPP Server failed to connect when using the hostname instead of IP address. (2.2)


Configuring Openfire without BOSH resulted in a failure to connect with the server. (2.2)


Adding a Real Time Clock or Alarm Generator in the LNS tree with a non-default name results in a “The base name cannot be found” error message, but everything continues to work. (2.2)


XMPP updates sometimes have a long delay after the first update. (2.2)


A memory leak occurred while sending Web connection updates via XMPP. (2.2)


A duplicate XMPP server was not detected. (2.2)


An error occurred on Chinese Windows while trying to insert a Data Point Value by Alias Name or Data Point Preset by Alias Name in the Configure Email Web page. (2.2)


Selecting “Show Message with Identical Program ID only” in the LON Device Identification dialog resulted in all service pin messages being filtered. (2.2)


Adding a new CP to an existing functional block will causeed the SmartServer user interface to hang.  (2.2)


Leading space non printable characters were lost or removed when updating a SNVT_string_ascii Data Point Value of type.  (2.2)

6       Known Problems and Workarounds

This section describes known problems and their workarounds for this release.  Numbers in parentheses at the end of the descriptions are Echelon's internal problem tracking IDs.

6.1    Slow Commissioning for Street Light Networks

When commissioning a street light network, improper configuration can cause excessively long commissioning times due to the large number of devices sharing the available power line bandwidth.

Workaround:  Do not use the default method for adding a device to the SmartServer using the device interface (XIF) file.  In this case, the SmartServer automatically defines a 600 second polling interval for each data point defined by the XIF file.  Thus, as you add devices and commission those, the total network traffic load increases because of this data point polling.  The polling traffic then competes with the traffic associated with device commissioning, so that commissioning each device can take a long time to complete.

Use device templates instead of defining devices with the XIF file.  Create a device template that defines the polling and heartbeat rates for each data point associated with a device type.  See Chapter 4 of the SmartServer User’s Guide for more information about creating and using device templates.

To add devices to the SmartServer using a device template rather than a XIF file:

  1. Add and commission a single device of each type (luminaire and Street Light Bridge module) using the device’s XIF file. 
  2. Create a device template for each device type that you added in step 1.  Ensure that you have exactly one device template for each device type.
  3. Edit the device template to set configuration and driver properties for each device to set polling interval and heartbeat values for all data points to 0. 
  4. Use the device template for each device type to add and commission all subsequent devices within the street lighting network. 
  5. Wait for all devices to complete the commissioning process.
  6. Edit the added devices, as needed, to set polling intervals and heartbeat values for appropriate data points.  Typically, you set polling rates for input data points to 0, and only poll output data points at a rate that is compatible with the logging requirements for the output data points. 

    If a luminaire provides a complex data type that collects information about the current operating state of the device, polling the feedback data point might prove redundant, and should therefore have a polling rate of 0.  In some cases, data points are used for real time monitoring, and are only polled when the device is brought into focus by a system management tool. 

You can also add functionality to your streetlight management system that sets polling and heartbeat rates after the device commissioning process is complete.  When the system is ready for operation, the streetlight management system can set the polling and heartbeats to values that are appropriate for the available channel bandwidth.

(57520, 57708)

6.2    Incorrect Offline Reports for Street Light Networks

When monitoring a street light network with active multi-hop repeating, online devices may be reported as offline due to delayed responses caused by the repeating chains.  Workaround: If you see unexpected offline reports in street light networks, increase the offline delay for LonWorks devices to accommodate the delayed responses.  To set the offline delay for devices, right-click the LonWorks channel in the SmartServer navigation pane and then click Properties on the shortcut menu. (58275)

6.3    6-Byte Authentication Keys Fail with the CRD 3000

A 6-byte authentication key will fail when used with the Echelon CRD 3000 Power Line/RF Bridge.  Workaround: Always specify a 12-byte authentication key for networks that use the CRD 3000.  (57993)

6.4    Intermediate SSL Certificates not Supported

You cannot use an intermediate SSL certificate to secure your SmartServer via HTTPS/SSL.  Workaround:  Create a self‑signed SSL certificate or obtain a direct‑signed SSL certificate.  (54561) 

6.5    Commissioning Devices with Changeable-Type NVs

You cannot commission a device in the LNS tree that has a bound output network variable with a changeable type that was changed with the SCPTnvType configuration property.  Workaround:  Commission the device with the LonMaker tool or other LNS application.  (54584) 

6.6    Persistent Synchronization Error Message

The “Cannot synchronize with LNS" error massage is displayed in the Web interface approximately 20 minutes after the condition has been resolved.  Workaround:  Manually clear the system log to delete the error message.  (54772) 

6.7    Misleading Alarm Notifier Error Message

If you open the Alarm History or Alarm Summary Web pages before configuring an Alarm Notifier, a “No application response for '#8000010128000000[4].UFPTalarmNotifier" error message is displayed in the Web interface.  Workaround:  Configure an Alarm Notifier, and then re-open these Web pages.  (57045) 

6.8    Analog Functional Block (AFB) Reset Error

The AFB output is not updated after the poll on reset delay interval is over if any of the input data points get an update during the interval.  Workaround: Specify a poll on reset delay of 0 for the AFB. (54503)

6.9    Disabled Security Web Page Cannot Be Enabled

Once you disable the SmartServer Security Web page, you cannot re-enable it.  Workaround: Use the console interface to change security settings after you disable the Security Web page. (54668)

6.10Cellular Carrier Network Incompatibility

Some cellular carriers such as Deutsche Telekom are converting their networks to use IP interfaces to carry Circuit Switch Data (CSD).  The IP interfaces have longer latencies than previous CSD interfaces, and as a result up to 8 seconds of latency can be added during modem initialization.  This increased time can result in modem initialization failures.  Workaround: Select a modem that is compatible with your carrier’s network. (63533)

6.11Releasing Neuron ID Strands Devices

If you add a device to the network in Standalone network management mode and attempt to commission the device with the wrong Neuron ID, the operation will fail as expected.  If you then use the Release Neuron ID' command, and use the correct Neuron ID, the Web UI will create a new device instance in the SmartServer, leaving the first attempted device in the list of devices.  These orphans may persist across resets.  On a SmartServer defined interval the SmartServer will continue to attempt commissioning these devices.  Workaround:  Use the Replace command.  (69187) 

6.12Using a Double Quote (“) Character in a Unit String

If you use a single double quote in the units field of a resource file format, the double quote will be treated as a special symbol and will not be displayed within the formatted text.  Workaround: To use the double quote (") character in a unit string, you must escape it with another double quote.  For example, to use a single double quote character to represent inches, enter two double quotes ("").  If you do not escape the double quote, the Data Logger: View Web page may not display the data point value. (67450) 

6.13Using a Duplicate IP Address Range for Different Interfaces

Communications may fail if you assign a duplicate address for the Ethernet IP address and the PPP IP, or if you assign addresses within the same subnet address range.  Workaround:  Assign local IP addresses outside the range of the SmartServer's Ethernet IP connection.  For example, do not use to for a local IP address if you are using the SmartServer's default IPv4 address (  (61637) 

6.14Misconfigured Heartbeats on Local NVs

If you misconfigure heartbeats for a dynamic output NV on the SmartServer, updates to the output may not occur when you expect them.  Workaround: Use the following guidelines for adding a dynamic output NV to a functional block in the SmartServer:

1.     After adding the functional block and a dynamic output NV with a heartbeat time defined, commission and set the iLON app online.  Heartbeats will not work if the iLON application is not commissioned and online. 

2.     The default SmartServer behavior for creating a dynamic NV is to create an Input NV.  If you are creating an output NV, you must select the Output NV option before you click Submit.

3.     Before you create a connection, select the type of connection.  If you do not specify the connection type, the SmartServer will select the connection type automatically.  The automatic selection may not be correct for your use case.  The connection type that works for most uses cases is Repeated LON Connection.

4.     Initialize the Output NV with a valid value to kick off the heartbeats. (69067) 

6.15Long Exception Names

Configuring an Event Scheduler with an exception name longer than 25 bytes on a SmartServer release prior to 2.2 may generate many unknown exceptions that appear in the event log.  In SmartServer 2.2, if you configure an Event Scheduler with an exception name longer than 25 bytes the Event Scheduler (not the Web UI) will only take the first 25 bytes and terminate the name with a null character at the 26th byte.  Workaround: Verify that the first 25 bytes of any exception names are unique. (68993, 69294)

6.16Internal Turnaround LON Connection Failure in PL Repeating Mode

Configuring an internal turnaround LON connection such as a connection from a scheduler to an alarm generator in PL repeating mode does not work.  Workaround: Always use SmartServer Web connections for connections between internal SmartServer functional blocks. (69353)

6.17LON Connection Failure with Uncommissioned iLON App

If you attempt to create a LON connection to an external device when the iLON App is not yet commissioned will silently fail.  Workaround: Always commission the iLON App before making any LON connections. (69411)

6.18i.LON 100 Plug-in Launch Failure  

When you attempt to open the i.LON 100 configuration plug-in, the following message may be displayed: "Unable to communicate with the iLON 100.  Please verify the IP address and network connection.  Application:  Dataserver NVL List."  Workaround:  Install the Microsoft MSXML4 SP3 plug-in as described in the following procedure: (69286) 



Echelon, LON, LonWorks, i.LON, LNS, and LonMaker are registered trademarks of Echelon Corporation in the U.S. and other countries.