MrBill

@oskrypuch in addition to @Bumbershoot's instructions... when prompted for your isy credentials: you must enter your PORTAL credentials here, not what you enter when on the local network.

Send support a ticket support@universal-devices.com they'll have you up and running in a jiffy, keep in mind they are california timezone but they respond very quickly.

You want admin console not dashboard.

I agree, I missed that there where two networks..... 192.168.4 and 192.168.1 don't pass traffic to each other without some advanced networking, they are on the surface considered separate networks. One or the other needs to be in bridge mode.

@GFuller01 An Insteon 2413S PLM plugs into Port A, using an "Ethernet cable" (but it's not really Ethernet protocol being used from PLM to Port A). The PLM must be fully powered up first. Next make sure the ISY is connected Network jack to your Router. Ethernet connection is required here. After the PLM is powered up for about 30 seconds and has a solid green light, then plug in the ISY. After it's had time to boot up, what light are on on the front of the ISY? an ISY994 does not have USB.

32 GB card also works, and is easier to buy.... look specifically for the newer A1 rating, also note it's a MICRO SD card. (A2 is also ok but will fallback to A1 as A2 requires hardware support that the ISY doesn't have.) the proceedure can be found here: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card

Do you have portal? if so use: https://wiki.universal-devices.com/index.php?title=ISY_Portal_IFTTT_Integration There is a network resource example here: https://wiki.universal-devices.com/index.php?title=ISY-994i_Series_INSTEON:Networking:Network_Resources:Twitter

The recent problem that occurred was the OS upgrades installed updates before UDI Processes has been modified to use the new functions, thus breaking installations because they were too up to date. If a user doesn't yet have IoP installed they should seek the assistance of UD support to get it installed without updating other things that may not yet be useful.

Please don't use the "classic" method. See this notice:

@Bernman If you end up resetting the credentials on the 994, follow these instructions exactly. Please note, the Factory Reset instructions are very similar, further if you are not careful when following the Password reset instructions you will instead factory reset the entire device.

did you say "Alexa, Discover devices"? Also did your set your devices up via the portal?

Is there a problem with the PG3 version of the node server? It does exist in the production store. Or were you wanting it altered? Also PG2 has been deprecated, but is still working. Deprecated means it won't receive additional enhancements, but as yet it hasn't been removed from the system.

@EMercado You should tell us what issues you are having? What procedures have you followed? Where/how are you getting stuck?

I wondered yesterday when I read this thread if the wiki should be updated? While the ISY994 accepts a wide variety of voltages, is that also true of Polisy?

It's really not too hard once you realize what you're doing. It would be nice if the driver ID appeared in the admin console to the right of the value name perhaps in white text. I suggested that years ago.

that's actually what the above does. You're only look up the driver name via the polyglot interface during set up. ${sys.node.<node address>.<driver>} is actually coming from what the node server has sent to the ISY. Sure you can do that. It's an extra step, and the time will just be a number. using the above method you'll get whatever formatted Value that you see displayed in the ISY. In the case i used above formatted temp looks like this: which is exactly what will be substituted for ${sys.node.n015_temps.GV15} But yes you can set a variable = to the node server value, adds programming steps and uses variables but sure...

to repeat for @jkrausanyone that missed it: To create your email or notification substitution: First make note of the current value of the temperature as shown on the node for the admin panel, that will be 95.2 for my example. Next head to PG2 or PG3 interface (note my screenshots are not from YoLink Node server, I don't own that product). First click from the PG2 or PG3 dashboard click on "details" and next on "Nodes" for the YoLink Node server. then scroll down until you find the node in question (#1 in the screen shot below) locate the temperature that you made a note of from the current value showing in the admin console (#2 in the screen shot below) Trace back to the left and find the Driver for that row (#3 in the screen shot below) In this case we found GV15 Next head back to the Admin Console for one more value, from the node that displays the node address: in this case it's n015_temps. Now we will put that together with the base substitution: starting with: ${sys.node.<node address>.<driver>} we will use the two things we found above to arrive at: ${sys.node.n015_temps.GV15} (your will be different than mine) Now create your notification using the string created ${sys.node.n015_temps.GV15} where you want the temp to be substituted in the notification. ---- About program creation, If you create the simplest program possible: If Pool Temp > 80.0 then Notify else (none) the problem that you will have is that every time the temp updates when it's over 80 you will get another notification. Especially annoying if the node server is reporting temps in tenths of a degree. To solve that you need 2 programs: Program 1 If Pool Temp > 80.0 then Notify Disable Program 1 (this must be the last THEN statement since we are disabling self) else (none) Program 2 (also set this to Run at Startup) If Pool Temp < 78.0 OR Time is 8:00 AM OR Time is 6:00 PM OR Pool Temp > 85.0 OR Pool Temp > 90.0 then Enable Program 1 (this must be the last THEN statement since we are disabling self) else (none) In Program 2 i included a number of OR's in the if statement.... add or remove whatever you want when you create your program. The first IF element, will re-enable after the temp drops.. Best not to make the enable/disable temps equal or too close as you run the risk of too many notifications, that's why I chose >80 and <78. The second and Third will give you reminders if the temp is high sometime after 8AM and 6PM, likewise #4 and #5 will give updates as the temp continues to rise. It should be pointed out that enabling the program won't actually trigger it, but the next time the temp changes after the enable, will trigger a new notification. If you'd like this to work a little differently than shown and can't figure out the changes needed post back and describe and I'll help you work it out.

@jkraus Did you see my detailed steps to follow before the forum ate it? I had a nice long reply with screenshots that I can re-create if needed.

@jkraus How does the ISY know the pool temp... can you screenshot the node, I can give you more info how to get what you want.

I'll add one more important fact. I think the recent change to only using the upgrade button in the admin console is because there are some package updates that got applied too quickly and the UD software wasn't ready for that to happen. I don't know the current state of the instructions in the wiki, they might be lagging being updated.

Login via SSH and type "uname -a" then email the results to support@universal-devices.com and await explicit instructions. You most likely need to run those commands in the wiki, but note that "Polisy OS versions below 13" refers to the FreeBSD version as supplied by uname -a, not "My polisy is running 2.2.13. " It's confusing, therefor I suggest contacting support for the exact instructions needed for your case.

Have you read the wiki page linked two posts up from yours?

@Chris McKean Early Polisy units originally shipped only have PG2 running, and the operating system on those units is older and won't run either PG3 or IoP, nor will it upgrade beyond a certain point in the UI. If you have a unit that old enough that it's NOT showing as an ISY in finder then you will need to contact support to upgrade your Polisy, and they will have you run ssh commands to get there. email support@universal-devices.com if you fall into this category (which it sounds like you do). Once your Polisy shows up in Finder its capable of 3 things.... PG2, PG3 and IoP. PG2 and its node servers are deprecated and not receiving anymore updates. You should update your node servers to the PG3 versions at some point (although at the moment it's not a rush thing that must be accomplished today or this week or even this month. PG2 and PG3 have seperate UI"s and are in fact entirely different processes running on Polisy. Once your Polisy is up-to-date to this point all future Polisy updates are done via the button in the admin console.

You need personalized assistance from support, please open a ticket email: support@universal-devices.com

This will solve that problem. Motion on, program timer off is a great setup especially with multiple motion detectors since off comes X Seconds after the LAST detector saw motion.