zwave-js-bot
commented
1 year ago 👋 Hey @windsurferwill!
It looks like you attached a logfile, but its filename doesn't look like it a driver log that came from Z-Wave JS. Please make sure you upload the correct one.
AlCalzone
Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?
NO, my problem is NOT within Z-Wave JS UI
Checklist
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem was not mentioned there.
Describe the bug
What causes the bug?
What do you observe? Change parameters 7 or 8 in the zwave device config menu. They change but when exiting the UI and coming back in they didn't stick. kpine had me submit diagnostic logs which show the parameter size sent vs expected don't match See https://github.com/zwave-js/node-zwave-js/issues/5271. Using Developer Tools to set the state works.
What did you expect to happen?
Steps to reproduce the behavior:
Device information
Manufacturer: nortek / goControl Model name: PD300EMZ5-1 Node ID in your network: 12
How are you using
node-zwave-js?zwave-js-ui(formerlyzwavejs2mqtt) Docker image (latest)zwave-js-ui(formerlyzwavejs2mqtt) Docker image (dev)zwave-js-ui(formerlyzwavejs2mqtt) Docker manually built (please specify branches)ioBroker.zwave2adapter (please specify version)HomeAssistant zwave_jsintegration (please specify version)pkgnode-red-contrib-zwave-js(please specify version, double click node to find out)Which branches or versions?
version:Driver Version: 11.6.0 Server Version: 1.30.0
node-zwave-jsbranch:zwave-js-uibranch:Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Don't know, this is a new device
If yes, where did it work?
No response
Attach Driver Logfile
zwave_js (1).log