MWareman

It should work. But there will be a short activation delay. You also will have to have the dimmer trigger programs for the functions you want - dimming will certainly be problematic to implement, or even not possible.

My engraver hasn't had much use, because I had a test setup in my living room. Not wanting to insist on everyone wearing laser goggles, I'm waiting until my basement craft space is finished.... A couple of weeks to go!

Take a look at post #6 above. Paul linked to the Wiki page on setting this up. Michael.

I do PHP as a cgi script under Apache. I've never done Python, but I'm sure you can execute the Python script from a small php script called in this way.

I use Pushover for all my user directed notifications. Highly recommended! I also tried most out there for writing the Wiki article linked above but ended up sticking with Pushover. I like that the network resource can send to multiple devices, use different icons for different events, send custom sounds etc... It's also cross platform...

You cannot run outside scrips on the ISY itself. It's operating system is not designed for general purpose use. Many on here use a device like a RaspberryPI, and have scripts by executable via a network call from the ISY.

I don't think the Echo API allows this. You could try creating the multiple programs though with these spokens... "volume down 1" "volume down 2" "volume down 3" "volume down 4" ....etc I don't know if it would work though...

Also, remember that when the sensor switches 'Off' - it will also cancel the run (and start running the Else clause - but you have nothing in this clause).

The fact that you get two, but your wife only get one seems to indicate that the first activation got cancelled after sending your notification, then run again - sending you a second and your wife her first. Try switching the notifications around and see if the problem switches...

Bear in mind, each time the motion sensor is triggered, it will terminate the program and restart it. Could you be having two motion sensor triggers 5 seconds apart?

I wouldn't ever have a geofence crossing automatically operate the door. Chances are, your mobile device thinks (for a moment) that the fence has been crossed and operates the door. Then it thinks it's crossed back, sending the signal again. This results in a small door move. This is not at all unusual with geofencing. It's not really suitable for automatically opening garage doors!

Yep. They just allow non-professional to create an account. Well they have since I setup mine - 14 years ago...

7) Without the network module, inbound requests to the REST API (mobile apps, for instance) and accessing the web interface all function normally. The network module enables making outbound requests from the ISY - for instance sending requests to IFTTT, Pushover, a local WiFi IR blaster.... etc I should also note that subscribing to the ISY Portal also gives you free use of the network module for the duration of your portal subscription. This is because the ISY Portal allows you to easily receive inbound triggers from IFTTT, and UDI wanted to allow the ISY to trigger IFTTT. This integration uses the Maker channel on IFTTT..

I think a few on here have one of these! (I don't have one, yet. It's on my shopping list though...)

This. I've never had an issue getting software and documentation from their website as an end user. I've even got support contacting them directly (purchased the Elk from smarthome.com).

I think Michel told us they had submitted it something like a month ago - but it's up to Amazon when they make it live, with little or no notice. I don't think there is much UDI could do about this...

That's what many do, but I seem to remember ISY has difficulty with a common (was it dnsmasq?) DNS forwarder used on many routers....?

io_guy has written a program called dsclinc to integrate DSC based alarms to the ISY. It runs on a Raspberry Pi. Plenty of people report success with it - but (IMO) nothing beats the native integration of the Elk M1 system.

I think at this point, Michel is going to have to comment. I seem to remember there was a way to kill subscriptions as well - if that's the problem. But how long they stick around in an 'Expired' state I don't know. Architecturally, there may be an issue with establishing a subscription on each tab.... Probably best to avoid that! I've never really dug into it.. Reusing the socket is from the SOAP subscriptions.... I don't think it's used at all for websocket connections.

I use pfsense as my nat router - and get ddns service thru dns.he.net. The only cost was the hardware to run pfsense on (I use an alix system)

Does a call to /rest/subscriptions show anything?

Elk thermostats are not under /rest/nodes, they are under /rest/elk (see the documentation at http://wiki.universal-devices.com/index.php?title=ISY_Developers:API:REST_Interface#Thermostat_Commands for the commands needed). Integration with Alexa only uses /rest/nodes to look for thermostats.

I use dynamic DNS (in my router), and then configure Mobilinc to use the ddns name. It's worked flawlessly..... No need for either Portal for this to work.

Here is one... Has a 500A fuse kit as an option... It has 10% thd though... http://www.theinverterstore.com/4000-watt-low-frequency-pure-sine-inverter-charger-230v-50hz.html

Get a RaspberryPI? (Almost) anything will become possible...