Hello@Genarro_6k ,
Thanks for contacting our community.
I noticed you've already contacted us, and I suggest you contact local support directly and attach the logs. Did you receive a response?
- I know how to read logs so there is no need for Support to translate. My question was and remains is there an ALL Inclusive guide for the code, for example
2025-08-03 23:50:36 access-control[4505]: <6> 239504 Service start
for TP-Link to share for Customer consumption?. If not then why not?
- I did receive the following response from Support. Please see below!
Also, what mode is your router in? Wireless router mode or Access Point mode? Have you tried downloading the beta firmware from the link I provided?
- Router is in Wireless Router Operation Mode
If the NAS is turned off but still shows as connected, please wait for the cache to refresh: observe for 1-2 hours to see if the NAS disappears from the list (this eliminates a temporary cache issue).
If it doesn't work, please restart the router: forcefully clear the ARP cache and DHCP lease list. Unplug the power cord and wait 10 seconds before reconnecting.
- I already attempted everything you suggest here, and more, but did not wait two hours to power cycle router...
- loaded the Beta release (1.4.3 Build 20250715 rel.64226(5553) to replace Beta General Release ( 1.4.2 Build 20250603 rel.65464(5553) and the router still shows my powered down NAS.
https://community.tp-link.com/us/home/forum/topic/834722
- Any option for Customers other than waiting for the next Beta for the Beta or General release?
Best
Suppport Response
I hope this email finds you well.
I understand the AI suggested explanation does not completely address your concern. Let me look into this further so I can provide you a proper solution.
Thank you for reaching out and for sharing your detailed observations and concerns regarding the recent firmware update (1.4.2 Build 20250603 rel.65464(5553)) for your device. We also appreciate your efforts to engage via the Community forum and apologize that you haven’t yet received a clear response.
To address your primary concern: at this time, the firmware version you mentioned has been temporarily removed from the download page as our internal teams are actively reviewing feedback and reports related to its performance. While there haven’t been widespread critical issues reported, we are investigating some anomalous behavior that a few users—yourself included—have responsibly brought to our attention.
Regarding a timeline for the next general release: unfortunately, we’re unable to share an exact date for the next official firmware rollout. Development and validation cycles depend on the scope of changes required and thorough quality assurance testing. However, your feedback is certainly being taken into account, and we aim to provide a stable and improved firmware version as soon as possible
As for your secondary questions (such as log interpretation and observed anomalies), we’re happy to assist further. If you could share specific examples or observations, we can escalate them to our technical team for analysis and provide guidance where possible.
Lastly, while beta firmware may be offered in certain cases for testing or to address specific scenarios, we understand it’s not everyone’s preferred solution. We’ll ensure you’re notified when the next stable version becomes available.
We truly appreciate your patience and engagement, and we’re here to support you further as needed.
We look forward to hearing back from you. If you have additional information or feedback to provide, please feel free to let us know.
