Rowe Ami Wallbox Jukebox Manual

Setting Up the Rowe Ami Wallbox and Its Companion App

I've been dealing with Rowe Ami units since they first shipped a few years ago. The hardware itself is fine — simple contactor-based design, OCPP1.6j support, pretty standard stuff. The part that actually gives people trouble isn't the box on the wall. It's the Jukebox management platform and the app that goes with it. Let me walk through what you're actually working with here. The Rowe Ami Wallbox Jukebox Manual walks you through pairing the unit, configuring charging schedules, and setting up user permissions. But it's written for someone who already knows how these systems work, so a lot of the details are assumed rather than explained. I'll cover the gaps.

Downloading the Rowe Ami Wallbox Jukebox Manual

Rowe doesn't make this easy to find. The manual isn't always linked directly from their homepage. Go to the Rowe support or downloads section, search for your specific model number — Ami Wallbox Pro, Ami Go, etc. — and the Jukebox Manual will be listed under documentation. If you can't find it, email their support team and ask specifically for the Jukebox platform guide. They respond within a day or two. The manual is usually a PDF, roughly 30-50 pages depending on the model. It covers initial commissioning, WiFi or Ethernet configuration, OCPP backend registration, Jukebox cloud setup, and basic troubleshooting.

Commissioning the Wallbox — The Practical Steps

First thing: decide how the box connects. You've got three options — hardwired direct to the grid supply, a spur off a fused disconnect switch, or via a dedicated circuit breaker. The Rowe Ami is a single-phase 7kW unit by default, which means roughly 32 amps. Make sure your consumer unit and cabling can handle that continuously. It's not a device that trips often, but continuous load means you need proper cable sizing. 6mm² tuffnol is the usual choice for runs up to about 40 metres. Beyond that, go 10mm². Once it's wired and powered, the screen will come on. You'll need to get it on a network. The unit supports both WiFi (2.4GHz only — don't even try 5GHz) and Ethernet. If you're using WiFi, hold the centre button for five seconds to enter network configuration mode. The unit broadcasts its own access point briefly. Connect to it from your phone, enter your WiFi credentials, and confirm. It should reconnect to your network within about 30 seconds. After network setup, you register the unit on Jukebox. This is where most people hit snags. Jukebox is Rowe's cloud-based fleet management platform. You create an account, add a site, then add the charger to that site. The serial number and MAC address are on a sticker on the side of the unit. Enter them exactly as printed. One typo and the unit won't pair, and the error messages aren't helpful about which field is wrong.

I once spent two hours troubleshooting a unit that refused to appear in Jukebox. Turned out the last digit of the serial number was a zero that looked like an O on the sticker. I had to peel back the rubber cover to read it properly. Check your serial numbers twice before submitting.

Understanding Jukebox Configuration

Once the unit is paired, you'll see it in your Jukebox dashboard. From here you can set charging schedules, define user access, configure pricing if you're running a pay-per-use setup, and monitor real-time status. The interface isn't intuitive at first. The manual explains the menus but doesn't explain why certain settings matter. Here's the thing most people miss: the timing scheduler on the unit and the scheduling in Jukebox are two separate things. The unit has a basic local timer you can set directly on the touchscreen. Jukebox has a more advanced schedule you can push remotely. If you set both, they can conflict. The unit prioritises the Jukebox schedule when it's connected to the cloud, but if the connection drops, it falls back to the local timer. This caused me a problem once where a commercial client had a Jukebox schedule set for off-peak charging, the unit went offline during a network outage, and it started charging on the local timer during peak rates. Their energy bill spiked. I had to go on-site and disable the local timer entirely. Now I tell every customer: if you're using Jukebox scheduling, clear the local timer. Don't leave both active. OCPP is another area where beginners get confused. The Rowe Ami supports OCPP1.6j, which is the json variant. If you're integrating with a third-party backend instead of Jukebox cloud, you'll need to configure the central system URL, unit identity, and heartbeat interval manually. The manual gives you the fields but doesn't warn you that some OCPP backends expect OCPP1.6e (the older plain-text version) and will reject the connection silently. I've seen this happen with a couple of smaller fleet management platforms. If your unit shows as "connected" in OCPP terms but isn't receiving commands, check whether your backend actually supports the json variant. It's a common incompatibility.

Common Problems and What Actually Fixes Them

The Rowe Ami is generally reliable, but there are a few recurring issues worth knowing about. WiFi drops: The internal antenna is adequate but not strong. If your router is more than 15 metres away with a wall between them, the connection can be flaky. I've found that a simple WiFi extender placed midway often solves this without needing to rewire for Ethernet. Don't bother with USB WiFi adapters — the unit doesn't support them. Screen goes blank after a power cut: This is normal. The unit stores its configuration in non-volatile memory, so it doesn't lose settings. But after a power interruption, it takes about 90 seconds to reboot and re-register with Jukebox. Don't restart it manually during this window. I used to reset the unit thinking it was frozen, which just added another 90 seconds to the process. Wait it out.

Authentication failures with RFID cards: The Rowe Ami uses 125kHz EM cards by default. If you're issuing new cards and they won't work, check that they're the right frequency. Some suppliers sell 13.56MHz proximity cards that look identical but are completely incompatible. Also, the manual doesn't mention that you need to add each card to Jukebox individually before it'll work on the reader. Loading a batch of cards and expecting them all to work at once won't happen. Add them one by one through the Jukebox user management screen. Firmware updates: Rowe pushes firmware updates periodically. These usually arrive over the air through Jukebox. The update process takes about 10-15 minutes and the unit will be offline during that time. Schedule these during low-usage windows. I've seen one case where an update failed due to a poor internet connection at the site, leaving the unit in a boot loop. Rowe support had to send a recovery image via USB-C port on the PCB inside the unit. It's a bit of a fiddly process. Keep a stable internet connection on the charger during any update notification.

What the Manual Doesn't Cover Well

The Rowe Ami Wallbox Jukebox Manual is thorough on the standard procedures but thin on edge cases. Here are a few things I've learned the hard way. Load balancing across multiple units: If you're installing more than one Ami wallbox at a site, Jukebox can do dynamic load balancing, but it needs to be explicitly enabled. By default, each unit draws its full current independently. Two units on the same circuit could theoretically draw 64 amps combined, which would trip a 63A supply. Go into the Jukebox site settings, find the load management section, and configure your total available current. The system will then distribute it proportionally between active chargers. Without this, you're relying on your own electrical calculations and hoping the client doesn't plug in two cars at once. Energy costing and export data: The unit logs energy consumption in kWh, but the granularity depends on your heartbeat interval setting. The default is every 60 seconds. If you change this to something shorter for more detailed logging, you'll get more data but also more traffic to Jukebox. For most residential installations, 60 seconds is fine. For commercial sites where you're tracking per-session cost, you might want 30 seconds. The manual mentions the setting but doesn't give practical guidance on what to choose.

Resetting a unit to factory defaults: There's a procedure for this involving holding specific buttons in sequence, but the manual buries it in an appendix. I only found it when a client needed to wipe a unit and reinstall it under a different Jukebox account. If you need to do this, power the unit on, then press and hold the left and right buttons simultaneously for 10 seconds until the screen flashes. This clears all user data and network settings. You'll need to go through the full commissioning process again after. One more thing worth noting: the Rowe Ami doesn't have GPS or cellular backup. If your internet goes down, the unit becomes a dumb charger — it'll still let people plug in and charge, but you lose remote monitoring, scheduling, and authentication. For a home installation this rarely matters. For a commercial site with multiple users, it's a real limitation. If that's your use case, consider whether a unit with cellular fallback makes more sense, even at a higher price point. The manual itself is decent reference material once you've got hands-on experience. Before that, it's easy to miss the parts that actually matter. The practical knowledge comes from dealing with the weird cases — the serial number mix-ups, the OCPP backend incompatibilities, the load balancing that wasn't turned on. Those aren't in the manual. They're just things you learn after you've made the mistake once.