I’ve moved my iTunes music library content to my NAS. I’m using automount to keep iTunes happy without losing the connection to the files. After upgrading to macOS Catalina, automount did not work as it used to.
Reason is the changed structure in the APFS container. If you have a look at the disk utility, it will show you a system container and a user container. The system contains macOS and is write protected, while the user container contains all your apps, data and so on.
I’m seeing my previous installation in /Library/Developer/CommandLineTools. However, if I run
I’m seeing the installer which tries to fetch the latest Xcode command line tools. However, it always fails with
Unable to Download App. "Xcode" could not be installed. Please try again later.
I don’t intend to install the large Xcode from the appstore. So I’ve tried to delete the existing installation of the command line tools with
sudo rm -rf /Library/Developer
but the problem is still present.
Many people suggest to go to the developer.apple.com page and to search manually for the Xcode command line tools. I thought this wouldn’t work, because I’m only seeing the Xcode command line tools for Xcode 12.
However, we’re already at Xcode 12.1, so I thought this is the wrong download and is already outdated. But after I’ve installed the tools from this dmg, its working again and
xcode-select: error: command line tools are already installed, use "Software Update" to install updates
shows a suitable error message.
So lessons learned: using the latest major version of the command line tools installer seems to be sufficient.
I’ve recently deleted a large preview database file for Lightroom and was happy about the 80GB won free space. However, the MacOS disk utility as well as the terminal command “df -h” did not show the free space. I’ve also checked the trash and cleared it, but there was no change in the available disk space.
I’ve taken a closer look at the free space column in the disk utility and found a new variable behind the available disk space: GB purgeable.
I own a Xiaomi Robot Vacuum. This robot can be controlled by the Xiaomi app, however, I don’t like it very much. The idea is to control this robot over HomeKit. To use HomeKit, I use an old Raspberry Pi 1B. The software will be HomeBridge.
Use Etcher to write the image to the SD card. Remount that SD card and add a file called “ssh” in the root of the mounted partition. This will enable SSH from the beginning so that you can login directly to the Pi. I don’t want to attach a screen or keyboard to that machine so it will only be reachable over the network. Now boot your Pi from this SD card.
Identify the Pi’s IP (e.g. by looking at the network overview in your router). Now connect to that IP with user “pi”. The default password is “raspberry”. Please change the password now with passwd and assign a new user password.
According to Wojtek only this version works currently with HomeBridge. I did not test any other version so I’m just describing what I did on my machine:
Download nodejs for the PI into your users homefolder, e.g. with wget https://nodejs.org/dist/v8.9.4/node-v8.9.4-linux-armv6l.tar.xz
Unpack the file with tar -xvf node-v8.9.4-linux-armv6l.tar.xz
sudo cp -R * /usr/local/
add export PATH=$PATH:/usr/local/bin to e.g. ~/.bashrc
node should be now available
Install the necessary libraries: sudo apt-get install libavahi-compat-libdnssd-dev
Install HomeBridge with npm: sudo npm install -g --unsafe-perm homebridge
open /etc/default/homebridge and safe it with this content:
# Defaults / Configuration options for homebridge
# The following settings tells homebridge where to find the config.json file and where to persist the data (i.e. pairing and others)
# If you uncomment the following line, homebridge will log more
# You can display this via systemd's journalctl: journalctl -f -u homebridge
open /etc/systemd/system/homebridge.service and safe it with this content:
Generate a new MAC address separated by : using this website. You’ll need the IP address of your Xiaomi robot as well as the token. There are several ways to get the token. I’ve extracted mine from the iOS backup. Instead of uploading the token I’ve used this command on the token taken from the sqlite database:
Install the Home app, if you’ve removed it from your device. You can reinstall it from the App store.
Open the Home app and add a new device
If you’ve give the app access to your camera, you can scan the QR code you’ve seen earlier. However, HomeBridge is now running as a daemon in the background so you won’t see that QR code. You can add the bridge manually by using the PIN you’ve set in the config.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.