* CHG: use TemperatureControl trait to report sensor
* fixup: blacked
* fixup: flaked
* fixup: flaked
* Adjust tests
* fixup test and rebase
* test coverage
* Set command only cover
* No need for override position now that we support command only
* Return empty state response for assumed state
Fixes#43178
Reverts: #23498
Co-authored-by: Paulus Schoutsen <paulus@home-assistant.io>
* Use http status codes and add HTTP_BAD_GATEWAY constant
* Address review comments:
- using constants in tado integration
- using constant in media_player init.py
* Add and use HTTP_ACCEPTED constant
* Make sure we set discreteOnlyOpenClose for binary sensors
* Mark switches that are assumed state as commandOnlyOnOff
* Drop stray extra line
* Fix pylint error
Co-authored-by: springstan <46536646+springstan@users.noreply.github.com>
Support the action.devices.commands.mute intent to mute and unmute
media_players that declare support for mute/unmute.
For media players with support for volume up/down, but no support for
setting the volume to a specific number, allow use of the
action.devices.commands.relativeMute intent to control volume up/down.
This will improve support for IR blasters and other open-loop
media_player integrations.
* Don't set SUPPORT_EFFECT on DemoLight if there are no effects
This requires an update to the group test - previously the other lights
instantiated by the DemoLight component had nothing in ATTR_EFFECT_LIST, but
still had SUPPORT_EFFECT set. This appears to have resulted in the light
group test code setting an effect on the group and expecting it to apply to
all lights, but given that two of the bulbs didn't actually support any
effects (due to the empty ATTR_EFFECT_LIST) this seems like a broken
assumption and updating the test to verify only the bulb that supports
effects has had one applied seems reasonable.
* Add support for exposing light effects via Google Assistant
The LightEffects trait only supports a fixed (and small) list of lighting
effects, but we can expose them via the Modes trait - this requires saying
"Set (foo) effect to (bar)" which is a little clumsy, but at least makes it
possible.
* Support Next/Previous for InputSelector
* Update homeassistant/components/google_assistant/trait.py
Co-authored-by: Paulus Schoutsen <paulus@home-assistant.io>
* Adjust to match new version of _next_selected
Co-authored-by: Paulus Schoutsen <paulus@home-assistant.io>
Franck Nijhof
Ville Skyttä
Jan Bouwhuis
Paul Bottein
Michael
tkdrob
Paulus Schoutsen
Bram Kragten
Chris Browet
Erik Montnemery
Marc Mueller
Tobias Haber
Joakim Plate
J. Nick Koston
Dror Eiger
Hmmbob
edomat
springstan
Justin Paupore
Matthew Garrett
Marcio Granzotto Rodrigues