Controller takes far too long to wake up, how to stop it?

[Mnyb]

If the controller is taking a long time to contact the router then this would seem to be the DHCP protocol, as fixed IP adapters (certainly wireless ones) connect instantly.

I know nothing about the controller's internal setup, but is it possible to assign it a fixed IP address? Mine runs in this state in effect, because its MAC address has a reserved DHCP address, but it still goes through the DHCP "conversation". The point being that my router would be no worse off for having this "always on" device run with an actual fixed IP address.

Yes it can have true static ip easiest way is to edit the etc/network/interfaces file on it

Example replace ssid with your network name and choose other ip's as you wish:

auto lo

iface lo inet loopback

mapping eth0
	script /etc/network/if_mapping
auto eth0=ssid
iface Liogor inet static
	address 192.168.0.6
	network 192.168.0.0
	broadcast 192.168.1.255
	netmask 255.255.255.0
	gateway 192.168.0.1
	dns 192.168.0.1
	up echo 'nameserver 192.168.0.1' > /etc/resolv.conf

[Owen Smith]

Thanks, I'll look at those when I'm back at home in a few days. I suspect Suspend (ie. Deep Sleep) is the one I want to disable.

It turns out that disabling Suspend and disabling Wireless Power Saving did the job. Screen turns on and displays stuff in the time from me picking it up to being able to read it. Normal sleep and display dimming/off doesn't appear to be a problem at all so I've left those enabled.

I also enabled screen dimming in the charger, this means I can leave the controller on all the time in the charger and not have to wait ages for it to switch on.

Thanks for the advice.