MrBill

I started using it as a front end to the ISY, to replace mobilinc, agave, etc... most has stayed in the ISY, but I added zigbee to HA... using about a dozen HA integrations mostly for things the ISY couldn't do.

Not surprising. I don't make scenes in HA, All my scenes exist in the ISY, HA can control the ISY scenes.

Yes UDI uses AWS for portal and polyglot cloud.

or buy this adapter. and use the cable you're using with the 994i I saw then Port A pinout somewhere, but I can't think where it is, but it shouldn't be difficult to configure the adapters pins.

2413s works with Polisy. It uses the cable that came in the box with the 2413s instead of the current cable you're using with the 994. 2413u also works with Polisy.

There's already a large number of threads (at least 12+) on exactly this topic. No you can't connect a USB PLM to the ISY-994i. the basic options are: 1) Buy the USB and open it and your dead serial PLM and swap the daughter board. 2) solder new caps into the broken serial PLM 3) build and adapater using several parts and a raspberri pi 4) convert to using a Polisy hardware with the ISY on Polisy softare running... which will allow the use of a USB PLM however ISY running on Polisy is in alpha or beta testing (I'm not sure what the current label is) and is far from bug free. There is also no clear easy migration path yet, that means you would need to start from scratch, rather than restore a backup on new hardware. --- the easy option is #1

If you have a Configuration > Portals tab and don't have a message to accept, then double check the UUID from Help > About to the UUID that's entered in the Portal. Also try restarting your admin console and checking again on the portal tab. Assuming the UUID is correct, the next step would be open a ticket with support@universal-devices.com -> Include that all import UUID number so they are see why it's not matching up.

Yes..... It's basically the same thing... But I use this program by @kclenden to set a number of date variables: Set Date Variables - [ID 0104][Parent 0126] If Time is 12:00:00AM Then // Determine Day of Week $sISY.DayOfWeek = [Current Day of Week] $sISY.DayOfWeek Init To $sISY.DayOfWeek $iISY.DayOfWeek = $sISY.DayOfWeek $iISY.DayOfWeek Init To $sISY.DayOfWeek // Determine the Month $sISY.DayOfMonth = [Current Day of Month] $sISY.DayOfMonth Init To $sISY.DayOfMonth $iISY.DayOfMonth = $sISY.DayOfMonth $iISY.DayOfMonth Init To $sISY.DayOfMonth // Determine the Month of the Year $sISY.MonthOfYear = [Current Month (Jan=1, Feb=2, etc.)] $sISY.MonthOfYear Init To $sISY.MonthOfYear $iISY.MonthOfYear = $sISY.MonthOfYear $iISY.MonthOfYear Init To $sISY.MonthOfYear // Determine the Week of the Month $iISY.WeekOfMonth = $sISY.DayOfMonth $iISY.WeekOfMonth -= 1 $iISY.WeekOfMonth /= 7 $iISY.WeekOfMonth += 1 $iISY.WeekOfMonth Init To $iISY.WeekOfMonth $sISY.WeekOfMonth = $iISY.WeekOfMonth $sISY.WeekOfMonth Init To $iISY.WeekOfMonth // Create Month.Day Combo $iISY.Date_Scratchpad = $iISY.DayOfMonth $iISY.Date_Scratchpad /= 100 $iISY.Date_Scratchpad += $iISY.MonthOfYear $iISY.MMDD = $iISY.Date_Scratchpad $iISY.MMDD Init To $iISY.Date_Scratchpad $sISY.MMDD = $iISY.Date_Scratchpad $sISY.MMDD Init To $iISY.Date_Scratchpad Else - No Actions - (To add one, press 'Action') I re-paste the program rather than just linking to the original which can be found below because there is a minor change "Week of the month" calculations. This version uses the i or Integer version of the variable for inline calulations, then copies the value to the state variable. The original used the state variable for inline calculation which results in false triggers of other programs for intermediate calculations. Why set both state and integer variables for each value? A state variable acts as a TRIGGER in an if statement, conversely an integer variable acts a FILTER in an If statement. Original thread:

First you say that you didn't want to confuse the guy, so you confused terminology purposely. then in the very next post the first line says: Polisy is the hardware Polyglot and isy are the primary software that runs on Polisy. UDI is a master of naming confusion ? Two great examples: They are still called "Integer" variables, but they've had the capability of decimal places for years now. The About screen of "ISY on Polisy" still calls the ISY software "firmware", that's a term that applies to the 994 hardware, not to the software process called isy that runs on Polisy. We'll being calling it "firmware version for many yours to come tho.

that does add to the perspective and is something I missed in my thinking. that sums it up well!!! ?

As far as I know you should be receiving an upgrade offer to version 4.9. That's the current latest and greatest in the v4 firmware lineup. It does have fixes you likely need if you're only on 4.5.4/ As far as I know. it's been a long time since I've been on the version 4 branch. But I believe it should be showing an automatic upgrade option. Yes there is a version 5 which opens up a lot of new features. In the V5 branch all updates are manual. The current release is v5.3.4 which is label as a "test build" but it's stable and the version everyone should be using. I typed a more detailed explanation early today. see: You should definitely upgrade to 4.9... reality is that it's really time to move up to V5... Another thread you might want to read from the top to get a better sense of where the ISY ecosystem is headed:

WAS... I realize, but we are trying to put this into perspective for a large group of people that seem to be having difficulty getting it.... we aren't bending history much.. 26, 99 and 994 and really hardware models that had their own specialized OS that ultimately run "isy" (assuming that isy software isn't so tightly intertwined with the OS that it's not the same as the OS--which is a possibility.) "isy" is replaceable firmware in the case of 26,99,994 it was running on that class of hardware. with Polisy, "isy" is no longer actually firmware but "software" running under FreeBSD. I suppose that like "Integer variables" that don't have to be "integers" anymore we are going to continue to call ISY software as "firmware" because the "about" screen in the admin console will forever persist calling it "firmware"

Actually I noticed just the other day that the iOS spellchecker on my phone corrected policy to polisy.

I think you mean Polyglot. there is no process named Polisy running on Polisy. Polisy and 994i are hardware. polyglot and isy are the software modules. Otherwise you've given a very good overview, but this thread is raging with inaccuracies. Several posts are very close, but then someone throws confusion into the mix right after.

POL-ISY is Polyglot and ISY combined in one... as @upstatemike points out its pronounced like Policy.

Pretty sure they are about to upgrade Covid to 700 series... 300 tho was deprecated before it was a pandemic... ?????

I was corrected just yesterday... However the version with z-wave support also did just arrive yesterday... and from other threads I've seen it's not perfect yet.

Log into the portal and look for MyProfile in the Upper right corner. Change the dropdown to "Use All ALexa's on Account."

You actually have me really confused here.... I'm not sure those two are different. Any ISY-994 is dedicated hardware with a dedicated OS that's tightly interwoven with the software we know as ISY. The admin conole is something else entirely, it's a java client that talks to the ISY running on either a 994 or "ISY on Polisy" Polisy is also hardware, but less dedicated and running FreeBSD as the OS. The two main applications that run on the Polisy hardware are Polyglot, and what's being called "ISY on Polisy" but it's really just ISY, we are using the term "ISY on Polisy" to differentiate that version of ISY and the version that runs on 994 hardware. Michel pointed out in another post yesterday that functionally other devices and clients see ISY version 5.3.4 running on 994 hardware exactly the same way they see v5.2.0 running on Polisy. So UD mobile, or home Assistant for example can't really tell the difference between the two. So, I'm not sure how "ISY on Policy" is different than "running an ISY on a Polisy". The process running on Polisy hardware is simply known as isy... if you can't see the box you're connecting to, you might never know...

Polyglot is an application. Polyglot 2 can actually be run a raspberry pi (it's original home) or Polisy. Polyglot 3 will require Polisy. All polyglot 2 nodeservers are open source and available on github... so if you know what you're doing and want to change the way the nodeserver works that's currently possible. With polyglot 3 nodeservers are closed source, and the limitation to polyglot 3 on polisy allows the nodeserver author to charge one-time or recurring fee's. correct... except a node isn't the physical ISY, a node is an entry in the Device tree on the 'main' tab of the admin console. Before node servers the only "node" types were insteon, z-wave, and scenes.... nodeservers can inject more nodes into the device tree.... perhaps a wireless tag placed inside the kitchen refrigerator: correct.

We have friends that are both natives of Puerto Vallarta and friends from group of Ex-pats that live there most of the time (we considered becoming permanent residents with dual citizenship)... they tell us virus control and vaccination level is low.

Correct, I thought you couldn't get rid the of the admin console with busy status bar. for the UUID issue you should open a ticket. support@universal-devices.com

To stop that you'll need to open Task Manager (Ctrl-shift-esc) and kill the java web launcher.

we are likely overdoing the fear level.... but you'd have to know my wife.. But I see her point... Test positive and then hope a hotel has a room for you for 2 more weeks, or whatever it takes... (we typically do AirBnB's, which will have another guest booked as soon as we leave). Then phone the Dog camp back home and tell them the dogs will be there much much longer....

click button A in admin console then right click it and choose "Group Devices"