CRC16 Encap support.
More...
CRC16 Encap support.
Provides utility functions for CRC16 Encap support.
You can check if endpoint node actually supports CRC16 Encap. Also you can flag a node and endpoint as expecting a CRC16 response to make sure that you use the same encapsulation as the sender.
◆ zwave_command_class_crc16_clear_expect_crc16_response()
Clear the CRC16 expecting response flag for a given node and endpoint.
- Note
- Nothing happens if the flag is not set.
- Parameters
-
| node_id | Node ID |
| endpoint_id | Endpoint ID |
◆ zwave_command_class_crc16_init()
◆ zwave_command_class_crc16_is_expecting_crc16_response()
Check if the given node_id and endpoint_id is expecting a CRC16 response.
- Parameters
-
| node_id | Node ID |
| endpoint_id | Endpoint ID |
- Returns
- true if the node_id and endpoint_id is expecting a CRC16 response, false otherwise.
◆ zwave_command_class_crc16_is_supported()
| bool zwave_command_class_crc16_is_supported |
( |
attribute_store_node_t |
endpoint_node | ) |
|
Check if the CRC16 command class is supported by a given node and endpoint.
- Parameters
-
| endpoint_node | Endpoint node |
- Returns
- false if the node is still in interviewing state
-
false if the node does not support CRC16
-
false if the node explicitly does not want to send crc16 frame
-
true if the node supports CRC16
◆ zwave_command_class_crc16_set_expect_crc16_response()
Mark the given node_id and endpoint_id as expecting a CRC16 response.
- Note
- You can call this multiple times on the same node_id and endpoint_id to have multiples CRC16 responses
- Parameters
-
| node_id | Node ID |
| endpoint_id | Endpoint ID |