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:
Back in April Home Assistant was updated to use a new copy of pylutron_caseta for compatibility with a firmware update, but the documentation was not updated.
The new version of pylutron_caseta joins the names of rooms and devices together so if you have a lamp called "Bedroom Lamp" and you've put it an a room called "Bedroom" the actual device name comes out as
bedroom_bedroom_lamp
. I've updated the documentation to suggest you should name the lamp just "Lamp" to getbedroom_lamp
. (I have a code change for entity registry support ready with the next release of pylutron_caseta should be very soon)More importantly, the version of get_lutron_certs.py bundled with the documentation should still work but exits with an error at the end. Since April, the pylutron-caseta repo has kept an updated copy of the script in its master branch, and I've updated the documentation to point to that one.
Finally, I've also reformatted the configuration section to use
{% configuration %}
.Pull request in home-assistant (if applicable): home-assistant/core#14013
Checklist:
current
. New documentation for platforms/components and features should go tonext
.