I’m using a Piso Wifi setup and the Pause Time app isn’t behaving the way I expect. Sometimes it won’t pause, other times it doesn’t resume properly, and users are complaining about lost time. I’ve tried restarting the router and reinstalling the app but nothing changed. Can someone explain the correct configuration steps or common fixes for Piso Wifi Pause Time issues so I can manage user sessions reliably?
Had the same headache with Piso Wifi pause before. Here is what I would check in order, keep it simple.
- Check time sync
- Log in to your LPB Piso portal
- Make sure the router time and timezone match your local time
- Turn off “NTP” for a while, set time manually, save, reboot
- Wrong time often causes lost time or wrong resume behavior
- Clear browser cache on users
- Some users load an old session page
- Tell them to use incognito or clear cache before connecting again
- Or add a short note on the portal page about refreshing
- Pause behavior settings
In LPB admin, check:
- Pause Time feature is ON
- “Auto resume on reconnect” type option is OFF if you want strict pause
- If you allow pause once only, set the correct value for “Allow pause per session”
Mismatch here makes users think it is broken
- Session handling
- Set shorter session expiry, example 1 to 2 hours instead of 24
- If sessions expire while paused, users think time was stolen
- Make sure “Session timeout” is not shorter than average user purchase time
- Check for IP conflicts
- Only one device should use 10.0.0.1 (or your portal IP)
- If you added another router or AP in router mode, put it in AP mode
- IP conflict causes random non working pause or resume
- Firmware and LPB version
- Check your Piso firmware version on the portal footer
- Compare with latest version from the dev or group where you got it
- Some older builds had pause bugs, upgrade if needed
- After upgrade, reset to factory, then reconfigure from scratch
- Test with one device
- Temporarily disable all other clients
- Buy 5 or 10 minutes on one phone
- Start YouTube, then hit pause
- Monitor if timer stops on the portal and on the user screen
- Resume after 1 or 2 minutes and see if the time matches
- Avoid double NAT
- Main ISP modem should be in bridge mode or router set to PPPoE / DHCP directly
- Extra router behind Piso device can break portal sessions
- If you use extra APs, put them in AP mode, DHCP off
- Check power and reboots
- If your router restarts, paused sessions sometimes get wiped
- Use a decent power supply and avoid cheap power strips
- See uptime in router status, if it resets often, fix that first
If all that still fails, post screenshots of
- Portal pause settings page
- Session list while paused
- Router time settings
Hard to guess the issue without seeing the config, but most pause bugs I saw came from wrong time, double NAT, or old firmware.
What @sterrenkijker said covers the “standard checklist,” but if your pause still acts weird after that, I’d look at a few less-obvious issues:
- Pause app vs router logic
A lot of people think the Android “Piso Pause Time” app controls everything, but in most LPB builds the app is basically just a remote button for the router. If the router is overloaded or the web backend is lagging, the app looks like it didn’t pause, when in reality the command was delayed or dropped.
- Try pausing directly from the LPB web portal instead of the app for a day.
- If portal pause works but the app is flaky, your issue is app → router communication, not pause logic itself.
- Heavy traffic / CPU load
On busy setups, the router can choke:
- When there’s torrenting or lots of concurrent users, the router sometimes fails to update session states properly.
- Check CPU/RAM usage if your firmware shows it. If usage is pinned high when people click pause or resume, the router might not commit the session changes reliably.
Workaround: limit max users or add bandwidth limits so the box is not dying under load.
- Misleading “lost time” reports
Users complain about lost time for a few reasons that are not actually bugs:
- They paused on one device, then tried to resume on another. Many Piso configs tie the session to MAC/IP, so it looks like the time vanished.
- Some portals show remaining minutes only after a refresh; users think it did not resume because the timer on screen didn’t instantly update.
You can test: one test phone, stopwatch in your hand, 10 minutes credit, pause at exactly 5 minutes used, resume after 2 minutes of real time. If you still get wrong numbers, then it’s a true config/firmware issue.
- Layer 2 stuff: ARP / MAC changes
If clients are behind another router, or they’re using VPN / MAC randomization:
- The system may see them as a new device and give them a new session, leaving the paused one “orphaned.”
- Turn off MAC randomization on phones when testing. Also avoid having the AP in router mode; use pure AP mode so the Piso sees the real client MACs.
- Testing with logging
Instead of just “click and hope”:
- Open the session list page.
- Click pause. Watch if the state or remaining time field actually freezes.
- If the timer keeps counting even though the UI says “paused,” that’s typically a bug in the firmware version or corrupted config. In that case, a full reset and clean reconfigure actually helps more than the quick power-cycle you already tried.
- Database / config corruption
I slightly disagree with just upgrading firmware and calling it a day like @sterrenkijker mentioned. If this started after a lot of random tweaking or many months of uptime:
- Export your settings, then do a hard reset / factory reset.
- Re-enter only the essential config manually, do not import old backups at first.
If fresh config + latest stable build still exhibits random pause / resume issues, that strongly points to a specific feature clash (like some custom portal mod, ad injection, or extra scripts).
- Avoid mixing multiple control layers
Some folks run:
- ISP modem with captive portal or QoS
- Then LPB Piso portal on top of that
Double-control of sessions can cause: - Portal shows paused, but upstream router keeps allowing traffic.
Turn off any captive portal or “parental control / guest network time limit” on the ISP modem or extra router. Only the Piso box should handle sessions.
If you can, share:
- A screenshot of your pause config page
- One sample session from “before pause,” “while paused,” and “after resume”
Because at this point, the key is to see whether the system is miscalculating time, or if the command to change state is not properly applied. The fix depends on which of those is actually happening.