paulbates

Hi and welcome to the UDI Forums! I think you're on the right track. The plugin (which is great) aside, media device modes and states can be very specific to the equipment. Experimenting will help get you to the right place. For recursion: The ISY is a very simple and fast state machine. It runs one instance of a program. You can call a program from itself, and it will restart. You need to be careful in that the ISY is very unforgiving about "tight loops". If your program calls itself there is the opportunity it will use all of its processor as the program re runs itself over and over again. You'll want to put a wait 10 seconds statement when you first write the program because its tough to stop tight looped programs (right click on the program and pick Stop). Start simple. Also, for status, the program will run when the state changes. So Watch TV will only run when a change in state from true to false happens Paul

An x10 coupler will do the same job Sent from my iPhone using Tapatalk

While its unusual, its pretty straightforward. You need buy a double pole breaker. What's important about that is that the signalinc needs to touch each of the 2 legs. When it does this, the insteon signal passes from one leg to the other, covering the entire electrical system. The double pole break insures that the signallinc gets a hot from each leg, by touching 2 adjacent bus bars on one side. The breaker also protects you when servicing the signalinc. It does not draw much power, that's not the point. http://cache.insteon.com/documentation/2406Hqs-en.pdf I added a 2 gang workbox that screwed in a panel punch out. I installed the signallinc on one side and an outlet on the other. I wired the signalinc as directed and wired the outlet to one of the hots of the double pole breaker along with the singalinc. I use the outlet for the PLM so its signal is right at the panel in the center of the electrical system Paul

Most likely. I've had a signalinc bridge on my electrical panel for a number of years and it made a big difference. You'll need to know how the power is set up for work, number of phases, how many panels, etc. If its a commercial location there are a number of possibilities. Scroll down to the section "Use Powerlinc Modem as a Phase Bridge" Paul

This sounds like insteon signalling problems. Have you been an long term inteon user, meaning you've confirmed bridging the power legs of your electrical system? The "moving around" problem is generally an indicator of the power legs not being bridged. The directions for insteon devices, like the plm, describe the "4 Tap" test for confirming the ability of Insteon devices to communicate with each other. I'd recommend that next. Paul

Welcome to the UDI Forums! Standard network cables should work, however the PLM is using RS-232 signaling, not ET. For the PLM cable, its more a matter of how long the cable is, not the standard RJ45 ET Pinout. There have been stories of 50', but I'd start with something shorter to validate it working, and then try longer lengths Paul

Hi Max In that situation I would factory reset and start again.. Associating the portal, resetting the password and adding modules back in won't take very long. That way, you'll start off your new house with a fresh ISY and V5 FW Paul

I think in the past I've seen threads on those lines but don't have the links. I was pretty sure about how to interpret the heap, but now not so sure. I have ~ 1/10th the number of programs you have and my results are fairly close about the same. Maybe @Michel Kohanim or @Chris Jahn could provide better insight here Paul

Its hard to nail that specifically. The 1000 was a general guideline, not a hard limit for the ISY Pro. Programs can be different sizes.. so its not a hard program # limit but rather when you exhaust memory. That's contributed to by anything you create/configure with the ISY.. programs, variables, network resources, web content, notifications, ISY Modules and Nodeservers (etc.) Another factor is the the number of events driving programs to run could overwhelm the ISY's processor's ability to perform as expected, even if memory is not exceeded. Symptoms would be long start times for the Admin Console, or ISY performance is not what's expected. Here is some info Query your ISY's memory use Use telnet (not SSH) to access your ISY locally. Type SM The first line will look like this, free heap space is what memory you have left: Static = 262144 used, Heap = 1114112 free, Total = 1376256 My sense of danger would kick in if that Heap number was less than 20,000, but maybe Michel or Chris can suggest another number https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card Paul

A common way to do it is Break the project into rooms or functional groups of devices Decide if any programs are still useful and delete the ones that are not (eg same logic but new devices to be added) Do the same for notifications, network resources, variables...eg don't keep "garbage" around As an alternative to the above three steps, factory reset the ISY... again.. if you don't want any of your old programs, etc Then, by room or functional group: Factory reset each device Add the device back in to the ISY Build the scenes necessary to support what you're doing Update programs if you kept any that apply Validate that things are working Move on to the next room / function Paul

Ed That is the only way. You can control scenes with programs but what I described is the only way to create them Any switch that needs to control the 3 way (or N way), has to be configured as a controller. So both switches need to be controllers. You can remove the primary switch by dragging it out of the scene (or single clicking it and pressing delete).. and add it back in and make it a controller. That will fix it. Paul

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

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

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