Elac Discovery Z3 firmware 1.0 (build 56)

I’ve had 4 of the Elac Z3’s for a while now and all have worked perfectly with Ethernet until firmware version ‘1.0 (build 56) stable’ was available.

I updated one of mine to the new firmware and since that time the unit is losing the connection with Roon every week or so. Power cycling the Z3 will get the connection going again for another week or so then it drops again. Rinse and repeat.

I’ve reported this to ELAC via the support ticket process but have not gotten any response after several months.

Since this is a Roon Ready speaker system and sold in the Roon store I hope Roon Support can get involved.

I have 3 Z3’s on 1.0 (build 55) that never loose connectivity.

I have two (would like to sell) on build 56 but have not had any difficulties.

Mine work via Ethernet w/o a problem. Once in a while it will not connect via airplay when I use my iPad as a source. Power cycling resolves that

Purchased the first one almost 4 years ago and added the other 3 at different times since then. Had a few issues with the first one on Wi-Fi but have not had any drops since the house was wired for Ethernet.

The only one dropping off the network, weekly or every other week, is the one in the home office space on a second switch.

But the drops did not start until it was upgraded to firmware 56.

I’ll try swamping it out with one of the others on firmware 55 to see if the issue continues.

Thanks @7NoteScale and @KMM for the replies.

Hi @Mike_LC,

Did you have any luck with your issue? Let me know and if at all possible, give me a good date/time that you see it drop (might have to be just a general window). I might be able to find something in the logging that points us in the right direction.


It happened on Feb 4th in the morning. I had started some music playing then it dropped off with Roon telling me to select a zone. Power cycled the Z3 and the zone reappeared with the progress bar. Hit the play arrow and the music continued from where it left off. It is a continuing saga since the last firmware update happening every week or two.

Is that time frame sufficient?

I have been using a Z3 (build 56) since early September and have experienced the same thing periodically. It just happened tonight while I wasn’t actively using the speaker. I upgraded my ROCK to earlyaccess build 1208 and when Roon remote reconnected to the core the Z3 disappeared from the list and I was asked to select a zone. I waited for about 5 minutes before yanking the power to the Z3. It was automatically re-selected in Roon remote within a minute of the power cycling. I should have checked to see if the Z3 was still answering by either the Z3 Control app or its web interface but sadly didn’t think to do so until it was back up.

I started the core update around 7:05pm and the Z3 power-cycle around 7:10pm, both EST. I can log these incidents more carefully in the future if it would be helpful.

Hi @Mike_LC,

Here’s what I am seeing for the morning of the 4th.

02/04 04:37:34 Trace: [Office Elac Z3] [Lossless, 16/44 TIDAL FLAC => 16/44] [100% buf] [PLAYING @ 0:04/6:13] Where Do You Start?/Once Upon a Time - Diana Panton / Alan Bergman / Marilyn Bergman / Johnny Mandel / Charles Strouse / Lee Adams
02/04 04:37:39 Trace: [Office Elac Z3] [Lossless, 16/44 TIDAL FLAC => 16/44] [100% buf] [PLAYING @ 0:09/6:13] Where Do You Start?/Once Upon a Time - Diana Panton / Alan Bergman / Marilyn Bergman / Johnny Mandel / Charles Strouse / Lee Adams
02/04 04:37:41 Warn: [Office Elac Z3] [zoneplayer/raat] long rtt sync ELAC Discovery Z3: realtime=292778224392292 rtt=63500us offset=214949333392us delta=13834us drift=13547us in 12.202s (1110.228ppm, 3996.820ms/hr)
02/04 04:37:42 Debug: FTMSI-B-OE ti/9622353F exit thread signalled

This just shows me that the device went unresponsive with the long sync error and it happens again right after that. It also happens that evening (only looking at the 4th).

From our perspective, the device is inaccessible. The only advice I have to offer is to hard reset the speaker. I would also be happy to give instructions for wiping the Roon slate clean and re-installing but I’m not certain it would help. It would serve to assist in the process of elimination though so I will list the steps below if you’d like to give that a try too.

Please be aware that this will reset your Roon Settings → Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:

  • Create a Backup of your current Roon Database
  • Stop RoonServer from running in Nucleus’s WebUI
  • Navigate to your Roon’s Database Location
  • Find the folder that says “RAATServer”
  • Rename the “RAATServer” folder to “RAATServer_old”
  • Restart the RoonServer in the WebUI to generate a new RAATServer

@Tom_Baxter I would normally ask you to open your own thread but I am going to dig into your diagnostics here in a moment and will reply to you as well.


Hi @Tom_Baxter,

I can’t find anything particularly telling in your diagnostics with the given time stamps. There are general “can’t connect” messages to the Z3 but this can happen if they’re in standby or off.

I would ask that you give the steps I provided to @Mike_LC a try. I would also invite you to try and pin down a date/time/track playing where it disconnects. I suspect the issues are similar if not the same but I’d like to confirm.


This issue happened again on 2/21/23 at 8:30 am. I looked at the clock exactly when it happened. I had just searched on Nina Simone and started an album playing. It dropped off and roon put up the “select a zone”. Power cycled the z3 and it was back immediately. I had intended to check the Z3 network control screen to see if it was on the network but in my haste I forgot. That is the first thing I intend to do next time.

Later I checked the log and searched on Nina Simone knowing that would take me to the right spot but the first occurrence for that name appeared at 14:28:51 in the log. So based on that it appears the time on my NUC may be off by 6 hours. I haven’t checked it since it was built in 2019.

It would be convenient if Roon displayed the core machine date and time stamp on the remote screen.

All logging is in GMT time and ROCK/Nucleus both maintain a time sync with UTC to further that consistency! All appears to be set correctly.

Thank you for collecting the instance information. It makes things a lot easier in identifying the key moments in the logs.

The snippet below shows we start losing smooth connectivity to the device.

02/21 14:30:44 Warn: [Office Elac Z3] [zoneplayer/raat] long rtt sync ELAC Discovery Z3: realtime=153330981584414 rtt=43500us offset=126324208584us delta=-36051us drift=41426us in 19.4375s (2131.241ppm, 7672.468ms/hr)

This snippet gives the same warning but then the connection is lost. These two warnings are 6 seconds apart.

02/21 14:30:50 Warn: [Office Elac Z3] [zoneplayer/raat] long rtt sync ELAC Discovery Z3: realtime=153336755816414 rtt=43500us offset=126324035816us delta=-172768us drift=-131342us in 25.5115s (-5148.345ppm, -18534.042ms/hr)
02/21 14:30:50 Trace: [raat] [Elac Discovery Z3 @] => Disconnected
02/21 14:30:50 Trace: [raat] [Elac Discovery Z3 @] lost client connection. Retrying
02/21 14:30:50 Trace: [raat] [Elac Discovery Z3 @] connecting (attempt 1)
02/21 14:30:50 Info: [transport] destroyed zone Office Elac Z3 was playing? True
02/21 14:30:50 Trace: [zone Office Elac Z3] Suspend
02/21 14:30:50 Info: [zone Office Elac Z3] OnPlayFeedback Stopped

After that, it looks like the device became visible to Roon again

02/21 14:32:15 Info: [raat] Initializing RoonReady Device
02/21 14:32:15 Info: [raat]     Address:         192.168.50.x
02/21 14:32:15 Info: [raat]     Port:            43711
02/21 14:32:15 Info: [raat]     IsDev:           False
02/21 14:32:15 Info: [raat]     UniqueId:        00000000-0000-0000-x-x
02/21 14:32:15 Info: [raat]     ProtocolVersion: 3
02/21 14:32:15 Info: [raat]     Version:         1.0 (build 56) stable
02/21 14:32:15 Info: [raat]     RaatVersion:     1.1.38
02/21 14:32:15 Info: [raat]     Model:           Discovery Z3
02/21 14:32:15 Info: [raat]     Vendor:          Elac
02/21 14:32:15 Info: [raat]     VendorModel:     ELAC Discovery Z3

From our perspective, the Z3 starts to walk out the door and then finally does. Only to pop back in within a couple of minutes. My only recommendations are to look at cables, factory reset the device, and try different ports.

If you have another instance you’d like to have me investigate, please just let me know.


1 Like

Thanks Wes. Alt least now I know to look 6 hours ahead in the logs. The Z3 popped back in after the power cycle (pull/replace the plug). That is the only way to get the connection back after it drops.

I’m thinking a factory reset is in order (if you haven’t done that already).

I did find this thread ELAC Discovery Z3 not connecting anymore that indicated the same issue and it was overcome by updating the Z3.

Let me know how it goes. I’m thinking there’s not much Roon can do but we are always happy to give you the story as Roon sees it!


Thanks for your time invested looking into this. This ticket can be closed.

1 Like

This has happened to my Z3 again, but I was unable to get exact timing details since I wasn’t the one using Roon at the time. When I discovered that the Z3 was unresponsive I verified that:

  • It was unreachable via its web interface
  • It was not discoverable by the ELAC iOS apps

I was still able to ping the speaker, but that’s about it. Like before, a power-cycle restored connectivity. Being that I couldn’t connect by three different methods, I’d say that it doesn’t look like an issue within Roon.


I didn’t think it was a Roon issue either. I had hoped they would be able to duplicate the issue if they had A Z3 on hand with firmware 56 for verification. But it’s a minor issue, not a big deal. I could try the factory reset and see if I could stop the updates at firmware 55 but will probably just let it ride and see if the next firmware update fixes it. I have 3 more Z3’s on 55 and they never drop the connection. I will hold off on updating those.

Thanks for the input.

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.