I upgraded to 2.1.0 this morning. Just built my Rasberry Pi4b yesterday and can connect with rooextend.local, however I can’t get the Nuimo to connect via Bluetooth. I have tried connecting by using a TP-Link USB Bluetooth Adapter for PC(UB400) adapter as well as removing the TP-Link adapter and seeing if it would connect with the Raspberry Pi’s built in Bluetooth. No luck.
I powered off the Pi several times as well as the Nuimo with no luck. Still have the blinking Bluetooth icon on the Nuimo. The Raspberry Pi is connected via Ethernet.
Stephen,
Did you select rooNuimo in “Controller selection” of rooExtend Settings (see screenshot)?
If so, do you see the rooNuimo Extension in the Roon Extensions Settings?
If so, does the rooNuimo extension prompt “licensed”?
I upgraded my Pi Zero W with the new version yesterday.
However I still have issues with waking up my Microsoft Surface Dial from Sleep. Even after the upgrade, the Dial is not able to connect (status shows Sleeping). This is after say 12 hrs after last listening / use when it was working perfectly.
Do I need to reboot the PiZero every time as this is the only way it connects. All extensions in Roon are showing enabled.
It’s always on . It’s a Roon Rock on Intel Nuc 8i7 in fanless case and always running I last used this morning 8 hrs ago and on return no joy. Will not connect. Only connected on rebooting the Pi Zero
Hi @DrCWO - I’m struggling a little after updating to 2.1.3 (rooDial 1.5.1). Previous updates have been uneventful. The extension seems to frequently restart itself - it appears and disappears in Extensions constantly. Won’t pair with the dial. Also won’t let me save settings. The RPi Zero W stays connected to the WiFi through all this. I’ve tried restarting the Core, restarting the RPi and removing/replacing batteries in the dial but nothing has made a difference. Any thoughts? Thanks!
Edit: Just reset to factory defaults via the Web page, same problem unfortunately.
Edit 2: My thanks to @DrCWO for following this up with me directly and resolving the issue
Hello Doc, I just saw, there is already a version 2.1.3 available. Could you please always provide some release notes? I have the NUIMO Hub and I would like to avoid frequent disassembly of the hub if it’s not really necessary. Thanks!
The last digit, in my version number in this the .3, is always reserved for hotfixes. Reason for a hotfix is always an issue reported by a customer in his often very special situation. If I decided his issue has to be fixed I publish a new hotfix.
It is important to know that these hotfixes don’t include any new functionality nor any functional improvement. This means the release notes for v2.1.0 are still valid
If you feel fine with the v2.1.x you use there is absolutely no reason to upgrade to v2.1.3.
I have been meaning to suggest that you leave the last digit off the version number when you name release notes and other documentation. So the release notes should be for “v2.1”, not “v2.1.0”. This might help people realize that the notes are valid for all versions of the 2.1 release, instead of wondering if the notes are out of date.
Really appreciate your software. With this latest version should I be able to see the Upnp extension on a pi zero 2? (I can use dial and stream to a dac with no issues)
Running UPnP with a Pi Zero2 W wireless is really no good idea. UPnP is prone to packet loss and wireless audio in two directions (from Access Point to Pi Zero2 W and back to Access Point) would give such unsatisfying result that I did not allow it.
rooUPnP is enabled in the Nuimo Hub now but not in Pi Zero2 W. Better use a Pi with wired Ethernet.
