What version of the UniFi controller and MongoDB do you have installed?

Click to expand...

Not sure on Mongo, Unifi was updated to latest, I ended up having issues which I since found out was the SD card filling up - was only an 8GB. I since moved to docker on Synology as it's always on and to have one less device. I still have it so will fire up and have a look.

Iirc the newest versions of raspbian install a different version of java and you need to install an earlier one.

Anyway googling for java / raspbian issues should help there.

Click to expand...

In the guide I linked to it mentions that...

Update Java 8
This step is pretty important with the newer release of the Unifi Controller. Starting with version 5.10.x the old Java version that comes with Raspbian isn’t supported anymore. So we are going to replace it with OpenJDK 8.

God that shits me. There shouldnt be any circumstances at all for a program to be routinely writing transitory data to anywhere under /usr/lib

Click to expand...

Totally agree, but according to the post by CQGLHyperion its all there in the command execution statement, the fact it is a Java based solution says it all, they probably have a team of Windows devs writing for Linux.

NB Only do this if the USB FTDI will always be plugged in, otherwise add the {idVendor} and {idProduct} so it does it only for that specific USB device, I'm working on a fixed product so these devices will never change.

My Pi boots and runs fine, if I connect a 2.5" spinning disk it detects, pops up on the Raspbian desktop and works, but the T5 connects but doesn't appear on the desktop.
Booting with the spinning disk attached works perfectly and it gets to the desktop with the external drive showing.
Booting with the T5 attached ends with a boot error (photo to come).

photo:

I tried an alternative power supply (a smaller one) to see if it wasn't getting enough power. With the spinning disk I get the little lightning bolt showing not enough power, with the T5 I still get the same error so I don't think it's a power issue.

Hi guys,
Firstly, I am a total noob. I know nothing about Pi, programming or anything connected to those.

I'm hoping someone can help me out here.

I want to display PC stats (CPU and GPU temps. frequencies, etc) on a tiny 3.5" display. Specifically, THIS ONE.

It comes with a 180° HDMI adapter, which is in turn hooked up to a HDMI to Mini HDMI adapter into a Raspberry Pi Zero W. Specifically, THIS ONE.

I'm trying to use a ModBros setup to get the stats from my PC, using an app loaded onto my PC in combination with their custom Pi Image, which should in theory bring stats via a wireless connection to the Pi and display them. The only cables I am supposed to need are Micro USB power to both the display and the Pi.

For details of this, watch the video below and check the links in the comments for both the PC software and the Pi image. I extracted the Pi ISO with 7 zip and flashed a 16GB Micro SD card with it using Etcher before installing it into the Pi.

I've installed the PC software and it appears to work fine. However, the Pi image doesn't appear to work as it is supposed to, as far as I can tell?

The Pi boots and displays on the screen. However, it doesn't reach anywhere to allow me to configure it. I've tried downloading the image again in case it was corrupted the first time, but I just reach the same point in the boot process and nothing more happens.

I've given it like 20 minutes to boot, as they do say the Pi Zero is slower than a 'normal' Pi, but it just won't get further than the image you'll see below. I hooked the Pi up to my main monitor just to make it readable, the little screen is a bit too high def. and with my weak eyes I actually needed a magnifying glass just to read the writing so I figured it would be better to read displayed on the big screen.

If anyone is willing to download the image and examine it, or if you can make any sense of what may have gone wrong by the displayed script, I would much appreciate some advice on where I may have gone wrong, or whatever the fuck is going on here.

Here's a pic of the Pi mounted to the tiny display.

And here is what is being displayed, and the point at which it stops. Keep in mind that this image a photo of my main display, connected to the Pi via HDMI, so if there is anything specific to the display that will vary from what I am seeing on the mini display.

Am I doing something wrong, or is there a problem with my choice of hardware, or is the Modbros Pi image to blame? Should I have installed some other OS before the Modbros image? I get the impression that its supposed to be a complete OS of sorts, and I would have thought that flashing the SD card with their image would make that a certainty?