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

esp_zb_zdo_device_leave_req() It did't work. (TZ-1439) #522

Open
1 of 3 tasks
badjane opened this issue Jan 3, 2025 · 7 comments
Open
1 of 3 tasks

esp_zb_zdo_device_leave_req() It did't work. (TZ-1439) #522

badjane opened this issue Jan 3, 2025 · 7 comments
Labels

Comments

@badjane
Copy link

badjane commented Jan 3, 2025

Answers checklist.

  • I have read the documentation ESP Zigbee SDK Programming Guide and tried the debugging tips, the issue is not addressed there.
  • I have updated ESP Zigbee libs (esp-zboss-lib and esp-zigbee-lib) to the latest version, with corresponding IDF version, and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.

v5.2.1

esp-zigbee-lib version.

1.6.0

esp-zboss-lib version.

1.6.0

Espressif SoC revision.

ESP32-C6

What is the expected behavior?

When the network is open, the endpoint device will be able to re-enter after leaving the current network

What is the actual behavior?

This is because the end device that invokes the interface cannot connect to the previous network after the restart

Steps to reproduce.

  1. A coordinator and endpoint device
  2. Ask the coordinator to turn on network 180s
  3. The endpoint device successfully joined the coordinator network
  4. Ask the coordinator to turn off the network 180s
  5. Shortly after joining, the endpoint device calls "esp_zb_zdo_device_leave_req()", leaves the network, and the software restarts
  6. Ask the coordinator to open the network 180s again
  7. At this point, the endpoint device can easily repeat the error of not continuing the network

More Information.

not

@badjane badjane added the Bug label Jan 3, 2025
@github-actions github-actions bot changed the title esp_zb_zdo_device_leave_req() It did't work. esp_zb_zdo_device_leave_req() It did't work. (TZ-1439) Jan 3, 2025
@badjane
Copy link
Author

badjane commented Jan 3, 2025

esp_zb_factory_reset() --> I tested it, but it didn't work

@badjane
Copy link
Author

badjane commented Jan 3, 2025

Snipaste_2025-01-03_16-46-28

@badjane
Copy link
Author

badjane commented Jan 3, 2025

image

@badjane
Copy link
Author

badjane commented Jan 4, 2025

esp-zigbee-lib version.
1.5.1

esp-zboss-lib version.
1.5.1
It works correctly

@xieqinan
Copy link
Contributor

xieqinan commented Jan 9, 2025

@badjane ,

Could you share the log of the end device? I suspect that the re-steering logic might have been triggered in the application.

@badjane
Copy link
Author

badjane commented Jan 11, 2025 via email

@xieqinan
Copy link
Contributor

press the button to close the HA switch and connect to the network.

I am a bit confused about this step. Which device do you expect to connect to the network? If it's the HA lamp, I don't think it's necessary since it is already part of the network.

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

No branches or pull requests

2 participants