First things first...
You should upgrade to 24.10 since 23.05 is EOL. The hardware works very well with 24.10, so there is no reason to avoid the upgrade.
Moving on...
Remove the VLAN filtering line above.
Then, in the section below, edit the lan interface to use br-lan.1 (instead of br-lan):
On the AP, it is similar...
Delete the last line:
use device br-lan.1:
Make the jn_iot network on the AP unmanaged:
It should look like this:
config interface 'jn_iot'
option proto 'none'
option device 'br-lan.10'
Delete all of this:
The rest of my comments are not part of the core issue, but recommendations that will improve the performance:
For each network, use the same SSID for both bands. This allows client devices that support both bands to switch between bands as needed for performance reasons. And for devices that support only 2.4GHz, this will have no impact at all. Make these changes on both the router and the AP.
Channel selection is critical (as is power):
For proper roaming, the radios should be set such that they use different, non-overlapping channels. It is also best to reduce the power on each radio such that you reduce the size of the area it covers to the minimum required, thus also reducing the overlap. This encourages the client to roam between APs. Obviously the encryption type and passphrase need to be the same for all APs on a per-SSID basis.
Don't use mixed mode as it can cause problems. Select either wpa2 (psk2) or wpa3 (sae). This advice is true for all APs
Remove the force line from the DHCP server for jn_iot (this is on the main router):
Finally, you may want to adjust the firewall on the main router to prevent the forwarding from iot > lan. My preferred method to do this is the same as the firewall used in a guest network. If you want to be able to initiate connections from the lan to the IoT network, you can add a forward for it (source lan, destination iot). That said, you may want to hold off on the firewall adjustments until you have verified that the rest is working.
After making the changes recommended above, restart both MT6000 devices and test.
Don't forget to upgrade to 24.10!