We’re checking with some new WiFi 7 router and detect that Ring Doorbell 2nd gen wouldn’t able to scan and connect to some AP which have too much elements in Beacon/Probe Response.
It seems like Ring Doorbell has its limit for checking the length of tag parameters in Beacon/Probe Response which cause this issue.
It should be a limited in Ring Doorbell 2 and this issue is not seen when I tested with other devices and Ring Camera also.
Need Ring develop team help to check because if we go to WiFi 8 for the next couple few years with more elements in Beacon/Probe Response, Ring might get this issue a lot
Additional information,
Looks like Ring Doorbell 2 would not accept Beacon with the Tagged parameters > 476 bytes
Hi @DannyVu_AN. As we value our neighbors’ feedback, we’ve created a Feature Request board. Feel free to add this and any future feature requests there. This will help us to organize and share your requests with our teams here, as well as allow other neighbors to comment and add interest, all in one place. Feel free to link that post you make in the Feature Request board here so other neighbors that come to this thread can easily find your feature!
1 Like