Once in a while I am still receiving inquiries of fellow audio folks asking for my Squeezebox Touch Toolbox.
Squeezebox Touch, a device that's been sold until 2011, if I recall correctly. The Toolbox is pretty much of same age. Time is flying by. It feels like a different life back than.
Fun fact. I am sure that this ancient Toolbox will still have a slight impact on modern DACs. Yep. Unfortunately we still face similar challenges on our digital gear after all these years.
The last toolbox version that I had out in the wild, was Touch Toolbox 3.0. That one I now uploaded to github.
You'll find
- a related document (background and setup) and
- the toolbox files
You should know how to download the stuff from git. Make sure to also apply the server tweaks I've been pointing out within the Audio Streaming Series.
Of course, there's no support for the Toolbox from my side. Consider the upload and the rough document review and update a favour from my side. I hope it all works out for you.
Enjoy.
Update 2023 - Feb - 7:
A little story.
I found my old Squeezebox Touch buried under a wild heap of old electronics. It looked pretty frayed.
Shall I give it a try !?!? Hmmh. I got curious. Hooked up to 5V the screen came up. Wow. Great after 10y. Within seconds it turned off again. WHAT !?!? Aah. I recalled. That's been the Toolbox feature "Screen OFF". Obviously I left the Touch Toolbox on when I trashed the device about 10 years ago. Next thought. Let's do a HW reset to default to factory settings. After pushing the button, nothing happened. Hmmh. Quickly, it dawned on me. That HW reset button got broken 10 years back from all the numerous resets I had to run during the Toolbox design phase. Q: Shall I open it up, perhaps I can run the reset from inside. !?!? Yep. Why not. T's been a 30 minute effort - wasted! Now I could look at the broken switch. Great. I then recalled that I had implemented a SW initiated factory-reset in the Toolbox. Ok. Let's try it that way.
Next task: ssh login. Puh.
Nice. The IP did show up on the net after power-up. Good. However. sshing into it didn't work at all from my Fedora machine. That's not good. I received all kind ssk key, cipher error messages. Why?
Obviously the SBT ssh package is pretty dated @ 12+ years lifetime. After googling and trying all kind of ssh options to find out if there's on option to get into the damned device, I just managed to get more and more errors away by entering another after another parameter. I finally gave up on the message: Bad server host key: Invalid key length. So far I was 2h on the project. While running the task I learned that my Fedora is running the latest openssh version and they rather recently increased the minimum key length to 2048. Grrr.
What about Debian based Raspberry PI OS !?!? Debian usually lags a couple of releases/years behind on the software side compared to Fedora. Fired my RPi up and gave it try. Bingo. From Raspberry Pi OS sshing into the SBT worked. Once in ten years it's of advantage to work on a usually outdated platform.
I ran the reset and all settings were back at factory-default. I did the initial setup. And hooked the SBT up to my Adams.
Let's play some music! A radio stream. Several of the radio stations that were on the SBT are not longer accessible. Finally music started playing when selecting Radio Paradise. Above image is proves it.
Meanwhile, a day later, the Fedora problem still kind of bugging me, I found the solution to also do the ssh login from Fedora. Below you'll see the result (the ssh command is actually just one line):
###########################################################################
SBT Login:
ssh -o KexAlgorithms=+diffie-hellman-group1-sha1 \
-o HostKeyAlgorithms=+ssh-rsa \
-o PubkeyAcceptedAlgorithms=+ssh-rsa \
-c aes128-cbc \
-o PubkeyAuthentication=no \
-o PreferredAuthentications=keyboard-interactive,password \
-o RSAMinSize=1024 \
root@192.xxx.x.xxx
pword: 1234
#############################################################################
No comments:
Post a Comment