larryllix

These are only scenes that ISY is aware of. Scenes created on the side (manually at the devices) will not show in that ISY display. Nice V5? feature though.

Go to the bottom of your devices in admin console and see if any Scene exists that contains The MS and/or the device. This would be a scene you created using ISY as a scene manager. To eliminate any scenes created without ISY scene management, right click on each device and select "restore" Battery devices have to be placed into "Linking mode" first,

What are they supposed to do? Sent from my SGH-I257M using Tapatalk

There could be two things I can think of. - You may not have enough posts to paste things (troll and spam control) - Try the Code paste box by clicking on the '<>' option above the text entry box.

Note you can right click on your program in the program tree, select copy, and paste it in the forum posts.

It is usually better to disabe all the jumpers except for #5 to allow ISY to set the options, disable the Off signal and ignore any timing built into the Insteon MS. A few workarounds have been found for disabling the MS to Lamp with a direct Insteon connection (scene). - dim the lamp level so it cannot be detected as On. - set a long ramp on speed for the MS/lamp scene and beat if out with a programmed Fast Off. https://forum.universal-devices.com/topic/17495-how-to-use-a-ms-with-lights-for-faster-response/?hl=faster IIRC v5 has a disable function built into the ISY language, now.

Zippo. Waits are retriggerable in ISY. If he keeps moving the Wait (in the Then section) starts over each time. Most disable the Off send from the MS so ISY can control it based on more decisions.

Maybe I tuned in too late but why are we deviating from the standard three line program for a MS and Light? Who cares if the light ws off if we are turning it on? IF Motion detector is switched On AND Laundry light is OFF Then ....set Laundry Light ON ,,,, wait 2 minutes ,,,,set laundry light off Else ....nothin'

Always, always, always factory reset every Insteon device before linking into ISY. Use the delete existing links when linking. Easier to setup the bulb when closer to the PLM and may need dual band Insteon devices as repeaters to reach the bulb, especially if it is on the other phase leg of the 240 volt service in your house. Dual band units close to the service panel or a mechanical bridge between the phase legs can work for this. I have avoided any extenders, or phase bridge units in my Insteon system...old technology replaced by dual band Insteon devices.

Not sure if this is too complex for you or actually are looking for (without reading the whole thread again) but have a look. https://forum.universal-devices.com/topic/17495-how-to-use-a-ms-with-lights-for-faster-response/page-1?do=findComment&comment=157022

Here is a problem with folder conditions. As with all other ISY statuses of devices it only knows what it has been told ...last. When you create a folder condition it always seems to think it is negative and locks out the folder from operating. Try operating the light switch manually so that the folder comes up to speed.

Perfect!

You shouldn't add a motion detector status or control / switched to a folder condition. Add the status of the light to the folder. Add the motion sensor control / switched to the program operating the light (as you probably aready have) Now drag and drop the program to the folder and let it go inside the folder. I am not disagreeing with Stu at all, just attempting to clarify the possible confusion of using the method. shhhhhhh... Don't wake Stu. He is prepping for the big night tonight and will be testing it first so we can safety enjoy it an hour or more later.

Folders can be nested. Just drop your folders involved into another folder temporarily with a condition until you are done testing or keep them that way.

Put all programs into one folder you want to stop. Put a logic condition for the folder in place, and make it evaluate to False.

Do they not work with ISY v5.0.11b ?

Yup. It was when the font sizing feature first came out, only on v4 UI and I misread postings that it could work with v5...about v5.0.1-.2 era. It hung my ISY completely and I had to factory reset my ISY. I learned the hard way when admin console shows a mess, don't ever edit or save your prgrams. That factory reset cleaned up a huge speed slow down after the many failed node server attempts at installs and removals.

I had this experience also after many failed attempts to upgrade ISY. Failed running v5 with v4 UI, installed early Polyglot, failed, removed, reinstalled then repeated a few times with NodeLink in earlier versions. Eventually I factory reset my ISY and things became like new again. My conclusion was that early methods of node server installs, left uncleaned out links to things that didn't function or exist any more. The difference in speed was extreme.

Michel doesn't monitor all posts. Either quote some of his text or post your request in the Feature Request thread.

I use the variable set and detect method in many places. Once setup with the bank of programs as drivers the modularity allows easy changes without recreating and remembering how obscure programming paths work. Use of variables to control lighting scenes, programs and devices also allows many different inputs to control that variable. eg: To run a sequence of lights that independently dim and change colouring involving Insteon overhead floods, MiLight bulbs, Hue bulbs and LEDenet RGBW strips it is as easy as one line of code in a program. then ....set $sGathRm.mode = $cMODE.SUNSET This would take a myriad of programming to trigger every program, and scene involved. This would be nasty to change three programs that use that sequence. The central variable control makes it very easy and modular for future mods.

I did a blend of ver 4 and 5 once and made a mess of my ISY. If you have, or do not have, a good backup, factory reset your ISY, do a restore, set up your location times zone and a few other things and continue like nothing happened. I think there is some scene problems updating past early version 5.x. They had to be touched up to continue. IMHO well worth it though.

I believe this categorisation by Alexa is or the prupose of linking only certain devices to an Amazon device. Since I do not have an android v5.0+ OS (or maybe an iOS device) this is only a PITA to me.

The two category selections are not related. One is an ISY category and the other is Alexa's categorisation = "device" or "not a device". This caused me some grief, at first, wondering where half my devices went.

FallenAngel discovered their app doesn't function properly on android less than v5 as declared by Amazon on the PlayStore. I can confirm both sides of that. Android v4 and v5 Sent from my SGH-I257M using Tapatalk

I've been consuming v5 since the stone age without any major problems. ....Fred Flintstone Sent from my SGH-I257M using Tapatalk