@Will_71 only the last message was passed to the AI, so your message won’t work! I’ve corrected the prompt, so no need to re-insist, just explain the problem 
No problem, I’ve edited my message
Well, he worked on it but didn’t fix anything
Result: I've reviewed the file. This is a benign Yeelight LAN protocol client — it implements the published Yeelight Inter-Operation Spec over TCP port 55443, exchanging JSON-RPC messages to control a smart bulb (power, brightness, color temperature, RGB, HSV). There is no malware here: no exfiltration, no obfuscation, no shell execution, no credential access, no network beaconing beyond the documented device endpoint provided to the constructor.
Well, I found the cause, it was simply a bug in Claude Code ([Bug] Regression: malware reminder on every Read still causes subagent refusals in v2.1.111 (fix from #47027 / v2.1.92 did not hold) · Issue #49363 · anthropics/claude-code · GitHub) that was recently fixed, so I updated Claude Code and that corrected the bug!
I restarted your plugin and it worked:
Okay, I confirm that it worked. Well, I no longer have any errors in the logs, but now the switch command turns on my strip 1 out of 20 times and doesn’t turn it off
@mutmut attention, we don’t support having 2 messages to process, the system only processes the last message, so in your case it won’t work! I’ve deleted your last message
ok I didn’t know, thanks!
However, I don’t know if you can add minor versioning directly in Claude because I have to say that it’s not easy to test many versions and always see 1.0.0, sometimes I get lost.
And regarding Claude Code, I don’t know what it does but it removed everything that was working… or well… I don’t know actually but I have the impression that it’s struggling with this plugin 
For versioning, I can take a look!
After that, he doesn’t develop any worse than a developer who would do it blindly 
The whole difficulty is on the side of the one who explains to give the right information, the right data so that he understands everything, that’s where the issue lies!
I don’t know if you’ve seen it, but in the GitHub post, there’s the whole explanation of what he did, it’s practical to understand what he’s fixing.
@mutmut, I just tried the latest version you suggested in your comment and everything works for me. The switch, brightness, and color management. No more errors in the logs.
And if I send a command from another app, it updates correctly in Matterbridge and therefore in Gladys.
For my case with my LED strip, it’s now 100% functional.
Well, I just tried the latest version and NOTHING works
I even have Matterbridge telling me that the lamp is Online when I’m not powering it at all.
And there’s no more information in the logs regarding the plugin, it’s completely empty
…
Then after several minutes, some information arrives in the logs to tell me that the lamp is « disconnected », which is true but it is still Online in the dashboard:
When I turn on the lamp (physically) it goes to « connected » but there’s no interaction with Gladys and the logs indicate no action
I’m going to test by completely removing Matterbridge with a clean sweep of the repos, we’ll see.
EDIT: well no actually you can’t reset Matterbridge, I confused it with Matter
After removing the matterbridge rep, it works again and communicates in both directions: if I turn it off from Gladys, I get the feedback in the app and vice versa.
However, the colors still don’t work for me, but it’s probably my ambilight ceiling model.