Deco X50 outdor buckhaul bug
I have been researching and troubleshooting my network for many months (since I bought the system in December 2024) and I came to the conclusion that X50 outdoor units must have a system bug ðŸ˜
Over these months I have simplified the system to rule out anything else, thrown away managed switches, simplified the distribution network, even bought an expensive BE65 unit as main Deco (which I wouldn't normally need), since I have seen that processor on X50 indoor unit was often highly loaded. I even bought more X50 outdoor units to rule out coverage problems 😠Overall, I have spent 3 times more money then what was considered sufficient at start..
My system is quite simple, ISP router connected to main deco BE65 (set as router). Main Deco connected to unmanaged switch SG1024D, and satelites connected to the switch, 3 x indoor X50, 4 x outdoor X50. For the sake of testing I disconnected all my outdoor X50 units and discovered that my network is OK during that time. As soon as I connect a single outdoor X50 unit my network start to have issues again, and I believe that this part of the log says all about it:
Sat May 24 07:51:59 2025 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1746: Error: can't find ifname[eth1.591] in eth_ifname
Sat May 24 07:51:59 2025 daemon.err /usr/bin/apsd: loop_avoidance_flush_switch_fdb_table:338: Error: set cmd:ssdk_sh fdb entry flush 1
It seems to be OK when I disconnect wired backhaul and go wireless for the outdoor X50 unit. I didn't spend extensive amount of time on testing, as I just recently discovered this dependency, but one thing is certain, I am no longer seeing these errors! and I also found one single post from user seeing exactly the same dependency: https://community.tp-link.com/us/home/threads/topic/814926
I have been continuously struggling with my IOT devices connected to X50 outdoor going offline and me keep restarting the IOT devices all the time to bring them back alive, and over and over again.
Also, lots of other instabilities in the whole network, e.g. both indoor and outdoor cameras difficulties in live view, or devices count getting freezed, no new devices being shown after connection, etc. I have done several hundreds of restarts for the whole system over the months.... and reached a point to start analyzing logs...
It is also quite confusing with regards to firmware version. Cameras came with version 1.2.8 Build 20240914 Rel. 35513, while when i check the latest for my region it says that only lower version is available: Deco X50-Outdoor(EU)_V1_1.2.6 Build 20240723. I have just tried a lower version, but that didn't solve the problem either ðŸ˜
I am really tired of this issue, I bought the system to improve my network, and it was supposed to be a plug and play solution. Before, I had many archer routers spreaded around with many local wifi networks and this system was perfect comparing with the struggle I am going through now.
I really count that someone from Tplink team pick on this issue and solve it, during my resarch I read that many users are actually waiting for a new firmware upgrade for tens of other reasons.
BTW, I am aware that this problem has to do something with guest network VLAN, I don't normally need it but have tried both, having it switched ON or OFF, and this doesn't make any difference.
Kind regards,
Mark
Hello David & Parker,
I would like to thank you for all the support I have received so far.
You have managed to troubleshoot my system to the point that I no longer have any issues, while running 130+ IOT devices.
No more random disconnections / IOTs getting offline requiring manual power off and on 
The main remedy is the new (I assume beta) software, especially with focus towards X50 outdoor units that was applied over my system which significantly improve overall experience with 2.4Ghz network.
The system is running so smooth that I can't still belive it after all this time I have spent on troubleshooting.
I must admit we also discovered a failing switch on top of everything which also contributed to the overall problems.
But it was not the main issue, I believe it has failed due to outdoor enviroment, even though it was mounted in IP68 cabinet.
This problem was anyway transitional only, as I didnt have it in the begining or in the end, it was part of the troubleshooting process to allow for wired backhual also in the garden.
Now, the system works perfect even with the garden Deco staelites operating through wireless backhaul, so don't see a strong need for wired backhaul any more.
Thank you again!
Kind regards,
Mark
Hello David,
Thank you for your quick reply.
In general the answer tou your question is YES.
I have done some more tests with all of the four X50 outdoor satelites connected wirelless only.
Of course this is not an easy setup as three of them are able to be connected only via other satelites, and only one directly to main deco.
In few cases the signal is also week, but despite of that all of the garden IOTs (bulbs, sockets and cameras) are connecting properly and are up to 95% stable comparing with when I connect staelites through ethernet backhaul.
I notice that there are still some of these errors appearing, but it is only ocassionaly and I guess this might be due to more complex wireless backhaul and week signals beteween satelites, where I am physically not able to connect all my satelites to main deco (due to higher distances and additional barriers).
Thu May 29 19:52:09 2025 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1746: Error: can't find ifname[ath0] in eth_ifname
Thu May 29 19:52:09 2025 daemon.err /usr/bin/apsd: loop_avoidance_flush_switch_fdb_table:338: Error: set cmd:ssdk_sh fdb entry flush 1
When I connect ethernet backhaul, I am getting these errors continously, more less every second and the hell break loose again 
All of these garden IOTs are of the same type as I also use inside the house.
I never had any problems with IOTs inside the house, its only with those being connected via X50 outdoor units....
So in my view it is pointless to spend time on investigating the IOTs themself, based on the facts given above.
When it comes to red flashing, I have only observed it every time I restart the system.
I didn't notice it during normal operation, while the isuse based on the logs seems to be a continous struggle when outdor units are connected via ethernet backhaul..
Kind regards,
Mark
Hello David & Parker,
I would like to thank you for all the support I have received so far.
You have managed to troubleshoot my system to the point that I no longer have any issues, while running 130+ IOT devices.
No more random disconnections / IOTs getting offline requiring manual power off and on
The main remedy is the new (I assume beta) software, especially with focus towards X50 outdoor units that was applied over my system which significantly improve overall experience with 2.4Ghz network.
The system is running so smooth that I can't still belive it after all this time I have spent on troubleshooting.
I must admit we also discovered a failing switch on top of everything which also contributed to the overall problems.
But it was not the main issue, I believe it has failed due to outdoor enviroment, even though it was mounted in IP68 cabinet.
This problem was anyway transitional only, as I didnt have it in the begining or in the end, it was part of the troubleshooting process to allow for wired backhual also in the garden.
Now, the system works perfect even with the garden Deco staelites operating through wireless backhaul, so don't see a strong need for wired backhaul any more.
Thank you again!
Kind regards,
Mark
