[VU+ Duo2] WOL has stopped working

[ArowonA]

Hi,

Is this still an issue as I've just tried and cant get it working?

 

[ashhinton]

What happens after a power failure?
Whenever I've shut it down (via the power switch at the rear) and powered it back up again - for example when I moved its location - my VU+ Duo2 booted back into normal (network reachable) standby.

Appreciate some might want deep standby and then WOL, but I was thinking what if I'm away.. theres been a power cut.. the power is back on and I wanted to set up a recording remotely (I have a static IP & VPN into my network) then if its default is to be in normal standby then not having WOL for now isn't too much of a problem.

 

[ArowonA]

What happens after a power failure?
.

Hmm, interesting, kind of unrelated to what I was asking as I was looking for a way to resume from deep standby while away from the house, but I suppose I could connect my DUO2 to a wemo switch and then rather than sending a WOL packet, toggle the power on and off.
Thanks, that could be a good workaround.
It would be nice if wol worked though

 

[ArowonA]

Finally got this working, I found out if I created a script containing the ethtool command and coldboot 1, WoL would work, so I went through the /etc/rc0.d folder removing all the files except K32ethwol and S50coldboot and it worked, I then added the files back a few at a time until I found the culprit, turns out it was S40umountfs, removing that symlink fixes the problem but I guess it's important to unmount stuff?
So I've replaced the file /etc/init.d/umountfs with the version here

http://code.vuplus.com/gitweb/?p=vuplus_openvuplus;a=blob;f=meta-openvuplus/recipes-core/initscripts/initscripts-1.0/umountfs

and it's working now, hopefully that file unmounts everything as it should?

 

[ashhinton]

Hmm, interesting, kind of unrelated to what I was asking as I was looking for a way to resume from deep standby while away from the house, but I suppose I could connect my DUO2 to a wemo switch and then rather than sending a WOL packet, toggle the power on and off.
Thanks, that could be a good workaround.
It would be nice if wol worked though

I was thinking more along general day-to-day lines, where because we know WOL doesn't work then we ensure the Duo2 is left in normal standby **particularly when we know we're going to be away** - obviously you can use deep standby if you're at home, because you have physical access to the unit.

My general question was whether its normal behaviour, after a power fail, to come back on in normal standby again (and not deep standby) or whether the behaviour follows the pattern of coming back on in whatever state it was in before the power went off.

I wouldn't advocate having something which can switch off the power as if you're pulling out the mains lead, as it probably won't do the box a lot of good and will almost certainly shorten its life.

Digressing a bit, it might be worth checking what the power saving difference is, compared to any extra costs/kit/shipping (& related emissions etc if you're thinking of the environment) to turn the power off. Will WOL be fixed before the power saving difference is worth the risk, and cost, of killing the power instead of using normal standby?

I once had a similar discussion with somebody who insisted on switching their internet router on & off each time they checked their email (!) thinking they were being environmentally friendly. Good intentions but it shortened the life of the router significantly, which needed me to travel & install a new one which had to be shipped from a supplier (by road). Also the financial costs of the a new router & my time = probably much more than the electricity saved, even at current (excuse the pun) energy prices.

 

[Trial]

Hi ArowonA,
thank you I can confirm that it works. I cannot say if the different umountfs can do some harm. I also did take a look at the WOL problem but could no imagine that unmout can have an influence on it.

I think

umount -f -a -r > /dev/null 2>&1

is the bad boy as it also unmount /proc which is needed to set WOL.

Ralf

 

[Rob van der Does]

....it might be worth checking what the power saving difference is, compared to any extra costs/kit/shipping (& related emissions etc if you're thinking of the environment) to turn the power off. ....

Power consumption is 0.5W versus around 15-20W. So if a box is used for 6hrs a day that would come down to around 15W x 18hrs x 365 days = 100KWh per year.
That is quite a lot, especially if you have more then one box.

 

[ashhinton]

Power consumption is 0.5W versus around 15-20W. So if a box is used for 6hrs a day that would come down to around 15W x 18hrs x 365 days = 100KWh per year.
That is quite a lot, especially if you have more then one box.

Wow, is that deep standby vs. normal standby or vs. switched on? I guess there's not a lot of difference between the two latter modes.

Assume deep standby still wakes up for a timer recording?

 

[ArowonA]

if you're pulling out the mains lead, as it probably won't do the box a lot of good and will almost certainly shorten its life.

From what I can tell, and people please correct me if I'm wrong, "Deep standby" is basically shutdown, it just leaves the IR receiver activate. So therefore, turning the power off (with a wemo switch for example) would be absolutely no different to flipping the switch on the back of the box, or pressing the power on the remote, it always seems to resumes to normal mode, I also notice no difference whatsoever in the power used between not-deep standby and On, this was my main reason for wanting WoL to work, Occasionally I get bored at work and if I can stream my TV that's good, but not so much that I want to waste money leaving the box on or in non-deep standby. The environment is also good though

 

[judge]

So therefore, turning the power off (with a wemo switch for example) would be absolutely no different to flipping the switch on the back of the box, or pressing the power on the remote

Using the remote to go to deep standby is completely different to cutting the power at source.
Cutting the power should really only be done when in deep standby mode first.

 

[ArowonA]

Maybe I didn't explain it well, my scenarios were all while in 'deep standby' I wasn't suggesting you just cut the power randomly.
I was just trying to say that while in deep standby, it wouldn't make a huge difference between pressing the power button and the power being cut and restored, both would leave the box on.

 

[judge]

Not fully sure what you mean either.
With the power cut off at source & turned on again at source, the box will boot into working E2.
So even if in deep standby, you cut the power, when you supply power again, it will boot into working E2.
Using ViX inbuilt power timers might help you if you want to cut & enable the power at source remotely.

 

[Rob van der Does]

Wow, is that deep standby vs. normal standby or vs. switched on? I guess there's not a lot of difference between the two latter modes.

The difference between 'on' and 'standby' is negligible.

Assume deep standby still wakes up for a timer recording?

Correct.

From what I can tell, and people please correct me if I'm wrong, "Deep standby" is basically shutdown, it just leaves the IR receiver activate.

Correct; it also leaves aon a clock (basically a 'ticker'), ticking seconds away until it's time for the next scheduled wake-up. Power consumption in deep is less then 0.5W.

I also notice no difference whatsoever in the power used between not-deep standby and On, this was my main reason for wanting WoL to work,

Don't we all

 

[Rob van der Does]

In ViX 3.2 the DUO2's WoL works again.

 

[ashhinton]

In ViX 3.2 the DUO2's WoL works again.

I can also confirm this is now working, it was one of the first things I tested after upgrading to ViX 3.2
Brilliant stuff, a big thank you to the ViX team.

Not sure if it was there before, but if anyone wonders whether it needs enabling look in the Network configuration settings and you will see WoL (Wake on Lan) as an option to enable or disable.

Now my settings are:

Power button (short press): standby.
EPG download: 4:00AM
Settings backup to USB: 5:00am
Power timer to deep standby: 5:30am

I suspect I'm leaving way to much time for each to complete, but ir does mean for most of the day (5:30am until around 7pm, sometimes later) its in deep standby. I expect I can increase the time its sucking the least electricity by another hour or so (EPG at 3am, Backup at 3:30am, Deep standby at 4am)

Most evenings its recording at least two or three shows, even if we're not there watching anything, so I accept the evening electricity usage as "would happen anyway"

 

[abu baniaz]

If your intention is to reduce energy usage/avoid wastage (very commendable), why the wake up at 4 am? Don't know why this has become customary amongst most users. The same for ABM too. There is no need to do so at that time, use a time slot fitting your usage/routine.

For example if receiver is not in use until kids come home at 3:45, time the process at 15:35 and 15:40.
A daily settings backup seems excessive to me. The only think that is likely to be of value is the timer.xml/autotimer. Autotimer populates timer, so once a week should be adequate. Most official channel changes for 28.2 are on Tuesday and Thursday. So Friday may be the best day to backup.

 

[ashhinton]

I seem to remember 4am being the default EPG download time when first setting up Cross EPG, something about it needing to tune to a particular transponder too - I guess if it couldn't (if all tuners were in use for watching live or recording) it would just wait until one of them became free.

If I really want an automated backup (autotimer.xml) I could background it during the evening - as it will run the moment the receiver gets power if it's been scheduled.

I'm thinking I'll do those changes, or at the very least get it to update the EPG early evening - we get in around 6-7pm, no kids one cat

Thanks again
Ashley

 

[mobileman]

intresting as just about to add another box along side my duo2, so may give this a bash, wonder if anyone has checked usage when connected to a smart meter device

taken from earlier in thread
Power consumption is 0.5W versus around 15-20W. So if a box is used for 6hrs a day that would come down to around 15W x 18hrs x 365 days = 100KWh per year.

100kwh on my providers tariff at the low use wattage figures above would save me £11-12 a year per box using WOL i really need to be a bit more green
as im terrible for leaving sky, pc, laptop, server, ps3, and few other devices in standby, should be easy enough for me to sort a fair few of them out

 

[Trial]

Hi mobileman,
you are lucking that you live in a "cheap" country. In Germany it can easily make up to €30/Year/Box.

ciao