Remote monitoring your system while away

Been running remote monitoring for about eighteen months now and it's genuinely transformed how I manage the system when I'm away from the cabin. Started with just the basics—Victron's VRM portal—but realised quickly that's only half the story when you're dealing with variable weather and battery state.

The setup that actually works for me combines a few layers. VRM gives you the headline figures (SOC, voltage, load), but I added a Shelly Plus 2PM for real-time circuit monitoring because I needed to know if specific loads were drawing unexpectedly. Connected both via a Fogstar 4G router so I'm not reliant on dodgy WiFi.

What changed everything was setting proper alerts. Temperature thresholds on the Victron, voltage warnings, and load limits on the Shelly. Sounds obvious, but catching a stuck relay or unexpected drain at 2am from 200 miles away means you can actually do something about it before the battery flatlines.

The EV charging side is trickier though—I use a Zappi which has its own app, but the integration between that and the solar system monitoring is still a bit clunky. Currently managing it manually, which isn't ideal. Anyone else here running EV charging on off-grid and found a cleaner solution for unified monitoring?

Also curious whether others are logging historical data properly. Raw Victron data isn't granular enough for me to optimise the system, so I've been exporting CSV and running analysis locally. Feels like there should be a better approach.

What's everyone else using? Are you comfortable with single-point monitoring or running redundant systems like I am?

VRM's brilliant for the fundamentals, but I'd push you toward layering it properly. I've got a Victron setup in the van and use VRM alongside a separate 4G camera—sounds redundant, but it's saved me twice when inverter faults looked like battery issues.

The real game-changer for me was setting up threshold alerts on your phone. VRM does email notifications, but if you're actually away, you need push alerts that'll interrupt you. I use a Raspberry Pi running Node-RED to cross-reference battery state-of-charge with load data; catches problems hours before they'd become expensive.

One thing worth considering: your monitoring is only as good as your connectivity. I run dual SIMs on my data logger—sounds paranoid until you're genuinely isolated and something breaks.

What's your current alert setup?

The VRM setup's solid, but what @MarinePhil's getting at is worth heeding—layering matters more than you'd think. I've got alerts configured through both VRM and a separate MQTT broker feeding into Home Assistant on a raspberry pi. Sounds overkill, but when you're on the boat and something's gone sideways with the batteries, you want redundancy.

One thing that's saved me: setting realistic alert thresholds. Too sensitive and you're getting false alarms constantly; too loose and you miss actual issues. I monitor SOC, inverter faults, and charger status separately rather than relying on one dashboard.

The real game-changer was adding a simple 4G router as backup—not for constant monitoring, but it means I'm not completely blind if the primary connection drops. Worth considering if you're relying on this for peace of mind.

Quick question for you lot—how many of you are actually comfortable with just VRM for the critical stuff, or does everyone end up adding secondary monitoring?

I'm looking at setting this up for my motorhome setup, and I'm a bit concerned about the single-point-of-failure aspect. @MarinePhil, @SimonThompson—when you say layering matters, are you talking about separate alerting systems entirely, or more about cross-checking the data?

The reason I ask is I've got a Fogstar hybrid inverter alongside the Victron kit in my garden office, and if VRM goes down (internet glitch, Victron's servers, whatever), I'd have no visibility on either system. That seems daft for something I'm paying attention to remotely.

Would something like Home Assistant running locally with WiFi alerts be overkill, or is that actually the sensible approach? I'm not after full automation yet—just want solid redundancy for the monitoring side so I know when things actually need my attention versus when it's just a connectivity blip.

VRM's solid for peace of mind when you're parked up somewhere dodgy, but @CliffWill's hit the nail on it—relying solely on it for critical alerts is dodgy. I've got alerts routed through both VRM and a basic MQTT setup piped to my phone, because the one time you really need a low battery warning is the one time Victron's servers are having a laugh.

The beauty of layering is cheap insurance: pair VRM with something like Node-RED or even just email alerts from your charger controller. That motorhome of mine runs a Fogstar MPPT alongside the Victron kit—gets its own monitoring thread running independently.

Real talk though—most people don't need industrial-grade redundancy. But if you're genuinely remote and reliant on the system not quietly dying, spend an afternoon setting up a backup notification method. Costs you nowt in hardware, just a bit of faffing about.

Right, I'll chip in here. Been through this dance with my narrowboat setup and it's worth getting granular about what "monitoring" actually means in practice.

VRM's your foundation—solid telemetry, decent alerting—but I'd argue it's more of a dashboard than a safety net. The critical gap most folks overlook is response time. If your battery's dropping faster than expected at 2am and you're six hours away, VRM tells you that it's happening. It doesn't stop it.

What I've layered in: a separate battery monitor with local SMS alerts (Victron's BMV with a basic relay module), and crucially, circuit-level automation rather than relying on remote intervention. Contactor cutoffs, load shedding based on state of charge—things that act without needing you to log in and fanny about.

The VRM piece is invaluable for trend analysis and spotting developing faults. But for actual system protection when you're away? You need dumb, reliable failsafes that work offline.

Worth having a think about what scenario you're actually

VRM's decent but I layer it with a separate 4G camera setup in my van—belt and braces approach. The thing is, VRM can be a bit laggy when you've got dodgy signal, and if something goes catastrophically wrong, you want to see it happening, not just read numbers.

For van life especially, I've found it helps knowing both your battery state AND that nothing's physically on fire. Had a relay stick once and VRM showed normal voltage for ages while the Victron was quietly cooking itself.

That said, if your system's solid and you're not gone for months at a time, VRM alone is probably fine. The real value is catching drift early—catching a slow battery sulphation issue or a charger that's decided to do weird things.

I'd say: use VRM for the peace of mind on routine stuff, but add something visual if you're seriously remote or paranoid like me.

VRM's alright for the basics, but I've found it's about as reliable as a sunny day in Manchester when you're relying on it alone. Had mine drop out for three days last winter because my 4G dongle decided to ghost me mid-trip.

Ended up bunging in a cheap Reolink camera on a separate SIM card—now I can actually see if something's on fire rather than just guessing from a dashboard that's gone offline. Costs about £80 and actually works when your main comms takes a nap.

The real trick is treating remote monitoring like belt and braces and a belt made of braces. VRM catches the numbers, the camera catches the actual "oh no" moments, and a basic SMS alert setup catches the stuff that matters at 2am when you're three hours away wondering if your batteries are having a laugh.

Don't cheap out on the redundancy—your peace of mind's worth more than saving a tenner on backup monitoring, trust me on that one.

@LuckySkipper spot on with the belt and braces. I use VRM plus a cheap 4G dongle with a Pi running a custom dashboard—gives me actual peace of mind. VRM's fine for voltage and charge state, but the latency can be dodgy. Secondary system means I know if something's genuinely gone wrong versus just a connection hiccup.