Skip to content

Updated docs for Lutron Caseta component and platforms #3310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 6, 2017

Conversation

upsert
Copy link
Contributor

@upsert upsert commented Sep 4, 2017

Description:
Updated and expanded documentation for the Lutron Caseta component and its platforms.

  • Expanded text for each platform to help new users understand how it will work. Gives an example for how their light/switch/cover/scene will appear in Home Assistant. Points them to the Home Assistant component for light/switch/cover/scene for additional help.
  • Expanded text with available services for each platform since not all services are implemented.
  • Standardized the spelling of 'Smart Bridge' and 'Smart Bridge PRO', which follows how Lutron names the products in their documentation and on their website.
  • On the component page, added the model numbers of the supported hubs and pointed them to the 'lutron' component if they have RadioRA 2. This can otherwise be confusing to the reader if they are uncertain why there are multiple Lutron components.
  • On the component page, added a note about DHCP reservation and how to set a static IP for the hub in the Lutron app.
  • On the cover platform page removed the configuation yaml text which was causing duplicate shades to appear (as per this thread). All platforms are loaded by the component so additional configuration is not needed.
  • Removed references to 'Serena' shades since the component will now support multiple Lutron shades.

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

@mention-bot
Copy link

@upsert, thanks for your PR! By analyzing the history of the files in this pull request, we identified @gurumitts, @fabaff and @kfcook to be potential reviewers.

Copy link
Member

@dale3h dale3h left a comment

Choose a reason for hiding this comment

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

Looks good! 🎃

@dale3h
Copy link
Member

dale3h commented Sep 5, 2017

Does this need to be merged into current branch instead of next branch?

@upsert
Copy link
Contributor Author

upsert commented Sep 5, 2017

@dale3h I'm not entirely clear on the branches for the documentation. The linked PR on home-assistant repo is in the dev branch so I assumed that would correspond to next?

@frenck
Copy link
Member

frenck commented Sep 6, 2017

@upsert That is a perfectly fine assumption, nevertheless, the changed documentation could also apply to the current release.

Nevertheless, it pairs with a parent PR, so I agree on the branch set.

@frenck frenck merged commit b12dce2 into home-assistant:next Sep 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants