dismania Posted January 19, 2017 Posted January 19, 2017 I just moved from an Insteon Hub to the ISY-994i. I did so for more versatility and ease of use. However, I am struggling to create a few scenes. I have a number of fanlinc insteon modules and want to create a scene to use with the 6 button keypads. I thought it could automatically do this for me, but I am struggling trying to figure it out.
larryllix Posted January 19, 2017 Posted January 19, 2017 I just moved from an Insteon Hub to the ISY-994i. I did so for more versatility and ease of use. However, I am struggling to create a few scenes. I have a number of fanlinc insteon modules and want to create a scene to use with the 6 button keypads. I thought it could automatically do this for me, but I am struggling trying to figure it out. Welcome to the UDI forums. - factory reset every device to rid them of existing links - using Admin Console, link each device using it's Insteon address. Battery devices need to be in linking mode. - create a scene in Admin Console in the device tree page/tab - drag and drop each device desired into the scene. ISY will prompt you for some devices if there is a controller capability. - clicking on the scene you should find adjustments for levels and ramp speeds for each device. Do NOT adjust the devices on the next lexical level. That only adjusts their local level settings for when you tap the button on the device itself. Not effective for scene purposes. - click on the On/Off buttons at the page bottom to test. - write programs to operate the scene or use any controller in the scene to operate it. Battery devices will need to be in linking mode to make any scene changes. When done they will time out or be taken out of linking mode manually.
paulbates Posted January 19, 2017 Posted January 19, 2017 Hi, and welcome to the UDI forums! Take a look at the manual, on the manual's page 21. It walks you through it. A few pages of reading, but worth it as the ISY gives a lot of control and flexibility. http://www.universal-devices.com/docs/production/ISY%20User%20Guide%204.2.8.pdf Paul
stusviews Posted January 19, 2017 Posted January 19, 2017 I just moved from an Insteon Hub to the ISY-994i. I did so for more versatility and ease of use. However, I am struggling to create a few scenes. I have a number of fanlinc insteon modules and want to create a scene to use with the 6 button keypads. I thought it could automatically do this for me, but I am struggling trying to figure it out. The reason that the ISY doesn't automatically program the KeypadLinc is that it doesn't know what you want it to do. Some day you may be able to vocally tell an Insteon device what you want it to do Currently you can only tell an Insteon device to do what you already programmed/linked to the devices to do.
dismania Posted January 19, 2017 Author Posted January 19, 2017 Can anyone share their config for a fan controlled by a keypad? I was able to get the on/off to work, but am struggling with the rest. I assume I want a scene for Fan high, fan medium, fan low and fan off. How do I make it so when you switch from let's say Fan high to Fan low, it turn the led off for high? This seemed a little easier with the Insteon hub, but I am excited with the possibilities the isy will give me. Thanks again!
oberkc Posted January 19, 2017 Posted January 19, 2017 If others dont get to it first, i will respond when on a real keyboard later today. In the mean time, I ask that you describe specifically WHAT you desire to accomplish before offering a solution regarding HOW to accomplish. Four buttons, one each for hogh, med, low, off? Do you want the button illuminated when off? What do you want to happen, if anything, when one presses a button that is already on? Are lights involved? What buttons do you want assigned the task of controlling lights? Details like that can drive a solution.
dismania Posted January 19, 2017 Author Posted January 19, 2017 Ok, sorry for leaving out details. I am looking for the following. Top and bottom button to be on/off. Light on the keypad on when activated. (This is currently working as I need it to) Button A will be fan high Button B will be fan medium Button C will be fan low Button D will be fan off I would like only the selected mode button to be illuminated. So, if I am on fan high, button A light is on. If I switch to fan medium, I want button B to light and button A to go off. Hopefully this makes sense.
Bumbershoot Posted January 19, 2017 Posted January 19, 2017 Here's a link that might be helpful: http://forum.universal-devices.com/topic/10415-programming-a-fanlinc-and-keypadlinc/ I have a light on this fan, so my configuration might be a little different than yours. Also, I'm running firmware version 5.0.8, so the screenshots might differ from what you see in your Admin Console. This is hard to describe, so see the screenshots attached. You might get an idea of what works for me. In short, I have two devices: FanLinc KeypadLinc Dimmer (this shows up a five button device in the Admin Console). and five scenes controlling the light and all the fan speeds: Light On/Brighten Off/Dim Fan Off Fan Low Fan Med Fan High You have to create a scene for each fan speed button (making it a controller) that includes the fan motor set to the appropriate speed and the other fan speed control buttons as responders (there's a screenshot showing scene membership for the Fan High scene). Set the Button Toggle Modes appropriately, as well as the Led Brightness values for each button.
dismania Posted January 19, 2017 Author Posted January 19, 2017 I think I have it now. I will find out when I get home tonight. I was programming it from work. Seems simple enough. Thanks for all the advice and guidance.
stusviews Posted January 19, 2017 Posted January 19, 2017 If A, B, and C are fan speed and D is Off. then set A, B, and C to non-toggle On and D to non-Toggle Off and create four scenes as follows: A on (high), B, C and D off B on (medium), A, C and D off C on (low), A, B and D off A, B, C and D off (D is off)
TrojanHorse Posted January 19, 2017 Posted January 19, 2017 If A, B, and C are fan speed and D is Off. then set A, B, and C to non-toggle On and D to non-Toggle Off and create four scenes as follows: A on (high), B, C and D off B on (medium), A, C and D off C on (low), A, B and D off A, B, C and D off (D is off) Once you've created these scenes, you can decide if you want to include the fan motor in the scene at the appropriate speed, or if you want the keypad to trigger an ISY program to change the fan speed. Pick your poison. I chose the latter in order to avoid the fast on / fast off behavior that results when the KPL button is held or double pressed. This can lead to, for example, holding the off button and getting the fan to turn on high speed. I've chosen to live with the 1 second delay introduced by the ISY program but my family and guests always get the expected behavior if they can just wait 1 second... Note, this is my only exception to using native insteon scenes throughout my installation as generally that is the way to do things. Sent from my iPhone using Tapatalk
oberkc Posted January 19, 2017 Posted January 19, 2017 To follow-up with stusviews recommendations, setting button D to non-toggle OFF will result in that button being non-illuminated at all times. Is this what you want? Note, too, that this CAN be done with a single scene, but this is effective if your plans are only to control the fan via the keypad. If you intend to use programs or phone apps or the admin console for control, separate scenes will likely work better.
dismania Posted January 20, 2017 Author Posted January 20, 2017 Well, I got close today. My issues are as follows: When I use Alexa to call the following scenes: Turn light off turn fan off I do not get the desired result on the corresponding keypad. When I turn the light off, the ON light (top button of 6 button keypad) stays lit, I want the bottom button to illuminate showing it is off, When I turn the fan off, the corresponding speed that the fan was set at goes off, but the button I want to be fan off (button A) ford not illuminate. It seems like I want buttons to be both a controller and responder for the scene, but it seems I can only choose one or the other. What am I missing? -Kevin
oberkc Posted January 20, 2017 Posted January 20, 2017 I am not a user of the ISY portal, or of the echo to control lighting. Given this, I am willing to take a guess that somehow you alexa is somehow responding to your commands by controlling individual devices rather than scenes (how is "light" and "fan" defined in your alexa skill?) . I am unsure as to the limits of the echo skills with the ISY, and whether scenes are part of them. If scenes are not one of the available skills, I believe you could create a couple of programs that turn on/off the fan scenes, and use alexa to trigger those programs. Hopefully this is a good enough guess that you can figure it out. Otherwise, another person will have to take a more learned guess at this one. It seems like I want buttons to be both a controller and responder for the scene, but it seems I can only choose one or the other. With the ISY, unlike the hub, devices defined as "controller" are, by definition, also responders. A device cannot be only a controller with the ISY scene construct.
Bumbershoot Posted January 20, 2017 Posted January 20, 2017 Well, I got close today. My issues are as follows: When I use Alexa to call the following scenes: Turn light off turn fan off I do not get the desired result on the corresponding keypad. When I turn the light off, the ON light (top button of 6 button keypad) stays lit, I want the bottom button to illuminate showing it is off, When I turn the fan off, the corresponding speed that the fan was set at goes off, but the button I want to be fan off (button A) ford not illuminate. It seems like I want buttons to be both a controller and responder for the scene, but it seems I can only choose one or the other. What am I missing? -Kevin If you created scenes as described above, then use them instead of the devices to control fan/lights with Alexa. The KeypadLinc buttons should light up correspondingly. It's a bit complicated for the fan, though. You'll have to have a separate spoken for the "Fan Off" scene to get the corresponding "Off" button to light. Example: turning on the "Fan Low" scene will light the "Low" button on the KeypadLinc, but turning off the "Fan Low" scene will not light the "Off" button, it will just turn off the "Low" button light. You'll have to run the "Fan Off" scene to get the "Off" button to light. This can get ugly, as in: "Alexa, turn on fan off"!
dismania Posted January 20, 2017 Author Posted January 20, 2017 Still having problems. I do have a fan off scene, but it does not seem to turn the right button on my keypadlinc keypad on. . It is a bit confusing. Also still having a problem with my light on the fan. I have a scene with the top button on the Fan as my controller. When I tell Alexa to turn the fan on, she does and lights the top light, just like when I press the button. When I say Alexa turn the light off, she does it, but the "ON" light stays on and the "Off" light on the bottom of the keypad linc does not come on. I only have scenes created to link the keypad to the fan, no devices for this. I have to be missing something simple, but I have tried everything I can think of. It is not a show stopper, but it would be nice if it worked the way I would like/think it should work. --Kevin
Bumbershoot Posted January 20, 2017 Posted January 20, 2017 Still having problems. I do have a fan off scene, but it does not seem to turn the right button on my keypadlinc keypad on. . It is a bit confusing. Also still having a problem with my light on the fan. I have a scene with the top button on the Fan as my controller. When I tell Alexa to turn the fan on, she does and lights the top light, just like when I press the button. When I say Alexa turn the light off, she does it, but the "ON" light stays on and the "Off" light on the bottom of the keypad linc does not come on. I only have scenes created to link the keypad to the fan, no devices for this. I have to be missing something simple, but I have tried everything I can think of. It is not a show stopper, but it would be nice if it worked the way I would like/think it should work. --Kevin I'll bet that Alexa is actually turning off the "on" scene, instead of turning on the "off" scene. Try to give the "off" scene an unrelated spoken name (such as, "chair" for example). Discover devices, then say, "Alexa, turn on chair". If that works, then that's your problem.
stusviews Posted January 20, 2017 Posted January 20, 2017 If you added the FanLinc fan mode to the ISY, then your scenes will not run properly if you use you voice to the the fan on or off. I added the four scenes and gave them the following spokens: fan to high fan to medium fan to low fan That way I can specify each speed with natural language. "Alexa, turn on the fan to medium," for example. "Fan" is the spoken for the off scene, not the FanLinc.
dismania Posted January 20, 2017 Author Posted January 20, 2017 My biggest problem is that I have 4 different fanlinc modules in my house. I am having an isse on how to really name them that makes them usable with alexa. Short names are difficult as I want the name of the room involved. I will keep plugging away at it. So far I am really impressed by the reliability and speed of the ISY.
Bumbershoot Posted January 20, 2017 Posted January 20, 2017 My biggest problem is that I have 4 different fanlinc modules in my house. I am having an isse on how to really name them that makes them usable with alexa. Short names are difficult as I want the name of the room involved. I will keep plugging away at it. So far I am really impressed by the reliability and speed of the ISY. One solution, if you have multiple Echos and the fans are in multiple rooms would be to use sub accounts.
stusviews Posted January 20, 2017 Posted January 20, 2017 That's one reason I have several portal accounts. You can have up to five (free) accounts for each portal subscription.
jlloyd_UD Posted December 23, 2017 Posted December 23, 2017 "That's one reason I have several portal accounts. You can have up to five (free) accounts for each portal subscription." I am having some difficulty establishing consistent "spokens" for scenes defined for my fanlinc motor speeds. I have struck on some strange combinations that I have not even defined that get my different speeds to work but I have no understanding why as no where are the combinations defined. I'll continue to puzzle through that matter before I request some additional help. In the meantime I am ready to install another fanlinc in a fan in an adjacent room. I'd be interested in knowing what another (free) account (a subaccount) could allow me to do as I have a portal subscription. I see where I have a "main account" and where I can add an account. Is that what I do to set up a sub account? Add an account and it is identified as a sub account? Should I add two sub accounts and set up my devices and scenes in the sub accounts? What would cause me to choose separating scenes into separate accounts? I see where more than one Echo might demand a sub account. Or, stated differently, are there other instances like fanlincs because of their naming syntax complexities where I should consider separate sub accounts? What is the best tutorial available on this matter of sub-accounts? Is it the wiki https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration#Instructions_for_Alexa_Skill ? I see there is a list of syntax that should be used in that wiki. I'll have to study that some.
stusviews Posted December 24, 2017 Posted December 24, 2017 Instructions for using Multiple Echos Smart Home. I use multiple accounts so that I can use identical spokens to control the same type of device in multiple rooms. For example, asking Alexa to turn on the light in the living room turns on the living room light. Using the same command in the bedroom affects only the bedroom light. An important consideration is whether the Echo devices are within earshot of each other. If they are, then multiple accounts won't work. Instead, give each Echo a different wake word. Our bedroom and living room are the rooms most used and are at opposite ends of the house, so we use the same wake word for each, in this case, "Alexa." But our dining room and kitchen are adjacent, so each Echo uses a different wake word. It can get confusing at times, but anyone with more than one child or more than one pet has experienced that You may also want to consider different wake words in place of different accounts. I use a combination of both.
jlloyd_UD Posted December 24, 2017 Posted December 24, 2017 Thanks. I understand what you are describing as uses for accounts or alternate wake words for separate echos. Makes sense.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.