Adjust device_automation type hints in netatmo (#72136)
-
Adjust device_automation type hints in netatmo
-
Improve type hints
Pinned
bdraco/addon_securityadvisor
16
⚡ Old Security Advisor for cPanel 11.40 (upstream repo) -- Use CPANELINC/addon_securityadvisor
bdraco/aiosenseme
12
⚡ SenseME by Big Ass Fans asynchronous Python library
bdraco/yalexs
9
⚡ Python API for Yale Access (formerly August) Smart Lock and Doorbell
bdraco/nexia
7
⚡ Python library for connecting to nexia
bdraco/dovecot
4
bdraco/powerwall
3
⚡ Updated powerwall integration for HASS
Activity
May
20
23 hours ago
bdraco push bdraco/home-assistant
bdraco
bdraco
Move manual configuration of MQTT alarm control panel to the integration key (#72165)
Add alarm_control_panel
bdraco
Adjust device_automation type hints in arcam_fmj (#72193)
bdraco
Adjust setup type hints in mqtt (#72227)
bdraco
Fix Shelly missing key config flow (#72116)
bdraco
Adjust setup type hints in agent_dvr (#72224)
bdraco
Fix for Xiaomi miio fan speed (#72027)
Update fan.py
bdraco
Include context state in logbook responses to improve localization (#72222)
-
Include context state in logbook responses to improve localization
-
reduce payload, dont send context_event_type if sending context_state
bdraco
Cleanup nest async methods that do not need to actually await (#72170)
Co-authored-by: epenet [email protected]
bdraco
Bump plexapi to 4.11.1 (#72121)
bdraco
Add support for cover positions in bond (#72180)
bdraco
Bump gcal_sync to 0.9.0 (#72237)
bdraco
Add yolink sensors (#72186)
-
Add more sensor support
-
change codeowner to active account
-
fix suggest
bdraco
Fix reauthentication for powerwall integration (#72174)
bdraco
bdraco
bdraco
bdraco
Merge branch 'logbook_stream' into integration
commit sha： 2f7b252e83ec41765b5ebb6c568d617e7e184e64
push time in 1 hour agobdraco wants to merge home-assistant/home-assistant.io
bdraco
bdraco
CONTRIBUTOR
createdAt 2 hours ago
Adds docs for UP Chime support
Proposed change
Type of change
- Spelling, grammar or other readability improvements (
currentbranch). - Adjusted missing or incorrect information in the current documentation (
currentbranch). - Added documentation for a new integration I'm adding to Home Assistant (
nextbranch).- I've opened up a PR to add logo's and icons in Brands repository.
- Added documentation for a new feature I'm adding to Home Assistant (
nextbranch). - Removed stale or deprecated documentation.
Additional information
- Link to parent pull request in the codebase: https://github.com/home-assistant/core/pull/71874
- Link to parent pull request in the Brands repository:
- This PR fixes or closes issue: fixes #
Checklist
- This PR uses the correct branch, based on one of the following:
- I made a change to the existing documentation and used the
currentbranch. - I made a change that is related to an upcoming version of Home Assistant and used the
nextbranch.
- I made a change to the existing documentation and used the
- The documentation follows the Home Assistant documentation standards.
bdraco
* **Device Configuration** - Smart chimes will get a volume slider to adjust the chime's loudness and a sensor for the last time the chime rang.
bdraco merge to home-assistant/home-assistant.io
bdraco
bdraco
CONTRIBUTOR
createdAt 2 hours ago
Adds docs for UP Chime support
Proposed change
Type of change
- Spelling, grammar or other readability improvements (
currentbranch). - Adjusted missing or incorrect information in the current documentation (
currentbranch). - Added documentation for a new integration I'm adding to Home Assistant (
nextbranch).- I've opened up a PR to add logo's and icons in Brands repository.
- Added documentation for a new feature I'm adding to Home Assistant (
nextbranch). - Removed stale or deprecated documentation.
Additional information
- Link to parent pull request in the codebase: https://github.com/home-assistant/core/pull/71874
- Link to parent pull request in the Brands repository:
- This PR fixes or closes issue: fixes #
Checklist
- This PR uses the correct branch, based on one of the following:
- I made a change to the existing documentation and used the
currentbranch. - I made a change that is related to an upcoming version of Home Assistant and used the
nextbranch.
- I made a change to the existing documentation and used the
- The documentation follows the Home Assistant documentation standards.
bdraco
bdraco
MEMBER
submittedAt 2 hours ago
bdraco wants to merge home-assistant/home-assistant.io
bdraco
bdraco
CONTRIBUTOR
createdAt 2 hours ago
Adds docs for UP Chime support
Proposed change
Type of change
- Spelling, grammar or other readability improvements (
currentbranch). - Adjusted missing or incorrect information in the current documentation (
currentbranch). - Added documentation for a new integration I'm adding to Home Assistant (
nextbranch).- I've opened up a PR to add logo's and icons in Brands repository.
- Added documentation for a new feature I'm adding to Home Assistant (
nextbranch). - Removed stale or deprecated documentation.
Additional information
- Link to parent pull request in the codebase: https://github.com/home-assistant/core/pull/71874
- Link to parent pull request in the Brands repository:
- This PR fixes or closes issue: fixes #
Checklist
- This PR uses the correct branch, based on one of the following:
- I made a change to the existing documentation and used the
currentbranch. - I made a change that is related to an upcoming version of Home Assistant and used the
nextbranch.
- I made a change to the existing documentation and used the
- The documentation follows the Home Assistant documentation standards.
bdraco
* **Button** - A button to trigger the chime manually for each smart chime device. Also, a disabled by default button is added to let you reboot your smart chime device.
bdraco merge to home-assistant/home-assistant.io
bdraco
bdraco
CONTRIBUTOR
createdAt 2 hours ago
Adds docs for UP Chime support
Proposed change
Type of change
- Spelling, grammar or other readability improvements (
currentbranch). - Adjusted missing or incorrect information in the current documentation (
currentbranch). - Added documentation for a new integration I'm adding to Home Assistant (
nextbranch).- I've opened up a PR to add logo's and icons in Brands repository.
- Added documentation for a new feature I'm adding to Home Assistant (
nextbranch). - Removed stale or deprecated documentation.
Additional information
- Link to parent pull request in the codebase: https://github.com/home-assistant/core/pull/71874
- Link to parent pull request in the Brands repository:
- This PR fixes or closes issue: fixes #
Checklist
- This PR uses the correct branch, based on one of the following:
- I made a change to the existing documentation and used the
currentbranch. - I made a change that is related to an upcoming version of Home Assistant and used the
nextbranch.
- I made a change to the existing documentation and used the
- The documentation follows the Home Assistant documentation standards.
bdraco
bdraco
MEMBER
submittedAt 2 hours ago
bdraco pull request home-assistant/core
bdraco
bdraco
CONTRIBUTOR
createdAt 3 hours ago
Adds UP Chime support for UniFi Protect
Proposed change
Adds support for the new UP Chime devices for UniFi Protect
- Number entity for UP Chime devices
- Button to trigger Chime playback
- Button to trigger Chime buzzer playback
- Last Ring sensor for the last time the Chime was activate
- A new service,
set_chime_paired_doorbellsthat lets your pair doorbells to a chime (this will make if so if the doorbell rings, the chime will also ring)- This service is basically an implemention of a "multi-select", if the select platform ever supports multi-select, the service can be removed and replaced
Images
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New integration (thank you!)
- New feature (which adds functionality to an existing integration)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/22754
Checklist
- The code change is tested and works locally.
- Local tests pass. Your PR cannot be merged unless tests pass
- There is no commented out code in this PR.
- I have followed the development checklist
- The code has been formatted using Black (
black --fast homeassistant tests) - Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
If the code communicates with devices, web services, or third-party tools:
- The manifest file has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- Untested files have been added to
.coveragerc.
The integration reached or maintains the following Integration Quality Scale:
- No score or internal
- 🥈 Silver
- 🥇 Gold
- 🏆 Platinum
To help with the load of incoming pull requests:
- I have reviewed two other open pull requests in this repository.
bdraco merge to home-assistant/core
bdraco
bdraco
CONTRIBUTOR
createdAt 3 hours ago
Adds UP Chime support for UniFi Protect
Proposed change
Adds support for the new UP Chime devices for UniFi Protect
- Number entity for UP Chime devices
- Button to trigger Chime playback
- Button to trigger Chime buzzer playback
- Last Ring sensor for the last time the Chime was activate
- A new service,
set_chime_paired_doorbellsthat lets your pair doorbells to a chime (this will make if so if the doorbell rings, the chime will also ring)- This service is basically an implemention of a "multi-select", if the select platform ever supports multi-select, the service can be removed and replaced
Images
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New integration (thank you!)
- New feature (which adds functionality to an existing integration)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/22754
Checklist
- The code change is tested and works locally.
- Local tests pass. Your PR cannot be merged unless tests pass
- There is no commented out code in this PR.
- I have followed the development checklist
- The code has been formatted using Black (
black --fast homeassistant tests) - Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
If the code communicates with devices, web services, or third-party tools:
- The manifest file has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- Untested files have been added to
.coveragerc.
The integration reached or maintains the following Integration Quality Scale:
- No score or internal
- 🥈 Silver
- 🥇 Gold
- 🏆 Platinum
To help with the load of incoming pull requests:
- I have reviewed two other open pull requests in this repository.
bdraco
bdraco
MEMBER
submittedAt 3 hours ago
Looks good
bdraco wants to merge home-assistant/core
bdraco
bdraco
CONTRIBUTOR
createdAt 3 hours ago
Adds UP Chime support for UniFi Protect
Proposed change
Adds support for the new UP Chime devices for UniFi Protect
- Number entity for UP Chime devices
- Button to trigger Chime playback
- Button to trigger Chime buzzer playback
- Last Ring sensor for the last time the Chime was activate
- A new service,
set_chime_paired_doorbellsthat lets your pair doorbells to a chime (this will make if so if the doorbell rings, the chime will also ring)- This service is basically an implemention of a "multi-select", if the select platform ever supports multi-select, the service can be removed and replaced
Images
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New integration (thank you!)
- New feature (which adds functionality to an existing integration)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/22754
Checklist
- The code change is tested and works locally.
- Local tests pass. Your PR cannot be merged unless tests pass
- There is no commented out code in this PR.
- I have followed the development checklist
- The code has been formatted using Black (
black --fast homeassistant tests) - Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
If the code communicates with devices, web services, or third-party tools:
- The manifest file has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- Untested files have been added to
.coveragerc.
The integration reached or maintains the following Integration Quality Scale:
- No score or internal
- 🥈 Silver
- 🥇 Gold
- 🏆 Platinum
To help with the load of incoming pull requests:
- I have reviewed two other open pull requests in this repository.
bdraco
camera = instance.bootstrap.cameras[doorbell_ufp_device_id]
bdraco merge to home-assistant/core
bdraco
bdraco
CONTRIBUTOR
createdAt 3 hours ago
Adds UP Chime support for UniFi Protect
Proposed change
Adds support for the new UP Chime devices for UniFi Protect
- Number entity for UP Chime devices
- Button to trigger Chime playback
- Button to trigger Chime buzzer playback
- Last Ring sensor for the last time the Chime was activate
- A new service,
set_chime_paired_doorbellsthat lets your pair doorbells to a chime (this will make if so if the doorbell rings, the chime will also ring)- This service is basically an implemention of a "multi-select", if the select platform ever supports multi-select, the service can be removed and replaced
Images
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New integration (thank you!)
- New feature (which adds functionality to an existing integration)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/22754
Checklist
- The code change is tested and works locally.
- Local tests pass. Your PR cannot be merged unless tests pass
- There is no commented out code in this PR.
- I have followed the development checklist
- The code has been formatted using Black (
black --fast homeassistant tests) - Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
If the code communicates with devices, web services, or third-party tools:
- The manifest file has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- Untested files have been added to
.coveragerc.
The integration reached or maintains the following Integration Quality Scale:
- No score or internal
- 🥈 Silver
- 🥇 Gold
- 🏆 Platinum
To help with the load of incoming pull requests:
- I have reviewed two other open pull requests in this repository.
bdraco
bdraco
MEMBER
submittedAt 3 hours ago
bdraco wants to merge home-assistant/core
bdraco
bdraco
CONTRIBUTOR
createdAt 3 hours ago
Adds UP Chime support for UniFi Protect
Proposed change
Adds support for the new UP Chime devices for UniFi Protect
- Number entity for UP Chime devices
- Button to trigger Chime playback
- Button to trigger Chime buzzer playback
- Last Ring sensor for the last time the Chime was activate
- A new service,
set_chime_paired_doorbellsthat lets your pair doorbells to a chime (this will make if so if the doorbell rings, the chime will also ring)- This service is basically an implemention of a "multi-select", if the select platform ever supports multi-select, the service can be removed and replaced
Images
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New integration (thank you!)
- New feature (which adds functionality to an existing integration)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/22754
Checklist
- The code change is tested and works locally.
- Local tests pass. Your PR cannot be merged unless tests pass
- There is no commented out code in this PR.
- I have followed the development checklist
- The code has been formatted using Black (
black --fast homeassistant tests) - Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
If the code communicates with devices, web services, or third-party tools:
- The manifest file has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- Untested files have been added to
.coveragerc.
The integration reached or maintains the following Integration Quality Scale:
- No score or internal
- 🥈 Silver
- 🥇 Gold
- 🏆 Platinum
To help with the load of incoming pull requests:
- I have reviewed two other open pull requests in this repository.
bdraco
doorbell_ufp_device_id = _async_unique_id_to_ufp_device_id(doorbell_sensor.unique_id)
bdraco merge to home-assistant/core
bdraco
bdraco
CONTRIBUTOR
createdAt 3 hours ago
Adds UP Chime support for UniFi Protect
Proposed change
Adds support for the new UP Chime devices for UniFi Protect
- Number entity for UP Chime devices
- Button to trigger Chime playback
- Button to trigger Chime buzzer playback
- Last Ring sensor for the last time the Chime was activate
- A new service,
set_chime_paired_doorbellsthat lets your pair doorbells to a chime (this will make if so if the doorbell rings, the chime will also ring)- This service is basically an implemention of a "multi-select", if the select platform ever supports multi-select, the service can be removed and replaced
Images
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New integration (thank you!)
- New feature (which adds functionality to an existing integration)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/22754
Checklist
- The code change is tested and works locally.
- Local tests pass. Your PR cannot be merged unless tests pass
- There is no commented out code in this PR.
- I have followed the development checklist
- The code has been formatted using Black (
black --fast homeassistant tests) - Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
If the code communicates with devices, web services, or third-party tools:
- The manifest file has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- Untested files have been added to
.coveragerc.
The integration reached or maintains the following Integration Quality Scale:
- No score or internal
- 🥈 Silver
- 🥇 Gold
- 🏆 Platinum
To help with the load of incoming pull requests:
- I have reviewed two other open pull requests in this repository.
bdraco
bdraco
MEMBER
submittedAt 3 hours ago
bdraco wants to merge home-assistant/core
bdraco
bdraco
CONTRIBUTOR
createdAt 3 hours ago
Adds UP Chime support for UniFi Protect
Proposed change
Adds support for the new UP Chime devices for UniFi Protect
- Number entity for UP Chime devices
- Button to trigger Chime playback
- Button to trigger Chime buzzer playback
- Last Ring sensor for the last time the Chime was activate
- A new service,
set_chime_paired_doorbellsthat lets your pair doorbells to a chime (this will make if so if the doorbell rings, the chime will also ring)- This service is basically an implemention of a "multi-select", if the select platform ever supports multi-select, the service can be removed and replaced
Images
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New integration (thank you!)
- New feature (which adds functionality to an existing integration)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/22754
Checklist
- The code change is tested and works locally.
- Local tests pass. Your PR cannot be merged unless tests pass
- There is no commented out code in this PR.
- I have followed the development checklist
- The code has been formatted using Black (
black --fast homeassistant tests) - Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
If the code communicates with devices, web services, or third-party tools:
- The manifest file has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- Untested files have been added to
.coveragerc.
The integration reached or maintains the following Integration Quality Scale:
- No score or internal
- 🥈 Silver
- 🥇 Gold
- 🏆 Platinum
To help with the load of incoming pull requests:
- I have reviewed two other open pull requests in this repository.
bdraco
def _async_unique_id_to_ufp_device_id(unique_id: str) -> str:
bdraco merge to home-assistant/core
bdraco
bdraco
CONTRIBUTOR
createdAt 3 hours ago
Adds UP Chime support for UniFi Protect
Proposed change
Adds support for the new UP Chime devices for UniFi Protect
- Number entity for UP Chime devices
- Button to trigger Chime playback
- Button to trigger Chime buzzer playback
- Last Ring sensor for the last time the Chime was activate
- A new service,
set_chime_paired_doorbellsthat lets your pair doorbells to a chime (this will make if so if the doorbell rings, the chime will also ring)- This service is basically an implemention of a "multi-select", if the select platform ever supports multi-select, the service can be removed and replaced
Images
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New integration (thank you!)
- New feature (which adds functionality to an existing integration)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/22754
Checklist
- The code change is tested and works locally.
- Local tests pass. Your PR cannot be merged unless tests pass
- There is no commented out code in this PR.
- I have followed the development checklist
- The code has been formatted using Black (
black --fast homeassistant tests) - Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
If the code communicates with devices, web services, or third-party tools:
- The manifest file has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- Untested files have been added to
.coveragerc.
The integration reached or maintains the following Integration Quality Scale:
- No score or internal
- 🥈 Silver
- 🥇 Gold
- 🏆 Platinum
To help with the load of incoming pull requests:
- I have reviewed two other open pull requests in this repository.
bdraco
bdraco
MEMBER
submittedAt 3 hours ago
bdraco wants to merge home-assistant/core
bdraco
bdraco
CONTRIBUTOR
createdAt 3 hours ago
Adds UP Chime support for UniFi Protect
Proposed change
Adds support for the new UP Chime devices for UniFi Protect
- Number entity for UP Chime devices
- Button to trigger Chime playback
- Button to trigger Chime buzzer playback
- Last Ring sensor for the last time the Chime was activate
- A new service,
set_chime_paired_doorbellsthat lets your pair doorbells to a chime (this will make if so if the doorbell rings, the chime will also ring)- This service is basically an implemention of a "multi-select", if the select platform ever supports multi-select, the service can be removed and replaced
Images
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New integration (thank you!)
- New feature (which adds functionality to an existing integration)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/22754
Checklist
- The code change is tested and works locally.
- Local tests pass. Your PR cannot be merged unless tests pass
- There is no commented out code in this PR.
- I have followed the development checklist
- The code has been formatted using Black (
black --fast homeassistant tests) - Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
If the code communicates with devices, web services, or third-party tools:
- The manifest file has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- Untested files have been added to
.coveragerc.
The integration reached or maintains the following Integration Quality Scale:
- No score or internal
- 🥈 Silver
- 🥇 Gold
- 🏆 Platinum
To help with the load of incoming pull requests:
- I have reviewed two other open pull requests in this repository.
bdraco
chime = instance.bootstrap.chimes[chime_ufp_device_id]
bdraco merge to home-assistant/core
bdraco
bdraco
CONTRIBUTOR
createdAt 3 hours ago
Adds UP Chime support for UniFi Protect
Proposed change
Adds support for the new UP Chime devices for UniFi Protect
- Number entity for UP Chime devices
- Button to trigger Chime playback
- Button to trigger Chime buzzer playback
- Last Ring sensor for the last time the Chime was activate
- A new service,
set_chime_paired_doorbellsthat lets your pair doorbells to a chime (this will make if so if the doorbell rings, the chime will also ring)- This service is basically an implemention of a "multi-select", if the select platform ever supports multi-select, the service can be removed and replaced
Images
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New integration (thank you!)
- New feature (which adds functionality to an existing integration)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/22754
Checklist
- The code change is tested and works locally.
- Local tests pass. Your PR cannot be merged unless tests pass
- There is no commented out code in this PR.
- I have followed the development checklist
- The code has been formatted using Black (
black --fast homeassistant tests) - Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
If the code communicates with devices, web services, or third-party tools:
- The manifest file has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- Untested files have been added to
.coveragerc.
The integration reached or maintains the following Integration Quality Scale:
- No score or internal
- 🥈 Silver
- 🥇 Gold
- 🏆 Platinum
To help with the load of incoming pull requests:
- I have reviewed two other open pull requests in this repository.
bdraco
bdraco
MEMBER
submittedAt 3 hours ago
bdraco wants to merge home-assistant/core
bdraco
bdraco
CONTRIBUTOR
createdAt 3 hours ago
Adds UP Chime support for UniFi Protect
Proposed change
Adds support for the new UP Chime devices for UniFi Protect
- Number entity for UP Chime devices
- Button to trigger Chime playback
- Button to trigger Chime buzzer playback
- Last Ring sensor for the last time the Chime was activate
- A new service,
set_chime_paired_doorbellsthat lets your pair doorbells to a chime (this will make if so if the doorbell rings, the chime will also ring)- This service is basically an implemention of a "multi-select", if the select platform ever supports multi-select, the service can be removed and replaced
Images
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New integration (thank you!)
- New feature (which adds functionality to an existing integration)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/22754
Checklist
- The code change is tested and works locally.
- Local tests pass. Your PR cannot be merged unless tests pass
- There is no commented out code in this PR.
- I have followed the development checklist
- The code has been formatted using Black (
black --fast homeassistant tests) - Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
If the code communicates with devices, web services, or third-party tools:
- The manifest file has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- Untested files have been added to
.coveragerc.
The integration reached or maintains the following Integration Quality Scale:
- No score or internal
- 🥈 Silver
- 🥇 Gold
- 🏆 Platinum
To help with the load of incoming pull requests:
- I have reviewed two other open pull requests in this repository.
bdraco
chime_ufp_device_id = _async_unique_id_to_ufp_device_id(chime_button.unique_id)
bdraco merge to home-assistant/core
bdraco
bdraco
CONTRIBUTOR
createdAt 3 hours ago
Adds UP Chime support for UniFi Protect
Proposed change
Adds support for the new UP Chime devices for UniFi Protect
- Number entity for UP Chime devices
- Button to trigger Chime playback
- Button to trigger Chime buzzer playback
- Last Ring sensor for the last time the Chime was activate
- A new service,
set_chime_paired_doorbellsthat lets your pair doorbells to a chime (this will make if so if the doorbell rings, the chime will also ring)- This service is basically an implemention of a "multi-select", if the select platform ever supports multi-select, the service can be removed and replaced
Images
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New integration (thank you!)
- New feature (which adds functionality to an existing integration)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/22754
Checklist
- The code change is tested and works locally.
- Local tests pass. Your PR cannot be merged unless tests pass
- There is no commented out code in this PR.
- I have followed the development checklist
- The code has been formatted using Black (
black --fast homeassistant tests) - Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
If the code communicates with devices, web services, or third-party tools:
- The manifest file has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- Untested files have been added to
.coveragerc.
The integration reached or maintains the following Integration Quality Scale:
- No score or internal
- 🥈 Silver
- 🥇 Gold
- 🏆 Platinum
To help with the load of incoming pull requests:
- I have reviewed two other open pull requests in this repository.
bdraco
bdraco
MEMBER
submittedAt 3 hours ago
bdraco issue comment home-assistant/core
bdraco
bdraco
CONTRIBUTOR
createdAt 3 hours ago
Fix reauthentication for powerwall integration
Proposed change
This is a fix to #70015, although it is hard to test because it is dependend on a firmware update of the powerwall. Through my changes the integration reauthenticates when it receives an AccessDeniedError. An AccessDeniedError indicates either the credentials that are provided are wrong or the token is expired, therefore the reauthentication. Before my changes the loop was always executed only once, because each branch of the try either returned or raised.
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New integration (thank you!)
- New feature (which adds functionality to an existing integration)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Additional information
- This PR fixes or closes issue: fixes #70015
- This PR is related to issue:
- Link to documentation pull request:
Checklist
- The code change is tested and works locally.
- Local tests pass. Your PR cannot be merged unless tests pass
- There is no commented out code in this PR.
- I have followed the development checklist
- The code has been formatted using Black (
black --fast homeassistant tests) - Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
If the code communicates with devices, web services, or third-party tools:
- The manifest file has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- Untested files have been added to
.coveragerc.
The integration reached or maintains the following Integration Quality Scale:
- No score or internal
- 🥈 Silver
- 🥇 Gold
- 🏆 Platinum
To help with the load of incoming pull requests:
- I have reviewed two other open pull requests in this repository.
bdraco
Looks like the approval didn't actually take since my internet dropped out for a minute, but its merged.
bdraco pull request home-assistant/core
bdraco
bdraco
CONTRIBUTOR
createdAt 3 hours ago
Fix reauthentication for powerwall integration
Proposed change
This is a fix to #70015, although it is hard to test because it is dependend on a firmware update of the powerwall. Through my changes the integration reauthenticates when it receives an AccessDeniedError. An AccessDeniedError indicates either the credentials that are provided are wrong or the token is expired, therefore the reauthentication. Before my changes the loop was always executed only once, because each branch of the try either returned or raised.
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New integration (thank you!)
- New feature (which adds functionality to an existing integration)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Additional information
- This PR fixes or closes issue: fixes #70015
- This PR is related to issue:
- Link to documentation pull request:
Checklist
- The code change is tested and works locally.
- Local tests pass. Your PR cannot be merged unless tests pass
- There is no commented out code in this PR.
- I have followed the development checklist
- The code has been formatted using Black (
black --fast homeassistant tests) - Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
If the code communicates with devices, web services, or third-party tools:
- The manifest file has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- Untested files have been added to
.coveragerc.
The integration reached or maintains the following Integration Quality Scale:
- No score or internal
- 🥈 Silver
- 🥇 Gold
- 🏆 Platinum
To help with the load of incoming pull requests:
- I have reviewed two other open pull requests in this repository.
bdraco issue home-assistant/core
bdraco
Powerwall integration lost connection to PW and didn't reconnect
The problem
At 2:26:31am, HA stopped connecting to my PW and fetching data. All sensors went to unavailable (expected) but never returned. Required HA to be restarted before the integration would recover.
2022-04-14 02:26:31 ERROR (MainThread) [homeassistant.components.powerwall] Error fetching Powerwall site data: Unable to fetch data from powerwall
(this was the only message in the log)
I have a binary ping sensor to ping the PW GW and that never went unreachable; I then have an automation to alert me, that also never tripped, so it was still connected at an IP level to my network. I could still ping it manually as well.
The PW has only been installed a week and therefore I can't comment if this has regressed at all.
PowerWall 2 (GW2) by Tesla Firmware: 22.9.1
Interestingly, I have a friend who also has HA and also has a PW, whose integration also did this last night ! Very different time though (10pm not 2am). They have firmware 21.44, and they have also seen this happen once before but didn't
What version of Home Assistant Core has the issue?
core-2022.4.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Tesla Powerwall
Link to integration documentation on our website
https://www.home-assistant.io/integrations/powerwall
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
2022-04-14 02:16:01 ERROR (Thread-6) [pychromecast.socket_client] [Kitchen Home(192.168.x.xx):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.x.xx', 8009)), retrying in 5.0s
2022-04-14 02:26:31 ERROR (MainThread) [homeassistant.components.powerwall] Error fetching Powerwall site data: Unable to fetch data from powerwall
2022-04-14 02:52:56 WARNING (Thread-5) [pychromecast.socket_client] [Front Living TV(192.168.x.xx):8009] Heartbeat timeout, resetting connection
Additional information
No response
bdraco issue comment home-assistant/core
bdraco
bdraco
CONTRIBUTOR
createdAt 3 hours ago
Fix reauthentication for powerwall integration
Proposed change
This is a fix to #70015, although it is hard to test because it is dependend on a firmware update of the powerwall. Through my changes the integration reauthenticates when it receives an AccessDeniedError. An AccessDeniedError indicates either the credentials that are provided are wrong or the token is expired, therefore the reauthentication. Before my changes the loop was always executed only once, because each branch of the try either returned or raised.
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New integration (thank you!)
- New feature (which adds functionality to an existing integration)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Additional information
- This PR fixes or closes issue: fixes #70015
- This PR is related to issue:
- Link to documentation pull request:
Checklist
- The code change is tested and works locally.
- Local tests pass. Your PR cannot be merged unless tests pass
- There is no commented out code in this PR.
- I have followed the development checklist
- The code has been formatted using Black (
black --fast homeassistant tests) - Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
If the code communicates with devices, web services, or third-party tools:
- The manifest file has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- Untested files have been added to
.coveragerc.
The integration reached or maintains the following Integration Quality Scale:
- No score or internal
- 🥈 Silver
- 🥇 Gold
- 🏆 Platinum
To help with the load of incoming pull requests:
- I have reviewed two other open pull requests in this repository.
bdraco
Ran fine overnight.
👍
bdraco issue comment home-assistant/core
bdraco
bdraco
CONTRIBUTOR
createdAt 3 hours ago
Fix reauthentication for powerwall integration
Proposed change
This is a fix to #70015, although it is hard to test because it is dependend on a firmware update of the powerwall. Through my changes the integration reauthenticates when it receives an AccessDeniedError. An AccessDeniedError indicates either the credentials that are provided are wrong or the token is expired, therefore the reauthentication. Before my changes the loop was always executed only once, because each branch of the try either returned or raised.
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New integration (thank you!)
- New feature (which adds functionality to an existing integration)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Additional information
- This PR fixes or closes issue: fixes #70015
- This PR is related to issue:
- Link to documentation pull request:
Checklist
- The code change is tested and works locally.
- Local tests pass. Your PR cannot be merged unless tests pass
- There is no commented out code in this PR.
- I have followed the development checklist
- The code has been formatted using Black (
black --fast homeassistant tests) - Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
If the code communicates with devices, web services, or third-party tools:
- The manifest file has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- Untested files have been added to
.coveragerc.
The integration reached or maintains the following Integration Quality Scale:
- No score or internal
- 🥈 Silver
- 🥇 Gold
- 🏆 Platinum
To help with the load of incoming pull requests:
- I have reviewed two other open pull requests in this repository.
bdraco
But I'm not sure how that could be achieved.
Yeah thats the problem isn't it. 🙈
bdraco push bdraco/frontend
bdraco
bdraco
Merge branch 'logbook_localize' of github.com:bdraco/frontend into logbook_localize
bdraco
Merge branch 'logbook_localize' into integration
bdraco
git push oirigin Merge branch 'integration' of github.com:bdraco/frontend into integration
commit sha： 11dfb74d9acd0b1276c72e42b1d1a25413e4223b
push time in 3 hours agobdraco push bdraco/frontend
bdraco
bdraco
Merge branch 'logbook_localize' of github.com:bdraco/frontend into logbook_localize
commit sha： d0c28555b7ec8df319da0eba32878942739d0694
push time in 3 hours agobdraco push bdraco/frontend
bdraco
remove unrelated changes
bdraco
Merge branch 'logbook_localize' into integration
commit sha： 3c5db5ca0a0e6e7da0dd713b8f6990243eae5de6
push time in 3 hours agobdraco push bdraco/frontend
bdraco
remove unrelated changes
commit sha： e9f9da89dd07f14a489f438eaf760b7ccbd5094d
push time in 3 hours agobdraco push bdraco/frontend
bdraco
Use new localized context state in logbook
- Refactor to remove more static english strings that come from the backend
bdraco
Merge branch 'logbook_localize' into integration
commit sha： 2e564e6357abb271e3d0d81532a9bd779bbb5cf8
push time in 3 hours agobdraco pull request home-assistant/frontend
bdraco
bdraco
MEMBER
createdAt 3 hours ago
Use new localized context state in logbook
Proposed change
- Refactor to remove more static english strings that come from the backend
Fixes #12698 (except for the backend messages that come from integrations)
Type of change
- Dependency upgrade
- Bugfix (non-breaking change which fixes an issue)
- New feature (thank you!)
- Breaking change (fix/feature causing existing functionality to break)
- Code quality improvements to existing code or addition of tests
Example configuration
Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue or discussion:
- Link to documentation pull request:
Checklist
- The code change is tested and works locally.
- There is no commented out code in this PR.
- Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- Documentation added/updated for www.home-assistant.io
Previous
Next
Adjust device_automation type hints in nest (#72197)