Deco M4R red light blinking after a while
Deco M4R red light blinking after a while
My home network has five TP-Link Deco: three of them are M5 while the other two are M4. The M4 are V2. FIrmware version is the latest for any Deco.
All of them are connected through ethernet cable. One of the M5 is the principal device. The Deco network is configured in AP Mode, as I have a separate VDSL router which manages DHCP, firewall and internet routing. All of these devices are connected to the same ethernet network.
The issue I have is after a while (about 1 or 2 months), both the M4 start blinking red light, approximately at the same time. They are unable to connect to M5 master for some reasons. When this happens, all of the M5 Deco's are fine and any wireless client connected to the M5s works just fine. The red blinking Deco M4 are still able to accept wireless clients, but then the clients cannot reach the internet.
I have already ruled out any hardware connectivity issue, seems like the M4s are not able to connect after a while to the M5 and the only thing I can do is to power them off and back on to regain the M4 connectivity. The Deco are "near" each other to be able to connect wirelessly if for some reason the ethernet cable fails, but not very near (5+ meters and some tick walls in between).
I have all of them since 3+ years and they always showed the same issue, no matter the firmware updates in the past years. This blinking only happens on M4 Deco, not M5 which are always functional. My father home has 2x Deco M4 with similar setup and he never experiences the same blinking red light, so seems like the issue is only happening when used in conjunction with M5.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi, Thank you very much for the feedback.
Is there any network switch used to establish Ethernet Backhaul among Decos?
If yes, can I have the model number of the switch?
Can I have a picture of the current network topology?
Is there any possible to modify the network topology to be like:
main VDSL router---network switch--main Deco M5 #1
\--satellite Deco M5 #2-----<Cable>-----Deco M4 #1
\--satellite Deco M5 #3-----<Cable>-----Deco M4 #2
Wait for your reply and best regards.
- Copy Link
- Report Inappropriate Content
@David-TP hi. I have same issue with m4r which fails and the other 4 m5 works fine
- Copy Link
- Report Inappropriate Content
Hi, is your Deco M4 also connected to the M5 via an Ethernet cable?
If however, it is wireless connected to the Mesh system, I think you could try the 1.7.0 beta firmware here in case the disconnection is due to this satellite M4 didn't connect to the nearby Deco M5.
Deco M4/S4_V2 Support Connection Preference
You only need to update the M4 and the login IP address of the M4 can be found on the Deco APP, such as 192.168.71.250 here.
Thank you very much and Best regards.
- Copy Link
- Report Inappropriate Content
@David-TP Thanks for your reply.
Here is my network topology. As you can see I'm a loyal Tp-Link customer :). Everything is connected through the ethernet backhaul. I am not leveraging the second ethernet port on Deco's.
The Deco M5 #1 is the main unit. What I can do is to move it to be directly connected to Archer router instead of M4 for testing purposes, but I would prefer to have faster WiFi as they are in the current configuration.
The Deco's work well for 1 or 2 months, after that period I start having the red blinking light in both M4 units. The M4 are still providing wireless access but no internet connectivity - seems to me they aren't able to reach the internal network. I am unsure of the triggering factor of the red blinking light, this might be a time issue (after X hours), or a spike/sink from the electric company, I don't know. But this is happening with that frequency. My father in his house has 2x M4 and never experienced any issue with them, so seems like it has something to do between M4 and M5. Again, hard rebooting M4 brings back to normal operation.
I think I can give a try to the beta firmware as you suggested in another reply, even though my Deco's are connected through ethernet. I don't know if this might help in my case but I can give it a try
- Copy Link
- Report Inappropriate Content
Thank you very much for the details. They are very helpful.
I noticed you have updated one of the Deco M4 to 1.7.0. Did it help improve the network stability?
Wait for your reply and best regards.
- Copy Link
- Report Inappropriate Content
@David-TP Everything is working fine so far. I've updated just one of the two M4 to verify if it will improve over the old one. I've had the last red light blinking event last week, so I guess it will take some 4+ weeks to have again the same issue.
If the 1.7.0 is going to fix that, I guess I'll have the red blinking light only on the other M4 which I didn't update. Glad that the updated M4 now has the IoT wireless network.
I'll keep you updated in this thread if something good or bad happens.
Thanks for the help so far.
- Copy Link
- Report Inappropriate Content
@David-TP brief update, today the Deco M4R I had updated to 1.7.0 beta firmware was blinking the red led.
The other M4R with the latest stable release wasn't affected and was still working.
I had to hard reboot the faulty M4R by pulling the plug to have it back online, so seems that the beta firmware hasn't fixed this issue.
- Copy Link
- Report Inappropriate Content
Hi, Thank you very much for the update.
Have you tried to replace a new Ethernet cable to connect Deco M4 to the Mesh system?
By the way, Which one do you update to 1.7.0, the Deco M4#1 connected directly to VR1210 or the Deco M4#2 behind TL-SG105?
Since it takes 1-2 weeks to repeat the issue once, It is a little difficult to locate what has happened.
Moreover, Deco units in AP mode work quite similarly regardless of the models. If possible, maybe you could try to swap Deco M4_1.7.0 with one of the Deco M5 to see whether the disconnection constantly follows up with the Deco M4.
Best regards.
- Copy Link
- Report Inappropriate Content
@David-TP Happened again today, both the M4R Deco became suddenly offline - red led blinking. Had to restart them.
Unfortunately, the cables are in the wall - cable between Archer and TL-SG108 #1 and #2. Archer and M4 #1 are 1 meter away, Archer has no wifi enabled.
Cables have no more than 2 years and sustain the whole wired traffic and they work well. The whole wired clients are attached to TL-SG108 #1, #2 and #3. In my house there are like 20 IoTs, both wired and wireless, up at any time and never had issues. More than 5 PCs are powered on/off, not counting mobile phones/tablets.
I have updated to 1.7.0 just the M4 #1. M4 #2 is at the latest stable, automatically updating. Doesn't seem the 1.7.0 fixed the red blinking issue.
The two M4 are very far and their wireless network won't overlap. In my father's house, he's using just two M4R in AP mode and they work flawlessly. I again suspect the issue is mixing M5 and M4 in the same network. Never happened on M5 to become disconnected - M5 #3 is very far and cable runs underground on the exterior of the building and never had any issue with that, M5 #1 and #2 partially overlap the wireless network, again never had any issue with them.
Maybe it has to do with some power shortages, power holes in the grid, transients, but the rest of my equipment didn't reboot and stayed up and running, so it would sound very strange to me.
- Copy Link
- Report Inappropriate Content
@David-TP Happened again today. One of the M4R was shut-off and powered two days ago as I had to move it to a slightly different place in the same room. Nevertheless, the two M4R were put offline at the same time.
I am suspecting an issue in the M5 main unit (AP mode) while dealing with M4R(s). The other M5 units were still working as usual. At least this M4R which has been rebooted is within reach of wireless connection to the main unit, although they are connected through cable. In any case, when M4Rs are blinking red, there is no way to let them reconnect to the main unit unless they are rebooted by pulling the plug and reconnecting it.
Everything has been updated to latest available firmware, no changes.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 801
Replies: 12
Voters 0
No one has voted for it yet.