dbwarner5

@ISY Newbie Bottom line, there is a TON of ways to automate your life. You will need to decide the balance of complexity of setup / programming vs how much you want to exactly meet every situation. By reading all of the posts and accepting your newbie experience, I would suggest simplifying and growing as follows: -Use the MS to initially turn on the lights upon entering. -Add a 6 button keypad to a light switch somewhere handy. -upon entering, decide which "scene" you want from the keypad, and press that button. -This would then initiate a series of programs: 1)disable the MS until either a certain time expires ie 3 hours, or the main light switch is turned on again 2) depending on which button was pressed, adjust the lighting scene inside the room for the way you want it... movies probably darker than sports etc. 3) program that resets everything when the main light switch is turned on with a slow brighten affect. this is a pretty simple and straitforward approach that gives you a pretty good start for what you are looking to do....control the lights in your movie room. Or you can achieve all of the above without a keypad by using an Alexa and simple voice commands as the initiator vs the keypad (my preferred route) you can always grow from here with polyglot, node servers, multiple MS, door sensors etc... but that starts to get pretty involved if you haven't mastered the basics of isy programming such as I have explained above. If you choose to do something simple like this, feel free to reach out and I can explain in more detail if you need it. good luck and WELCOME to the ISY.. you won't ever look back once you get the hang of it...

@Michel Kohanim I have submitted a ticket. In trying to get the IP address changed so that the dashboard would work, the polyisy is now nowhere to be found on my network. Pushing the reset button does NOT create any beeps fyi.

Larry. Lol. And that is only the tip of the iceberg.... Sent from my iPhone using Tapatalk

bob.. go to universals devices website and you can see the ISY... there is definitely a learning curve with it, but it is well worth it if you would like to really control things, both automatically, and via Alexa or your phone etc. For example, I have three garage doors. I have programs that if any of the garage doors are open, several keypad buttons light up around the house. If after dark, they will start to blink to attract my attention. I can then either press any of them, or ask Alexa to "close the garage doors". The Isy will then determine which doors are open, blink lights in the garage as a warning, then make two attempts to close them. If any of them fail to close after 2 attempts, then the house announces the problem (could be through Alexa) that one of the doors is still open. If they all close successfully, the same keypad lights will blink slowly and an announcement will be made if my rear access door is also left open (often done in the summertime). Meanwhile, I can at anytime, open or close any of the doors simply by asking Alexa ("Alexa, open the north garage door") or pushing a "dashboard" button on my cell phone mobillinc app. All very easy. The point is, that with ISY, there really is no limit to what you can do; it just takes time, patience and a little experimenting to figure it all out. This forum is an excellent resource, but at times, some of the answers you may get may be a bit more complicated than often is needed for a beginner, so just keep asking.

I did not use a secondary z-wave controller when I updated from 4 to 5. But did do a z-wave backup before and a restore after. No problems. Sent from my iPhone using Tapatalk

yes glowing hair.. easy enough to do, but you still need to check once in a while, and having the LD is a really quick way to scan down your program list to see if if indeed they are set they way you intend them. Will do your suggestion in conjunction! thanks.

Have been waiting for less trouble and finally updated last week from 4.7.3 to 5.16a.... followed hart2hart's check list below. Upgrade went flawlessly with exception of leak sensors. Just upgrades to 5.16b. Again no issues. Waiting 24 hours for heartbeat to know for sure. One additional tip / idea to the list below: - I have historically had issues with certain programs that should be disabled, becoming enabled due to power outages etc. and have always had a challenge going through my hundreds of programs to sort them out. -So a while ago, I adopted the nomenclature rule for my system where if a program is meant to be disabled, then I end the name of the program with LD for Leave Disabled. See below for an example -This is a one time effort to rename, but it made it super easy during the upgrade to reset everything as it should be w/o the need to compare two lists as recommended by hart2hart Thanks UDI and everyone who actively contributes to this forum.... you all are great! Merry Christmas.

Hi Wes, I am long time Mobilelinc customer, and currently have HD set up on several devices. I also use the ISY portal. What is the advantage of switching to X? Currently I don't have any issues with HD. All is working just fine. thanks. Doug

DualBandAid and others.......Update to efforts above: Success but with some trials and learnings about the Phillips bulbs 1) for some reason my Hub user name would not appear no matter what combination / effort i made. When I was about to give up, i tried it in a new browser window exactly as in the directions and voila, it worked.. don't know why. 2) found i couldn't get the lights to the right color. It appears i have two downward bulb that use an additional or in place of(?) parameter of "xy" for the color. Once I added that to my resource body, the color changed correctly. -New Resource looks like this: {"on":true, "bri":39, "sat":65202, "hue":254, "xy": [0.6817,0.3036], "transitiontime":5} After running the above resource via TEST, the GET command from debugger shows the following and the light shows the right color. Interesting to note that the numbers don't match exactly. "state": { "on": true, "bri": 39, "hue": 65203, "sat": 254, "effect": "none", "xy": [ 0.6818, 0.3036 ], "ct": 153, "alert": "select", "colormode": "xy", "mode": "homeautomation", "reachable": true }, Notice it says in the GET --> "colormode": "xy". The Does anyone know what "ct" is? On a different bulb, the GET info says "color mode": "hs", which i assume means Hue, Saturation and therefore the original directions would have worked. This may be worth an add to the original directions. For those interested, here is the rest of the GET info from first bulb: "swupdate": { "state": "noupdates", "lastinstall": "2018-12-07T19:04:07" }, "type": "Extended color light", "name": "Dougs reading light", "modelid": "LCT011", "manufacturername": "Philips", "productname": "Hue color downlight", "capabilities": { "certified": true, "control": { "mindimlevel": 2000, "maxlumen": 650, "colorgamuttype": "C", "colorgamut": [ [ 0.6915, 0.3083 ], [ 0.17, 0.7 ], [ 0.1532, 0.0475 ] ], "ct": { "min": 153, "max": 500 } }, "streaming": { "renderer": true, "proxy": true } }, "config": { "archetype": "floodbulb", "function": "mixed", "direction": "downwards", "startup": { "mode": "safety", "configured": true } }, "uniqueid": "00:17:88:01:02:aa:ba:5f-0b", "swversion": "1.46.13_r26312", "swconfigid": "E6785CC3", "productid": "Philips-LCT011-1-BR30ECLv1" Here is the complete GET Info from a standard Phillips bulb where the colormode is "hs". and where the original directions in this forum work. { "state": { "on": true, "bri": 254, "hue": 255, "sat": 254, "effect": "none", "xy": [ 0.6863, 0.3122 ], "ct": 153, "alert": "none", "colormode": "hs", "mode": "homeautomation", "reachable": true }, "swupdate": { "state": "noupdates", "lastinstall": "2018-12-07T19:04:12" }, "type": "Extended color light", "name": "Great room lamp", "modelid": "LCT016", "manufacturername": "Philips", "productname": "Hue color lamp", "capabilities": { "certified": true, "control": { "mindimlevel": 1000, "maxlumen": 800, "colorgamuttype": "C", "colorgamut": [ [ 0.6915, 0.3083 ], [ 0.17, 0.7 ], [ 0.1532, 0.0475 ] ], "ct": { "min": 153, "max": 500 } }, "streaming": { "renderer": true, "proxy": true } }, "config": { "archetype": "sultanbulb", "function": "mixed", "direction": "omnidirectional", "startup": { "mode": "safety", "configured": true } }, "uniqueid": "00:17:88:01:03:b3:76:d6-0b", "swversion": "1.46.13_r26312", "swconfigid": "9DC82D22", "productid": "Philips-LCT016-1-A19ECLv5" TH' or ANKS EVERYONE! 'hs **UPDATE: It seems that for the regular bulbs, the method of color choice, "hs" or "xy", changes depending on what ios app or Alexa I last used to adjust the light.One of the apps I use has animations. These seem to put all the bulbs into "xy" mode. So the simple solution is to ensure both data is included in each resource so that when ISY invokes it, the color is correct in either case of which the bulb reads the data.

DualBandAid…… this is amazing. I have had the network module for over 4 years and have not had the time/guts/energy to figure it out. I see now that I will be able to do so and using this as a stepping ground to learn to do other things like control my russound. In the meantime, for those that like me are a bit intimidated by NR, with the new features that ISY has with Alexa, there is a simple way to do basic things, albeit it can get a bit convoluted with programs / routines calling each other from different systems--> ISY program calling on an Alexa routine which then calls the Hue Hub to change lights. -Use a variable from ISY to initiate a routine in Alexa per this wiki page: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3 -This variable can be integrated into any ISY programming / logic desired. -The Alexa routine can set most basic parameters of the HUE light or rooms etc. Thanks to everyone who has contributed to this topic. I just installed 5 hue lights yesterday and will look forward to tackling NR next. but in the meantime

On to p of things as usual! thanks Michel.

thanks! it wouldnt hurt to add a note to that affect in the Wiki. https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3#ISY_Can_Talk_To_You.21_.28Alexa_Routines.29

First off, using Alexa has been the missing link to make my ISY/ Elk installation useful for EVERYONE in the house.. GREAT JOB UNIVERSAL DEVICES.. works really well. Cant wait to start integrating voice responses per the newer capability. Simple question: I have both of the above skills enabled on my Alexa account. Nowhere do I find much about the ISY app VS. the ISY Optimized for Samrt Home V3 app.. Do I still need the ISY one? Is it redundant and possibly causing conflicts? If anyone could clarify that would be great! Thanks!

Hi Sanders.. a somewhat "unrelated" question for you... i have an ELK / ISY system as well, plus a Russound MCA88-8. I have the Network Resources module installed in my ISY with the hopes of integrating my ISY with the Russound for wake up music etc. I noticed you mentioned the Russound Serial interface. Can you help me get started in my goal above in terms of how do i start using the networking resources and how do i set up a serial interface? I have downloaded the MC66 serial commands and binary codes but am not sure what to do with them. also, my inputs to the MCA88 are Apple Expresses and Apple TV's so I am looking for some sort of input that i can queue up to play in the morning through the ISY interface to play what i want in the morning, but can't think of anything yet. Any suggestions here? thanks!

David... FYI, i had the same thing happen but it was the MED setting on the fanlinc that went bad.... very frustrating to trouble shoot.. luckily i had another fanlinc that i hadn't installed yet so i swapped them out and proved it was the fan linc not my programming... thanks!

Thanks Bambamf16... I am not sure i understand what you said... but it worked like a charm! thanks..

Thanks Stu. As I mentioned each scene is properly set up. If I go to the scene in the admin console and press on or off it behaves 100% correctly in each case. But when I press the keypad button I get very different results. All three buttons will light up and the fan goes to high regardless of which button I press Any other thoughts? This is a "new" install. I have had a system for the last 4-5 years but took it down for the last year while we rebuilt our house. Starting fresh and don't have any other switches installed yet so may just reset everything including the plm to factory settings and see if that clears things

I have just installed two fanlincs with 6 button keypads. I created 3 scenes for each one as follows: 1) Fan on High: -Keypad a, Responder: set to zero -Kepyad b Responder: set to zero -Keypad c Controller: set to 100 -Fanlinc Fan Responder: set to High 2)Fan on Med: -Keypad a, Responder: set to zero -Keypad b, Controller: set to 100 -Keypad c, Responder: set to zero -Fanlinc Fan, Responder set to Med 3)Fan on Low: -Keypad a, Controller: set to 100 -Keypad b, Responder: set to zero -Keypad c, Responder: set to zero -Fanlinc Fan, Responder set to low All scenes work perfectly when I click on or off in that scen on the ISY. However, when i press any of the three buttons on the keypad, all three buttons light up and the fan will run on high. Press any of them a second time and they all turn off and so does the fan.. What is going on here? thanks!

My plan is very similar to this, with the addition to adding an old fashion round mercury thermostat in between the ignitor and the i/olinc output as a safety break if the fireplace were to turn on when i wasn't home and get too hot. This seems the cleanest and cheapest way to accomplish post 12's point and if I ever abandon Insteon, I can easily just replace the levity with an on /off or a thermostat. Any thoughts on this? thanks!

Huddadudda, Thanks for the comments. I am working with a custom AV home theater person who will be running all my cables and installing the base systems. Great choice and you are 100% correct. Will think more about the ipad mount. Our home is just in the early phases of framing. Hardwire decisions will need to be finalized in January. Thanks everyone for the continued feedback!

Thanks everyone for your input. Seems like we are all on very similar tracks. House construction has just recently started. Will be finalizing the hard wiring in probably 2 months time, so everyone's input is greatly appreciated!!

As i read the owners manual for the 2441ZTH, it says: Waterproof Temperature Sensor (2433A3) INSTEON Waterproof Temperature Sensor is an external sensor that wires to your INSTEON Wireless Thermostat. When connected, the thermostat’s LCD display will show the sensor readings in small digits above the thermostat’s temperature. Does this reading show up in the ISY? Or are you somehow overriding the thermostats temp with the external probe feeds? I am looking to attach a probe to the heater element of a hot tub and then monitor its temperature and have alerts etc for out of ranges. Thanks, Doug

Thanks Michel. I think i will go with option 1. Its only 4 folders with 4 programs each and that should work fine by allowing me 15 minute increments between 5am and 845 am.

I am thinking about the best way to use ISY as an alarm clock. The key will be to be able to easily vary and enter the time I want the "wake up" routine to run the next morning. The "wakeup" routine will be just some variation of programming of lights, music, temperature etc. I am looking for any input on the best way to accomplish this. Here are a few options I have come up with. Option 1: Use an 8 button keypadlinc, where the left column of buttons represents fixed hours such as 5am, 6am, 7am, 8am, and the right column represents 15 minute increments of 00, 15, 30, 45. As i go to bed i can press the correct button on each side to choose times in 15 minute increments from 5am to 8:45. The left side would set a Integer variable called Hour of 5, 6, 7 or 8. The right side would set an Integer variable called Minute of 0,15, 30 or 45 The programming would be 4 folders, the first enabled only when Hour = 5, then next 6, then 7 and then 8. Each folder would then have 4 identical programs. In the first folder, the first program is If Minute =0, then run Wake up routine at 5:00, the second If minute =15, run wakeup routine at 5:15 etc. In the morning, a fast on or a fast off of any of the keys (so you don't have to be picky which ones you hit) would enable a snooze of ~10minutes. While a single on or off would signal the ISY that i am awake, but leave on the music / lights etc. If an awake signal is not received after ~ 10 minutes then a "chime" would go off to make sure i got out of bed etc.or what ever wake up routine ends up working the best for our lifestyle. Option 2: Through Mobilinc, I manually set the two integer variables similar to the above situation but with out the use of the keypad. However if the above approach was used in conjunction, it would light the appropriate buttons and operate as above. Another similar option that would bring ultimate flexibility could be accomplished if there is a way to make a variable relate to a time. Is this possible? Some other way of turning it off would also have to be accomplished if the keypad didn't exist and this was the only way to set the alarm. Option 3: Is there some way, in using Network resources, that i could simply send a text message to ISY to tell it the time i want to wake up? A keypad button could light up as acknowledgment etc. Any other ideas? Has anyone set up something like this? The ideal is a) ease of time entry, flexible times c) acknowledgement, d) snooze. Looking forward to hearing everyones thoughts. Thanks!

Blueman: i more add about the garage doors... this may able to be done thru the Elk module in ISY as well, but one thing i like about having the I/O LInc on the garage doors is that i can also use Moblinc IOS app with Geofencing to "know" when i have arrived back at my home and that in combination to a Motion Detector (insteon), it opens the garage doors for me, depending on what trigger i set when i left, and turn on lights inside if needed etc. Works reasonably well, but often has a long delay from when the MD picks me up until it gets processed, other times, immediately.