Migrating From SmartServer 2 To SmartServer IoT FAQ (KB1365)

    The SmartServer IoT is the replacement for the i.LON SmartServer2.


    This document provides some basic information on how to transistion to the new SmartSErver IoT.

    See the SmartServer IoT FAQ for what the SmartServer IoT can do.

    https://enoceanwiki.atlassian.net/wiki/spaces/IEC/pages/5275861/Frequently+Asked+Questions


    Migrating SmartServer 2 to SmartServer IoT Frequently Asked Questions:

    1. The SmartServer 2 has a built-in FT or powerline channel, what about the SmartServer IoT?
      • The SmartServer IoT doesn't have a builtin FT-10, XF-1250 or Power line channel, you need to separately purchase a U60 or U70 for the SmartServer IoT to directly connect to one of these channels
    2. Does the SmartServer IoT have built-in DI, DO and pulse input like SmartServer 2? ?
      • No, the SmartServer IoT has no built-in I/O. See the SmartServer IoT FAQ for example metering and I/O

    3. Does the SmartServer IoT have a RS-232 or RS-485 like SmartServer 2?
      1. Only the SmartServer IoT PRO WiFi has two RS-485 ports, but no RS-232 ports. The non-WiFi SmartServer IoT doesn't come with any RS-485 ports. 
      2. The IOX has RS-485 and RS-232 support (sold separately).
    4. Can I use my SmartServer 2 image on a SmartServer IoT?
      • No, the SmartServer 2 and SmartServer IoT are different products so you can't copy the SmartServer 2 image files to the SmartServer IoT.
      • The SmartServer 2 is based on VxWorks and the SmartServer IoT is based on Linux.
      • SmartServer 2 Custom Web pages or custom application will not run on the SmartServer IoT.
        • The SmartServer 2 and SmartServer IoT use different APIs.
        • The SmartServer 2 uses SOAP API for custom web pages and custom application.
        • The SmartServer IoT uses REST and MQTT APIs for custom web pages and custom applications.
      • FPMs developed for SmartServer 2 will not work on SmartServer IoT.
      • You will need to create a new SmartServer IoT image.
    5. Does the SmartServer IoT have type translators like the SmartServer 2?
      • The SmartServer IoT has a built-in Node-RED editor that you can make Web and data flows which can be used to do type translation.
    6. Does the SmartServer IoT support FPMs like SmartServer 2 ?
      • The SmartServer IoT allows you to create custom Internal device, Internal apps and Internal drivers but works differently then FPMs.
      • We have a number of examples using node.js
      • To push data to the cloud you can use Internal devices or Node-RED flows (create or download an existing flow).
    7. For LNS networks, do I need to change my LNS database to support the SmartServer IoT?
      • Yes, you will need to add a SmartServer IoT device to a subsystem in order to export device information to the SmartServer IoT.
      • The SmartServer IoT Device is similar to the SmartServer 2 i.LON App except:
        • The SmartServer IoT device is connected to the SmartServer IoT IP-70 channel.
          • Each SmartServer IoT must have its own IP-70 channel.
        • The SmartServer 2 i.LON FTT device is connected to a FT-10 channel, and i.LON PLN is connected to powerline.
    8. Can I create a golden image for the SmartServer IoT like I do for the SmartServer 2?
      • The SmartServer IoT has three ways to back up data .  
        • Export settings using CMS Web page Import/Export button .
          • Some CMS Widgets allow you to export the Widget settings
        • Clone system backup - this how you create a golden image.
          • though you can't use this image on more than one SmartServer on the same site as clones on older software also change the new SmartServer MAC ids.
        • System backup - this is meant to only be restored on the same SmartServer or a replacement SmartServer.
      • When importing files into the SmartServer IoT you need to make sure that you allow the SmartServer IoT enough time to load the file and templates before loading in the next file.
        • You can import in one or more zip files in order to configure the SmartServer IoT
      • After you import some settings you will need to .
        • Node-RED flows may need to have IAP input and IAP output nodes re-assigned after importing them in.

    9. Does the SmartServer IoT use EES to do database synchronization synchronization?
    • SmartServer IoT uses a different synchronization process than SmartServer 2.
    • SmartServer 2 uses EES (LNS Proxy) for sychronziation, SmartServer uses iNex export tool.
    • SmartServer IoT synchronization requires you to put a SmartServer IoT device on the Subsystem.
      • Using the iNex export tool, device information for devices in this subsysem (and their child subsystems) are exported to the SmartSever IoT.
    • There is no automatic synchronization in the SmartServer IoT, you must run the iNex after changes to the LNS database.

    Published