Replies: 2 comments
-
|
Hi, thanks for the detailed feature request — and for documenting the manual workaround! This is on our radar. Device renaming via the OCT web UI would indeed be a nice quality-of-life feature, especially for setups with multiple speakers. Right now our focus is on stability and the upcoming Restore Wizard (restoring backups to devices), plus telnet-based provisioning for devices that can't be set up via USB. Once those are solid, features like device renaming are great candidates for the next round. In the meantime, your SSH workaround is the way to go. Could you please also create a Feature Request issue so we can track this properly? That way it won't get lost in the discussion threads. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
We've created a tracked feature request for this: #204 Great suggestion — and thanks for documenting the manual workaround so thoroughly. This will help when we get to implementing it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Feature Request: Device Rename Support in OpenCloudTouch
While working with multiple Bose SoundTouch devices under OpenCloudTouch, I noticed that device renaming currently does not seem to be available directly inside OCT.
At the moment, renaming only works manually over SSH by editing:
and changing:
Example:
Afterwards, the device needs to be rebooted.
Since OpenCloudTouch already communicates locally with the SoundTouch devices, a simple rename feature directly inside OCT would be very useful.
Possible implementation ideas:
SystemConfigurationDB.xmlThis would especially help users running multiple SoundTouch devices in local-only setups.
With several devices on the network, having a direct rename option inside OCT would be a great quality-of-life improvement.
Current workaround:
sed -i 's/OLDNAME/NEWNAME/g' /mnt/nv/BoseApp-Persistence/1/SystemConfigurationDB.xml rebootBeta Was this translation helpful? Give feedback.
All reactions