31-10-2022 12:39 AM
13-11-2022 07:07 PM
Same problem here! Have you found a solution?
21-11-2022 08:09 PM
Similar problem here - trying to register Samsung m5550 soundbar and getting error 15-100 at point where registering with Samsung, having provided Wi-Fi credentials. Signal is fine, credentials are fine. Is there a way to formally log the problem with Samsung?
29-12-2022 02:34 AM
Same here... ridiculous
30-01-2023 11:30 AM
Any fix yet?
07-02-2023 08:09 AM
I was having the same issues and then noticed the password for my internet was defaulting to something old.
as soon as I corrected that it worked
30-04-2023 12:34 AM
Why did you mean by "corrected that" exactly? Because my problem may stem from the same thing.
My Q990B Soundbar was well connected to Smart Things and worked perfectly!
Then, after changing the password to my wi-fi, I got disconnected and havent been able to register it ever since.
I've tried everything - 2,4 and 5 network, changing wifi names and passwords, reinitializing the soundbar, reinstalling the Smart Things app, disconnecting my soundbar from my Samsung Account, WPA settings, even registering from a friend's iPhone (mine is SamsungAndroid and he got the same error).
The app detects the soundbar, it even connects to it via bluetooth but fails during the "registration to Samsung account" phase.
Please help - I don't have full functionality of the bar 😞
And I was so happy with Samsung and recommended it to everyone 😞
29-06-2023 08:33 PM
I have th exact same issue with a Q990C and a Verizon FIOs Wi-Fi router
30-06-2023 02:02 AM - last edited 30-06-2023 02:03 AM
I ended up contacting samsung technical support through the smartthings app (contact us > error reports) and they asked me to run some diagnostics, send them the results file and after a few calls of them remotely analyzing and walking me thru some config changes (that didn't work) and tests, they escalated the issue and one day it started working and I got an email asking if the issue is resolved. Been ok since, knock on wood.
20-09-2023 09:50 PM
Same issue here. Has anyone found the solution yet?