mlamoureux

Yes I noticed it doesn't work with the latest Alfred. Jason, have you considered joining forces with these guys, who also have a Python implementation of a NEST library? https://github.com/johnray/Indigo-Nest-Thermostat-Plugin

Wasn't hard after all, pushed some updates which now allow for filtering during the steps.

That ability is highest on my list to get working. I have yet to find a example workflow to model it after, but I haven't looked very hard. The devices you use the most should eventually float to the top of the list due to the way I name them in the XML. It's a built in feature of Alfred to bring the common items to the top. I do not have as many devices as you do, and I heavily use variables and action groups to group my macros together. Glad it works so far, I'll post updates as I have time and improve it.

Okay I posted an update. I tested the login and password and it seems to be working. Sorry that I was lazy and did not create a command to configure the login and password parameters, I'll do that in a future update. For now, you will need to install the plugin, configure your server, then manually edit indigo.config to set your login and password. Be sure to set AUTH_REQUIRED="TRUE". Let me know if you find any issues, I'm sure there will be a few link: https://github.com/mlamoure/Alfred-Indigo-Workflow

Mike I plan on posting a copy of the workflow in the next day or so that supports authentication. Right now I'm building it where you would provide the login and password to a configuration file. Will let you know when I post it.

I completely forgot that Indigo allows password protecting the web interface, and I didn't realize it also applied to the REST URL's that I'm using. I'm going to add this to the known issues and I'll consult with the indigo guys on how to authenticate to the REST URL's. If I do come up with a solution, it will likely involve saving the password, which might be in plain text until I learn to use the Keychain (I'm not a OSX developer). I personally do not password protect my indigo since I do not expose it to the internet (I use a VPN when I want to control from home). Sorry for the trouble.

The latest version of the workflow now contains some checks to see if the scripts have the appropriate permissions to execute. Also I've improved logging which can be turned on by going to the workflow directory and editing the "indigo_common_functions.sh" script and changing DEBUG=TRUE

Would love to help, thanks for testing it. I think I stupidly posted the workflow with both debugging and my server pre-configured. You should be able to type: "indigo server http://YOURHOSTNAME:YOURPORT" then hit enter. Alfred should pop right back up again, with the keyword "indigo" pre-typed, and three options available: Devices, Actions, and Variables. Alternatively, entering your server into the server.txt will also work. You will know the plugin is connecting to your Indigo correctly if you hit Devices, and your devices dynamically load into Alfred. If you are getting the querying message, make sure you do not have a "/" at the end of your URL (I plan to fix this, but right now it makes the plugin not work, Indigo is finicky about their URLs). If you are still stuck, please send me your log.txt in the workflow directory via private message, or email to mikel@mikelamoureux.net

I've created a workflow to control a Indigo Home Automation Server. The workflow allows the user to control devices, action groups, and variables from Indigo. Common use case is to turn on an off lights, or control volume levels or A/V properties, etc. Hope to extend it to include NEST and other thermostat controls. Screenshots and a link to the workflow and source can be found on my blog. These forums were a big help in figuring this out, so thanks to everyone for the contributions. Mike