Hi @Peter_Bevan
Looking at your logs it seems your Flirc is not detected.
Keep in mind that it needs to be plugged in when the system is being configured.
Can you trigger a configure? By changing a (harmless) parameter?
Thanks
I would have not set “auto update” for a specifically “patched” version!! Glad that I waited with the update on mine…
I did that this morning, and it seems to have worked! Thankyou!
Sent a feedback log, in case there’s anything useful in there for you: f08af1f1a21bcaf8
1 Like
Some of mine have yet to update…that’s ok but some often update and drop out of pairing in the extensions. Re pairing it connects without a hitch. One is just used as a dispel the other a powered amp amd speakers on the HAT
I have gone back to .09 so no .11 feedback
@spockfish, here is my feedback with Allo USB Signature on 2023.11 which has clicking noise.
dd5a9171dc25022e
Thanks!
Hi @Phil_RF1_Chan ,
Thanks for your feedback.
I’ve found the regression. I can’t explain (yet) why this happened, but I’m preparing an update to fix this, stay tuned.
Thanks
2 Likes
1 Like
@spockfish. Thanks 1188 works on the USB Sig.
Will download a copy for backup once it is available on RoPieee web site.
@spockfish I absolutely LOVE RoPieee! Thank you for all of the work on this. I don’t even use Roon; my install is primarily for the Plexamp component, although I also make use of Squeezelite.
Question: I don’t see an update button. I do have auto-update on, but I am still on 2023.09. Any magical incantation I need to use? 
Thanks again!
Harry (@spockfish) - can you please check my unit’s logs (feedback - 848a76f0ff75cfa6), please preaty please? Almost 5 days since last reboot, and no update notification, so I wonder if there is an incompatibility with my WAN / ISP (IPv6 DS-Lite).
note: in September i had to manually upgrade to 2023.09 (1118)
thanks.
Your feedback is emtpy.
I’m wondering if there’s isn’t some firewall getting in the way.
that’s disapointing, but at least is an “improvement” - sending feedback from 2023.07 failed 
new feedback generated - 927b2ee331d082dd.
q: if i disassmble the rPi touch-display case and mount the SD card, any logs you want me to collect / look at ?
edit: and another feedback - 574f09b59c706bec, collected after i disabled IPv6 on my router & rebooted the PI.
The 927… is still empty.
The 574… is not. It is however not long enough running to see anything particular wrt the update process.
I suggest you leave it running and me an update of that unit (without rebooting) tomorrow.
1 Like
Is there a manual way to send feedback? Mine has failed, and I don’t think it’s a firewall issue, as it’s exposed to the internet behind a standard router like everything else. It should be able to send it’s diagnostics (unless I should be enabling uPNP for this device or forwarding a port…)
after around 15h uptime, no update notification (yet) - 10eea4555f28d059
Your feedback is again empty.
So something is not ok: either it is network related or you have a corrupted system.
I’m not sure what you mean exactly. If you can’t send feedback from the RoPieee webpage (how do you come to the conclusion that it failed?) then there’s nothing else I can do.
Thanks
Maybe I wasn’t clear. The update didn’t fail. Sending the feedback log continues to fail. I was just asking if there was maybe a way to download the logs locally and then email it the old fashioned way. I also know my way around a linux command-line. I was also thinking maybe I could SSH in and find that same info. In any case, thanks again. I guess I will just flash the latest version.
Sounds like a corrupt sd card or dead so I would burn a new one - not the existing one just to be sure