feat(config): add config file for Nice IBT4 BusT4

[zwave-js-bot]

fixes: #2518

TODO:

• Change PR title to be more specific

[zwave-js-assistant]

🚧 It seems like this PR has lint errors 🚧

I should be able to fix them for you. If you want me to, just comment
@zwave-js-bot fix lint

[AlCalzone]

These alarm configurations need to be partial parameters

[cdnninja]

@AlCalzone I may need a hand with this one. Maybe just some pointers would be great on partials. I have started here focused around slot one since they are a clone. https://github.com/cdnninja/node-zwave-js/blob/master/packages/config/config/devices/0x0441/ibt4zwave.json

1. I think my masks are wrong considering values could be up to 255? Otherwise could you check if my partial parameter approach is correct.
2. Partials 1,2 and 3 state it follows zwave spec. I have found this spec for Notification Type but not for Notification Status or Event/State Parameters. I have used the few examples in the manual for this as a start. If you have anything to point me to let me know.

[AlCalzone]

As you suspected, your bitmasks are wrong.

This parameter determines to which alarm frames and how the device should react. the parameters consist of 4 bytes, three most significant bytes are set according to the official Z-Wave protocol specification.

Looking at the manual

[MSB] – Notification Type
– Notification Status
– Event/State Parameters
[LSB] – action: 0x00 – no action, 0x01 – open, 0x02 – close

the high byte (3) is the Notification type, byte (2) the status and (1) the notification event. Byte 0 is the "action" of the device itself

In the documentation for partial params, we have a bitmask calculator to help you figure out the bitmask. Here's what it spits out for the notification type byte:

I have found this spec for Notification Type but not for Notification Status or Event/State Parameters

Notification status has possible values 0 and 255. Since 255 means "Unsolicited transmissions are enabled for the specified Notification Type", I'm not even sure if allowing 0 makes sense.
The Event/State Parameters (we should call that "Notification Event") depend on the selected notification type, so we won't be able to model that in the config files. Just make that a free entry between 0-254.

[AlCalzone]

Actually, reading the manual confuses me more. They call the bytes Notification Type, Notification Status, and Event/State Parameters, but the explanations next to the values treat Notification Status as if it were the Notification Event...
The example in the submitted file does the same:

Example: Event: Home Security (0x07) Status: Motion Detected (0x08) Parameter: None (0x00) Action: Open (0x01) = 0x07080001 which is 117964801 decimal to be entered in the gateway.

So maybe byte 2 is actually the notification event (0-255) and byte 1 a single-byte event parameter (0-255).

[yuvalmesika]

Actually, reading the manual confuses me more. They call the bytes Notification Type, Notification Status, and Event/State Parameters, but the explanations next to the values treat Notification Status as if it were the Notification Event...
The example in the submitted file does the same:

Example: Event: Home Security (0x07) Status: Motion Detected (0x08) Parameter: None (0x00) Action: Open (0x01) = 0x07080001 which is 117964801 decimal to be entered in the gateway.

So maybe byte 2 is actually the notification event (0-255) and byte 1 a single-byte event parameter (0-255).

@AlCalzone @cdnninja Can I help in some way?
currently when the gate is closed the target value is 0,
when it`s open the value is 99
There is another mode to the gate (when operating from the remote control and not from the ibt4zwave device) which is partially open (the device shows a value of 99, but I not sure why, when I used openZwave it was showing 255 or 254 I think).

If you want me to test something let me know.
Thanks for your work.
Yuval

[AlCalzone]

Sorry, but that info has nothing to do with the configuration parameters that influence which notification events are sent.

[cdnninja]

@AlCalzone I have updated with your feedback. I left 0 as available for notification status as the manual states 0 is the default of disabled for a few of the slots. If the first slot looks good I will clone this to the others reflecting defaults and such. I think we start with following the documentation and see if it works as intended.

[cdnninja]

#2576 2576

[zwave-js-assistant]

🚧 It seems like this PR has lint errors 🚧

I should be able to fix them for you. If you want me to, just comment
@zwave-js-bot fix lint

[zwave-js-assistant]

🚧 It seems like this PR has lint errors 🚧

I should be able to fix them for you. If you want me to, just comment
@zwave-js-bot fix lint

[AlCalzone]

@zwave-js-bot fix lint

[zwave-js-assistant]

🚧 It seems like this PR has lint errors 🚧

I should be able to fix them for you. If you want me to, just comment
@zwave-js-bot fix lint

[zwave-js-bot]

🐌 Please wait for the lint check to complete, then try again.

[zwave-js-assistant]

🚧 It seems like this PR has lint errors 🚧

I should be able to fix them for you. If you want me to, just comment
@zwave-js-bot fix lint

[AlCalzone]

@zwave-js-bot fix lint