Not sure I agree, if the player was 'off' it should remain off.  In what cases where you able to cause it to not resume when it reconnected after power cycle?

Steven and I chatted with Matt C on this. The usage scenario expected is that the player will resume play upon power interruption, such as power outage or being turned off at night.

It is expected that the user will never press play on the remote -- ever.

Let's say there is a power outage in the middle of the night and the player was off for the night.  When the player comes back it will remain off.  The next morning, someone will press power and it will begin playing again.

The concern is if the remote goes missing, ends up in a happy meal or something, while the player was in an off state there is no other easy way to get the stream playing again.  So it really comes down to what is more important to an io4business customer, that the player stays off when the unit is power cycled or power cycling allows the stream to play when the remote has gone missing.

I am not sure it's possible to implement that without also making the player auto-start when it is off and gets bumped to another server during the daily server restart.  This means it will probably start playing in the middle of the night often.  I don't agree it should work like that.  I think we can expect them not to lose the remote.  If they lose the remote, they can call RadioIO support who can start the player from the SN web UI if needed, and overnight them a new remote.

Moving bugs as this product category will be removed from Bugzilla