Ok. I got this working now (it’s great).
Here’s the process I followed on Mac, which should be the same on Windows I assume as long as you have something similar to Terminal on your machine.
This was on DietPi on a RPi 3+, with Roon Endpoint and Roon Extension Manager installed (I didn’t install node.js because that got installed already when the Roon Extension Manager was installed, but you can double check in the Dietpi software config package manager).
This is all based on the instructions I found on https://github.com/pluggemi/roon-web-controller which ended up pointing the way.
Access your DietPi via console by putting in this command
ssh root@[IP Address of your Pi]
This assumes you have not changed the admin username on your DietPi install from root, edit accordingly. You should now be prompted for a password to access the Pi.
Now paste this at the command prompt once you are accessing the Pi:
git clone https://github.com/RoonLabs/roon-extension-devialet-phantom-volume.git
You should see the files getting extracted into
Change the directory you are accessing into the directory where the software was extracted using this command:
Install the Node.js modules by typing the command
Run the application by typing
nohup node app.js &
The extension should be running now. In order to exit Terminal or Putty, or whatever command line interface you are using, make sure to type
exit, rather than just closing the window, to ensure the process stays active.
On an existing Roon client, go to “Settings” then “Extensions”. You should now see the
Devialet Phantom Volume Control listed and it will either be searching for the device, or you’ll see Status: Found # device.
Now you can follow @danny’s instructions on the github repo https://github.com/RoonLabs/roon-extension-devialet-phantom-volume/blob/master/README.md ensuring you enable UPnP in Spark, and changing the device volume control in Roon in Settings/Audio/
The extension seemed to disappear when I power-cycled the Pi. There may be an additional instruction on how to ensure that the app is started up on boot. I had to go back in, cd into the directory again, and run
node app.js to get the extension running again.
Hope this helps.