DennisC

Yes, I'm writing on a mobile device and it looks like it has a mind of it's own. Going to edit my post to correct.

I have a Yolink door contact installed in a metal mail box located about 100 feet away and thru a concrete wall from the hub. They advertise up to 1/4 mile with no obstacles. So far it has been working. I intergraded it in to eisy with the node server. The reaction has been almost immediate. So far, it is working with no problems. If I didn't hard wire GDO in to my Elk, I wouldn't hesitate to try Yolink solution for it.

The only reference to wifi for Polisy is in this section or the instructions: Installation Installation is quite easy Make sure your network has DHCP auto enabled Connect one end of the included Cat5e cable to Polisy’s Network Port and the other to your network. You must use the port that’s closest to the right most edge of Polisy when the front of Polisy is facing you (closest to the db-9 serial port). Note: the network must initially be DHCP auto enabled If you have the PRO version, attach the included antennas to the back of the unit. Connect the power supply Make sure the bootup sequence is as described below. I take that to mean if you have DHCP enabled, which is required, and do not plug anything in to Ethernet port, Polisy should auto configure for wifi. In PG3 or PG3x, all that is then needed is the IP address and the port number, if Polyglot can not auto configure.

Yes, the process is simpler without Zwave. Here are sections you need to follow from the migration document. What to Expect During Migration Insteon The Insteon network on ISY-994 will be seamlessly transferred to Eisy / Polisy. Your nodes, programs, and scenes using Insteon will remain unchanged. Network Settings Starting with Polisy, and due to massive support requests, we have disabled static IP configuration. Please use DHCP reservation in your router instead. The advantage of DHCP reservation is that, in case you change your router, you can still find your eisy/Polisy. Preparing for Migration from ISY-994 On your ISY-994 Make sure the ISY-994 is upgraded to 5.3.4, If you are not migrating your Z-Wave network Make a backup of your ISY-994 (Admin Console | File | Backup ISY) On the Eisy / Polisy your are migrating from Make sure Eisy / Polisy is up to date Go to Admin Console configuration page and select Upgrade Packages If you are not migrating your Z-Wave network Use (Admin Console | File | Backup ISY) Migrating On the Eisy / Polisy you are migrating to Do the appropriate preparation step (see above) Make sure Eisy / Polisy is up to date Go to Admin Console configuration page and select update packages If you don't have a current backup, make a backup of your Eisy / Polisy (Admin Console | File | Backup ISY) If you are using Insteon, plug in the PLM If you are not migrating your Z-Wave network Use (Admin Console | File | Restore ISY) to restore either your Eisy / Polisy backup or your ISY-994 backup. If you are using Insteon Go to the Admin Console configuration tab and make sure INSTEON Support is enabled (default username/pwd = admin/admin) If you are using a new PLM, Restore the PLM Reconfigure any software utilizing to point to this Eisy / Polisy, restart the other software, if necessary. If you have ISY Portal on your 994 Follow these instructions to migrate your account, license, and Alexa/Google Home settings This will also migrate all node server licenses from your Polisy to Eisy / Polisy. Have you completed all of the above? Were there any errors? Did you move the PLM or start with a new one? Did you check the Insteon support box on Configuration tab and restart? Does the PLM on eisy show connected?

Restore is not the way to migrate from ISY994 to eisy. You need to follow the migration instructions linked by @lilyoyo1 Before migrating be sure to read and understand all of the instructions. Ask questions about what you don't understand before starting. Also, be aware, you either require a USB PLM or if you want to use your existing serial PLM an adapter cable available in the UD store.

Are you sure about that? Zwave devices with the prior Zwave board and Zooz stick were named ZW. If you migrate to ZMatter, the name is upgraded to ZY. Although I see it has been removed from the migration wiki, this use to be specifically called out in the migration instructions. I believe it still holds true.

Try going to the log tab, setting it to information or higher, and then restart the node server. Check the log for problems. Keep the admin console closed while doing this.

I would suggest running restore PLM again. Keep the event viewer open set at level 3 while doing this. Monitor for any errors.

As I said above, the ZW items didn't migrate over. Not sure if you can rerun the migration tool? If not, you would need to delete them, factory reset each device, and re-add. I don't see the need to reset Zwave network. However, part of the migration process is correcting the programs for the change in node address.

What did you upgrade to? Are you now on eisy with ZMatter dongle? If so, no you should not have both. ZW was the original Zwave prefix and ZY is the new prefix for UD's ZMatter dongle. Sounds like the devices still with ZW did not migrate. Not sure what you are asking, what are you trying to find?

Do You have a portal subscription? A portal subscription makes remote access easy, obtain your unique portal ID URL from the portal, start IoX Launcher, click on add, and add the URL. When and how are you seeing the text you posted?

Followed the More info link in the store and it showed this:

I just checked the node server store (or plugins) and see it indicates to install via Polyglot v2?

I haven't installed my mini split unit yet, working on that next week. Afterwards, I will install the Sensibo.

2 way communication is dependent on exactly what you would be looking to do. It appears the Sensible can turn on/off, apply time schedule, geofencing, and control temperature. The model I posted a link to can interact with the usual voice activated 3rd parties. The only thing I have seen that it can not control at this time are the movable louvers. You can also add optional remote temperature sensors. Yes, you need to plug in Sensible, but I don't have an issue with that. As for it not working with Dalkin, I saw those reviews and I also saw other reviews that indicated it did work with Dalkin. The manufacturer seems to think that it works with almost all of the units with a remote control, as it appears to either interrupt that signal, clone it, or some how piggyback on it. We will see.

Sensible Air is supposed to work with all mini split systems with a remote control. Amazon has them for $124, but has been running sales for $99 on and off. There is so an API available. I am installing a mini split this weekend and shortly after will install theSensibo Air. https://www.amazon.com/Sensibo-Air-Conditioner-Controller-Installation/dp/B08T9XXFRW/ref=mp_s_a_1_1_sspa?crid=CDQB96SQ5NI7&keywords=sensibo+air&qid=1698199185&sprefix=sensibl+air%2Caps%2C106&sr=8-1-spons&ufe=app_do%3Aamzn1.fos.18ed3cb5-28d5-4975-8bc7-93deae8f9840&sp_csd=d2lkZ2V0TmFtZT1zcF9waG9uZV9zZWFyY2hfYXRm&psc=1

When creating a tile or widget of the command type, you can select and set display status and the command to run. At the bottom of the screen, select add, followed by the node. You then select from available run commands. Does this do what you want?

If you have a Polisy, it sounds like time to migrate.

Try setting up a test. Start the log at level 3 and have someone operate the breaker off - on. See what appears in the log.

Delete PLM is something you do not want to do. There is no recovery from it. You would need to reinstall your devices. Speaking of reinstalling devices, if you are willing, you could try deleting one device, factory resetting, and adding it back in as a new device. I would reboot after deleting and before reinstalling.

The downloaded file start.jnlp gives the Launcher instructions regarding version of firmware you are running. UD made some changes to the discovery method to try to improve the process. This change required a new start.jnlp be downloaded. I last ran this process on Monday with a Win 10 machine and had no issues hearing Java cache, downloading start.jnlp, and having new Launcher on desktop after running.

Query is available for the Then portion of a program. I'm not in front of a computer to tell you exactly where, but should be easy to find if you look through the available options.

You could try rebooting, then clear Java cache, all 3 boxes. Then download new start.jnlp and run it.

You get the Launcher from running start.jnlp available from UD website, but first you need to clear your Java cache he (all 3 boxes). You can download start.jnlp from here: https://isy.universal-devices.com/start.jnlp There is also a link in the wiki instructions page: https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop The not found box is the result of using an outdated Launcher. To correct the issue, clear your Java cache and download a new start.jnlp.

From the About menu, what version firmware & UI are you running? When changing PLM, did you follow the correct procedure and did you do a restore PLM (different from restore backup).