ZEN32 Config Browser Missing Parameter 27 #7453
Unanswered
karwosts
asked this question in
Request Support / Investigate Issue
Replies: 1 comment
-
👋 Hey @karwosts! Thanks for opening an issue! It doesn't look like you provided a logfile though. While not strictly necessary for every issue, having a driver log on loglevel debug is required to diagnose most issues. Please consider uploading a logfile that captures your problem. As a reminder, here's how to create one: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Checklist
I have read and followed the above instructions
I have checked the troubleshooting section and my problem is not described there.
I have read the changelog and my problem was not mentioned there or the fix did not work.
Describe the issue
What is happening?
Browsing https://devices.zwave-js.io/?jumpTo=0x027a:0x7000:0xa008:0.0#, I don't see config parameter 27 listed for the Zooz Zen32 scene controller.
This option is mentioned on their advanced options documentation page: https://www.support.getzooz.com/kb/article/608-zen32-scene-controller-advanced-settings/, and there haven't been any new firmware releases lately.
Is this just missing from the configuration file?
What did you expect to happen instead?
Parameter 27 listed at https://devices.zwave-js.io/?jumpTo=0x027a:0x7000:0xa008:0.0# (and ultimately to be able to control it in home assistant ZwaveJS)
Steps to reproduce the behavior:
Anything else we should know?
Software versions
Driver (node-zwave-js): ...
Z-Wave JS UI: ...
Home Assistant Z-Wave Integration: ...
Home Assistant Z-Wave JS Addon: ...
ioBroker.zwave2 Adapter: ...
If you are using something non-standard, tell us here: ...
Z-Wave Controller (Stick/Dongle/...)
discussions
Device information
Manufacturer: ...
Model name: ...
Node ID: ...
Checklist
I made sure to provide a driver log on level debug.
The log includes a re-interview of the problematic device (if applicable).
The log includes the problematic interaction with the device (if applicable).
I provided the node ID of the problematic device (if applicable).
Upload Logfile
No logfile as its just an issue with the config browser.
Beta Was this translation helpful? Give feedback.
All reactions