AdrianLucas
September 22, 2021, 8:10pm
1
I am running openHABian v1.6.5 on a RPi 3 with an Aeotec Z-Stick Gen5 and I am having problems setting some configuration parameters on a Fibaro Smart Implant FGBS-222. I have searched for posts about this device but none found concern my particular problem.
I want to set parameters 40 and 41 to allow all possible scenes to be sent. The description says “This is a BIT flag allowing all options to be set” but in the Thing’s Configuration Parameters section, the 4 options are represented by radio buttons of which only one can be pressed at a time. From my understanding, I think these should be check boxes (not radio buttons) so any number can be selected.
I am happy to contribute by attempting to fix this but I would need some pointers to where the code for generating this part of the UI is located. Alternatively, perhaps someone familiar with the code could fix it very quickly.
I am a newcomer to openHab and am enjoying learning about it and using it to control several Z-Wave devices and Hue bulbs. I wasn’t sure if this post should be in the UI section or maybe even Development so I’m sorry if it’s in the wrong place.
robmac
September 22, 2021, 9:57pm
2
It does look like an issue with the UI though it might be possible to fix in the device database.
As a workaround have you tried setting the values on the code page tab?
Probably will not show on the normal UI but should send to the device as I do not think the binding will have an issue.
AdrianLucas
September 23, 2021, 12:40pm
3
Thank you for suggesting that workaround. I had completely forgotten the Code Tab. Great feature! I will try it out and also file an issue (I don’t think it has been filed before). Thanks again for your help.
AdrianLucas
September 24, 2021, 10:55am
4
The workaround works fine and I have filed an issue:
opened 10:50AM - 24 Sep 21 UTC
bug
main ui
<!--
Please DO NOT ERASE this template, but fill in the details as requested. T… his will ensure your issue is properly filed and will be considered. Otherwise, we may reserve the right to close it without further action.
-->
## The problem
<!--
Describe the issue you're having. In most cases it is appreciated to share screenshots or
even animated GIFs of your issue.
To make screenshots:
* On Windows: use Win+Shift+S
* On macOS: use Cmd+Shift+4
To make animated GIFs we recommend:
* On Windows: ShareX - https://getsharex.com/
* On macOS: Giphy Capture - https://giphy.com/apps/giphycapture
* On GNU/Linux: Peek - https://github.com/phw/peek
-->
(I'm not sure if this is a general UI problem or one specific to a binding and Thing so apologies if it's in the wrong place)
<img width="616" alt="Screenshot 2021-09-24 at 11 25 21" src="https://user-images.githubusercontent.com/91279390/134660650-af32c7a1-ac0f-40ed-8a3a-954f73e000c5.png">
In the Thing’s Configuration Parameters section, the description says “This is a BIT flag allowing all options to be set” but the 4 options are represented by radio buttons of which only one can be selected at a time.
## Expected behavior
<!--
Describe what you expected to happen or how it should look/behave.
-->
The options should be check boxes so more than one can be selected.
## Steps to reproduce
<!--
Provide accurate steps to reproduce the issue, including pastes of widget/page code if necessary.
-->
1. Include a Fibaro Smart Implant (FGBS-222) with the Z-Wave binding
2. Try to set parameters 40 or 41 with more than one selection.
## Your environment
<!--
As an admin, in the main UI, choose *Help & About* on the left sidebar, expand *Technical information* and click on *View details*, then click *Copy* and paste the results here. You may omit information that is not pertinent to this issue if you feel it's divulging information you'd like not to share.
-->
```yaml
runtimeInfo:
version: 3.1.0
buildString: Release Build
locale: en-GB
systemInfo:
configFolder: /etc/openhab
userdataFolder: /var/lib/openhab
logFolder: /var/log/openhab
javaVersion: 11.0.12
javaVendor: Azul Systems, Inc.
javaVendorVersion: Zulu11.50+19-CA
osName: Linux
osVersion: 5.10.60-v7+
osArchitecture: arm
availableProcessors: 4
freeMemory: 72733352
totalMemory: 194772992
bindings:
- hue
- network
- zwave
clientInfo:
device:
ios: false
android: false
androidChrome: false
desktop: true
iphone: false
ipod: false
ipad: false
edge: false
ie: false
firefox: false
macos: true
windows: false
cordova: false
phonegap: false
electron: false
nwjs: false
webView: false
webview: false
standalone: false
os: macos
pixelRatio: 2
prefersColorScheme: dark
isSecureContext: false
locationbarVisible: true
menubarVisible: true
navigator:
cookieEnabled: true
deviceMemory: N/A
hardwareConcurrency: N/A
language: en-gb
languages:
- en-gb
onLine: true
platform: MacIntel
screen:
width: 2240
height: 1260
colorDepth: 24
support:
touch: false
pointerEvents: true
observer: true
passiveListener: true
gestures: false
intersectionObserver: true
themeOptions:
dark: dark
filled: true
pageTransitionAnimation: default
bars: light
homeNavbar: default
homeBackground: default
expandableCardAnimation: default
userAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15
(KHTML, like Gecko) Version/14.1.2 Safari/605.1.15
timestamp: 2021-09-24T10:42:13.394Z
```
## Browser console
<!--
Open the developer tools in your browser, go to the Console tab and paste errors and other messages that might be relevant to this issue.
You may also paste a screenshot if you prefer.
-->
```txt
```
## Browser network traffic
<!--
Open the developer tools in your browser, go to the Network tab and paste
screenshots of the network traffic and the details of individual requests that failed.
-->
## Additional information
<!--
Provide any information not pertinent to the above sections that you'd still like to share.
-->
There is a workaround by setting the parameters in the "Code" tab
