esp-matter icon indicating copy to clipboard operation
esp-matter copied to clipboard

OperationalSessionSetup[3:00000000E226355C]: operational discovery failed: 32 (CON-1573)

Open bilalahmaddev opened this issue 1 year ago • 4 comments

Why my commissioned device received these errors when Matter app is not opened:

Image

bilalahmaddev avatar Feb 28 '25 11:02 bilalahmaddev

At boot your controller is trying to reestablish a saved permanent session to a device which is not turned on.

When you create a session there is a parameter for making a temporary or permanent session, you have it set to permanent.

jonsmirl avatar Feb 28 '25 18:02 jonsmirl

Where can I enable this to make session permanent?

bilalahmaddev avatar Feb 28 '25 18:02 bilalahmaddev

auto_resubscribe on esp

    subscribe_command(uint64_t node_id, ScopedMemoryBufferWithSize<AttributePathParams> &&attr_paths,
                      ScopedMemoryBufferWithSize<EventPathParams> &&event_paths, uint16_t min_interval,
                      uint16_t max_interval, bool auto_resubscribe = true, attribute_report_cb_t attribute_cb = nullptr,
                      event_report_cb_t event_cb = nullptr, subscribe_done_cb_t done_cb = nullptr,
                      subscribe_failure_cb_t connect_failure_cb = nullptr)
        : m_node_id(node_id)
        , m_min_interval(min_interval)
        , m_max_interval(max_interval)
        , m_auto_resubscribe(auto_resubscribe)
        , m_buffered_read_cb(*this)
        , m_attr_paths(std::move(attr_paths))
        , m_event_paths(std::move(event_paths))
        , on_device_connected_cb(on_device_connected_fcn, this)
        , on_device_connection_failure_cb(on_device_connection_failure_fcn, this)
        , attribute_data_cb(attribute_cb)
        , event_data_cb(event_cb)
        , subscribe_done_cb(done_cb)
        , subscribe_failure_cb(connect_failure_cb)
    {

jonsmirl avatar Feb 28 '25 18:02 jonsmirl

Hi, there is a feature named subscription resumption on the end-devices which helps the end-devices establishing CASE session with the controller/commissioner and reporting their statuses to the controller/commissioner. This could decrease the rate of the no-response error.

Looks like you are using a special Matter app to commission the end-device. And that Matter-app will send subscription request to the end-device after commissioning. The end-device will store that subscription and try to resume it on reboot. It will discover the Matter app over mDNS. If your Matter app is not open, it will not advertise mDNS service, so the end-device fails to discover the Matter app and resume subscription.

wqx6 avatar Mar 12 '25 12:03 wqx6

@bilalahmaddev Is there any update you can share? Please close this issue if resolved

dhrishi avatar Jun 06 '25 09:06 dhrishi

Closing as the questions are answered

dhrishi avatar Sep 13 '25 02:09 dhrishi