Magic Home: RGB LED strip - Cannot determine protocol

[SnowDrifterr]

The problem

Trying to set up an FVTLED RGB strip via Magic Home

It seems to be stuck in a loop where it says 'cannot determine protocol' and keeps retrying

What version of Home Assistant Core has the issue?

core-2024.7.4

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

Magic Home

Link to integration documentation on our website

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

Diagnostics information

2024-07-30 10:54:39.556 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.54', 5577) => 0x81 0x8A 0x8B 0x96 (4)
2024-07-30 10:54:47.058 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.54', 5577): Connection lost: None
2024-07-30 10:54:47.059 DEBUG (MainThread) [flux_led.base_device] 192.168.1.54: set_unavailable: Connection lost
2024-07-30 10:54:47.086 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.54', 5577) => 0xEF 0x01 0x77 (3)
2024-07-30 10:54:54.588 DEBUG (MainThread) [flux_led.base_device] 192.168.1.54: set_unavailable: Cannot determine protocol
2024-07-30 10:54:54.588 DEBUG (MainThread) [flux_led.base_device] 192.168.1.54: set_unavailable: Connection closed
2024-07-30 10:54:54.589 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.54', 5577): Connection lost: None
2024-07-30 10:54:54.589 DEBUG (MainThread) [flux_led.base_device] 192.168.1.54: set_unavailable: Connection lost

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @icemanch, mind taking a look at this issue as it has been labeled with an integration (flux_led) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `flux_led` 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 flux_led` 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)}}

---

flux_led documentation flux_led source _{^{(message by IssueLinks)}}

[clivefrog]

I had a quick look today as I'm facing the same issue with a newer FVTLED light strip. The missing models and protocols are managed by Danielhiversen. Some packet capture reverse engineering or device mocking is required to determine the updates needed. I sadly don't have time right now to go any further but have found my lights retain their existing light settings when powered on / off so I have just thrown a basic smart switch on them to at least get power controls, will manage light settings using the FVTLED app when needed (Magic home doens't even recognise this strip) and will hope that someone can pick this up to fill in the blanks one day.