?
Its pretty difficult to diagnose these kinds of problems remotely but 95% of the time I have seen the issues be operator error and one of the following:
1. ?Failure to place a "wpa_supplicant.conf" file in the FAT32 directory after imaging and prior to booting, and expecting the PI to connect to your WiFI.
2. ?Bad SD card or failed imaging step. ?I use Win32DiskImager on Windows, and Etcher on a Mac, and never really had a problem (Low Likelyhood)
3. ?The OLED screen is not going to do anything until you actually configure it in the Pi-Star Configuration.?
The fact that you do not see the Pi while connected to Ethernet suggests a bad image or Pi (unlikely), but the fact that an old Pi-Star SD card did not boot would point to that. ?Check for the "Pi-Star" auto-Access Point on your network. ?Also I seldom have issues with a Pi2, 3 or 4. ?I have had a couple HRO Zumspots and the first I bought is Ok, the second bought about a year later died, was replaced, and died again. ?Chose to give up on them. ?Make sure your Pi's have heatsinks on the appropriate chips.
The "Update" function within Pi-Star is perfectly adequate for bring an image up to current release without re-imaging. ?That is what it was designed for. ?Early versions of Pi-Star required re-imaging to update version, or the use of the Command Line utility in the "Expert" mode. ?You should not have to do that any longer. ?Re-imaging is always problematic and takes time and always requires steps to connect to your network and configuration. ?Obviously hams like to tinker but Pi-Star now seems to be designed to eliminate the need to ever re-image, unless the SD card goes bad (and cheap SD cards do go bad and won't take a lot of re-imaging).
?
/g/PiStar/topic/hot_spot_dead_after_update/85780329
?
?
?