MrBill

To be clear, the Philips Hue Bridge is required to use the Hue Node Server or ISY Network Resources.

who did you order from? the UDI store is here: https://www.universal-devices.com/store/ and 994's are still available... that said... at this point in the game I'd reccoment that you should spend your money on a polisy instead. (standard Polisy is fine, Pro option unnecessary at this point.)

no hub, just a Pi, a 3 will do a 4 is better. Can also be done via a VM or container on something else, easiest to maintain tho if you pick one of the options with HA o/s and Supervisor. https://www.home-assistant.io/ click "Getting Started" at the top to look thru the various options. It's an open source project with no subscription fees unless you want to pay for their cloud interface. Once it's up and running add the Universal-devices integration and the Pentair integration. If you want to drive the lights from the ISY there's a number of ways to set the control up.

By default, PG2 runs at https://<Polisy ip address> PG3 is https://192.168.1.89:3000 Ports 443 and 8080 are used for IoP, but you still need the admin console.

Personally I use the menu item in the PG2 interface, System > Shutdown Polisy or from the admin shell login sudo shutdown -n now The wiki also suggests using the hidden button on the front of Polisy.

There's a long thread that i just spent 15 minutes trying to find via google site search but I'm not turning it up. I've tried a number of things over the years. The best used to be an Autellis hardware interface that wires in parallel to the screenlogic brick. That company appears to be dark, and the product is unavailable. The new best IMO is the Home Assistant Integration that connects directly to Screenlogic via IP address. I then configured a few variables and programs to pass a few values back to the ISY. I added a Salt cell level adjustment that takes input from the UV sensor of the weather station (that's an ISY Node server piping its values to HA via integer variables). I haven't perfected this automation yet because I did it over the winter and the water is not warm enough yet for the salt cell to function. The point tho is to increase chlorine production on sunny days and decrease it on cloudy/overcast or rainy days.

PG2 will still run on a pi. PG3 was designed for Polisy only. As for your conflict... think of Polisy as an upgrade to your ISY. In addition to Polyglot, Polisy runs ISY (on the 994 it's firmware on the Polisy it's technically software). To reitherate, this will retire your 994 hardware and run both polyglot and ISY on a single piece of hardware.

You can ask. it's possible the enhancement makes sense for IoP also... it which case it maybe possible to backport it to the 994 firmware as well... or not.... anyway there's actually a place for product enhancement requests to be posted, which is a good thing... in a regular thread they might get lost.

The program is checking two things Status and looking for DOF. In DON never changes the status to On the compound statement won't be evaluated. I gotta hand it to @apostolakisl this is a cool programing technique.... I haven't moved over to Polisy yet but I've already used it..

The hub doesn't have a built in web server or local software produced by insteon. there are a few open source software pieces that allow access to the hub for what I would call infrequent needs. There are also overall home control packages that will use a hub like the ISY uses a PLM. (The ISY doesn't support the hub, only PLMs). Home Assistant is the one of those packages that I'm most familiar with. Home Assistant is open source and does not have a lisc fee, runs on a Pi (a 4 is recommended but a 3 will work) or many other platofrms. When the Insteon integration is added, the user also supplies the local IP address of the HUB (found via the router) and the usnername and password on the label on the bottom of the hub (not the credentials used for the app). Home assistant over the next few hours will find on the insteon devices, the process can be sped up by walking around and turning this on and off. The caveat is that HA doesn't allow you to access schedules that are existing in the hub. The workaround is to get one of the utilites that access the hub and delete those and then use the HA automation functionality or alternatively factory reset the hub and all devices and re-link manually using a developer tool in HA. To add Alexa functionality one would need to subscribe to the HA cloud at 6.50 /month or $65/year (annual discount = 2 free months or 16%) There are many other things that can also interface with Home Assistant if your friend is interested.

You'll need a program for that, and you could use either the single node with the correct logic or the second node.

A 2413s PLM must be plugged in and online when Polisy boots or the port won't be found. (May or may not be true for 2413u).

You should open a ticket: support@universal-devices.com

like @oberkc's response I suggest linking programs, I'd do it slightly differently. Use your existing programs for what happens all the time, the last statement of that program being to run the optional programs. One thing NOT covered in that response was that these extra conditional programs must be disabled. A disabled program still runs when commanded to by another program. EXISTING PROGRAM: If (probably blank because it's an Alexa command) then ... do whatever to turn on the inside lights... Run Program OutdoorEventLightsON (If) else ... do whatever to turn on the outside lights... Run Program OutdoorEventLightsOFF (If) --------------------------------------------------------------- Program OutdoorEventLightsON (Disabled) if Sunrise to Sunset (same day) then .... do whatever to the outside lights during TURN ON if it's day (this might be left blank) else ....do whatever to the outside light during TURN ON if it's Night out. -------------------------------------------------------------- Program OutdoorEventLightsOFF (Disabled) if Sunrise to Sunset (same day) then .... do whatever to the outside lights during TURN OFF if it's daytime else .... do whatever to the outside light during TURN OFF if it's Night out.

Now this sounds like an easily reproducible bug. One that you should open a ticket to make certain it gets attention.

I suspect this is because Polisy is much faster than 994. It's able to update "status" more quickly than 994.

I use the 2node which I think creates what you're looking for on a bathroom door. Go in close the door and the light comes on, open the door to leave and the light turns off.

Polyglot cloud is offline due to security issues. No ETA for it's return.

Note: this does not need to be enabled for the ISY to have internet access and should in fact be left disabled. It's poorly named it actually enables UPnP which is an out of date protocol that's generally no longer used anywhere due to the security issues it creates.

Both are true. You can get a 30 day free trial for a new device anytime by just adding it to the portal. Polisy also comes with a 2 year portal license. To redeem that license I believe you must email UUID number to support@universal-devices.com and they will manually extend the subscription date. NOTE: portal licensing is per device and not per account. Many users that purchased Polisy early used the free 2 year portal license on the 994 to allow access with Polisy.

It's hard to tell by your word choice, Are you saying you are using "Mobilinc Connect" or the "ISY Portal" (aka: my.isy.io) to connect your ISY to Alexa servers?

I'll counter that with, I try to keep all the magic in my local controller, using Alexa only a "dumb" I/O device. In the beginning the only local controller was the ISY, then ISY got a brother Home Assistant. In the end today it depends which controller has direct control of a device as to which controller get the automation or program or scene or grouping. My son on the other hand.. has recently had to adopt Home Assistant as he was an Insteon hub user. In sorting thru all the "stuff" he's bought and added to his house we find it difficult to make Home Assistant the brain or controller because some many of those "things" are "works with alexa" cloud accounts. At his house Alexa is ending up being a co-controller again, because there are too many cloud only devices not supported by a home assistant integration. When purchasing items he didn't make the connection between "cloud" vs "local" control. Now after the insteon debacle he wishes his "stuff" had all local control, so that he could use Alexa as an I/O device only, retaining local control when the internet is off, alexa's down, or the company goes out of business.

This is essentially the diagram you are describing, however your description has an error. should read: Top of stairs: 14/2 - Power/line in (Black as line was connected to the black screw, white is neutral) 14/3 - Goes to bottom stair switch (white neutral, black and red travelers Should read: Bottom Stair: 14/3 - Goes to top of stairs (white neutral, Black and red traveler) 14/2 - To lights/Load (black to common, white neutral). So as you have discovered, the 2nd switch needs to be the companion switch and not a second of the same model.

I agree that the hub has to get factory reset to get rid of schedules. What I'm unclear about (and actually my son just called and asked a similar question. If you reset the hub, and/or factory reset a switch how do you add it back to the hub? He's migrated from insteon hub and alexa to Insteon hub and Home assistant. for the most part he's got 3 switches that (I think) got manually linked weirdly. Anyway the solution seems like those 3 switches could be factory reset (non are 3-way) but then how do we link the back to the hub?

HA can use a HUB, it can also use PLM's, for the insteon integration. The devices are still stored in the hub, thats the basis for the red banner on the forum, telling people not to factory reset their hubs... its easier to set up HA to operate the hub if the devices haven't been wiped out of it.