Skip to content
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

Invited user cannot create new locks, users or keypads #92

Closed
runderwo opened this issue May 8, 2018 · 3 comments
Closed

Invited user cannot create new locks, users or keypads #92

runderwo opened this issue May 8, 2018 · 3 comments

Comments

@runderwo
Copy link

runderwo commented May 8, 2018

A user that is invited to my SmartThings account is unable to create new locks, users or keypads either in SmartThings Classic or the new SmartThings app. There is a fullscreen error in SmartThings Classic saying "Something's Wrong. We can't load your screen right now." with a 'Retry' button that does not improve the situation. In the new SmartThings app, there is a toast complaining about a server error.

Unfortunately, since the user is on a Samsung phone, she is also unable to log into a SmartThings account that is separate from her Samsung account (due to the Samsung Connect system app that cannot be disabled without root, while rooting the phone is impossible since it's a carrier model), so we cannot just share the master account as a workaround (as undesirable as that would have even been).

@ethayer
Copy link
Owner

ethayer commented May 9, 2018

This is a platform issue, not a LockManager issue.

A work around is to publish all child apps so that they are available to all users connected to a hub. Apps that are not published, for some reason, are only available to the user who published them.

@ethayer ethayer closed this as completed May 9, 2018
@bryanyork
Copy link

Publishing all apps didn't fix this. Any other ideas?

@runderwo
Copy link
Author

@ethayer Can you please just try it and see for yourself? Alternatively can you publish the exact workaround steps and/or add them to the documentation since it seems that we are all doing something different?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants