chrisys / led-pixel-controller Goto Github PK

The services are stuck when trying to start up. It seems like there is a typo in the docker-compose file, where the GW is not in the same subnet as the other IPs. But also with this entry fixed, the services keep restarting.

I can't get the artnet part to work

The dockerfile fails on this line:

RUN apt-get update && apt-get install -yq \ python-twisted && \ apt-get clean && rm -rf /var/lib/apt/lists/*

with the error:

The command '/bin/sh -c apt-get update && apt-get install -yq python-twisted && apt-get clean && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100

I tried manually installing python-twisted from the command line on another Pi running without Balena and it installed correctly. Not sure what is wrong here, any ideas?

When I testing on Pi 4 the other day I noticed everything works fine, but then when I was testing on the Pi 3 the automatic control of Glediator (and hence scheduling) doesn't appear to be working.

This can be resolved by turning the compression and quality down (maybe even just compression) using the settings > advanced menu in noVNC. I'm trying to figure out a way to set this by default but nothing I'm trying is working.

I tried this in start.sh:

# Change the default quality and compression
sed -i 's/this._qualityLevel = 6;/this._qualityLevel = 2;/g' /noVNC/core/rfb.js
sed -i 's/this._compressionLevel = 2;/this._compressionLevel = 0;/g' /noVNC/core/rfb.js
sed -i 's/<input id="noVNC_setting_quality" type="range" min="0" max="9" value="6">/<input id="noVNC_setting_quality" type="range" min="0" max="9" value="2">/g' /noVNC/index.html
sed -i 's/<input id="noVNC_setting_compression" type="range" min="0" max="9" value="2">/<input id="noVNC_setting_compression" type="range" min="0" max="9" value="0">/g' /noVNC/index.html

But it seemed to make no difference.

Per another forum thread, was curious to use xLights to interface to FadeCandy Server running on the Raspberry Pi. Made the changes discussed in that thread (updating the FadeCandy server.json file) to listen on OPC Channel 1, since xLights can't be configured for channel 0.

Alas - that broke the existing Glediator -> ArtNet (-> FadeCandy) functionality of this project. Suspect it's a quick / trivial adjustment to the ArtNet server config to make a corresponding change to it's OPC output configuration.

Is there any downside to shifting the whole project from OPC Channel 0 to Channel 1 for broader interoperability? Had hoped to contribute by submitting a PR with both these changes -- but I'm struggling to find the authoritative documentation for the ArtNet server. My hack-y attempts to edit:

artnet/src/artnet-server_fc.py

Have not yet yielded positive results. Will update the issue, or even submit a PR, as I learn more.

Cheers!

VNC client on port 80 seems unable to connect to the on-device server even though it works from external clients.

Does this run on a Pi 4? I can't seem to get it to work. FCSERVER seems to be crashing and if I go to the IP address of the Pi, I get the Glediator interface, not the FCSERVER one.

The Pi is continuously issuing this error:

02.12.20 20:40:39 (+0000) fcserver /usr/bin/entry.sh: line 59: /usr/src/app/fcserver-rpi: No such file or directory

And FCSERVER keep trying to restart and hitting the same problem

UPDATE: I tried on a Pi 3+ and have the same issue.

The instructions here: https://www.balena.io/blog/build-festive-lighting-for-the-holidays-with-balena/

don't show a VNC process running and say that if you connect to the ip of the pi you should get the fadecandy web interface.