* Add new preset to Tado to enable geofencing mode
Add new 'auto' preset mode to enable Tado to be set to auto geofencing
mode. The existing ‘home’ and ‘away’ presets switched Tado into manual
geofencing mode and there was no way to restore it to auto mode.
Note 1: Since preset modes (home, away and auto) apply to the Tado home
holistically, irrespective of the Tado climate entity used to select
the preset, three new sensors have been added to display the state of
the Tado home
Note 2: Auto mode is only supported if the Auto Assist skill is enabled
in the owner's Tado home. Various checks have been added to ensure the
Tado supports auto geofencing and if it is not supported, the preset is
not listed in the preset modes available
* Update codeowners in manifest.json
* Update main codeowners file for Tado component
* Get hostname id from get_settings
* Add try except in get_hostname_id function
* Update tests after adding get_hostname_id function
* Revert "Update tests after adding get_hostname_id function"
This reverts commit 5fa4e533cb.
* Add test for G2 models in config flow.
* Add test for helper module.
* Fix test for numbers.
* Revert "Add try except in get_hostname_id function"
This reverts commit 059f5bd9b4.
* Update variable name with known hostname ids to be private
---------
Co-authored-by: Stefan Gmeiner <stefangm42@gmail.com>
* airzone: climate: add Temperature range support
This is useful for HEAT_COOL climate mode (Airzone AUTO).
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* trigger CI
---------
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* Refactor zwave_js.sensor and add test coverage
* use walrus
* inherit config parameter class from list class
* use walrus in more places
* improve config parameter test
* Add change service
* test subtract
* Test no change if timer not running
* Modify example
* Raise
* Finalize
* test event
* Fix tests
* Fix tracking time
* Added new integration to support Electra Smart (HVAC)
* fixes + option to set scan interval
* renamed the module to electrasmart and added unittests
* added non tested files to .coveragerc
* changed the usage from UpdateCoordinator to each entity updates it self
* small fixes
* increased pypi package version, increased polling timeout to 60 seconds, improved error handling
* PARALLEL_UPDATE=1 to prevent multi access to the API
* code improvements
* aligned with the new HA APIs
* fixes
* fixes
* more
* fixes
* more
* more
* handled re-atuh flow
* fixed test
* removed hvac action
* added shabat mode
* tests: 100% coverage
* ran hassfest
* Update homeassistant/components/electrasmart/manifest.json
Co-authored-by: Shay Levy <levyshay1@gmail.com>
* Update homeassistant/components/electrasmart/manifest.json
Co-authored-by: Shay Levy <levyshay1@gmail.com>
* Update homeassistant/components/electrasmart/manifest.json
Co-authored-by: Shay Levy <levyshay1@gmail.com>
* Update homeassistant/components/electrasmart/climate.py
Co-authored-by: Shay Levy <levyshay1@gmail.com>
* address Shay's comments
* address Shay's comments
* address more comments
---------
Co-authored-by: Shay Levy <levyshay1@gmail.com>
* init commit
* use official version release
* remove options
* moved first refresh to gather
* add extra tests
* remove model_sepcification
* remove old mqtt test
* bump to 13.4
* fix dndtimer
* bump to 14.1
* add status back
* bump to 17.0
* remove error as it is not used
* addressing mr comments
* making enum access use get()
* add check for empty hass data
* Add always connected option to Yale Access Bluetooth
If the lock does not support push updates via advertisements or you want lock operation to be more responsive, you can enable always connected mode. Always connected will cause the lock to stay connected to Home Assistant via Bluetooth, which will use more battery.
* Update homeassistant/components/yalexs_ble/config_flow.py
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
---------
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
* Update UpCloud config entry data on successful reconfig
* Add already configured test
* Improve success case request mocking
So that the data fetch that might happen in the background after success
won't trash the test log with misleading errors.
* Simplify already configured test
Thanks-to: Martin Hjelmare <marhje52@gmail.com>
* remove impossible test
IndividualAddress telegrams are not processed by xknx.telegram_queue
* Use Telegrams helper class for group monitor messages
* Store 50 telegrams in deque for group monitor
* Send recent telegrams at once on connection of group monitor
* Update KNX-frontend to support group monitor prepopulation
* Copy openai_conversation to google_generative_ai_conversation
This is to improve diff of the next commit with the actual implementation.
Commands used:
cp -r homeassistant/components/openai_conversation/ homeassistant/components/google_generative_ai_conversation/
cp -r tests/components/openai_conversation/ tests/components/google_generative_ai_conversation/
find homeassistant/components/google_generative_ai_conversation/ tests/components/google_generative_ai_conversation/ -type f | xargs sed -i \
-e 's@openai_conversation@google_generative_ai_conversation@g' \
-e 's@OpenAI Conversation@Google Generative AI Conversation@g' \
-e 's@balloob@tronikos@g'
* Add google_generative_ai_conversation to Google brand
* Google Generative AI Conversation
* Sync recent openai changes
* handle empty responses
* telegram device trigger initial
* add Telegrams helper class
to parse and convert Telegram only once instead of once per device trigger
* translation
* label for extra_field
* test device trigger
* test trigger callback removal
* rename extra_field key to same name as used in trigger
* typo
