There’s a flaw with the new auto sleep function (at least on my Moon Neo ACE) that I’m hoping you can address in a future update.
The function to sleep works…
Set Auto Sleep to 30 seconds (for ease of testing)
Play music through Roon
Stop music
30 seconds later and “click” Moon goes to sleep
However this also happens if you switch the input to something else…
Set Auto Sleep to 30 seconds (for ease of testing)
Play music through Roon
Stop music
Change input (to optical input for example)
30 seconds later and “click” Moon goes to sleep
This is very frustrating when you’ve just settled down to a movie and the device goes to sleep half-way through the film (I had auto sleep set to 1 hour).
Thanks for the report, @Jason_T — I’ve passed this along to the team for further investigation and I’ll be sure to reach out when we have more information.
I’m not having any issues with my Simaudio Moon 390 Preamp. I’ve set it for 30 seconds and if I pause the track with the remote, then click to Phono, for example, the unit remains on.
Clicking Stop on the remote control seems to have the same effect as clicking the Input on the remote. Roon indicates “Lost control of the device because the input was switched”.
Interesting and firstly, my apologies, but by “Stop” I meant “Pause” from Roon.
I’ve tested a few more scenarios. All with auto sleep set to 30 seconds:
Play track in Roon…
A. Click pause in Roon = ACE sleeps after 30 seconds
B. Press pause on remote = ACE sleeps after 30 seconds
C. Press stop on remote = ACE stays awake and message in Roon “Lost control of the device because the input was switched”
D. Switch input on remote = Roon continues to play, but input on ACE is correctly changed
E. Click pause in Roon, then switch input on remote = ACE sleeps after 30 seconds
F. Press pause on remote, then switch input on remote = ACE sleeps after 30 seconds
I have checked for firmware updates and unplugged it from the mains for 60 seconds. No difference.
Mind Version: 1.09
ACE Version: 1.14
EDIT:
Roon Version: 537
In my opinion A, B & C are correct behaviours
D seems unrelated to the auto sleep feature
E & F are undesirable behaviours of the auto sleep feature
We really appreciate the detail that you’ve explained your testing, so thank you for that. I’ve forwarded this to the QA team for further analysis. As @Greg mentioned, we’ve confirmed that things are working with the 390 so there may be a discrepancy with the ACE causing this behavior.
By way of an update; There’s a firmware update for the Moon ACE (version 1.15) which addresses auto-standby issues, but it’s not made any difference to what I’m experiencing with the Roon Auto-Sleep.