Among the numerous Note taking applications Joplin is the one I prefer to use on my daily basis. In this guide you can learn how to set up a Joplin Server on a Raspberry PI to sync your notes across different devices.
Many guides exist describing how to flash a CC2531 USB adapter using a Raspberry Pi instead of a CC debugger. The problem with almost all of those guides is that they are outdated and don’t work on newer devices (specifically with 64 bit architecture). Most of the times the issues have to do with outdated version of wiring PI, or the precompiled for 32 bit devices cc_* binaries (cc_chipid, cc_read, cc_write). In this guide you will learn how to flash CC2531 using a Raspberry PI 4 or any other device with 64 bit architecture OS.
Today I read this official document (published on September of 2022) which describes how to change the MAC Address of Raspberry PI Devices. Interestingly it describes a different method for Raspberry Pi 4, 400 and CM 4 by editing the EEPROM configuration, using the following command:
sudo -E rpi-eeprom-config --edit
In the configuration file append a new line with the required MAC Address as follows:
Save the new configuration (Use Ctrl + X to stop editing, Y to overwrite current file and ENTER to confirm). Upon saving the following message appears:
Finally, reboot your device in order to apply the new MAC Address. Warning If the device gets IP from a DHCP server, then most probably after the reboot it will be assigned with a new IP address.
This is a different (and simpler) technique from the one which I described in a previous post (which works for all models)
Even if your home’s automation is separated from any other network and not internet accessible, it’s always a good practice to use encryption. Failing to encrypt the connection to HomeAssistant’s web interface using an SSL/TLS certificate, results in leaving your password and other data traveling the network as plaintext susceptible to eavesdropping.
In general a watchdog is a piece of equipment that supervises other systems and resets them in case it detects that those systems are failing, automating the process and increasing the reliability of the system. Network Watchdog is a simple watchdog for monitoring network connectivity and power cycle a device based on ICMP ping replies.
With it’s minimal power requirements, Network Watchdog can use the controlled device’s DC Power source (between 5 and 12 volts) to function, avoiding any additional power requirements. The following is an example setup:
If you happen to read the previous post, this one is an extension to the BYOPM device for enabling 2FA on the VaultWarden instance using a Solokey. Two Factor Authentication (2FA) is implemented to better protect both a user’s credentials and the resources the user can access.
BYOPM is a portable Password Manager implementation based on VaultWarden, an unofficial implementation of BitWarden and a Raspberry PI Zero. It’s a self hosted solution, with full functionality, which is activated by just plugging the device on your computer. Bitwarden’s Official browser addons and extensions are also supported, and the device has been tested both on Windows (10 and 11) and Linux (Debian Based).
This is how to enable Home Assistant’s SMS Integration Service using the Geetech Arduino GPRS Shield (based on the SIMCom SIM900 module) on a Raspberry PI 4 over serial communication. The host system is using Home Assistant Supervised which was deployed in docker.
Windows offer many different ways to manage your Network Connections including adapters status/configuration and network routing from the Command Line. The most frequently used are the Windows Management Instrumentation Command Line and the Netsh Command Line utility. Those commands can be used to automate Network Configuration in Batch Scripts.
Due to the fact that Hypervisors stand between hardware and software, they sometimes disrupt the proper communication between the two causing the software to fail. One such case is when software is locked on specific hardware, for example Microsoft Windows Server ROK.
If you follow the default procedure and install the OS directly on the server then everything runs fine without any issues. But what happens when you want to install the OS as a Virtual Machine on the same server? Well if you are using oVirt as your virtualization solution then you get the following message: