ysc
October 13, 2021, 6:26pm
32
This is by design:
opened 06:52PM - 30 Dec 20 UTC
enhancement
main ui
## The problem
I am not sure whether this is a bug in Main UI or intended beh… aviour:
The Homematic binding creates all thing and channel definitions dynamically. For a dimmer there is a channel-type “LEVEL”. This channel-type contains several entries as you can see here:
The entries are correctly considered e.g. in he equipment display:
But when I open “Add Metadata / State Descriptions” the values for “Max”, “Min”, … are empty:
```
value: ""
config: {}
```
I found the same behaviour with other bindings (e.g. Shelly binding)
## Expected behavior
Pre-occupy the meta data settings with the values retrieved from the binding.
## Steps to reproduce
1. Use a binding that contains a channel of type dimmer with stateDescription values for "minimum", "maximum", "step"
2. Create an item for this channel
3. Open "Add Metadata / State Descriptions"
## Your environment
```yaml
runtimeInfo:
version: 3.1.0
buildString: "Build #2107"
locale: en_DE
systemInfo:
configFolder: /etc/openhab
userdataFolder: /var/lib/openhab
logFolder: /var/log/openhab
javaVersion: 11.0.9.1
javaVendor: Azul Systems, Inc.
javaVendorVersion: Zulu11.43+55-CA
osName: Linux
osVersion: 5.4.0-58-generic
osArchitecture: amd64
availableProcessors: 8
freeMemory: 23140880
totalMemory: 230686720
bindings:
- homematic
- shelly
clientInfo:
device:
ios: false
android: false
androidChrome: false
desktop: true
iphone: false
ipod: false
ipad: false
edge: false
ie: false
firefox: true
macos: false
windows: true
cordova: false
phonegap: false
electron: false
nwjs: false
webView: false
webview: false
standalone: false
os: windows
pixelRatio: 1.5
prefersColorScheme: light
isSecureContext: false
locationbarVisible: true
menubarVisible: true
navigator:
cookieEnabled: true
deviceMemory: N/A
hardwareConcurrency: 16
language: de
languages:
- de
- en-US
- en
onLine: true
platform: Win32
screen:
width: 2560
height: 1440
colorDepth: 24
support:
touch: false
pointerEvents: true
observer: true
passiveListener: true
gestures: false
intersectionObserver: true
themeOptions:
dark: light
filled: true
pageTransitionAnimation: default
bars: filled
homeNavbar: default
homeBackground: default
expandableCardAnimation: default
userAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:84.0) Gecko/20100101
Firefox/84.0
timestamp: 2020-12-30T18:45:56.634Z
```
## Browser console
```txt
```
## Browser network traffic
## Additional information
These state/command options are provided by the channel the item is linked to, so you can’t override them.@rlkoshak that’s causing the formatting issue - you can’t have both state description options and a pattern. In that case the pattern is likely be ignored.command options and leave the state description alone. Then the pattern would be considered for the display state and you’d still have the command options (a menu sheet with Open, Tilted, Closed when you click the widget).
1 Like
