Hello World!

When using Unity Hub on linux, some modules may seem to silently fail to install after downloading. This appears to happen mostly on Windows build target modules, which often contain compressed .7z archives.

Despite being a required dependency for extracting these archives, UnityHub might not always install 7z automatically. This issue was encountered on Unity Hub 3.15.3; other versions may also be impacted.

Checking Unity Hub Logs

Assuming that UnityHub has been installed without the use of a sandbox such as Flatpak, logs can be found at ~/.config/unityhub/logs/info-log.json. To quickly check the logs, open in a text editor and scroll to the end of the file or use the tail command.

After running Home Assistant on a trusty first revision Raspberry Pi 3b for a number of years, it unfortunately is no longer able to keep up. Both due to the incremental creep in system requirements for newer versions of Home Assistant Operating System (HAOS); Along with changing demands and extra duties placed on the machine over that time. This has resulted in large periods of time where the load is too much and my smart home goes down or otherwise becomes non-responsive.

Home Assistant provides battery readings for devices with the official companion app installed. We can replicate this functionality for other devices using the MQTT integration.

Prerequisites

• File Editor or some other way to edit your configuration.yaml
• The MQTT Integration installed
• An MQTT broker server (can use mosquitto broker addon if you wish to host locally)

Creating the Sensor(s)

Assuming you already have the MQTT integration configured with an MQTT broker server, you can add the following straight into your config.

Want to connect to a machine that isn’t directly exposed to the internet? You can achieve this by using the jump host feature built into ssh.

Command line argument

You can use the -J option with SSH to specify a jump host directly in the command line:

ssh -J jump.example.com dest.example.com

This command routes your SSH connection through the jump host to reach your final target.

Agent Forwarding

By combining this with the -A argument, you can allow the jump server to use your local machines ssh agent to authenticate with the target server. This removes the need to re-authenticate by adding your private SSH key to the jump server or reentering a login password. While convenient, agent forwarding should be used with caution. Ensure that you trust the jump server and its security, as it gains the ability to access your authentication credentials. Although the target server cannot directly see your private SSH key, it can authenticate on your behalf while you are connected.