The Bose Community Forum was launched at a time when robust online support was not available for Bose customers. Over the past several years we have added new online service channels that provide a more interactive and complete digital experience. Additionally, we have enhanced the My Bose Account capabilities to deliver a more personalized and self-service experience. As a result, Bose has made the decision to close Community Forum for Consumer electronics products on September 30th. The Bose Pro portion of the Community will still operate as usual.

Please visit our support homepage to experience one of our many other digital service channels or simply use your Community log-in credentials to sign in to your My Bose Account to view your orders and view support options.

Thank you to all who have contributed and benefited from interacting in our Community. We look forward to continuing to serve you online.

Bose Customer Service Team
Showing results for 
Search instead for 
Did you mean:
  • 2
  • 7
  • 1
Registered since

Mar 20, 2021

Firmware Tonematch T4s and connectivity to L1 Pro 32

L1 Pro 32 & Tonematch T4s

Firmware Ver for Tonematch v 1.1.4


When you dial into into Prefs on the T4s and then scroll to L1, whether you are successfully connected or not, the T4s will inform you as follows: NO CONNECTION. I was informed by tech services in Philippines that this is a firmware glitch that requires correction. This "glitch" caused me great frustration as I was trying to get a good connection between the two devices, which I have posted about twice earlier.


I've got two questions:


1. How could a world class manufacturer of electronic goods put out into the marketplace one of their most expensive products with a glitch like that?


2. When will Bose fix this glitch with a firmware update?


Thanks... Mitch




Re: Firmware Tonematch T4s and connectivity to L1 Pro 32

Hi Mitch!

This issue occurs as the Ethercon pin-out on the T4S is differently configured to that on the T1.

This messaging conflict will not affect functionality in any way, but I have raised this in a ticket to our engineering and development team for updated visibility on this. 

Feel more. Do more. Be more.
Come check out my profile here. New to the community? Check out the Getting Started board.
Help others find answers to your questions by clicking on 'Accept as Solution' at the bottom of a reply. If you see a post you like, make sure to give it a thumbs up!