RoPieee - Feature requests


(Wim) #242

Not sure if this has been requested earlier but it would come in handy if we could save RoPieee configurations so that they can be easily restored after a re-flash or when we want to copy a config from one RoPieee to another.


(Harry ten Berge) #243

This actually crossed my mind a few times. I’m reinstalling stuff all the time, so it would be great if you could ‘sync’ settings easily.

Challenging part is how to do this without introducing something like an ‘account’.


(Ged) #244

Could you write something to the installation flash card and the user could copy that off manually if they wanted to?


(Harry ten Berge) #245

sure, but that to me doesn’t sound very user friendly :slight_smile:


(Ged) #246

Probably not but I’m not sure it would be used by anyone who couldn’t cope…


(Harry ten Berge) #247

Agreeing on that. Still thinking on how we can store this in the cloud.
Maybe with a opaque identifier or something like that.


(Ged) #248

Stick a hash on the card that the user can go look up in the cloud?


(Harry ten Berge) #249

yes something like that


(Nathan Wilkes) #250

Interesting discussion @ged_hickman1 @spockfish.

I am not sure storing a hash on the card would be a net plus for the user — often (but not always) the reason for the re-flash is the card itself, and remembering to access, retrieve, and store a hash elsewhere seems more work than simply setting the config values again, especially if one has setup DHCP reservations or isn’t using static IP.

I’d be inclined to think that a more standard email login / config retrieval system might be easier for the normal user to use?

Another approach would be to store config values for all RoPieee devices on a network on all devices, and to suggest auto fill (or “copy from”) when setting up a “new device”? There would be some overhead involved here regarding setup when adding the second device (eg key mgmt in a secure way).

Or, even more simply, a simple export function to backup a config, say to a text file, and the ability to import that config. I prefer to build systems that don’t require access to a file system (eg using a phone or tablet for all config and setup), but this is another approach.

**

Alternatively, improving the speed and accuracy of RoPieee setup could be achieved by:

  • Drop down for Roon Zone (to avoid typos)
  • Auto magically suggest timezone

Nathan


(Hideaki yamagami) #251

Hi Harry,

Have you any plans to support the TEAC AI-503 USB DAC?

https://teac.jp/jp/product/ai-503/top

I don’t see it in your list of Supported Audio Outputs

Regards
Hideaki


(Hideaki yamagami) #252

Hi Harry,

Have you any plans to support the DENON PMA-60 USB DAC?

I don’t see it in your list of Supported Audio Outputs

Regards
Hideaki


(Harry ten Berge) #253

All USB DAC’s will work out of the box. The list on the website only mentions devices that support native DSD.


(John Merritt) #254

Hey all, forgive me if this has already been mentioned further up the thread - it’s a long one!

I’d really love to be able to use Roon extensions - specifically a sleep timer/alarm clock function. I run ROCK + a couple of RPis, and my understanding is that I cannot install the extensions on either the ROCK server or the RPI endpoints either.

I have no idea whether it’s feasible, or how much work would be required, but the ability to install Roon extensions on a RPI would be amazing.

Cheers! John


(Mr Fix It ) #255

You can under Dietpi


(Reader of the Internets) #256

How about a button which just sends the config to the browser interface as a JSON (or yaml, whatever) response? The user could then copy it off the browser and save it to the location of their choice.