Add Alarm Control Panel to secure devices#10249
Closed
engrbm87 wants to merge 47 commits into
Closed
Conversation
google calendar docs linking to wrong page
updated for latest FireTV OS
Installed the Fritz!Box device tracker today on Hass.io without the need to install additional packages.
With hass.io no need for additional packages
Update heos.markdown
* Clarify device blocking functionality The documentation did not clearly explain that you had to use MAC addresses to allow for blocking/unblocking clients. * Minor change
I noticed a mistake in the TTS engine example it should be `tts.google_translate_say` not `tts.google_say`
On the website they look like commented lines
Small typo in the "full example" part. :)
condition: numeric state => condition: numeric_state
I spent some time (newbie) before I found out I had to fill '*' for fields I did not plan to fill (like 'hour')
* Document 'name' config parameter in rejseplanen Document the undocumented but fully working name config. This is an optional config but essential to know to define more than one instance of the rejseplanen sensor and getting a predictable result. Otherwise the sensor name defaults to sensor.next_departure_# and the numbers can swap around after an HA restart * An example where policy and common sense clash Done as suggested though I do not agree * ✏️ Tweak * Adjust default * Fix sample
* Update from Integration to component * Revert a change
The example isn't valid, oops
Add breaking changes bling
fix adr-400 link in breaking changes section
* Document user-provided services.yaml file * ✏️ Tweak
* Update installation.markdown Remove reference to `update_config` service, which has been removed. * 🚑 Fix build error
probot-home-assistant
Bot
added
has-parent
5 tasks
Member
|
There are a lot of unrelated commits in this PR |
Contributor
Author
|
I wanted to add this to the next branch as it is a new feature in the google assistant. what do you recommend to fix this PR? |
Contributor
Author
|
I made a new PR again next branch with my commit only. i will close this one. |
Member
|
I think you made the branch before we dit a massive merge for the 0.98 release 😉 Just pull the latest changes from the upstream repo and I think the commits will be gone. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
Pull request in home-assistant (if applicable): home-assistant/home-assistant/#26249
Checklist:
nextis for changes and new documentation that will go public with the next Home Assistant release. Fixes, changes and adjustments for the current release should be created againstcurrent.