Ebenso die diversen virtuellen Schalter für Sprachkommandos - die sind jetzt keine Alexa-Schalter mehr (über die Cloud), sondern Matter-Glühbirnen (lokal). openHAB kann über Matter nur Glühbirnen oder Steckdosen zur Verfügung stellen, ein Schalter ist ein "Controller", kein "Controlee" 🤓

#openHAB #Matter

Openhab von 5.0 auf 5.1 upgegradet. ✅

Ärgere mich wieder einmal über die nutzlosen Fehlermeldungen. "Wir haben unsere Anforderungen geändert, deshalb musst du deinen Code ändern, aber ätschi-bätsch, wir sagen dir nicht was oder wo!"

Der Interpreter stolpert ja über eine bestimmte Skriptzeile, was die Meldung auslöst. Ist es wirklich so unmöglich, dabei die Nummer der Zeile in die Meldung mitzunehmen? 🤦

#openhab

nach unendlich langer Zeit habe ich #openhab bei mir installiert und alles eingebunden, was irgendwie Daten liefert. Meine PV und besonders den Viessmann KW200 Gaskessel mit Solarthermie. Am Kessel läuft ein Raspi mit mqtt, der die Werte via vcontrold und einem Optolink an Openhab sendet. Funktioniert perfekt (bis auf das instabile WLAN am Raspi) und ich konnte so ziemlich einfach die Heizkurve optimieren, ohne dass wir frieren müssen. Als nächstes kommt die Solarthermie hinzu (KM-Bus)

Full PDF catalog at www.creasol.it/catalog
#domoticz #homeassistant #nodered #openhab #modbus #mqtt #domotica #homeautomation #catalog #products

IME, a lot of good information on how to achieve things with the #OpenHAB Rules DSL requires good searching on the OpenHAB forums or mining through the Javadoc.

I thought I'd use Claude over the weekend/last night to help generify some stuff in my config, and it suggested a cool approach whereby I could put metadata against items and then use that metadata in my rules to customise behaviour.

It's also described here: https://forum.aqara.com/t/exploring-openhabs-rule-design-with-metadata-for-enhanced-flexibility/20956

Unfortunately, Claude seems to have just completely made up how to _read_ the metadata (validated against the Javadoc). It then proposed an alternative approach, which again seemed reasonable - but completely made up (again, validated against the Javadoc).

Trying a third time got it to say:

> Let me check what's actually available in OpenHAB for accessing metadata from rules

...and then:

> Unfortunately, accessing item metadata from Rules DSL is quite limited in OpenHAB. The documentation confirms that "Metadata can be added and removed, but not read" from Rules DSL

I know none of this is news; but... yeesh.

I had an insane push this weekend to get #HestiaPi & #OpenHAB to be compatible with a heat pump HVAC system. I'm testing it by running LEDs through the relays to see when they flip on.

I have one prototype that I manually configured. I have the basics down: heating, cooling, ruining the fan, 2-stages for both heating and cooling.

Next up, boosting and tons of regression testing. I rewrote huge parts of many of the roles and made serious logic/flow changes.

I need sleep too!

Re-sharing publicly my fun #openHAB rule to have my microwave's clock always set to the right time by briefly cutting its power at midnight every night.

Tomorrow we'll see if it works 😅

The house didn't properly wake up this morning, so that needs debugging today.

It seems there were some changes/fixes to groups in #OpenHAB, so it could be that (maybe).

This morning I upgraded #OpenHAB from 2.5 to 4.3. Mostly things are working. Mostly.

I also tried to use `adb` to disable background stuff like Alexa on our #Philips #AndroidTV - if nothing else to try and get the Channel 4 app working reliably.

It is not better 😡 - happily shows adverts but then crashes when it gets to the programme proper.

Meine alte OpenHAB <> MQTT <> Beaglebone Black <> Python <> DIY Platine <> Hausbeleuchtungssteuerung. :)

Ton an um die Relais klackern zu hören. ^^

#smarthome #electric #openhab #diy

I have a much better opinion of #musicassistant. It's still very buggy but in this case I can understand. Media streaming is complex and messy, I think the Music Assistant developers are doing a good job overall. I wish it had better integration with #openHAB. I guess I'll have to take care of that myself.

I honestly don't understand why people like #homeassistant so much. It's confusing, full of limitations, it literally runs random Python code it finds in the MQTT broker without asking (https://www.home-assistant.io/integrations/mqtt/#value_template), but most importantly...

How can you stand the level of enshittification it has reached? They make everything so hard to do locally unless you buy their hardware and their shitty cloud based subscription.

I really do not understand how it came to be this popular.

I get that #openhab uses more memory and it has a bit of a learning curve to set up, but so does Home Assistant! It would take me an entire weekend to sort that awful dashboard in Home Assistant, and I've already hit a brick wall trying to get my Garmin smartwatch to control HA.

Please, people, I beg you, give openHAB a shot. It's a great, well designed project, built by an organization that is *actually* not for profit (https://www.openhab.org/imprint.html). It's already great, let's make it more popular, attract contributors and make it even better.

Linux Box Dev Edition brings Armbian Linux with Home Assistant support

https://fed.brid.gy/r/https://linuxgizmos.com/linux-box-dev-edition-brings-armbian-linux-with-home-assistant-support/

Four weeks (One Month) since #HomeAssistant published their intent to deprecate http.server_host for all installation types, because it doesn't spark joy (apparently breaks Supervised Backups, I don't know) for them.

https://github.com/home-assistant/core/issues/157961

There have been _zero_ responses by Home Assistant team members.
I'm contemplating moving away to #OpenHAB.

https://www.openhab.org/blog/2025-12-22-openhab-5-1-release.html

#openHAB

Puuh, Upgrade von #OpenHAB Version 5.0.3 auf 5.1.0 unter Debian Linux ... und es hagelt im Anschluss "communication error"-Meldungen und Binding-Issues im Webfrontend. In den Logs nix Offensichtliches zu finden. Zwei oder drei Neustarts (auch die ganze VM), keine Besserung.

In der Verzweiflung nochmal die gleichen Pakete mit "apt install ... --reinstall" drübergebügelt, und es läuft plötzlich direkt ohne Probleme.

Sowas macht mich dann doch etwas stutzig 🧐 ... das hatte ich jetzt schon mehrmals bei OpenHAB.

My #openHab instance has started throwing 401 errors for `strict-origin-when-cross-origin` without me to my knowledge changing anything.
I'm using a #nginx reverse proxy, and I'm having trouble figuring out if nginx or openHab itself are generating the 401 errors.
And unless I don't understand this at all, the origins are correct

#openhab Wechsel von Raspberry zu Debian VM hat keine 5 Minuten gedauert, dank openhabian Backup. Damit hab ich nicht gerechnet 🔝

Plus: openhab 5 schleift soviele Ecken und Kanten, dass es mittlerweile grandios einfach ist, ein "smartes Home" ohne Datenschutzprobleme oder Vendor-Lockins zu haben 👍

#Velbus turned out to be the rock solid open home automation system, easy to extend and easy to integrate. #OpenHAB link? No problem. #HomeAssistant? No problem. Industrial 4..20mA or 1 to 10 V sensors? No problem. Relay output/input? No problem. Power measurement, access control, RGBW LED lights, meteo station to control window blinds. So far I could not find anything that can't be done with Velbus and OpenHAB 😍 I started a page to gather all Velbus related info: https://velbus.wiki

Starting to think that using #OpenHAB for my "smarthome" for my case is kinda overkill…

I have some sensors (temperature and humidity), some reed switches for windows and possibly I'll add thermostats for heating batteries (because here, even with 0°C outside, the central heating works for all the money and it is impossible to sleep and work without all opened windows). All things are using #ZigBee so my #server uses some ZigBee coordinator dongle and #zigbee2mqtt with some MQTT broker inside. I already able to read all necessary data from sensors by reading the right MQTT topics.

And the OpenHAB just communicates with my MQTT broker and displays some nice widgets on the Web UI. This is cool, because I don't need to think about how to work with MQTT and how to output data — all somehow works "by magic".

But the price is very big. The OpenHAB eats near 600 MB of RAM and swaps a lot (near 1 GB for now). It is a largest memory consuming service in my server, which has only 2 GB of RAM (and a RAM prices already increased here :drgn_sigh: ). And also it's sandbox takes near 3.5 GB of SSD space.

So, do I really need not to think about how it all works under the hood while wearing out my SSD or get some services OOMed if I disable swap and start e.g. using BorgBackup? Looks like the game is not worth the candle. I can literally pick #EclipseMosquitto #C library, unwrap some memories about how to use CGI and get the same nice page with sensors data and some logic inside. But with a waaaay less memory footprint and with possibility to open this page from #Dillo :drgn_happy_blep:

#SelfHosting