rooNuimo has nothing to do with iOS. It works fully independent and therefore it is not required / necessary.
1 Like
Hi DrCWO
I have my nuimo set up to switch to a radio station on a long touch bottom button. This works great but i cant work out how to go back to the normal play mode. ITs locked in radiostation mode uptil i change on a lapptop for example.
Is that normal behaviour? It would make a lot of sense if you could switch back to where you were in your play list
It should switch back to the last title on the playlist by performing the same action (long touch bottom in your case). It seems that we introduced a bug in the latest version. We will fix this for the next version. Thanks for the bug report!
Thanks for confirming im not crazy 
Hi with 2.3.1 I’m having a connection problem with the Nuimo. Is this a known issue?
I’m also having connectivity problems since upgrade to 2.3.1. Nuimo cannot connect or disconnects in 5 seconds.
In logs it looks like that:
Aug 14 16:34:07 rooExtend rooExtend[540]: ***** Nuimo got disconnected, restart Extension
Aug 14 16:34:07 rooExtend rooExtend[540]: Worker rooNuimo terminated with code: 5
Aug 14 16:34:07 rooExtend rooExtend[540]: Restarting Worker rooNuimo
Aug 14 16:34:08 rooExtend rooExtend[540]: ##### Start: rooNuimo 1.2.0
Aug 14 16:34:08 rooExtend rooExtend[540]: ***** rooNuimo got paired with CORE
Aug 14 16:34:08 rooExtend rooExtend[540]: Waiting for first nuimo device to appear…
Aug 14 16:34:12 rooExtend rooExtend[540]: Appeared deviceId: d0d27bfc6331
Aug 14 16:34:27 rooExtend rooExtend[540]: ***** Cannot connect to Nuimo, restart rooNuimo to retry
Aug 14 16:34:27 rooExtend rooExtend[540]: Worker rooNuimo terminated with code: 5
Aug 14 16:34:27 rooExtend rooExtend[540]: Restarting Worker rooNuimo
Aug 14 16:34:28 rooExtend rooExtend[540]: ##### Start: rooNuimo 1.2.0
Aug 14 16:34:28 rooExtend rooExtend[540]: ***** rooNuimo got paired with CORE
Aug 14 16:34:28 rooExtend rooExtend[540]: Waiting for first nuimo device to appear…
Aug 14 16:34:32 rooExtend rooExtend[540]: Appeared deviceId: d0d27bfc6331
Aug 14 16:34:47 rooExtend rooExtend[540]: ***** Cannot connect to Nuimo, restart rooNuimo to retry
Aug 14 16:34:47 rooExtend rooExtend[540]: Worker rooNuimo terminated with code: 5
Aug 14 16:34:47 rooExtend rooExtend[540]: Restarting Worker rooNuimo
Aug 14 16:34:48 rooExtend rooExtend[540]: ##### Start: rooNuimo 1.2.0
Aug 14 16:34:48 rooExtend rooExtend[540]: ***** rooNuimo got paired with CORE
Aug 14 16:34:48 rooExtend rooExtend[540]: Waiting for first nuimo device to appear…
Aug 14 16:34:50 rooExtend rooExtend[540]: Appeared deviceId: d0d27bfc6331
Aug 14 16:35:05 rooExtend rooExtend[540]: ***** Cannot connect to Nuimo, restart rooNuimo to retry
Aug 14 16:35:05 rooExtend rooExtend[540]: Worker rooNuimo terminated with code: 5
Aug 14 16:35:05 rooExtend rooExtend[540]: Restarting Worker rooNuimo
Aug 14 16:35:06 rooExtend rooExtend[540]: ##### Start: rooNuimo 1.2.0
Aug 14 16:35:06 rooExtend rooExtend[540]: ***** rooNuimo got paired with CORE
Aug 14 16:35:06 rooExtend rooExtend[540]: Waiting for first nuimo device to appear…
Aug 14 16:35:09 rooExtend rooExtend[540]: noble: unknown peripheral d0d27bfc6331 connected!
Aug 14 16:36:14 rooExtend rooExtend[540]: noble: unknown peripheral d0d27bfc6331 disconnected!
During startup RPI complaints that “Failed to start Raspberry Pi bluetooth helper”
1 Like
No, nothing got changed in this respect.
I had a preliminary report from an other customer who seams to have encountered that. But with his second Nuimo all works fine. The Nuimo in question also make trouble with with 2.2.x. So I think 2.3.x is not the reason why.
In my personal setup I now use the USB bluetooth antenna ZEXMTE BT 5.0/5.1. I also installed the USB antenna about 30cm away from the Raspberry (with a USB extension cord) and taped it to the inner front side of my wooden drawer where the Pi and my RME ADI-2 Pro reside.
This gives me aprox. 10m distance where I can operate the Nuimo perfectly through one brick wall in my kitchen. Since that the connection is 100% stable 
This is normal.
The disconnect is a timeout. In the xternal Settings you have “any”?
Try to put the Nuimo closer to the Pi for initial connect.
My Nuimo worked perfectly in 2.2.x and ive not moved anything. The Pi is 4m away from the Nuimo and I’m using the ZEXMTE BT 5.1, so all optimally setup.
I’m pretty sure its software issue @DrCWO
Strange, nothing was touched in this corener of rooExtend. Also no new Linux this time 
Have you tried to go back to 2.2.x?
I didn’t keep a copy of 2.2.x how do I obtain that now?
Hi @DrCWO is there a different kernel in use for this version.
I’m a little behind at the moment due to travel and work, but I downloaded 2.3.1 this afternoon just as these posts were starting.
I will try on my two devices later as I have an BT dongle as well and the 2.2.X version has been pretty much perfect for me.
I will let you know how I get on tomorrow
No, not at all…
Remind me again how i get that?
- Get the IP of your rooExtend from its settings dialog all down
- Open your browser with http://[IP you got]
- Scroll down the page
- locate the button System log at the very end
- Click it and you get the log
Best DrCWO
Thanks @DrCWO so I’ve rolled back to 2.2.2 and Nuimo 1.1.4 from 2.3.1 (roonExtend) and 1.2.0 (Nuimo)
All is working perfectly again. Sorry but i forgot to take logs for 3.2.1 before formatting and reinstalling 2.2.2
@DrCWO
I have both licenses and have tried to load the roodial license when the license of the roonuimo is already entered. However the extension does not accept both licenses together . I am using the current version of rooextend - 2.3.1
Hi Suresh you need a Pi per RooNuimo device and the license needs to be entered into each Pi.
Sorry if I have misread your question