DennisC

UD is aware of both these issue. The subscription issue will be fixed in the next release. I'm not sure if they have identified the upgrade packages issue, but appears that after several reboots it goes away, or at least doesn't appear as frequently. This last upgrade requires a second reboot after the update packages completes due to the files that are being updated.

No, you can not pick and choose during the migration, you either migrate or start over. Having said that & first, let me say I have not tested this but: According to the wiki migration instructions: "If you don't actually change your Z-Wave network by adding/removing Z-Wave devices after migration, you can back out the migration by connecting whatever Z-Wave dongle you were using before migration and restoring the backup you made prior to migration." When you migrate, none of the devices, programs, network resources, or variables are actual removed from your existing system. Theoretically, if you used a new PLM for Insteon and you had a different dongle for ZWave, you could just delete the devices in eisy after migrating and continue to use your existing system. However, you will have a lot of errors all over the system. I see at least several potential issues for doing this. 1. Part of the migration process is migrating your portal & node server license, & the node servers. From the wiki: Migrating Node Servers to PG3x Migration is only possible with version 3.1.17 or later of PG3x. The version of PG3x that ships with eisy is currently 3.1.16 which does not support migration. Please upgrade packages first and make sure you are running version 3.1.17 of PG3x before attempting to migrate. Backup PG3 on Polisy. Restore from PG3 backup on eisy using the "Migrate from PG3 Backup" option. Cautions: Node servers currently installed on eisy will be removed (and possibly replaced). Node servers migrated are left in the "stopped" state. You will need to manually start each one after migration. If the Polisy was configured to manage node servers on more than one IoX (say both Polisy IoP and i994) only one IoX will be migrated and you can't choose which one it will migrate. Node servers installed on the Polisy from the local node server store will likely fail to install on the eisy. Node server licenses should be migrated as part of the Portal migration step. I guess you could skip this step. 2. Once you delete Insteon devices from eisy, you will have communication errors unless you factory reset the PLM that stays on eisy. For ZWave it may or may not be an issue. In any event, you should not have two programs on two different systems controlling your devices, you probably should disable one set of programs. 3. When you are ready to make the final change over to eisy, you will have a lot of manual manipulation to complete and you might risk a strong possibility of a conflict or corruption of something(s). 4. Did I say you would have a lot of errors........... 5. You would be in uncharted territory here, and anything might happen. As for my opinion, this is not a path forward that I would want to undertake. If your system is that large, why put yourself through that much extra work? A safer cause of action would be to hold off from migrating a while longer until things settle down some more and managing Zwave device settles down a bit more.

UD Mobile was not designed to work with the EOL Elk Module. UD Mobile fully supports the Elk Node server and both developer's have worked together before to correct any issues. In UD Mobile using the Elk Node server, outputs appear as any other node.

As stated in my previous reply, the current crop of node servers run on a Polisy or eisy. The cloud based node server offering was shutdown due to security concerns. Depending on the specific node server, some cloud participation may be required for specific manufactures but Elk is not one of them.

Yes, I and many others are currently using this node server. I have been using it for over two years. Its functionality is at the least on par with the now end of live Elk Module and in some ways much better. The support from the developer is top notch. I am unaware of any of the approximately 100 current node servers developed mainly by individual developers with support from UD called "faux node server", but maybe it exists somewhere. The current list of Polyglot v3 node servers that can run on Polisy or eisy is here: https://polyglot.universal-devices.com/ If you follow that link and click on the name Elk, and then click through the next page, you will see information about the node server and its functionality. If you click the link at the top of the Elk node server github readme file called Issues, you will find current open issues the developer is tracking. You mention "ISY" in your last post. If you are referring to an ISY994, I use to, but I moved on to a Polisy and now an eisy. The current version of the node servers in the link to the list I posted will not run on a ISY994. These node servers require either a Polisy or eisy. The ISY994 is now end of life. Previously, with Polyglot v2, node servers could be run on a raspberry pi, however, while Polyglot v2 might still be available (?), it is also end of life and there will be o future development.

Prior to upgrading to v5.5.7, I had to manually query them to get them to populate since on eisy after a reboot of eisy. After upgrading to v5.5.7, yes, all nodes populated on their own, but it took about 7 minutes. Thanks for the explanation, I understand.

I suggest updating your support ticket to capture your testing. Sorry it didn't work.

Based on @Steve L comment, try triggering motion and immediately wright changes to device.

It's good that you were able to add it. Make sure the device is awake (if battery powered), right click on it and select write updates. If that doesn't work, I would suggest opening a support ticket so UD is aware of the problem. Reporting it is the only way to make sure it gets fixed. Open UD Support Ticket

Glad you got it working.

I don't think it will resolve itself without intervention. The only further suggestion I have is to power down eisy and after it shuts down, remove the plug for a few minutes and then power it back up. If that doesn't work, then flag @bpwwer to look at you posts (3 & 6 post up) and see what he thinks. He maintains pg3x and offers assistance freely.

Not sure I understand your question. I use the Elk Node Server and I can assure you it is genuine and not fake.

Hmmm, used for years has me wondering if the 2 year period for your account license expired. You might want to sign directly in to UD portal via a web browser and check your expiration date license on the eisy in question. If you migrated the account from another device, it might not of had a lot of time left. If you used a trial license it might have ended.

Are you running any node servers and are they populating in the admin console? Is this a new portal account or have you been using it on the same machine for awhile?

Glad you got it to work.

Interesting, did you excluded both before trying to add them?

I think responded to your other post. Try rebooting one more time. After shutdown pull the plug for a bit and then power up. Wait 10 - 15 minutes before trying to login. Also confirm you are being asked to login to the portal and you are using the correct credentials for both logins. PG3x uses the admin console login, which might not be the same as the portal login.

One node server or PG3? If PG3, try power cycling the system one more time. After shutdown pull the plug for a minute.

I would suggest opening a ticket with UD spelling out exactly what you did. Not sure I understand the "reinstall of PG3" and the reason for doing so.

I'm getting it also, sometimes frequently. I had reported this to UD on v5.5.6 and now it is happening on v5.5.7. I owe UD a report on .y testing of a bunch of issues on 5.5.7, so I will pass this on to them.

Glad you got it working.

The login should be the same as you use for eisy, have you not changed user from the default (something you should do)? However, you should have received a portal login before you could enter login for PG3x, did you login in to the portal? If you didn't receive that login page, I would suggest you reboot eisy.

Not sure, maybe try it both ways. I looked at the Sun node server looking for instructions, but the link doesn't work. I copied this from TimeData: Configuration Enter latitude in the form 12.3456, negative is south Enter longitude in the form 123.4567, negative is west

I believe he is speaking about 10 concurrent subscriptions, not number of node servers.

I rebooted a few times and all of the node servers loaded. They take a little time, about 7 minutes, but they all loaded with a query.