New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Smartthings Integration: Unable to complete SmartApp install #29303
Comments
As an update, I tried to change this to use Nubucasa for remote access vs my own (duckdns addon with a forwarded port) and it worked just fine. The app installed and worked. One thing to note, my base_url orignally has: https://somedomain.duckdns.org:[someport] |
Ok- after some debugging, it appears there is a bug when the base_url has a port number attached to it. When my base_url had a port associated with it, I got the original error in this bug report. I cleaned up the ST integration config and then when I changed port forwarding around to use 443 and therefore have a base_url: https://somedomain.duckdns.org/ everything works fine. |
Yep, SmartThings expects it to run on a standard port. Glad you've figured it out! 👍 |
Update based on learnings of: home-assistant/core#29303
created a PR to update documentation: |
* Added commentary about base_url port requirements Update based on learnings of: home-assistant/core#29303 * Update source/_integrations/smartthings.markdown Co-Authored-By: Franck Nijhof <frenck@frenck.nl>
Home Assistant release with the issue:
0.102.3
Last working Home Assistant release (if known):
none
Operating environment (Hass.io/Docker/Windows/etc.):
hassio
Integration:
Samsung Smartthings
Description of problem:
I'm using my own SSL certs and base_url and attempting to get smartthings integration working.
I've created an access token, inserted it into the integration and see the SmartApp created on the classic version of the Smartthings app. When I go to install that app, I get the 'Something went wrong. Please try to install the SmartApp again' error message on my phone and a pysmartapp.errors.SignatureVerificationError (see below) error message as the webhook is called.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
The text was updated successfully, but these errors were encountered: