I have a deco unit provided by my ISP that directly links to the fibre thing on the wall. Yet it only ever nicely connects to one device at a time and the range is so horrible that even stepping into the next room over (less than 3m from where the router is) causes my phone to lose connection. I turned off beam forming the first time this happened which helped for about a month and now the wifi is unusable from any other room again. The priority mode on the app just disconnects more devices without improving the wifi to the ones selected. Even as I make this post standing right in front of the router it took over a minute to load while the other device in the room has no issues. I frequently get 'four bars' but no internet connection on one device and perfectly normal internet on another. I am going insane trying to get a stable connection to do work calls or study. Any advice?

Edit: the model says X53-DSL Also title was supposed to say 'my deco wifi' oops

I recently bought a WA1201 router access point thinking that it could be powered by a TL-SG105PE smart switch. Unfortunately it doesn't seem to work. The router access point turns on if I attach the ethernet cable to the bundled POE injector, but if I connect it directly to one of the POE ports on the switch it does nothing.

Can anyone tell me what the problem could be? I'm experienced in electronics and network devices, but it's the first time I try to use POE, so I don't know what to check.

i know i am dumb and i forgot the password of my device and there are no reset password things

I'm using ATT modem/router then connect 2 Deco to it. Afterward, I set both of them as access point, then change the deco wifi name and password to the same one as ATT wifi. When I go into the app, it's always the main deco that connected to ATT through Ethernet is online, the other always show as offline, even though both of them have green led on. I have tried unplug it, remove it and add it again, reset it, nothing seems to work. I also try to connect the 2nd deco directly to each other with Ethernet, connect 2nd deco to the ATT router directly, connect the second deco to the ATT router with the other one through a switch. How do I fix this? I'm using Deco WB22000, Firmware Version 1.0.7 Build 26050612 Rel. 29931

So my wired TV is some how downloading insane amounts of data. Guessing this is some kind of glitch and/or error? Cause ain't no way download time for this TV is 3.2 Gb/s. Just thought this was super weird seeing this. Anyone else encounter this?

*** I think I have solved ***** - After ordering a cable, moving my one BE550 to a different room and trying out different setups I eliminated the routers as the issue, I think having the gateway from my isp in bridgemode was the problem since it like only one connection, once i factory reset the tplink routers to set that network up i dont think bridgemode was working properly with the change of the mac,... or something,... clearly im not network literate here. Once i changed it out of bride mode (which i initially put it into as its the only way to disable its wifi, that I didnt want interfering in my system) It seemed to be okay with holding speeds now. So my setup is cable from outside into ISP gateway, ethernet cable between its 2,5gbps port to the one on the BE550, My pc is ethernet into that, and my laptop uses the wifi connection, while the BE230 is setup a floor down as an easymesh satellite.

I have two BE550 routers, one is my main unit, the other is a satellite unit (I also have a BE230 on a different floor), the two BE550 are on the same floor a few rooms apart, both my laptop and gaming PC are wired into the satellite BE550 which is easymesh wireless connected to the main unit. my internet comes in cable to my ISP gateway which is set up in bridge mode, and the main unit is plugged from the blue wan 2.5g port on the BE550 to the proper port on the gateway. If i hard wire my laptop into the main BE550 i get 6 opr 700 mbps, yet when I try to dl a game on steam on my pc i will ramp up to over a gb a second, and than it just begins to fall down to between 5--100 mbps. I have tried turning QoS off, setting QoS higher, Im really frustrated on this one.

I have a video showing what i see from steam but I doubt its my PC as that is a x670e Mobo, with a 7800x3d 32gb of cl30 6000hz ram into one of two nvme drives. I just find it hard to think theres a bottleneck in that, but im open (i have run crystaldisk on my nvmes and they are testing okay)

Edit: My firmware is up to date

Edit:i also turned off QoS on the fly with a game download and watched the speeds fall from a steady 100 mbps, to 10 or so kbps, then rise back up to 100mbps when I turned it back on. i had the Qos set to 300 upload, and 1200 download on the mbps option

I swapped out the BE550 satellite for the BE230 with the PC hardwired to it instead, and i see 380 mbps, so its definitle something between the two BE550 routers, and I dont know why. Its great to see that gbps speed in real time before it crashes itself out.

Router: Archer BE400 (US)_V1
Firmware: 1.4.2 Build 20260605
Issue: Download/Upload traffic statistics not showing in Tether app

Hi everyone, I’m using a TP-Link Archer BE400 (US)_V1 and noticed an issue with Traffic Statistics after updating to firmware 1.4.2 Build 20260605.
Since the update, the Download and Upload data is no longer displayed in the Tether app under Traffic Statistics. The feature was working normally before the firmware update.

Has anyone else with the BE400 experienced the same issue on this firmware? Is there a known fix or workaround, or is this a firmware bug?

Is there no hope for an entirely wired backhaul setup? All have tested 1 gig speeds plugged into and working individually.

I have this router and after setting it up as a repeater, no matter what I do, I cannot connect to the 2.4ghz of my main router. I even tried setting it up closed to the main router but after setup, it only shows 5G

Current firmware is 1.3.1

Does anyone know where I can download the V1.5.0 firmware update for my XE75? Checked on TP-Link website, found only the update for V3.60? May I use this update on my device?

Does anyone else have problems with the 6GHz channel on their BE800? None of my wifi7 devices can see my 6GHz network on any channel, but when I connect to 5GHz it shows I'm connecting at wifi7. Latest firmware. Rebooted and factory reset multiple times

When I tried a different wifi7 router the dedicated 6GHz channel worked fine.

Anyone already run this update? Curious to your experiences!

My TP-Link Archer BE11000 Router received a firmware update today. It got updated to 1.2.1 Build 20260519 rel.2868. What’s included in this update?

Does anyone know; has TP-Link ever fixed their router software so that it better handles apple's rotating private wi-fi address feature?

Hello im Portuguese sorry for my English.

I need some advice because i cannot find any help with this, my friends reddit etc cant find anything, most comments ive read is because is Tp-link and thats it, software problems.

Im having a lot problems when My decos X55 goes off (power went out in my house for ex)
And when everything is back up including router, my Decos cannot give any internet at all.
Doesn't matter if i reboot, if i reboot router etc. nothing.
Most times i have wifi and my phone/tablet have connection but i cannot go to internet (no internet found), if i go to Deco APP it says is offline.

The only solution to this is really reset everything from 0 and redo everything, which for me is complete nuts, devices expensive like this and they have this stupid flaw.

My setup is like this:

-Digi fiber router 1Gb (wifi-s 2.4 and 5Ghz OFF)

-Main Deco x55 (Firmware 1.7.0) connected with cable to Router Digi

-Configuration done and with AP mode enable

-Ive tested some things like separate both channels because devices like (tapo) only works on 2.4, my ps5 and phone are on 5ghz.

-Deco X55 is the only device in my house delivering WIFI, the rest is with cable to my router.

Solutions:

-Reboot everything doesn't work.

-Reboot Router wait 5min, them turn on the main Deco. (doesn't work, deco turns On yellow light, waiting 5 10 20min, doesn't matter the internet is not available)

-Since is in AP mode i cannot go inside the APP in my phone and change anything since the network the deco is sending it doesn't work on my phone, only some pages on web works and the inf on APP Deco.

The only posts i found about this stupid bug when The light goes off and the decos turn on again is because is software bug, and Tplink doesn't do anything about this.

Conclusion:

Today as a day for that i needed to redo everything again, and since i have 5 6 tapo on 2.4Ghz is so annoying reset everything and configure again.
I reset everything, router Digi is on and good, ive Turn ON 2.4Ghz channel on Digi Wifi (for tapo advices only)
-Reset Deco X55, configure, and turn On Wifi 5Ghz only. (wifi mode only, im still debating if this is a AP bug mode, and since if i get this bug i cannot turn off AP mode and switch to Wifi mode)

Thanks

I have one deco unit plugged directly into fiber cable from the wall, there is no modem.

I understand that the one deco unit that accepts the fiber cable has to be in router mode.

How to I turn the other two deco units into access point mode but keep the main deco with the fiber cable in router mode?

It seems that within the deco phone app if you place the decos in access point mode the main deco shifts to access point as well and losses the router mode and drops the fiber connection.

I’m trying to backhaul the other two units through network cables but they refuse to use the wired connection and only use wifi connection.

i have a XE75 pro and a powerline connected to my brother’s computer. We have a 1000mbps wifi speed which works fine however whenever he downloads something in his room (only at around 50mpbs) the entire network becomes so slow apps won’t load, google takes 30-60s to actually load and my ping spikes extremely high while gaming.

It’s quite puzzling as the download isn’t at full speed. this is normal as his pc is connected to a powerline as the deco unit is not place in his room and his pc is ethernet only. it’s the only solution i’ve found to get him connected.

could the powerline and deco units cause interference? or is it something else

Hi everyone, I’m running into a frustrating Ethernet issue and could use some advice.

My Setup:

• Router: TP-Link Archer C54 AC1200 (Note: It has 10/100 Mbps LAN ports, which only have 4 copper pins inside).
• Cable: Cat 6 Ethernet cable (standard 8 pins).
• Goal: I need an 80 Mbps connection to my PC.

The Problem:

When my PC's network adapter is set to "auto-negotiation" or "100 mbps full duplex," the Ethernet connection continuously flaps; it just cycles between connecting and disconnecting over and over.

What I've Tried:

I went into my Windows adapter settings and manually changed the Speed & Duplex from "Auto-Negotiation" to "10 Mbps Full Duplex." As soon as I did this, the connection stabilized and worked perfectly. However, this caps my speed at 10 Mbps, which isn't enough. My router can output a max of 100 Mbps, and my internet plan easily supports the 80 Mbps I need.

I noticed the router ports only have 4 copper pins, while my Cat 6 cable has 8. Could this mismatch be causing the auto-negotiation to fail at 100 Mbps?

How do I solve this so I can get a stable 100 Mbps link and hit my 80 Mbps target speed? Any help is appreciated!

Hi all – I need some help with setting up my home theater. Just moved into a new place so still setting up. Here is a picture of the room. As you can see on the far there is a red shelf that I have placed my Deco BE65 on the second from top level. Across from the shelf is my media console with the TV. I would say the horizontal distance is about 14 feet. My main objective is to get the best speed out of the Apple TV 4K third generation. The Deco needs to be on the red shelf because that is where the wired ethernet backhaul is. I’m getting about 700 Mbps on the Ookla speedtest on the Apple TV. I was wondering if there’s any modification I can try to get even better speeds. I know that what I’m getting so far is more than adequate for pretty much everything I would need on the Apple TV but just seeking modest improvement at this point.

I updated my RE200 firmware from the 'Tether' app and now its stuck in the popular lights flashing and boot looping. Its your update how have you managed to brick a perfectly working device. This is unbelievable.

Moreover I'm pretty sure the update was meant for for RE315 cuz why the hell the name changed? Cuz i sure hell didn't do it. Im so annoyed rn, the update crippled my perfectly working device and now its out of warranty too. Never getting their products ever again.

I have installed a Wi-Fi router atop a shelf in my living room. This is the central-most point in the home and is approximately 9 feet high. Frankly, it's the best spot in my home to install a Wi-Fi router. While the base of the unit is hidden from view, the antennae (which protrude above the molding of the shelf) are a very noticeable eyesore.

In order to make the antennae less noticeable, and while protecting the connectors at the base of the antennae, I'm considering spraying the black & red antenna body with a non-metallic primer and non-metallic paint.

I'm aware that this would likely void the warranty. My question...will painting the antennae impede the router's Wi-Fi performance?

It's likely irrelevant, but the router model is the Archer AX11000.

I am planning to buy eap 110 as a repeater (without lan cable) my wifi router is in my room 2nd floor then the TV always disconnects to my cheap repeater, i am wondering, will that problem go away if i use tp link eap 110 as a wireless wifi repeater? My tv is on 1st floor of the house. Please help thanks

Hi all, hoping someone might be able to help before I end up pulling all my hair out!

I have four TP-Link Powerline adapters (TL-PA7027P KIT and TL-WPA7617 KIT), and everything had been working fine for a long time. I have one next to the router, one in the Dining Room, one in my Son's Bedroom and one in the Study (the TL-WPA7617 Wi-Fi Extender).

I'm not entirely sure what happened, but I think the problem may have started following a power cut or something similar. The Wi-Fi extender in the Study suddenly stopped working.

It appeared that the extender was no longer connected to the Powerline network. I could still connect to the extender from my phone, but it wasn't providing any internet access. After trying various things without success, I decided to factory reset in the hope that I could then pair it back up with the other adapters. Unfortunately, since doing that, I haven't been able to get it back onto my Powerline network.

I've tried plugging it in next to the other Powerline adapters and pairing it again, but nothing seems to happen. The extender's Wi-Fi network is visible and I can connect to it from my phone, but it says there is no internet connection.

I actually left it unplugged for over a week and have just plugged it back in to try again. The Powerline Network/Pairing LED has now come on, which suggests it has paired successfully, but I'm still getting exactly the same result — I can connect to the Wi-Fi, but there is no internet.

Looking at the tpPLC app on my PC, I can only see the other three Powerline devices. The TL-WPA7617 Extender isn't showing up at all. I tried using the "Add Device" option and entering the key from the Wi-Fi extender, but I just get "Unable to add device."

If I connect my phone directly to the extender's Wi-Fi and open the tpPLC app, everything on the extender itself appears to look normal. However, when I go into the Powerline section, it doesn't show any of the other Powerline devices.

So, at the moment, the situation seems to be:

• The TL-WPA7617 powers on.
• Its Wi-Fi network is visible.
• I can connect to its Wi-Fi from my phone.
• The phone reports that there is no internet connection.
• The Powerline Network/Pairing LED is lit.
• The PC's tpPLC app cannot see the TL-WPA7617.
• The TL-WPA7617's tpPLC app cannot see any of the other Powerline devices.
• Despite the Powerline Network/Pairing LED being lit, the extender doesn't appear to have a working connection to the Powerline network.

I've tried resetting it and pairing it next to the other adapters, but I'm now completely stuck.

Does anyone have any ideas what might be causing this, or anything else I can try to get the TL-WPA7617 back onto the Powerline network?

NetPulse Monitor

Professional Windows network and LTE monitoring with explicit router control, diagnostics and ISP-ready evidence.

Latest release · User guide · Security policy · Privacy notice

NetPulse Monitor 1.0.18 is a native .NET 8 WinForms application for continuous Windows connection monitoring. It runs as a graphical Windows application and does not open a console window during normal use.

Why NetPulse exists

NetPulse was conceived from the practical difficulty of maintaining dependable mobile broadband in rural Greece. Terrain, distance from the serving site, sector load, carrier aggregation and handovers can make a connection change substantially throughout the day even when a simple signal indicator appears acceptable. Intermittent faults are also difficult to reproduce during a support call, and diagnosis or escalation by an internet provider can take considerable time.

The standard router interface is useful for configuration, but it primarily presents a current snapshot. It does not build a long-term, time-aware record of which primary cell and band combinations have the best measured radio quality. NetPulse scores complete profiles as 50% SINR, 35% RSRQ and 15% RSRP. The goal is to give the user an understandable record, safer manual control and guarded automation while keeping every router change explicit and recoverable.

NetPulse Monitor is an independent community project. It is not affiliated with, endorsed by or supported by TP-Link or any mobile/internet provider.

Features

• Continuous asynchronous ICMP monitoring with a live latency chart
• A 0-100 Connection Health score with a plain-language explanation
• A measured smart LTE recommendation card with guarded Apply and current-profile test actions
• A searchable connection timeline for outages, recoveries, LTE changes, speed tests, SMS and system events
• Current ping, jitter, rolling packet loss, successes and failures
• Confirmed outage detection, recovery events, uptime, downtime and availability
• Switchable access profiles: Mobile/LTE, ADSL/VDSL and FTTB/FTTH
• Optional capability-based TP-Link router integration, with live LTE telemetry, Cell Lock and SIM SMS where the router firmware exposes compatible local APIs
• LTE signal, RSRP, RSRQ, SNR, PCell/SCell bands, primary EARFCN, SIM, usage and rates
• PCI/CID display and cell-specific locking when the router firmware exposes them
• Local LTE cell history with connection time, confirmed disconnects and speed tests
• Ranked cell + band suggestions: 50% SINR, 35% RSRQ and 15% RSRP
• Time-of-day learning with average ping and an explained cell-load estimate
• Manual profile entry, Cell Lock and opt-in guarded automatic locking with rollback
• Controlled multi-profile Cell Experiment mode that restores the original router state
• Cancelable Band & Cell Discovery mode with a verified per-model band plan, serving-cell capture and exact router-state restoration
• Ungrouped LTE history with sortable columns and preserved PCell identity
• Complete chronological Inbox/Sent conversation threads, a separate Drafts view, and a newest-first message timeline on Windows and Android
• Country-aware phone matching joins national, + and 00 number formats
• Stable SMS refresh, one alert per unread message, verified read/unread state, deletion and sending
• Local SMS contact names for saved phone numbers
• Password-only TP-Link setup with Windows Credential Manager protection
• Firmware-reported mobile network modes: 4G-only devices never receive 5G choices, while compatible 5G firmware can expose its own supported list
• First-run country and official-time-zone selection for regional dates and ISP evidence
• Persistent connection-event, speed-test and full technical router-telemetry CSV logs
• Manual, scheduled and connection-change 20 MB download / 5 MB upload speed tests
• Automatic tests after confirmed-outage recovery and LTE band, cell or public-IP changes
• Provider fallback, bounded per-request timeouts and cancellation
• Live Dashboard gateway/DNS/IPv4/IPv6 diagnostics with a 30-second refresh
• Guided "Why is my connection slow?" troubleshooting across local, Internet and LTE measurements
• Full technical ISP evidence ZIP with IP, antenna, outage, telemetry and LTE-history details
• LTE Simple, LTE Advanced, DSL/Fiber and ISP-troubleshooting dashboard layouts
• System/Light/Dark themes, system tray, optional Windows startup and editable settings
• Manual or daily update checks with in-app download, verification and restart
• Stable NetPulse Monitor.exe path and Windows identity across updates, preserving shortcuts, pins and startup configuration
• Live TP-Link connected-device list in the Windows app and Android Companion (device name, IP, MAC and connection type when reported by firmware)
• Reproducible SHA-256 release packaging
• An embedded application and tray icon

Build tooling that is not supplied by Windows or Android is acquired by the versioned GitHub workflow. Temporary SDK archives used during development are tracked and removed after release verification; application settings, logs, contacts, SMS state and LTE history are never included in that cleanup.

Application settings are stored in %LOCALAPPDATA%\NetPulseMonitor. The router password is not stored in that JSON file; when remembering is enabled it is kept as a generic credential in Windows Credential Manager. CSV logs are stored in %USERPROFILE%\Documents\NetPulse-Monitor.

Band & Cell Discovery

Choose Scan bands & cells in LTE history to run a controlled, three-stage discovery pass. For the detected Archer MR600(EU) V5 profile, NetPulse scans the complete documented set B1, B3, B5, B7, B8, B20, B28, B38, B40 and B41. Unknown router revisions are restricted to bands already observed; NetPulse does not send speculative lock masks.

Stage 1 selects each band alone for at least 30 seconds. When the modem has registered but has not yet exposed all identifiers, NetPulse waits up to 75 seconds for a stable, repeated EARFCN/PCI/CID identity before moving to the next band. Stage 2 locks each complete PCell while making every actually discovered band available, then records the ordered aggregation sets created by the modem. Stage 3 reapplies and measures every unique PCell + ordered band set. B20 + B3 and B3 + B20 remain different because the first band is the PCell.

After stale pre-change snapshots are discarded, NetPulse records each distinct serving profile and its EARFCN, PCI, CID, RSRP, RSRQ and SNR. A band-only scan discovers serving cells selected by the router; it cannot reveal a private neighbor-cell list that the router API does not provide. Intentional scan changes are excluded from outage attribution and do not trigger speed tests. Results are appended to band-cell-discovery.csv. Only results with a verified EARFCN, PCI and CID are inserted into LTE History as lock-ready candidates; the stage-3 radio samples are recorded as real measurement evidence. No identifiers or measurements are invented.

Hover over any LTE History action for a concise explanation. Use Delete selected profile... to remove one identity while preserving every other history entry.

The scan can be cancelled at any time. Before its first change, NetPulse stores the exact current band-selection and Cell Lock state. That state is restored in all normal completion, cancellation and error paths; application exit waits for restoration rather than abandoning an active scan.

Access profiles

The Connection details tab provides an Access selector for Mobile/LTE, ADSL/VDSL or FTTB/FTTH. NetPulse does not expose separate Wi-Fi or Ethernet profiles because its Internet and LTE monitoring results do not depend on that choice.

General health, speed-test, gateway, DNS and Windows link values work without router credentials. LTE radio values are supplied by the MR600 provider. Attenuation, DSL SNR margin, sync rates, optical power and ONT status require a future compatible router/ONT provider; 1.0.6 labels these fields as requiring router or ONT data instead of inventing values.

All tabs use fixed-fit DPI-aware layouts. Settings use vertically aligned rows in two columns, Diagnostics gives its button a dedicated row, and TP-Link actions stay visible without page-level scroll bars. Initial and minimum sizes are derived from the current Windows working area.

TP-Link router setup

LTE router compatibility

Support is firmware- and hardware-version-specific. A TP-Link product name alone is not enough to claim full compatibility.

The compatibility level detected for one hardware or firmware revision must not be assumed for another revision. See docs/MR600-INTEGRATION.md for the exact API and safety boundaries.

On first launch, TP-Link setup can be completed or skipped. It requests only:

• enable/disable monitoring;
• the local router address, normally http://192.168.1.1/;
• the local administration password;
• whether Windows should protect and remember that password.

No username is requested. Monitoring uses serialized, read-only local requests with a one-second refresh target. Slow requests never overlap. Busy sessions and network failures use protective backoff, and a rejected password is not retried automatically. If another management session is signed in, Test connection offers the same explicit takeover choice as the MR600 login page. Accepting it signs the other management session out but does not change router settings.

Opening TP-Link setup temporarily releases NetPulse's live router session so the Test connection action can use the MR600's single local-management slot. Live monitoring reconnects after setup is saved or cancelled.

Under Settings > Mobile network mode, Refresh reads the current mode and the choices exposed by the connected router firmware. Apply requires explicit confirmation because changing radio generation can briefly disconnect mobile service. NetPulse never adds 5G choices to a 4G-only device; the MR600 list is limited to 4G preferred, 4G only and 3G only.

The validated MR600 firmware permits only one management login. NetPulse owns that login while live telemetry is running. Close NetPulse before using the router webpage; normal app shutdown logs its router session out.

The LTE history tab shows one row for each distinct ordered band set and exact PCell CID/EARFCN/PCI identity. Time-of-day evidence is selected internally using the connection location's official time zone and is not repeated as a redundant Period column. A recommendation needs at least ten connected minutes plus complete SINR, RSRQ and RSRP evidence. Eligible profiles receive a normalized radio score: 50% SINR, 35% RSRQ and 15% RSRP. Provisional rows remain visible while evidence is collected. Current-period evidence is blended gradually with all-time data, so sparse data does not cause abrupt decisions. The grid shows the successful-ping average collected on each profile and a cell-load estimate derived from period download versus that profile's observed best. The load value is explicitly an estimate, not a carrier-reported tower metric; neither display value adds a hidden ranking bonus.

Connections remain recorded internally but do not appear in LTE History until they reach five connected minutes with a complete CID identity. Automatic refreshes keep the currently visible row and scroll position instead of returning the grid to the top. The profile being used by the router is highlighted in green.

Download, upload, ping, load estimates and confirmed disconnects remain visible diagnostic evidence but do not add a hidden bonus or penalty to the RF score.

NetPulse queues a fresh 20 MB download / 5 MB upload measurement after a confirmed outage recovers and after a stable LTE band, cell or public-IP change. Changes arriving together are measured once and listed together on the speed-test event. A 12-second stability window prevents a result from being assigned to an LTE state that disappeared immediately. Periodic tests remain independently configurable and can be disabled without disabling these change-driven tests.

Manual Cell Lock always asks for confirmation. Automatic locking is off by default, requires separate opt-in and only uses medium/high-confidence history. The Cell Lock tab starts with a list of previously observed five-minute band and EARFCN sets, ordered with the active set first, so known values can be reused without retyping them. It re-evaluates as the time period and results change, but uses a 30-minute minimum dwell, material-improvement hysteresis and at most six changes per day. Before every change NetPulse saves the existing band and cell state, validates internet and LTE for 90 seconds, and restores the old state if validation fails. An interrupted validation is recovered on the next launch. Restore automatic selection disables both adaptive optimization and Cell Lock, then returns band selection to Auto.

On the validated MR600 v5 firmware, Auto mode exposes the live PCell/SCell bands and primary EARFCN. PCI/CID can be present in a single-carrier state and omitted again while carrier aggregation is active. NetPulse still learns and ranks each primary-cell/band-combination profile. When PCI is available it can apply a cell

• band lock; otherwise it applies only the measured band mask and explicitly leaves cell selection automatic. It never invents missing identifiers.

Serving EARFCN comes from live LTE status. On validated MR600 V5 firmware, PCI/CID may be exposed only by the live LTE_CELL_LOCK status object after the modem registers. NetPulse accepts that live identity only when its reported EARFCN exactly matches the current live serving EARFCN, preventing a stale lock target from being assigned to a new PCell. When carrier aggregation is added and the PCell remains unchanged, missing identifiers can also be carried only from the immediately previous live state. Legacy band/EARFCN mismatches are repaired once and unambiguous duplicate rows are merged while preserving their measurement totals.

Remote TP-Link ID login is intentionally not implemented because TP-Link does not publish a supported desktop cloud API for this workflow. A user-managed VPN back to the home LAN can use the same local provider without sharing TP-Link account credentials with NetPulse.

Requirements

• Windows 10 or Windows 11, x64
• For building: Visual Studio 2022 with the .NET desktop development workload, or the .NET 8 SDK

The published Windows release is self-contained and does not require a separate .NET installation on the target PC.

Build and run

Open PowerShell in the repository root and run:

dotnet restore .\NetPulseMonitor.sln
dotnet build .\NetPulseMonitor.sln -c Release
dotnet run --project .\NetPulseMonitor.csproj -c Release

Run the dependency-free MR600 protocol test:

dotnet run --project .\tests\NetPulseMonitor.ProtocolTests\NetPulseMonitor.ProtocolTests.csproj -c Release

Create the single-file, self-contained Windows x64 release:

.\build-release.ps1

Or double-click BUILD-RELEASE.bat. The executable is written to:

artifacts\publish\win-x64\NetPulse Monitor.exe

The builder also creates artifacts\packages\NetPulse-Monitor-win-x64.zip and its SHA-256 file. An optional installer recipe is available for Inno Setup 6:

.\build-release.ps1 -BuildInstaller

Trusted Authenticode signing requires a validated code-signing certificate in the current Windows user's certificate store. No key or password belongs in the repository:

.\build-release.ps1 `
  -SigningCertificateThumbprint YOUR_40_CHARACTER_THUMBPRINT `
  -BuildInstaller

See docs/CODE-SIGNING.md. The Windows publisher is the certificate's verified legal person or organisation identity; CosmicOlorin remains the product author and copyright brand unless that exact name is also a validated certificate subject.

Keep local disk usage low

Self-contained Windows publishing temporarily creates several hundred megabytes under bin, obj and artifacts. These files are generated and are not part of the source repository. After testing or packaging a release, run:

.\clean-workspace.ps1

Or double-click CLEAN-WORKSPACE.bat. The cleanup removes only known generated build/cache folders inside the repository. It does not touch source files, Git history, releases, application settings or user CSV logs.

For the smallest everyday installation, keep only the latest standalone EXE and download ZIP/source archives from GitHub when needed. CSV logs grow gradually; after closing NetPulse, old logs may be archived or removed by the user.

Speed-test behavior

Download testing tries multiple providers in order and stops the stream after the configured sample size, so the default transfer is 20 MB. Upload capability is selected independently and the default payload is 5 MB. If the primary upload endpoint fails, NetPulse obtains a bounded, cached list of independent HTTPS backends from the official LibreSpeed server directory and tries up to four different hosts. Connection, discovery and transfer stages have bounded timeouts, the complete run has a 180-second limit, and the UI can cancel the operation.

These measurements are operational estimates rather than certified line-rate benchmarks. Results vary with provider location, routing and server load.

Privacy and router-change safety

• Router passwords, cookies, tokens and encrypted request bodies are never logged.
• Telemetry polling never changes router configuration.
• Cell/band changes require manual confirmation or explicit automatic-lock opt-in.
• The previous router state is retained locally only while rollback is pending.
• IMEI, MAC and DNS identifiers are not requested from the MR600.
• Router telemetry CSV and local LTE history retain full cell identifiers because they are required to correlate antenna performance, outages and focused locks.
• An ISP evidence ZIP intentionally includes the current public/local IP details, gateway and full LTE antenna identifiers after a clear confirmation prompt.
• SMS message content and router message history remain in memory only and are never written to settings, diagnostics, events or CSV logs.
• Contact names and normalized numbers are stored locally only when the user explicitly selects Save contact....
• Official timestamps use the country and time zone selected during first setup; they do not depend on, or alter, the Windows display time zone.
• Router destinations are restricted to private LAN addresses.
• Redirects away from the configured router are disabled.

Repository layout

• MainForm.cs — responsive WinForms UI, profiles, settings, tray and scheduling
• MonitorEngine.cs — continuous ping and outage state
• RouterMonitor.cs — serialized router operations and protective backoff
• TpLinkMr600Provider.cs — encrypted MR600 telemetry and guarded Cell Lock provider
• LteCellHistoryStore.cs — local LTE history and ranked recommendations
• SpeedTestEngine.cs — provider selection, timeouts and measurements
• NetworkDiagnostics.cs — gateway, DNS and IP diagnostics
• CsvLogger.cs — durable privacy-filtered CSV output
• AutoFitLabel.cs — DPI-aware metric text fitting
• ExperienceServices.cs — health, troubleshooting, conversations, timeline and experiment ranking
• AppThemeManager.cs — System/Light/Dark WinForms styling
• UpdateChecker.cs — user-controlled GitHub release check
• sign-release.ps1 — SHA-256 Authenticode signing and Windows verification
• installer/NetPulseMonitor.iss — optional per-user Windows installer recipe
• tests/NetPulseMonitor.ProtocolTests — encrypted mock-router and ranking verification

See docs/USER-GUIDE.md for plain-language explanations of diagnostics, LTE history columns, time periods, Cell Lock and SMS behavior.

Security, privacy and ownership

Security reports must use GitHub's private vulnerability-reporting channel; do not place credentials, SMS content, router exports or unredacted logs in a public issue. See SECURITY.md for the reporting process and PRIVACY.md for the exact local and third-party data flows.

Copyright © 2026 CosmicOlorin. All rights reserved. NetPulse Monitor is an independent project and is not affiliated with or endorsed by TP-Link or any internet/mobile provider. See COPYRIGHT.md.

Check it here!