gzahar

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

Check for zwave communication issues. Maybe try a heal. Watch the event log. Sent from my iPad 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).

FYI, in Mobilinc you can actually activate the relay control by pressing the status icon. (saves you from needing both icons on screen). Not sure how you are using the relay, momentary (to simulate the hard wired switches) or open/closed. I had an issue with a gate control that did not report the proper status of the relay after issuing a command that should do a momentary close. I don't recall the specifics, but I would have to issue the command twice to get it to operate. To fix this, I wrote a program that queried the relay several seconds after it saw the relay state change. If this is your issue, then maybe the query will do the trick (based on seeing the door state change). If the relay is not being used in a momentary configuration, then you may need to write a program that adjusts the state of the relay whenever it sees the door state change. (there would probably need to be some delays factored in)

Hopefully not with the command "Alexa, Alarm off"!

Same here. Thanks.

Are you running any node servers? (and ISY V5 firmware) Nodelink has a data device that create a node for the current minute, hour, day, etc. You could use 'If minute = 0 then execute stuff'. I think Polyglot has a similar node server.

On iOS. Go to Devices. Click + (upper right) Select 'Add Device' Select 'Other' (bottom) Select 'Discover Devices'

Basically any non battery powered Zwave device will act as a repeater. There are many recommendations in the Zwave sub-forum. It is also recommended to use devices with Zwave+ vs older non + devices. Sent from my iPhone using Tapatalk

What firmware version are you using? If not 5.0.15A, see 678 below. 5.0.15A Beta is now available, it contains the following fixes in addition to the changes below Fixes: 0000675 - Z-Wave Garage door open/close commands not available 0000676 - Consistent use of operator names in program conditions XML (X10 "is not" program fails to load) 0000677 - Default to supporting all button presses for Z-Wave central scene controllers when actual supported is unknown 0000678 - FanLinc Low status may not cause programs to run 0000679 - Support node server thermostats in ADR Developers: - Starting in version 5.0.15A, the event value for the Low status of Insteon FanLinc Motor changes from 63 to 64

Sorry, not talking about program. In order to query the MSII (and potentially reset the battery level) you must wake it up first by manually putting it in Link mode (press & hold set button until LED blinks green). Once in link mode, go to admin console, right click motion sensor node and select query. After you have done the query, go back to MS II and press (don't hold this time) the set button. It should now be showing double green blinks. Now press set button one more time and blinking should stop. At this point, hopefully battery level is showing proper level and everything is back to normal.

What is the current reported battery level? Is the sensor reporting motion correctly? Have you tried putting it in set mode when doing query? Sent from my iPhone using Tapatalk

Why don’t you right click the main sensor node and select group device. Maybe you have a low battery node but it didn’t get moved to the correct folder. Grouping the device should make it visible with the other nodes (if you do have one). Sent from my iPhone using Tapatalk

If you scroll down in the MS II options, there is a setting to create a battery node. (none or one) Don't know if this node will work like the MS I sensors in resetting battery status as mine are USB powered.