larryllix

Really? You mean we have been paying big bucks for the silly IO/Linc to get a status contact input all this time??? Why didn't you say so before? ...like two years ago? OMG! Awesome!

Exactly and I agree. In a Switchlinc and most Insteon devices ...status comes fromthe dimmer circuitry ...switched ON/Off comes from the paddle. Nothing else can tap the paddle. When you turn on the dimmer from any source the status changes. It sends no switched signals. When you tap the paddle it sends a Control/switched. It has no status.

My son has one of those vacancy sensors in his bathroom. PITA having half an MS. Else section runs when the logic in the If section evaluates as false (in boolean logic) This will happen when a time frame is over (from-to). Since the MSes can only generate a "swicthed On" signal they only generate a True when the signal is received and False all other times. This means when the time frame "To" generates a True the MS conditions are False and run the Else section anyway. In the end the combination says If either MS sees motion...AND the time is between From and To, run the Then section, turning the lights on and restarting the Wait timer. Also, if the triggers from the time frame are exactly those times but no MS signal is present (not possible) run the Else section This program already contains the watchdog timer Teken was posting about. Confused yet?

You cannot detect vacancy. You can only detect occupancy. Vacancy can be assumed after lack of motion (or other) detection after some selected time. It is important that your MS is positioned to catch the most and slightest motion so that is crosses the sensing from side to side. If it is a commercial endeavour I would install two MS units, maybe on walls 90 degrees to each other to be as sensitive to motion as possible. Enable software configuration for the MS units and disable Off and dark only options. Use "switched" for a retriggerable timer action If ...( ...MS1 is switched ON ...OR ...MS2 is switched ON ...) AND ...from 7:00 AM ...to 1:00 AM (next day) <--- this will switch off lights if the wait fails because it logically evaluates to False running Else Then ...turn lights On ...Wait 30 minutes ...turn lights Off Else ...wait 10 minutes ...turn lights Off

I have the other view. I hate the look of the KPL. Although it has it's uses and may look OK in those applications. eg. fan speed control where there are multi-levels of speeds, maybe light levels. Think about a stranger, guest in your house that you would have to explain to them how to turn on a basic light switch! The WAF is not there either. They don't like to be "trained". I think a light switch doing light based jobs is what we expect and can be laied out to work as similar to a mechanical switch as possible. I have a large Gathering Room with one main switchlinc dimmer. That same switch performs 8 different functions that take very little training. That same switchlinc controls, 7 Insteon overhead flood lights, 5 Hue bulbs, 4 MiLight bulbs, and 5 RGBWW LED strips, including colour schemes. tap down = everything off double tap down = turns off all white ceiling potlights, and turns perimeter Hues, Milight bulbs and strip coloured to a seasonal theme determined by the date/season for festive lighting only. long tap down = Movie mode with very low whites and coloured perimeters similar to above long tap up = all white lights semi bright double tap up = all white full briliiance (like an operating room with about 300W of LED) tap up = toggles between TV mode and reading mode (a little brighter over the chairs) This is done by switch control programs that set a state variable to values between 0 and 20 and nothing else. Constant variables help clarify usage there (see below) I use a bank of programs in a separate folder that only recognise those state variable values and set the whole room to the desired effect. I use scenes for the Insteon bulbs and call them but there are many more non-Insteon bulbs that take NR, and Nodelink on a RPi, as well as my own NRbridge.py on the same RPi. Scenes are not necessary but make it quicker and more simultaneous than just programs. When you borrow a light for some alarm etc.. you only have to replace the value in the control state variable and everything is forgiven and back to the way it started again. WAF is high due to just tapping the top of the switch to turn lights on and tapping down to get lights off. If you want more light tap up again. Double tap up for even more light. We use that for dull days and the depression is much less on so many grey days we get. I could mesaure the difference, I am sure. And yet, the same lights are used for movie watching late at night with multi-coloured themic lighting to set the mood. Greazer, the variables are a good start toward the way I would do it again. You have simplified your package a fair bit. Looks good. I do find the tap down to turn things On counterintuitive though. Make sure you use a wait on that one. BTW: Most of us prefix variables with $s.xxxxx or $i.xxxxx. I only prefix state variables with $sXxxxxxxxx and not integer variables, so I/we don't get caught with the huge difference in function later. I also prefix constant variables (integer) with prefix $cXXXXXXX to keep all these values easy and not confused.

I was thinking that too but I think there were other GDO threads going on at the same time.

Yeah, many seasoned programmers have trouble with event driven software systems, over inline code systems. I sent a lot of time with VB and a real-time OS system doing electrcal grid protection with it. I loved it but definitely some screwy techniques needed. Yes, the wait is like an old Windows psuedo multi-tasking OS when you voluntarily give up your time slice to the OS so that other programs may run. Waits only need to be used, in this case, when a device may be operated simultaneously from two different programs or devices. It has unpredictable results. Your programs do a lot of overhead/homework to work off other program statuses. This complicates understanding. Calling other programs from Trigger only programs adds a lot of program complexity too. Must run at the moment.

Your main program calls the flicker program and then immediately calls a program to turn them off while Flicker is running. You have no control on which program ISY will execute first. Put your program lines from both program back into the DrivewayMotion program and addd a "Repeat 1 times" as per MWareman, if you want another Off insurance. Increase at least one Wait to 3 seconds. I like make the Off time 3 seconds and the On time 1 second so it looks more attention getting.

I would be quite surprised the open/close sensor would work well for a garage door sensor with it's shorter range of detection. Glad you have some success!

With a general ISY problem like that I would contact UDI support or factory reset your ISY. First attempt to take a good backup before doing this and hopefully you have one previous to the problem. admin/admin will result for the user/apssword and you will need to reset your time zone, and time etc and possibly restore your programs. Your recent backup may be a problem too, but the process is very easy to do again with the previous backup. You may want to contact UDI support first if you are not confident in doing this. Also this may help UDI be aware of some other problem they can dig into using your ISY as a report-bed.

Hitting an Insteon Network with repeated commands sometimes bogs it down and the ISY/PLM transmit buffers may overflow and forget/miss things. Try a longer wait time in your loop for an experiment. This sounds like you have some flakey comms and that will increase the Insteon traffic congestion even more with repeated tries. Yu could also try putting the devices into one scene and flash it on and off. It causes less Insteon traffic. I use with 20 devices in it (whole house) and it works much better for flashing. Two second delays work better though.

Have you checked your event viewer for excessive program action? The only time I have heard of programs not working is when some tight loop is executing and totally bogging down the ISY logic engine. Usually a constant busy box would be displayed on the admin console screen but the event viewer may show heavy traffic. Again Post a program that doesn't trigger so others can look at it.

I haven't followed all your logic through. It is too twisted and spaghetti bowl for me (I wouldn't use program true/false logic) but... You are trying to operate devices On and off at the same time without any delays. This can, and usually, results in a race netting random results. The processing logic order, inside ISY, is not clearly defined to the programmer, and no guarantee of order will happen. You have separated your If sections and your Then sections into different programs. I see no reason for that. You have Wait on the last line of programs. Then there is no following line. You are waiting for nothing to follow.

Strange!I had another one today where the light responded immediately and the "OK" came from 45 to 60 seconds later. I assume you have tried to factory reset the receptacle?

I have thought there was a previous thread regarding this that the IOLinc could not be included in scenes for one part or the other??? The only usage I can see is to extend the remote control of the garage door opener without any programs. Seems strange to me. Perhaps a good next step would be to request a photo of th e terminal wiring?

I was counting Teken's words. It twern't no rant! I hope that wasn't a typo just before the emoji.

Post your programs controlling the door. You mentioned after a power outage and this makes the program suspect after ISY reboot.

Just another cloud service that can suddenly take minutes or respond. I have one dot that seems to have poor comms with my router and it sometimes decidee to just stop reponding in the middle of a sentence or takes 30 seconds to turn off a light, at times. They will update the system with more hardware and then everything will be like new for a few months, again.

On AC the 2441ZTH only report humidity faster Nothing else changes.

All that and Scotty hasn't even got out of bed yet. emoji6976, emoji10567...whatever

This has been a fine example of network data collisions, exemplified by a forum analogue. Who the heck is emoji35, emoji13?

The Tags are much easier and cheaper to set up and have native charting provided for them and the CAO Reed Tag takes a 1-wire sensor to accommodate the possible heat with the Tag mounted in a cooler space. Just fasten a DS18B20 to a truss or "...beam me up Scotty!" Ohhh you thought I was talking to you? OP walks away shaking his head, never to come back again...

If it never gets that hot in a person's attic, why did you spend the money to install an attic fan? also Attics shouldn't get hot enough to destroy electronics after a properly running attic ventilator is functioning. What happens when it fails? Do we now replace both? You can't make a claim that attics never get hot enough to ruin electronics based on your own attic with a ventilation fan running for a reason.

It would be much easier to us the double tap up and down to control the other light. To achieve #2 you would double tap up and then down. To achieve #4 ...you wouldn't. Tapping up to turn lights off would break the normal habits and confuse people, lowering the WAF. But, as a logic problem.... Create four scenes...one for each scenario...on/on...on/off...off/on...off/off Create four programs, one to operate each scenario..each with a trigger for a state variable = 0, 1, 2, 3. You may require a Wait 1 second for the On turns it Off programs. Then use a program like this to rotate the state variable through all possible values. If ....SwitchLinc is switched On ...AND ...$sVariable < 3 Then ...$sVariable += 1 Else ...$sVariable = 0

Very strange. Let's satisfy both arguments with a DS18B20 1-wire sensor into the provided input on the bottom of the CAO Reed Tag see post #5. There is a reason the OP and you have installed a ventilation fan in your attic. There is also a reason some placed electronics in their cooled attic space to monitor it. BTW: your momma looked OK to me.