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.

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

[bug] Options for configuration values not handled properly #763

Closed
2 tasks
NYZack opened this issue Feb 27, 2021 · 2 comments
Closed
2 tasks

[bug] Options for configuration values not handled properly #763

NYZack opened this issue Feb 27, 2021 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@NYZack
Copy link

NYZack commented Feb 27, 2021

Before submitting a bug please read: https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/bug_report

Version

Build/Run method

  • [X ] Docker
  • PKG
  • Manually built (git clone - npm install - npm run build )

zwavejs2mqtt version: 1.3.0
zwavejs version: 6.4.0

Describe the bug

When options are listed for configuration parameters in device configuration files on zwavejs and allowManualEntry is true, the options don't show up in the zwavejs2mqtt configuration interface: one can only enter the value manually, and there is no dropdown. On the attached node export (see config parameter 5 [32-112-0-5], for instance, and the attached configuration json file), it doesn't look like the options data actually make it over from zwavejs.

Also, if I have options set for a read-only parameter (and allowManualEntry is set to true) - if the actual value returned isn't one of the options, the value doesn't show up.

Expected behavior

If options are listed in a configuration file and allowManualEntry is set to true, there should be a dropdown with the options, or the user should be able to enter the value manually. On a read-only parameter, if the returned value matches one of the options, the option should appear; otherwise, the raw value should appear.

image
node_32.json.txt
zse29.json.txt

@NYZack NYZack added the bug Something isn't working label Feb 27, 2021
@robertsLando
Copy link
Member

@NYZack did you try to re-interview your device?

@NYZack
Copy link
Author

NYZack commented Mar 1, 2021

Yes. This is the issue in #779 so closing this one.

@NYZack NYZack closed this as completed Mar 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants