You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Finding esp_zb_identify_notify_handler_register in the API I figured registering a callback would automatically route identify commands for the endpoint to the callback. But this doesn't seem to be the case.
With only a handler registered with esp_zb_core_action_handler_register I receive a ESP_ZB_CORE_SET_ATTR_VALUE_CB_ID command ID at the action handler. However, this only happens on the first 'boot' of the ESP.
When I register a callback with esp_zb_raw_command_handler_register, the identify command is seen on every request. The command ID and payload is as expected. If I return false from this callback (unhandled) the command appears to be then routed to the callback registered in esp_zb_core_action_handler_register - but again only on the first identify request for that boot.
If I call zb_zcl_send_default_handler and return true from my raw command handler, the core handler is not called. This is expected behavior for core, but hoped it would call my endpoint specific callback from esp_zb_identify_notify_handler_register.
Additional context.
Sending ID commands from homeassistant. Commands appear to be well formed coming out of home assistant and received at the raw command handler.
Trying to get IDs to work on an EP specific basis without writing endpoint specific code into my core action handler.
***edits - clarity.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
How is esp_zb_identify_notify_handler_register intended to be used?
How is esp_zb_identify_notify_handler_register intended to be used? (TZ-1515)
Jan 25, 2025
Question
Finding
esp_zb_identify_notify_handler_register
in the API I figured registering a callback would automatically route identify commands for the endpoint to the callback. But this doesn't seem to be the case.With only a handler registered with
esp_zb_core_action_handler_register
I receive aESP_ZB_CORE_SET_ATTR_VALUE_CB_ID
command ID at the action handler. However, this only happens on the first 'boot' of the ESP.When I register a callback with
esp_zb_raw_command_handler_register
, the identify command is seen on every request. The command ID and payload is as expected. If I returnfalse
from this callback (unhandled) the command appears to be then routed to the callback registered inesp_zb_core_action_handler_register
- but again only on the first identify request for that boot.If I call
zb_zcl_send_default_handler
and returntrue
from my raw command handler, the core handler is not called. This is expected behavior for core, but hoped it would call my endpoint specific callback fromesp_zb_identify_notify_handler_register
.Additional context.
Sending ID commands from homeassistant. Commands appear to be well formed coming out of home assistant and received at the raw command handler.
Trying to get IDs to work on an EP specific basis without writing endpoint specific code into my core action handler.
***edits - clarity.
The text was updated successfully, but these errors were encountered: