I had the same issue and found a fix! Not sure if you still need help, but here it is. posted on youtube.
Graham Donoghue5 months ago
Try this worked for me on my samsung soundbar. Turn soundbar off then press and hold play/pause button on remote until soundbar display shows init ok. Your soundbar should now be reset. Now go through normal bluetooth set up on your tv and when you turn your tv off then on again it should auto connect to bluetooth soundbar. Hope this helps.
Sorry, but it's not a true solution to have to reset your customized settings each time that this issue rears its head. The issue shouldn't arise in the first place. And as for Samsung's repeated responses indicating that a resolution to this issue is considered to be a "feature request", well shame on them for that. We're not asking for bonus settings on the device. We're looking for a resolution to broken functionality.
I have the same problem with my QN65Q70R TV and HW-MS650 soundbar using an optical connection. There doesn't seem to be a pattern, and the firmware is up to date. Obviously, there is a Samsung problem.
Hi I had the same problem so I registered to tell you how I fixed it.
I realised the sound bar dropped connection from the Samsung Tv after 10 seconds of turning the tv on. They sound bar stayed on though. I notice this happens when there is a power cut.
What I did was unplug and plug my tv and sound bar from the mains. Now the connection is stable until there is another power cut.
Hope it helps.
Same issue here. I have a Samsung KS8000 with a HW-K650 soundbar connected via digital optical. Every time I turn on the television, I get an echo because the tv defaults to the tv speakers (and the soundbar comes on too). Both devices have current updates.
I just wanted to come in so I can get updated with the solution because I've been dealing with this since I bought my TV and sound bar. I finally did a search on this problem because I was fed up and it looks like this is a problem with other people too. I can't believe Samsung hasn't fixed this yet.