When I look at who is connected on my routers status page it has an uptime column. I wonder if yours has something similar and if you notice any correlation between that uptime and when we lose the bulb.
For me, it’s 100% of the time, that uptime gets reset at the same time the bulb’s lan mode stops working which leads me to believe that the bulb has performed a reset and didn’t quite come back properly (which, in turn. is hopefully a big clue to where in the code lay the issue).
I don’t have access to my router at the moment but looking at my Fingbox logs they don’t seem to show that my bulbs went off the network when they became unavailable. I’ll check my router when I get a chance.
Yes I’m on this server but nothing is offered to me… anyone have a idea?
It’s unfortunate not to be able to downgrade, it worked very well… personally I am disappointed.
Good luck
you need to kill the app and reopen it.
2.0.6_0062 version is uploaded, remove the network restart logic, please give a try and let’s know the result.
Hi, thank you so I don’t know why my ID have change… could you add me in whitelist with this id:
1813091070
tkx
First thing I noticed is speed. Check this out, the third column is the time (in seconds) it took to connect, retrieve the power status and close the connection. A worst case of 2 hundredths of seconds, that’s 5 to 10 times faster than before the update (in my ‘no internet’ network) and probably as good as possible with my cheap equipment.
Monday 2019-10-14 16:12:26.573971
10.1.0.201 Ok 0.012926
10.1.0.202 Ok 0.007405
10.1.0.203 Ok 0.008448
10.1.0.204 Ok 0.008352
10.1.0.205 Ok 0.012237
10.1.0.206 Ok 0.008121
10.1.0.207 Ok 0.019893
10.1.0.208 Ok 0.020284
10.1.0.209 Ok 0.017132
10.1.0.210 Ok 0.018756
10.1.0.211 Ok 0.018656
10.1.0.212 Ok 0.016873
10.1.0.213 Ok 0.017278
10.1.0.214 Ok 0.019103over 20 hours, no problems with 14 bulbs.
My bulbs just disconnected, worked for a little under 36 hours.
I’m just coming up on 24 hours (5 minutes away) with no issues. They’ve remained associated to my wireless and have been very responsive. Of course, I’m weird and doing everything in-house myself. A couple questions if you would.
Did your bulbs disconnect from your network completely or did they come back (without needing to be power cycled)?
Can you ping them?
Can you connect to port 55443 (like use telnet X.X.X.X 55443)?
I am wondering if we’re having two different issues because this resolved everything for me which is what I expected. Regardless, the more info we give the better the results will be.
And, one more question, did they all disconnect or just a few?
Unfortunately, my router provides no details on a clients’ up time. Can’t also determine registration with DHCP as all of my bulbs’ IP’s are static (required to make them work with Home Assistant. However, I use a FIngbox appliance in my network and its logs did not show disconnection of any of my bulbs.
Yes
I’m unable to Telnet to any client in my network due to this error
Could not open connection to the host, on port 23: Connect failed
However, a port scan on any of my bulbs does not show 55443 (or any port) open
They all disconnected at the same time (which might be a clue)
Give it a few more days before concluding. Someone here had his bulbs working (on earlier FW build) for 96+ hours before disconnecting.
Give it a few more days before concluding. Someone here had his bulbs working (on earlier FW build) for 96+ hours before disconnecting.
Agreed, and my input is hardly the end all, I’m in my own little world but it may end up useful to have the different views.
It is interesting that they all disconnected at once as that hasn’t been my experience. Conversely, The port 55443 not open issue is exactly the problem I was (or may still have as you say).
If it continues for others and not for me then that’s a nice clue that it’s being triggered externally. If it kicks me around 36hours that will be a great clue too. Onward…
This has always been in my case. All bulbs disconnect at the same time.
I’ve always had a few go offline at different times but always at the bulbs internal reconnect timeout (which was removed to test in .62).
Soliciting others to chime in:
Are other people seeing all the bulbs go unresponsive at the same time or a few at time?
I’m interested in hearing this as well.
You need to specify the port in your telnet command, which should be “telnet ip 55443”.
Confirming that nmap (my vers 7.60) does not scan port 55443 unless specifically told to and, so, won’t normally detect it as open.
Weiwei’s test of ‘telnet ipaddress 55443’ (or on linux ‘nc -v ipaddress 55443’ is the best way to tell if the command port is open.
Yes, I know and I did. But for some reason I’m getting an error saying port 23 is closed and unable to telnet (to any host, not just the bulbs).
Pardon this statement because I don’t know your skill level, If you expected any device to accept a port 23 connection then it doesn’t tell us too much because lots of things don’t.
If, on the other hand, you’re getting refused on things that you know should have port 23 open (other than yeelight hw) that suggests (not proves) a network issue.
We need more folks to check in with their experience with .62.