Migrating From SmartServer 2.2 to SmartServer IoT FAQ (KB1365)

Frequently Asked Questions:

1. The SmartServer 2.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.2?
   1. No, the SmartServer IoT has no built-in I/O, but you can connect one or more IOX devices (sold separately) that has DI, DO, relay control and RS-485. One version of the IOX has metering.
3. Does the SmartServer IoT have a RS-232 or RS-485 like SmartServer 2.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.2 image on a SmartServer IoT?
   • No, the SmartServer 2.2 and SmartServer IoT are different products so you can't copy the SmartServer 2.2 image files to the SmartServer IoT.
   • The SmartServer 2.2 is based on VxWorks and the SmartServer IoT is based on Linux.
   • SmartServer 2.2 Custom Web pages or custom application will not run on the SmartServer IoT.
     • The SmartServer 2.2 and SmartServer IoT use different APIs.
     • The SmartServer 2.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.2 will not work on SmartServer IoT.
   • You will need to create a new SmartServer IoT image.
5. 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.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.2 i.LON FTT device is connected to a FT-10 channel, and i.LON PLN is connected to powerline.
6. Can I create a golden image for the SmartServer IoT like I do for the SmartServer 2.2?
   • The SmartServer IoT doesn't have a mechanism to create a golden image as the SmartServer IoT MAC IDs are stored in the SmartServer IoT Backups and you are not allowed to have two devices on the internet using the same MAC IDs.
   • Once you created your SmartServer IoT image, you can then export all the features you want and then import them into one or more new SmartServers.  
     • Device Templates
     • XIF and Resource File set
     • DLA, and DTP files
     • Device Import File
     • Connection file (DMM mode only) - connection files can't be exported
   • 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.
7. Does the SmartServer IoT use EES to do database synchronization synchronization?
   • SmartServer IoT uses a different synchronization process than SmartServer 2.2.
   • SmartServer 2.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.