gzahar

I think your best bet is to cap the KPL load wire and use a secondary Insteon device (micro module, etc. as suggested) to control the second motor with an ISY program based on Fanlinc status.

Good catch. Forgot about that. It must be inherent delay in the status changing that restarts the program. Or it’s queuing up the status change?

It is not getting to the Stop program command. When you change the device (center ceiling) it causes the program to re-trigger the 'if' evaluation and run 'Then' or 'Else' accordingly. You have created an infinite loop. As far as why the stop menu command is not working, I can only guess. The last insteon command to change the light has probably already been sent out by the PLM when you issue the stop. But the light then responds to the command after the program has stopped (due to communications or queue delays) and that starts the program up again.

Please click on the red IRLinc E shown in your latest picture. It will have a set of scene definitions. Do they match your 1st picture?

How are you activating the scene? Can you show this section of your scene:

You could use something like this paired with an I/O Linc. https://www.amazon.com/dp/B00LWX9PPA/?coliid=I3TZQA51Z1RMS9&colid=3FU9DR7KP09DP&ref_=lv_ov_lig_dp_it&th=1

I see similar situation with programs involving node servers (but not Sonos specific) after a reboot of ISY. I can also fix the issue by toggling the state of the node in the ‘if’ statement. What version are you running? One of the newer RCs has a fix for a similar issue with ELK nodes. Was hoping it also fixed this. I haven’t tried the last two. You are seeing this reoccur without an ISY restart?

I see similar situation with programs involving node servers (but not Sonos specific) after a reboot of ISY. I can also fix the issue by toggling the state of the node in the ‘if’ statement. What version are you running? One of the newer RCs has a fix for a similar issue with ELK nodes. Was hoping it also fixed this. I haven’t tried the last two. You are seeing this reoccur without an ISY restart?

Turning a scene off, turns everything off. Devices will stay off if they were off in the scene 'on' definition. If you want lighting to go back to the level it was before the scene was turned on, you will need to use programs to save the states and restore them when the scene is turned off. I don't remember, but this may require V5 firmware also. You would probably not be able to assign the KPL button directly to the scene so that you can capture the current lighting levels before the scene 'on' is activated. The KPL button would trigger the scene on/off program(s) instead.

Unless you move to 5.x you will only get the features of the MS I. Per your screen shot, the ISY thinks it is an MS I (2842); and this is the only support for it in 4.x. Out of curiosity, what is ISY version 8.6.0? You should have a firmware and UI version that match. Assuming 8.6.0 is not a firmware number?

@Michel Kohanim FYI, the email address on that page appears to be miss-typed. (but the link is correct)

You can create a scene with just the fan off button in it as a responder so that you can turn the button on/off when you want. Then write a program that turns that scene on if the status of the fan motor is off (and turns scene off if you want in the else).

Not sure, but would try this. If from time to time + 6 minutes Then Set lamp device ramp rate to 5 min Wait 5-10 seconds (may need time for RR to get programmed) Dim lamp device to 25% Else Set lamp RR to 2 sec. Don’t think you need to use scenes. Sent from my iPhone using Tapatalk

If by triggering event you mean a program triggered by the button, that would be slower. But as others have said, using the button as a controller in the scene is the way to go, but create it using the ISY admin console. Sent from my iPhone using Tapatalk

You need to replace [YourISY] with IP address. Sent from my iPhone using Tapatalk

I think I did something like that using an Insteon device successfully . Haven’t tried with Zwave. Sent from my iPhone using Tapatalk

Could it be a firewall issue?

That is gone in V5. So apparently that is the version you are using. If you have a big scene, it may be worth recreating by adding the responders first and setting them to the levels you want. Then add the controllers and they should adopt the current settings (or so I have read).

V5 is beta s/w. It needs to be manually updated.

Agreed. But this is kind of like removing the on level and ramp rate from the AC UI because all Zwave switches don't support those features. And telling you to use parameter entry for that on Insteon switches because we want to support multiple technologies. I get the time/effort/payback reasons if that is the case, but don't believe it is a technical issue. I know this has hit the forum many times and there is no appearance it will be changed; so no need to really rehash it. I don't use very many large scenes so not a big problem for me (but then maybe this is why?)

You could have it as an option for Insteon only scenes (and disabled if mixed).

I believe your program should work as is. A few notes: You don't need to stop a program before you disable it (just disable it). "Run Program 'Movie Program' (If)" will not stop execution of the currently running 'Movie Program Start' (unless that program purposely stops it) If doesn't have to finish before the rest of the current program continues. What does 'Movie Program' do?

You do know there is a program step that allows you to enable and disable other programs? Movie program would disable all the programs you don't want running, maybe adjust/turn on an outside lighting scene, wait 4 hours, enable the programs you previously disabled. Maybe enable/disable programs is a V5 feature only and you are on V4?

I won't say that I understand the intricacies of the MSII and it's timers enough to completely grasp what you are trying to convey (mainly I don't want to think that hard!), BUT I will say that I am using the MSII (under USB power) to trigger and keep a light on and it is working fine for me. If I stand still long enough (or hide) the lights will go off and they turn back on after I move around again. Also I do use 2 of them in the area to cover spots that can't be seen by the other and they are USB powered as I mentioned; so maybe that makes a difference. Happy to share any settings or programs (that I stole/modeled from examples on the forum) if that helps.

Agreed!