EzTemp&RH crowdfunding project

Today Eloísa Romero sent me an email presenting me her EzTemp&RH crowdfunding project.

20140912094736-EzTnRH_labeledI really like it. It takes away a lot of the hassle you encounter when measuring temperature and humidity. It also features some quite precise components, including an auxiliary connection for an additional sensor of your choice. Great for an Raspberry Pi!

Take a look at the projectsite. https://www.indiegogo.com/projects/easy-temperature-and-humidity-for-raspberry-pi

Cresta TX320 longer antenna

Last week I bought 5 sensors of the type Cresta TX320 for my Domoticz system. Unfortunately they have a very weak transmitting signal strength. One HR++ glass pane and a concrete floor is too much to reach the RFXTRX433e transceiver. I removed the old internal antenna and exchanged it with a solid wire matching the length of 1/4 of the wavelength of the 433Mhz band. That is 17,3 cm from the PCB to the end of the wire.

Please note that I routed the whole antenna out of the top of the device. Routing it downward causes quite a lot of the signal strength to be absorbed by the batteries, which then are close to the antenna.

This setup still has a weal signal strength, but just enough to reach my transceiver.

Cresta TX320 with longer antenna

Cresta TX320 with longer antenna

Cresta TX320 with longer antenna

Cresta TX320 with longer antenna



Home Automation System – Part I

Last week I managed to get WiFi working on my Pi. Because yesterday my Slice of Pi arrived from Ciseco, I could continue building the heart of my Home Automation System (HAS).

The core of my HAS will be the Raspberry Pi. It will be connected using WiFi but communication between sensors and actuators inside the HAS will be done over 868Mhz using XRF modules. So today it was time to add an XRF module to the Pi using the newly arrived Slice of Pi, and an XRF radio I had in stock.

After assembly I installed Minicom on the Raspberry Pi, and connected to its serial port. Then I plugged in a SRF Stick in my Mac to check the connection using the handy tool “CoolTerm”. Everything turned out to be working. Very nice!

Please note that Raspbian has a getty on the serial port by default. So do remove it to get an interface to the XRF. Remove the references to ttyAMA0 from /boot/cmdLine.txt and /etc/inittab.

Next: Building a framework on the Raspberry Pi in Java which will be used for data retrieval and event triggering. Also have to decide which DBMS will be used on the Pi.

To be continued…..

Soldering the Slice of Pi

Finished soldering the Slice of Pi

Finished the assembly. One problem….the case can’t be closed anymore.

Casing fits after making a hole ;)

Cheap and green homelab – Part III

The last few weeks my homelab made a whole different turn. No ESXi, No Hyper-V, No XEN Server. I gave Proxmox a try, and I’m loving it. You get a fully functional and competing virtualisation environment for free. Yes, you can buy support subscriptions, but apart from that you get the whole package opposed to VMWare.

The web interface is pretty awesome. Taking over the console is easy and uses a small Java applet or Spice. This is a huge pre for Proxmox compared to ESXi and Hyper-V which require a Windows client for management purposes.

Give it a try. You’ll love it!

Raspberry Pi WiFi

Today I decided to buy myself a Raspberry Pi – Model B. Going to use it in my home automation system. Because the Pi doesn’t have WiFi onboard you’ll have to use a WiFi dongle. Still had a Sitecom N300X4 laying in the drawer. After trying some different setups, I now have a good one.

——– lsusb listing of the N300X4
Bus 001 Device 004: ID 0df6:0060 Sitecom Europe B.V. WLA-4000 802.11bgn [Ralink RT3072]

——– /etc/network/interfaces – wlan0 config
#allow-hotplug wlan0
auto wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet static

——– /etc/wpa_supplicant/wpa_supplicant.conf – WPA2 WiFi
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev

pairwise=CCMP TKIP

Ditching Ziggo VOIP

After Ziggo (my ISP) announced to stop (april 1st 2014) the free calls between Ziggo members, I decided to take a look at something different. The new offer of Ziggo is to pay them 9,95 Euros per month to get our free calls back. Huh? Free calls? !@*&^%$

Some calculations:
At the moment our subscription consists of a standard 9,95 Euro fee each month. No free minutes in that subscription, but because we mainly call other Ziggo members we get a lot of minutes for free that way. It was a selling point years ago.
An average month:

  • 205 minutes to other Ziggo members = 0 Euros
  • 80 minutes to non Ziggo members = 7,20 Euros

This brings the total of such a month to 17,15 Euros (standard fee + minutes).
As of the 1st of April I will pay them (at least they hope) 35,60 Euros (285 minutes at a 9 cent rate + standard fee). Ziggo, are you nuts?

Ah well, they have their great offer now. If I pay them 9,95 Euros (standard fee) plus an additional fee of 9,95 Euros, I get free calls to everyone. Free calls after paying 2,75 Euros extra each month. That’s not going to happen!

So I decided to take a look at some cheap VOIP providers. I don’t need you for my voice dialling Ziggo!

Looked at Skype, VOIPBuster but eventually ran into CheapConnect. A Dutch company offering VOIP for great rates. At MAX ICT I bought a Cisco SPA112 ATA which can convert VOIP to an analog signal my home telephone can use. This is because when I leave Ziggo VOIP, they won’t let me use the VOIP-port on their modem. ;)

Today I went to pickup my SPA112 and it turned out to be a good investment. Hooked the thing up to a test account at CheapConnect, and I started calling within 5 minutes. Good sound quality and excellent rates.

A calculation:

  • Voip In/Out account = 0,75 Euros per month (8,95 Euros per year)
  • 265 minutes = 6,30 Euros per month (0,0238 Euro per minute)

Compared to the Ziggo offering, this solution is 12,85 Euros per month cheaper! I should have done this much earlier.

Ok, lets be honest. I had to buy the SPA112 costing me 42 Euros, and I have to pay CheapConnect a one-time fee of 5 Euros to port my old number from Ziggo. That’s a one-time investment of 47 Euro which I will earn back in less than 4 months.

Ziggo, thank you! Thank you for trying to let people pay extra for free minutes. Thanks to you I will save 155 Euros each year!

Cheap and green ESXi homelab – Part II

After a week of giving several hypervisors a try, I came to the conclusion that Microsoft Hyper-V is my current preferred choice.

Why? ESXi seems to be an obvious choice, but VMWare is clearly taking the home labs out of business by silently making the VSphere Client obsolete. I also tried Citrix Xen Server. A nice product, but something simple like adding additional local storage can’t be done through the GUI. That’s just plain stupid, and I don’t like stupid products.

Currently I’m sticking with MS Hyper-V Server 2012R2. It’s free to use, and comes with a nice feature set. Setting up management in a workgroup environment can be a bit pain in the ass, but eventually it works quiet well. The Hyper-V Manager though is a bit error prone when working on a weak WiFi connection with lots of packet loss.

Today I bought a new WiFi router. It’s a Asus RT-N66U. It performs great even through my concrete floor. Ping times are stable around 3 ms and the throughput is 5 times faster than my old router.

Additional posts on this topic won’t be called “Cheap and green ESXi home lab”, because of the choice for Hyper-V. ;)

Cheap and green ESXi homelab – Part I

In the need for a lab to exercise for my MCSE and MCSD certifications, I have been busy lately figuring out the right way to set it up. ESXi is chosen as hypervisor, because I can choose to run HyperV on top of it, enabling me to play with both hypervisors, without dismantling my infrastructure. The other way around isn’t a possibility.

A few possibilities that passed my mind:

  • Use my old PC to host the lab.
    Gave it a try, but only having 4GB available turned out (obviously) to be a big problem. The CPU was allright (i7 870). Storage consisted of a stack of WD green disks, which  ran into performance issues right away. RAM was the first bottleneck to upgrade. Too bad the maximum amount of RAM was 8GB. Trashed this possibility.
  • Use my PC at work through VPN.
    PC has a bit more memory (16GB), so that shouldn’t be a big problem. Processor (a cheap i7) also no problem. IO a BIG problem. The disk in this machine turned out to be even worse than my WD green disks. Trashed this possibility.
  • Get a bit of resources on a corporate ESX test cluster.
    No cluster existed, so this was an easy one.
  • Privately rent a bunch of VPSs.
    Turned out to be fairly expensive, although some do have very nice offerings. Please check out: http://klauwd.com I will probably use them for one of my other projects.
  • The last option was getting a better PC at home. Because my home is fairly Mac centric, I wasn’t too happy with this solution, but it turned out to be te most viable one. I have taken a look at getting a second hand Mac Pro 3.1 or 4.1, but these pieces of art still cost a fair amount of money. Too my opinion a bit too much.

So I was really getting a PC. Looked at two particular machines that are currently reasonably priced second hand. The HP Z600 and the Dell T5500. Both have great specs like the option to have Dual CPU – Quad Core Xeon running at 2.93 Ghz. Giving me 16 threads. Awesome. Second biggest issue still is the storage. Dead slow 7200 RPM SATA or SAS disks. This would require an investment buying me a few SSDs, next to the expensive machines, making it a double expensive option. But the biggest problem these machines have, is the lack of energy efficiency. The T5500 heating up my desk from underneath it, wasn’t a very pleasing idea.

I decided to build something by myself. My first PC build since the 90’s. My old 8088 and 80386 didn’t even need any heatsink. The old times, when you needed to change the crystal, if you wanted to change your CPU speed.  True jumperless ;)

My new PC had to be cheap, green and fast for the purpose of this lab. So CPU isn’t that important. Running a typical MS AD lab doesn’t utilize your CPU that much. Storage is a whole different story. That needs to be fast, preventing me from getting annoyed. There also has to be enough RAM to accommodate all the virtual machines.

Anyways, as a Mac enthousiast I decided to choose the the casing of my new PC first. It should be simple, cheap and the less ugly one (because they are all ugly) I could find.
I ran into a brand Fractal Design. They make some very simplistic cases, so I decided to buy their cheapest model. The Fractal Design Core 1000 USB3. Simple, not hitting the top on the ugly scale and cheap.

The processor had to have support for VT-X, VT-D and I decided to be happy with a Quad-core non-HT model. HT doesn’t deliver that big an advantage, especially in my lab environment. Nice piece on this subject: http://wahlnetwork.com/2013/09/30/hyper-threading-gotcha-virtual-machine-vcpu-sizing/
I decided to buy the Intel i5 4440 processor. A common CPU, on-cpu graphics, well priced.

For the memory I just bought the cheapest 32GB DDR3 1600 RAM I could find.
4 x Crucial Ballistix Sport BLS2CP8G3D1609DS1S00CEU

The motherboard had to be sort of out-of-the-box ESX compliant. Because it had to be cheap, I decided to drop full compliancy right away. I came up with a board that works great after injecting a NIC driver into the ESXi installer ISO. ASRock B85M Pro4

Storage had to be SSD. All my Macs have SSD and it’s just awesome. Booting a physical or virtual computer from a conventional harddisk should be forbidden by law.
Decided to buy 2 240GB SSD’s to accommodate the VMs. Crucial 2.5″ M500 240GB
One of my old Apple disks will contain installation sources.

The whole config including everything like PSU, SATA cables costed me around 750 Euros. I sold my old PC for 300 Euros.

In the near future I will post my experiences regarding this setup. Beneath are a few pics of the building proces in reverse order:

ESX Booting

ESX Booting

The finished product

The finished product

Everything connected

Everything connected

Disks on the tray

Disks on the tray

Position of the disks

Position of the disks

CPU mounted

CPU mounted

Starting the wiring

Starting the wiring

The motherboard

The motherboard

The case

The case




Sabayon 4.2 on a Dell XPS M1330

During my quest finding the perfect GNU/Linux distribution for my daily computing needs during the last 13 years, I have ran into Sabayon Linux. Sabayon 4.2 to be precise. You can get it in two flavours a KDE and a GNOME flavour.
I don’t care about either of those two. I want to use XFCE this time.
Because Sabayon doesn’t come in an XFCE flavour, you’ll have to choose GNOME or KDE to startup with.
I have chosen KDE….but GNOME is fine too.

During installation you’ll have the option to chose the kind of installation. Or KDE (or Gnome on the GNOME DVD), or XBMC, or FluxBox, or blablablabla.
Obviously no XFCE there either…..Because I wanted a clean starting point, I chose to go for the FluxBox installation.
That way I would have a minimal and more important clean installation perfect for installing XFCE later on.
The installation is pretty straight forward. Not very much additional choices that can be made.
After installation the idea of the clean installation went up in flames.
Despite the fact that I chose for the FluxBox installation a lot of KDE stuff was installed.
Ah well….we can uninstall the useless stuff later on, as I did.
Sabayon 4.2 does a good job handling all my notebook’s hardware. Everything is detected and it all works out of the box. No need to install the Nvidia drivers…they are already there and just work. No need to fiddle with my soundchip….it just works. Just install XFCE and you’re ready to go. Thumbs up to Sabayon!

A few things I had to alter to the configuration to get rid of some annoyances:

* System bell/beep
One of the most anoying things while working in the terminal on Linux is the system bell.
Especially if you like to use tab (auto-completion) and you don’t have an exact match.
On Sabayon (not sure if it is Sabayon or my M1330) the beep isn’t a real beep. It’s even more annoying.
It’s some sort of high pitched chicken. Had to get rid of that one….fast.
You can easily achieve that by editing the following items:
– Uncomment the “#set bell-style none” to make it look like “set bell-style none” or if you like “set bell-style visual” in the file /etc/inputrc.
This disables the beep in the consoles after reboot.
– Add “/usr/bin/xset -b b 0″ to some of the possible places for this. Like your X session manager or xinitrc.
– Add “blacklist pcspkr” to the /etc/modprobe.d/blacklist file.
This disables the pcspkr kernel module after a reboot.

* Trackpad
The M1330 has a fairly small trackpad. Sabayon by default has trackpad scrolling enabled on the edges of the pad. I don’t like that. If you want to disable this, open “/etc/hal/fdi/policy/11-x11-synaptics.fdi”. In this file you’ll see four lines that say something about scrolling. Depending on your needs set the ones you don’t like to “false”. I personally disabled all…..what a relief.