blueman2

OK, I sort of have my Insteon Thermostat working with the Echo. I manually put this into the command for my Thermostat-Main device: /rest/nodes/<thermostat-device-ID>1/cmd/CLISPC/${intensity.percent} It works, setting my AC to whatever temperature I give to Alexa by saying "Alexa, set Thermostat to 74". However, the ISY divides the number you give it by 2 because every digit is 1/2 of a degree. So if I say "Alexa, set Thermostat to 74" it will set the thermostat to 37. As a work around, I can change the command line to write the ${intensity.percent} to a State Variable in the ISY. I then use a program to multiply this by 2, and using the 5.0 ISY firmware write the variable to the thermostat I am not on 5.0 yet so cannot confirm this will work but it should assuming V5 allows writing variables to a device. (??) (edit: corrected to multiply vs divide per LeeG message below)

Jay5, First, congratulations with the new addition to your family!!! Let us know how it goes. Get some sleep now. You will need it. Second, thanks SO much for sharing. I had no idea that Nest had an open API to access. This information alone is very valuable to me. Thanks for adding your work to the community! Blueman2

Excellent Barry!! I am traveling but look forward to getting your new version installed and tested when I return. Great news on the z-wave addition. You have done a fantastic job on documentation. Your background is really showing.

Not sure, but it seems to be about 25% per dim/brighten command. Not settable that I know of. But you can of course give an exact % to go to.

Thanks again, Barry. I am thrilled with the dimming!!! At least this shows variables like this can be passed to the ISY. I changed all the SET commands to CMD commands using update. Both seemed to work just fine, but better to use what is more standard. I have found the easiest ways to set a brightness level is: Alexa, set the den light to 60 or Alexa, brighten the den light or Alexa, dim the den light

Barry, noticed you had a 2.0.0 version up. I gave it a try, using the one time update button. I pressed 'next' as it evaluated each device. I did notice that it incorrectly thought some of my switches were dimmers and added intensity setting. I will track down the model of those switches since I am guessing it is related to certain model numbers. Also, after the update, 8 of my 29 device listings were not discovered by Alexa. No correlation I could find on which ones and why. I ended up switching back to a backup of my database. I did add a few new dimmable scenes into alexa. Alexa accepted the dim command, but lights only turned on or off. No dim so far. By the way, I noticed some scenes are given a CMD and others a SET command by your tool. Curious what the differences are between them. Fun to play with this!! EDIT: I GOT DIMMING!!!!! I am still unable to make my scenes dim, but I did delete and the re-create a lamplinc device on your AWS-config tool and sure enough, it dims!!! I tried 10%, 30%, 53%, 100%, and they all worked. BARRY!!! You da' MAN!!!!! Now to figure out why the scenes are not dimming. I think I will just delete everything and re-create from scratch, and see if that helps.

You are up kind of late on the east coast! Thanks for the update. I cannot wait. There are really only 2 things that are missing for me: setting temperature by degrees for my HVAC, and dimming lights. I will be curious of the dimming capability can at some point be extended to work with thermostats for a specific temperature.

Holy crap!!! Dimming!?!?! Please don't make me stay up all night wondering how you did that!!!!!

Working just wonderfully, Barry. Once again, thank you for sharing your work! Bob

Doh! I forgot to RTFM. Beautiful!! More than I hoped for in terms of custom endpoints. I will start using now and let you know how it goes! Bob

Thanks, Barry. Just installed 1.1.82 and all is working perfectly! What does the 'list of control addresses' refer to? I did not understand that reference.

My only aversion to "cloud solutions" is that they are typically just an excuse to force the consumer to put 'some function' on another computer so that the owner of that computer can charge you a monthly fee. Often, the 'some function' does not need to be remote and would work just as well, probably better, on a local computer. It is done remotely just to generate fees. I think UDI feels the same (prefers not to use portals unless truly required), but is trapped by Amazon into using a portal solution. It will probably mean monthly fees though. The size of those fees will determine whether the portal is worth it. But I am preparing myself to continue to use my own bridge and keep all functionality local on my LAN. Time will tell which route will be better, but I urge everyone doing development today not to slow down or wait for a portal solution.

Frankly, I would leave it as is for now. I only have one custom device for now anyway. If I add more later, I can either create an endpoint to distribute the commands or I can just change the custom IP in the .ini and add the other device. But as for the 'update' bug in the custom settings, it would be nice to have that fixed!!! Also, if it is fixed,then I can manually adjust the http command to whatever I want in the URL on and off boxes. Thanks again for being so kind to share your work with us. I really appreciate it!!

But you also need to include the line for specific folders to show. For mine, it is: Scene Filter = Scenes, Interior, exterior

Barry, With regard to Custom devices. I have enabled it with the 'Custom Address' in the .INI file. What if I need to talk to several different custom end points? I tried editing the default custom IP:Port in the On URL box and doing an update, but that just appended the old default to the new address I edited. Is there another way to add multiple custom devices? I guess I could change the .INI whenever I needed to add another custom device. Since I would rarely do that, this would probably work just fine. I was going to use this to power on/off my amplifier that accepts http commands. EDIT: I realized that there is an issue with updating any custom device. If, for example, you change the name and hit update, it will append the default IP address again. is this a bug?

Ferdie, You need to include the Scene folders you want to display in your .ini. I had the same issue with no scenes showing up until I edited the .ini file.

Michel, Is there a thread or topic discussing the details of what can be done with this, what is required, potential costs, etc? For example, will this allow dimming? Perhaps customer phrases beyond 'turn on' and 'turn off'?

Thanks, Barry. 1173 indeed works perfectly!!! As for the Mikrotik, I recall these guys made bare boards that were out of this world. Some of the best h/w out there. But I am a long time dd-wrt guy and am not sure I am up for learning a new OS, especially one that is as complex and powerful as the one provided by Mikrotik! Also, I noticed you have some info below your application's main window (some words on the left, a list of all discovered devices in the middle, and a 'help' text box on right (until you hit okay!). Just curious what those will be / are used for?

This is very cool. It would be great to get the HVAC item working as a 'proof of concept'. In preparation for this, should I go ahead an install stunnel on my RPi? Let me know if/when you need someone to beta test. Your current configurator with 2 copies of the 0.4.4 bridge is working perfectly and rock solid on my RPi2. So I need something else I can break!

Just tried it. I only copied the .exe file; I hope that is OK. When i tried to move, does bypass the OK dialog, but when I select the new bridge from the drop down, it crashes with the message "Stop Statement Encountered"

Yes, I can see how you got there. But you seem to have done a very good job with the red lettering 'select emulator' that shows up near the bridge selection area to make it clear this should be filled in. If the OK dialog is removed, it will still wait for your to select a bridge, right? And if you do not, no harm since it does what you really want in terms of selecting least used. I think you wrote the software very well, so that it does not need the OK dialog, but I certainly understand why you put it in. I would prefer it be removed though. Not a big issue, however. I was just reading about your background on your web site. Damn impressive. And wonderful work on this project. How far along are you on the "Alexa, ask Sarah to..." functionality. I did not see any software associated with this yet. But I am probably just not up to speed with what you are doing there.

Oddly, it turned out that using my RPi wireless was the issue. If it connected to the right WAP, it was fine. If not, it did not work well. So I just went wired for ethernet and all is well. Barry, your configuration program is wonderful. Does everything I want. Only minor change I might suggest is to remove the need to press "OK" every time you move a device between bridges. I had to move 30 devices, and hitting the extra OK key each time slowed things down. Great work, Barry.

Barry, Thanks to the GREAT documentation you have in your AWS_Config tool package, I was able to get my RPi2 up and running with 2 emulators (all I want for now). I added a device and it works perfectly. Just as responsive as the emulator running on my server tower. However, after doing MOVES of several devices from my old emulator running on my PC, I am finding that Alexa no longer discovers any devices on my RPi2. I have rebooted several times. Your configurator sees all the devices, but Alexa only wants to discover devices on my PC, not the RPi2. I even turned my PC off, but still no joy. Any ideas?

Barry, What Linux are you using on your RPi2? Raspbian? Also, are you using wired or wireless connection? Some people say one will work while other will not. I tried to get an older version working on my RPi2 a few weeks ago and never figured it out. I am going to try again and wanted to duplicate your setup as much as possible. I do have an FTP server for uploads, but I think it would just take too long to upload a 16G image!

Fully agree. And since I did not see a thumbs up icon in our library..... ...../ ) .....' / ---' (_____ ......... ((__) ..... _ ((___) ....... -'((__) --.___((_)