Posts: 14
Threads: 5
Joined: Jun 2021
Reputation:
0
Roon released an update to its Roon Bridge yesterday. It's not visible "in" Roon itself, it says the Bridge on moOde is up to date. From what I gathered so far, this is also an issue on Ropieee. Manually downloading and installing the new Bridge via command line works though. Not sure if that's something that can be fixed on moOde side, thought I'd mention it nonetheless.
Posts: 14,001
Threads: 318
Joined: Mar 2018
Reputation:
571
Thanks. I don't think there is anything in moOde that would need to be looked at. I'm not familiar with the Roon ecosystem but it sounds like Roonbridge update detection and notification is not working in the main Roon app or maybe the app only checks for updates to official Roon Ready endpoints??
Posts: 451
Threads: 11
Joined: Sep 2019
Reputation:
28
07-07-2021, 01:30 PM
(This post was last modified: 07-07-2021, 01:37 PM by vinnn.)
This seems to be a Roon thing, nothing to do with the operating system.
Maybe something to put on the roon forum.
I had noticed the same when all was running 1.8 for a while and the bridge was still on 1.7, re-running the Roon Bridge installer script on your Pi will download the latest version regardless and replace the installed version.
Posts: 7
Threads: 0
Joined: Feb 2021
Reputation:
0
I have the same problem. Roon bridge on my Allo USBridge Sig running Moode still shows build 1.7. I tried to run the installation script and it does work (failed to connect to Roon). I have a display running RopieeeXL, it is 1.8.
Posts: 7
Threads: 0
Joined: Feb 2021
Reputation:
0
Thanks Kent.
My Allo USBridge Sig is connected to my network via ethernet. Any chance it is not connected to the internet? How do I test and fix it (if not connected)?
Posts: 14,001
Threads: 318
Joined: Mar 2018
Reputation:
571
pi@rp1:~ $ ping google.com
PING google.com (142.250.190.14) 56(84) bytes of data.
64 bytes from ord37s32-in-f14.1e100.net (142.250.190.14): icmp_seq=1 ttl=115 time=16.8 ms
64 bytes from ord37s32-in-f14.1e100.net (142.250.190.14): icmp_seq=2 ttl=115 time=15.4 ms
64 bytes from ord37s32-in-f14.1e100.net (142.250.190.14): icmp_seq=3 ttl=115 time=16.4 ms
64 bytes from ord37s32-in-f14.1e100.net (142.250.190.14): icmp_seq=4 ttl=115 time=15.3 ms
64 bytes from ord37s32-in-f14.1e100.net (142.250.190.14): icmp_seq=5 ttl=115 time=15.9 ms
64 bytes from ord37s32-in-f14.1e100.net (142.250.190.14): icmp_seq=6 ttl=115 time=17.2 ms
64 bytes from ord37s32-in-f14.1e100.net (142.250.190.14): icmp_seq=7 ttl=115 time=16.3 ms
^C
--- google.com ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 13ms
rtt min/avg/max/mdev = 15.275/16.174/17.205/0.655 ms