Confirm a working awake baseline
With the device on, identify its model and software under Settings, System, About and check it against Roku’s current AirPlay support information. Confirm the Apple sender and receiver use the intended network. A working awake connection gives you a different starting point from a device that never appears.
Then note whether the device becomes absent only after entering standby. Keep the product type explicit: Roku’s guidance distinguishes integrated televisions and Streambar from streaming players, whose normal power and network context can differ. Do not apply a television’s power menu to every external player.
Inspect the appropriate standby feature
Roku’s support describes Settings, System, Power, then Fast TV start for a television or Fast start for Streambar. It says these features maintain the network path needed for AirPlay or HomeKit to reach the device while it is off.
The same guidance notes increased power use and an override of normal standby settings. Choose the state that matches your intended remote-wake behaviour, rather than treating it as a mandatory playback repair. Keep the previous setting so the household can restore its preferred standby behaviour after the comparison.
Separate wake control from programme playback
After changing a supported setting, compare whether the receiver remains discoverable in standby. If it does but a particular programme still cannot play, that is a later source-application or media question. Discovering the receiver does not establish permission or compatibility for every programme.
For HomeKit power control through an external Roku player or Streambar, Roku also documents television HDMI-CEC and 1-touch play requirements. Record whether the failing task is discovery, waking the TV or actual playback. Those separate results prevent a working AirPlay receiver from being diagnosed solely through an unrelated television-power command.