csand
July 28, 2021, 8:46pm
21
There is already an active issue since February :
opened 09:02AM - 26 Feb 21 UTC
bug
main ui
## The problem
Color items for newly discovered things (Extended Color Lights… ) don't get any color widget shown in all parts of the Main UI. Eg.:
I already opened an issue in the openhab-addon repository related to the Zigbee binding (see: https://github.com/openhab/openhab-addons/issues/10223)
Although, @cdjackson as the maintainer of the Zigbee binding suspects the cause in the webui. Therefore I raise this issue here too to start the discussion if it is to be solved in the binding _or_ the webui.
The following seem to support Chris's point of view:
```
openhab> send ZIGRGBWStripBuero_Color ON
Command has been sent successfully.
openhab> send ZIGRGBWStripBuero_Color 120,75,41
Command has been sent successfully.
openhab>
```
Openhab accepts the ON/OFF as well as the color commands sent to the item. And the real device indeed updates the color.
## Expected behavior
I'd expect a color widget show in standalone or lists allowing to control the color, e.g.:
## Steps to reproduce
- discover extended color light by the Zigbee binding (maybe other binding are affected as well)
- bind the color channel of the discovered light to a color item by "create equipment from thing" from within the model page
-
## Your environment
```yaml
runtimeInfo:
version: 3.1.0.M1
buildString: Milestone Build
locale: de_DE
systemInfo:
configFolder: /etc/openhab
userdataFolder: /var/lib/openhab
logFolder: /var/log/openhab
javaVersion: 11.0.10
javaVendor: Azul Systems, Inc.
javaVendorVersion: Zulu11.45+27-CA
osName: Linux
osVersion: 5.10.12-sunxi
osArchitecture: arm
availableProcessors: 4
freeMemory: 105461296
totalMemory: 323035136
bindings:
- astro
- bluetooth
- harmonyhub
- hue
- knx
- kodi
- miio
- mqtt
- network
- networkupstools
- rfxcom
- shelly
- sonos
- systeminfo
- zigbee
- zwave
clientInfo:
device:
ios: false
android: false
androidChrome: false
desktop: true
iphone: false
ipod: false
ipad: false
edge: false
ie: false
firefox: false
macos: false
windows: true
cordova: false
phonegap: false
electron: false
nwjs: false
webView: false
webview: false
standalone: false
os: windows
pixelRatio: 1.25
prefersColorScheme: dark
isSecureContext: false
locationbarVisible: true
menubarVisible: true
navigator:
cookieEnabled: true
deviceMemory: N/A
hardwareConcurrency: 8
language: de-DE
languages:
- de-DE
- de
- en-US
- en
onLine: true
platform: Win32
screen:
width: 3072
height: 1728
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) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/88.0.4324.182 Safari/537.36
timestamp: 2021-02-26T08:59:41.316Z
```
I just linked this conversation
1 Like
ysc
August 1, 2021, 12:07pm
22
chris:
Sorry to repeat, but in my mind, the major issue here is that the UI should allow a command to be sent even if the device is in UNDEF state. It seems to allow this for switch and dimmer types - just not colour types (@ysc what do you think?).
Yes it would appear so - more accurately, the color control isn’t shown at all when the state is UNDEF. I think I already saw this somewhere, either here or GitHub.
4 Likes
