oberkc

Open Alexa app. On the lower left are some options that include one that is short parallel lines (settings, I assume). From there is the "skills" option. Scroll down to "my skills". Scroll until you see the universal devices skill, which should show you the version.

This is a good point. My experience with the transition from the ISYwas not exactly trouble-free, and much of the struggle was with Z-wave side of things. You describe your z-wave devices as "a few". If "few" means not to many, it may be easier and even beneficial to simply remove them from the ISY network, factory reset the z-wave devices, and add them back.

Not mentioned is the reliance of the hub on the internet and cloud services. Such devices run the risk of becoming a door stop should the cloud service cease to operate. I have always considered local operation to be a major selling point of the ISY series of controllers.

Has anyone noticed a "matter" option on the new hub? I don't believe it yet works, but suspect this is a sign of things to come.

@Panda88: I have yet to install the new Yolink hub. I have had some other issues (such as moving over to the EISY from Polisy) to work out first, but I would be fully understanding of a second Yolink plugin specifically for the local hub, keeping the original version for the original hub. The only downside I could see for you was maintaining two versions.

update...I never did get Polisy to add some matter thread devices (specifically, the nano leaf bulb). I was able to add a govee matter device and a GECync matter device, but I think they were matter-over-wifi. I migrated to the EISY recently, and the matter-over-thread now seems to work. I am now able to add the nano leaf bulbs.

Are you able to access the dashboard for polyglot? Assuming so, can you find the plugins store? Assuming so, can you find the plugin for Govee? Once found, do you see how to install the plugin? Also, in the store listing for each plugin I would expect a "more info" option. From there you will often find some very basic instructions relevant to each plugin. For Govee, it takes you here: https://github.com/UniversalDevicesInc-PG3/udi-govee-nodeserver/blob/main/README.md Once installed and set up, mine found the three Govee devices that I have and once found, the IoX showed the Govee devices as nodes, which can be used like the Insteon or zwave nodes in programs and scenes (with some limitations). Hopefully, along with the response from @dbuss, this will get you started.

I have had some luck adding zwave devices when close to the ISY, then moving to the final location. Many of my zwave devices have additional nodes for which I have no known use. I think some can be used to build zwave scenes, but have never had much luck with this. I suggest ignoring them if you can otherwise make your device function as desired.

This is how I do it. despite the warnings, I actually like the mutually exclusive option with keypad buttons. One has to recognize, however, the limitations. It only works if you manually press the affected buttons physically. The relationship is not enforced when you change the state of those buttons via the ISY.

I am not near my system, but recall the mutually exclusive feature to be found from the admin console, selecting the keypad and, along the bottom of the main window, you should find an “option” button (or similar) where ome can configure which butons are part of the mutual exclusive relationship.

One could use the mutually exclusive option built into every keypadlinc but this works only when manually pressing the respective button. It does not work if the buttons are controlled via program or scene or direct commands from the ISY. A scene might be more effective, where one would set up one button as a sea controller, and the other button as a scene responder, having an ON level of zero, or off. EVEN THIS METHOD MIGHT HAVE USED CASES WHERE ONE OF THE BUTTONS IS TURNED ON INDIRECTLY, where the SCENE RELATIONSHIP WOULD NOT BE ENFORCED. A third option would be using a program or programs such as if One button is on Then Turn the other button off A program such as this might be effective in the most number of situations. The approach you take would depend on how you expect to use each of the two keypad buttons.

Thank you all for the references. I have forgotten, or did not realize, that there was a difference between having a portal account and having an active subscription. Ultimately, I feel extremely comitted to the “ISY” system and it is quite imbedded into my house. Though I have every reason and hope in the continued viability of universal devices, I very much want to avoid having to suddenly remove this system should any external resource such as portal accounts (active or otherwise) become disabled or eliminated for any reason, rendering my sytem inoperative.

Thanks for the pointers. That gives me some relief. I am still stuck with the perception that a portal account is required, however. If one does not have a portal account, does the system not work? If one has a portal account but later chooses to cancel it, does the system quit working?

I have been watching, with interest, the discussion on the newest software and UI. I understand that one must use the portal account credentials to login. Is this suggesting that a portal account is now required to use an EISY? Does this suggest that the newest version of iox requires an Internet connection to work ? Am I correct in my understanding that the old Java interface is still available and, if so, is that the only way to access the EISY locally?

I am in the same situation. I assume I must order the EISY and zwave eclosure (planning to move my old zwave board to the new EISY. I did not see the “migrate to zmatter” option. (I guess the reason is that I am not using the zooz dongle, but it makes me concerned that the instructions are not updated or complete.). I must admit that similar transitions in the past did not go smoothly for me and my ambition for future upgrades is waning. Are there any other particular tricks or pitfalls that I should be watching out for?