chaimt
(Chaim Turkel)
August 6, 2022, 9:02pm
1
After upgrading to 8.1 all my switches with broadlink are missing.
I downgraded to 7.7 and it is back working
Did i miss something?
nickrout
(Nick Rout)
August 6, 2022, 10:21pm
2
There seems to be known problem Issues · home-assistant/core · GitHub
Try reloading the broadlink integration. It has worked for many. Look in the 2022.8 release thread.
chaimt:
Did i miss something?
Yep, heaps of chat about it in the main 2022.8 release thread.
CaptTom
(Tom)
August 7, 2022, 12:42am
4
Does reloading the integration lose any entities? I’d hate to have to re-pair all my Broadlink switches.
zagnuts
(Zagnuts)
August 7, 2022, 5:14am
5
This is at least the second time the Broadlink integration has been broken for me after an update. The current issue seems to be the integration itself not starting in time for when switches are setup. So instead I’ve moved it into a script. For example here’s my code for turning on/off my fireplace.
First create a script (in my case in scripts.yaml):
fireplace_on:
sequence:
- service: remote.send_command
target:
entity_id: remote.basil_remote
data:
command: b64:sg8cAAwPDxobDw8aDxoEEg8aExoEEg8aDxobDxsAAlwAAAAAAAAAAAAAAAA=
fireplace_off:
sequence:
- service: remote.send_command
target:
entity_id: remote.basil_remote
data:
command: b64:sgYcAAwODxobDw8aDxoPPg8aExoPGg8bGg8bDxsAAl0AAAAAAAAAAAAAAAA=
You will now be able to test running the scripts to send the codes. Now to turn it into a switch (in my case, in switch.yaml).
- platform: template
switches:
fireplace_mode:
value_template: "{{ is_state('input_boolean.fireplace_mode', 'on') }}"
turn_on:
- service: input_boolean.turn_on
entity_id: input_boolean.fireplace_mode
- service: script.fireplace_on
turn_off:
- service: input_boolean.turn_off
entity_id: input_boolean.fireplace_mode
- service: script.fireplace_off
Then to track if the fireplace is off or on, need to setup a boolean entry (most likely in configuration.yaml - you can do this through the gui, but I like it hard coded just in case I need to do a rebuild from scratch)
input_boolean:
fireplace_mode:
initial: off
Obviously this is a pain to do if you have a lot of switches/codes using Broadlink but fortunately for me I didn’t have many.
CaptTom
(Tom)
August 7, 2022, 8:17pm
6
It looks like maybe there’s a fix in 2022.8.2 :
home-assistant:dev
← elupus:broadlink/platform_setup
opened 01:00AM - 07 Aug 22 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
We must setup the platform data with the config entry setup callback,
and device information. So trigger a platform not ready until the entry
has been setup, then use the stored callback function to setup.
The old solution relied on platform setup having completed before config entry setup. This is no longer guaranteed (if it ever was)
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #76297
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] 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][dev-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][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] 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 running `python3 -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][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io