This is amazing! Thanks so much for putting this together and sharing here. I’m totally going to get this setup at home and give this a whirl. Excited to see what else you create and please let us know what we can do to best support you. Something like turning off the screen feels like something we should support and would make the Homebridge integration even better.
Let us know if there are any other limitations that you run into that would make your time easier and we’ll see what we can do on our end!
Thank you for putting this together. I’m not very technical but can usually follow instructions. However, I’m having issues following this. I was able to install homebridge on my NAS; i believe it is a docker container. Do you have any idea how I could install pixlet in this container within homebridge? Could I use the homebridge terminal?
It is hard for me to help since I’m not familiar with your NAS setup, but if you are adding customizations to Homebridge it might make sense to build a new Docker image that bundles Homebridge + Pixlet + your homebridge plugins (like homebridge-tidbyt) and run that on your NAS instead.
Alternatively, your setup may allow you to put the Pixlet binary on a data volume or mapped host directory and then perform the setup after attaching to the running container with docker attach.
I’m running Homebridge on a Raspberry Pi and simply installed a pre-compiled Go binary and built pixlet from source there.
I’ve added a new feature to Custom Apps: Config Scripts
Config Scripts are Node.js modules that you can execute to dynamically build configuration parameters before they are passed to the Render Script . This allows you to tap into the vast ecosystem of modules available on npm to build your own connected applets.
A Config Script is a very simple Node module that exports a single function that returns a Promise that resolves to an array of key/value pair objects. The most trivial example looks like this:
I’ve put together a little tutorial to demonstrate how Config Scripts can be used in conjunction with Render Scripts to pull data from the XBOX LIVE API and push your Gamerscore to your Tidbyt device.
Wow thank you so much for getting this created!
I was curious, what do you have homebridge setup on?
I’m on a Raspberry Pi 4 w/ Raspberry Pi OS but have been unable to get pixlet installed.
Any chance you have a similar setup?
The file would be /home/pi/.bashrc. By default, ls does not show hidden/dotfiles, so the file prefixed with a period does not show. you can use ls -a to show them.
If the file doesn’t exist you can create it with those lines and it will be fine.
Alternatively, you can avoid ~/.bashrc and alter the build command instead like this:
cd pixlet && PATH=$PATH:/usr/local/go/bin GOPATH=$HOME/golang make build
From your last screenshot, it looks like you’ve moved the entire pixlet source folder into /usr/local/bin. What we wanted to do was move the built binary there instead.
Move the source back to your home directory
> sudo mv /usr/local/bin/pixlet /home/pi/pixlet
Build pixlet:
> cd /home/pi/pixlet
> sudo PATH=$PATH:/usr/local/go/bin GOPATH=$HOME/golang make build
> sudo mv pixlet /usr/local/bin/pixlet
Ahh i think i figured out the missing step.
After sudo PATH=$PATH:/usr/local/go/bin GOPATH=$HOME/golang make build
I had to cd /home/pi/pixlet/build/out then sudo mv pixlet /usr/local/bin/pixlet