Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Document that effects may be required to control Twinkly (plus) #35156

Closed
gdgib opened this issue Oct 9, 2024 · 4 comments · Fixed by #36797
Closed

Document that effects may be required to control Twinkly (plus) #35156

gdgib opened this issue Oct 9, 2024 · 4 comments · Fixed by #36797
Labels
integration: twinkly

Comments

@gdgib
Copy link
Contributor

gdgib commented Oct 9, 2024

Feedback

Recent firmware updates to Twinkly Plus devices forced a reset of the saved effects. HomeAssistant could not control the lights at all (the light entity was disabled) until I saved at least one new effect per string. This seems like a weird edge condition of the twinkly API. I suggest documenting it:

"Please note that Twinkly strings without any saved effects may not be controllable through HomeAssistant. This includes new strings, strings whose saved effects have been deleted by a firmware update, or strings where you have deleted all the saved effects. Such a string can be added to HomeAssistant, but the light entity will show as disabled. If you encounter this, save at least one effect to the string using the Twinkly app, reload the integration, and the entity should be enabled and available."

URL

https://www.home-assistant.io/integrations/twinkly/

Version

2024.10.1

Additional information

No response
@home-assistant
Copy link

home-assistant bot commented Oct 9, 2024

Hey there @dr1rrb, @RobBie1221, @Olen, mind taking a look at this feedback as it has been labeled with an integration (twinkly) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of twinkly can trigger bot actions by commenting:

  • @home-assistant close Closes the feedback.
  • @home-assistant rename Awesome new title Renames the feedback.
  • @home-assistant reopen Reopen the feedback.
  • @home-assistant unassign twinkly Removes the current integration label and assignees on the feedback, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.

@github-actions GitHub Actions
Copy link

github-actions bot commented Dec 8, 2024

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved.
If this issue is still relevant, please let us know by leaving a comment 👍
This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale The PR had no activity for quite some time, and is marked as Stale label Dec 8, 2024
@gdgib
Copy link
Contributor Author

gdgib commented Dec 8, 2024

Definitely still relevant. I guess I'll need to figure out how to open a PR for this.

@github-actions github-actions bot removed the Stale The PR had no activity for quite some time, and is marked as Stale label Dec 8, 2024
@gdgib gdgib mentioned this issue Jan 8, 2025
Merged
8 tasks
@gdgib
Copy link
Contributor Author

gdgib commented Jan 8, 2025

Opened #36797 to document this. Hopefully we can get a merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
integration: twinkly
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Twinkly devices may require an effect to enable control gdgib/home-assistant.io
1 participant
@gdgib