Piso WiFi Multi-Machine Monitoring

Part of: Piso WiFi Business · Also in Business, Vendo and Setup: Best Location for a Piso WiFi Machine · Piso WiFi Permits and Taxes in the Philippines

One machine is easy to watch. You walk past it, you hear the coin slot, you see the customers sitting nearby. Two or three machines in different places are a different job. A machine can go quiet for a day before anyone tells you, and a quiet machine still costs you internet, electricity, and licence money while it earns nothing.

Multi machine monitoring is not about watching a screen all day. It is about knowing, quickly, whether each machine is online, selling, and behaving normally, and catching the odd one out before a small fault becomes a week of lost sales. This post covers what to monitor, a daily and weekly routine, how to use platform dashboards in general terms, alerts and logs, what to check when one machine drops while the others stay up, and how to reconcile sales across machines.

For the wider business case for running several machines, including location choice and expansion timing, see How to Start a Piso WiFi Business: Costs, Location, ISP Choice, Permits, and Honest Income Factors. This post does not repeat that overview. It covers monitoring only.

What to Monitor on Every Machine

You do not need to watch everything. You need to watch the handful of signals that tell you a machine is healthy or in trouble. Check these for each machine, not just for your best one.

Online or offline status

The first question is simple: is the machine reachable and serving customers? An offline machine earns nothing, and customers will walk away rather than wait for you to notice. Note the time you first saw it offline, because that time matters when you later work out how long sales were lost and whether the fault lines up with a power cut or an internet outage.

Sales, by machine and by day

Sales tell you whether a machine is alive even when it looks fine from the outside. A machine that is online but selling nothing may have a portal problem, a coin problem, or a rate problem that customers are quietly avoiding. Record sales per machine per day, and keep coin sales and voucher sales separate where your platform allows it. A combined total hides problems. If voucher sales stay normal while coin sales fall to zero, the fault is probably at the coin slot, not at the internet connection.

Version consistency

Machines on different versions can behave differently, and that difference can confuse both you and your customers. One machine may pause one way while another pauses another way, or one portal may show a button the other does not. You do not have to update every machine on the same day, but you should know which version each machine runs, and note it in your log. For update and rollback steps, see Piso WiFi Software Update: Versions, Backups, and Rollback. That post also explains the firmware tracker, which is the same log you can use here to record versions per machine.

Pause and voucher behaviour

Pause and voucher problems are the complaints customers remember, and they often show up as a pattern across one machine only. Watch for repeated reports from one location about paused time not returning, sessions ending early, or voucher codes being rejected. One complaint can be a customer mistake. Three complaints from the same machine in a week are a signal to test that machine as a customer yourself. Do not change a setting on all machines because one machine misbehaved. Test the affected machine first.

Coin and power problems

Coin problems and power problems are the two faults most likely to stop sales without any warning on a dashboard. A coin slot that stops accepting coins, a full coin box, or a loose power supply can leave a machine online but useless. Watch for sales dropping suddenly on one machine, for coin sales falling while voucher sales continue, and for any machine that goes offline at the same time each day, which may point to a power or timer issue at that location rather than a platform fault.

A Daily Monitoring Routine

A daily check should take minutes, not hours. Do it at the same time each day, ideally after the busy period, so you compare like with like.

1. Check each machine is online. Note any machine that is offline, and the time you found it.
2. Check today’s sales per machine. Flag any machine with zero sales, or sales far below its normal day.
3. Check for stuck sessions or sessions that look wrong, such as a session that has run far longer than your longest rate allows.
4. Read any new customer complaints or messages, and match each one to a machine. A complaint without a machine name is hard to act on, so always ask which location it came from.
5. If a machine needs a visit, note what you will check on site: cash, coin slot, power, signal at customer seats, and a test payment as a customer.

If you have a helper or a shopkeeper at a remote location, agree on one simple daily message from them, such as online or offline plus any customer complaint. A short daily message beats a long weekly report that arrives after the fault has already cost a week of sales.

A Weekly Monitoring Routine

The weekly check is where you spot slow trends that a daily check misses.

1. Compare each machine’s weekly sales with the previous week. A slow fall over three weeks matters even if no single day looked alarming.
2. Compare coin sales with voucher sales per machine. A shift in the mix can point to a coin fault, a voucher stock problem, or a change in what customers at that location prefer.
3. Check version consistency across machines, and note any machine that is behind after an update.
4. Check licence validity and renewal dates per machine, so a licence expiry does not surprise you on a busy day.
5. Review the fault log for repeats. A fault that has happened three times at one location is not bad luck. It is a repair or replacement decision waiting to be made.
6. Plan visits for the coming week, starting with the machine with the worst trend, not the one closest to you.

Keep the weekly check in one place, even if it is only a notebook or a simple sheet with one row per machine per week. The value is in the comparison over time, not in the format.

Using Platform Dashboards, in General Terms

Most commercial platforms offer some form of remote view of your machines, but what each dashboard shows, and how it is labelled, differs by platform and version. Use the dashboard as a first check, not as the final word. A dashboard can show a machine as online while customers at the location cannot connect, and it can show a machine as offline during a short internet blip that fixes itself. When the dashboard and the customers disagree, trust the on site test.

In general terms, a dashboard check usually means: confirm the machine appears in your account, check its online status, check recent sales or session activity, and check for any error or warning shown for that machine. Do the same steps for each machine, in the same order, so you do not skip one by accident.

Only the remote examples already covered in existing content

Existing content on this site already names remote management for three platforms, and this post stays within those examples. Do not assume any other platform offers the same remote view until you have checked with its own supplier.

• LPB: remote management is listed for LPB in existing content. Use it to check machine status and sales remotely, then verify on site if the status looks wrong.
• AdoPiSoft: remote management is listed for AdoPiSoft in existing content. Use it the same way, as a first check followed by an on site test when something looks off.
• PisoFi: cloud features are listed for PisoFi in existing content. Use the cloud view to check machine activity remotely, then verify on site if the activity does not match what customers or the shopkeeper report.

Check with your own supplier for what your platform version actually shows, what it does not show, and whether remote access needs any extra setup or licence tier. A feature listed for one version may not exist on an older version, and a dashboard that worked last month may behave differently after an update, so recheck after every update.

What a dashboard cannot replace

A dashboard cannot collect cash, clean a coin slot, check signal where customers actually sit, or talk to an unhappy customer. Plan site visits for those jobs even when every dashboard light looks green. A machine that looks perfect remotely and has a full coin box is still a machine that will stop accepting coins soon.

Alerts and Logs

Alerts are useful only if they lead to action. An alert you ignore every day will soon be ignored on the day it matters.

Set up alerts only for events that need a same day response, if your platform offers them: a machine going offline, a machine with no sales for a full day, or a repeated error on one machine. Check with your supplier what alerts your version supports, because alert options differ by platform and version. If your platform offers no alerts, your daily check is your alert system, and missing a day is the same as switching alerts off.

Keep a simple monitoring log, one row per machine per check, with these fields:

Field	What to record
Date and time	When you checked
Machine	Location and machine identifier
Status	Online or offline, as shown and as reported on site if different
Sales today	Coin and voucher sales separately, where available
Version	Version shown, if you checked it that day
Complaints	Customer reports matched to this machine
Action	Visit planned, setting checked, supplier contacted, or no action needed

A log with gaps is still useful, because the gaps themselves show which days you did not check. A log that only records problems is less useful, because you cannot tell whether a quiet week was a healthy week or a week you never looked.

When One Machine Drops While the Others Stay Up

This is the most useful fault pattern in multi machine monitoring, because it narrows the cause. If all machines drop at once, the cause is likely shared, such as a platform problem or a wide internet outage. If one machine drops while the others stay up, the cause is almost always local to that machine or that location. Work through the local causes in this order:

1. Power at that location. Ask the shopkeeper or check on site whether the machine has power, whether there was a power cut, and whether the power supply and plug are firm. A machine that drops at the same time each day may be on a shared switch or timer.
2. Internet at that location. Check whether other devices at the same location can get online, and whether the machine’s internet source is a wired plan, a SIM, or a shared connection that may have changed. Test with a laptop connected to the same source, as covered in the troubleshooting posts, before you blame the platform.
3. Hardware on that machine. Check the board, the access point, the cables, and the power supply for loose connections, heat, or damage. Swap nothing blindly. Note what you checked, so the next visit does not repeat the same checks.
4. Coin and portal behaviour on that machine. Test as a customer with a small payment, and test pause and voucher if offered. A machine can be online yet unable to sell if the portal or coin path has failed.
5. Version and licence on that machine. Check whether this machine missed an update the others received, or whether its licence has expired while the others are still valid.

If the fault follows the location after you swap a part, the location is the problem. If the fault follows the part to another location, the part is the problem. Write down which one you tested, so you do not swap the same part twice.

Sales Reconciliation Across Machines

Reconciliation means matching what the platform says you sold with the cash and voucher value you actually collected. Do it per machine, not as one combined total, because a combined total lets one machine hide another machine’s shortfall.

For each machine, for the same period, record:

• Platform sales total, split into coin sales and voucher sales where your platform allows it.
• Cash collected from that machine’s coin box, counted and dated.
• Voucher value redeemed on that machine, where your platform reports it, kept separate from coin cash.
• Any refunds or re-credits you gave on that machine, with the reason noted.

Then compare. Small differences can come from timing, such as a sale recorded just before midnight and cash collected the next morning, or a voucher sold in one period and redeemed in the next. A large or repeated difference needs investigation: a coin counting error, a voucher record error, cash handling at that location, or a session record problem. Do not adjust the platform record to match the cash, or the cash to match the platform, without noting the difference and the reason. An unexplained adjustment today becomes an unexplainable gap next month.

Reconcile weekly for busy locations and at least monthly for quiet ones. A machine that has never been reconciled is a machine whose real income you do not know, however good its dashboard looks.

Frequently Asked Questions About Multi Machine Monitoring

How many machines can one person monitor?

It depends on distance, not just count. Three machines in one building are easier than three machines in three towns. Start with the number you can visit within a day when a fault needs a visit, and add a local helper at each remote location before you add another remote machine.

Do I need a dashboard to monitor several machines?

A dashboard helps, but the routine matters more. A daily status and sales check, a weekly comparison, and a simple log will catch most faults even without alerts. If your platform offers a dashboard, use it as a first check, but still test on site when the dashboard and customer reports disagree.

What is the first sign that a machine has a problem?

A sudden fall in sales on one machine while the others stay normal is usually the first sign, followed by customer complaints from that location. A machine with zero sales on a normally busy day deserves a check the same day, not at the next weekly review.

Should all my machines run the same version?

It is usually simpler when they do, because behaviour, support, and troubleshooting stay consistent. If hardware or licence tiers force different versions, record the version per machine in your log and test each version separately, because a setting that works on one version may not work on another.

How do I know if a fault is a platform problem or a local problem?

Compare machines. If all machines show the same fault at the same time, suspect a shared cause. If only one machine shows it while the others stay up, work through the local causes in this post: power, internet at that location, hardware, coin and portal behaviour, then version and licence.

What should I do if dashboard sales and collected cash do not match?

Do not adjust either figure silently. Record both figures, the period, and the difference, then check timing, coin counting, voucher redemption timing, and any refunds given on that machine. If the difference repeats, investigate that machine and location before you assume a counting mistake.

What to Read Next

If you want the wider business picture for running several machines, go to How to Start a Piso WiFi Business: Costs, Location, ISP Choice, Permits, and Honest Income Factors. If you need update and rollback steps, go to Piso WiFi Software Update: Versions, Backups, and Rollback. If a machine fault needs fixing, go to the Troubleshooting guide. If you need scripts for the customer complaints monitoring uncovers, go to Piso WiFi Customer Dispute Scripts.