Delete notification_types_node when there are no supported notification types

[monikasoni]

Change

When the notification frame of the command class contains more than two bit masks, the SUPPORTED_NOTIFICATION_TYPES node stays undefined. Consequently, the ZPC (Z-Wave Protocol Controller) makes repeated attempts to retrieve the supported notification type from the device. This continuous loop causes the device to remain in an "Online interviewing" state for an extended period.

zwave frame

71 08 03 00 00 40

attribute store

(350) Supported Notification Types ........................ <undefined> (<>)

Logs

2023-Nov-28 13:25:19.410614 [attribute_resolver] Attribute ID 83 needs a Get 2023-Nov-28 13:25:19.411275 [attribute_resolver] Retransmitting Get command for Attribute ID 83 (attempt 4 out of 5)

2023-Nov-28 13:25:22.265804 [zwave_command_handler_callbacks] Dispatching incoming command (encapsulation 3) from NodeID 5:0 - [ 71 08 03 00 00 40 ] 2023-Nov-28 13:25:22.266390 [zwave_command_class_notification] Supported notification types Bit Masks length is wrong

2023-Nov-28 13:25:30.952589 [attribute_resolver] Attribute ID 83 needs a Get 2023-Nov-28 13:25:30.953289 [attribute_resolver] Retransmitting Get command for Attribute ID 83 (attempt 5 out of 5)

2023-Nov-28 13:25:33.824015 [zwave_command_handler_callbacks] Dispatching incoming command (encapsulation 3) from NodeID 5:0 - [ 71 08 03 00 00 40 ] 2023-Nov-28 13:25:33.824700 [zwave_command_class_notification] Supported notification types Bit Masks length is wrong

Checklist

• [x] A Contribution License Agreement has been established between @SiliconLabs and author's company (matching email domain)

[rzr]

Please rebase on main to make sure it's building