MWareman

If in the U.S., I've had great success with Watchlight (alarm relay). They charge $120/year with (I think) a $35 setup fee...

No. Yes. The network module allows you to make outbound network requests from the ISY in response to events. It's not required for external devices to use the API to trigger events (etc) on the ISY.

Honestly, don't get rid of the Elk M1! It's one of the premier security systems available, and interfaces seamlessly with ISY like no other alarm system. You can add a wireless transceiver to it and wireless sensors to supplement or replace existing sensors.

No, it might not. Yet another reason to dislike iolincs connected to garage door openers!

Get a second ISY... [emoji14]

2FA is an acronym for 2 Factor Authentication. I always recommend everyone uses it - it provides very strong protection for your account. I'm glad you got things going!

If 2FA is NOT enabled, allow 'less secure apps' on this page: https://www.google.com/settings/security/lesssecureapps If you have 2FA enabled, create an 'app specific password' to use instead ontyour usual Google password and 2FA PIN via this page: https://security.google.com/settings/security/apppasswords Michael.

Do you have 2FA enabled on your Gmail account? You need to make sure to modify your Gmail account to allow unsecure clients, and make sure you are using an application password (if 2FA is enabled)

Check the other thread on this. I posted an example on how to post JSON with variable substitution. It works fine, as long as you don't use encoding (I suggest using RAW instead of 'URL Encode'.

I truly cannot see how the PLM losing all its links can be the fault of the ISY. The ISY connects over a serial protocol with limited command sets - the IsY would have had to either issue a reset command, or individually deleted the links (without deleting the links in linked devices). Neither of these scenarios seems plausible at all. The PLM losing links has been caused by bad power (spikes, brownouts, poor waveform) and the infamous capacitor failure that hits many PLMs. I myself have had a PLM loose links twice starting about a month before the PLM finally bit the dust on bad capacitors (about 26 months after purchase). I would be seriously suspicious of the power.... Losing all links unilaterally like that really is a symptom of something going on at the PLM level... not the ISY.

Seems we have all had to deal with temporarily supplying power to devices... [emoji14]

That's pretty much what I do, but I like living on the edge! Try an extension cord with an inline switch - so its easy to turn it off before switching devices!

You could always make a quick rig to attach power to each device in turn (safely!) and perform a reset on each device... That way you'll get rid of the now unneeded link records...

1) I wouldn't use a folder at all for this. Use time as the trigger for a program (in 'If'). Put a command in ''Then" to turn the scene on and a command in "Else" to turn the scene off. Folders don't 'run'... 2) Still not sure I totally understand. Do you mean the indicator lights on the SWL? It's not possible to have them show a different level that the load. I always thought you could adjust the 'backlight' level to dim them, but my SWLs don't appear to respond to that... Not sure what else to advise here. 3) So, a mechanical issue rather than an Insteon or ISY issue.. . I don't have any brown KPLs, so cannot advise here. Maybe others that have them can...

Folder conditions won't trigger programs to run. They allow programs to run. The program must have a triggering clause in the 'If' section. For 1, put the devices into a scene as responders (no controllers). Write a program to turn the scene in at 7pm, off at 10pm same day. For 3, maybe the KPL button is not a responder to the scene? Or the controlling device is not a scene controller of the scene that the KPL button is a responder to? For 2, thats tough. Its not possible to decouple the light status from local control on the SWL itself. The LEDs will always represent the status of the dimmer and (therefore) the load. You could separate the two (control the load with a micro dimmer) then work on logic to adjust the led position independent of the load. It would help to know what you are trying to do though.

I did. I stopped when they said it was only coming in some versions of the Genesis.

Smarthome have valves that are *much* cheaper, and I have (a 1" one) hooked up to my Elk... http://www.smarthome.com/smarthome-select-electronic-water-shutoff-valve-3-4-inch-12v-dc.html http://www.smarthome.com/smarthome-select-electronic-water-shutoff-valve-1-inch-12v-dc.html

Are you *certain* that # works in a network resource?? If so, which firmware version are you running? This would be news to me... It's well known for email substitutions (which get substituted in a blocking way when sent). Network substitutions are non-blocking - so # (to represent the triggering device) is not available in the network resource context. UDI has said that they *may* in the future be able to give us a checkbox to allow network calls to be optionally blocking, to allow this to work.... Personally, I'd settle for being able to use # in the 'Then' and 'Else' branches, and string variables...

Yep - I use all of that! Regular no noise notifications for garage door up and down, emergency notification when it's been left open. Alarm notifications that are persistent on the device until acknowledged. Doorbell sound when the doorbell is pushed... These things cannot be specified via email I don't think...

I believe Paulbates (above) has pointed to the same wiki page I would have pointed to. The ISY does not support string variables - so that's not possible. I do know it's on a wish list - but no timeline yet... if it's even ever accepted. The best you can do is a separate resource for each device you wish to notify... Set the message to 'Outhouse light is ${sys.node.11 22 AA 1.ST}' (change '11 22 AA 1' for the address of the load device). At runtime, the ${..} will be substituted for the formatted value ("on" or "off"). Caution though - if it's a dimmer it will try sending something like 80% if not full on or off - and the % will cause an error. You cannot do 'URL Encoding' to fix this either ('Encode URL' will prevent the substitution occurring because it encodes at save time - modifying the substitution string). If it's a dimmer, consider 'Outhouse light is ${sys.node.11 22 AA 1.raw}' and you will get a value from 0 to 255 instead - and no characters needing encoding. I've already raised a feature request to defer URL encoding to runtime (rather than rule save time) - but that's also still pending. Michael.

That's for email based connectivity - I think OP is asking about network resource pushing.... Very similar though. In the 'Then', select the network resource instead of notification. On a recent ISY firmware, you can now use substitutions. Make sure you don't use 'Encode URL' if you expect substitutions to work. Also, you cannot use any # references in substitutions. Michael.

This. You cannot set keypad lights directly from a program....

I had a Fanlinc go bad after working for two years - low and medium would work - but sending a direct 'high' it would shut off. I had to replace it.

Most browsers have now removed support for executing Java applets from within the rendered pane.... Try pulling the admin.jnlp from http://isy:84/admin.jnlp and then executing it locally outside of the browser.

If the admin console didn't learn about a device changing state, it means either their is a communication issue (caused the status message from the device to not make it to the PLM), or your PLM may be going bad, and missing messages. In the Admin Console, open up the level 3 log and toggle the light on and off a couple of times. Post the section of the log here....