Companion to the allotment-network video · Working article · 13 November 2026
I’m the first to admit that having a network on the allotment is an indulgence, one that for me is only really possible thanks to people suffering through YouTube adverts. However since I’ve now committed that future Youtube revenue is going to be spent only on the allotment, it was an easy justification for me to make.
There is something slightly incongruous about cycling along the frosty coastal path and getting a message from my AI, that’s just checked the polytunnel’s temperature and notified me that it’s warm enough for sunbathing. But that is where this project has taken us. A fun project as well as a practical one, a bit of technical challenge to complement my relaxed allotment life, a bit of luxury as a reward for the hard work.
When I built the allotment cabin, installed the battery and it’s solar panels, and brought the network to life, I wanted to make the allotment more enjoyable, comfortable, convenient and relaxing, all year round. I also wanted to blend the different sides of my personality, the person who loves to work hard for his rewards, who loves nature, but also carefully chosen technology, who looks to the future, while trying to understand and respect the past, who loves to deeply relax and sit back with a good book but also likes to potter around and garden for hours. A person who gets a lot done, but does very little that’s not convenient.
My answer was a small, solar-powered network at the allotment, connected privately to Home Assistant at home. Jane, my AI assistant, has helped research, configure and test it. The running power controls, however, are ordinary deterministic scripts—not a language model waking up to decide whether a battery needs charging. The most interesting challenge was not getting everything online on a sunny afternoon. It is keeping the useful parts available through a long winter night without spending more energy powering the technology than the sun provides.

Our functional architecture: orange power, blue data and purple control. H200 power is Jackery USB-A 5 V → diybits inline boost converter → 9 V DC barrel connector, confirmed by Steve’s supplied product image. Final solar input wiring remains to be confirmed on site. The C425 uses Mudi Wi-Fi, but video stays in Tapo rather than streaming into HA. Diagram: Steve + Jane, 13 November 2026.
The diagram separates three things that are easily muddled: power, data and control. Solar charges the Jackery; its switched low-voltage outputs supply the router and sensor hub. The router’s own battery keeps the internet path alive when those outputs are off. Sensor measurements travel through the hub and a private network to Home Assistant. A separate controller can ask the Jackery to restore DC power to the router, to charge it up, while that internet path to send the message still exists.
| Component | Its job in our installation |
|---|---|
| Two Renogy 200 W ShadowFlux panels | A 400 W nominal solar array for the off-grid supply |
| Jackery Explorer 3000 v2 | Stores solar energy and provides separately controlled low-voltage and AC outputs |
| GL.iNet Mudi 7, GL-E5800 | Cellular internet, local networking, private remote access and its own battery reserve |
| Tapo H200 | Ethernet-connected bridge between the network and low-power Tapo sensors |
| diybits 5 V → 9 V boost cable | Converts the Jackery’s 5 V USB-A output to the H200’s 9 V barrel-power input |
| Tapo T315 monitors | Temperature and humidity in the cabin and polytunnel, with screens |
| Tapo T320 monitors | Low cost displayless temperature and humidity sensors scattered around the cabin and plot, these allow me to check conditions for specific crops in storage |
| Tapo C425 camera equipment | Battery-powered camera capability, viewed through Tapo on demand, no storage or streaming. Allows me to check the cabin door is closed and polytunnel integrity |
| Home Assistant OS on our home server | Integrations, sensor entities, history and dashboards |
| Mac mini running Jane’s scripts | Read-only status collection, Telegram reporting and bounded power experiments |

Explorer 3000 v2, UK model. Manufacturer product image. Image: Jackery UK.
The Explorer 3000 v2 has a 3,072 Wh nominal LiFePO₄ battery and up to 3,600 W aggregate AC output. Those are useful capabilities when we are on site.
I chose this battery for a few reasons. It was just the right size to tuck away in a hard to access corner of the cabin, essentially built into the structure. With the right tools I can get it out, but it’s designed to stay put and all my control is via the iPhone app. Just as important was to ensure that Jane had full access to read the Jackery’s status and to control it directly and via her scripts.
I wanted a powerful battery, one able to power any combination of power tools, vacuum cleaners, chargers, heaters, lights and cooking gear, albeit not all at once. I also wanted a battery pack that could take two solar inputs, to give it a chance of getting through the whole year. I’m not expecting to be using it extensively in mid-winter for heating, the solar energy can’t achieve that, but in spring, summer and autumn it should provide some luxuries!
I also wanted powerful and flexible charging capabilities and it definitely delivers all of those. I can easily charge my Ryobi power tools, lanterns, laptop, phone and water pumps. Since I mainly cycle to the allotment this matters, I can’t be carrying batteries to the allotment and back all the time
For unattended networking we use the low-voltage side and normally leave AC off. Cooking, tools and heating loads belong to a different, intermittent budget. Currently only the network’s DC supply is fully automated; AC loads remain manual.
I also discovered to some annoyance that the power output reading on the Jackery display (which I can’t see because of it’s location) and in the app and via the API that Jane reads, is not the actual power being drawn from the battery, it’s the power being consumed by the DC or AC appliances. The Jackery has electronics of its own, which consumes power invisibly when either of the AC or DC subsystems are active and that over-head is considerable.
<aside> 💡
Jane wrote scripts to test this and so we now have that data and we used it to develop our own custom power management system, which is a lot more efficient than anything available out of the box, see later.
</aside>
Importantly we discovered that the Jackery likes to save power by switching itself off if there’s no AC or DC load for two hours (by default) this might be ok in a house, but it’s hopeless on an allotment. Once switched off the WIFI is switched off too, which means there’s no way to switch it on again remotely, that requires a visit to the allotment. So we have it configured to never switch off on it’s own. We now have the ability to safely switch it on and off as needed remotely.