Mikrotik Audience experience is completely broken

Hey folks, I have a massive problem with my Audience devices.

Preconditions

3 Mikrotik Audiences: 1 primary device and 2 CAPs
7.12 ROS and routerboard firmware

I have owned these devices for several years, and everything worked like a charm.

Problems

1. Audience factory reset creates default encrypted WI-Fi network

For some reason, when I do a factory reset on the primary Audience, it doesn’t start with open Wi-Fi networks. Currently, I see two channels (2 and 5 GHz) networks which are encrypted with the password.

The most ridiculous thing is that the label on the bottom contains only ID, FCC ID, IC, E01, W01 and SN. There is no default Wi-Fi password and never was.

The primary device is in a pretty inconvenient place to play with a LAN cable, so I cannot get the wireless workaround.

2. Audience CAPs don’t connect to the primary device anymore.

I could unmount the primary device, set the admin password and change Wi-Fi settings in the QuckSet menu. These are the only changes I made.

I did a factory reset on two CAP Audiences, forcing them to start working as CAPs by default (pressing the RESET button for around 10 sec to power the devices). Then, I synced devices via the WPS button. Both CAPs were green, and I thought everything was going well.

However, CAPSMAN doesn’t add my two CAPs at all. There are no other devices In CAP Interface. DHCP serverLeases doesn’t show any CAPs with their IP addresses.

The primary device’s log is clean and contains no errors. I obviously cannot check the CAP log because I cannot reach both devices.

Questions

  1. What happened with the default Wi-Fi config on the primary device?
  2. Why do CAP Audience devices not connect appropriately as they have for years? How can I add CAPs?

Regarding the second problem, the solution that worked for me was to perform this command on the primary device

/interface bridge port add bridge=bridge interface=wlan3

It makes the first problem more prominent because, obviously, something went wrong with the default config.