Skip to content

Commit

Permalink
Icons shall not be changed in rules
Browse files Browse the repository at this point in the history
• insert the conclusion from openhab/openhab-core#3958
  • Loading branch information
dilyanpalauzov committed Feb 24, 2024
1 parent 67a019a commit f9be963
Show file tree
Hide file tree
Showing 4 changed files with 6 additions and 138 deletions.
1 change: 1 addition & 0 deletions .vuepress/docs-sidebar.js
Original file line number Diff line number Diff line change
Expand Up @@ -68,6 +68,7 @@ module.exports = [
'concepts/discovery',
'concepts/audio',
'concepts/units-of-measurement',
'concepts/profiles',
'concepts/rules',
]
},
Expand Down
131 changes: 0 additions & 131 deletions concepts/categories.md

This file was deleted.

2 changes: 2 additions & 0 deletions configuration/items.md
Original file line number Diff line number Diff line change
Expand Up @@ -297,6 +297,8 @@ In the example below, the "switch" icon has been selected:
Switch Livingroom_Light "Livingroom Ceiling Light" <switch>
```

Please note that icons (also know as categories) are not meant to be changed dynamically via rules.

#### Icons provided with openHAB

openHAB provides a set of [classic icons](/docs/configuration/iconsets/classic/) by default.
Expand Down
10 changes: 3 additions & 7 deletions developers/bindings/thing-xml.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ In that way, a generic thing type could be listed for users and a corresponding

### Thing Categories

A description about thing categories as well as an overview about which categories exist can be found in our [categories overview](../../concepts/categories.html).
Thing categories are used to set an icon for that Thing. The available categories correspond with the available icons of the classic icon set, however categories are written in Java class-naming style, e.g. FrontDoor instead of lowercase frontdoor.

## Channels

Expand Down Expand Up @@ -145,9 +145,6 @@ There exist system-wide channel types that are available by default and which sh
| electric-power | system.electric-power | Number:Power | Energy | Measurement, Power | Electric power |
| electric-voltage | system.electric-voltage | Number:ElectricPotential | Energy | Measurement, Voltage | Electric voltage |
| electrical-energy | system.electric-energy | Number:Energy | Energy | Measurement, Energy | Electrical energy |

For further information about categories see the [categories page](../../concepts/categories.html).

The `advanced` property indicates whether this channel is a basic or a more specific functionality of the thing.
If `advanced` is set to `true` a user interface may hide this channel by default.
The default value is `false` and thus will be taken if the `advanced` attribute is not specified.
Expand Down Expand Up @@ -411,7 +408,7 @@ public class ExampleHandlerFactory extends BaseThingHandlerFactory {

### Channel Categories

A description about channel categories as well as an overview about which categories exist can be found in out [categories overview](../../concepts/categories.html).
Channel categories are used to set an icon for that Channel. The available categories correspond with the available icons of the classic icon set, however categories are written in Java class-naming style, e.g. FrontDoor instead of lowercase frontdoor.

### Channel Groups

Expand All @@ -434,7 +431,7 @@ Inside the thing types XML file channel groups can be defined like this:
```

The channel group type is defined on the same level as the thing types and channel types.
The group type must have a label, an optional description, and an optional [category](../../concepts/categories.html).
The group type must have a label, an optional description, and an optional category (icon).
Moreover the list of contained channels must be specified:

```xml
Expand All @@ -450,7 +447,6 @@ Moreover the list of contained channels must be specified:

When a thing will be created for a thing type with channel groups, the channel UID will contain the group ID in the last segment divided by a hash (#).
If an Item should be linked to a channel within a group, the channel UID would be `binding:multiChannelSwitchActor:myDevice:switchActor1#switch` for the XML example before.
Details about the category can be found in our [categories overview](../../concepts/categories.html).

## Properties

Expand Down

0 comments on commit f9be963

Please sign in to comment.