larryllix

Take the LEDS out of the scenes and use a program, with a Wait 2 seconds in it before operating another scene with the LEDS only in it. I don't believe you can adjust KPL led levels in a scene, only turn them on and off. I am not a scene guy or a KPL guy but I know that KPL s are weird and demand weird controls. Maybe it is your button labels that confuse me but I am on mobile right now and can't view it easily.

Your program will do what it is designed to do regardless of what any other program does. From runs Then To runs Else There are several ways to handle this Manual Override. You can use change your program to call another disabled program with conditions in it. You could write a Manual Override program that temporarily disables your auto-program and then re-enables it when you are done. Probably many other methods but those are the two method I would use. Warning. I always put a failsafe long timer (like 6 hours) in my manual override programs because people get used to lights turning themselves off, and will walk-away from the On light, expecting it to look after itself.

There is something wrong with those scene involving the KPL. KPLs do some weird things with cross button from history here. As an experiment, I would divorce the button LEDs from the scenes and try a program to set just the LEDs with a few second delay for the LEDs. This should separate the button push command signal from the LED signal in time, to avoid Insteon signal clashes. This is providing the factory resets don't make it all go away. The ALL ON I created last month, was involving a KPL using command signals to immediately send back a signal to set a KPL LED on/off. All the KPL functions are considered one device, and that can cause problems, for some reason in the Insteon protocol, when you include two different parts in one operation, apparently. I am grasping at straws here, but there must be a way to sleuth this down to the root cause or bug.

There are plastic boxes that seal out rain better but... Boxes can be mounted on the surface or inside the brick level to the surface. With a flood light fixture mounted on the box you will hardly see the extra 2" of box, if not level mounted in the wall. After that you may notice that many other house already have them.

OK then the pipe and surface mount box I was going to suggest, down the wall is a no go. Wouldn't look good in the bedroom. LOL The module inside the octagon box for the wall fixture would keep it cooler and ladder accessible, for maintenance, if needed.

Are you running above the garage in the attic space? is your run to the attic existing or are you adding it?

This appears that your scenes are interoperating. Scenes are supposed to be individual and not interact. Did you factory reset the KPL especially, and every device, before linking to ISY? Have you factory reset the KPL, especially, but all of them, and restore each from ISY? Have you checked your links in each device and used the automatic compare feature in ISY to identify messed up links?

Thanks. Another day. After finding the iR LEDs wired back to back and the way the thing acted erratically and different so many times, and now it doesn't link at all, I am a little disheartened with it, and so close to the garbage too. I may give up on this route and go buy different AV equipment. Time for some Anynet+ stuff anyway. LOL

I know we get can away with that in certain Industrial installations but not residential.Breakers are not made to switch loads on and off buut they do.

I don't think that is really acceptable, but if there is nothing else on the breaker you don't want shut down...sure. Switches/dimmer and MS sensors always have an air gap feature for safety when changing bulbs. If possible, I would install a switchbox somewhere semi-convenient, and keep all electronics not too inconvenient. You also may want to switch it on/off as you walk past at times. Your PLM could be dying and taking a week to get a new one.

Your OP stated it wasn't working fine. I was attempting to give you a method to help of locate your problem.

You need switch somewhere to change the bulb, not alive, and for when any inline products fail. You can control the light there by paddle or from any Insteon device / ISY in your network.

Stuffing a Wait 5 seconds into your program can help diagnose sources of trouble.

hmmmmm. No, AV gear is inverter backup up and this circuit isn't. It's an extra circuit that runs around the room dodging AV and Network closet gear circuits. LOL A few Hue and MiLight bulbs running on it. I plugged an On/OffLinc into the duplex receptacle at the base of the 10' long extension cord. When I did get it to link (a few times) and ran a test program to test the iR 100 times, the iR flashing pattern and blue linking LED never seemed to miss. So I assume the Insteon signal gets there OK. That may be my next try to take it into another room circuit.

A note about NR hitting on your Hue bridge. You can do variable substitutions in the NR but the substitution is not done until transmit time. If you use a few variables as passed parameters, for your Hue setting NR, and you immediately change the parameters to another value/bulb etc.., There is a good chance you will not transmit the data parameters for the first NR transmit, when it grabs the variables, for substitution, from the variables at the time of Tx not at the time of the NR call. UDI has promised to make this time and option in a later version. Until then, you will need a Wait 1 second between each call, or make a set of variables for each bulb.

There is no syntax conversion. same syntax. Maybe the upgrade conversion corrects a few minor items that you don't see or notice.

Sorry. corrected the step numbers.

Thanks Stu The event log shows ISY getting involved at step 4 as soon as the button is held down to link. Mon 12/05/2016 09:41:58 PM : Stop Insteon Device Linking Mode, Final processing to follow It just doesn't seem to do any ACK to the iRLinc to shut the flashing off as per Step 5. EDIT: Listed step 6 and 7 in error.

It all seems to go OK, until step 5, which never happens. I allowed about 15 minutes, one trial, and it just seemed to time out, and the LED stopped blinking. No linking data was received after on the same trial. On step 7 I click OK and nothing happens. It did work a few times, when I first got the unit with the bad iR cable, but now I can't make it work at all. Step 1 sometimes doesn't go into linking mode and wont blink. It takes many tries at double taps to make it work sometimes. Not ISY related but...I have discovered the recording of the iR code has no intelligence. Other smart remotes, I have experienced, want many repeats of the code sample to ensure they have it correct via repeat verification and then extract one good pattern of the code for sending. This unit records and iR sends as many repetitions as you hold the button down for while recording. This can take a lot of time if the pattern is not kept short while recording. Here is a level 3 Event log from factory reset (first line) to giving up at step 7 and tapping again to stop the flashing link LED. ISY-Events-Log.v5.0.7__Mon 2016.12.05 09.43.24 PM.txt The iRLinc IP address is 33.54.2A. I don't see that appearing in the event logs but lots of another address. 27.1B.85 which is a KPL in another room.

Welcome to the forum! I am not really sure what is happenning but I will try to relate some information to inprove your ideas, maybe. Scenes do not rely on ISY at all. ISY is a very good scene link manager to make it easy to set up scenes and have them download into your devices. scenes can be done the old fashion way without iSY by doing tap sequences and putting devices into linking modes. If you have a scene (link between two devices) whether done with ISy's help or not, It is already sending the codes between devices. If try to compete with this process you may get the effects you disclosed. I like using all programs in ISY to do things except for MS with lights where I use a scene to turn it on really fast and a program to turn it off when it gets around to it and no rush. I also use scenes for every device in the house whre I would use it for a blinking house effect / alarm. You situation sounds like you have a scene turning your light on and a program that tries to do it at the same tie. This may also cause some Insteon data storms to slow things down when so many commands are shoved into the tiny Intseon data tube.

Now I can delete a dozen test programs and a couple of test scenes. Then we wonder how we get bad links in devices. LOL

See my previous admission! I am so glad this was workable in v4.x for you. Yes I was using the scene, as you persisted and got caught doing the opposite of my own preachings from a year ago. Sorry to have eaten your time on this. I goofed up twice here, badly. I use this technique for dula device scenes but never one. With v5, I don't need it though.

Bingo! You hit the nail on the head. I was selcting my scene contrary to what I was tooting to everybody else a year ago Son of a b... I got caught on my own stuff. grrr... At this point, totally embarrassed, I have to thank you, carealtor for being so stubburn and persisting with my education. I was always informed you could do this. Thanks!!! A also have to thank zerop for posting the idea in the first place. I didn't know you could do this with one device in a scene. It totally does make sense, user wise but again I was misinformed a device couldn't do this. Thanks so much! Stu. Thank you also for being so persistent in my education. After all that I realise I don't need the technique with v5 as the On level and ramping are settable without scenes. probably doing the exact same codes behind the scenes, I would be sure. I have to reread that UDI documentation again. I believe they are stating it incorrectly, supporting my original ideas.

Here is a UDI wiki document explaining what you are describing.https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Working_With_Scenes_-_in-depth_tutorial#INSTEON_Devices_and_Local_Settings It also explains that the controller/responder device does not respond with the settings from the scene but only from it's own local settings when it's local button/paddle is activated to cause the scene to be activated. The SwitchLinc is described as a controller and responder also (as you stated) but it doesn't respond to scene activation. The docs also mentions devices that are only controllers and not responders.

Yuphttp://forum.universal-devices.com/topic/17495-how-to-use-a-ms-with-lights/?hl=%2Bxathros+%2Btechnique If this actually works there will be a lot of really happy people but it doesn't work in v5.0.7. Anybody else test or use this technique?