-
-
Notifications
You must be signed in to change notification settings - Fork 202
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] Device Configuration - not working #844
Comments
@Masterz69 That's strange. Could you attach a full |
Hope it will help - zwavejs2mqtt.log & 2 latest zwavejs_*.log 's. |
@AlCalzone Seems like the config options values are out of the range of the allowed options, the strange thing is that the allowManualEntry is not true and also when he try to set a value the feedback tells another value is set (try to write 0 and updates it to 13) |
I can't make out which device that is exactly, but our config file seems to be wrong. Config parameter #5 returns a value of 120 but our config thinks this stands for Enabled/Disabled.
No, the 0 is being set but the device does not accept it and returns 13 instead That being said - zwavejs2mqtt needs to be able to display values that are out of range. It looks like the values are missing when they are not. This will not be the last time that we have an incorrect config file. |
/cc @blhoward2 |
Yep I'm on this right now 👍 |
Both right now connected devices are identical. Tried to configure node 2. As far I see in json file: deviceId":"600-4135-512", Purchased it from that Ali seller - there no model name, unfortunately. As far I see configuration page based on this ^^ product info. But let see some photo from in package included manual: "please share the device ID or our config browser link and the firmware version." |
Pls see information about another plug from Hubitat Elevation: deviceId, deviceType, manufacturer - same one. Probably here is a plug firmware version, not sure. Just guess, may be with another firmware/hardware version changed also parameters etc....? |
Found previously created issue "Add missing Neo Coolcam device (INFO ZWAVE: Node 6 ready: Unknown manufacturer 600 - Unknown product 4135 (512))" & "Add missing Neo Coolcam devices". In @ookonbekend comment I see link to |
Looks like I found config link; https://devices.zwave-js.io/?jumpTo=0x0258:0x0200:0x1027:null Probably there must be a new config for V2. Kindly asking to add it, it would be great ! Thank You in advance. |
Duplicate of zwave-js/node-zwave-js#1221 |
* fix(ui): show custom values in select too Fixes #844 * fix: read only values style * fix: move to scoped styles
Issue about changing device configuration from ZWaveJS Control Panel - IMHO there is nothing about HA.
Version info: HA Core 5.12 on RP4 4G + Aeotec Z-Wave Stick Gen5.
ZWave device: Shenzhen Neo Electronics Co., Ltd. NAS-WR01ZE
See attached JSON ZiP:
node_2.zip
Basic functions, like switching and measurements looks working.
Tried to disable button on device, by using
Whch is decribed in manual as following:
Function: Enable Button On/Off
Parameter Number: 10.
Parameter Size: 1 Byte
Available Settings: 0, 1.
Default Setting: 1
Immediately after selecting "Disable Button" and pressing arrow in log appears:
2021-03-08 22:59:29.169 DEBUG SOCKET: Event ZWAVE_API emitted to toZSjkq3V9Aj4DM3AAAL
2021-03-08 22:59:29.173 INFO ZWAVE: Calling api writeValue with args: [ { nodeId: 2, commandClass: 112, property: 10 }, 0, [length]: 2 ]
2021-03-08 22:59:29.176 INFO ZWAVE: Writing 0 to 2-112-0-10
2021-03-08 22:59:29.231 INFO ZWAVE: Success zwave api call writeValue { success: true, message: 'Success zwave api call', result: undefined }
2021-03-08 22:59:30.296 INFO ZWAVE: Node 2: value updated: 112-0-10 0 => 13
But device button still operable, configuration not changed, looks like.
In same way tried to change "[2-112-0-7] Remember Relay ON/OFF status after power failure." or "[2-112-0-2] Meter Report Interval" - nothing works..
Not sure, but looks like not any value of configuration item actually are retrieved from device, see only fake numbers -not default values, as must be on device with factory settings:
The text was updated successfully, but these errors were encountered: