For AdoPiSoft operators expanding Wi-Fi coverage: 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.
Start with the correct platform and role
Piso WiFi is a category of prepaid/captive-portal deployments, not one standardized router firmware. A vending/controller platform, the upstream ISP router, and separate Wi-Fi access points can all have different addresses and credentials. The customer portal and the operator admin page are also different security roles. Follow AdoPiSoft’s current access-point/network instructions plus the exact AP manufacturer guide.
Step-by-step checklist
- Map the existing WAN, controller LAN and customer subnet before adding hardware.
- Configure the additional device in access-point/bridge mode when that is the intended topology.
- Give management a predictable, non-conflicting address or DHCP reservation.
- Connect the AP to the controller/switch LAN and verify clients receive the Piso WiFi gateway/DNS, not a second DHCP server.
- Test captive-portal redirection, paid-session accounting, roaming and internet access through the new AP.
- Measure signal and channel use in the target area before increasing transmit power.
What not to assume
A second router left in normal router mode can create double NAT, another DHCP server and a separate captive-portal path. Verify topology rather than copying a random AP setup video. Likewise, 10.0.0.1 is only a private IPv4 address. Its presence does not identify the software by itself, and changing the address does not change how the vending/session system works.
Customer-side checks
- Stay connected to the Piso WiFi SSID and turn off a VPN temporarily if the portal will not open.
- Do not type operator credentials into a public search result.
- If a portal fails only on one phone, test browser captive-portal state, Private DNS, MAC randomization and date/time before blaming the machine.
- Keep payment/voucher proof until the session is confirmed.
- For pause/resume or voucher issues, use the same device when the platform ties sessions to a device identity.
Operator-side checks
Troubleshoot in layers. Confirm stable power, then WAN internet, controller WAN/LAN interfaces, DHCP/DNS, access-point reachability, captive-portal service, payment input, and finally the user/session database. If every client fails, focus on shared infrastructure. If one client fails, compare that client with a working one before rebooting or resetting the system.
Security and reliability
- Change initial/factory administrator credentials after setup.
- Keep customer traffic separated from the management LAN where the platform supports it.
- Use official software updates and make backups before upgrading.
- Protect the controller, coin acceptor and power hardware from moisture, heat and unstable power.
- Use a proper access point for coverage and capacity rather than assuming the controller board’s radio can serve a busy area.
- Never expose the admin dashboard directly to the public internet through an unrestricted port forward.
Network architecture matters more than the portal IP
A healthy installation normally has a clear upstream/downstream design: ISP modem or ONT, then the device responsible for routing/session control, then switches/access points serving customers. Avoid accidental double DHCP, overlapping subnets and a consumer Wi-Fi router running NAT behind the vending controller unless the design intentionally calls for another routed boundary. Label WAN and LAN cables so a maintenance visit does not silently reverse them.
Payment and session integrity
When money or vouchers are involved, troubleshoot payment confirmation separately from internet access. Keep transaction/session logs long enough for legitimate support and reconciliation, but do not collect secrets that the payment provider does not require. For digital wallets, the operator should never request a customer PIN or one-time password. Test duplicate payments, failed callbacks, controller restarts and recovery after power loss before advertising a new payment option.
Maintenance checklist
- Keep the controller/router and access-point software on supported releases from the official vendor.
- Back up configuration before updates and store a copy away from the machine.
- Check power supply, ventilation, storage health and cable condition.
- Review peak-hour WAN utilization, loaded latency and access-point client counts.
- Audit admin accounts after staff/vendor changes and remove access that is no longer needed.
- Test the customer journey—from joining Wi-Fi through payment, portal access, session expiry and reconnect—after every major change.
Check the exact platform before using credentials or reset steps
Piso WiFi systems are not one standardized firmware. Match the machine name, installed version, controller type and local network before applying a login, password-recovery or reset instruction. If the device label or installed platform shows a different address or workflow, use the information for that exact machine rather than forcing a value from another platform.
Make sure the AP extends the customer LAN instead of replacing it
The added access point should bridge the intended customer network back to the controller so captive-portal and session policy remain in the traffic path. If the AP runs its own NAT/DHCP service, customers may receive a different gateway and bypass or break the vending workflow. Disable routing features when the design calls for a pure access point.
VLAN examples are topology-specific
AdoPiSoft documents an access-point setup using VLAN 22 in one supported design and also documents alternatives where VLAN-capable equipment is not available. Follow the topology that matches the controller image and hardware. Do not copy an IP mask, VLAN, or static management address without understanding which side of the network it belongs to.
Test roaming and session continuity
After adding the AP, start a real customer session near the original AP, move toward the new AP, and verify that internet/session credit continues as intended. Current AdoPiSoft session settings can use cookies/MAC synchronization to help session continuity across multiple APs. Also test a new client, captive-portal redirect, DNS, and a paid transaction through the new radio path.
Plan management addresses before adding many APs
Give infrastructure devices predictable management addresses outside the normal customer DHCP pool, or use reservations where appropriate. Record AP model, location, management IP, uplink port, SSID, band/channel, backhaul type, and PoE/power source. This makes a future “one AP is down” problem solvable without scanning the entire customer subnet or unplugging random cables.
Capacity test after adding the AP
Check that a new client receives the normal Piso gateway/DNS, the captive portal appears, a paid/test session authorizes correctly, and customer isolation still works. Measure throughput and latency near the new AP and at its coverage edge. Then test roaming between APs with an active session. If the AP is wired, verify Ethernet speed/duplex; if it is wireless/mesh backhaul, measure backhaul quality separately from the client radio link.
Frequently asked questions
Should the added AP create its own routed subnet?
Normally not when it is extending the Piso customer LAN. It should bridge the intended network so customers still receive the controller gateway and captive-portal/session policy.
Does every AdoPiSoft AP deployment use VLAN 22?
No. AdoPiSoft documents VLAN 22 in a specific supported AP topology, while hardware and deployment methods can differ. Match the guide to the controller image/equipment rather than copying a VLAN blindly.
What should be tested after adding the AP?
Check client DHCP/gateway/DNS, portal redirect, payment/session authorization, customer isolation, internet performance, AP management reachability, and roaming/session continuity from the old coverage area to the new one.
Why is the new AP slow with a good signal?
The uplink/backhaul can be the bottleneck. Check Ethernet negotiation/PoE/cabling or wireless backhaul quality, channel contention, client load, and whether the AP is using a congested band/channel.