Also experiencing this very issue. Have done a reset by holding power, re-setup etc. Hopefully that works.
Shame they removed the 1 min turn off timer too in the same update.
Mar 6, 2018
Curious about a solution as well.. I updated to 1.3.3 yesterday and now this automatic power-on "feature" is really annoying and I cannot seem to disable it anywhere 😞
Since the update to the v1.3.3 is a few weeks old and no official statement or software update is available, we must deal with this.
At first: for all new users seeing this thread! Do NOT update to v1.3.3 through btu.bose.com or BOSE Connect App, except you like the “feature”, that the Revolve and Revolve+ gets powered on, when it finds a known Bluetooth device.
My experience during the last days and weeks hardened my first thoughts, which I posted here three weeks ago.
This behavior comes through the newly introduced feature in v1.3.3 ("The user can now power on the puppet (companion) speaker through the Bose Connect App"). It is not the user. It is the Revolve which powers on and then reconnects to the device.
There are three solutions for this:
I believe I’m speaking for all of you, that this new “feature” is totally frustrating. We want our “OFF” state back! Now!
Aug 25, 2017
Thank you for reaching out. In the most recent update, we enabled a feature that allows any previously connected speaker to be powered on remotely via the Connect app. This feature is primarily intended for ease of use when creating a stereo or party mode pairing, but will also work when you drag to connect any compatible speaker within the app.
Additionally, I've passed along your feedback in regards to wanting to be able to disable this feature, I'll let you know when I have new information to share.
I hope you're all doing well,
we understand the new feature. New features are always nice, but the implementation is in this case very faulty. It seems that it has not been tested at the development site at all.
Instead of having the ability to remotely turning on the Revolve through the App it starts by itself when it finds any previuosly paired device. This is without user interaction. And to be clear: I don't use the App (due to non-availablity on Windows).
I believe I speak for all of use, that we want the old behaviour back (OFF is OFF) and do not like that the Revolve awakes and shouting out ("Battery eighty percent. Connected to Surface. Connected to Surface and FireTV Stick") whenever a known device gets active.
At least make the feature either optional (default should be "disabled"; let the master user with the App decide) or improve it to make it more resilient. The behaviour we now have since four weeks is more than annoying. It is truely a horror, when you power on your notebook at night and in the room next to you the Revolve turns on, speaks and draws the standard audio connection from the Notebook to the Revolve - if someone tries to sleep in this room!
As there is no "hard power switch" we all have to turn Bluetooth off on all smartphones and PCs to not let the Revolve awake. I guess that this is not the intended behaviour!
The only chance we now have is with the AUX. This causes only reading out loud the battery percentage and then falls asleep after a few minutes.
So please release a new fixed firmware or give us the v1.2.4 as v1.3.4 back!
No firmware update ... no new leads ...
I've turned off the voice prompts "+" and "-" when powered-on. This keeps the SoundLink silent (with only a few bleeps).
This issue is resolvable, there is no need for Bose to release an update.
You need to completely clear the speaker, press and hold the power button, keep holing it for a good minute.
Once done you will notice it's not connected to anything, the name is reset in bluetooth devices, etc.
Delete it from your devices BT history, reconnect, and add go back into the app to set it all back up
To PWhiteside: Yes, you are correct. If the Bluetooth list in the SoundLink is cleared it does not recognize any known devices and therefore the SoundLink will not power on. But when you have paired your devices again, the horror comes back. So what's the point of your "solution"?
We need a fixed firmware and not multiple reset procedures just to keep the SoundLink quiet!