rooExtend – The easy start with Roon Extensions

[Tampo_Tempo]

I tried searching again and found it this time!

The discussion starts here, and includes the workaround /serviceaction.html?command=reboot solution from @Henry_Svendblad a few replies further down:

rooExtend – The easy start with Roon Extensions

@DrCWO I have a feature request, and I don’t think this is a heard one. It would be much appreciated if you could add a “Reboot rooExtend”-button under the “Shutdown rooExtend”-button in the GUI of rooExtend. Now, when there have been any sort of issue with rooExtend, and you just want to restart/reboot the RPI, you have to push on “Shutdown rooExtend” and then you have to power off the RPI an d power it back on. But pushing the button, you can do from wherever you have network-access. Powerin…

[Tampo_Tempo]

@DrCWO

So the only thing I am able to offer is to add the reboot button if no ZEXMTE antenna is plugged.

In fact, it would be great if you could do this conditional feature , @DrCWO

A button on the extended settings page would be more convenient than the <rooextend-ip-address>/serviceaction.html?command=reboot workaround (for anyone without the ZEXMTE BT antenna).

[DrCWO (C.W. Oehlrich)]

@Tampo_Tempo

could you please remind me what the URL parameter is that I can append to the rooExtend IP address to reboot rooExtend

If you open the IP of rooExtend with http://[ip of your rooExtend] you will see a lot of buttons for the different functions at the end of the service page.

Just press the button you like to use and look to the URL in the browser after that.

There is no button for reboot as with a reboot the antenna for BT cannot be initialized again and rooDial and rooNuimo will not work after that any more. So only the shutdown is available.

Best DrCWO

[Tampo_Tempo]

@DrCWO

So the only thing I am able to offer is to add the reboot button if no ZEXMTE antenna is plugged.

Thanks @DrCWO. Some time ago, you mentioned a possible enhancement to add the reboot button conditionally, when no BT antenna is detected.

I’m just wondering if you would be able to implement this feature sometime? It would be a nice convenience for those of us that are not using BT.

Like some others have mentioned, I have my rooExtend RPi in the cellar. So it’s not convenient to restart it after a shutdown, on the rare occasion that I do so.

[DrCWO (C.W. Oehlrich)]

@Tampo_Tempo

The discussion starts here, and includes the workaround /serviceaction.html?command=reboot solution from @Henry_Svendblad a few replies further down:

I checked the code and this is real
I once implemented a set of service actions and forgot about it
So you can trigger all of the with a URL from the browser or elsewhere.

You can trigger these service actions with the following URLs

• Reboot rooExtend
  http://[IP of rooExtend]/serviceaction.html?command=reboot

• Delete all your configuration settings
  http://[IP of rooExtend]/serviceaction.html?command=deleteConfig

• Unpair the Surface Dial
  http://[IP of rooExtend]/serviceaction.html?command=unpairDial

• Delete the WiFi settings
  http://[IP of rooExtend]/serviceaction.html?command=deleteWiFi

So I see no more need to implement the button.
Best DrCWO

[Frank_M (Frank Minne)]

Perhaps because a button is way more conviniant than to have to remember an URL of 10cm long?

[DrCWO (C.W. Oehlrich)]

Another Hotfix

Hi guys,
this is for all having freshly installed rooExtend in 2026 from the ARMv8 image or with a rooExtend-Box activated in 2026.

You should have applied this hotfix and now see release 3.5.3 of rooExtend.

If you attempted to activate RoonCommandline in the License Manager while in this situation, it likely did not work. You can select “Yes” as often as you like, and there is no reaction.

A reference to an external package in RoonCommandline was the cause of the issue. So just like the last time I had to release a hotfix.

It was a bit complicated to find the reason why and it took me a lot of time to provide a fix. Now, finally, I can provide a hotfix that resolves the issue.

You install the hotfix the same way as the hotfix before but - only difference - enter the following URL in input field: https://rooExtend.com/fixes/fixRoonCmd/fixRoonCmd.sh
Please copy and paste as Upper and Lowercase matters!

After having done this, immediately open Roon Settings/Extensions and look for a Roon Extension looking like this:

You have to enable it to finalize the fix. After that rooExtend will shut down.

After a power cycle (Off/On) rooExtend will come up again. Now you should be able to enable RoonCommandline in the rooExtend License Manager. After saving the settings you will see the Roon Extension for RoonCommandline.

You also have to enable this which the normal process for enabling RoonCommandline.

Wait until it disappears. After that it will reappear for a short time again and RoonCommandline should work from now on.

Best DrCWO

[Henry_Svendblad]

@DrCWO

https://rooExtend.com/fixes/fixRoonCmd/fixRoonCmd.sh

Hello @DrCWO - Long time, no see

I was able to get this installed but for some reason my RPI locked after completing the re-install of CommandLine.

I unplugged the RPI, re-powered and it came back fine. Command Line now like this:

Sharing here just in case anyone else runs into it.

Danke schön,

Henry

[DrCWO (C.W. Oehlrich)]

@Henry_Svendblad

but for some reason my RPI locked after completing the re-install of CommandLine

After RooCommandline was enabled in Roon Settings/Extensions the hotfix will terminate so you have to reboot.

Anything fine

Best DrCWO

[Tampo_Tempo]

@DrCWO

Another Hotfix

Hi guys,
this is for all having freshly installed rooExtend in 2026 from the ARMv8 image or with a rooExtend-Box activated in 2026.

You should have applied this hotfix and now see release 3.5.3 of rooExtend.

@DrCWO, just to be sure, there’s no action required for those of us who installed in 2025 or earlier, correct?

In my case, I set up a RPi4 with a rooExtend license in April '25, applied the original hotfix in August '25, and am currently on version 3.5.3. I don’t currently use rooCommandline.

[DrCWO (C.W. Oehlrich)]

@Tampo_Tempo

In my case, I set up a RPi4 with a rooExtend license in April '25, applied the original hotfix in August '25, and am currently on version 3.5.3. I don’t currently use rooCommandline.

This should be fine.
Nevertheless installing the hotfix does no harm and guarantee a reliable RoonCommand operation.

Best DrCWO

[Tampo_Tempo]

Okay, thanks Dr. CWO. Done!

[Ralf_Blaesen]

Is there any way to get a trial license for Rooplay? I’d like to try it out first before buying anything.

[DrCWO (C.W. Oehlrich)]

Get it and if you don‘t like it I will give you a refund.
I’m sorry but there is no other way to get a trial.

Best DrCWO