Fix broken links (#2108)

Some documentation files were moved in #1872 which caused these links to be broken.

Signed-off-by: Wouter Born <github@maindrain.net>
pull/2109/head
Wouter Born 2023-07-30 22:40:46 +02:00 committed by Confectrician
parent 070f012212
commit 2985c83ae2
3 changed files with 7 additions and 7 deletions

View File

@ -123,7 +123,7 @@ The `ThingManager` creates for each Thing a `ThingHandler` instance using a `Thi
Therefore, it tracks all `ThingHandlerFactory`s from the binding. Therefore, it tracks all `ThingHandlerFactory`s from the binding.
The `ThingManager` determines if the `Thing` is initializable or not. The `ThingManager` determines if the `Thing` is initializable or not.
A `Thing` is considered as _initializable_ if all _required_ configuration parameters (cf. property _parameter.required_ in [Configuration Description](config-xml.html)) are available. A `Thing` is considered as _initializable_ if all _required_ configuration parameters (cf. property _parameter.required_ in [Configuration Description](../addons/config-xml.html)) are available.
If so, the method `ThingHandler.initialize()` is called. If so, the method `ThingHandler.initialize()` is called.
Only Things with status (cf. [Thing Status](../../concepts/things.html#thing-status)) _UNKNOWN_, _ONLINE_ or _OFFLINE_ are considered as _initialized_ by the framework and therefore it is the handler's duty to assign one of these states sooner or later. Only Things with status (cf. [Thing Status](../../concepts/things.html#thing-status)) _UNKNOWN_, _ONLINE_ or _OFFLINE_ are considered as _initialized_ by the framework and therefore it is the handler's duty to assign one of these states sooner or later.
@ -454,7 +454,7 @@ The Hue gateway is an IP device with an HTTP API, which communicates over the Zi
In the openHAB model the Hue gateway is represented as a _Bridge_ with connected _Things_, that represent the Hue bulbs. In the openHAB model the Hue gateway is represented as a _Bridge_ with connected _Things_, that represent the Hue bulbs.
_Bridge_ inherits from _Thing_, so that it also has _Channels_ and all other features of a thing, with the addition that it also holds a list of things. _Bridge_ inherits from _Thing_, so that it also has _Channels_ and all other features of a thing, with the addition that it also holds a list of things.
We have a FAQ, discussing [Thing, Bridge and Channel modelling](faq.html#structuring-things-and-thing-types). We have a FAQ, discussing [Thing, Bridge and Channel modelling](../addons/faq.html#structuring-things-and-thing-types).
When implementing a binding with _Bridges_, the logic to communicate with the external system is often shared between the different `ThingHandler` implementations. When implementing a binding with _Bridges_, the logic to communicate with the external system is often shared between the different `ThingHandler` implementations.
In that case it makes sense to implement a handler for the _Bridge_ and delegate the actual command execution from the _ThingHandler_ to the _BridgeHandler_. In that case it makes sense to implement a handler for the _Bridge_ and delegate the actual command execution from the _ThingHandler_ to the _BridgeHandler_.
@ -727,7 +727,7 @@ In the case that a `property` will be used to match the representation property
updateProperty("uniqueId", uniquePropVal); updateProperty("uniqueId", uniquePropVal);
``` ```
Alternatively in the case that a `configuration parameter` will be used to match the auto discovery representation property, the parameter must be declared in either, a) the `thing-types.xml` file, or b) the `config-description` [XML file](config-xml.md). Alternatively in the case that a `configuration parameter` will be used to match the auto discovery representation property, the parameter must be declared in either, a) the `thing-types.xml` file, or b) the `config-description` [XML file](../addons/config-xml.md).
And it must also be declared in the Thing handler's `Configuration` class: And it must also be declared in the Thing handler's `Configuration` class:
```java ```java
@ -1016,4 +1016,4 @@ This is done by implementing the `getServices` method in your bridge handler:
## Frequently asked questions / FAQ ## Frequently asked questions / FAQ
Various binding related questions are answered in our [Binding development FAQ](faq.html). Various add-on related questions are answered in our [Add-on development FAQ](../addons/faq.html).

View File

@ -197,7 +197,7 @@ There exist system-wide trigger channel types that are available by default:
| rawrocker | system.rawrocker | Can trigger `DIR1_PRESSED`, `DIR1_RELEASED`, `DIR2_PRESSED` and `DIR2_RELEASED` | | rawrocker | system.rawrocker | Can trigger `DIR1_PRESSED`, `DIR1_RELEASED`, `DIR2_PRESSED` and `DIR2_RELEASED` |
In the following sections the declaration and semantics of tags, state descriptions and channel categories will be explained in more detail. In the following sections the declaration and semantics of tags, state descriptions and channel categories will be explained in more detail.
For a complete sample of the thing types XML file and a full list of possible configuration options please see the [XML Configuration Guide](config-xml.html). For a complete sample of the thing types XML file and a full list of possible configuration options please see the [XML Configuration Guide](../addons/config-xml.html).
### Default Tags ### Default Tags
@ -522,7 +522,7 @@ A new discovery would then automatically find this Thing again and add it to the
See also [Implementing a Discovery Service](index.md#representation-property) See also [Implementing a Discovery Service](index.md#representation-property)
When comparing representation properties, the auto-ignore service checks for matches between the representation property of the newly discovered Thing, and both the properties and the configuration parameters of existing Things. When comparing representation properties, the auto-ignore service checks for matches between the representation property of the newly discovered Thing, and both the properties and the configuration parameters of existing Things.
If a configuration parameter will be used, then its respective `parameter` shall be declared in the XML `config-description` section or the `config-description` [XML file](config-xml.md): If a configuration parameter will be used, then its respective `parameter` shall be declared in the XML `config-description` section or the `config-description` [XML file](../addons/config-xml.md):
```xml ```xml
<thing-type id="thingTypeId"> <thing-type id="thingTypeId">

View File

@ -83,7 +83,7 @@ slots: ...
``` ```
- a **uid** (its Unique IDentifier) - a **uid** (its Unique IDentifier)
- a **props** structure describing its own properties; props define parameters and parameter groups following a subset of the configuration description schema found in bindings, services and throughout openHAB: see [Configuration Descriptions](/docs/developer/bindings/config-xml.html) - a **props** structure describing its own properties; props define parameters and parameter groups following a subset of the configuration description schema found in bindings, services and throughout openHAB: see [Configuration Descriptions](../developers/addons/config-xml.html)
- a set of **tags** - a set of **tags**
## Widgets: Definition & Usage ## Widgets: Definition & Usage