Random thoughts

 I've been using quick launchers like kupfer or ulauncher for a while, but I needed to switch to something else because kupfer tends to crash from time to time (Ubuntu 20.04) and ulauncher is a memory hog with lots of plugins ( https://github.com/Ulauncher/Ulauncher/issues/590 ). I've looked around and rofi looks like a great little launcher - with the added bonus that it runs only when you launch it (it's not resident in memory). For best features it should be installed from git, not apt (instructions here: https://github.com/davatorium/rofi/blob/next/INSTALL.md ). First prepare the build environment. You'll need to enable deb-src in your /etc/apt/sources.list for this to work. Make sure you have the correct distribution (in case you did a do-release-upgrade you may have wrong deb-src entries commented out): https://unix.stackexchange.com/questions/537537/how-to-put-some-source-uris-in-your-sources-list sudo apt-get build-dep rofi git clone https://github.com/davatoriu...

I've been working for a while on this project - with the purpose of getting SmokePing measurements from different hosts (slaves) into InfluxDB so that we can better graph them with Grafana. The slaves run multiple Smokeping instances inside Docker so that they have separate networking (measure through different uplinks, independently). This will not be a comprehensive configuration guide, but a quick "how to" to handle setup and basic troubleshooting. It assumes you already know how to set up and operate a regular Smokeping install with or without slaves and that you are fluent in Smokeping configuration syntax, know your way around Docker and aren't a stranger from InfluxDB and Grafana (sorry, there's a lot of information to take in). 1. Getting Smokeping with InfluxDB support - you can get it either from the official page (most changes have been merged) - https://github.com/oetiker/SmokePing (PR discussion here: https://github.com/oetiker/SmokePing/issues/...

Here's a quick setup guide for controlling your Android TV from within Home Assistant. I've used it to control a genuine Android TV (Philips 7304) and an Odroid N2 running Android TV. For this to work you need ADB access. It can usually be enabled from within Developer Settings. The great part is - you don't need root access! The most important things are described in the androidtv component for Home Assistant: https://www.home-assistant.io/integrations/androidtv/ Make sure you go through the adb setup. My configuration is simple (inside configuration.yaml): media_player:   - platform: androidtv     name: TV Bedroom ATV     host: 192.168.1.61     device_class: androidtv Once Home Assistant restarts, your TV might require you to accept the connection (adb authentication). This happens only once (or until you reset your ATV to factory settings). Once running the integration will show you the current ATV state (on or off) and al...