Posts: 3
Joined: Jan 2017
Reputation:
0
2017-01-13, 08:43
(This post was last modified: 2017-01-13, 09:13 by Jack2.)
Since Kodi 17 each server will be automaticly wakeup through a magic paket.
This is for sure not ideal, because in my situation it wakeups 3 file servers and this is maybe only if i want to stream something from the internet.
In Kodi 16 was this different. The server was wakeup only if you selected the source in the video section.
I am using the functionality under power saving: Try to wake server on access.
Is there a work arround or some additional configuration possible to get the same functionality as in Kodi 16?
Thanks for helping!
Posts: 3
Joined: Jan 2017
Reputation:
0
@Developers:
Is it possible to for future releases to make this configurable?
-Wakeup servers when you select the source in the video section. (as is in Kod 16)
-Wakeup all servers after starting (as is in Kodi 17)
Posts: 283
Joined: Mar 2012
Reputation:
13
Thanks for the testing and logs, other skins have been known also to access media when starting and now it seems Estuary does too. There are reference to 'folder.jpg' on media sources and that will trigger wake-on-access. Perhaps there are some skin settings that can be deactivated to avoid the problem, I dont know. In any case this issue belongs under Estuary so try to get attention in that sub-forum if no-one notices these posts.
Posts: 132
Joined: Jan 2012
Reputation:
1
Has this ever been resolved? It’d be nice if Kodi strictly only woke up a server when it accesses a media file (e.g. movie) on that server. As the OP metioned, you might start Kodi only wanting to stream content and it ends up waking up multiple media servers, unnecessarily spinning up hard drives and wasting energy. I realize it was said that this is an issue related to the skin, but I didn’t find any posts related to WOL issues with this skin.
It seems that Kodi could more strictly enforce the wake up on demand feature without allowing skins to somehow override this. It’s a poor user experience for most, since they won’t understand why the setting isn’t being honored properly.
Posts: 1,918
Joined: Sep 2015
Reputation:
60
Atreyu
Posting Freak
Posts: 1,918
A quick way to work around this may be disabling 'wake on magic packet' on the NIC's of the server(s) that shouldn't be woken up if possible.
Computer will still wake up when a share is accessed.
Ofcourse, adding some options for this in Krypton would be great.
Posts: 1,918
Joined: Sep 2015
Reputation:
60
Atreyu
Posting Freak
Posts: 1,918
Yes, pointed that out indeed
