“… to 10%.”
Maybe the endpoint detection had just engaged after the delay before “to 10%”. The result? Volume was set to 10 — the maximum level for the Echo Show. Tchaikovsky blared through the house, injecting a lot of energy at bedtime.
Endpoint is a fickle thing. However, requesting the maximum volume doesn’t happen that often and a false acceptance has a larger negative impact than a false rejection of the command.
Maybe there’s a way to add some safeguard or at least a bias against inadvertent commands to pump up the volume?