Skip to content

Added description for source priority.#8773

Merged
fabaff merged 1 commit into
home-assistant:nextfrom
gorynychzmey:patch-1
Feb 28, 2019
Merged

Added description for source priority.#8773
fabaff merged 1 commit into
home-assistant:nextfrom
gorynychzmey:patch-1

Conversation

@gorynychzmey
Copy link
Copy Markdown
Contributor

@gorynychzmey gorynychzmey commented Feb 28, 2019

Description:

Added description for source priority to Person (with examlpe).

Pull request in home-assistant (if applicable): home-assistant/core#21479

Checklist:

  • Branch: next is 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 against current.
  • The documentation follows the standards.

@ghost ghost added the to-do label Feb 28, 2019
@fabaff fabaff merged commit aae5a60 into home-assistant:next Feb 28, 2019
@ghost ghost removed the to-do label Feb 28, 2019
@gorynychzmey gorynychzmey deleted the patch-1 branch February 28, 2019 09:02
The person component allows to connect device tracker entities to one or more person entities. The last state update of a connected device tracker will set the state of the person. For example if you connect your router and your OwnTracks device as trackers to your person, the last state update from either the router or your OwnTracks device will set the state of your person.
The person component allows to connect device tracker entities to one or more person entities. The state updates of a connected device trackers will set the state of the person. When multiple device tracers used, the state of berson will be determined next way:

1. If there are sources presenting status 'home', than latest of this sources will be taken.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't correct totally correct, since gps trackers are excluded from this group. This needs clarification. Please also add examples.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MartinHjelmare, I've corrected description in documentation, examples will be later. But I still haven't decided, should I really exclude GPS sources from 'home' sources or not. Seems to be that nothing changes for status, only difference is, which device will be presented as source.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's update the docs so it's correct according to the current source code first.

Then please open an architecture issue where we discuss the details of the implementation.

Thanks for responding quickly!

@gorynychzmey gorynychzmey restored the patch-1 branch February 28, 2019 11:20
@frenck frenck added new-feature This PR adds documentation for a new Home Assistant feature to an existing integration next This PR goes into the next branch has-parent This PR has a parent PR in another repo labels Feb 28, 2019
@klaasnicolaas klaasnicolaas added the parent-merged The parent PR has been merged already label Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

has-parent This PR has a parent PR in another repo new-feature This PR adds documentation for a new Home Assistant feature to an existing integration next This PR goes into the next branch parent-merged The parent PR has been merged already

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants