Posts

What is Ambilight? It’s just a marketing term used by the Philips brand that describes extra RGB illumination near and/or behind the television that matches the color of what is displayed on the screen. I wouldn’t say it’s an immersive effect, but it is stunningly pleasing to the eye and removes the sharp contrast of a bright screen in a dark room. Preface I’ve had a desire to configure Ambilight on my living room television for several years. I’ve seen others with the moody backlighting behind their television, and started researching what I’d need to accomplish this. I currently have two LG WebOS televisions. One for the living room, and one for the master bedroom. I utilize Home Assistant for automation, and the majority of my lights are from Phillips Hue. Realizing that my only options were a $300 Phillips Hue Sync Box, or a Raspberry Pi running Hyperbian (Raspberry Pi OS comprised of Hyperion-NG), I threw up my arms. Not because of the price, but mainly for the fact that I don’t want extra devices and cables dangling around my TV. ...

If you have spent any time automating your domicile, you may have acquired a MyQ based garage door opener that was manufactured by Chaimberland, Liftmaster, or Merlin. Perhaps, like myself, you signed a mortgage on a home that included one or more of these MyQ openers. You were probably excited with the ability to create automations revolving around the use of garage entrance into your home. There are many great home automation platforms. I’ve used Homeassistant for the better part of six years. I’ve found the features and add-ons to be comprehensive, and backed by a bustling community that’s always available to answer complex questions. I discovered the built-in NodeRed add on as well, which I find to be superior to the built in automation of Homeassistant. So I was excited to move into my new home, especially after noticing the MyQ logo on my new pre-installed garage door openers. ...

Initialize cluster on master node curl -sfL https://get.k3s.io | sh -s - server k3s server --cluster-init --node-taint CriticalAddonsOnly=true:NoExecute --tls-san [K3S IP] --disable servicelb --disable traefik a K3S TOKEN should be generated and presented in the console, take note of it a SERVER TOKEN is also generated and stored in /var/lib/rancher/k3s/server/node-token Add additional masters curl -sfL https://get.k3s.io | K3S_URL=https://[K3S IP]:6443 K3S_TOKEN=[Token] sh -s - server --node-taint CriticalAddonsOnly=true:NoExecute --tls-san [K3S IP] --server https://[This node's IP address]:6443 --disable servicelb --disable traefik Add additional agents curl -sfL https://get.k3s.io | K3S_URL=https://[K3S IP]:6443 K3S_TOKEN=[K3S TOKEN]::server:[SERVER TOKEN] sh - Install Helm curl https://baltocdn.com/helm/signing.asc | sudo apt-key add - sudo apt-get install apt-transport-https --yes echo "deb https://baltocdn.com/helm/stable/debian/ all main" | sudo tee /etc/apt/sources.list.d/helm-stable-debian.list sudo apt-get update sudo apt-get install helm Add KUBECONFIG environment variable Add the following environment variable on the masters. ...