SoundTouch Portable works with on-device install

[tadhgj]

Notes:

• Speaker was on Bose firmware version 27.something
• Micro USB port on back accepted an old OTG cable I had for an android phone
• USB was formatted through the diskutil utility on macOS instead of the Disk Utility app. While both format methods resulted in the drive reporting the Bootable property to be 'No', the speaker did enable root ssh with a USB wiped with the command line utility
• Had ~25mb free on /mnt/nv, enough space for AfterTouch
• Port 8000 was unreachable using the speaker's IP, ssh forwarding fixed it
• The web interface's migration was blocked when 127.0.0.1 or localhost was set as the domain, but localhost.localdomain worked

(Pictured is the speaker running with Spotify Connect before I got AfterTouch installed, but it's a good visual)

Presets set using this before I installed AfterTouch were preserved and worked. Some radio stations do not work, didn't really dig into things. Didn't set up Spotify or Amazon auth. TuneIn requests result in 'Service Unavailable'. Didn't bother figuring out why

[gesellix]

Thank you for the overview. If you need any help, just leave a note here or create an issue! I'll try to add your notes (especially the hint about the usb stick) in our docs.

The web interface's migration was blocked

Can you elaborate which web interface you mean? I suppose you mean the AfterTouch admin web ui?
Did you get any error messages by the browser or the web ui?

[tadhgj]

On the Aftertouch migration tab where you configure where the speaker should look for the servers, entering 127.0.0.1 or localhost shows a box that says this is a loop back address, which I guess is an error instead of a warning, because the migration buttons are disabled.

[gesellix]

Ah, makes sense. Localhost should be allowed for on-device installs. I only tested with the speaker's network IP address.

[Henri-be]

I have the same need as tadhgj.
I'd like to use the Migration tab to change the URLs to point to the local server, but the interface won't let me...
Would it be possible to change this?
My goal is to be able to use my speaker without having to assign it a static IP address.

Thanks in advance

margeServerUrl: loopback URL — speakers can only reach this if AfterTouch is installed on the speaker itself (on-device install). For the typical multi-device setup, use a LAN-reachable IP or hostname.
statsServerUrl: loopback URL — speakers can only reach this if AfterTouch is installed on the speaker itself (on-device install). For the typical multi-device setup, use a LAN-reachable IP or hostname.
swUpdateUrl: loopback URL — speakers can only reach this if AfterTouch is installed on the speaker itself (on-device install). For the typical multi-device setup, use a LAN-reachable IP or hostname.
bmxRegistryUrl: loopback URL — speakers can only reach this if AfterTouch is installed on the speaker itself (on-device install). For the typical multi-device setup, use a LAN-reachable IP or hostname.

[tadhgj]

@Henri-be use the domain localhost.localdomain instead of 127.0.0.1

[Henri-be]

@tadhgj Thank you for your advice, it works well this way.

[gesellix]

Closing this, since it works now. Thanks @tadhgj for the tip and @Henri-be for
confirming.

For anyone finding this later: the Migrate tab no longer blocks a loopback
URL on an on-device install. http://localhost:8000 is accepted when it
matches what the service itself answers as, which is the on-device case
(fixed as the follow-up to
issue #546, reported
in issue #621). A
loopback URL is still refused when AfterTouch runs on a separate host, because
the speaker cannot reach it there. The localhost.localdomain workaround is
no longer needed.