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] Device Configuration - not working #844

Closed
Masterz69 opened this issue Mar 8, 2021 · 11 comments · Fixed by #853
Closed

[bug] Device Configuration - not working #844

Masterz69 opened this issue Mar 8, 2021 · 11 comments · Fixed by #853
Assignees
Labels
bug Something isn't working

Comments

@Masterz69
Copy link

Masterz69 commented Mar 8, 2021

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.
image

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
image

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:
image

@Masterz69 Masterz69 added the bug Something isn't working label Mar 8, 2021
@robertsLando
Copy link
Member

@Masterz69 That's strange. Could you attach a full silly level log of zwavejs?

@Masterz69
Copy link
Author

zwavejs2mqtt-store.zip

Hope it will help - zwavejs2mqtt.log & 2 latest zwavejs_*.log 's.

@robertsLando
Copy link
Member

@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)

@AlCalzone
Copy link
Member

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.
@Masterz69 please share the device ID or our config browser link and the firmware version.

when he try to set a value the feedback tells another value is set (try to write 0 and updates it to 13)

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.

@AlCalzone
Copy link
Member

/cc @blhoward2

@robertsLando
Copy link
Member

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.

Yep I'm on this right now 👍

@Masterz69
Copy link
Author

Both right now connected devices are identical. Tried to configure node 2.

As far I see in json file: deviceId":"600-4135-512",
"manufacturer":"Shenzhen Neo Electronics Co., Ltd.",
"manufacturerId":600,"productType":512,"productId":4135, ...
"productLabel":"NAS-WR01ZE","productDescription":"Wall Plug Switch",

Purchased it from that Ali seller - there no model name, unfortunately.
Looking on products.z-wavealliance.org - found that one.

As far I see configuration page based on this ^^ product info.

But let see some photo from in package included manual:
20210309_125420
Here parameter 5 is exactly 120 as a default value. At least manual and device say same data.

20210309_125510

"please share the device ID or our config browser link and the firmware version."
^^ not sure what provide all You asked. if no - let me know.

@Masterz69
Copy link
Author

Masterz69 commented Mar 9, 2021

Pls see information about another plug from Hubitat Elevation:
deviceId: 4135
deviceType: 512
manufacturer: 600
inClusters: 0x5E,0x98,0x9F,0x55,0x73,0x86,0x85,0x8E,0x59,0x72,0x5A,0x25,0x32,0x71,0x70,0x6C
zwNodeInfo: D3 9C 00 04 10 01 5E 98 9F 55 73 86 85 5C 8E 59 72 5A 25 32 71 70 6C 68 23
properties: measure-power
firmwareVersion: 2.23
protocolVersion: 6.04
hardwareVersion: 16

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....?

@Masterz69
Copy link
Author

@Masterz69
Copy link
Author

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.

@AlCalzone
Copy link
Member

Duplicate of zwave-js/node-zwave-js#1221

@AlCalzone AlCalzone marked this as a duplicate of zwave-js/node-zwave-js#1221 Mar 9, 2021
robertsLando added a commit that referenced this issue Mar 9, 2021
* fix(ui): show custom values in select too

Fixes #844

* fix: read only values style

* fix: move to scoped styles
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

Successfully merging a pull request may close this issue.

3 participants