[Feature request]: Add router device property favorite

[bongosmurf]

Is your feature request related to a problem? Please describe

I'm always frustrated when I want to add a new device to the network and have to power off my lab/testing devices to prevent them from parenting the new device. Rationale is that I want the new device to join through a device that has an expectation of permanently being part of the network, so that the new device will not have to time out to search for a new parent. Also, there are to my knowledge devices that will not look for a new parent.

Describe the solution you'd like

I would like to be able to mark a limited number of strategically located router devices as favorites and be able to use a "Permit join (Favorites)" selection rather than "Permit join (All)". In order not to overburden the network with individual permit join request messages, the number of favorites should be limited to a dozen or so.

Describe alternatives you've considered

See
[Feature request]: Add router device property no-join #27011

Additional context

I frequently have new devices/device types that I'm experimenting with in my lab. They have no expectation of being powered while in the lab. Also, they will be located elsewhere, when placed into service.

[PayneRae]

Hello, have you tried pairing via a specific device: https://www.zigbee2mqtt.io/guide/usage/pairing_devices.html
or binding: https://www.zigbee2mqtt.io/guide/usage/binding.html?

[PayneRae]

Hi again, after reviewing the documentation and alternative fix more closely, I would recommend pairing via a specific device during onboarding. Suggesting binding was a mistake. Pairing via a specific router or the coordinator would be more tedious and case-by-case than your suggestion, but perhaps it could be a temporary fix.

I understand @Nerivec described the problem with your previous suggestion #27011 as not feasible due to the many join requests that would be sent out to individual devices overloading the network, and any attempt to alleviate this would cause timing and feedback problems.

For your favorites idea above, instead of just the single Permit join(all) request being sent, you would also have a Permit join(favorites) request. I wonder, would the network be constrained with just these two requests? Perhaps I have misunderstood and individual device requests would be sent instead.

I am interested in following this issue and seeing the comments. I hope pairing via a specific router or coordinator can be a temporary solution for you.