openhab · jlaur · Sep 28, 2024 · Sep 15, 2024 · Sep 15, 2024 · Sep 17, 2024
@@ -23,7 +23,7 @@ For more information on the available APIs in scripts see the [JSR223 Scripting]
 
 ## Code reuse
 
-One can place *.groovy files with Groovy classes under `automation/groovy` configuration directory.  
+One can place *.groovy files with Groovy classes under `automation/groovy` configuration directory.
 Those classes can be imported in JSR-223 scripts or the UI rules action with the usual Groovy `import` statement.
 
 To apply shared code changes, one has to restart the `openHAB Core :: Bundles :: Automation` bundle on the Console or an openHAB instance altogether.

@@ -670,7 +670,7 @@ items.build do
 
   # dimension Temperature inferred
   number_item OutdoorTemp, format: "%.1f %unit%", unit: "°F"
-    
+
   # unit lx, dimension Illuminance, format "%s %unit%" inferred
   number_item OutdoorBrightness, state: 10_000 | "lx"
 end

@@ -55,7 +55,7 @@ The thing **aha Waste Collection Schedule** provides four channels for the upcom
 wasteCollection.things
 
 ```java
-Thing ahawastecollection:collectionSchedule:wasteCollectionSchedule "aha Abfuhrkalender" [ commune="Isernhagen", street="67269@Rosmarinweg+/+Kirchhorst@Kirchhorst", houseNumber="10", houseNumberAddon="", collectionPlace="67269-0010+" ] 
+Thing ahawastecollection:collectionSchedule:wasteCollectionSchedule "aha Abfuhrkalender" [ commune="Isernhagen", street="67269@Rosmarinweg+/+Kirchhorst@Kirchhorst", houseNumber="10", houseNumberAddon="", collectionPlace="67269-0010+" ]
 ```
 
 wasteCollection.items

@@ -15,7 +15,7 @@ This binding supports two thing types:
 
 ## Discovery
 
-All relevant thing types should be added automatically to the inbox through the mDNS discovery process.  
+All relevant thing types should be added automatically to the inbox through the mDNS discovery process.
 
 In the case of the ShieldTV or PhilipsTV, openHAB will likely create an inbox entry for both a GoogleTV and a ShieldTV or PhilipsTV device.
 Only the ShieldTV or PhilipsTV device should be configured, the GoogleTV can be ignored.
@@ -24,7 +24,7 @@ This could cause undesired effects.
 
 ## Binding Configuration
 
-This binding does not require any special configuration files.  
+This binding does not require any special configuration files.
 
 This binding does require a PIN login process (documented below) upon first connection.
 

@@ -99,6 +99,7 @@ R=RFID
 ```
 
 transform/ekey_names.map [NO spaces allowed]
+
 ```text
 -1=Unspecified
 1=JohnDoe

@@ -9,10 +9,10 @@ The binding will search your Jollyday event definition files in the sub folder `
 
 The binding handles the following Things:
 
-* default holiday data (`holiday`)
-* custom holiday file (`custom`)
-* daysets (`dayset`)
-* weekend (`weekend`)
+- default holiday data (`holiday`)
+- custom holiday file (`custom`)
+- daysets (`dayset`)
+- weekend (`weekend`)
 
 ## Discovery
 
@@ -24,7 +24,6 @@ There is no configuration at binding level.
 
 ## Thing Configuration
 
-
 ### `custom` Thing Configuration
 
 | Name            | Type    | Description                                       | Default | Required | Advanced |
@@ -39,7 +38,6 @@ The file has to use the syntax described here : https://www.openhab.org/docs/con
 |-----------------|---------|---------------------------|---------|----------|----------|
 | name            | text    | Name of the dayset used   | N/A     | yes      | no       |
 
-
 ## Channels
 
 ### `weekend` Channels
@@ -80,15 +78,15 @@ The file has to use the syntax described here : https://www.openhab.org/docs/con
 
 ## Full Example
 
-### Thing Configuration
+### Thing Example
 
 ```java
 Thing ephemeris:holiday:local "Holidays"
 Thing ephemeris:weekend:local "Week-end"
 Thing ephemeris:custom:events "Event" [fileName="events.xml"]
 ```
 
-### Item Configuration
+### Item Example
 
 ```java
 String         ToD_Event_Current          "Event Today"       <calendar>    (gEvents)                           {channel="ephemeris:custom:events:title-today"}

@@ -106,11 +106,11 @@ Please note that you have to replace _\<N\>_ with your loadpoint id/number.
 
 Those channels exist:
 
-* 1 per configured loadpoint with `chargerFeatureHeating = false`:
-  * These channels point to the heating device that is currently active/connected at/to the loadpoint
-  * Please note that you have to replace _\<N\>_ with your loadpoint id/number
-* 1 per configured vehicle:
-  * Please note that you have to replace _\<ID\>_ with your vehicle id/name
+- 1 per configured loadpoint with `chargerFeatureHeating = false`:
+  - These channels point to the heating device that is currently active/connected at/to the loadpoint
+  - Please note that you have to replace _\<N\>_ with your loadpoint id/number
+- 1 per configured vehicle:
+  - Please note that you have to replace _\<ID\>_ with your vehicle id/name
 
 | Channel                                            | Type                 | Read/Write | Description                                                              |
 |----------------------------------------------------|----------------------|------------|--------------------------------------------------------------------------|
@@ -126,11 +126,11 @@ Those channels exist:
 
 Those channels exist:
 
-* 1 per configured loadpoint with `chargerFeatureHeating = true`:
-  * These channels point to the heating device that is currently active/connected at/to the loadpoint
-  * Please note that you have to replace _\<N\>_ with your loadpoint id/number
-* 1 per configured heating device:
-  * Please note that you have to replace _\<ID\>_ with your heating device id/name
+- 1 per configured loadpoint with `chargerFeatureHeating = true`:
+  - These channels point to the heating device that is currently active/connected at/to the loadpoint
+  - Please note that you have to replace _\<N\>_ with your loadpoint id/number
+- 1 per configured heating device:
+  - Please note that you have to replace _\<ID\>_ with your heating device id/name
 
 | Channel                                                 | Type               | Read/Write | Description                                                           |
 |---------------------------------------------------------|--------------------|------------|-----------------------------------------------------------------------|

@@ -159,6 +159,7 @@ You can retrieve the actions as follows:
 ```java
 val froniusInverterActions = getActions("fronius", "fronius:powerinverter:mybridge:myinverter")
 ```
+
 :::
 
 ::: tab JS

diff --git a/bundles/org.openhab.binding.homematic/README.md b/bundles/org.openhab.binding.homematic/README.md
@@ -212,7 +212,7 @@ homematic:bridge:NAME
 - **bridge** the type, fixed
 - **name** the name of the bridge
 
-### Example
+### Bridge Configuration Example
 
 #### Minimum configuration
 
@@ -448,7 +448,7 @@ Adds multiple virtual datapoints to the HM-Dis-WM55 and HM-Dis-EP-WM55 devices t
 
 **Note:** The HM-Dis-EP-WM55 has only a black and white display and therefore does not support datapoints for colored lines. In addition, only lines 1-3 can be set.
 
-#### Example
+#### Button Example
 
 Display text at line 1,3 and 5 when the bottom button on the display is pressed
 
@@ -734,6 +734,7 @@ The problem can be solved by increasing the `bufferSize` value in the bridge con
 
 openHAB and the CCU are using different values for the same state of a rollershutter.
 Examples: HmIP-BROLL, HmIP-FROLL, HmIP-BBL, HmIP-FBL and HmIP-DRBLI4
+
 |         | Open | Closed |
 | ------- | ---- | ------ |
 | openHAB | 0%   | 100%   |

@@ -787,9 +787,9 @@ If you want to dive deeper see [Troubleshooting](#troubleshooting) `feature-capa
 
 In order to be able to analyze problems 3 advanced channels are placed in the vehicle group.
 
-* `feature-capabilities` - showing which feature your vehicle is equipped with
-* `command-capabilities` - showing which commands can be sent to your vehicle
-* `proto-update` - latest update of your vehicle data
+- `feature-capabilities` - showing which feature your vehicle is equipped with
+- `command-capabilities` - showing which commands can be sent to your vehicle
+- `proto-update` - latest update of your vehicle data
 
 In case you find problems regarding this binding add items to these 3 channels.
 The items are reporting Strings in JSON format.
-Original file line number
+Diff line change
@@ Expand Up / @@ -99,6 +99,7 @@ R=RFID @@
     ```
     transform/ekey_names.map [NO spaces allowed]
     ```text
     -1=Unspecified
 =JohnDoe
@@ Expand Down @@