You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I tried to move Twinkly to area these started to become very unavailable. When it was a group at first it worked fine. Now even after dispairing it seems to be unavailable.
Hey there @dr1rrb, @RobBie1221, @Olen, mind taking a look at this issue 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 issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign twinkly Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
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 with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem
When I tried to move Twinkly to area these started to become very unavailable. When it was a group at first it worked fine. Now even after dispairing it seems to be unavailable.
I made some test on the basis of #83076 (comment) by @Olen - logs below.
I'm not sure if this is Twinkly related or rather TTLS, but I would be glad if anyone could help.
Devices: Dots 60 + Curtain RGBW 210, I have 3x Icicles 190 RGBW groupped as normal group - these are working fine.
I have no problem with access using mobile app.
What version of Home Assistant Core has the issue?
2023.12.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
twinkly
Link to integration documentation on our website
https://www.home-assistant.io/integrations/twinkly/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
Logged to TTLS as well: jschlyter/ttls#37
The text was updated successfully, but these errors were encountered: