This project is mirrored from https://github.com/home-assistant/core.git.
Pull mirroring updated .
- Feb 13, 2021
-
-
Álvaro Fernández Rojas authored
Co-authored-by:
Martin Hjelmare <marhje52@gmail.com>
-
J. Nick Koston authored
Changes: https://github.com/ikalchev/HAP-python/compare/v3.2.0...v3.3.0
-
Shay Levy authored
-
Shay Levy authored
-
Rob Bierbooms authored
-
- Feb 12, 2021
-
-
Maciej Bieniek authored
-
Franck Nijhof authored
-
Christophe Painchaud authored
RFLink compoment when used over TCP protocol suffers a major issue : it doesn't know when connection is timeout or lost because there is no keepalive mechanism so it can stay disconnected forever. I wrote a small patch for the underlying 'python-rflink' library which will enable TCP KEEPPAlive. On HASSIO side it will just add an optional argument in yml file which will propagate to python-rflink caller.
-
- Feb 11, 2021
-
-
Joakim Plate authored
* Add config flow to philips_js * Adjust name of entry to contain serial * Use device id in event rather than entity id * Adjust turn on text * Deprecate all fields * Be somewhat more explicit in typing * Switch to direct coordinator access * Refactor the pluggable action * Adjust tests a bit * Minor adjustment * More adjustments * Add missing await in update coordinator * Be more lenient to lack of system info * Use constant for trigger type and simplify * Apply suggestions from code review Co-authored-by:
J. Nick Koston <nick@koston.org> Co-authored-by:
J. Nick Koston <nick@koston.org>
-
- Feb 10, 2021
-
-
ehendrix23 authored
Co-authored-by:
J. Nick Koston <nick@koston.org>
-
J. Nick Koston authored
Co-authored-by:
badguy99 <61918526+badguy99@users.noreply.github.com>
-
J. Nick Koston authored
-
Erik Montnemery authored
-
Leonardo Figueiro authored
Co-authored-by:
J. Nick Koston <nick@koston.org>
-
Alan Tse authored
-
Franck Nijhof authored
-
Erik Montnemery authored
-
Shay Levy authored
-
uvjustin authored
-
Greg Dowling authored
-
- Feb 09, 2021
-
-
Khole authored
* Convert Hive to Async * Update Refresh System * Update load platform to Async * Changes from review feedback * Review Round 2 * Updated service * Updated dict keys * Convert Hive to Async * Update Refresh System * Update load platform to Async * Changes from review feedback * Review Round 2 * Updated service * Updated dict keys * Convert Hive to Async * Update Refresh System * Update load platform to Async * Changes from review feedback * Review Round 2 * Updated service * Updated dict keys * Updated Refresh System
-
bsmappee authored
-
J. Nick Koston authored
-
- Feb 08, 2021
-
-
Bram Kragten authored
-
Greg Dowling authored
-
Fabian Affolter authored
-
Hmmbob authored
-
Per Sandström authored
-
Fabian Affolter authored
-
- Feb 07, 2021
-
-
Matthias Alphart authored
-
- Feb 06, 2021
-
-
ehendrix23 authored
-
- Feb 05, 2021
-
-
functionpointer authored
* MySensors: Add type annotations Adds a bunch of type annotations that were created while understanding the code. * MySensors: Change GatewayId to string In preparation for config flow. The GatewayId used to be id(gateway). With config flows, every gateway will have its own ConfigEntry. Every ConfigEntry has a unique id. Thus we would have two separate but one-to-one related ID systems. This commit removes this unneeded duplication by using the id of the ConfigEntry as GatewayId. * MySensors: Add unique_id to all entities This allows entities to work well with the frontend. * MySensors: Add device_info to all entities Entities belonging to the same node_id will now by grouped as a device. * MySensors: clean up device.py a bit * MySensors: Add config flow support With this change the MySensors can be fully configured from the GUI. Legacy configuration.yaml configs will be migrated by reading them once. Note that custom node names are not migrated. Users will have to re-enter the names in the front-end. Since there is no straight-forward way to configure global settings, all previously global settings are now per-gateway. These settings include: - MQTT retain - optimistic - persistence enable - MySensors version When a MySensors integration is loaded, it works as follows: 1. __init__.async_setup_entry is called 2. for every platform, async_forward_entry_setup is called 3. the platform's async_setup_entry is called 4. __init__.setup_mysensors_platform is called 5. the entity's constructor (e.g. MySensorsCover) is called 6. the created entity is stored in a dict in the hass object * MySensors: Fix linter errors * MySensors: Remove unused import * MySensors: Feedback from @MartinHjelmare * MySensors: Multi-step config flow * MySensors: More feedback * MySensors: Move all storage in hass object under DOMAIN The integration now stores everything under hass.data["mysensors"] instead of using several top level keys. * MySensors: await shutdown of gateway instead of creating a task * MySensors: Rename Ethernet to TCP * MySensors: Absolute imports and cosmetic changes * MySensors: fix gw_stop * MySensors: Allow user to specify persistence file * MySensors: Nicer log message * MySensors: Add lots of unit tests * MySensors: Fix legacy import of persistence file name Turns out tests help to find bugs :D * MySensors: Improve test coverage * MySensors: Use json persistence files by default * MySensors: Code style improvements * MySensors: Stop adding attributes to existing objects This commit removes the extra attributes that were being added to the gateway objects from pymysensors. Most attributes were easy to remove, except for the gateway id. The MySensorsDevice class needs the gateway id as it is part of its DevId as well as the unique_id and device_info. Most MySensorsDevices actually end up being Entities. Entities have access to their ConfigEntry via self.platform.config_entry. However, the device_tracker platform does not become an Entity. For this reason, the gateway id is not fetched from self.plaform but given as an argument. Additionally, MySensorsDevices expose the address of the gateway (CONF_DEVICE). Entities can easily fetch this information via self.platform, but the device_tracker cannot. This commit chooses to remove the gateway address from device_tracker. While this could in theory break some automations, the simplicity of this solution was deemed worth it. The alternative of adding the entire ConfigEntry as an argument to MySensorsDevices is not viable, because device_tracker is initialized by the async_setup_scanner function that isn't supplied a ConfigEntry. It only gets discovery_info. Adding the entire ConfigEntry doesn't seem appropriate for this edge case. * MySensors: Fix gw_stop and the translations * MySensors: Fix incorrect function calls * MySensors: Fewer comments in const.py * MySensors: Remove union from _get_gateway and remove id from try_connect * MySensors: Deprecate nodes option in configuration.yaml * MySensors: Use version parser from packaging * MySensors: Remove prefix from unique_id and change some private property names * MySensors: Change _get_gateway function signature * MySensors: add packaging==20.8 for the version parser * MySensors: Rename some stuff * MySensors: use pytest.mark.parametrize * MySensors: Clean up test cases * MySensors: Remove unneeded parameter from devices * Revert "MySensors: add packaging==20.8 for the version parser" This reverts commit 6b200ee01a3c0eee98176380bdd0b73e5a25b2dd. * MySensors: Use core interface for testing configuration.yaml import * MySensors: Fix test_init * MySensors: Rename a few variables * MySensors: cosmetic changes * MySensors: Update strings.json * MySensors: Still more feedback from @MartinHjelmare * MySensors: Remove unused strings Co-authored-by:
Martin Hjelmare <marhje52@gmail.com> * MySensors: Fix typo and remove another unused string * MySensors: More strings.json * MySensors: Fix gateway ready handler * MySensors: Add duplicate detection to config flows * MySensors: Deal with non-existing topics and ports. Includes unit tests for these cases. * MySensors: Use awesomeversion instead of packaging * Add string already_configured * MySensors: Abort config flow when config is found to be invalid while importing * MySensors: Copy all error messages to also be abort messages All error strings may now also be used as an abort reason, so the strings should be defined * Use string references Co-authored-by:
Martin Hjelmare <marhje52@gmail.com>
-
- Feb 04, 2021
-
-
Fabian Affolter authored
-
Fabian Affolter authored
-
Fabian Affolter authored
-
Martin Hjelmare authored
-
Martin Hjelmare authored
-
Martin Weinelt authored
This can get unnecessarily spammy and doesn't represent an actual actionable issue. Fixes: #45235
-
- Feb 03, 2021
-
-
Niccolo Zapponi authored
* Add support for iCloud 2FA * Updated dependency for iCloud * Updated dependency and logic fix * Added logic for handling incorrect 2FA code * Bug fix on failing test * Added myself to codeowners * Added check for 2FA on setup * Updated error message
-
Brandon Rothweiler authored
-