A while ago I upgraded openHAB from version 2.4 to 2.5. That comes with the usual share of problems, but eventually I got it working.
A while ago I upgraded openHAB from version 2.4 to 2.5. That comes with the usual share of problems, but eventually I got it working.
A while ago I got a recommendation to look into a Raspbee (from dresden elektronik) as Zigbee gateway. That looked like fun, therefore I ordered one of the devices. The first step is the installation of the Pi itself and then the software for the Raspbee.
The openHAB display in the kitchen is still the problem child. Occasionally it just stops, other times it does not refresh the HABpanel, even though it has a connection to the openHAB server. Then there is the problem with the network card in the Pi. And - ok, that’s a server-side problem - occasionally the weather stops updating. All in all that’s a lot of trouble for a display which is just supposed to run standalone.
In the latest iteration I looked into activating the integrated hardware watchdog in the Raspberry Pi. Checking the temperature it never goes above ~55°C celcius, even though the display is in an almost closed frame and can’t exchange much heat with the environment. But nevertheless occasionally the Pi just halts, and stops operating.
As mentioned in my previous openHAB blog post: it seems to be too much to ask to have a reliable and working display in the kitchen.
Another problem I found is that the weather data occasionally does not update. Everything seems to work, no errors in the log, just no updated data. Of course this results in outdated weather info in the kitchen, and the threat that “someone” will buy a regular weather station and render my 7" Raspberry display useless.
Another Ansible upgrade, another Playbook failing.
I have a number Playbooks which run on virtual machines. Some tasks are “outsourced” to the physical machine where the VM is running on, using delegate_to. One of the tasks (which I haven’t used in a while, because I rarely touch this machine) stopped working, and instead throws a variable undefined error. But from the beginning, here is the VM Playbook:
Every time Ansible runs a Playbook, the first step (by default) is gathering facts about the target system:
About two years ago I blogged about how to create and renew Let’s Encrypt certificates using Ansible. Back then, the “letsencrypt” module was State of the Art. This changed, and with all the Let’s Encrypt API changes, the Ansible module changed quite a lot, and is now “acme_certificate”. ACME stands for: Automatic Certificate Management Environment, and is the idea that every step along the way of creating and renewing certificates should be automated. No more manual creation of CSR (Certificate Signing Request), sending them per mail or manually uploading them to a CA website, enter your credit card details, and at some point get a mail back with the new signed certificate. All of this (except the credit card - you no longer need one) can be automated, and handled in a matter of seconds.
Time to write an updated blog post for the new module.
Another Ansible upgrade deprecation warning, which appears in Ansible 2.8:
The Ansible 2.8 upgrade brought a few failing Playbooks. I ran into the following error:
The openHAB HABpanel we have in the kitchen runs on a Raspberry Pi and uses a touchscreen display. The browser starts in fullscreen mode, and shows a specific HABpanel screen for this display. That’s all nice, but by default the mouse cursor is in the way. Let’s get rid of it.
The Raspbian system which runs on the Pi comes with a package called unclutter. This hides the curser after a few seconds. All I have to do is install the package, and start the app. Right?