oberkc

Is not the thread you referenced the one we are in, and currently corresponding?

Thanks. I would have assumed something like that. I also assume what is now called "Backup" is what was formerly called "Full". Unfortunately, these are the types of details that cause me some loss of confidence. This wiki page has been recently quoted as the latest migration process, which includes updating to ISY 5.3.4 (step 1, which cannot be done with 300 series z-wave dongle). Things can go wrong when one gets careless with the details.

I am, after so many difficulties in recent times, getting the ambition to make the transition to IoP from the legacy -994. I am trying to follow the instructions on the wiki and want to be sure to be precise. In step three of the wiki is: Wiki step 3: "Backup your 994's Z-Wave dongle (Admin Console | Z-Wave | Utilities | Backup | Full)" Unfortunately, I see no "Utilities" option under Z-Wave, nor do I see a "Full" option. Yes, I am on 5.3.4. Is this a problem? Why do the instructions not match my admin panel options?

As far as I know, there is no direct access to “works with alexa” devices. Alexa devices do not show up in the ISY device listing, and status is not directly tracked. Having said this, one can trigger alexa routines via the ISY. My memory is a little vague on this, but some ISY devices can be added to alexa as “sensors”, as can ISY variables. Such “sensors” can be used as a trigger in alexa to force n lexa rotuine to activate. I use this method to control alexa announcements via ISY programs, but anything that can be done via an elexa routine cna be triggered via ISY including, I assume, controlling alexa-enabled devices.

Does it appear that your ISY is operating normally? Programs working? No funny lights on the ISY front panel? In my IoX launcher, the format for the URL is http://myISYaddress:myISYport/desc I am hopeful that you know your ISY address and port. Regardless, my IoX has alway found my ISY and polisy and I do not recall having to add them manually. There have been times when I had to reboot one or both, and times when it seemed that removing IoX and re-installing (including the clearing of the Java cache) was helpful. You might try this.

I may have missed it, but I saw no stated requirement for this to run on the "last" day of each month.

Yes, I think this is something you should do. IIRC, the additional of calendar variables was one of the big reasons I was excited to make the update to 5.X. Without it, your options are quite a bit more limited (and potentially more time consuming than making the software migration.

I assume that one is skilled enough to recognize the number of days in each month, and that some have 31, some have 30, one has 28 (and sometimes 29). I also assume that one recognizes that if one picks some number greater than 31, such a program will never trigger, that if one picks a number such as 29, 30, or 31, it will only trigger on some of the months. I would like to think that if one is trying to create computer programs using Boolean logic, that such person can figure the simpler parts out on their own.

I would be more inclined to create a variable to keep track of the day of month. Once each day (I do mine in the 3am cleanup program), run a program that includes a step: $dayofmonthvariable = [Current Day of Month] Create a program such as: if $dayofmonthvariale = some number then turn on Insteon module wait for some period of time turn of Insteon module else nothing The program, above, will work only for periods of time less than 24 hours. 24 hours after this program runs true, the day of month variable will change, become false, and halt any wait state.

I suppose you could test his theory by watching the program log while you execise the various keypad buttons. Does the program run twice, first true, then false?

Mine showed the migration option also on 5.5.2

I am waiting as well. I dont have an immediate need to move from the -994 at this point, so until that changes or I am more confident that the zwave migration path is less rocky, I will stay with the trusty ISY.

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.