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.

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

Twinkly unavailable after trying to group as an area #105839

Closed
OldShaterhan opened this issue Dec 15, 2023 · 2 comments
Closed

Twinkly unavailable after trying to group as an area #105839

OldShaterhan opened this issue Dec 15, 2023 · 2 comments

Comments

@OldShaterhan
Copy link
Contributor

OldShaterhan commented Dec 15, 2023

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?

Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x000001540402FFA0>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x000001540402FA00>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x000001540402FD30>
== Details ==
{'bytes_per_led': 4,
 'code': 1000,
 'copyright': 'LEDWORKS 2021',
 'device_name': 'DEVICE NAME',
 'flash_size': 64,
 'frame_rate': 11.06,
 'fw_family': 'G',
 'hardware_version': '307',
 'hw_id': '793b14',
 'led_profile': 'RGBW',
 'led_type': 12,
 'mac': 'MAC',
 'max_movies': 55,
 'max_supported_led': 510,
 'measured_frame_rate': 13.33,
 'movie_capacity': 4786,
 'number_of_led': 210,
 'product_code': 'TWW210SPP2',
 'product_name': 'Twinkly',
 'uptime': '87031996',
 'uuid': 'F4946876-5A32-4DDC-8E30-9C8E16B8B5F3',
 'wire_type': 4}
== Setting color ==
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x000001540402F400>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x000001540402F970>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x000001540402F280>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x000001540402F580>
== Setting color done ==
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x000001540402F790>
== Installed movies ==
{'available_frames': 4786,
 'code': 1000,
 'max': 55,
 'max_capacity': 4786,
 'movies': []}
## Cant get current movie ##
400, message='Data after `Connection: close`:\n\n  bytearray(b\'{"code":1102}\')\n                ^', url=URL('http://192.168.0.207/xled/v1/movies/current')
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x000001540402FD00>
## Movies are unavailable ##

----


Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x0000020C8402F820>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x0000020C8402FA30>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x0000020C8402FD30>
== Details ==
{'bytes_per_led': 3,
 'code': 1000,
 'copyright': 'LEDWORKS 2021',
 'device_name': 'DEVICE NAME',
 'flash_size': 64,
 'frame_rate': 40,
 'fw_family': 'S',
 'hardware_version': '601',
 'hw_id': '2e3258',
 'led_profile': 'RGB',
 'led_type': 33,
 'mac': 'MAC',
 'max_movies': 55,
 'max_supported_led': 500,
 'measured_frame_rate': 40,
 'movie_capacity': 21141,
 'number_of_led': 60,
 'product_code': 'TWD060STP',
 'product_name': 'Twinkly',
 'uptime': '86889260',
 'uuid': '449B7CD1-7B02-4D76-A1C5-AE11AA808DD6',
 'wire_type': 4}
== Setting color ==
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x0000020C8402F430>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x0000020C8402F9A0>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x0000020C8402F580>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x0000020C8402F5E0>
== Setting color done ==
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x0000020C8402F6D0>
== Installed movies ==
{'available_frames': 21141,
 'code': 1000,
 'max': 55,
 'max_capacity': 21141,
 'movies': []}
## Cant get current movie ##
400, message='Data after `Connection: close`:\n\n  bytearray(b\'{"code":1102}\')\n                ^', url=URL('http://192.168.0.57/xled/v1/movies/current')
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x0000020C8402F7F0>
## Movies are unavailable ##

Additional information

Logged to TTLS as well: jschlyter/ttls#37

@home-assistant
Copy link

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.

(message by CodeOwnersMention)


twinkly documentation
twinkly source
(message by IssueLinks)

@issue-triage-workflows
Copy link

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.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 22, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Apr 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant