gzahar

Sorry, I was thinking about detecting if the fan died, not whether it was turned on/off. @MrBill's suggestion should work fine. Otherwise, you might be able to use something like this (for 12V fans) as a front end to the relay: https://www.amazon.com/Temperature-Control-Speed-Controller-Module/dp/B019P0FLHW (Using a relay instead of the buzzer)

No. At least not directly w/o putting some kind of sensor on the fan/circuit. Dry contact closure basically means an open or short circuit like that provided with a relay. It is also possible to use an electronic circuit (like a transistor or optoisolator) to simulate a relay contract closure.

Not an easy question to answer. But: 1) will allow you to upgrade past 5.0.16c when/if needed. 2) z wave backups are a lot faster on 500 board (not something that is needed often, but nice) 3) If you have all z wave plus devices it will give you advantages of zwave plus.

Understood, but based on a number of people doing that exact thing, Michel commented that it was not valid (at least that was my interpretation). Anyway, glad it is worked out now.

Please see Polisy thread. Michael commented that this does not work in a browser. It worked for me on the Polisy.

If you right click one of them, do you have a ‘group devices’ option?

Interesting; my Firefox gave me this: What can you do about it? forum.universal-devices.com has a security policy called HTTP Strict Transport Security (HSTS), which means that Firefox can only connect to it securely. You can’t add an exception to visit this site. Had to move to a different browser.

Just worked for me. FreeBSD 12.2-RELEASE-p2 r368666 POLISY

You will need to ungroup devices first.

Right click - delete?

Depends how ‘bad’ the repair was. If any devices were updated with the newer repaired PLM address during the restore you will need to do a restore again with the older PLM. Since this may be hard to know, the safest bet is to restore again.

Just found Portal requirements also. Says minimum for network module (also used with Portal) is 4.4.?. But either way, that’s not your issue. Is your ISY UUID registered in My Account?

I don’t think this will resolve your problem, but the firmware and UI should match. If you you use the ISY launcher it should load the correct UI for your firmware. Be sure to clear the Java cache first. I think you need v5 firmware to use portal?

Right click the My Programs folder and select "copy folder to clipboard". Then paste it into a text editor (like notepad etc.). The icon with an arrow indicates program changes have been made and need to be saved. (save changes button at bottom). I would verify the UI and firmware are the same version (help, about).

There's nothing preventing you from sending an email (from ISY or otherwise) with any information you want to include (SSN, hard coded IP address, etc.). So having a variable substitution method for the IP address is no less secure. It is the user's decision to publicize that content.

The second item in the menu should say "Remove/Exclude...". Excluding is basically the same process as removing. You are really just removing a device that is not added yet.

Those are on 5.0.15, but you probably need a pro version of ISY for them to show up.

I think you want to put each button & switch in a scene with both being controllers. Sounds like you have the switch as only a responder (or used programs).

They are not very loud (don't have the dimmer outlet, but I have a dual outlet). A program like this should work (remember to stop it if after you locate the device). Right click the program and "Run Then" to start. Outlet Beep - [ID 0144][Parent 0005] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat Every 3 seconds Set 'Missing Outlet' Beep Else - No Actions - (To add one, press 'Action')

If you are trying to accomplish the first step (Create a State Variable named “Manual override” and set its value to 0), that is done in the variables tab (not a program). Also, the program calls for a state variable (make sure to use the state variable section when creating). Your sample looks like you're using an integer. Once you create the variable (using Add then Save), you can double click on the name to edit the name. The other steps above indicate where to locate each program line (if, then, else). The first line of the "if" section will not matter if you use 'and' or 'or', unless you later rearrange the program lines. The remaining lines in the section will use the 'and' or 'or' shown preceding the lines above. Use 'is' for "=". ('is not' for not =).

You could try to control it from the ISY admin console and see if it responds with expected status or gives an error trying to communicate. Also, if you wrote down the 6 digit Insteon ID before deleting, you could try to re-link it by using "New INSTEON device" and inserting the ID again. (If those show the device exists, yes there is a way to get it to beep, or turn the light on/off repeatedly while trying to locate)

1) Is the light output affecting the sensor status? (light goes off -> sensor goes off -> program turns light back on) Test by controlling a different device or indoor light. 2) Is there another program controlling the lights? (you can search by right clicking in programs for usage of device 'outside / eaves') 3) If you are really controlling the lights using the relay output of the I/O linc ("Then I have an ISY program that tells the I/O to turn off my outside lights"); do you have "Relay Follows Input" selected in the device options?

Post your program.

On the NodeLink webpage there is. It is on the devices page. This is obviously a manual operation.

Wrong person. I was clarifying what we were talking about.