gzahar

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.

I think it’s ‘copy folder to clipboard’ but you probably figured that out. Sent from my iPhone using Tapatalk

Good to know. I am running in a NAS container also and ended up with the Bumbershoot route: ln -sf /usr/share/zoneinfo/America/Chicago /etc/localtime

Just noticed that my result for 29/100 is giving ..28. 28/100 = .28, 30/100 = .30, but 29/100 = .28 (unless I change the precision to 3 instead of 2, then it is .290 as expected). Running 5.0.13D. Anyone else seeing this?

Your notification is longer than a standard text message allows, so it is broken up into 4 separate messages. Sent from my iPhone using Tapatalk