Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update thing-xml.md - Added subheadings to have anchors for linking #1236

Merged
merged 1 commit into from
Jun 16, 2020
Merged

Update thing-xml.md - Added subheadings to have anchors for linking #1236

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions developers/bindings/thing-xml.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,8 @@ The granularity of channel types should be on its semantic level, i.e. very fine
If a Thing measures two temperature values, one for indoor and one for outdoor, this should be modelled as two different channel types.
Overriding labels of a channel type must only be done if the very same functionality is offered multiple times, e.g. having an actuator with 5 relays, which each is a simple "switch", but you want to individually name the channels (1-5).

### State Channel Types

The following XML snippet shows a thing type definition with 2 channels and one referenced channel type:

```xml
Expand Down Expand Up @@ -152,6 +154,8 @@ Especially for complex devices with a lot of channels, only a small set of chann
Whether a channel should be declared as `advanced` depends on the device and can be decided by the binding developer.
If a functionality is rarely used it should be better marked as `advanced`.

### Trigger Channel Types

The following XML snippet shows a trigger channel:

```xml
Expand Down