lindnergt Posted April 3, 2023 Posted April 3, 2023 Still trying to migrate from isy to eisy. Both devices connected to network and accessible by both Admin Console and UD mobile. eisy populated. eisy connected to PLM via USB-serial adapter. Nothing responds to attempts to turn lights (INSTEON) off or on. Reconnected to PLM to isy - works fine. Did I miss something?
MrBill Posted April 3, 2023 Posted April 3, 2023 when PLM is connected to eisy, rebooting eisy is required. Also Insteon support must be enabled (before the reboot) in the admin console Configuration tab. If all that's been followed what happens when you select Tools > Diagnostics > PLM Info / Status in the eisy admin console?
DennisC Posted April 3, 2023 Posted April 3, 2023 In addition to @MrBillcomments, which USB-serial adapter did you use (the one by UD) or? At least one other poster received a deflective USB-serial cable recently. Did you follow the migration guide? https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration
lindnergt Posted April 8, 2023 Author Posted April 8, 2023 MrBill, Thanks for your post. I have tried the steps you suggested without any progress. PLM Status returns 0.0.0 v0 / Not connected. DennisC, Thanks for your post. Yes, I did (attempt) to follow the (very confusing) migration guide (several times). I have a PLM 2413S. I bought the USB-serial adapter directly from Amazon and wired it according to the US doc. Still no joy. My ISY was bullet-proof and worked great for years. Eisy is so far a big disappointment and needs better documentation that does not mix up with the ISY documentation. The UD mobile app is also a disappointment. Did UD have their documentation and migration guide tested by anyone outside of their shop of not well acquainted with all their systems? I've been coding since 1973 (FORTRAN IV) but rarely have had to struggle with anything as much as I have with this eisy migration. Thanks for your help. Any more ideas? Gary
MrBill Posted April 8, 2023 Posted April 8, 2023 2 minutes ago, lindnergt said: PLM Status returns 0.0.0 v0 / Not connected. This is the problem. Make certain that you have the PLM online for 30 seconds or so before booting eisy.. It needs to detect that the port exists. 4 minutes ago, lindnergt said: I bought the USB-serial adapter directly from Amazon and wired it according to the US doc. ...or the cable or it's built in converter is bad... or it's "wired" wrong and not communicating because of that. 1
DennisC Posted April 8, 2023 Posted April 8, 2023 16 minutes ago, MrBill said: ...or the cable or it's built in converter is bad... or it's "wired" wrong and not communicating because of that. That's my guess..... 1
keepersg Posted April 8, 2023 Posted April 8, 2023 If none of that works, open a ticket. I had this problem with my eisy and could not solve it despite proving the PLM and cable were good. It was some software problem with my eisy that was beyond my knowledge. UDI remoted in and spent quite a bit of time diagnosing and fixing it. Great support.
lindnergt Posted April 22, 2023 Author Posted April 22, 2023 Bought a new USB PLM. Got it working. Thanks for your help. New Problem migrating Alexa. Utility says ISY "address of new eisy" already has a license. I guess I did a step easlier in my many migration attempts. I'm not sure what license it is referencing. Is there something to clear or delete from the new eisy before trying to Migrate to the new?
DennisC Posted April 22, 2023 Posted April 22, 2023 4 minutes ago, lindnergt said: New Problem migrating Alexa. Utility says ISY "address of new eisy" already has a license. I guess I did a step easlier in my many migration attempts. I'm not sure what license it is referencing. Is there something to clear or delete from the new eisy before trying to Migrate to the new? The directions you should be following to migrate Alexa are here: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Migrate_configurations_to_a_new_ISY First, make sure you are following them exactly. On which step are you running in to issues? 1
lindnergt Posted April 24, 2023 Author Posted April 24, 2023 Thanks for the reply Dennis. I had been following those directions. Upon review I noticed further down that the license can only be migrated to an unlicensed system. Since I did an incomplete migration during an earlier try, the documentation seems to indicate there is no way to redo or complete the migration. I guess I will have to recreate all my Echo Spokens.
DennisC Posted April 25, 2023 Posted April 25, 2023 (edited) 1 hour ago, lindnergt said: Thanks for the reply Dennis. I had been following those directions. Upon review I noticed further down that the license can only be migrated to an unlicensed system. Since I did an incomplete migration during an earlier try, the documentation seems to indicate there is no way to redo or complete the migration. I guess I will have to recreate all my Echo Spokens. Just wondering if you did this step originated, "To use your spokens on the new ISY, your preferred ISY may need to be updated with the new ISY uuid. If you selected "Updated preferred ISY" during the migration, it will be updated for you." If not, you might have to do that manually. Since the instructions indicate you can reverse the migration of the spokens, you should be able to migrate them if it wasn't completed. To me, it appears only migration of the license for the portal can't be undone. Also, make sure you have approved your new unit in the admin console: Configuration | Portals | +Approve Edited April 25, 2023 by DennisC Correct Spelling 2
Recommended Posts