kgividen

I'm looking for some android beta testers if anyone is interested. http://forum.universal-devices.com/topic/17870-beta-testers-needed-specially-android/

FYI I'm looking for some beta testers for a mobile app. Specially android beta testers. http://forum.universal-devices.com/topic/17870-beta-testers-needed-specially-android/

I would like this feature too. We could probably get away with three per device but can you make it so you could just add as many spoken names to the devices as needed? Right now it says one spoken name already exists but could it just add it if you say "yea I know".

I have two Echos talking to the Hue Emulator. It works fine.

When you do step 5 and get that link does it match the link you use to get to your REST server? i.e. if you click on that link can you get all the REST information? If not then something is wrong with the data you are entering into the form under "Get ISY devices". Additionally, if you want to enter it in manually the devices address is in the REST information when you hit the link manually. You can then use the "Add a new device manually" section if you wanted. One other thing to note is because of cross side scripting protection you need to open Chrome with web security disabled by closing all of your chrome windows and doing "open -a Google\ Chrome --args --disable-web-security"

What are the XXXX in your URL? Those shouldn't be there unless you put them there just for this. You can always hit the ISY rest server directly using the URL and get the addresses but that's exactly what the configurator.html page does. If you hit the URL http://username:password@ipaddress/rest/nodeswhere username and password are your ISY login creds and the ip address is your ISY IP address you should see an XML doc. Once you can hit that URL correctly put that info into the configurator.html page and it should load.

I run the bridge jar on windows but I don't see a reason it wouldn't work on a Mac. I use this on my Mac to configure it: https://github.com/kgividen/EchoBridgeConfigurator I haven't used the mapper but I believe that is windows only.

There are a few challenges with the current SDK for UDI vs. HUE but none of them are deal breakers in my opinion and will probably be overcome. kingwr summarized them a bit but let me see if I can add some detail and context: 1) Voice Commands. Right now you have to say "Alexa, ask ISY to turn on kitchen light". vs. Hue you can just say "Alexa, turn on kitchen light" It's only three words. Additionally, you can say "Alexa, launch ISY" Then you can say "Turn on kitchen light" and then "turn on basement light" without having to re-launch. Not a huge deal and can be coded in preparation for UDI to make a deal with Amazon to get rid of the three extra words. 2) Registering the Echo. Right now you'd have to have a web page (or mobile app or something) where the user would have to register their Echo with some custom web service. You would have to store the User Login (or maybe some unique Echo number) for that user somewhere and associate that with either their ISY portal or IP address that is exposed on the internet. This is so when a request from an Echo hits the web service you know which Echo it is and where to send the REST commands. VS. Hue where they don't have to do this...you can go into a "discover devices" mode and it uses I think UPNP to find all the HUE devices on the network and automatically adds them. Then they are available to control via the Echo. This is probably the greatest challenge. However, it really wouldn't be that hard to create a web page to do this and one advantage is you could have the user set a "spoken command" at the time they register and they could select which items they wanted controlled by the Echo. 3) ISY Current Advantages. a) Right now there seems to be a 28 device limit with HUE (although I haven't hit it as I'm controlling less than that). I don't see why this would be with ISY and the Echo if the above is finished. It would be nice to be able to edit the spoken command easily c) You could expose much more control because the entire power of the ISY REST interface would be exposed/available. Anyway, even with my simple code it would be close to having #1 done. A simple version of #2 could probably be done without a ton of trouble. Then UDI can work with Amazon to figure out how to eliminate the three words and get some sort of auto discovery thing going. I'm willing to work on this a bit more to help UDI out. Specially if any of you familiar with this are interested in teaming up a bit.

@kingwr I definitely agree with you. I've written this bridge (Lambda function) which is more of a proof of concept. It does use the new ISY portal from UDI but it could easily be modified if your ISY has it's ports exposed on the internet. The code isn't as clean as it should be right now but it does work. A developer account is currently needed to use it since some values are hard coded like username and password. It automatically connects to the REST server and gets all of the devices. It uses the name of the device as the spoken name right now. https://github.com/kgividen/IsyEchoBridge However, even though this works, the HUE bridge is a cleaner solution for the reasons you've stated above. Maybe if all of use with developer accounts start talking to Amazon UDI could do something similar to what they've done with HUE. Additionally, another thought is to include something like the HUE bridge on the ISY some way in the meantime and use a wrapper like what @ferdies has talked about before. That way it would be connected directly to the ISY and wouldn't have to be run separately. Although it does sound like there's a 28 device limit there. Anyway...like @randyth said it's been interesting playing around with this API.

@randyth I know you weren't thrilled about sharing your lambda function but would you be interested in sharing your Echo Intents and Speech patterns? I'd be interested in collaborating even on that level if you are. Plus I could share the code I'll be working on this week to get your input if you're interested. Michel has my email address but you could just email using my name here with a @gmail.com on it.

@randth and @Michel, I just found a getUser and get UserId method in the Java version of the echo appkit. I'll have to see how that might apply to Lambda nodejs functions but we might be able to use this to let the user "register" their ISY device. We could make a service they hit saying "register your device with ISY" and it would go add one of those unique IDs to a database so the portal knows it's them. Then return back some sort of code they can then go with a browser and register that device with the portal. Or something along those lines. We can cross that bridge when we get there but that does possible give us some options.

Right. The difference is the HUE has a special settings place in the Echo App. There is no custom place to set the user and password for additional apps. We will have to work with the Amazon Echo team to figure that out or leverage the Hue interface in the meantime.

Randy/Michel, you should be able to connect via the http module with the username and password but that will have to be hard coded in the lambda function unless we can pass it on from the echo some how. Randy, have you seen any way in the ISY developer kit where a user can configure or store a username and password? I don't see that in the API anywhere. You can display cards in the echo app but I don't see yet how we can make this work where a user can enter a username and password or key that would be passed to the lamda function. If we can figure that out or figure out a unique Id to be passed from the Echo we should be able to do this. I will be doing some basic testing with the ISY portal and my lambda function this week.

Check your URLs to the ISY. 401 means unauthorized so you're probably not passing in the credentials. The URL should look something like http://kgividen:myPassword@192.168.111.4/rest/nodes/25%203B%20F2%201/cmd/DFON/100 You have to have the "kgividen:myPassword@" piece in the URL so it can do basic auth to the ISY. If you don't have that then the HUE emulator cannot connect to the ISY. If you post your HUE console log here I also might be able to help.

Michel. I have a developer account and can help you out. I emailed you at your tech email address.

We might want to move this to the github issues page so as not to clutter up this thread since this is really meant as a thread on the echo/isy. Whichever is better... In any case...based on this console error it seems one or two things might be happening. 1) The URL does not look correct as I would expect it to say something like http://username:pwd@192.168.1.15/rest/nodes/ Hence the 401 which means bad authorization. You said you edited the JS to add your ip address, username and password but this shouldn't have been necessary if you used the configurator.html page. There are fields for these on that page. I would recommend using those. Additionally, if you open the chrome developer tools and look at the network tab when getting the devices you'll see the exact GET and the URL being used to make sure the username and password are being passed through. 2) The No Access Control Origin error is usually related to CORS and I wouldn't expect that if Chrome was loaded without the security. I've only tested this on the MAC so maybe there's something additional you have to do if you're using windows. But the URL still needs to be corrected.

Are there errors in the browser console?

I liked the idea of this page so I enhanced it for use with the ISY. You can get to it at https://github.com/kgividen/EchoBridgeConfigurator Here are some features new and old: - See what is currently added into the emulator (existing feature) - Delete devices from the emulator (existing feature) - Button to get all ISY devices from the REST API. (new feature) - Rename devices before adding them. (new feature) - Button to click and add ISY devices to the HUE emulator. (new feature) This way you can quickly add ISY devices into the HUE emulator and control them with the ECHO

I have an Amazon Echo and I also have an Echo Developer license and I've been looking at the API. I'm also familiar with the ISY REST interface as I wrote the mobile xControl app using that. I'm interested in writing an application for the Echo that will allow us to control the ISY without the HUE adapter but I don't want to duplicate anything if it's already being done. Are there others doing this right now?