JeeLight Bug

Kubasaak

JeeLight stops sending in commands (probably) to the lights after 10-20 seconds of use. When I try using Ethernet and turn off wifi, it also works flawlessly for about 15 seconds and then gets stuck, the program does not freeze, but what ever i click on, the lights don't respond. Only the refresh button reconnects them but it says ''unreachable'' and 1 second after it says connected, but the lights do not respond to either starting ambilight or changing colors. I need to click refresh many times for it to properly connect. I tried using Kodi app on windows, and the addon YeeMee, and that works nicely, but the transition between the colors is not smooth as on jeelight and this can be only used on the Kodi app, so I can't use it for games etc. It's defo not about pc performance, that's fine to me. Any idea what it could be?
Thanks for your reply!

Rayonner

Hello, I have a similar problem as you. After investigation with wireshark it appears that yeelight answer "client quota exceed" afterfew second of using ambilight. It's strange since jeelight use music mode. This problem appears only on my w10 pc. I have another w7 pc running jeelight ambilight without getting this error. I have no idae how to solve it.

Update: problem solved by updating java /removed some vmware virtual ethernet interface

terrainer

I have this issue as well. reinstalled Java, but that did not work. Don't have VMWare Virtual Ethernet Interface.

terrainer

my issue is also with "client quota exceeded"

Blueforcer

"client quota exceeded" comes from the Yeelight bulb firmware.
Reinstalling java couldnt help here of course.

terrainer

Even after a factory reset, it's still occuring. The firmware for these bulbs hasn't been changed in a long time, and others have reported it to be working. What could be causing the issue? With reinstalling Java, I was just doing what others said had worked for them. Firmware is 1.4.2_0076

Blueforcer

i have not used jeelight for a long time. I also don't know if anything has changed in the last year in the firmware. If i find the time i will have a look at it

terrainer

if that's possible I would be greatly appreciative

TedSal

hello guys, i had the same problem and i found that the issue was only the firewall;
i solved it using this guide
i'm guessing it will work only if you are using the original windows firewall.

terrainer

I have allowed Jeelight through my firewall, but I'll try this later when I'm on the PC
EDIT: this did not work for me unfortunately.

erik

I have this exact same issue.
It just freezes and then starts automatically working again after half a minute or so.
Java is added into my Firewall and I am on Windows 10

Blueforcer

cannot recreate this error. after some month now .running a yeelight in abmiblight mode again for couple of hours now, without problems

erik

So I just reinstall my PC (windows 10)
The problem is now solved. So I guess there is a strange issue going on if you run it in combination with something else.
Works perfect now 🙂

FrankJane

i followed that video as suggested by TedSal but problem is not solved at my end either.

Freejack

Same problem on my machine also. Too bad there is no fix and problem is hardly reproducable for others.

djbanek

Ich habe das gleiche Problem. Meine Vermutung lag erst auf einem Java Update und auf dem JeeLight 2.4 Update. Ich würde nun aber auch denken, dass es mit einem Windows 10 Update zu tun hat.
Es funktioniert nach einem "reset" (App neu starten, Lampen mit Alexa umsteuern) vorerst für einige Sekunden. Dann friert der Lichtwechsel wieder ein um später wieder zu beginnen.
Kann man mit irgendwelchen Logs und co. irgendwie unterstützen?

Blueforcer

Das Problem tritt auf wenn es mehrere Netzwerkadpater gibt.
Jeelight fragt zum Aufbau des TCP Server Windows nach der Lokalen IP.
Wenn es aber mehrere gibt, gibt Windows den erst besten zurück. Ob richtig oder falsch.
ist es die IP einer VM oder VPN, kann sich die Yeelight Lampe natürlich nicht verbinden.
In der nächsten Version kann man die Lokale IP manuell korrigieren. Bis dahin -> Alle anderen Netzwerkadapter deaktivieren

The problem occurs when there are multiple network adapters.
Jeelight asks Windows for the local IP to set up the TCP Server .
But if there are several, Windows returns the best one first. Whether right or wrong.
it is the IP of a VM or VPN, the Yeelight lamp can't connect of course.

In the next version you can correct the Local IP manually. Until then -> deactivate all other network adapters

djbanek

Also Netzwerkadapter habe ich eigentlich nur einen. Das war auch schon immer so... Ich habe mal den Workaround aus dem Video befolgt und abgewandelt.
Die Firewall gibt jetzt eingehend und ausgehend alle Java Prozesse frei und zusätzlich habe ich jeweils java.exe und javaw.exe ergänzt.

Im Moment scheint 2.4 reibungslos zu funktionieren. Subjektiv sogar noch besser als 2.3... Alles extrem flott, flüssig und sauber.
Vielen Dank für die Unterstützung und vor allem das Tool!!!

djbanek

Problem tritt sporadisch immer noch auf... 🙈 Was könnte man noch probieren?

Blueforcer

djbanek Probiere mal meine aktuelle Entwicklungsversion:
https://cloud.blueforcer.de/s/LLcGYceEkgyEdTb

Changelog:

Zeigt die aktuelle lokale IP in den Settings
Capturespeed um ca 40-50% gesteigert.
Weichere Übergänge

snowyleopards

Blueforcer This solved my problem, thank you!