It would not impact me at all, but, I never argued there should not be a WOL ability or that the dev’s should not include it, I think that they will add it in at some point since there is enough interest in it. I was just responding to a specific line that I disagreed with in that “keeping the server up all the time is not a good idea”. Servers are on 24/7 all the time without negative hardware or software consequences. Whether a Roon server is running 24/7 or not is mainly a financial decision, not one that is based on hardware or software needs.
When I look back on my post from November, so much has now been implemented. Now that we have many users moving into Roon Server / Roon Bridge / tablet Control setups I’d hope a WoL capability is further up the list. Let’s drop a flag for @danny and see if he can add anything to his earlier comments.
the feature has actually become more complex… should it wake up roon bridges? how about roon ready devices?
Probably. The question becomes does it wake up everything Roon on the network or only what was last used…is there a way to have a user choose what to wake?
thats a good idea too, just make a WOL manager
Just the server.
I don’t think there’s any need to over complicate this. On start-up, Roon just needs to send a magic packet to a specified MAC address. If it’s easy to implement, then additional MACs could be included but one would be suffcicient for me.
indeed. please make it happen.
hi guys, i have a problem. i have roon server installed on my old mac mini (2012) and everytime he goes to sleep i cant wake him up with the roon app. any ideas how to solve this problem?
Don’t let your mini fall asleep, or if you really must – use a (free) Wake-on-LAN app:
OS X (or should I say macOS already? ;-)): https://itunes.apple.com/nl/app/wake-me/id662753364?l=en&mt=12
As for Roon support WOL: while sending out a magic packet isn’t exactly rocket science, with all the different networks (Wifi and extenders, anyone?) / endpoints around, things could turn into a support nightmare quickly. Even a simple table containing MAC-adresses of devices to be woken would need to be cached and updated on all different remotes in use.
Why do people insist on trying to over complicate this? Most of people would be happy with the app just sending one magic packet directed at the Roon server.
The Squeezebox apps (Ipeng, Squeezepad) have been offering the feature for years. High time Roon lab did something to promote green use.
THX a lot René
Would be great, plus at least one connected NAS drive would be ideal. I don’t think it’s complicated even to support multiple devices. All you need’s their MAC addresses in most simple home network environments. I use a few tools and just send two wake ups for good luck - never fails but not half as convenient. If Roon wanted to be clever it could look ahead at your playlist, and if your NAS is offline trigger the wake up based on its wake-up duration. Even that’s petty trivial IMO. Outside of Roon I script mine to wake up before backups (2 min lead time). But there are lots of priorities - do I want this over EQ/Room Correction? No. Although it’s significantly simpler to implement than either of those.
A post was split to a new topic: Play sleep mode
Because we like to think about solutions to the inherent problem at hand, and not a solution to a single situation.
We’ve met about this feature multiple times and spent unknown hours discussing it… WoL provides such a bad user experience, and we are trying to fix that core bad experience in a way that doesn’t have us building a complicated WoL system.
We can solve it nicely in some simple cases (the one you state), but it’s unclear to me if that is the common case.
We’ll keep on thinking about something, but in the meanwhile, use a 3rd party WoL app that solves this problem for all use cases. Sorry guys! I know it’s not the answer you want to hear, but this is what it takes to make good software.
WoL provides such a bad user experience,…
??? - but not with a third party app? Sorry, but I’m struggling to understand the logic here.
Anyway, no reply needed. I’m done with this thread
I have a little free app on my iPhone that wakes my Windows 10 PC. Works great. I can get the name if anybody’s interested.
Just paid for my lifetime subscription and I love it so much!
WOL would be highly appreciated! My little Intel NUC is now running 24/7 with Windows 10. Letting hime sleep from time to time wouldn’t be bad
It seems Roon controller still doesn’t seem to be able to send a wake-on-lan package to Roon Core.
Did you really give up on this?
Having it would be great because today I am forced to keep my MacMini on the whole time.
Since I never know if my Core is sleeping your suggestion of using a 3rd party app forces me to:
- Load Roon Controller
- If it can connect… load a WOL app an wake server
- Load Roon Controller again
This is so inconvenient.
Can you explain what’s the downside of silently sending a WOL package to the Core the first time a Controller tries to connect to it?
Feature Requests don’t come with guaranteed developer response. We get to tell the devs what we want and why. They build the product. Occasionally they will poke their heads in and say that something is being picked up, less often they will say something is ruled out. More often they will take the Requests on board without ruling something in or out.
There are any number of WoL apps that can be configured to send a packet in a myriad of ways. Features to implement something in Roon that can be readily done outside Roon may not enjoy the same priority as things that only Roon can do.
If WoL arrangements are causing inconvenience, I’d suggest fixing them using existing tools external to Roon rather than continuing to suffer through any development and implementation period.