Does anyone have smartthings devices integrated into homeassistant without using Nabu Casa? I have just 2 devices that are solely on smartthings (door lock and garage door opener) been trying for several days to enable secure remote access to get smartthings and HA integrated but none seem to working.
I forwarded port 8123 and have a duckdns domain but got error because it wasnt SSL.
Tried added “http” config into my config.yaml with Letsencrypt and was unable to access my HA GUI because http is no longer supported?
Just wanted to see if anyone has any other workarounds?
Running Hassio/supervised HA on docker on my OpenMediaVault 5 server.
Hi
I had a smartthings hub connected with just 2 door multi purpose door sensors.
I don’t remember it needing Nabu Casa.
It’s integrated as a webhook.
But I have long removed the hub and put all my zigbee on Deconz/ConbeeII.
I’m running HA in Docker on an Ubuntu 20.04 NUC and use the ‘default’ SmartThing integration. I also use DuckDNS to access my HA instance. Going thru the default setup process here: https://www.home-assistant.io/integrations/smartthings/ worked fine for me.
Worth pointing out that when I upgrade to either .111 or .112 it ‘broke’ my integration, so I simply removed it and re-installed and it’s back and working fine now. Also worth mentioning I actually have two of these hubs running - one at ‘Home’ and the other ‘Work’ and haven’t had issues (knock on wood).
Sorry I miss typed above…I meant “mydomain.duckdns.org” I have my duckdns add-on configured with a duckdns domain, but when I add the http config to my config.yaml to set the baseurl, I got an error saying baseurl is depreciated and couldnt access my HA GUI until I took out the http config.
Depending what version of HA you’re running, baseurl under the http section has indeed been deprecated. Do you not heed the warnings? Go read the config docs for the http component of HA and you’ll see what needs to be done to fix that.
I’m running 112.4 and squirtbrnr is 100% correct, these have been changed (http: and homeassistant: sections of configuration.yaml) in the last release.
My http: section looks like this now:
and the relevant portion of my homeassistant: section looks like this:
Definitely worth looking into the docs to understand more about the changes. HA is an ever-upgrading environment, so realize it’s difficult to keep up sometimes
Thanks, those shots were helpful. Able to access externally with my duckdns domain with browser.
Now I deleted the integration with my nabucasa. Restarted the server, Then try to add ST again through integrations, it generated the webhook fine with my duckdns domain. I input my ST token into HA, I get redirected to the ST website to log in, after I log in however, I am met with this error:
Not sure if this is a HA error or a ST error. But Its farther than I was able to get before (when it stopped me from generating a webhook)
If I restart server and re-enable my nabucasa and try the same actions, it adds without any issues.
I’m no expert, but I believe it’s either / or. You either you use WEBHOOK or use the TOKEN. Personally, I went the token route and by following the instructions on the integration page (https://www.home-assistant.io/integrations/smartthings/) was able to get it going.
I think I had that issue once before, when it dropped off, I either ended removing it removed any file in the /config or .storage folders and I created a new myapp on smartthings.
I had this same issue. After many hours of troubleshooting… found that there was a file /config/.storage/smartthings that needed to be deleted manually. Thank you @Harry13 for the suggestion.
