g1of4

I have one, and installed two at a friend's house. What would you like to know?

There is also the Ecobee to consider. I prefer the Ecobee to the Nest, and use it with several remote wireless sensors. I have it integrated in my home automation, but not directly through the ISY.

Logically you could use a state variable to indicate the location of the dog. When the dog is inside, going out you change the state to 1. Since it was 0 when the door was opened, you turn lights on. The next time when it is 1 and you open the door you can turn the lights off. The can be encapsulated in one program if you like, or separate programs. The challenge is if you need to open the door to yell at the dog to stop barking in between

v12 of the mapper was uploaded to the share tonight. I think I caught the elusive bug that was happening with update and removal of devices. No new features at this time.

New APIs and announcements today on the Echo and Alexa. Lighting API looks VERY promising. https://developer.amazon.com/public/community/post/Tx23PZD8E8GWHAY/Introducing-the-New-Alexa-Lighting-API

In trying to added nested program folder support I ended up introducing a bug where I end up trying to connect to a program URI that doesn't exist. I will see if I can get an update of the mapper out shortly with a fix. Sorry you've had trouble. C

@bgrubb1 - I am working on a mapper update that will include a save + add from file option. Fixed a couple bugs that slipped in when I added support for programs in folders. Haven't had much coding time lately, but trying to stay on top of it... I'm also working on 'hue discovery' to try and mimic what the echo does to discover to try and help with initial configuration issues. I will also try and pickup the latest emulator drop and check for issues. Cheers, C[g1of4]

Got a bunch of requests for the mapper, and got great feedback on a couple issues folks were hitting. It is hard to manage the requests, so I created a new post here: http://forum.universal-devices.com/topic/16337-echo-mapperconfigurator/and dropped a link. Please use the other thread for feedback, feature requests, etc specific to the mapper. I'll copy a portion of madmartian's post (if they don't get to it first ) over there so the full steps are covered.

Is there a build I can grab with notes somewhere? It looks like the beta forum post has 4.3.8. With respect to divergence: I was trying to understand from http://wiki.universal-devices.com/index.php?title=ISY_Developers:API:REST_Interfacewhy Z-Wave devices don't expose control interfaces over REST in the same way as nodes. Certainly there are differences in the broad capabilities of devices, but it would be nice to be able to activate say a z-wave switch (or in my case a lock) with a REST construct. It could be I'm just not understanding. I ended up wrapping my Z-wave device in a program to get the desired outcome and use the runThen and runElse. With the outlet linc, when I navigate to the URI for the node with DON, I get an empty properties response. Here: http://isy/rest/nodes/2A%209E%20B4%201/DON resultsin: <properties/> A few people have tried out the C# Windows Forms app I cobbled together to configure the HUE Emulator based on the existing ISY devices. I would like to add 'alternate spoken names' to notes, hence the ask for 4.3.9. Keep up the great work, and welcome to the SDK If you happen to figure out the forget + rediscover design pattern please let me know so I can add that too C.

Notes would be awesome. I was trying to figure out where to store mappings from ISY <-> HUE, adding as an item attribute would be great. Michael, any feedback on why there is a divergence of support over REST for Z-wave devices, and why I was having outletlinc issues with node URIs? I was able to control an outlet linc and a z-wave kwikset lock with programs in the end. C.

I wrote a quick and dirty 'mapper' that uses the 1.3 JAR. It reads off the emulator devices, and enumerated ISY programs, scenes and nodes. You double click an item to add/remove it. Seems to work pretty well. Alexa is doing great work with the light management now. The issue I ran into with 'not responding' was for an outletlinc. I couldn't get the REST API to work for either a node, or scene end point. I created a program with a simple then and else clause that changes the state and now Alexa controls that too. I haven't hit the 28 node limit, but with my mapper could test the Echo limits by adding the same device a bunch of times with different names. I ran into a similar problem controlling z-wave door lock state, but wrapped that in a program and voila, Alexa is locking the front door! I have some polish to put on the mapper (it has very little error handling and some proto-UI stuff) but would be willing to share. I am thinking about adding an automatic update to the Echo as well (forget ++ rediscover) but haven't decided yet if worth the effort... C.