ads' corner

Occasional HABpanel disconnect from the openHAB server

The new display showing HABpanel works quite nice. But occasionally the fullscreen browser will lose the network connection. As far as I can see, it’s not a Wi-Fi problem of the Raspberry Pi, but still annoying: in the morning the browser shows a small red warning that the connection to the openHAB server is lost, time is still correct, but temperature and the status of other devices is outdated. To fix that, I have to leave fullscreen mode, hit reload - and then there is no keyboard for going into fullscreen mode again (that’s using the F11 key).


Automatically start a fullscreen browser on a Raspberry Pi - show openHAB HABpanel

The Raspberry Pi with the touch display for the home automation system is coming along nicely. One problem to solve: how to display the openHAB HABpanel, and which browser to use?

Firefox and Chrome don’t run on Raspbian. However Chromium (the open source part of the Chrome browser) is. That’s a good start. But how to start the browser automatically, and in full screen?


Raspberry Pi: disable Wi-Fi powersave, and stay connected all the time

Recently I installed a Raspberry Pi with Raspbian, and attached a touchscreen to it. The device is supposed to work as a display for our openHAB home automation system. All nice and shiny, except the Pi occasionally disconnects from the Wi-Fi - apparently in order to safe power. Once the network device is needed, the Wi-Fi is reconnected. That is the default setting.

That is quite annoying, because the HABpanel will lose it’s connection to the openHAB server, and no longer show widget updates. Some widgets like “time” will just continue to work, but other widgets like status of the washing machine, or the current outside temperature just show the last state, and never update.


openHAB: widget with multiple different background colors

Previously I blogged about how the washing machine and the dryer are integrated into the openHAB home automation system.

For a while I had a standard Dummy widget in HABpanel, but that didn’t look very nice, was very standard, and the different icons for different states don’t really work. When I started integrating another Raspberry Pi with a touch screen (blog post to come), I refreshed the HABpanel, added another dashboard, and along the way I wrote a new “Template” widget for the washing machine and the dryer.


Raspberry - Raspbian - First steps

Installing a new Raspberry Pi is always the same few steps, and still I have to look them up almost every time. Here is the summary.


Avoid "wear out" of SSD-cards in an openHAB system

You might know that problem: the brand new SSD in your system is super fast, but after a good time using it, the card is dead. Unlike spinning disks, which usually fail over time, and show I/O errors by blocks, SSD cards are prone to a problem called Wear leveling. Blocks which are written more often will “wear out”, and become unresponsible. More writes increase this risk. And a typical openHAB system does a number of writes all the time: every time an external status changes, it’s written to the event log. By default the syslog is written to disk as well, and then there is a myriad of systemd services, writing status information into files.


Configure a FRITZ!Box in openHAB, using Ansible

A while ago I posted about adding a Fritz!Box to openHAB, using Ansible. Now I had to use the Playbook to install another Raspberry, and found that some parts are missing in my posting. Mostly at the end, when it comes to configuring the Fritz!Box.

Therefore let’s run over all the steps again, and make sure that everything is covered.


Install openHAB2 bindings using Ansible

Recently I started looking into Home Automation, using a Raspberry Pi and the openHAB as platform. The website provides ready-to-go images based on Debian, named openHABian. Me being me, I decided to install the image, let it boot up for the first time, and then take it from there using Ansible as automation tool. That’s a bit more effort in the beginning, but ensures that I can always just wipe the SDcard, and start over from the beginning. Especially useful if I screw up at some point during testing.