Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
bilalahmaddev opened this issue Feb 28, 2025 · 4 comments

Comments

@bilalahmaddev
Copy link

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

Image

@github-actions github-actions bot changed the title OperationalSessionSetup[3:00000000E226355C]: operational discovery failed: 32 OperationalSessionSetup[3:00000000E226355C]: operational discovery failed: 32 (CON-1573) Feb 28, 2025
@jonsmirl
Copy link
Contributor

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.

@bilalahmaddev
Copy link
Author

Where can I enable this to make session permanent?

@jonsmirl
Copy link
Contributor

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)
    {

@wqx6
Copy link
Contributor

wqx6 commented Mar 12, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants