CI-Uniti 102 appears as Cast target but fails to connect (Chromecast)

Streaming Audio
1

Hi everyone,

I’m having a minor issue with my CI-Uniti 102.

I didn’t notice the exact moment it started, but it seems that Chromecast functionality stopped working after a recent firmware update.

On my phone, the Naim device still shows up as an available Cast target, but selecting it results in nothing happening no connection or playback starts. So far, I’ve only tried power cycling (unplugging the unit from the mains), but that hasn’t resolved the issue.

Has anyone else experienced this, or is there a recommended fix/reset procedure for Chromecast on the CI 102?

Thanks,

Vladislav

2

Hello everyone,

Since my local installer claims no one else is experiencing this issue, and given that I don’t have deep access to debug the Naim unit directly, I ran a few network diagnostics and Python scripts from my PC on the same local network. Here is what I found:

  1. SSL / TLS Check**:** When testing the TLS connection via openssl s_client on port 8009, I get a valid SSL certificate.

  2. Cast Endpoint Query (/setup/eureka_info on port 8008): Querying the endpoint via curl returns a valid JSON payload containing the public key, timezone, and other device specs. However, there is a notable discrepancy in the firmware track:

  • Naim CI-Uniti 102:

    “release_track”: “dev-channel”

    “build_version”: “726811595”

    “cast_build_revision”: “1.68.cast_20250214_0202_RC06.726811595”

    Notice the RC06 (Release Candidate) tag and dev-channel track.

  • WiiM Player (for comparison): “release_track”: “stable-channel”

  1. Chromecast Discovery (pychromecast): When scanning for Chromecast targets on my network, there is a clear difference in how the devices are identified:
[3] WiiM Soba (audio) -> IP: 192.168.1.87
[4] Naim (cast)       -> IP: 192.168.1.90

Why is the Naim being identified generic “cast” instead of “audio” like the WiiM?

  1. Python Exception: During the discovery process, the Python script catches this SSL exception specific to the Naim unit:
Failed to determine cast type for host <unknown> (<urlopen error EOF occurred in violation of protocol (_ssl.c:1145)>) (services:{ServiceInfo(type='mdns', data='CI-Uniti-102-ad4****************4095._googlecast._tcp.local.')})

It seems the Naim unit is stuck on a dev-channel build for its Google Cast module, causing SSL handshake drops during client metadata queries, which prevents phones and scripts from casting reliably.

I believe I’ve extracted all the debugging information I can from my side. Any insight or help on how to push the unit back to a stable release track would be greatly appreciated.

Best regards,

Vladislav

3

Vlad, have you contacted Naim support about this?

4

Thanks for the replies!

To be honest, this issue has been going on for a while, but since it wasn’t a total dealbreaker for me (I can always cast to the TV and run audio via HDMI), I didn’t reach out to support right away.

I kind of expected this to be a known issue with a quick fix in “two clicks.” But when I asked my local dealer, they told me I was the only one complaining :slight_smile:

I’ll keep my fingers crossed for a bit to see if anyone here has run into this before. If nothing comes of it, I’ll definitely open a ticket with Naim Support.

Cheers,

Vladislav

5

I have recently purchased a CI-Unit 102 and I have discovered the same issue with mine. It is visible as a Chromecast device within BBC Sounds but does not connect when that option is chosen.

I have also tried several times to set it up as a device within the Google Home app, as suggested by the Naim support info, but the Home app cannot see the CI-Uniti on my network, despite it being powered up and connected to the network via Ethernet.

I haven’t had chance to discuss this with my dealer yet but I will be doing so soon and it will be raised with Naim support.