Device recognized but cannot recognize protocol

[bchevreau]

The problem

I have a Surp Life controller for a set of Hexagon lights that I was excited to integrate to my setup. It is well recognized in Surp Life, google assistant can turn it on and off, and it gets discovered thru the Magic Home integration.

However upon initializing, it fails and tries over and over again.

Here is what I can see from the logs activating debug mode:

2024-05-01 14:35:03.090 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.91', 5577) => 0x81 0x8A 0x8B 0x96 (4) 2024-05-01 14:35:03.097 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.91', 5577) <= 0xEA 0x81 0x02 0x00 0xAA 0x09 0x23 0x24 0x01 0x50 0xF0 0x78 0x64 0x5E 0x00 0x00 0x02 0x00 0x0C 0xFF 0xFF 0xFF 0xFF 0x01 0x00 0x00 0x01 (27) 2024-05-01 14:35:03.098 DEBUG (MainThread) [flux_led.base_device] 192.168.1.91: set_available: Received message ea810200aa0923240150f078645e000002000cffffffff01000001 2024-05-01 14:35:03.098 DEBUG (MainThread) [flux_led.aiodevice] 192.168.1.91: Ignoring unknown message: 0xEA 0x81 0x02 0x00 0xAA 0x09 0x23 0x24 0x01 0x50 0xF0 0x78 0x64 0x5E 0x00 0x00 0x02 0x00 0x0C 0xFF 0xFF 0xFF 0xFF 0x01 0x00 0x00 0x01 2024-05-01 14:35:10.592 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.91', 5577): Connection lost: None 2024-05-01 14:35:10.592 DEBUG (MainThread) [flux_led.base_device] 192.168.1.91: set_unavailable: Connection lost 2024-05-01 14:35:10.597 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.91', 5577) => 0xEF 0x01 0x77 (3) 2024-05-01 14:35:18.099 DEBUG (MainThread) [flux_led.base_device] 192.168.1.91: set_unavailable: Cannot determine protocol 2024-05-01 14:35:18.099 DEBUG (MainThread) [flux_led.base_device] 192.168.1.91: set_unavailable: Connection closed 2024-05-01 14:35:18.100 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.91', 5577): Connection lost: None 2024-05-01 14:35:18.100 DEBUG (MainThread) [flux_led.base_device] 192.168.1.91: set_unavailable: Connection lost 2024-05-01 14:35:28.615 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.91', 5577) => 0x81 0x8A 0x8B 0x96 (4) 2024-05-01 14:35:28.630 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.91', 5577) <= 0xEA 0x81 0x02 0x00 0xAA 0x09 0x23 0x25 0x65 0x50 0xF0 0xB4 0x64 0x64 0x00 0x00 0x02 0x00 0x0C 0xFF 0xFF 0xFF 0xFF 0x01 0x00 0x00 0x01 (27) 2024-05-01 14:35:28.630 DEBUG (MainThread) [flux_led.base_device] 192.168.1.91: set_available: Received message ea810200aa0923256550f0b46464000002000cffffffff01000001 2024-05-01 14:35:28.630 DEBUG (MainThread) [flux_led.aiodevice] 192.168.1.91: Ignoring unknown message: 0xEA 0x81 0x02 0x00 0xAA 0x09 0x23 0x25 0x65 0x50 0xF0 0xB4 0x64 0x64 0x00 0x00 0x02 0x00 0x0C 0xFF 0xFF 0xFF 0xFF 0x01 0x00 0x00 0x01 2024-05-01 14:35:36.118 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.91', 5577): Connection lost: None 2024-05-01 14:35:36.118 DEBUG (MainThread) [flux_led.base_device] 192.168.1.91: set_unavailable: Connection lost 2024-05-01 14:35:36.129 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.91', 5577) => 0xEF 0x01 0x77 (3) 2024-05-01 14:35:43.631 DEBUG (MainThread) [flux_led.base_device] 192.168.1.91: set_unavailable: Cannot determine protocol 2024-05-01 14:35:43.632 DEBUG (MainThread) [flux_led.base_device] 192.168.1.91: set_unavailable: Connection closed 2024-05-01 14:35:43.632 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.91', 5577): Connection lost: None 2024-05-01 14:35:43.632 DEBUG (MainThread) [flux_led.base_device] 192.168.1.91: set_unavailable: Connection lost 2024-05-01 14:36:03.992 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.91', 5577) => 0x81 0x8A 0x8B 0x96 (4) 2024-05-01 14:36:04.007 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.91', 5577) <= 0xEA 0x81 0x02 0x00 0xAA 0x09 0x23 0x25 0x65 0x50 0xF0 0xB4 0x64 0x64 0x00 0x00 0x04 0x00 0x0C 0xFF 0xFF 0xFF 0xFF 0x01 0x00 0x00 0x01 (27) 2024-05-01 14:36:04.008 DEBUG (MainThread) [flux_led.base_device] 192.168.1.91: set_available: Received message ea810200aa0923256550f0b46464000004000cffffffff01000001 2024-05-01 14:36:04.008 DEBUG (MainThread) [flux_led.aiodevice] 192.168.1.91: Ignoring unknown message: 0xEA 0x81 0x02 0x00 0xAA 0x09 0x23 0x25 0x65 0x50 0xF0 0xB4 0x64 0x64 0x00 0x00 0x04 0x00 0x0C 0xFF 0xFF 0xFF 0xFF 0x01 0x00 0x00 0x01 2024-05-01 14:36:11.495 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.91', 5577): Connection lost: None 2024-05-01 14:36:11.495 DEBUG (MainThread) [flux_led.base_device] 192.168.1.91: set_unavailable: Connection lost 2024-05-01 14:36:11.502 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.91', 5577) => 0xEF 0x01 0x77 (3) 2024-05-01 14:36:19.003 DEBUG (MainThread) [flux_led.base_device] 192.168.1.91: set_unavailable: Cannot determine protocol 2024-05-01 14:36:19.003 DEBUG (MainThread) [flux_led.base_device] 192.168.1.91: set_unavailable: Connection closed 2024-05-01 14:36:19.003 DEBUG (MainThread) [flux_led.aioprotocol] ('192.168.1.91', 5577): Connection lost: None 2024-05-01 14:36:19.004 DEBUG (MainThread) [flux_led.base_device] 192.168.1.91: set_unavailable: Connection lost

What version of Home Assistant Core has the issue?

core-2024.4.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

home-assistant_flux_led_2024-05-01T06-43-29.238Z.log

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)}}

[bchevreau]

Additionally, I can see a few extra info in the app:

It shows as a Zengge on my router, dunno if that helps in any way...

Firmware: WF.52.AA.35.0,V9_ZG-BL-3KEY

Type of IC Setting : tried to make those match to what is mentioned on the Magic Home integration documentation but with no luck...

[LauraSophieM]

Any solution? Having the same problem here

[bchevreau]

Sadly this integration is abandonned. I'd be willing to decode the new stuff if someone explained it to me a bit, even thru a lot of trial and error, but I have a feeling this is not an easy task... @bdraco sorry for the ping, any chance you could point us towards the right way of decoding and sniffing those codes to retrofit the new Magic Home models and protocols ?

[bdraco]

When a new protocol is released, I would install the magic home app on an arm mac and use Wire Shark to watch the packets between the device and the mac to, than change each color/temp/white until I figured out the commands.

You can do a similar thing with the android app if you use https://httptoolkit.com/ or https://www.charlesproxy.com/ (or some other tool) to watch what commands are sent to the cloud service and cycles though each color/temp/white etc.

[bdraco]

You can also mock a device using https://github.com/Danielhiversen/flux_led/blob/master/examples/mockdevice.py and discover it in the magic home app which will than try to control it.

[ridderdk]

I got the samme issue with the Magic Home integration, must be never models, a ceiling led with firmware WF.50.3D.13.0, V1_ZG-BK2 Cannot determine protocol

[issue-triage-workflows[bot]]

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.