phil-d-wilson
commented
1 year ago Hey there,
Sorry it's taken so long for us to get back to you. I'd point out how busy everyone is, but that's not a decent excuse. We are actively thinking through how to better support our blocks, or archive them if we can't support all the things we've ever made.
In this case, the issue wasn't about using a Pi3 image on a Pi4. A Pi4 can run base 32-bit images just fine. The issue was that it was running a really old version of debian, and the packages were not being found any more. I've updated the base images and the packages to reference Python3, and tested it all on a Pi4 and a Pi3 for completeness.
All seems fine now.
I have tried to use this image in several raspberry 4 devices and it seems that is not booting as expected so I can not see my device in my relative fleet.
How to reproduce
Expected behavior
To see the device in my fleet after some seconds and be able to use Node Red when I enable the public URL.
Actual behavior
Once it is powered on, both green and red light of the raspberry pi stays on. I don't see the device in my fleets or I see anything when I enter the HDMI. I have tried the same process to different devices.
Notes
Looking at the code I think that the base image should be referencing the version 4 but I have not tried to change that yet, neither I am sure that this is the cause of the problem.