Skip to content

Explain workaround for limitlessled assumed_state #4856

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

Conversation

amelchio
Copy link
Contributor

@amelchio amelchio commented Mar 7, 2018

Description:

This has been a frequent topic since home-assistant/core#12475 was released so I thought it would be a good idea to put it in the documentation.

Fixes home-assistant/core#12853

Checklist:

  • Branch: Fixes, changes and adjustments should be created against current. New documentation for platforms/components and features should go to next.
  • The documentation follow the standards.

@frenck frenck self-assigned this Mar 14, 2018
frenck
frenck previously approved these changes Mar 14, 2018
@frenck
Copy link
Member

frenck commented Mar 14, 2018

@amelchio Thank you for this excellent contribution! 🥇
Applied a tiny grammar fix and can be merged as soon as the build passes.

@frenck frenck force-pushed the limitlessled-assumed_state-workaround branch from 9a16e91 to 880c984 Compare March 14, 2018 19:51
@frenck
Copy link
Member

frenck commented Mar 14, 2018

Rebased this PR, awaiting build results

@frenck frenck merged commit dc01806 into home-assistant:current Mar 14, 2018
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.

2 participants