Geddy

IoX = ISY on Anything (as announced/documented by UDI) It is specifically meant for ISY running on Polisy and eisy as of now. It's not deemed backwards compatible with ISY994 so that remains simply "ISY", but specifically for ISY994 devices. Remember that ISY is a service, ISY994 is the device running the ISY service. Polisy and eisy are devices running the ISY and Polyglot services. Each of those services have different version values. IoX appears to be able to stay at the same version for Polisy and eisy. At least to this point. People with Polisy and eisy have all been able to update to 5.5.5. In the initial release of the eisy both PG3x and PG3 had identical PG3 version numbers. PG3x (eisy) has since been updated to 3.1.22 while PG3 (Polisy) remains at 3.1.17. Yes, it gets confusing, but not really that much as all the "Current Release" posts are in the Current Release area of the forums. So it's easy to see what's "current". (That's by design!) I think I'm going to lock this thread now because it's kind of drifted off course. I think @johnnyt got the answer to the original question.

PG3/PG3x is different than IoX versions. PG3 refers to the Polyglot version running the node servers. Polisy is PG3 and (I think) is currently 3.1.17 eisy is PG3x and currently 3.1.22

@johnnyt Since you're not using IoX then updating is fine. At this point updating the Polisy or eisy (I know you don't have the eisy, just referencing it for clarification) is done by using the "Upgrade Packages" button in IoX Admin Console for the device you're using (Note...IoX is ONLY for Polisy and eisy). The main thing you need to consider is what version of PG3 are you using? If it's current then you're good in that department. If it's not then that would upgrade as well. I think we've all learned what not keeping a system updated means at this point. It's a little more time sensitive sometimes for the Polisy (and now eisy) to get those updates when you can. While it won't really impact your situation it would mean that your system would be operating with the current releases of ioX and PG3. If something changed dramatically in a future update and the upgrade path from an outdated system to a current release system broke then might require a lot of additional work and support. no benefits to your current setup since you're using ISY994 as controller. No, it's a free firmware update to IoX. I believe those were more related to PG3x (eisy) and 5.5.5 in how PG3x handles node servers differently on the eisy than the current version on Polisy. But that's only from memory of reading too many posts. Make sure you review those posts to see if you can tell if they were eisy related or Polisy if you're overly concerned.

@Methos000 Your PG3 version and frontend version are out of sync. You'll need the help from support to get things brought up to current versions for the Polisy.

@TimWing I'm not sure if it caused this, but your screenshot in your first post seemed to have "Automatically Write Changes to Devices" turned off as well. You only need the write to battery option turned off when you restore the PLM. Part of the process is to write the updated PLM information to the other devices. Wiki steps - https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu See "Restore PLM" on that page. I would suggest turning "Automatically Write Changes to Devices" back on, but leave the battery off and try Restore PLM again. I think trying to restore the device failed because it's (probably) looking for the PLM at the old link/address because the Restore PLM process didn't send the command out to the devices to update the new PLM address/links. Did you have a backup from before you started this? (probably not needed, but just checking if you had a recent backup in case you need to restore it and try again.)

Try the setup found in the wiki: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#ISYs What PG3 version are you running? I think Polisy is still on 3.1.17. Make sure you add your ISY admin user and password. Otherwise, what's "all sorts of messed up"?

https://forum.universal-devices.com/forum/113-nodelink/ A 3rd party development by @io_guy.

There was a comment from @bpwwer in another thread (not looking for it at the moment), but apparently there's an issue with 5.5.5 and PG3x that impacts users with multiple node servers running. Perhaps that's your issue and sometimes one will randomly run correctly but others wont. I'd leave things alone and stop removing/reinstalling until more updates are released. You're just creating useless work for yourself.

@K-bert also make sure you pay attention to the part about battery devices! "If you have PRO Series, click on the Battery icon at the top. This will prevent ISY from trying to update programming on your RF devices which are probably in sleep mode" IoX (on Polisy and eisy) are all "pro" versions. So if you have battery devices be sure to follow this step.

@Bobby g The best way to get this answer is to open a support ticket with UDI to get required information. https://www.universal-devices.com/my-tickets

Specifically check the setting under "My Profile" when you're logged into ISY Portal. That should have preferred ISY set at the eisy UUID. If you left the default settings in the step @MrBill links you to then you shouldn't have to do this. But if you've tried doing something manually it might be a missed step and might still be pointing to the old ISY994.

@firstone Do you happen to have a (recent) backup from the Polisy before you migrated on that device? I mention recent because the IoX would probably need to be somewhat close to what you have in the eisy. Then restore that Polisy backup on the eisy. Just a thought. Rather than having to factory reset the eisy. But, if the eisy was never used what's the harm in factory reset?

@RocKKer unsure (I do not use). But here is the additional details you can review: https://github.com/UniversalDevicesInc-PG3/udi-poly-airscape/blob/master/README.md Also, looks like the node server does offer 1 month trial so you could install to see if it works and if so how it works for you before you buy.

@TRI0N replied to your post of this same issue in the IoX support thread, but glad you started one here. I haven't had the same problem so can't help. I wasn't able to control the hue devices after initial update, but just had to restart the node server and it then allowed control through admin console and UD Mobile just fine. Since you're reinstalling are you sure that you're finding the bridge properly? Make sure you press the button on the bridge then restart the node server. When you install it is it stay "disconnected" in current status? Click on the log then change to "debug" and then "start" do any errors show up in the log on the screen? I'm not sure how much @xKing is around, but maybe you can send a log package to him to see if there's something fishy on your install that's not allowing it to connect. Others on the support thread they haven't had this issue so it's user specific currently.

@Davey A couple of things to check first: What's the firmware for IoX? Have you updated it before you tried to migrate into eisy? Current release is 5.5.5. There were some issues with earlier IoX versions that caused migration issues, but they've been fairly good as of late. If you just received the eisy and didn't update it prior to migration you might be having such issues. You said you moved the eisy and plugged in the network cable...had you initially set it up on wifi and then changed it to hard wire when you moved it to where the old ISY994 was? That shouldn't matter, but again, if it was older IoX it could be an issue. Make sure that your firmware and UI match (help -> about) - They should as long as you're using IoX Launcher (start.jnlp), but always need to make sure. Do you have a lot of battery devices that you tried to migrate? (I don't so can't help you there, but think that's been slowing some down as well) I think there's a way to turn off writing to battery devices and it might stop the update process from happening next time. Though you do need to make sure all battery devices are migrated properly.

Make sure you refresh the page. Maybe even hard refresh depending on your browser (Chrome (and edge) is CTRL + F5). Somebody earlier reported the issue and after removing a node server that wasn't in use something triggered it to match. But I just ran the update (no issues other than restarting Hue node server) and refreshed the page and showed 5.5.5 just fine.

New email out from Ken @ Insteon with some neat aspects. Hopefully most here have signed up for such news letters. If you haven't at the end of every page at https://www.insteon.com is a form to "Sign up for the latest and greatest news from Insteon." There are two surveys in this that appear tied to recipient's email so won't be posting those links, but the other good thing is a link to "FEEDBACK to Insteon". Many here have been hoping for specific devices or other information from them (ie allowing UD access to new Insteon details so hopefully it will be supported in future IoX updates). Here is that feedback link: https://www.insteon.com/general-feedback Rest of the update: ----------------------- Hi everyone, I am happy to share that our new i3 Dial and Outlet are now shipping. The response to these two new products has been amazing and we cannot wait to hear what you think about them. We also will be having our next ‘Lunch with Insteon’ webinar scheduled for 2/17, registration details to be sent closer to the event. In this webinar, Richard (my co-founder) will be giving a demo of the new features in the latest version of our Director app. Speaking of which, one quick note about the version of Director released last week – you are now able to see if a sensor has not communicated with the Hub for a few days. The tile for this sensor in the app will appear yellow. This likely means a dead battery that needs to be changed. However, if a new battery does not resolve the issue, it may be a communication issue. You can read more about this feature and learn some troubleshooting tips here. Regarding future updates to Director, we had discussed exposing unsupported devices and displaying some basic information that you might find useful. For example, you may not be able to control an unsupported device, but you would be able to see information such as: whether the device is communicating with your Hub, its Insteon ID, its communication types (powerline and/or wireless), etc. We would like your input on what these should be listed as. We have kicked around a few and want to know your thoughts. While we’re on the subject of feedback, we also want to know your “wish list” of what we should be bringing back into stock. Please note, your responses do not guarantee we will resume the manufacturing of those devices, but we would really like to see the demand for these products. I know a few people have reached out saying “You keep asking for feedback, how do I give it to you?” Moving forward, all of my updates will include a link to a feedback form under my signature. Please tell us what we are doing right. And, more importantly, what we can do better. Richard and I are committed to reading each submission. Thank you in advance for doing those two surveys* and for any feedback you would like to share, Ken CEO, Insteon Technologies Feedback Form Link: https://www.insteon.com/general-feedback * Note, we will close the surveys in a week so we can begin looking at the results. ---------------

@rahnee looks like IoX 5.5.5 is good to go now.

I 100% agree. Thankfully I do not rely on node servers so haven't worried about such issues. They really seem great for people that need them and rely on them. My system isn't that complicated and not spread between multiple ecosystems that would require node servers to monitor/control everything through ISY. I think most (as with PG2) have always just taken the leap of faith a little more blindly and trusted that there would be support for the systems they're using. To me, I've always looked at node servers as something somebody made to support their system. They then offered it to others at large through PGC/PG2. With the development of PG3/PG3x UDI gave those developers a way to get paid for their development and (ongoing) support. Some have probably been more diligent with their development and support than others. But at the end of the day I see this more as an individual offering rather than company offerings and at that level feel that ongoing usability and support should be hopeful at best. Case in point that @bpwwer mentions at least one has recently decided to abandon development and turn their offerings over to others. Sadly, people that had purchased those node servers might now have to wait for them to be usable again. I highly doubt that many individual developers have a true license that is in place. I would assume it's under an blanket license agreement with UDI as a part of the developer level process. You bring up a lot of great and valid points for your situation and concerns. Others just take the leap of faith and keep on trucking.

Do you mean trial before you buy? Or something specific to the license? @palayman many node servers do offer a trial period. This gives you the ability to install and make sure they work before you commit. That information is usually seen in the details of each node server. Elk (for example) shows this: So you can try it for a month then pay $30 to have ongoing access to it.

What kind of "disaster waiting to happen" are you envisioning? My eisy+ZMatter sits in a cabinet and doesn't get moved/touched/adjusted. So it's a set it and forget it device. Minimal disaster ability to inflict issues with it (for my install). Do you have an issue with other USB devices randomly falling out of the port they're inserted in? If so, something else is wrong. I've never had a USB device disconnect without exerting some force to remove it from the host device. I'd say this is the same for eisy + ZMatter dongle. I haven't measured it, but there are 4 total USB ports available. ZMatter takes one and PLM takes another. My ZMatter sits off the rear USB port and the PLM is in one of the 3 on the side. I'm not sure how many USB devices you plan to plug into the eisy, but there are still 2 perfectly usable ports available. And if you're worried about the ZMatter taking up space there are USB extension cables to remove the dongle from the eisy unit itself. Personally, I feel the eisy is a nice little update from the Polisy. It's a much smaller footprint and only the ZMatter antenna add to the height. It's only slightly larger than the ISY994, but has a ton of new capacity. Sure, it's not as big or bulky (or shiny) as the Polisy, but it's just as good (if not better depending on what can be run in parallel down the road).

@Illusion Have you attempted to contact Insteon to see if their support has any tips/tricks not mentioned here or thought of? https://www.insteon.com/support I guess it could be that they're just old and have failed, but only partially.

@wacvmd No.

@Steve L glad you found it. Wasn't really sure what you were asking since you kind of floated all over the subject of what you really needed to know. For each node server you install there should be a "Details" button for the node server. From there you can see the configuration area for most node servers. Generally it's a good rule of thumb not to have Admin Console open while you're adding/adjusting node servers. Typically one of the steps is to restart Admin Console so it will load any new nodes being sent to the ISY. It seems that you might have installed the node servers while admin console was open and your reboot allowed the nodes to push to admin console correctly. And the general wiki is about all you'd need for Polyglot. Make sure you review the entire eisy user guide in the wiki: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide

Since you don't have the "Update Packages" button and you say you're on 5.4.0 your Polisy is out of date. The easiest path is to open a support ticket to get assistance with bringing the system up to date. Please open a ticket here: https://www.universal-devices.com/my-tickets