oberkc

As suggested by @tazman, your next step would be to choose "migrate...." in the configuration tab. I have the Polisy, not the EISY, but I had the same experience and "dongle not responding" message. UD responded to my ticket with the same advice. Unfortunately, I understand that the migration process is still having growing pains so, if you plan to migrate in the future, my best guess is to hole off. If your intention is to start with a fresh z-wave installation, I would go ahead a choose the migrate option>>>use zwave dongle without migration. Unfortunately, I have not seen these instructions (regarding the migrate option) in the wiki, so I suspect this will be an ongoing issue.

I am wondering aloud whether the legacy ISY can be maintained, along with the EISY/Polisy, only for the IR capability. Of course one would have to create a communication path between the old and new (network module?). Unfortunately, I cannot offer any assistance in this matter other than to recall in the past that some were using multiple ISYs and could communicate between them.

I do not use programs for garage door status or control. All is done with scenes. What happened to your existing programs or scenes? A failure of a controller would not cause loss of any programs or scenes? How do you expect your system to operate? (What are your functional requirements?)

I don't know how long ago that the wiki reference was made. At one point, I don't think Alexa had room-sensitive commands...this is relatively recent. Before then, I assume that one could put a single Alexa , along with related devices, under separate accounts for each room. Alexa has evolved since then, and this workaround is no longer necessary.

I understand that, and have been waiting on, this is software that allows one to migrate an existing zwave network to the new zmatter system without having to go through the exclude/include process for every zwave device. I did not want spend all the time needed to recreate the zwave network. My existing system is working fine and I had no urgent need to migrate to IoP. For those of you willing to manually re-add all your z-wave devices to IoP (whether using zmatter or a dongle) I do not think that this announcement is any big deal. Or, perhaps this earlier software releases were "beta" and this one is actually z-wave certified.

Yes, one can migrate Insteon. I understand that zwave migration yet to be available but is coming soon. I should have been more specific.

I am using polisy with the legacy ISY-994. (I am waiting on the migration software to move the ISY capability over to the polisy). It works well. As Goose66 says, this will allow you to integrate additional devices into your ISY without the complications of using the network resources module. I use hue lights, roku, Sonos, and a few others. The ISY now can control such things.

Even if we don't get the migration software by the 9th, there are still better options, like golf and pickleball.

As near as I can tell from my various echo devices...I have several, with each assigned to a room, along with lighting devices assigned to a room....when I say "Alexa, lights on", any "light" in the same room as the responding echo will turn on.

What is the device? I perceive such errors associated with the few Insteon devices not directly supported by the ISY, such as the newer version of the motion sensor.

I did not know, or had forgotten, about this. Thanks. Fortunately, a good night's rest seems to have done wonders for the Polisy and IoX. Because of nothing that I have done it is now working. I can now access IoP and both versions of polyglot from the new launcher.

I would have difficulty doing this, since my IoP no longer shows on the finder (now called IoX). The "update package" option is in the IoP, with access to it being no longer available from my updated IoX launcher. Am I missing something?

mine, too, is broken. My "new" IoX launcher appears on the desktop, but only has the legacy ISY showing. It does not have the IoP showing. Trying to add the IoP by using the URL:8443/desc resulted in a "not found" message.

Have you ever checked the status of "driveway dusk dawn" during a random turn off? Is it possible that the dusk dawn sensor is being fooled by some artificial light source?

I, too, hope you are wrong. My memory may have failed me, but I thought that was the intention of the EISY and matter board for the Polisy?

I still have mobilinc on an iPad. It still works. I do not know whether it is still available on the App Store. I never used the subscription, either, so I don't know that status. Most, I would guess, use UDMobile at this point. I believe it requires a certain version of ISY software so, if you have not "paid much attention" to your system, you may need to update.

My routines are working, but seem much delayed compared to times past. I have done no troubleshooting.

And...I can understand this and find such a limitation reasonable. My concern is with the initial login to PG3, just to get to the home page, dashboard, and settings. If the portal login is driven only by the node server store, then allow me to log into the polyglot without the portal, requiring portal login only once I try to access the store. I understand that I cannot download new node servers or, likely, update old ones, but I have assumed that the node servers I have already download and/or purchased (with the portal account active) would continue to work without a portal account no longer active (should I choose to later end the subscription). Is this assumption false?

Are you suggesting that my polisy (at least PG3) now becomes a paper weight if I don't have internet and a portal subscription? I thought portal subscription was used only for node server store?

If my experience is typical, I would be hesitant to do so if planning to keep running PG2 and ISY. Performing a recent update on my IoP caused my PG2/ISY relationship to fail.

FWIW, mine uses HTTPS: and port 8443. I noticed your finder used HTTP only. Have you tried replacing, in the "input" screen, the IP address in place of the word "polisy"?

Yes, there are three options you listed, but you may need to do all three depending on your goals. You could choose your option number 1, but that would only change when the scene is controlled via ISY action (it would have no effect when devices are manually controlled, nor when responding to another controller device. Assuming you want the stated on-levels regardless of how a device is initially turned on, 1. Click on the scene and set the on-levels of the two devices to suit your 50/28 preference. 2. Click on each controller device within the scene and set the on-levels of each of the two devices to suit your 50/28 preference. See if this works for you.

Thanks for that bit of knowledge. In an attempt at full disclosure, there was a short time where I had changed the default login credentials on the IoP and had yet to make the change to the PG3 settings. I don't doubt that this created some log errors until I updated PG3. I had two "ISY"s connected to PG3. During all this difficulty I was having, my belief that both the ISY/IoP were connected was because there was at least one node server (not the Hue Emulator) on each that was appearing to work, and reflected in the admin console (the nodes were in the device listing, as well as under the drop down node server dialog box.) Thanks for your help

My whole experience with the IoP and PG3 has been odd (putting it kindly). I had a working ISY-994>PG2. I was preparing to migrate to IoP by updating the software of the IoP. The results included breaking my ISY-994>PG2 relationship. I thought I had, but I can see it was not obvious, or perhaps answering the wrong question. I have checked multiple times and my settings are correct as best I can tell. Both show "connected". I was on 3.1.8, but am now on 3.1.10. It took me a few minutes to recognize that the update reset the username and password to default. This did seem to have an affect. Hue node servers are now showing connected on ISY-994 and IoP. I tried installing the Hue Emulator node server on IoP and ISY-994. No more errors and both are showing "connected". I am going to call this a small victory. The hue nodes now show up in "my lighting" , as does the hue emulator. I will call it a big victory when I can confirm or configure all the programs and scenes with the hue lights. Usernames are correct as best I can tell. Both have been showing, and continue to show connected. Both had some node servers working but others not. But...the point may now be moot given that moving from PG3 v3.1.8 to 3.1.10 may have fixed the problem. I will know more soon, but it all seems to be coming together now The non-standard port was driven many years ago. I had another device that also used port 80, so when I tried to access the ISY on port 80 from a remote location, it found the other device. I gave the ISY it's own port at that time and things have been working well, so I never changed it back. I will continue to check out everything to see if it is working or, if not, update all the programs and scenes to their original configuration.

Thanks for looking and finding the errors in the log. I wish I knew what do to about such a revelation. I can get the hue node server to run on PG3>IOP, so the connection seems to be working. Unlike the Hue node server, the hue emulator, I notice, has fields for the ISY, which I have populated multiple times, and match the global PG3 settings for the ISY. In the hue emulator, I notice that the port for ISY (8080) is the same as the port for the emulated hue (also 8080). I assume that this is not a problem. I also observer that I can install the hue emulator, I get the big red error message during installation, but the hue emulator still shows up on the dashboard (disconnected). I can then populate the ISY fields under the configuration page, but after a few minutes, the dashboard no longer has the hue emulator. FWIW, I also have a second ISY (the legacy ISY-994) running and recognized by PG3. The results with the hue emulator are nearly identical. Furthermore, the hue node server (as opposed to the emulator) will not connect (it DOES connect to the IoP).