drich

Thanks, I upgraded to 5.0.15A as soon as it came out for that very reason.

Thanks, that clears it up! I need to go through my code and see if I have any other lingering checks that have both conditions on a status instead of a control. Now if I can just figure out what is up with that one KPL.... I need to go through and add the programs to two more KPL to see if they behave properly as well.

Well this is interesting... I just tried the same group of four programs on a different Fanlinc/KPL combination, and it works perfectly. There's something up with this particular KPL, but even doing a restore doesn't seem to fix it. It works fine locally but even running the scenes from MobilLinc only triggers whatever button is turned on first - I.e. If I trigger the Low scene, the low button (C) will come on. If I then trigger Med, the fan goes to medium speed, the Low button (C) turns off but the Med button (B) doesn't turn on At this point, only the Low button will light from triggering any of the scenes, Med (B) and High (A) stay dim no matter what speed the fan is running at. If I press any of the buttons on the KPL it triggers the correct scene. And it resets which button lights up -- after I use a button whichever scene I trigger from MobiLinc will light the correct button, but then the other two buttons won't light up. I've checked both of the KPLs are identical - all buttons set to toggle and the scenes control the grouping, I haven't used the "Buttons Grouping" button in the UI. They are both of the same generating, both showing v.40 in the ISY Admin app.

Yep, that's why I'm trying to trigger the scenes when the device state changes. See the comment in the code block: " 'Fans / Great Room Fan' is the device node, 'Fans / Great Room Fan Low' (Med and High) are the scenes". I.e. anything with "Low/Med/High/Off" in the name is a scene. So the "if" is checking the device status, the "then" block is triggering the scene. Is this new in 15.x? This wasn't the case in prior releases. Using your code, the status of the program would never change to false in the past. If you look back at some of the early posts I made when I first got started with the ISY (almost 10 years ago) I was told to always write code like: If 'X' is On And 'X' is not Off Otherwise the Else condition never triggers (not really an issue in this case since I am not using Else) However, I just tried it with the fan programs and the state does do the right thing with just the single If statement - thanks! Huh, I never noticed that "Copy to Clipboard" before... Easier than retyping like I did above! Using state variables is a thought... I went down that route with my Whole House Fan since it doesn't have native fan support, it instead depends on a Network Resource I put together a few years back. (Airscape 1.7 WHF). I'm not sure that addresses the issue where the device itself is triggered though, that's the whole reason I started working on this program in the first place. I'm having a hard time getting the rest of the household to run the scenes when they can see the devices in MobilLinc, and other systems like HassIO see the fan nodes natively.

I have a handful of FanLincs being controlled by KPLs (I really wish there was a better option) and for the most part they work really well. The one problem is if someone uses the fan device instead of the scene to control the fan. If they do (or if some other home automation software turns on the fan like HassIO) the fan will come on, but the KPL buttons don't light up. I figured the easy way around this was with a group of programs, but I still can't get them working. For example, take the following programs: If 'Fans / Great Room Fan' Status is not off And 'Fans / Great Room Fan' Status is Low And 'Fans / Great Room Fan' Status is not Med And 'Fans / Great Room Fan' Status is not High Then Set 'Fans / Great Room Fan Low' On Else If 'Fans / Great Room Fan' Status is not off And 'Fans / Great Room Fan' Status is not Low And 'Fans / Great Room Fan' Status is Med And 'Fans / Great Room Fan' Status is not High Then Set 'Fans / Great Room Fan Med' On Else # Repeat for High and Off, with Off turning all threse scenes off in the Then block as I don't use the 'D' button to indicate off # # 'Fans / Great Room Fan' is the device node, 'Fans / Great Room Fan Low' (Med and High) are the scenes This actually works -- sometimes. The first time I set the 'Fans / Great Room Fan' device to a speed, the correct scene (Low/Med/High) will be triggered. However, if I change the speed the first speed KPL button will go out, no other button lights up. The program status appears correct, the Low/Med/High/Off program will show true for whatever speed is selected. And if I look at the scenes themselves, they show the correct button status; i.e. if I go from Med to Low, they show the fan at Medium and the Low button as "On". Given that I have nothing in the Else block for any of these, I'm not sure why the buttons are turning off (probably because the scene change is getting partially triggered), much less why they aren't turning on after the first on. I'm assuming there is some sort of race condition in here somewhere, but I'm stumped f I can find it. This leads to a couple of questions... What is going on that might be causing this behavior? Is there a better way to get the buttons to respond to changes in the fan device, or are programs the only way?

I just updated my open ticket with Smarthome, after taking my fan canopies down (all but one I can't get to w/o moving furniture) and it's consistent -- all four of my old FanLincs work fine. Both the two I purchased recently and the two RMA units all show the same issue. The old ones are all labeled "0912 REV1.1" and the new ones are a mix of "3.1 4118" and "3.1S 3418". The old ones show up as v.41 in my ISY, the new ones as v.45. The fan control works fine The light control works with fast-on/fast-off Sending an Insteon on command will cause the FanLinc to reset when the light reaches around 30-40% brightness (tested by setting the ramp rate to 8.5s and counting between 3-4 sec before the FanLinc resets). If I have the ramp rate at 0.1s, the light will flicker for an instant before it resets. If I use the start with the light off and use the brighten Insteon commands, I can get to just past 30% before the FanLinc goes into a reset loop. The only way to fix that is to use the pull chain on the fan to turn off the light so I can then turn it off in the FanLinc once it has reset itself. I'm assuming there has been a hardware change as well, as looking at the FCC photos there is virtually no way they could get the new wiring pattern of white/blue/red/black with the original circuit board. I wish I could open these up to get photos of the internals and see what has changed, but since they are all likely to be RMAed I don't want to void the warranty by opening them.

That was what I thought when I first received one of the new ones. However, the installation sheet that comes with them has been updated to still show red for the fan motor, blue for the fan light, and white and black for hot/neutral. And I do have two of them that work fine - although one of them is an RMA since the original one was DOA.

The latest fan (the one I'm currently fighting with the FanLinc) is just a 2-wire install with the switch controlling the power. The old fan that is being replaced had a remote, so that's all it needed when the prior owner of the home installed it. That switch is going to get replaced with a KeypadLinc if I ever get the FanLinc working reliably, so the switch will be out of the circuit at that point. You're correct, the FanLinc shouldn't reset -- hence the problem. It doesn't appear to be losing power, it looks more like something is causing it to reset like it's detecting a short. However, an old FanLinc doesn't have the same issue with this fan. It also does the same thing with a different light kit (from the same model of fan) installed. Personally, I think the latest generation of FanLincs have horrible QA, as this isn't the first time I've had to go through multiple ones to get one that works.

The FanLincs in question are linked to my ISY994i, and I would swear the light button works just fine on the local device - but I don't really feel like ripping a fan canopy apart to check at the moment. I've tried multiple brands of LED and the incandescents the fan came with. I have a nice collection of various brands after trying to fix a flickering issue on two of the fans that have newer FanLincs, they would flash on any Insteon traffic on the network. This isn't a unique problem, I've seen several posts on this issue on various forums, for example: For these fans (Westinghouse Comet) turning on the light with the pull chain causes the FanLinc to reset -- most of the time. Fast On will work, so will using the fader to dim the light up from 0%, although at some percentage it will put the FanLinc into a reset loop. The only way to fix that it so turn off the light with the pull chain. Once the light is off, the FanLinc goes back to normal. I've gone through three rev 3.1 FanLincs so far with no luck. This is actually progress, as the first two would reset even with Fast On. However the older FanLincs (the ones that with the wires going white/black/red/blue) work fine. The newer ones (white/blue/red/black) all have issues with the lights in these fans. The motor control works perfectly however. And of course the light works fine when wired directly to a wall switch with the FanLinc out of the loop. Smarthome is stumped, although I've only spoken to their front-line support who honestly doesn't even seem to know what the products are. I miss the days when the support was down in Irvine, CA and they had people who actually knew the Insteon products...

Something seems to have changed lately with the FanLinc, the last few I have ordered have different wiring from the older ones (the wires coming from out of the case are in a different order) and I have have had one DOA, two that won't control the fan light properly, and one that died after a few days in use. My older FanLinc modules work fine with the same fans. In my case it isn't programming, out of the box they didn't work properly, even using the buttons on the FanLinc. I'm about to go for my 2nd round of RMAs with my latest ones. I've reached the point where I'm starting to wonder how long Smarthome will be around with their nearly constant sales, outsourcing of support, and lack of people who know their own products working for them. I just haven't found a replacement for some of their products like the FanLinc and KeypadLinc so I'm somewhat stuck at the moment. Meanwhile I have two fans that I can't get working as I only have a single hot and neutral wire running to them and no good way to control them. And since we do use both the speed control and dimming, the options are limited.

Has anyone come up with an alternative to Smarthome's Fanlinc? I am in the process of replacing some older ceiling fans and want to add controls to them, but am having mixed results with the newer generating of Fanlincs. To date I've had flickering with LED lamps, one fan where the Fanlinc will reboot itself if I turn on the lights, and another Fanlinc that appears to have been wired improperly internally (Smarthome replaced that one). I'm starting to think it's time to give up on the Fanlinc, but to date I haven't found anything else with the same functionality. Most of these fans only have a hot and neutral wire in the box, so short of doing quite a bit of rewiring I don't have the option of controlling them with a pair of switches. I haven't seen much on the market that will install in the fan canopy and allow non-proprietary control. Has anyone else found anything?

Ok, it's an older question, but since I'm in the process of upgrading my 20-year old ceiling fans... My choice was to cap the red wire from the KPL and use the FanLinc to run both the fan and lights. I've had much better luck with the FanLinc reliability than I have with KPLs, I think I've replaced nearly half of my KPLs at one point or another. I just wish the FanLinc had some competition. It's hard to believe that it's the only combo fan/light controller on the market. I'm amazed that one of the Z-Wave manufactures hasn't come out with something similar yet!

Another thing you can do is have the kpl or switchlinc beep after a successful fast on or off. I wish I could. These are old SwitchLincs, they can't beep. Thanks for the idea though!

That's the thing that took a while for me to get my head around when programming the ISY. You aren't checking the state of the switch but the state when it changes. So most of the time the code does nothing, but when it changes state to either fast on or fast off, it executes. Writing code like this is the only way to get your program to execute the "then" branch when one thing happens and the "else" when the other happens. If you do something like If Control 'SwitchLinc DB Dimmer v40' is switched Fast On Then ... do something ... Else ... do something else ... your else block will never execute as there is nothing to make the program go false (unless you run it from another program, of course). Switching the switch fast-off will not make that if statement go false.

LeeG, You got it, that was my problem. Apparently I was just double-clicking too fast. I never noticed it on the other switch where I use a similar idea (fast-off in the bedroom turns off the hall motion sensor at night so the lights don't come on and wake me up if anyone else is up). Since that one is a KeypadLinc, I just can't double-click it as fast as I can with the SwitchLinc. I modified my program so now it flashes the lights when I turn double-click, that way it is really obvious when I do it right. Thanks for the help!

Well, the trace shows my problem, I'm not getting a fast-on when I double-click on the SwitchLinc. Below is what I see when I walk across the room and do a double-click on it. Any ideas why a double-click wouldn't generate a fast-on? The lights connected to the switch do come up to 100% immediately, although the admin interface only shows them at 30%, which is what the current on-level is set to at night when the motion detector triggers. If I query the device, then the level jumps to "On". The devices involved: [*:2fljw7vr]12 1E B5 - Hall Switch 1 [*:2fljw7vr]12 1D 83 - Hall Switch 2 [*:2fljw7vr]14 10 62 - Hall motion detector [*:2fljw7vr]14 10 58 - Motion detector in the room I'm in Thu 09/26/2013 19:53:18 : [iNST-SRX ] 02 50 14.10.58 00.00.01 CB 11 01 LTONRR (01) Thu 09/26/2013 19:53:18 : [std-Group ] 14.10.58-->Group=1, Max Hops=3, Hops Left=2 Thu 09/26/2013 19:53:18 : [ 14 10 58 1] DON 1 Thu 09/26/2013 19:53:18 : [ 14 10 58 1] ST 255 Thu 09/26/2013 19:53:18 : [iNST-SRX ] 02 50 14.10.58 00.00.01 CB 11 01 LTONRR (01) Thu 09/26/2013 19:53:18 : [std-Group ] 14.10.58-->Group=1, Max Hops=3, Hops Left=2 Thu 09/26/2013 19:53:18 : [iNST-DUP ] Previous message ignored. Thu 09/26/2013 19:53:19 : [iNST-TX-I1 ] 02 62 00 00 1A CF 11 00 Thu 09/26/2013 19:53:19 : [ Time] 19:53:19 9(0) Thu 09/26/2013 19:53:19 : [iNST-ACK ] 02 62 00.00.1A CF 11 00 06 LTONRR (00) Thu 09/26/2013 19:53:19 : [ 15 4A F 1] ST 102 Thu 09/26/2013 19:53:23 : [iNST-SRX ] 02 50 14.10.62 00.00.01 C7 11 01 LTONRR (01) Thu 09/26/2013 19:53:23 : [std-Group ] 14.10.62-->Group=1, Max Hops=3, Hops Left=1 Thu 09/26/2013 19:53:23 : [ 14 10 62 1] DON 1 Thu 09/26/2013 19:53:23 : [iNST-SRX ] 02 50 14.10.62 00.00.01 C7 11 01 LTONRR (01) Thu 09/26/2013 19:53:23 : [std-Group ] 14.10.62-->Group=1, Max Hops=3, Hops Left=1 Thu 09/26/2013 19:53:23 : [iNST-DUP ] Previous message ignored. Thu 09/26/2013 19:53:30 : [iNST-SRX ] 02 50 14.10.58 00.00.01 CB 11 01 LTONRR (01) Thu 09/26/2013 19:53:30 : [std-Group ] 14.10.58-->Group=1, Max Hops=3, Hops Left=2 Thu 09/26/2013 19:53:30 : [ 14 10 58 1] DON 1 Thu 09/26/2013 19:53:31 : [iNST-SRX ] 02 50 14.10.58 00.00.01 CB 11 01 LTONRR (01) Thu 09/26/2013 19:53:31 : [std-Group ] 14.10.58-->Group=1, Max Hops=3, Hops Left=2 Thu 09/26/2013 19:53:31 : [iNST-DUP ] Previous message ignored. Thu 09/26/2013 19:53:31 : [iNST-TX-I1 ] 02 62 00 00 10 CF 13 00 Thu 09/26/2013 19:53:31 : [iNST-ACK ] 02 62 00.00.10 CF 13 00 06 LTOFFRR(00) Thu 09/26/2013 19:53:31 : [ 12 1D 83 1] ST 0 Thu 09/26/2013 19:53:31 : [ 12 1E B5 1] ST 0 Thu 09/26/2013 19:53:32 : [iNST-TX-I1 ] 02 62 00 00 19 CF 11 00 Thu 09/26/2013 19:53:32 : [ 1B 9E A2 6] ST 0 Thu 09/26/2013 19:53:32 : [iNST-ACK ] 02 62 00.00.19 CF 11 00 06 LTONRR (00) Thu 09/26/2013 19:53:32 : [ 12 1D 83 1] ST 76 Thu 09/26/2013 19:53:32 : [ 12 1E B5 1] ST 76 Thu 09/26/2013 19:53:32 : [iNST-TX-I1 ] 02 62 00 00 19 CF 11 00 Thu 09/26/2013 19:53:32 : [ 1B 9E A2 6] ST 255 Thu 09/26/2013 19:53:32 : [iNST-ACK ] 02 62 00.00.19 CF 11 00 06 LTONRR (00) Thu 09/26/2013 19:54:25 : [iNST-SRX ] 02 50 14.10.62 00.00.01 C7 13 01 LTOFFRR(01) Thu 09/26/2013 19:54:25 : [std-Group ] 14.10.62-->Group=1, Max Hops=3, Hops Left=1 Thu 09/26/2013 19:54:25 : [ 14 10 62 1] DOF 1 Thu 09/26/2013 19:54:25 : [ 14 10 62 1] ST 0 Thu 09/26/2013 19:54:25 : [ Time] 19:54:26 9(0) Thu 09/26/2013 19:54:25 : [iNST-SRX ] 02 50 14.10.62 00.00.01 C7 13 01 LTOFFRR(01) Thu 09/26/2013 19:54:25 : [std-Group ] 14.10.62-->Group=1, Max Hops=3, Hops Left=1 Thu 09/26/2013 19:54:25 : [iNST-DUP ] Previous message ignored. Thu 09/26/2013 19:54:30 : [iNST-SRX ] 02 50 14.10.58 00.00.01 CB 13 01 LTOFFRR(01) Thu 09/26/2013 19:54:30 : [std-Group ] 14.10.58-->Group=1, Max Hops=3, Hops Left=2 Thu 09/26/2013 19:54:30 : [ 14 10 58 1] DOF 1 Thu 09/26/2013 19:54:30 : [ 14 10 58 1] ST 0 Thu 09/26/2013 19:54:30 : [iNST-SRX ] 02 50 14.10.58 00.00.01 C7 13 01 LTOFFRR(01) Thu 09/26/2013 19:54:30 : [std-Group ] 14.10.58-->Group=1, Max Hops=3, Hops Left=1 Thu 09/26/2013 19:54:30 : [iNST-DUP ] Previous message ignored.

I have a pair of switches that control a single light that is also activated by a motion detector. I'm trying to write some code that disables the motion detector when I double-click the switch, and renables it when I double-click it off. This seems like it should be really easy, but for the life of me I cannot get it to work! I have a program called "Hall Motion Disable" that has the following code: If ( Control 'Lighting / Hall Switch 1' is switched Fast On And Control 'Lighting / Hall Switch 1' is not switched Fast Off ) Or ( Control 'Lighting / Hall Switch 2' is switched Fast On And Control 'Lighting / Hall Switch 2' is not switched Fast Off ) Then Run Program 'Hall Light Timer' (Else Path) Else What I would expect is that I if I double-click either switch the program would show a status of True in the Program Summary, and if I double-click them off it would switch to False. However, the program status never goes to True. In fact, it shows that it has never even run. Am I missing something really obvious here? This seems like it should be a no-brainer. The two SwitchLincs are controllers in a scene along with another KeypadLinc that has a button I use for status, but other than that there isn't anything special about them. Fast-on on either switch does bring the light on at 100% immediately, so I know they are talking to each other and the ISY does show the light level correctly in the web gui. If no one has any obvious ideas, I'll grab some debug output from my playing with the switches tonight and see if that helps (pardon the pun) shed some light on the problem.

I am using a couple of KPLs to control FanLincs and in one case a remote In-LineLinc. They almost do what I want, but not quite, and I want to see if I'm doing something wrong or they just don't work the way I think they do. With the FanLinc, I have three scenes, one for each fan speed. In each of those scenes I have one button set as a controller and two other buttons set as responders. This lets me have the controller turn on but the other two buttons off; essentially having three grouped buttons. This works great from the KPL, but if I turn on the scene from the web interface or from my phone all of the buttons light up. Is there any way to have both the buttons act as grouped buttons and also be able to turn the scene on? I'm trying to do something similar with the In-LineLinc, but in that case I am going to be controlling them from a pair of KPLs in different rooms. I'm writing some code to treat the A, B, C, D buttons as timers and need to be able to turn the scenes on and off to activate the buttons. The one thing I thought of was to have one set of scenes just with the buttons I want on and the FanLinc/In-LineLinc as responders and a separate set of scenes setup like I mentioned above. I couldn't get that to work reliably either. Any thoughts?

I trued using 255 (and various other values) in the admin interface, 0 seems to be the only thing that will take it back to full brightness. In the program I was using 100%, which I assume should map to 255. I had also tried 30% and 70% as dim values as I'm trying to set it to a lower value at night.

Oddly enough, I can adjust the LED brightness on my SwitchLinc switches (0.38) just fine from the admin gui, but not programatically. I can dim them from a program but cannot get them back to full brightness. Going back to the gui and setting the brightness to 0 brings them back to full brightness (which is brighter than when I set them to 255 via the gui).