A short daily check catches failures before they become lost sales: confirm WAN health, controller/storage status, captive portal, one transaction path, access-point availability, backups and physical/payment hardware.
Good rate plans balance customer clarity, real backhaul capacity, session policy and operating costs. Start with a small number of understandable packages and measure peak usage before adding complex bonuses or long sessions.
AdoPiSoft documents adding access points behind the vending/controller network. The access point should extend the intended customer LAN without accidentally creating a second DHCP/NAT boundary unless the design explicitly calls for one.
AdoPiSoft’s official activation flow instructs an operator to connect to the machine, open 10.0.0.1/admin, sign in with the documented initial admin/admin credential for that workflow, and activate the machine using the account/device information. Treat that credential as an initial commissioning value, not a permanent shared password.
Back up before software upgrades, major rate/network changes and hardware migration; record the software version/device identity so you know what a backup belongs to.
Separate the admin/management plane from customer traffic, change initial credentials, update controller/router software, back up configuration, and minimize exposed services.
Fair bandwidth limits should be derived from real WAN capacity and peak concurrent users. A per-user limit that looks generous with two users can overload the backhaul when twenty users arrive.
Voucher/rate design should be tested as a transaction workflow: create a small rate, issue one voucher, redeem it as a customer, verify time/data behavior, then scale up. Menu names and pricing logic are platform-specific.
A reliable Piso WiFi deployment has four separate layers: internet/WAN, the vending/controller platform, captive-portal/session logic, and Wi-Fi access points. Build and test each layer independently before taking payments.
Pause/resume is a captive-portal session feature, not a property of the 10.0.0.1 IP itself. Whether it exists, how long a session may remain paused, and how a device is matched are platform/firmware settings.
