Configuration of openHAB

Development
72

I think you are still not understanding what I am proposing. The yaml file is a drop in replacement for the jsondb. But with the yaml file structure it is possible to move configurations into another yaml file or while it still can be used with the yaml parser. This provides the flexibility for proper configuration.

Example:
Openhab does auto discovery and detects a z-wave device and links some items. This is what gets created

- zwave:
  - device 1
    - channel1
    - channel2
- items:
  - name : item1
    channel:
    - zwave:device1:channel1
  - name : item2
    channel:
    - zwave:device1:channel2

Now I move the entries to another file:
items.yaml:

  - name : item1
    label: my custom label1
    channel:
    - zwave:device1:channel1
  - name : item2
    label: my custom label2
    channel:
    - zwave:device1:channel2

and modify the openhab.yaml

- zwave:
  - device 1
    - channel1
    - channel2
- items: !!load_from_file items.yaml

Note that the openhab.yaml is still valid and can still be written to by the parser.
Openhab registers the file changes and loads everything back.
A part of the gui configuration became now manual configuration.
→ Benefit of db & gui but still allows full manual configuration

With a good concept there is no compromise needed!

1 Like