I have tried using the yeelight app on my iPhone to connect my colour bulb . When I first used the app it connected Ok and I was able to control the bulb. It also appeared on the DHCP list on my router. Using the app I saw that a firmware update was available so set it downloading. It appeared to finish but in the app I could no longer see the bulb.
I reset the bulb (on and off 5 times) and tried to connect again but got to 25% then got to the page with a big red X appears. I also tried the MiHome app and I was able to connect to the wifi and it loaded to 100% but then goes back to the reset page. This process is stuck in a continuous loop. The bulb also no longer appears in the DHCP list on the router.
I have been stuck with this problem for a few weeks now.
Can you please assist me at connecting my yeelight? I am using the Singapore server in the Yeelight app and my account id is 1726106272
I have been able to connect to and control the bulb by setting up a personal hotspot on my iPhone (linked to my home wifi) and then connecting my iPad to that phone’s hotspot (instead of direct to home wifi). When I use the yeelight app on the iPad it completes the setup and lets me control the bulb.
However as this is using the hotspot from the phone it is no good for remote access/IFTTT.
I’m not sure why using the hotspot works as it is just connected to my home wifi.
Once I close the hotsport and enable wifi on the router the bulb does not show in the DHCP list of devices on the router and shows as offline in the app.
I’ve check the router logs after re-enabling wifi and noticed an entry:
17:18:16, 11 Sep. (921309.850000) Lease for IP 192.168.0.43 expired. MAC: 34:ce:00:88:61:6a, host name: yeelink-light-color1
The lease time is set on the router as being for 2 days, I’m not sure why it would expire within minutes of the router restarting.
Hi, my router is a BT HomeHub5. I tried to reboot the router when first had the problem but not since trying to link the bulb through the hotspot. I’ll try rebooting it later and see what happens.
I’ve tried rebooting the router but the bulb still appears offline in the app.
In the route log I can see entries for the bulb trying to connect:
13:19:42, 17 Sep. ath00: STA 34:ce:00:88:61:6a IEEE 802.11: Client associated
13:21:42, 17 Sep. ( 734.550000) Lease for IP 192.168.0.43 expired. MAC: 34:ce:00:88:61:6a, host name: yeelink-light-color1
13:23:46, 17 Sep. ( 858.880000) Lease for IP 192.168.0.43 expired. MAC: 34:ce:00:88:61:6a, host name: yeelink-light-color1
13:25:49, 17 Sep. ( 981.270000) Lease for IP 192.168.0.43 expired. MAC: 34:ce:00:88:61:6a, host name: yeelink-light-color1
From the time of the entries for the bulb it looks as though it is losing the lease after 2 minutes each time. It is doesn’t appear in the DHCP table.
I’ve tried rebooting the router again a few times but the bulb still just remains offline in the app.
In the router logs I noticed it still loses the lease after 2 mins. There’s also a lot of post forwarding requests being made but closed around the time of the lease request. Does the bulb require any ports to be made open on the router to allow it to connect?
This looks like a DHCP compatibility issue, since your router is very uncommon so we won’t be able to capture the traffic and do analysis.
Do you know wireshark? Maybe you could help us capture some packets so we can do some investigation.
With not knowing what it is you would find useful, I’ve made a log of the traffic while trying to connect the bulb to my network - when it fails at 25%
While I wait to see if the info I posted from Wireshark is any help identifying the problem, I noticed in other posts that it was suggested to post the results of pinging ot.io.mi.com and sg.ot.io.mi.com - I get:
Pinging sg.ot.io.mi.com [52.220.159.77] with 32 bytes of data:
Reply from 52.220.159.77: bytes=32 time=270ms TTL=47
Reply from 52.220.159.77: bytes=32 time=271ms TTL=47
Reply from 52.220.159.77: bytes=32 time=270ms TTL=47
Reply from 52.220.159.77: bytes=32 time=270ms TTL=47
Ping statistics for 52.220.159.77:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 270ms, Maximum = 271ms, Average = 270ms
and
Pinging ot.io.mi.com [42.62.48.113] with 32 bytes of data:
Reply from 42.62.48.113: bytes=32 time=190ms TTL=43
Reply from 42.62.48.113: bytes=32 time=190ms TTL=43
Reply from 42.62.48.113: bytes=32 time=190ms TTL=43
Reply from 42.62.48.113: bytes=32 time=190ms TTL=43
Ping statistics for 42.62.48.113:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 190ms, Maximum = 190ms, Average = 190ms
I see a lot of people are having a similar issue as my without any solution.@weiwei was the information I posted from wireshark useful? If not could you give me some guidance on what you need.
The wireshark file you provided is not helping, we can’t parse it since it’s not in pcap format.
I went through your posts again and I highly suspect it’s the compatibility issue of DHCP. Could you post your DHCP settings page of your router here?
@weiwei I’ll have another look at doing a wireshark capture and getting the information in pcap format.
I know other people with the same router and ISP as myself who use the bulbs without any problems.
Is it possible to change the firmware back to the earlier version that my bulb shipped with? The bulb connected fine first time but then did the firmware update and hasn’t connected to my wifi since. Could it be a problem with the firmware?
First of all, please connect the bulb to the cloud (through other methods, maybe hotspot). Then share your device with us and we can downgrade the firmware to original version.
Share it with 147758983.
Let us know the firmware version (if you can remember).
@weiwei I’ve added the bulb through a hotspot on my phone to my account 1726106272 and shared it with the account you mentioned. I’ve connected via the Singapore server.
The bulb is currently showing as firmware version 1.4.1_52 I’m not sure what version it was when I received.
