larryllix

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

V5 Sent from my SGH-I257M using Tapatalk

I have found my applet in various places over the years. Look in the start pullup menu under ISY. Sent from my SGH-I257M using Tapatalk

The "send On commands only' option need to be selected so that only ISY programs control the Off cycle.

Yeah... four and a half seconds! That is too frequent! Sorry. My bad. Must be our time zone difference.

Your updates for each parameter are only about every four and a half minutes. That isn't unreasonable for any polled data system. Less than that you would get into human noticeable delays. I don't understand the polling you are referring to. I didn't know anything had to poll ISY, but rather ISY initiated the push of any events to the subscriber, after the initialisation dump.

Look like a defective stat. I assume this is an Insteon 2441?TH. Insteon devices are not polled by ISY typically. They report using push technology when things change. The 2441ZTH (note 'Z') will send humidity "CLIHUM" every about 45 seconds IIRC on AC power (adapter) and about every 5 minutes on batteries. You don't happen to have the stat powered from an AC adapter with a bad power supply filter capacitor, do you?

Ouch! I think we did but were too darn nice. N'est-ce pas? This brings up a good question. "Does Alexa understand French?"...or even Spanish?...from testing just now...nope.

Good catch! That would explain a lot of the problems. Thanks FallenAngel!!! I would be sure the Canadian location problems should have all gone away that I had before. This and previous major vs minor geo problems have confused the troubleshooting. Amazon is definitely playing OS favourites here! Again some brands lose out Now the decision to be made. A few Google Homes are a far cry cheaper than a a new android mobile phone. I only have five amazon devices so far. Maybe a different browser on my android tablet may make it work but for now I don't see any more effort to make this work. it would be nice to make the intercom feature work but that shouldn't need a permanent usage of an android 5 or later. Now I have to figure out why all my Dots and Echoes blurped as loud as they can go, and now have yellow throbbing on top for the last four hours, after reloading the android 5 app again.They all HA function still

There are certain things not allowed in Canada for various political and economical reasons. Right now I am discovering huge differences between browser versions. Google chrome on my Android 6.0 tablet is not allowed to access the app due to it being reported as "not compatible". My Notebook with win 7 x 32 using IE 11 cannot access the web page version. The "Remember me", "Show Password" and "Log in" buttons have been disabled so no access can be had there. My desktop with win 10 using IE 11 can load the webpage but none of the new features work...yet. My mobile Android 4.2.? loads and runs the app just fine but no new features are enabled...yet. This is changing weekly as features seem to get enabled. My mobile Android 5.? device, after removing everything and reinstalling (it wouldn't update or recognised it needed to) seems to have all the features now! AFAICT That's one success so far.