This are my notes to install home-assistant on a raspberry-pi 3. At the end, this is a multipart how-to for installing home-assistant and mosquitto (MQTT) with a NodeMCU and some magnetic contacts.
Copy Raspbian Lite to an SD Card on Mac OSX (use rdisk is faster):
sudo dd if=Downloads/2017-11-29-raspbian-stretch-lite.img of=/dev/rdisk4 bs=4m
Enable SSH (create a file named ssh on the SD-Card):
Put the SD-Card into your raspberry and boot it up.
Login and change password of user pi and root:
sudo passwd root
wpa_passphrase “YourWLANSSID” “yourWLANPassword”
Configure WLAN in /etc/wpa_supplicant/wpa_supplicant.conf:
#psk=”yourWLANPassword” <<<<<—– REMOVE THIS COMMENTED LINE!
You have a fixed IP? (preferred!)
Edit /etc/dhcpcd.conf and set the hostname inside this file.
Add config for your interface:
static domain_name_servers=XXX.XXX.XXX.XXX, XXX.XXX.XXX.XXX
Use raspi-config to configure your raspberry hostname and partition then reboot.
Continue reading HomeAssistant on Raspberry Pi
Do you want to build your Airplane tracker by yourself? It’s easy and it’s realtime, not delayed like flightradar24.
What do you need?
Here are the steps for Linux/Unix Systems:
Download and unzip the Software:
Change into the unzipped directory and execute make:
Plug in your DVB-T stick and launch dump1090:
./dump1090 --interactive --net
The option “interactive” tells the program to output planes with automatically refreshed screen every second
The option “net” enables networking support.
After a few seconds you should see the first planes:
You can even connect with your webbrowser to http://127.0.0.1:8080 to see the planes on a map.
Now you should see planes near you. It’s best to go outside with your antenna to track airplanes. You can even build better antennas 😉 See the links below.
Happy plane tracking!
DIY Antenna: ADS-B wine cork antenna
Or if you use Windows see this post here: dump1090 on Windows
Did you ever want to test the network-speed to your ESX-Host with iperf? iperf exists already on installations with vSphere 6.0. Follow this short description:
iperf is located on the ESX host at /usr/lib/vmware/vsan/bin/iperf
Execution of /usr/lib/vmware/vsan/bin/iperf gives an error:
bind failed: Operation not permitted
Workaround: Make a copy of the binary:
cp /usr/lib/vmware/vsan/bin/iperf /usr/lib/vmware/vsan/bin/iperfcopy
Disable the firewall during the tests:
esxcli network firewall set --enabled false
Start the copy of iperf:
Perform tests from client: (download iperf here)
After the tests, don’t forget to re-enable the firewall with:
esxcli network firewall set --enabled true
A project I’m currently working on, is the Arduino powered Bobbycar for my Son.
Because my Son is currently so interested in Switches / Buttons and Lights, I decided to add some on his Bobbycar with future extension possibilities.
I did not want to destroy his new Bobbycar, a gift from his Godmother. So I bought a used one (with trailer) for 20 bucks on ricardo.
Prototype cabling & programming the RBBB (Also already used in this Project):
Prototype Board designed with Fritzing:
19.11.2016: Put all together.
20.11.2016: Drilling, soldering, FINISHED 😉
Sometimes it could happen, that you get inaccessible files on your ESXi Cluster with VSAN.
Here are the Steps to clean up inaccessible files with vCenter Server on Windows 2012R2:
Connect to vcenter server with rvc.bat in C:\Program Files\VMware\vCenter Server\rvc
login with firstname.lastname@example.org@localhost:
C:\Program Files\VMware\vCenter Server\rvc>rvc.bat email@example.com@localhost
Check command: vsan.check_state “pathToYourCluster”
> vsan.check_state /localhost/myDatacenter/computers/Cluster01/
2016-07-14 07:34:49 +0200: Step 1: Check for inaccessible VSAN objects
Detected 1 objects to be inaccessible
Detected bf9c6a57-9cc3-d20c-ccb3-a0369f89ecac on 192.168.1.4 to be inaccessible
2016-07-14 07:34:50 +0200: Step 2: Check for invalid/inaccessible VMs
2016-07-14 07:34:50 +0200: Step 3: Check for VMs for which VC/hostd/vmx are out
Did not find VMs for which VC/hostd/vmx are out of sync
Delete inaccessible VSWP Objects command:
2016-07-14 07:35:00 +0200: Collecting all inaccessible Virtual SAN objects...
2016-07-14 07:35:00 +0200: Found 1 inaccessbile objects.
2016-07-14 07:35:00 +0200: Selecting vswp objects from inaccessible objects by c
hecking their extended attributes...
2016-07-14 07:35:00 +0200: Found 0 inaccessible vswp objects.
Delete other inaccessible objects:
Connect to ESXi Server and issue the following command, which should show you the related objects:
/usr/lib/vmware/osfs/bin/objtool getAttr --bypassDom -u bf
Check the output of the related object and make sure you can delete this file.
Delete the file with:
/usr/lib/vmware/osfs/bin/objtool delete -u bf9c6a57-9cc3-d
20c-ccb3-a0369f89ecac -f -v 10
Run check in vSphere Web Client on “Cluster” -> “Monitor” -> “Virtual SAN” -> “Health” -> Click on “Retest”.
Everything should be ok now.