gzahar

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!

After re-reading PurdueGuy's method, I agree that would be as good or better of a solution if you already have the complete scenes with the fan control setup. The OP stated he could not control the fans from an external system via scenes. (I don't use HA, so I will go on his word here) He wanted to have the button status follow the fan status (when adjusted externally). What I am suggesting would operate in addition to the setup you have. The programs I suggested do that, and I can't see how this creates a race condition (but I could be missing something). I do see where you would have 4 writes to update the 4 LEDs at roughly the same time. I would expect the ISY to be able to queue these, but interesting point. So as an update each program could add an incremental wait to the else condition. This should minimize/eliminate message clobbering. program 1) Else: wait 1 sec, set LED 1 off program 2) Else: wait 2 sec, set LED 2 off etc.

Q1. In order to change a button state (LED) on a KPL, place the button as a responder of a new scene. Then turn this scene on/off in a program. (it will not activate/change the scene that the button is a controller of)

Just to be clear, I am only referencing scenes that control the button light on the keypad. (and the next command sent by that button if it is in toggle mode) It is not a scene that includes the fan motor or any other button / device and will not change the state of the fan. I have separate scenes for that. This should not create any race conditions, but yes it is 4 programs x # of fans that you have to write once.

In order to update a button state on a KPL, place the button as a responder in a scene. Then turn the scene on/off in a program (based on the fan state). Use 4 programs similar to this: Office Fan High - [ID 0111][Parent 0085] If 'Office / Office Fan-Motor' Status is High Then Set 'Office / Office Fan High LED' On <-- scene containing button Else Set 'Office / Office Fan High LED' Off

I think you rename the 'ISY' node in the network tree: (right click on it)

The password for the EVL is not the same as the online account. I think the default password is ‘user’. Sent from my iPhone using Tapatalk

The version of Mobilinc I have (HD) is a subset of the version you are running (HD doesn't have resource manager built in); so they should operate the same regarding an I/O linc device. Make sure you are directly pressing the garage door icon (or whatever icon you chose). This works for me both on dashboard and device pages. Reading back over your post a little more carefully, I think the issue might be that you are associating the status of the relay with the status of the door. With the relay set for momentary operation, it should always be in the same state (regardless if the door is open or closed) except for a brief time when it operates. i.e. it should always be open except for the fraction of a second when it closes to simulate the hard wired buttons. There is a sort of a 'bug' in ISY that will show the relay as 'on' after you issue an 'on' command (to close the relay), even though relay operation was momentary and immediately went back 'off'. This is why I wrote a program to query the relay 3 seconds after is detected the relay status as 'on' so that it could properly show the status as 'off' again. This use to save me from having to press the status icon twice in Mobilinc to get it to toggle again, but I just disabled that program and things worked on the first press (even though ISY & Mobilinc showed the status of the relay wrong). So either an update in ISY or Mobilinc appears to have fixed the issue I was having. (but it is still nice having the proper status of the relay shown in both places.) I see in the 2450 data sheet there is an example for controlling a garage door that uses momentary setting C (which uses logic for whether the sense input is open or closed to determine if it should operate the door). Don't know if you are using this mode to get discrete open/close commands, but I just use momentary 'B' to get toggle operation (open if closed / close if open). That may also be complicating matters (regarding getting the Mobilinc status icon to operate the relay properly).