Question 1

How to ensure YAML-defined items and things are loaded correctly during openHAB startup?

Accepted Answer

The default start level configuration in services.cfg does not include YAML providers. As a workaround, manually edit the services.cfg file (located in the openHAB userdata/etc directory) and add YAML provider entries to the relevant start level lines. For example: ```startlevel:20=dsl:items,managed:item,dsl:things,managed:thing,managed:itemchannellink,dsl:persist,managed:metadata,yaml:items,yaml:things,yaml:persist``` Also add `managed:persistence` to level 20 if missing. Restart openHAB after changes.

Question 2

Why does my openHAB DSL rule with switch-case fail to load after updating to snapshot 5380?

Accepted Answer

A parsing bug introduced in commit e2aacb11 causes switch-case statements with numeric cases of two digits (e.g., case 10) to fail with 'mismatched character' or 'no viable alternative at input' errors. Workaround: Use single-digit numbers (0-9) for case values, or rewrite the logic using if/else if/else blocks. Track issue #5586 for a fix.

Question 3

Why is my openHAB thing handler initialize() called twice when using YAML thing definitions, causing 'handler already disposed' warnings?

Accepted Answer

This is a known timing issue in ThingManagerImpl when YAML things are created before the binding starts. The handler may be initialized twice without disposal. Fix: In ThingManagerImpl.java (path: bundles/org.openhab.core.thing/src/main/java/org/openhab/core/thing/internal/ThingManagerImpl.java), change method `thingUpdated` at line 467 from `unregisterHandler(thing)` to `unregisterAndDisposeHandler(thing)` to ensure proper disposal before re-registration. Rebuild or replace the core.thing JAR.

Question 4

Why do I get a NullPointerException in openHAB rules when using variable names like 'ms' or 's'?

Accepted Answer

This is caused by new reserved keywords introduced in DSL conditions (e.g., 'ms', 's'). Any string defined in the grammar becomes a global keyword, blocking its use as a variable name. Rename the variable to something else (e.g., 'myMs'). The misleading error is a known issue; track #5498 for a clearer error message.

Question 5

How to fix semantic model inconsistencies after upgrading to openHAB 5.1 when custom tags became standard?

Accepted Answer

Delete and recreate the affected items. This clears stale semantic metadata that is no longer updated. Track issue #5363 for a possible permanent fix.

openHAB Core

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects