OK. My Samsung account uses same e-mail address with this forum account.
Enabled support access to “Until turned off”
I have only one hub, and its name is ‘SmartThings Station’
I accepted invitation and enrolled those channels from Jan 31 2023 to Feb 2 2023.
I did delete my smartthings account data and reset hub on Feb 3 2023.
Hi, @ijoesj
Sorry for the delay.
Following up on this, the team mentioned that in all these cases it seems the invitation was already accepted but you don’t have the corresponding permissions.
They also said there will be a fix released to avoid this issue but there’s no ETA yet for it. Once I get more info, I’ll let you know in this thread.
I’m glad to hear that there is a fix coming for this issue.
I’ll wait for the fix to be released, thanks.
I have the same problem after having my hub reset, doesn’t want to show the webpage to accept invitation or straight up telling " you do not have permission to access the required invitation "
I’ve contacted support where I got transfered here and there but they still have.no clue at what’s happening, so they said they’re transferring my case to engineers team.
Could you perhaps help with that?
SmartThings support access is granted on my account.
Hi, @romain
Did you accept that same invitation before the Hub reset?
Hi @nayelyz
Yes precisely, and something I realized recently is that I am able to successfully subscribe to channel invites and install drivers for any never subscribed links.
So basically all the drivers and channels that I was subscribed before the hub reset, are inaccessible now. But it seems that I can still subscribe subscribe to anything new.
This is a bit of a problem for me since I want to install what I had before the reset. And I can’t find other similar drivers since, before the reset, I had many channels and drivers for one device to test them. So I don’t have much options now.
Thanks for any help you can provide!
Thanks for the confirmation, @romain. I shared above the following:
I already pinged them again to see if we can get more info.
Wich is weird because I just receive an email from Samsung asking me for the second time now, that I need to reset my account Samsung account ) which I did the first time already. And then create a bunch of logs from hub
They pretty much asking me to do exactly what I just djd
In my last email to support I proposed that they completely remove my SmartThings account themselves since I’ve already did it to no avail.
And so I will be sure that this can’t be the problem. And I am actually thinking the problem might be there but some how the subscribed drivers or channels information stays somewhere that doesn’t disappear after account reset.
Perhaps the reset of the hub and the Samsung is not enough
I’m out of idea
Hi, @romain
I don’t have more details about why this is happening, I only know that creating a new account to start fresh has solved the problem for others, so, it seems some cleaning is needed.
Can you please share the ticket number to see if I can check that ticket with Customer Support? We’re different teams, so I’m unaware of what they have mentioned or investigated in your case.
I’ll try to reset everything again a delete my SmartThings account data.
I am not sure what is the good ticket number, either this: #92015538 or this:1454754. Thanks a lot for your help.
Greetings,
I too find myself unable to roll back my drivers after I accidentally quit smartthigs. I do not consider acceptable as well as it is impossible for me to do, the creation of a new account. We urgently need to fix the driver recovery after reset problem. best regards
Hi, everyone
The engineering team mentioned the fix for the issue entering channels after the Hub’s reset was released today, so, you should be able to accept the invitation to those channels again. Please, let us know if this works for you.
3 Likes
Reactivated everything. Channel invites are now working again. One major flaw and problem remains. especially the inability to make a personal local backup in case of these incidents. Thanks for the fix of course.
I am having the same 403 issue with: