-
Posts
5609 -
Joined
-
Last visited
Everything posted by paulbates
-
Device Membership Does Not Work in Administrative Console?
paulbates replied to Ed Sybesma's topic in UD Portal
Ed To Brian's point, its best to pick groups of devices (e.g. rooms or functions), delete them from the ISY if they're currently added, factory reset and re-add thedevices. You can use linking mode as you listed and remove existing link. The devices will then appear in the main tab of the ISY. To add link the devices in a scene, use the New Insteon Scene option in the Linking menu and name it something meaningful. Then use the mouse to drag and drop scene members into the new scene. If the device should be a controller too -- turning all the related devices on and off, then check the controller box before proceeding. It could take up to a couple of minutes for the ISY to link all the devices. Repeat that process one room or function at a time, verifying everything works as intended before moving on. Remember wireless devices like motion sensors need to be put in linking mode before dragging into the scene Paul -
Device Membership Does Not Work in Administrative Console?
paulbates replied to Ed Sybesma's topic in UD Portal
When using the ISY, the links/scenes need to be created with the ISY. The ISY will not be aware of Insteon links created previously “device to device”. If you didn’t create links and scenes with the ISY, you should factory reset them and recreate with the ISY Sent from my iPhone using Tapatalk -
Did you have a DYNDNS type address to your house and the router at the vacation home have an external port routed to the ISY? You should be able to do that again, sans portal and complete the step... then use the portal from then on out. If you press Add when the finder pops up you should be able to add it again. If you use the new ISY launcher, it will pause so you can try to re enter the remote access info again Paul
-
I don't believe you can. You have to use the Configuration / Portals tab one-time to establish the relationship. If you don't have access to the ISY, that won't be possible. Nobody with access to the vacation home in that area to talk it through with? Paul
-
Hi, Welcome to the UDI Forums! Unfortunately no. If you have linked devices in a scene, Fast On is part of the Insteon protocol. If its causing problem with a responder, you can partially get around it by not creating scenes between a switch and its linked responder and write an ISY program that sees that the switch was turned on and then turns on the responder. That would stop the fast on from affecting the responder. Unfortunately the switch being turned on will still show an "on" state when double tapped. You could have a program look for the fast on from the switch and turn it back off. Paul
- 1 reply
-
- 2
-
-
If you're linking scenes members to remotelinc buttons (or removing them), you'll need to put the remotelinc in linking mode first, meaning you'll have to have physical access to it. You will not have to "link a remotelinc" each time, just make sure the remotelinc is in linking mode (press and hold the set button until it beeps). Then drag things into (or out of) the scene. If you are only modifying programs that use the remotelinc buttons that have the scenes created, no. Paul Edit. From your previous post, the barn part should work as well.. if its working don't worry about it. The rf remotelinc will communicate through a dualband device and repeated over the powerline if that's the available route. 150 ft is a long way for RF, but not necessarily powerline. If the signals are getting their reliably that's not uncommon.
-
I've gone through this insanity as well. I like the Lutron Claro screwless. Usually Home Depot has them. They also make blanks that will fill unused. Get a 4 gang cover and 2 blanks and fill in however you'd like. Some good info here too. Paul
-
Hey Pat Getting them all on 100% is easy, create a scene, include all of the lights as responders and set them to 100%. To turn them all on, make the switch you want to activate them a controller in for the scene, and turn it on Its potentially a little trickier going back. Are the lights all at certain levels at certain/different time periods? Or, could they be at random levels because the occupants turned them on or off independently? If its 1, it could be accomplished with a few programs and scenes by creating individual scenes for each time period, writing programs that respond to the light being turned on and being in that time period .... then counting down and then turning the specific scene for that time on If its 2, I agree with Oberkc that I'm not aware of a resume insteon feature Paul
-
? This is one of the daily doorbusters just for 11/22. But to your point, it wouldn't be the first time I've played the "I've been an insteon customer since back in aught 7" ... and gotten away with it ?? Paul
-
Thanks for pointing that out, I scrolled right by. On the fence.. I have 7 of the original bigger white single band dimmer modules for lamps and Christmas lights, and this is a 7 pack.. They've passed their 10th birthday and continue to work perfectly and are behind furniture where they don't get noticed. Decide tomorrow I guess.
-
This gives the look ahead at what the "door busters" will be. Its all multipacks, a good opportunity if you have a lot to install https://www.smarthome.com/black-friday-daily-doorbuster#dailydeals
-
The long press will not have consistent behavior. For instance, let's assume the switch is off, and the default local on level is 80%. When you "long press" the switch on, it will climb to 100%, and then stop sending fast ons. Similar for dimming to off. You can experiment with this by linking a lamplinc to a key and watching the behavior. My point is that smarhome designed long press to support dimmer operation, not discrete remote control by a program. Paul
-
While the "long press" is technically feasible, it would mean capturing fade up and fade down messages. That's what a long press means to an Insteon switch, brighten or dim linked controllers when long pressing. That would get tricky as fade up and fade down alternate... The switches assume the first press is fade up and the following press is fade down. It will be more predictable to use the key double tap, aka "Fast On". Your program can use this logic for that: If 'keypad key' is switched Fast On Then stuff That will respond directly to a double tap when the switch is currently off. Or Fast off if the switch is on... that will reliably capture the "double press" behavior from the kepad key. Paul
-
The only other thing I can think of, other than than the other suggestion above, is to right click on the keypad in main and pick restore device. When that completes, repeat those steps with the garage switchlinc, and test again. Kind of a long shot, but easy enough to try Paul
-
Hey Joe, It sounds like communication problems, potentially even the load controlled by the garage switchlinc is creating noise.. and after its turned on the noise from the load makes it difficult for the switchlinc to "hear" the off command. Since its intermittent, i think that may be it. I would try the following: What type of load is the garage lights? (LED, Florescent, ect) Remove the load if you can and retry the test. If it works consistently without the load, it is load noise... replace the lights or filter You might be able to get around it this way: Right-Click on the keypad in the Main device tree. (It doesn't matter which of the keys you pick). Pick Advanced from the pop-up menu and PLM communications. Assuming its a newer keypad, you'll see something like what's in the picture. For the key in question, change the value to 3 retries. This may provide some relief but its kind of the "Hulk, Smash!" solution. There will likely be a delay between pressing the key and the lights. If this works, you'll still want to try and solve the signal problem. (Even though it says PLM communications, I've gotten this to work on noisy lights as well when I didn't have another choice) Paul
-
When you're accessing the ISY remotely through the portal using the admin console, it can be affected by the speed of the internet service to the property. I'm not sure how mobilinc works, but the Admin Console has to down load all of the devices initially, and their statuses. That can take time. I have had similar experiences at hotels with marginal internet service, and for grins and giggles I tried the AC on gogo on a plane. Sometimes, it takes a while. Typically ISPs allocate more bandwidth (=speed) to downloads than uploads. This can be a problem for remote use of the Admin console. One thing to try is to just let the admin console sit for a few minutes after starting it to get everything loaded. Most likely you'll be ok. Paul
-
Ben I use the ios Locative app, configured with the link provided in the portal Paul
-
Yes, I have something very similar DrivingInGolfview - [ID 0041][Parent 0040] If From Sunset - 15 minutes To Sunrise + 15 minutes (next day) And 'Paul's iPhone / Paul's iPhone Home' Occupied is True Then Set 'Yard / Premise Lights / Floodlights On' On $Occupied = 1 $Occupied Init To 1 Set 'HVAC / Family Room' Home / Away Home Else - No Actions - (To add one, press 'Action') Iphone location from locative to turn on floodlights and kitchen table light when pulling in the neighborhood via ISY portal
-
That shows the first 3 to 20% and the last to 50%, all around 19 second ramp rate. Is that what you were expecting, and its doing something else? ...or? Paul
-
If you have windows 10, use the snipping tool to copy an image of the admin console and paste it in a response window here.
-
Can you post a pic of the scene that includes the linked devices? Paul
-
Cool, glad everything worked out Paul
-
Hey Yes I know the ganging thing is a bit unusual. You can read about it on page 17 of the switchlinc dimmer manual under Mounting: "Mounts in single or multiple-ganged wall box. Control 200W less load for each immediately adjacent SwitchLinc Dimmer installed. For example, 600 W load control becomes 400 W with another dimmer to the immediate right or left. Use a triplegang box with a mechanical switch in the center to avoid derating." It could be that your loads are lower like LEDs, or if you area not controlling a load with the switch, it won't be affected. I think if you were going to have a problem with it you'd have notices, and you'd have hot switches and buzzing / noise. Switchlincs are just the product name of insteon dimmer and relay wall switches. Paul
-
Yes, but the load control is set to the A button for an 8 button or the On/Off (Top / bottom) of a 6 button. You can't make the load controlled directly by the other buttons. Another installation point to consider. While you're already potentially experiencing this, multi ganging dimmers, even keypad dimmer, reduces their load potential by almost 50%. A dimmer ganged between 2 other dimmers will have very low load potential. If you notice the switches getting very warm or buzzing noticeably a few feet away from the box, its likely a problem. However, since it sounds like you're reducing the # switches, it likely reduces this problem. Try to gang dimmers away from other dimmers.. eg, switchlinc relay in the middle. Yes, absolutely. I'm set up that way. Create a New INSTEON Scene under Link management. Add the switch participants as controllers to the scene (assuming they can be physically controlled by the occupants). Yes, the ISY can track the status of any of them and/or control them. Create the scene, and drag each switch in with the mouse. Click Controller/Responder checkbox. When you use the ISY to control the lights... turn the Scene on and off, not the individual lights. That will turn them on and off in unison. For instance I have a switchlinc at the bottom of my stairway to the second floor, and 6 button keypad at the top. The switchlinc controls the load. The on/off button of the keypad can turn the stair lights on/off too. Both are linked as controllers/responders to a scene. I have a 7 minute timer that sees that the lights were turned on, then dims them after 6 minutes, and then turns them off by using the scene. I did this because these lights are chronically left on, even though everyone is just passing through. This has worked out well.. no complaints, and the lights do not stay on all of the time. Hope this helps Paul
-
The ISY has 2 functions with Insteon: Controller and automation using ISY programs. Insteon network manager. While this function supports 1., its separate. By using the Link Management menu, Insteon devices are found, added to the ISY and scenes programmed into the devices remotely, rather that using manual linking between devices as described in the directions provided with the device. In the ISY Link management menu, pick "New INSTEON Scene" to manage all links on all of your devices If you choose to manually link devices.. you can, but the ISY will not have any knowledge of that and can't participate. Its much better to let the ISY set it up using scenes and features for the irlinc. There are also specific features for the irlinc that UDI has added to the ISY. See the pic below The short answer is that the ISY does not activate the irlinc scenes. As network manager, the ISY programs the links from the irlinc to the insteon network up front when you add the irlinc and its buttons. This one time and the ISY is done at this point. You don't need the ISY or PLM after this setup is done. Both could fail and this will keep working. You can use ISY to enhance events via programs if that helps. I know this sounds like a pain, but my suggestion is that you: Scroll down on this page and read how the ISY supports the IRlinc Write down the remote / button logic of what you have today in the GC/irlinc. Delete the IRlinc from the ISY, if its in the ISY Factory reset the irlinc Add the IRlinc back into the ISY using the linking menu Add the buttons back in using the linking menu features in the picture Paul