I also had the problem that problem on one of my RPIs, namely that it got stuck in stage 4.
In that case one cannot go to the web interface, as the RPI is not yet connected to the network.
This is my only RPI which has a FLIRC-dongle.
I removed the FLIRC-dongle and wired the network-connection (afterwards I don’t think I had to wire the network-connection).
Did a hardware reset by removing the power cable and reconnecting it.
Now the RoPieee passed the stage 4, and I was able to logon the web interface of RoPieee to make use of the trick of Spockfish.
When reconnecting the Flick-dongle afterwards, everything was OK again.
@spockfish Harry, Thank you for all the efforts and time you put in this software to keep improving RoPieee. Great job!
And if a device is set to autoupdate on a weekly reboot, how do I stop it updating? Will it update if I change the setting to not auto update then ‘Apply’?
I’ve done changes and configure many time…no joy still so I’ll wait to see Harry issues as a fix update. Plus w use OSMC dongle remotes that’s breaking the boot up
Have you also hard cycled the unit? I’m not sure if the graphics chip is f* up if it can recover with a soft reboot. Your latest logs show that it should be ok.
So hard cycle the unit, restart it and send me direct feedback if possible.
I’ve finally have been able to reproduce your screen corruption issue.
It is indeed related to Flirc/OSMC, but you can fix it.
Remove the Flirc/OSMC dongle, reboot your unit, change a parameter (screen rotation), configure and reboot. It should then recover. After that it’s save to reinstall your dongle.
This also explains why @Nathan_Wilkes had initially the same issue but recovered, while not exactly clear how.
Hi Harry, it seems you had a sleepless night (only 3hrs not responding). Hopefully you still have fun with your outstanding project. Thank you for this great project! RoPieee using is part of my (our) daily live.
Hi @spockfish
My issue seemed to be with the OSMC dongle/remote - just followed the instructions for wizardofoz and the unit came back up. Unit now working.
However I then reattached the OSMC dongle and this shows up as OSMC in the web interface but the remote doesn’t actually do anything. I have tried re-pairing and rebooting but without success. Not urgent and not a deal breaker but would be good to get it back.
I had two Pi4s with FLIRC dongles attached (but no screens involved) fail to update. Unfortunately, I didn’t see this thread before I updated. Pulling the dongles, then disconnecting and reconnecting the power to the devices, allowed the update to finish. I won’t plug the FLIRC dongles back in until the next release. Harry is a miracle worker, and I know this is a minor hiccup (one of the very in many years of using Ropieee). I always appreciate what Harry has given us.
Hi @spockfish ,
I’m currently running RoPieeeXL 2023.11 (1188) on Allo USBridge Sig with no issues.
I’m a bit confused : my web interface reports “Update 2024.01.0 [1267] downloaded and available for your device”, but the title of this thread says [Release 2024.01 [PULLED: DO NOT UPDATE].
What is safe to do? Also. is the compressed image for USBridge under Download page the same that gets downloaded by the unit automatically?
TIA
I would wait a bit. If you reboot your device the update will be removed.
The image on the website is conceptually the same, but an update image (that is being downloaded by an already installed unit) only contains the delta (and thus is smaller).
Hi Harry, odd that the 2 units with OSMC dongles are both fine now (without the dongles in) but others are still not. I’ll send you feedback when I get time to deal with it if the rotation swap and back doesn’t help.
thank you Harry @spockfish , it took two reboots, but now the update alert doesn’t show up anymore.
I’ll wait for the new stable authomatic update, surely much easier than re-flashing and reconfiguring everything.
Thanks so much for your continuing and fast support
Ok dongles I’ll do in the morning but the last 2 screens are ok now after toggling the rotated screens and rebooting plus back again.
I don think I did that on the other 2 units…I turned on/off screen controls iirc, that didn’t work for the last 2. Anyway all good now thanks Harry, and happy new year!!!