larryllix

hmmmm.. something tells me that logic doesn't work. If I use ... Control XXXX is NOT switched off it will run the else section when an Off control is received. However if use status ....Status is NOT off won't it run the Else section when the status if NOT off? I don't think that applies the same logic but I would try ...Status >= 1% for each line and see what happens. I know there is some discrepancies between some devices using "0%" or "Off" not triggering properly but I can't remember which devices were involved, or the correct logic, that has to be used in each case. BTW; You need a Wait in the then section before turning on the LED, especially if any of these lights are turned on by a battery operated Insteon device. I just had my first ALL ON in three years and the cause is felt to be just that...a battery operated Insteon device sending out multiple signals, like they do, and a program turning on a KPL LED simultaneously. yeah it was 2:15 AM and a few dozen lights went full on. WAF was real low when it woke her up.

You have a line ....Wait 4 minutes in each program, that has nothing to wait for.

What mode are you using for your KPL button? Most use non-toggle On mode so that the operation and control of the LED is more straightforward. It sounds like you have toggle mode enabled.

Bingo. That would be my opinion, also.

In your first program, when activated, it turns your light on dim...now it is not off, causing the else section to run and your first program to become False. As an alternative you can just detect the dim signal from the switchlinc and run the scene. You can shut them all off with a double tap off which causes a more universal feeling to the operations for users. Long tap down for dimming. Single tap down for Off Double tap down for more Offs I try to keep this fairly consistent throughout my house for better WAF and my own memory. The same applies for tap up. The programs become a lot simpler and do not require any status checking anywhere.

Your motion sensing device may be sending Off signals. This should be blocked usually. Use control xxxx is switched On to retrigger your timer every time motion is sensed. Using status may cause problems where your MS has a dead time and your wait time turns the light off. Also status will run your else, every time the MS times out. Using control allows your program to control it better without ever running the else section. The retrigger time on your motion sensor may have a dead time in it that can cause you dead time spots.

Welcome to the forum!! You don't say what platform you want it for. I assume this is for an iOS device.

What firmware and UI version are you using?

Try turning off one set before each trail and then test. Rotate the off set tested for each trial. Run several for each unit test. There may be a problem with a warm ballast/circuitry vs. a cold one also so length of time on may be a factor. This could help you identify which one is making the worst noise and the problem or one of the problems. Try a movable dual band unit right beside or on the same circuit as the outdoor lighting that is the problem to attempt to boost the signal at that point in the wiring. One of those medium base light splitters 1 male:2 female, comes to mind, with a med.base to plug in adapter and an Insteon plug-in module comes to mind for testing.

That usually indicates communication signal problems. Are some HID lamps?

I beleieve I followed the process laid out in the ISY wiki and it wasn't too bad excpet for the "what account are they referring to' in many places. When multiple accounts and places are involved every mention of an account has to be specified in complete detail. Yeah, typists lament.

Not ISY related! My wife tried this four times and I tried several additional times, also. Alexa confirms the date interim as Nov. 11th, when it asks time, or other clarification, but when you say 11:00 AM it confirms with November 4th, every time. Wife called me over and demonstrated this several times more, and then I tried it myself. Sometimes it confirms the date November 11th, when it asks for more information and yet everytime it finalises with ..."OK , you have an event on Friday November 4th, at 11:00 in the morning called Test Appointment. Right?" Try it and you can always say "No' upon the final confirmation. We have had suspected wrong appointments from Alexa, before, but never one we could repeatedly observe making a mistake.

Big task to take on. What is an ISY Portal? What is an Amazon Alexa account? I use the supplied app as the only way I know to make adjustments to the Alexa setup. The acount allows me to download the app if I am located in the right goegraphic location. Not to be be nasty but people familiar with a process usually have a hard time explaining things to newbies, that seem so obvious to them, once they have done them. Big job.

Have you tested your lights via manual control from the ISY admin console?

So you just remembered what version was on it previously but there is no notification. I thought maybe I had missed something ....again. [emoji3]

How are you aware of a firmware update?

Yeah. I am expecting an answer back within 48 hours effective over a week ago.

It can be done ok but you have to be partially insane or very meticulous in every move you make. If you ever do a Restore in ISY, all hub links are gone.

Many threads are full of sample programs using variables. There are too many uses to describe. The best is to read other people's code and see the examples.

Yeah. And my math was bad too. That's a six month penalty for experimenting. I wonder why amazon would be so stiff on the penalty. Even 30 days would be a deterent to not abuse their servers. Did you just call them by phone or email support or how did you plead the insanity case?

There is no point in doing that. Just right click on each device and select Restore causing ISY to clean out and refresh all links in each device. It's the same as starting over and .... 'feels like the first time'

No suggestions. They don't have weather anywhere close to me either and I can't change my location to my area in Canada either

I discovered another snag. If you create a household, linking accounts for different room operation setups, you cannot create a new household for 180 days after cancelling the last household configuration. No more of that for me for 3 months after my experimental setup and test. EDIT: duh! 6 months.

You can use either type of variable but if you want to trigger programs from it in other programs you will eed to utilise a State variable type, as mentioned by blueman2 above.

That would take v5.xxx or a series of programs based on each temperature threshold or a NR that sends the current temperature to ISY (itself) for every change in temperature above say...-1C