home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.18k stars 30.2k forks source link

Surplife Led Controller stopped working after firmware update #116725

Closed bchevreau closed 1 month ago

bchevreau commented 5 months ago

The problem

I recently received a led controller. It worked ok for a few hours, and now became completely unresponsive to any commands except on/off and sometimes some of the effects. Color change doesn't work anymore, so is brightness. The firmware update on the controller seem to have added a lot of new features... That this integration also were sadly missing. It seems like most updates are not integrated yet, sadly there is no way to go back to previous firmware in Surplife.

(the device is on 192.168.1.131 IP, ignore the 192.168.1.168 which is another device, also by Magic Home, that sadly also doesn't work because of a more recent firmware... :-(

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-03T18-39-19.272Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Issues start at Line 100, and more importantly line 624

2024-05-04 02:33:38.289 DEBUG (MainThread) [flux_led.aiodevice] 192.168.1.131: Ignoring unknown message: 0xEA 0x81 0x01 0x00 0x33 0x0B 0x24 0x61 0x1B 0x34 0xF0 0x04 0x64 0x64 0x00 0x00 0x00 0x00 0x00 0x00

Additional information

No response

home-assistant[bot] commented 5 months ago

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 commented 5 months ago

@bdraco Any chance anyone is working on Magic Home devices at this point? I just realized this integration is based on a Public Archive integration...

bdraco commented 5 months ago

I no longer use any Magic Home devices. I finished migrating everything to ESPHome a few months (maybe years at this point) ago.

issue-triage-workflows[bot] commented 2 months ago

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.