MWareman

Also, just get the $50/2yr ISY Portal - and you'll get ISY to integrate with Alexa without the skill... All the benefits of ISY with all the benefits of the Insteon Hum - no Hub required.

ISY or Homeseer on the ISY forum. I say ISY - but then I might be biased. Safe to assume most are biased to ISY around here....

I'm sure it can be retrieved from the API - its just not documented... I'll take a peek this evening.

I do agree their tech support model is the same as many other large companies - which makes it hard for smaller integrators (and home users). The problem is, they sell direct (and via places like Amazon) as well, without providing support to those purchasers. Their policy is 'get support from your var' - but when your place of purchase was Amazon that's not possible. Try getting tech support for an F5 or a Cisco ASA (I could go on and on!) that you purchased from eBay!. Anyway, a much more reasonable review. I appreciate it! I hate it when I see a strong negative about any product without any details of the source of the opinion. I'm going to have to look at the Ruckus devices now!

My 2 programs do this: Garage Monitor - Closed - Alert - [ID 026C][Parent 0052] If Elk Zone 'Garage Door' is Violated Then Set Scene 'Main / SC - KitchenKPL - B' On Else - No Actions - (To add one, press 'Action') Garage Monitor - Open - Alert - [ID 026D][Parent 0052] If Elk Zone 'Garage Door' is Normal Then Set Scene 'Main / SC - KitchenKPL - B' Off Else - No Actions - (To add one, press 'Action') 'Main / SC - KitchenKPL - B' is a scene simply containing the KPL button as a responded (as LeeG stated). My garage door sensor is hard-wired to an Elk zone that I have named 'Garage Door' (entry 2 type in my case - so opening the door triggers a longer than usual entry timer). Michael.

May I ask what is it about the devices and your direct experience that would lead you to state this? I know a couple of people that say they are junk, and further research revealed they felt hard done by on their Kickstarter - and it was a reflection of that experience rather than the final products. This opinion goes counter to the experience of many.... I know many professionals that use these. Those that have actually used them have relayed nothing but good experiences to me. And I use them myself, with great success.

I've often thought the user should be able to 'uninstall' a module - leaving it still purchased in the UI... So it can be installed again later if wanted again...

Sure! It's pretty straightforward though.... My transformer supplies 24vac (some are 12vac, others 16vac - you'll need to get a relay with an appropriate voltage coil - make sure it's an AC coil!)... There are two circuits - transformer to relay coil via the bell push - and a second circuit from transformer to bell via one set of n/o relay contacts. At that point - the bell push works properly, ringing the bell - with the addition of a relay click. I then wired the other relay n/o contacts to my Elk (could easily be an iolinc).

Yeah... No 'spoken' words added for any locks or alarm system controls - except one on a program that locks the doors and sets the alarm. No way to unlock or disarm by voice....

3.3.10 non-pro cannot connect to most SSL servers now - because it only supports ciphers that are now considered so insecure that most web sites have now removed them. To use any of the network notification services you'll either have to upgrade to a 994 - or setup a reverse proxy to handle SSL for the old ISY. Michael.

Not currently (I want this as well). I know it's on UDIs features to come list (string variables that can be substituted).

Pretty typical for Amazon...

More than once, my Alexa has piped up over dinner to announce "I don't understand what you just asked me" when nothing was asked of her.

I put a dpst 24vac relay between the button, 24vac transformer and bell, allowing me to have dry contacts that (in my case) trigger a non-alarm zone on my Elk, but could equally trigger an iolinc. Since I had the Elk already, it cost me less than $3 for the relay...

I love the feature as well - my Elk pings me when it's armed with just a notice, a non-urgent 'ding' when it's disarmed, and a siren if it's set off - all in the same app profile with appropriate icon. Same with my garage door. Simple quiet notice for open or close - but an audible notice with an attached picture from my camera if it's left open.

My Dot is showing with an April 8 delivery date... I hope it dosnt slip...

I have 16 Pushover 'Apps', and a few weeks ago I tried adding another one, and got a message I was at the limit. However, I just tried adding one more just now, and it let me... Not sure what that means though. Michael.

I do Pushover by API - and have defines separate apps (each with their own API key and icon) to group them.. In fact I hit Pushover app limit... Not sure how to get around that...

Welcome to the ISY world @bgav! It's truly sad that they are simply shutting it down - no refunds or recourse at all - based on that fact that the 1 year warranty is over for all purchasers... Wow is all I have to say. While not a Revolv user myself it does show why a cloud-only (or even cloud-first) product should be avoided at all costs if you want to maintain the (significant) investment that home automation takes.

Have you seen my Javascript Websocket example at http://forum.universal-devices.com/topic/15248-problems-creating-a-websocket-connection/page-2?do=findComment&comment=150499 ? Granted - it runs in a browser - but I suspect you could modify it to subscribe to events for other use cases. (This is an example page designed to be served directly from ISY.... and the JS executed from the connected browser. This is because of the authorization header and security requirements of WebSockets. In a non-browser implementation - the var ws_host = "wss://" + isy_host would likely have to be changed to var ws_host = "wss://username:password@" + isy_host Michael.

Reach out to io_guy and see if it can be integrated into nodelink.... That way the MyQ stuff will be represented as actual nodes rather than variables....

Could it be that the secondary button nodes don't have link records back to the PLM until they are in a scene? Maybe only the primary node is linked by default... Even a scene with one device adds a scene link so the PLM is notified. I'm thinking that without being in a scene secondary buttons likely won't report anything to the PLM.

Can I 'Like' this more than once???

I do exactly this with my Elk sensors. All can be used to trigger programs on ISY, as long as you have the Elk module installed and configured.

I have a (Maker channel) skill defined as 'Goodnight' - calling my 'Goodnight' program (via the portal integration). 'Alexa, trigger goodnight' works every time. It's pretty much my only skill in common use.