Zwave JS UI can't set parameter

Configuration Z-Wave
1

I have an HS-FLS100+ motion sensor that has a parameter 2 that allows for the switch in the motion sensor to be controlled only by zwave instead of both zwave and the PIR in the sensor. I’ve been trying to set the parameter via the Zwave JS UI, but it always reverts back to the original number. I’ve re-interviewed the device, it seem perfectly operational, except i cannot set that parameter for the life of me. any ideas what to try next? This is what i see in the UI log:

2022-12-31 12:15:43.766 INFO Z-WAVE: Calling api writeValue with args: [
{ nodeId: 95, commandClass: 112, endpoint: 0, property: 2 },
0,
{},
[length]: 3
]
2022-12-31 12:15:43.768 INFO Z-WAVE: Writing 0 to 95-112-0-2
2022-12-31 12:15:44.459 INFO Z-WAVE: Success zwave api call writeValue true
2022-12-31 12:15:46.360 INFO Z-WAVE: Node 95: value updated: 112-0-2 50 => 50
2

Usually if it reverts the parameter doesn’t exist. You sure it exist? Is it software version (od device) dependent?

3

Do you have the HS-FLS100+, or the HS-FLS100-G2? The parameters are different between the two.

4

i have the original HS-FLS-100+.

5

good question, i don’t know if it exists. i’ve been searching everywhere to get any info on the device, but can’t find anything other than the doc from Homeseer and the Z Wave JS Config database both of which show the parameter as something that is supposed to be there. is there a way to test if it is there?

6

i enabled logging and this is what i see when i try to set the parameter. doesn’t give me much, just that the API call failed.

2023-01-01T15:38:42.919Z SERIAL » 0x011600a9015f0a6c01ab06700402020000250000000071f4                  (24 bytes)
2023-01-01T15:38:42.920Z DRIVER » [Node 095] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      113
                                  └─[SupervisionCCGet]
                                    │ session id:      43
                                    │ request updates: true
                                    └─[ConfigurationCCSet]
                                        parameter #:      2
                                        reset to default: false
                                        value size:       2
                                        value format:     UnsignedInteger
                                        value:            0
2023-01-01T15:38:42.927Z SERIAL « [ACK]                                                                   (0x06)
2023-01-01T15:38:42.928Z SERIAL « 0x010401a90152                                                       (6 bytes)
2023-01-01T15:38:42.928Z SERIAL » [ACK]                                                                   (0x06)
2023-01-01T15:38:42.928Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2023-01-01T15:38:43.550Z SERIAL « 0x011d00a97100003d01ab7f7f7f7f02010318000000010100007f7f7f7f7fca    (31 bytes)
2023-01-01T15:38:43.551Z SERIAL » [ACK]                                                                   (0x06)
2023-01-01T15:38:43.551Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            113
                                    transmit status:        OK, took 610 ms
                                    repeater node IDs:      24
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 9.6 kbit/s
                                    ACK RSSI:               -85 dBm
                                    ACK RSSI on repeaters:  N/A
                                    ACK channel no.:        2
                                    TX channel no.:         1
2023-01-01T15:38:43.720Z SERIAL « 0x010e00a800015f056c022b020000abee                                  (16 bytes)
2023-01-01T15:38:43.721Z SERIAL » [ACK]                                                                   (0x06)
2023-01-01T15:38:43.722Z DRIVER « [Node 095] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -85 dBm
                                  └─[SupervisionCCReport]
                                      session id:          43
                                      more updates follow: false
                                      status:              Fail
                                      duration:            0s
2023-01-01T15:38:43.726Z SERIAL » 0x010e00a9015f028611250000000072c4                                  (16 bytes)
2023-01-01T15:38:43.726Z DRIVER » [Node 095] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      114
                                  └─[VersionCCGet]
2023-01-01T15:38:43.727Z CNTRLR   [Node 095] [setValue] result of SET_VALUE API call for ConfigurationCCAPI: (Su
                                  pervisionResult)
                                    status:   Fail
2023-01-01T15:38:43.727Z CNTRLR   [Node 095] [setValue] not updating value
2023-01-01T15:38:43.733Z SERIAL « [ACK]                                                                   (0x06)
2023-01-01T15:38:43.733Z SERIAL « 0x010401a90152                                                       (6 bytes)
2023-01-01T15:38:43.734Z SERIAL » [ACK]                                                                   (0x06)
2023-01-01T15:38:43.734Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2023-01-01T15:38:43.982Z SERIAL « 0x011d00a97200001801ac7f7f7f7f02010318000000010100007f7f7f7f7feb    (31 bytes)
2023-01-01T15:38:43.983Z SERIAL » [ACK]                                                                   (0x06)
7

Does setting any other config parameter work, or is number 2 the only one?

8

It does it for all the parameters on that node. i spot checked some other devices and i can set parameters without issue on them.

9

Sounds like a device issue then? Perhaps you should submit a support request to HomeSeer?

You could try including the device insecurely, instead of with S2, and see if that makes any difference at all.

Maybe the device doesn’t support Supervision with Configuration CC, for some reason (another HomeSeer device has problems with Supervision, as do other devices), even though it reports support? Usually that would prevent the device from working entirely though. Using a custom device config file that disables Supervision could verify if that’s the case.

1 Like
10

thanks, i opened a ticket with them and will try some of your suggestions in the meantime. I will also create another topic to see if anyone has the same device and can set parameters

11

Similar issue with a different device: Zooz Outdoor Motion Sensor ZSE29 - SupervisionCCReport fails - cannot change device configuration values · Issue #5157 · zwave-js/node-zwave-js · GitHub

1 Like
12

thank you! i hate to ask such a noob kind of question, but i read the issue and all related issues. i have modified the file for the device, but… i have no idea how to get it into the zwave JS container. the file management of zwave JS ui only has a download button and as far as i can tell, since i am running HASOS, all the other containers are kind of hidden.

13

You can create new files and directories in the Store UI. When creating a new file, copy and paste the text into the empty view and save.

14

strange, i can create the directory and the file, but it does not let me paste anything in the view. i can modify existing files, so i know the editor works, but it does not let me paste anything on a new file. anyhow, i will keep messing with it till i figure it out. thank you for all the help!

15

It’s working over here. Example:

file

1 Like
16

finally got it to work. thanks!