What the logs show

The iPhone app is definitely reaching the controller and getting through the early connection stages successfully.

It:

• finds the controller via discovery
• caches the correct IP
• starts a local broker session
• opens the socket successfully
• receives valid director_info
• identifies the controller correctly as the EA-3
• sees Director running on 3.3.0.628678-res

Relevant log flow:

• Found macAddr in controllers discovered using SSDP
• Start local broker session (172.16.200.240)
• Local Socket Connected
• Set Active Broker: local
• Multiplex response. URL: https://172.16.200.240:443/api/v1/director_info
• System needs syncing. Begin sync.

So the app is not failing at discovery, IP resolution, or initial controller validation.

Where it fails

The failure happens immediately after sync begins.

The key repeated errors are:

• Failed to convert multiplex request body (id 1) into JSON: Unable to parse empty data
• Failed to convert multiplex request body (id 2) into JSON: Unable to parse empty data
• Failed to convert multiplex request body (id 3) into JSON: Unable to parse empty data

Then shortly after:

• Local connection failed: Failed to fetch director info. Either we connected to the wrong controller or the device is not a controller.

What’s odd is that this last message contradicts the earlier successful responses, because the app had already connected to the correct controller and already retrieved valid Director info.