Jump to content
4loveofpunk

Alfred Workflow v3 and Smartthings

Recommended Posts

Hello all,

 

Just got my lovely v3 update of Alfred but I'm now unable to use Smartthings Workflow. I'm going to mimic what this person said because it's the same exact scenario.

 

"I'm able to authenticate to smartthings and when I'm done I get a message that says:

Success
Stopping embedded HTTP server - none.

After this I can't seem to access any of my devices via the "st" prefix. The device.txt file is also empty.

I have a v2 hub and am using the latest version of Alfred."

Share this post


Link to post

Hello all,

 

Just got my lovely v3 update of Alfred but I'm now unable to use Smartthings Workflow. I'm going to mimic what this person said because it's the same exact scenario.

 

"I'm able to authenticate to smartthings and when I'm done I get a message that says:

Success

Stopping embedded HTTP server - none.

After this I can't seem to access any of my devices via the "st" prefix. The device.txt file is also empty.

I have a v2 hub and am using the latest version of Alfred."

 

A quick look at Smartthings(https://github.com/PhysicalGraph/SmartThings-Alfred) shows me that you have to change the hardcoded "Alfred 2" paths and

tell application etc. 

In the workflow folder:

alfred/core.py

In the workflow itself(applescript top right):

set temp to "{query}"
set temp to do shell script "echo " & quoted form of temp & "| tr -d '\\r\\n' "

if temp is "" then
	tell application "Alfred 2" to search "st_login "
else
	do shell script "python get_endpoints.py"
end if

Change "Alfred 2" to "Alfred 3".

 

That's just a quick look, you gotta check what else is there that relates to Alfred 2.

 

Hope that helps :)

Edited by FroZen_X

Share this post


Link to post

I'm having the same issue. I've been using Smarthings with Alfred 3 for quite some time now with no issue, however this past weekend I just upgraded to the SmartThings V2 hub and I had to re-add all my devices and set it up from scratch. At first I tried to just re-authenticate via st_login but it didn't work. So I've tried removing the workflow and reinstalling it from github. I've checked core.py info / applescript and all verified they say Alfred 3 as I see the last commit shows that these changes were in fact made to the workflow anyway.

 

If I remove and reinstall the workflow and login, I authenticate just fine, however I get the same "stopping embedded HTTP server" popup and nothing happens after I run st_update and st_login says I'm already authenticated and trying it again doesn't do anything either.

 

So I'm running Alfred 3 and verified I'm using the latest SmartThings workflow that all mention "Alfred 3" in the various files. Frankly I'm not sure what else I can do here to get it working again?

Share this post


Link to post

It looks like a change in the SmartThings API caused this. I tracked it down and submitted a Pull Request to the SmartThings-Alfred repo that should fix everything - it's working fine again for me.

 

Pull request: https://github.com/PhysicalGraph/SmartThings-Alfred/pull/5

My updated version: https://github.com/ChrisHardie/SmartThings-Alfred/archive/master.zip

 

I hope that helps.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×