gzahar

I am on version 13: FreeBSD 13.0-RELEASE-p3 #11 releng/13.0-n244752-b368bb75bad ISY service running: isy is running as pid 1098 But response from add URL in Launcher (http://192.168.2.12:8080/desc) is 'Not Found'. Tried https port also with same results. Not sure where to go from here.

In order to change those parameters it must be usb powered or woken up by holding the set button. There may be programmatic ways to to write updates w/o doing this, but it is more involved.

Right click the device and select "Restore device".

I believe so (since they are battery powered and probably go to sleep after a time of inactivity). It made a difference for me, I was getting the same results as you before I changed it.

A retro gaming platform!

Did you try restarting the Admin console? If you right-click one of the Living Room nodes (scenes), does it give you the option to group devices? If so, will that locate the root node? If all else fails, try removing/excluding from ISY and re-adding. Factory reset before re-adding if that can be done.

When you right click the locks (in the AC) and look at Z-Wave/Z-wave Options, is Always Awake set to no?

Orchestrated Home is showing that they have these for sale. $140 if you want one that bad. Can't verify if they have them in stock though, but you can apparently place an order for one. Worth a call if you are interested. https://www.orchestratedhome.com/shop/pc/PowerLinc-Modem-Serial-PLM-Dual-Band-29p141.htm

I thought it specifically mentions starting the update neighbors process and lists each device as it updates neighbors then a final update complete. Maybe you need to change your log level. I’m on 5.0.16x still so that may be a difference also.

Did you try https? (vs just http)

I do not believe lights going on/off will trigger your motion sensors. I have never witnessed this behavior and it would be very problematic for many situations. Regarding your program, are you seeing the status of the motion sensor change at all? Also there is an options setting for changing the timeout of the sensor to turn back off. Check the summary tab in the program area to see the last time your program was run.

I believe it’s in the event log.

Yes, but I don't know of any other suggestions for you other than maybe adding it close to ISY w/o going through any repeaters. I am using 5.0.16C firmware. My Zwave version is 6.81. I didn't know there were newer versions available.

Just noticed Seco-Larm uses the word "Enforcer" on many of their products, so you are apparently using a different model than I am.

You can connect the white wire (relay output common) to the GND terminal on the 2450. The gray (Normally Closed) or black (Normally Open) should be connected to the sense (S) terminal. The sense input will activate on the 2450 when the external connection is closed, so depending on how you have the Enforcer setup will determine whether you should use the normally open or closed wires. Alternately you can reverse the logic of open vs closed in the ISY to send out notifications. The data sheet for the Enforcer does not show a red wire and is consistent with the one I have. Regardless, you will need to find the pair of wires that go between open (no/infinite resistance) and closed (< 1 ohm) when the sensor changes state and wire them to the GND and S inputs of the 2450.

Great. Was confused by this statement on the configuration page. (made is sound like state variables could be used) "There are 3 kinds of virtual devices, switch, dimmer and temperature. You do not need to have a state variable for each entry."

@markv58Same question. I'm assuming this is correct. Also agree this is a very useful NS. Thanks!

I think if you are using the ISY Launcher it dynamically downloads the correct UI over the internet after checking your firmware version. (but you would think it would use a cached version first before trying to download). Alternately, you can download the admin console directly from the ISY if the internet is down using <your ISY IP>/admin.jnlp.

Don't use momentary mode. Write program that turns it off after 75 mins. If Relay status is on Then Wait 75 minutes Turn off relay

Why don't you just edit an mp3 file to be 15 seconds long (with the part you want). That's what I do (you will need to upload the file to a music service such as Apple Music and tell Alexa to use that service). Thanks for this tip. Previously I was only able to get the song on one echo device. Now I am able to play on all.

The locks.

I believe some sensors can be written to when they wake to report status (such as motion, not sure about door/window). If you search the forum you can find some examples of programs that write any updates when a status change is detected. Edit: this may only be available on ISY Pro or V5 firmware, not sure.

They are.

I was going with the assumption he wanted the lights on for the first Thursday of the month, hence disabling the Friday after (you will need the > 1 for that). Your example will disable on the first Thursday. May not matter. Other than that, I don't see how yours is any different than what I posted.

Any day of the month after (>) the 14th will start being the third 'day' of that month. So once you hit the 15th day or greater and it is a Thursday, it will be at least the 'third' Thursday of that month. It may also be the 4th Thursday (Thanksgiving), but it doesn't matter because you still want the lights enabled (starting from the third Thursday). Keep in mind when using '>' any day after the 14th will be true for that line and it will also need to be November & Thursday for the program to run 'Then'.