Beta Asuswrt-Merlin 3006.102.6 Beta is now available

[dwadj]

I got a AiMesh setup with guest network pro setup for the IOT devices.
Main router GT-AX11000 pro is running 3006.102.6_beta2 as well as the Aimesh node GT-AX11000 pro.

The Reolink is connected on a AiMesh node (GT6) with the IOT network.
However it is not shown as IOT device in guest network pro.

All other IOT devices are in the guest network pro.
Is this an issue with the GT6 nodes since they only have stock firmware 388_24675?

Second issue.
I disabled the Aura light on all.
However on reboot the 2 GT6 nodes have the aura light again enabled.
I always need to disable it through the app.

 

[Jom76]

Updates my AXE16000 to Merlin 3006.102.6_beta2 from 3006.102.4...

Sonos speakers are throwing continuously the following message:

Nov 21 10:53:53 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:53 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:53 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:53 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:55 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:55 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:55 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:55 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:59 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:59 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:59 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:59 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:03 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:03 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:03 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:03 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:05 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:05 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:05 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:05 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:09 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:09 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:09 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:09 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2

Not sure why they won't connect anymore.
Any suggestions?

I have the same issues with sonos with RT-BE86U. I'm running Merlin firmware 3006.102.5, not the beta.
Look at my post in another thread for possible workaround https://www.snbforums.com/threads/issues-with-sonos-since-the-latest-update.95555/page-2#post-968977
Not the best workaround but it works. Hopefully the sonos issue will be solved in a future release of either sonos firmware or asus firmware. If you dont have this problem with firmware 3006.102.4 perhaps the issue was introduced in 3006.102.5? I might try downgrading if it's possible to do that?