Field Notes

2026-11-09 · Auckland, New Zealand

One drawing of the whole tunnel, and a head count

Five new sensors went on the bus today, the tomatoes set fruit, and I counted every plant in the channels for the first time since the outage. It is also the point where I can no longer explain the site to a visitor without a pen, so this note starts with the drawing I should have made in August. Everything in it is running tonight.

How to read it

There are three separate bodies of water and they never mix. The NFT channels on the left share one reservoir, so everything in them gets the same feed, and the plant list is chosen to live with that: lettuce, cos lettuce, spinach, a few bok choy, strawberries, garlic shoots and two melons that will outgrow the recipe and have to move. The buckets in the middle are one 130-litre loop for the plants that want twice the strength, tomatoes and capsicums. The coco system on the right is not recirculating at all: each irrigation is fresh feed from a 20 L tank, what drains out of the pots goes to the ground, and a cup of the runoff is measured so I know what the roots actually sat in.

Two of the three systems hang off the same cabinet controller, running as two independent fertigation instances with their own probes, pumps and targets. The bucket loop has its own smaller unit. All three keep their loops on the board; the cloud is a window, not a dependency. The ventilation and the wall fan belong to the NFT controller because that is where the air probe is, but the night rule from last week reads the bucket water temperature, so the drawing has one arrow that crosses systems.

What each crop is getting

• Channels. EC around 1.1 mS held in a band a hundredth wide, pH between 5.8 and 6.2 with acid or base, dose sizes learned from the reservoir's own response. Four flow meters at the channel inlets; under 1.2 L/min for two minutes is a blocked channel and a phone alert. An air stone comes on when the water passes 20 °C.
• Buckets. EC 1.05 mS as of last night, pH floor 5.8 with base only, since this water only ever drifts down. Each bucket has its own air stone. It is the warmest water on the site, 23 to 27 °C this week, and the reason the windows now stay open on warm nights.
• Coco. Feed 2.4 mS, pH 6.0 with acid only. Four irrigations a day of sixty seconds between eight and six, each pot through four drip stakes. The 20 L tank is refilled by a float valve in batches, and the A and B pumps are fed forward from the water meter so the new batch arrives at the right strength before the probe has finished thinking about it. Runoff reads 1.6 mS against the 2.2 that went in.

New eyes

The coco line has been irrigated on a clock since it started, because I had no way to see the substrate. Today four moisture-and-temperature probes went into the four pots and an air temperature and humidity transmitter went on the post beside them, all on one RS-485 bus into a spare port on the controller. First readings: air 19.2 °C at 87 % humidity after a wet afternoon, substrate 15 to 17 % in all four pots, 20 °C in the coco. The moisture number is a relative one. These are cheap dielectric probes calibrated for mineral soil and coco holds far more water than they will admit to, so I will be reading the shape of the day, the step at each irrigation and how far it falls before the next one, not the absolute value. The plan is to let that shape set the number of irrigations once the cucumbers start drinking seriously.

Getting five cheap sensors to answer on one bus took most of the morning and taught the firmware two things it did not know. These devices take 12 to 18 milliseconds to start replying, and they ignore any request that arrives less than about 10 milliseconds after the previous frame on the bus. With the controller's old 20 ms reply window nothing came back at all, and with no gap between polls every second reply went missing. Both are now per-device settings in the scan table rather than constants, the sensors get 60 ms and a 20 ms pause, and the bus has run clean since.

Plants

Head count in the channels this afternoon, done properly for the first time since the outage: 33 lettuce, of which 21 are the August planting that has been picked leaf by leaf for two months and is still sweet, 17 cos lettuce, 8 spinach, 4 bok choy that survived their own eviction notice, 6 strawberries, 3 garlic shoots and the 2 melons. Seventy-three plants in four channels.

In the buckets the tomatoes have set fruit. There are two: a bush variety that will not be pruned, and a grafted cordon whose side shoots had already grown into three proper stems before I got to it, so it keeps three leaders and loses every shoot from here on. The flower trusses grow from the stem, not from the side shoots, which is why pinching the shoots costs no fruit. The capsicums are half the height of the tomatoes and that is normal for the species; the water temperature is harder on them than the feed is. In the coco pots the cucumbers have tendrils and the first female flower at the tip, and the eggplants are doing what capsicums do, which is take their time.

Two bugs, both found by the plants

The coco system irrigated at 12:39 today, right after a firmware update, and again on schedule. The scheduler kept its "done this slot" marks in memory, so every reboot inside an irrigation window meant a second drink. It now writes the time of the last irrigation to its learning file, and after a reboot it rebuilds the day's marks from that: slots that started before the last recorded irrigation count as done, slots missed while the unit was off are not made up. The record decides, not the clock.

The second was not a bug in the plants' sense but it cost me a day of worry. The controller's second core reported 24 % load for a week, then 41 % after today's update with nothing new running. It turned out to be the load measurement itself: the microsecond clock used to time task switches is built from a millisecond tick plus a hardware counter, and for a few microseconds at each rollover the two disagree. Whether a task switch ever lands in that gap depends on the phase between two timers fixed at boot, so each boot got its own constant error, credited to whichever task ran first after the tick. The snapshot now reads the counter's overflow flag on both sides and corrects, and the real load is 22 %, with the new sensor bus costing about four points of it.

Honesty section

The bucket system's charts are still not on the public page. The coco irrigation is still a timer; the probes report but decide nothing yet. The substrate moisture values are uncalibrated and I have said so above, but they will still look like percentages on a chart. The capsicums and eggplants are behind and I have called it normal twice today, which is the kind of sentence that deserves a photo in two weeks. And the site still has no backup power, eight weeks after an outage killed a planting; the drawing above is complete except for the box that keeps the pumps running when the grid does not.

2026-11-08 · Auckland, New Zealand

A bigger fan, a rule for warm nights, and a week of wrong water temperatures

Three things happened today that belong in the same note: the exhaust fan was swapped for a 40 cm one, the ventilation logic learned to use the night, and I found out that the bucket system's water temperature I had been quoting for a week was the wrong number. The plants section is at the end.

Was the old fan doing anything?

Before touching the hardware I asked the logs. For the last four days the fan ran every afternoon, and the honest way to compare days with different weather is to bin every five-second sample by outdoor temperature and look at the tunnel temperature inside each bin. With the old fan running, outdoor 24 to 26 °C gave a tunnel of 27.4 to 28.2; outdoor 26 to 28 gave 30.0 to 30.6; outdoor 28 to 30 gave 31.6 to 31.9. Windows alone, fan off, gave almost the same numbers. The fan's share was about half a degree. That is what a small fan on a 30-metre tunnel is worth, and it is why the heat kept getting through the shade cloth.

The 40 cm fan went on the wall between four and five this afternoon, so it has exactly one hour of controlled running in the data. In that hour the tunnel sat 1.3 to 1.9 °C above outdoor; the old fan had held 2.5 to 3.7 earlier the same day, and the moment the new one switched itself off at 17:18 the gap went straight back to 2.9 and 3.4. Same hours yesterday, no fan, 2.7 to 3.5. So the new fan is worth about a degree and a half, three times the old one. One hour, one evening, weak sun; tomorrow's midday run is the real test. Two things to watch: whether the tunnel stays within a degree and a half of outdoor while it runs, and whether it runs for less than today's 456 minutes, because a fan that can actually get the tunnel below 26 °C gets to switch itself off.

The night the controller was wasting

The ventilation logic was a pure air-temperature ladder: open at 25, step up when cooling stalls, step down at 22, close at 20. No clock, no season, and it has worked all spring. But look at any evening this week. By 20:00 the air is 21 to 23 °C and the windows are closing. The NFT reservoir at that moment is 24 to 26 °C and the buckets are 25 to 27. With the windows shut the tunnel settles half a degree to a degree and a half above outdoor, the water sits two to four degrees above the tunnel, and it loses heat at 0.5 to 0.7 °C an hour before midnight and 0.2 after. By seven in the morning the NFT water is still 21 to 22 and the buckets 23.5 to 24.7. The coolest air of the day was outside, behind a closed window.

The fix is a second rule driven by water temperature, not air. If the water is above 22 °C, the outdoor air is at least three degrees colder than the water, outdoor is above 12 °C and the tunnel is above 15 °C, all for five minutes, the window gets a floor: it may not close below fully open. The floor comes off when the water drops to 20, or either guard trips, or outdoor comes within a degree of the water and there is nothing left to gain. The fan never takes part at night. There is no summer mode and no winter mode to switch between; in winter the water never reaches 22 at night and the frost guard holds, so the rule is simply silent, and it wakes up by itself when the nights warm. The one thing the site cannot sense is rain, so a drop of three degrees in outdoor temperature inside an hour, the signature of a front or a squall, limits the floor to the first notch for an hour.

It went onto the controller tonight and fired at 21:58, with the water at 24.4 °C, outdoor 18.8 and the tunnel 20.1. The window that would have been shut by then is fully open. What I expect from it is modest: the tunnel a degree closer to outdoor overnight, the water losing heat about forty percent faster, a morning reservoir about a degree lower. It will not touch the 27 to 28 °C afternoon peak, because that heat comes in through the sun on the channels and the tanks, and shading those is a separate job.

The number I got wrong

The bucket system's heartbeat carries two temperature fields: the raw probe value and the calibrated one, 3.4 °C apart. I had been reading the raw one, and reporting that the buckets ran two degrees cooler than the NFT reservoir. They run two degrees warmer. Corrected, the buckets were 23.4 to 26.6 at night this week, bottomed at 23.5 before dawn and reached 28 on Thursday afternoon. They are the warmest water on the site and the slowest to cool, losing three degrees overnight where the channels lose five, which is what twenty litres of dark plastic in a tunnel does and exactly why the reflective wrap from the last note is still on the list.

The same log turned up a second fault: two or three times a day the calibrated temperature dropped to between 9 and 17 °C for two or three samples and recovered over the next fifteen seconds, while the raw probe value in the same message had not moved. That is the signature of a burst of bad conversions from the 24-bit ADC slipping past the three-sample median and then decaying out of the two-second filter. Tank water cannot move two degrees in two seconds, so the firmware now refuses any sample more than two degrees from the filtered value unless five in a row agree, which still lets a real step through in ten seconds. That version went onto the bucket controller tonight as well, and the dashboard's automatic refill detector, which had been firing on the coco system's runoff cup drying out between irrigations, now watches each reservoir on its own.

Plants

The NFT channels were replanted today: ten Chinese cos lettuce, five strawberries, two melons. The previous four strawberries did not survive the September outage; they dried out in the channel. The chives, the bok choy that had bolted, the last capsicum and the pea all came out. The melons are the odd ones in a lettuce reservoir, they will want twice the EC once they set fruit and they climb, so they will either get a string or a move to one of the other systems. The bucket system's tomatoes and capsicums have rooted; their EC target went from 0.8 to 1.05 mS this evening and the loop put in its first fertilizer in three days within the hour. The coco cucumbers and eggplants have come through transplant. Their runoff is now reading 1.63 mS against a feed of 2.18, up from 1.23 two days ago, which is the substrate loading up as it should.

Honesty section

The fan verdict rests on one hour of evening data. The night rule has run for one evening. The bucket system's charts are still not on the public page, and after a week of me quoting its temperature from the wrong field, that is probably the right call for a little longer. The count of lettuce, spinach and celery that survived the outage has still not been taken; the register says "to be counted" and so do I. And the fault in the temperature filter had been in the data for at least six days before anyone looked at the minimum column.

2026-10-26 · Auckland, New Zealand

Eighteen lettuces back in the channels, and a second system on buckets

The channels have been mostly empty foam collars since the September power cut. Today eighteen lettuce seedlings went in, the first tray of what was sown in sponge blocks on the 20th. The controller is holding the reservoir at 0.9 mS while they root, roughly two thirds of the cruising value, and the target goes back up once the new roots are hanging in the flow.

Four buckets, two tomatoes, two capsicums

The other half of the tunnel got its first system today: four 20-litre buckets plumbed together at the bottom, a control bucket with the float valve, pump and probes, and a recirculating loop through all of them. Two tomatoes and two capsicums went in, all from pots, which means soil. On a recirculating system the soil has to come off, so each root ball was washed down to bare roots before it went anywhere near a pump.

The tomato root was 30 centimetres long and would not go through the slots of a net pot. The trick is to cut a cross in the pot's base, feed the washed roots through from the inside, and let the flaps hold the clay pebbles. The capsicum got the same treatment with one difference: its crown stays at the old soil line. A tomato stem buried deeper grows new roots along it; a capsicum stem buried deeper rots.

The buckets are run by a second controller, a smaller single-board unit that is still in development, with its own EC and pH probes and three dosing pumps. Its charts are not on the public page yet. A freshly planted system spends its first fortnight with the operator pulling the targets around, and that is not a curve anyone should learn from. They go public when it settles.

The loop that correctly did nothing

First question of the afternoon: why did the new system not dose when told to? It had not been told to. EC read 1.16 mS against a target of 0.9, so no fertilizer was due, and pH read 6.12 against 6.00 with the loop allowed to push pH up only, so no base was due either. Base fires below 5.80. A dosing loop that stays quiet when both readings are on the right side of their targets is the whole point. The buttons on the panel, meanwhile, want a three-second hold before they unlock, which is deliberate and which I had forgotten.

Water temperature, and what is not a chiller

The buckets sat at 22.9 °C this afternoon and read 26.7 on the day they were filled. Above about 25 the dissolved oxygen falls and the root-rot organisms wake up, and a spring like this one says the summer will sit there for weeks. A chiller is the last thing on the list, not the first. First the buckets get wrapped in reflective foam, because a dark bucket in a sunlit tunnel takes most of its heat through the wall. Then the control bucket moves out of the tunnel into shade. If that is not enough, thirty metres of polyethylene pipe buried a metre down, where the ground stays at 16 °C all year, will take two or three hundred watts out of the loop for no running cost. Under all of that: more air, a beneficial bacillus added weekly, and a lower EC in the heat.

One controller, several reservoirs

A third system is being wired up this week, coco slabs in buckets with drip arrows, fed from a 20-litre batch reservoir and draining to waste. That is the third kind of hydroponics on one site, which exposed a limitation in the firmware: the dosing control was written for one reservoir, with the pump coils, the probe channels, the saved files and the dashboard fields all assumed to be the only ones. It has been restructured today so that a reservoir is an instance. A binding says which points and channels are its probes, pumps, floats and meter, and anything the system lacks is simply marked absent; adding a reservoir is one more binding. Every input and output is addressed as a point in the controller's scan table, so a third-party Modbus soil probe on a front RS-485 port binds the same way as a module on the backplane. The old system keeps its commands, its files and its dashboard field unchanged. The new one is addressed by name.

Two small design decisions came out of the coco planning that are worth writing down. Drip arrows run at half a litre a minute in total, which is below where a hall flow meter starts turning, so there is no meter on the irrigation side; the reservoir's float switches give a fixed batch volume and the pump seconds per batch give the rate, and a rate that drifts down is a clogging line. And the refill uses a plain float valve on the mains with a meter on the inlet rather than a solenoid, which means the loop doses for each litre as it arrives, the way the NFT reservoir already does, instead of stopping everything for a batch.

Honesty section

The restructured dosing firmware compiles and reads the same as the old one line for line, but it has not been on a board yet. The bench unit that would have regression-tested it left with a customer last month, so it goes onto the greenhouse controller with the next batch of changes and earns its keep by producing the same journal as before. The water temperature plan above is a plan; nothing is wrapped yet. And the eighteen lettuces are a lot fewer than the ninety-four plants this system started the winter with.

2026-10-20 · Auckland, New Zealand

Shade cloth on, fan on the wall, and the first day's numbers

October has been hot in the tunnel. On every day this month when the outdoor air passed 24 °C the greenhouse passed 33, with peaks between 36 and 38 and the roof vents already at their last stage by mid morning. Tomatoes stop setting fruit above about 35, and leaf temperatures above 32 shut photosynthesis down, so the heat was costing more than any shade would.

Two things went up today. A 50 % shade cloth, 5 by 10 metres of UV-stabilised HDPE, laid flat over the film and tied down rather than raised on a frame, because this site is windy and a flat cloth that stays put beats a raised one that flaps. And a 2000 m³/h exhaust fan in one gable end, with the opposite end opened up as the inlet. The fan is mounted and its controller output is assigned and tested; the mains-side relay that actually switches it is the next job, so today's data is the cloth alone.

How to read a single day

One hot day against another proves nothing, so I do not compare the inside temperature. I compare the difference between inside and outside, hour by hour, which takes the weather out. The controller logs both: the outdoor probe and the greenhouse air probe sit on the same four-channel water-quality module that reads the reservoir, so the two numbers come from the same board at the same minute.

The numbers behind the chart, taking the mean of inside minus outside between 11:00 and 15:00 with the vents fully open on all four days:

Day	Outdoor max	Inside max	Rise, 11 to 15 h	Hours above 30
17 Oct	20.2	32.4	+10.5	1.1
18 Oct	23.6	35.6	+10.1	4.8
19 Oct	22.4	33.2	+8.2	1.4
20 Oct, cloth	25.1	29.6	+5.6	0

Today was the warmest outdoor day since the 14th and the greenhouse did not reach 30. The 11 to 15 h rise dropped from 8 to 10 kelvin to under 6, which is the level this tunnel previously only managed on overcast days. The house also woke up later: the air passed 20 °C around 08:30 instead of between 07:30 and 08:15 on the three days before. My estimate is that the cloth takes 3 to 5 kelvin off the afternoon, with the caveats below.

The spike at 08:40

The one place the orange line jumps is 08:40, when the inside briefly touched 27 °C and the rise hit 9. That is the closed house heating before the first vent opens. The vent rule arms at 25 °C and waits three minutes before the first stage, and on a bright morning the air gains two degrees in those three minutes. Every sunny day has this spike. It is worth a lower opening threshold on mornings that are already warm, and that is on the list.

What the fan will do

The fan is not another notch on the vent ladder. The ladder already escalates a stage when the house has sat above 25.5 for ten minutes and is not cooling, and under shade cloth a fully vented house sits between 25 and 29 all afternoon. That rule would run a mains fan every day from mid morning to evening for a degree or two. So the fan has its own two thresholds on top of the ladder: on when the air holds 29 °C for two minutes, off when it holds 26 for five. The vents stay fully open underneath a running fan, and the 20 °C close rule still shuts everything if the weather turns. The public dashboard shows the vent stage as a number; stage 4 means the fan is running.

Honesty section

I did not log the minute the cloth went on, so I cannot split today into before and after. There is no light sensor on site, and the outdoor curve says it was a clear day without being able to prove it, so the 3 to 5 kelvin figure needs a few more sunny days before I would defend it. The fan output was pulsed from the dashboard with nothing on the far side of it, which proves the control chain and nothing about airflow.

The camera has been returning a placard instead of a picture since the 19th. The vendor's cloud service that the snapshot pipeline pulled from has ended its free period and locked the device out, stills included. The lesson is one this project already applies to control: nothing in the loop should depend on a third party's server staying friendly. The replacement is a camera that pushes its own snapshots to our server on a schedule, which is being tested now.

2026-10-05 · Auckland, New Zealand

Seven days and seventeen hours without power

There has been no post since 12 September, and for the last week of that there was no data either. On 26 September at 17:10 rain got into something on the greenhouse circuit and the earth-leakage breaker tripped. Everything on site is behind that one breaker: the circulation pump, the dosing pumps, the vent motor, the controller. The power stayed off until 4 October at 11:16.

The plants

Almost all of them are dead. An NFT channel holds no reserve. The roots sit in a film of moving water, and when the pump stops the film drains away in minutes. Seven days of that is not survivable for lettuce. I have no photos and I am not going to pretend otherwise. The channels get cleaned out and replanted in the next few days.

What the controller did

Nothing, for seven days, because it had no power. The server noticed the board go quiet and sent the offline alert to my phone, and the public dashboard carried a notice saying the site was unpowered so that nobody read the stopped curves as a crashed controller.

When the power came back the board started by itself and logged the reset cause as a brown-out. It restored its dosing settings and the gains it had learned in September, then waited twelve minutes before making its first dosing decision. Its clock had kept running on backup power and was 17 seconds off when it next synchronised. The four gutter flow meters read 1.2 to 1.3 L/min straight away, the same as before the cut.

The reservoir had barely moved: EC was 1295 µS/cm in the last record before the cut and 1299 in the first one after. The two pH probes disagreed by 0.8 for about half an hour after sitting in still water, which raised the probe-disagreement alarm, and then came back together on their own.

Then the hottest day on record

Today the greenhouse air reached 36.3 °C at 12:02 with the roof vents at their third and last stage. That is the highest reading since logging started in August; the previous high was 34.3. The reservoir peaked at 26.8 °C in the late afternoon, also a record, and spent nearly seven hours above 23. With the channels about to be empty that matters less this week than it will after replanting.

Honesty section

The electronics came through a week-long outage with nothing lost except the week. The crop did not, and a controller that restarts cleanly is no use to plants that died while it was off. One breaker for the whole site was the weak point, and the pump shares it with whatever leaked. I have not decided yet how to keep water moving when that breaker goes. The camera has not come back online either. The dashboard stats page now marks the outage days as an outage instead of as missing data.

2026-09-12 · Auckland, New Zealand

Twenty-eight hours of flat pH, and the number the loop could not learn

Yesterday's post ended with the new dosing loop switched on at 14:14. This is what the first twenty-eight hours look like, what the loop learned, what it could not learn, and the two changes that went to the greenhouse controller tonight because of it.

The numbers

The day before the switch, pH fell from 5.89 to 5.59, a quarter of a unit, because this fertiliser recipe pushes it down and nothing was pushing back except me. In the twenty-eight hours since, the one-minute readings have all been between 5.82 and 5.87, standard deviation 0.007 pH. That is one minimum shot wide, which is what the design said it would be: the loop fires 2 ml whenever its running estimate says the tank is about 0.03 short, and 2 ml moves the tank about 0.03. EC held 1300 to 1310 against a target of 1300, standard deviation 3 µS/cm. Twice today the float valve added three and a half litres of rainwater and EC dropped to 1280; both times the loop had it back above 1295 within four minutes of the drop, because it fired the moment the reading came in rather than waiting for the next scheduled decision.

The loop also learned. The A/B gain it started with, 14 µS per 50 ml of each part, was measured on the old liquid fertiliser; after nine shots it had moved the stored value to about 20 µS per 50 ml, which is what the dry-salt mix actually does. Individual shots are noisy, a 16 ml shot moves the reading by five to eight counts on a one-count meter, but the two larger shots it fired after the top-ups landed on the same number as the average, so I believe it. The EC drift it learned, about 70 µS per day of plant uptake, matches the daily A/B total to within a few per cent.

The number it could not learn

The pH-up pump's gain never changed from its starting value, and it took me an hour of staring at the event log to see why. The loop only trusts a shot as a measurement of the pump when the expected movement is at least 0.04 pH, four counts, because the probe's last digit is noise. But the loop, doing its job well, never needed more than 2 ml at a time, and 2 ml is expected to move 0.026. Every shot was below the threshold. Meanwhile the drift estimator saw "pump fired, reading did not move" and booked the whole thing to drift, which crept from the seed value of 0.15 pH per day to 0.43 per day and was still rising when I looked.

The control result is fine either way; the tank does not care which of the two numbers is right as long as their ratio is. But the two are not separable from minimum-sized shots alone, and the wrong split has a real consequence: I told you yesterday the litre of working solution would last half a year at 12 ml a day. The pump has actually delivered 35 ml a day, so it is two months. Either nitrification really did speed up when pH went from 5.6 to 5.85, which is plausible, or a two-second pump pulse delivers less than the calibration says, which is also plausible. I do not know yet, and the loop as written would never find out.

Two changes, pushed tonight

The first is a probe shot. When five consecutive pH shots have been too small to learn from, the next one that was going to fire anyway is enlarged to the smallest size the learner accepts, 4 ml at the current gain. No extra shots, one slightly bigger one every seven hours or so, an overshoot of 0.03 at most, and in return a real measurement of the pump. The first one should land tomorrow morning.

The second closes the top-up gap properly. The controller already counts the water meter on the fill line. From tonight, every 0.1 litre the float valve lets in is converted into an EC debt, volume times target divided by tank volume, and paid back through the learned A/B gain as soon as it adds up to a minimum shot and the pumps are free. A three-and-a-half-litre fill owes about 70 ml of each part; the pumps start on it while the valve is still open and finish in about three minutes, instead of the loop noticing a dip and chasing it afterwards. The main loop holds its decision while the valve is open and restarts its settling clock after each compensation shot, so the two cannot both pay the same debt. The tank volume became a setting; the daily A/B cap went up because the compensation rides the same counter.

Honesty section

Twenty-eight hours is twenty-eight hours. The flat line is real and it is the best this reservoir has ever looked, but the learned drift is a number I have just told you is probably wrong, and the top-up code has not seen a top-up yet. The learned values survived tonight's firmware swap and reboot intact, which was the one thing about persistence I had not yet tested. I will report the first probe shot and the first automatic fill compensation when they happen, including if they do something silly.

2026-09-11 · Auckland, New Zealand

A fourth pump, a wrong prediction, and a dosing loop that now learns

Three things today. The controller got a pH-up pump, which I had said two weeks ago it would not need. The dosing loop was rewritten from "wait for the edge of the band, then fire" to a loop that estimates the drift, doses ahead of it, and measures its own pumps. And I pulled five plants to look at their roots, because a shop page said falling pH means root disease. It does not, here.

The prediction that was wrong

On the 29th of August I worked out from the bottle label that the liquid A/B fertiliser carried a lot of its nitrogen as ammonium, which is why the reservoir pH fell every day. The plan was to switch to dry salts and let the pH float back up on its own, as nitrate-fed lettuce normally does. The dry salts went in last week and the pH kept falling, 0.1 to 0.2 a day. The reason is on the second bag: the potassium-side product lists 15 % nitrogen as 11.3 % nitrate and 3.7 % ammoniacal. Mixed with calcium nitrate that is about 16 % of the nitrogen as ammonium, which is above the roughly 10 % where the net effect flips from pushing pH up to pushing it down. I had checked one bag and assumed the other.

So the direction a reservoir drifts is set by the fertiliser recipe, not by the water or the crop, and a controller that only has an acid pump is half a controller. That is a product lesson as much as a farm one: the pH channel has to be bidirectional, and which pump does the daily work depends on what the grower buys.

The fourth pump

A fourth peristaltic pump went onto output 4 of the relay module, fed from a bottle of potassium hydroxide "pH Up" diluted about 1:30. The concentrate is 48 % KOH, strong enough that a millilitre of it would overshoot the whole tank, so it is diluted first and the pump only ever sees the working solution. The first shot was 20 ml by hand at 12:22, with the tank at 5.59: the pH rose to 5.85 and levelled out in about twelve minutes, and EC did not move. That one measurement, 0.013 pH per millilitre, became the pump's starting calibration.

A loop that doses ahead of the drift and measures itself

Until this afternoon the dosing loop was the simplest thing that works: if the value sits outside the band for five minutes, fire a fixed shot, wait twenty minutes for mixing, look again. It is safe and it is easy to reason about, but the ripple is the width of the band by construction, and a fixed shot is either too big for a small error or too small for a large one. The new loop does three things differently.

It works in cycles of twelve minutes, the settling time measured this morning, and makes one decision per cycle. The decision starts from the error, target minus reading, and adds a feed-forward term: the drift it expects over the next cycle, carried over from cycle to cycle until it is worth a shot. The shot size is that need divided by the pump's gain, so a 0.03 error gets 2 ml and a 0.1 error gets 8 ml. Nothing fires until the computed dose reaches a minimum, 2 ml for the pH pumps and 15 ml for A and B, which puts a floor under the ripple of about 0.03 pH rather than the 0.1 to 0.2 of the old band. Only one variable is dosed per cycle, EC first, so that when the next reading comes in the loop knows which pump to credit.

That credit is the learning. After each shot the loop takes the change over the cycle, subtracts what the drift alone would have done, and divides by the millilitres. That is a fresh measurement of the pump's gain, and it is blended into the stored gain, 30 % per observation, clamped to a fifth and five times of the starting value so a stuck probe cannot teach it anything absurd. Drift is learned the same way from three-hour windows, from the residual once the shots are accounted for. A cycle in which the float valve added water, or somebody poured something by hand, or the circulation stopped, is thrown out. Three consecutive shots that should have moved the reading and did not is a fault and the loop switches itself off: empty bottle, tube off the pump, dead probe.

Two rules came from the person who runs this farm, and both are right. The learned values are written to flash every time they change, so a reboot does not start from ignorance; and the starting values are the measurements already made here, not textbook guesses. The first learning event landed at 15:53: an 18 ml A/B shot moved EC by 6 µS/cm where 5 was expected, and the stored gain moved from 0.28 to 0.31 µS per millilitre. Every one of these is a line in the event log, so the chart will show what the loop believed and when it changed its mind.

Honesty section: the roots

The reason I was reading a shop page in the first place is that it said a falling pH "could be root diseases attacking your plants". With the water having been above 24 °C on three afternoons this month, that deserved a look rather than an argument. Five plants came out. The roots are cream to tan, not white, which is what a month in nutrient solution with chelated iron does to them, and the tests that matter all passed: distinct strands that do not slough off when you run them through your fingers, new white tips, root hairs along the new growth, and no smell. The water consumption has held at 6.5 to 7.5 litres a day all week, which is the other thing rotting roots do not do. The drift is the fertiliser. The air pump from Monday is still the right precaution.

2026-09-08 · Auckland, New Zealand

The blocked gutter, an air pump, and a rule about water temperature

Three small things today, each of which is the kind of thing a farm system is actually made of: a flow meter that had been telling the truth for a week while I explained it away, an air pump that got its own rule, and a fertiliser bottle that ran dry on paper before it ran dry in fact. All of it is in the public data.

Gutter 3 was never slow. It was half blocked

Each of the four NFT channels has a small pulse flow meter on its feed line. For a week the dashboard showed gutters 1, 2 and 4 at 1.4 L/min and gutter 3 at 1.2. When I measured them with a jug on the 4th, gutter 3 came out at 1.0. I wrote that down as the true value and moved on, as if the meters had personalities. This morning I put a hand into the feed end of gutter 3, pulled out a wad of root and leaf that had drifted down from the lettuce, and the meter went to 1.4 within a minute. Same as the other three. The 1.0 in the jug and the 1.2 on the chart were the same blockage seen at two stages of growth.

Two lessons. The clean baseline for this pump and these channels is 1.4 L/min on every line, so from now on anything below that is a blockage question, not a meter question. And the blocked-line alarm, which fires when a gutter stays under 1.2 L/min for two minutes, never fired, because 1.2 was exactly where the blocked gutter had settled. I had set that line from the jug numbers, and the jug numbers already had the blockage in them. The line can move up now that I know what clean looks like.

An air pump, and why it needed a rule

An aquarium air pump and an air stone went into the reservoir today, switched by output 9 of the relay module. The first version of the control logic was "on". That lasted about an hour, until I thought about what happens after a reset. This controller resets itself when it decides its network stack is wedged, and it has done so twice in the last week. Outputs come up off after a reset, which is the right default for pumps that dose acid, and the fan, and the roof. But nothing in the software knew the air pump existed, so nothing would have turned it back on. The pump would have stopped one night and stayed stopped until somebody looked in the barrel and wondered where the bubbles went.

So the pump got a rule, the same shape as the roof vent and the dosing loop. It runs when the water is at or above a set temperature for one minute, and stops when the water has been a degree below that for five minutes. The first valid reading after a boot decides immediately, so a reset cannot leave it silently off. If both water temperature probes are lost for ten minutes it runs anyway, because bubbling a cool tank costs nothing and not bubbling a warm one costs roots. The set temperature is a setting, not a constant, and it is logged when it changes.

I set it to 20 °C. The usual target for nutrient solution is 18 to 22, and the organisms that cause root rot get going in earnest above 24. Dissolved oxygen falls as water warms while the roots want more of it, so a warm tank is the one that needs air. Aeration does not cool anything; if the tank ever sits above 24 in summer the answer is shade and cooling, not a lower setpoint. Starting the pump at 20 just means it is already running by the time the risk begins. Today the water was 22.7 when the rule went live, so the pump has been on since. It should switch off some time after midnight when the tank drops under 19, and back on tomorrow morning. One prediction to check: bubbling strips dissolved carbon dioxide, so the pH should creep up a little while the pump runs. With a fertiliser that pulls pH down all day, that would be welcome.

The bottle that ran out on paper

The fertiliser stock on the dashboard is a ledger, not a sensor: each refill I log is a starting volume, and every dose the controller makes is subtracted from it. Last night the ledger for part A reached zero and the phone said so. The bottle was not actually empty, because I had topped it up the day before and never told the system. This morning it got 1.5 litres and the log entry to match, and the ledger says four days at the current rate. The refill was logged from a new box on the dashboard itself, from the phone, standing next to the barrel. Until today that took a script on the laptop, which is exactly why the entry was missing. The same box takes free-text notes, which is how the gutter cleaning got its timestamp on the chart.

Also today

The air pump is the reason a new module went on the drawing board this afternoon. The existing 16-channel output module switches 24 V with solid-state outputs, which is right for valves and small pumps and wrong for anything on mains. Today that gap was covered by one interposing relay on a DIN rail. A 16-channel relay output module that fits the same housing family is now being designed. More on it when there is a board to photograph.

2026-09-07 · Auckland, New Zealand

Four probes in a bucket, and the alarm that sent me back to the greenhouse

Two days ago I promised to put all four temperature probes into one bucket of water and report what they said. I did, and one of them was wrong enough to change a conclusion. Later in the afternoon I knocked a conductivity probe out of the flow cell without noticing, and the system noticed for me. Both stories are in the public data.

The bucket test

At 12:34 all four PT100 probes went into the same bucket. I had checked the water with a separate thermometer: 21.7 °C. The two flow-cell probes read 21.5 and 21.6. The reservoir probe read 22.0. The inside-air probe, the one behind the "colder inside than outside" paragraph, read 20.7. A spread of 1.3 °C between four probes of the same type is not what I guessed on Friday. I said they would agree within 0.3 and that the night-time inversion was real. Half right. The air probe was reading a full degree low, so the 2.1 °C inversion I reported was really about 1.1. The effect is still there, the film still lets heat radiate out on a clear night, but it is half the size I claimed. The paragraph on the 5th stays as written, because that is what I believed at the time; this one is the correction.

The fix is a one-line offset per channel. Each probe got told "the water is 21.7" and the module worked out its own correction and saved it. Afterwards all four read 21.7 or 21.8. Then the two flow-cell probes went back to their places and settled 0.25 °C apart, which they had not been in the bucket. So the flow cell has a small real gradient between the two positions. I nudged them to their midpoint anyway, because two water temperatures on one dashboard that disagree by a quarter of a degree make people distrust both. That is cosmetic and I am saying so. The absolute reference is the bucket, not the nudge.

16:05: probe out, pumps held, phone rings

Working in the tunnel in the afternoon I caught the cable of EC probe 2 and lifted the electrode out of the flow cell. I did not notice. The controller did, in six seconds. With the electrode half in air the reading fell to 839 µS/cm against 1292 on probe 1, the two disagreed by more than the allowed gap, and the dosing loop went on hold. Six seconds later the module declared probe 2 invalid outright and stopped publishing it at all, which is why the orange line simply disappears in the chart. From that point the loop was back to running on probe 1 alone, the designed fallback when one probe is bad rather than merely different. It dosed once at 16:21 after the float valve had topped the tank up with 3.5 L. That top-up was real; the water meter counted it.

The phone alarm came at 16:15, ten minutes after the fault. That delay is on purpose. An invalid probe has to stay invalid for ten minutes before anyone gets paged, otherwise rinsing an electrode or swapping a bottle would ring the phone every time. I was walking out of the greenhouse, looked at the message, went back in, and there was the electrode hanging in the air. Back in the water at 16:35 it read 1366 for the first sample, an air bubble in the electrode cavity, then 1284 a minute later, seven µS/cm from probe 1. Alarm cleared at 16:37. I should have taken a photograph. The chart will have to do.

Honesty section: the day the phone was quiet

The reason I checked the phone at all is that it had been too quiet. The morning report had not arrived, and neither had the stock warning for the fertiliser bottles that I knew were nearly empty. The server log said both had been sent. They had not. Two days earlier, adding a small feature to the notification settings, I rewrote a configuration file and dropped one line from it, the line that says where the messages go. Nothing changed at the time because the running process still had the old setting in memory. At a restart the next night it reloaded the file, the destination was blank, and from then on every message was written to the log and sent nowhere. There was no error, because sending to nowhere is not an error. Fixed in the morning, and the bottles got their 15 litres of B in the afternoon. The lesson is old: after changing a config file, check what the running process actually has, not what the file says. The absence of a message is the only symptom you get.

Also today

The greenhouse camera spent the morning stuck in infrared mode, black and white in full daylight, so the canopy-cover number skipped two frames. A power cycle fixed it, and while it was reconnecting the cloud service handed my capture script a white "device offline" placard as if it were a video frame. The script accepted it. It now checks for near-white, colourless frames and throws them away.

At 15:08 the controller lost its cloud connection for thirty minutes and reset itself, which is what it has been told to do since the August incident where a stuck network stack kept the board silent for hours. It was back in under a minute, the vent logic re-read the air temperature on boot and reopened the roof to full. The dosing loop waited its twenty-minute grace period before making any decision. Nobody in the greenhouse would have noticed, and that is the point.

2026-09-05 · Auckland, New Zealand

A slow probe, a narrower band, and the coriander goes back to soil

Nothing broke today. This is what most days look like once a system is running: one sensor is getting worse, one setting needed changing, one crop didn't work out, and one chart was giving the wrong impression. All the numbers are in the public data if you want to check them.

pH probe 2 is wearing out

Both pH electrodes were recalibrated yesterday, in the same buffers, one after the other. Overnight they read 0.05 pH apart and stayed there while the water cooled from 22 to 15.5 °C. That is what a calibration leaves behind, a fixed offset. Today was different. In six hours in the same tank, probe 1 moved 0.03 pH. Probe 2 went up 0.06 and then down 0.12. The gap has nothing to do with water temperature, because it sat still through last night's 6.5 degree drop. The electrode is just wandering. Its slope also came out under 90 % of theoretical yesterday. Put those together and you have an old glass membrane: slow to respond, drifting, and only correct at the moment you calibrate it. I am going to replace it rather than calibrate it again. The dosing loop already runs on probe 1 and only uses probe 2 to check for disagreement, so the plants don't notice.

Part of this is on me. During yesterday's calibration the reading in the pH 7 buffer was still moving by a few tenths when I accepted the point. A slow electrode needs minutes to settle and I gave it seconds. The calibration tool will get a settling check, so a point can't be taken until the reading has held within 0.01 for a minute.

Dead band cut in half

The feed loop dosed five times last night. Every dose was triggered at the bottom of the ±20 µS/cm band around the 1300 target, and EC never got back to the middle. One 50 ml shot of each part adds about 14 µS/cm, so with a 40 wide band the loop was happy to sit on the floor. I changed the band to ±10. That should mean about twice as many shots of the same small size, and the tank should sit around 1300 instead of just above 1280. The daily fertiliser cap is still there as a limit.

Colder inside than outside

Clear night, clear morning. At 07:00 the air in the tunnel was 12 °C. At 08:00 it was 22. The roof went from closed to stage 3 in twenty minutes starting at 08:20, which is the first time it has climbed that fast in the morning. What surprised me is the night. For the last two nights the inside reading has been below the outside reading all night, by as much as 2.1 °C at 05:00. There is a real explanation. Plastic film lets infrared through, so on a clear still night the ground and leaves inside radiate heat to the sky as if the film wasn't there, and the film stops the air mixing that would bring warmer air back in. It is a known effect in unheated tunnels. It is also exactly what two probes with different offsets would look like. So tomorrow all four temperature probes go into one bucket of water for twenty minutes. My guess is they agree within 0.3 °C and the inversion is real. If not, I will correct this paragraph.

Coriander: ten days, no new roots

Six coriander plants came into the channels from soil ten days ago. None of them grew a single white water root. Coriander has a taproot and does not like being moved at all, and going from soil to water on top of that was too much. They went into the garden bed today. Next time coriander gets sown straight into the foam or not at all. In their place there is one pea seedling from a primary school science experiment. It arrived today and will need a string to climb within two weeks.

On the way past I pulled a lettuce with wilting outer leaves to look at its roots. The old soil plug in the collar was black and matted, the fine roots inside it were brown, and there was a grey fuzz on the surface. It looked like root rot. But the new roots outside the plug were white, firm and translucent, and there was no smell. Rot smells sour or like sulphur. Dead potting mix smells of nothing. Two hand tests are enough: smell it, and pinch a brown root. If the skin slides off and leaves a thread behind, that is rot. This was a waterlogged soil plug and a healthy plant. I rinsed the plug off, kept the white roots, and put it back.

A chart that gave the wrong impression

The water meter panel used to plot cumulative litres. That is a staircase that only goes up, and at a glance it looks like the tank is being topped up all the time. It now plots litres per minute, so a top-up is a spike and the rest of the day is a flat zero. The cumulative total is still in the raw files, which is where the daily totals come from.

Next: the four probes in a bucket, a new pH electrode, whether the narrower band actually puts EC on 1300, and a string for the pea.

2026-09-02 · Auckland, New Zealand

Pull a probe out and nothing happens. That is the feature

Today the system got attacked on purpose. Probes yanked out of the tank while the control loop watched, reboots dissected for fingerprints, and a day of numbers handed over to the person the numbers are actually for. Every step below is timestamped in the public data.

The pull test: two probes, two directions

The verdict experiment promised yesterday. Pull probe 2 out of the tank for eight minutes: the survivor moved less than 0.01 pH, which is the resolution floor. Pull probe 1: same result for its survivor. Zero electrical cross-effect in both directions, which is the number a customer should demand.

The entertaining part is what the pulled probes did. A glass electrode out of the tank keeps a wet film for minutes, and reads its own film instead of the water: probe 2 drifted smoothly down to pH 5.0, probe 1, a different brand with a different junction, drifted up towards 6.3. Two spikes on the chart, one down, one up, each electrode's personal signature, while the neighbour's trace stayed ruler-flat. That asymmetry is also a warning: a moist probe in air is electrically indistinguishable from a probe in water, so software cannot detect the pull for several minutes, and probe 1's air-drift climbed to within 0.04 pH of the acid-dosing trigger. The dosing loop now cross-checks the two probes and freezes acid dosing whenever they disagree beyond a configurable band. Configurable, because an installation that splits its probes across two tanks would find the cross-check meaningless.

Three reboots with no fingerprints

Morning drama: the controller silently reset three times in forty minutes. Not the watchdog, not a fault handler, not a commanded reboot, not a stack overflow. Every instrumented path came back clean, which was itself the alarming part. The response was to make anonymity impossible: every intentional reset in the firmware now writes its reason into battery-backed RAM before pulling the trigger, the fault handlers' black box is read out and journaled at every boot, and a reset that arrives with neither leaves the word UNNAMED in the log as a confession that something jumped the rails. The epidemic stopped the same day and has not recurred; the trap stays armed. Sometimes the deliverable is not the culprit but the forensics kit.

Meanwhile, for the farmer

The dashboard grew a stats page: daily water, feed and acid consumption computed from the journals, fertiliser stock countdown from refill notes, feed cost per day (four cents, it turns out), growing degree days, comfort hours, a red/yellow/green day status, and the local forecast. The idea is that a grower should get the morning report from one glance, not from asking an engineer to pull data. The water meter now journals every top-up with its volume, which immediately sorted a real 2.5 L refill from a calibration artifact that chemistry alone had confused. And a camera went up over the channels: timelapse first, canopy-coverage curves next. Transpiration and pixels agreeing about growth is the plan.

Next: whether the new nitrate-heavy fertiliser really pushes pH upward like the chemistry says it should, the first canopy-coverage numbers, and a week of the farmer's stats page in daily use.

2026-09-01 · Auckland, New Zealand

The greenhouse learns to feed itself

At 19:43 tonight the controller decided, on its own, that the reservoir was hungry. EC had sat below the trigger line for five straight minutes, so it ran pump A for 63 seconds, then pump B for 63 seconds, fifty millilitres of each fertiliser part, and wrote the dose to the journal as ec-low instead of manual. Twenty minutes of mixing later the curve landed where the arithmetic said it would, and an hour after that it decided it wanted one more round, and took it. Eleven days after the first seedling went into a channel, the system feeds itself.

Three pumps and a posture

Chemicals get a stricter contract than windows. The pumps boot off after any restart and a human has to re-arm the loop each time; one pump runs at a time; each pump has a daily cap; a single manual shot has a ceiling; and if the sensor reading is missing or implausible the loop refuses to dose at all. A probe reading air must never be allowed to conclude the tank needs a whole bottle of fertiliser. The auto rule itself is the same one I had been executing by hand for a week: below band for five minutes → one measured dose of A then B → wait out the mixing → look again. The controller just does it without sighing.

The water meter takes the stand

Its first day on the pipe, the meter did no metering and a lot of testifying. Twice today the EC chart stepped down and the software wrote top-up detected in the journal. Dilution, says the chemistry. Both times the meter had counted zero pulses. No water had entered the tank. Both steps turned out to be the measurement scale itself moving (next section), and the detector had been fooled, which is now provable, because a pulse counter on a pipe outranks any clever inference from chemistry. This is why you put a meter on every line you can afford to.

The thermometer that could only count in 0.8 °C steps

Two temperature probes in the same tank kept disagreeing by half a degree, and the disagreement wandered. Calibration chased it all day and never pinned it. The raw readings finally confessed: each channel only ever produced two values, exactly 0.8 °C apart. That is one ADC step. A PT100 on this front end moves the converter about 1.3 counts per degree, and the firmware was averaging 64 samples and then throwing the fraction away in an integer division, buying sub-step resolution and discarding it on the same line of code. Keeping the fraction fixed it: steps are now 0.05 °C and the two probes agree to a tenth. Side effect worth admitting: the old truncation had been biasing every temperature low by up to a degree, so the whole scale stepped up when the fix landed, and since EC is temperature-compensated, the EC reading stepped down ~2.5% at the same instant. That step is what the top-up detector mistook for water. One fix, one fake dilution, one acquittal by flow meter.

Honesty section: three firmware versions before midnight

Pulling one pH probe out of the tank moves the other by 0.02–0.04 pH. Small, but as a customer I would want it to be zero, so tonight I tried to make it zero. The two probes' reference contacts already sit on separate solid-state switches, so the firmware can tie one reference at a time and let each channel read purely against its own. Shipped it, pulled a probe, and the surviving channel wandered a quarter of a pH unit for minutes instead of 0.04 for a second. The physics I had ignored: the water itself needs at least one connected reference pinning its electrical potential at every instant. Naive turn-taking leaves the tank adrift every time the absent probe's turn comes around, and a glass electrode takes minutes to forgive that. Version three, an hour later, grants a measurement turn only to probes whose own readings prove they are wet. Pull one out and the survivor keeps the water pinned full-time. It is live now; the verdict experiment runs tomorrow in daylight. All three versions and both failed tests are on today's charts, timestamped.

Also today

The water-quality board was swapped for the new hardware revision, and the greenhouse gained an outdoor temperature channel in the bargain. The public dashboard now shows outdoor, greenhouse air, and two water temperatures as separate curves, which will make the vent controller's decisions much easier to audit against the weather.

Next: the pull-test verdict, the first full day of closed-loop dosing, and what a water meter says about a float valve's honesty over a whole week.

2026-08-29 · Auckland, New Zealand

Day eight: the first bowl

Eight days after the first plants went into the channels, the greenhouse fed us. Outer leaves off the bok choy and the lettuce, every coriander top, one bowl. Nothing was pulled: the plants stay in their collars and keep growing, so the same 84 crowns will be cut again in a few days. It is a small harvest and it changes nothing on the dashboard, except that from now on the transpiration curve is measuring a crop that is also being eaten.

Why chives, in a lettuce system

Garlic chives are the least demanding thing you can put in nutrient film: perennial, frost-hardy, indifferent to the pH and EC a lettuce wants, and happy with the nitrogen form that gives lettuce trouble. Cut them and they tiller; by late summer a fifteen-shoot clump is thirty or forty. They also make a useful control: they share the reservoir with everything else, so if the chives ever sulk, the water is the problem. If only the lettuce sulks, the lettuce is.

The pH verdict is postponed

Yesterday's post hung a called shot on today: pH was supposed to turn back up within 48 hours of the big fertiliser day. It did not. This morning it was still sliding, so I raised it deliberately with 0.9 g of soda ash into 165 L, predicted +0.2, measured +0.18 and +0.19 on the two probes three minutes later, which at least says the reservoir's buffer capacity is now a known number. Then the day did something the day before had not: pH drifted up through the afternoon and kept drifting up after dark, on a day that got three fertiliser doses, when the previous day with no doses at all had drifted down. Two consecutive days, opposite behaviour, and I have several candidate explanations that each fit one day and not the other. I am not going to pick one tonight. Tomorrow's overnight curve is the tiebreaker, and it gets its own post, including the fertiliser label arithmetic, once I know whether it survives contact with the data.

Next: the pH tiebreaker, the fertiliser label, potassium bicarbonate versus soda ash, and the water meter.

2026-08-28 · Auckland, New Zealand

The ladder walks both ways

Yesterday the vent controller made its first decision: it opened a window. Opening is the easy half. A thermostat proves itself on the retreat, knowing when the heat is spent, giving ground a stage at a time, and shutting the house before the night gets in. Today it did all of that, and not the way I predicted it would.

Wrong about my own controller

The control law has two ways down. A patient one: air at or below 22 °C sustained ten minutes, drop one stage, repeat. And a blunt one: at or below 20 °C for two minutes, close everything from whatever stage you're at. Between 22 and 25 is a hold band, no climbing, no retreating.

Around midday I confidently explained that at this time of year the patient path is decorative: a late-winter evening falls through 22 to 20 faster than the ten-minute step-down can accumulate, so the blunt rule always wins and the log will just read 3->0 close. The greenhouse spent the afternoon preparing a correction. A mild, slow cooldown parked the air between 20.7 and 21.2 °C for half an hour, and the journal came back with this:

Every rung, both directions, exactly ten minutes apart on the way down. The climb was legitimate too, 26.9 °C at the second escalation, real hot air, not yesterday's evening-shaped false alarm. Day two of autonomy and the machine's log is already correcting its author's forecasts. That's the right direction for the errors to flow.

A fan joins the night shift

Second air-moving device on site: a 12 W circulation fan, hung just above the top canopy, aimed down the 8-metre axis, on its own power supply, running around the clock. It looks like an afterthought. It's doing three jobs, and the subtle one is the reason it went in.

The obvious two: mornings here start with the film dripping wet, and clear cold nights leave the air in layers, warm at the ridge, cold pooling around the bottom channel. Moving air dries the film and stirs the layers flat. The subtle one is about calcium. Still air wraps each leaf in a saturated boundary layer; transpiration stalls; and calcium, which only travels with transpired water, stops reaching the leaf tips. In lettuce that arrives as tipburn, and on a site that runs entirely on rainwater, every milligram of calcium comes from the nutrient bottle. A gentle draught that keeps the leaves barely trembling is the cheapest tipburn insurance there is. Acceptance test: stand at the far end, hold a hand at canopy height, feel for the breeze. Tomorrow's film is the first audit.

The float valve keeps its own diary

The top-up auto-detector logged two entries today: a −25 µS step at 09:21, about four litres, and a −16 µS step at 18:14, another two and a half. Add the 3 a.m. signature from two nights ago and the picture is complete: the valve quietly replaces six-odd litres of transpiration a day on its own schedule, morning, evening and small hours, the same silent mechanism that stands accused in the short-dose case. The detector can now spot every refill from conductivity alone; what it can't do is measure one. The pulse water meter stays on order, and every diary entry the valve writes is another line in the argument for it.

Honesty section: that called shot is still in the air

Yesterday I wrote that the pH drift was "already turning". It turned, wobbled, and kept sliding: the morning rise to 5.87 didn't hold, and the day closed at 5.84 on one probe, 5.81 on the other. Before anyone scores that a miss, the window isn't shut. The heaviest fertiliser day of the week was yesterday (500 ml a side), so the 24–48 hour ammonium clock runs to tomorrow afternoon; and the slide is decelerating hard, from −0.07/day overnight to −0.02 today, which is exactly what a finite fuel burning out looks like. The absolute level, for the record, is textbook. 5.8 is where lettuce wants to live. What's on trial is only whether the trend stops on schedule.

So, in public, the tripwires: if pH breaks 5.70, or the slide steepens instead of flattening, the mechanism goes back on trial and I'll write up whatever the re-investigation finds. Otherwise tomorrow's entry gets to say "landed" and mean it.

Postscript, same evening: the deceleration was fake

A few hours after this entry went up, a closer read of the minute-level curves broke the paragraph above. Both of today's upward pH moves, the morning rise I was ready to credit to the crop and the evening rebound, align to the minute with the float valve's two top-ups. Both probes step together within a sample or two of the EC drop, sharply, and then hold. Two independent electrodes don't hallucinate the same step at the same minute twice in one day: that's real chemistry. The top-up water carries alkalinity.

Run it backwards through the acid calibration's buffer capacity and each refill delivered roughly 0.6–1 meq/L of carbonate, which pure rain doesn't have. Somewhere in storage this water picks up lime: the tank, the roof, mortar in between. A titration of a tank sample goes on the list. (Silver lining: lime travels as calcium bicarbonate, and on an all-rainwater site a little free calcium is a gift, see the tipburn section above.)

Strip those two bumps out and the underlying slide is still running about −0.09/day, same as last night. Not decelerating. The "finite fuel burning out" evidence is withdrawn; the mechanism window (tomorrow afternoon) and the 5.70 tripwire stand unchanged. And the model gains a standing term: every litre the crop transpires comes back, on the valve's own schedule, as a small dose of alkali. The reservoir ledger just grew a column nobody ordered.

Next: the fan's first night versus the condensation, the pH verdict, a tank-water titration, and the water meter's arrival.

2026-08-27 · Auckland, New Zealand

The greenhouse closes the loop

For its first week on site, the controller was allowed to watch but not touch: instrumentation only, every decision made by a human with a jug. Two entries ago we promised a vent actuator. Today it went in, and by mid-afternoon the controller had made, and journaled, its first autonomous decision.

The actuator, and why "off" means "closed"

The hardware is a 24 V linear actuator on the end-wall vent. It is the spare arm from a double-swing gate opener kit that only ever had one gate to open, cost to this project: zero. It sits behind a small driver board that accepts three exclusive stage inputs from the relay expansion module: assert one output and the window drives to that opening and holds; assert none and it closes. That mapping was chosen for what it does when things go wrong. The relay module carries a 3-second safe state. Lose the controller, lose the backplane, lose power to the logic, and the outputs clear, so the window closes itself. The screw drive self-locks with no holding power, which doubles as a free night latch. Fail-safe by wiring, before a single line of control code.

A thermostat with a ladder, not a switch

The control law is a pure temperature ladder on greenhouse air: open one stage after 25 °C holds for three minutes; sit at each stage for ten minutes and judge the cooling slope. If opening didn't actually cool, climb a stage; jump straight to stage two past 30 °C; step back down through 22, close fully at 20. Sensor lost for ten minutes? Close and raise a fault. Deliberately absent: a clock. Night close falls out of the physics as the air cools, which means no timezone code, no daylight-saving edge case, nothing to misconfigure.

Every stage change writes an event into the on-board journal with the temperature and the reason, which means every decision shows up as a flag on the public dashboard, next to the curves that caused it. The called-shots policy now applies to the machine itself.

First decision

The firmware went out over signed dual-bank OTA in the afternoon, site running, nobody driving to the greenhouse. The reboot closed the window (fail-safe doing its job), and nine minutes later the journal read:

The nine minutes are the interesting part. Air sat at 25.3 °C right after boot, above the threshold, and the controller refused to act, because the reading wobbled below 25 before the three-minute hold completed. It opened only when the heat was sustained and real. That hold was designed on paper to stop hunting; watching it decline a marginal trigger on live data was the first sign the tuning is roughly right.

Roughly. Honesty section: through the slow natural cooldown of late afternoon, the ladder climbed all the way to stage three. The slope criterion can't yet tell "opening isn't working" from "evening is coming", so it kept escalating at a time of day when more airflow was harmless but pointless. The windows still closed on schedule as the air fell through 20 °C. Next tune: escalation will also require the air to still be hot, not merely cooling slowly. One constant, one line.

The dose that came up short, and what it turned out to measure

Morning dosing had its own detective story, still open. First dose of the day: predicted +70 µS, curve stopped at +44 and never grew a tail. A second, identical dose an hour later hit +66, so the calibration constant is fine, and the first dose genuinely lost something. Two suspects remain. One is the float valve topping up on its own schedule at exactly the wrong moment: the same data sweep found its fingerprint elsewhere, a clean −15 µS step at 3 a.m., overnight transpiration being quietly topped back up, and roughly four litres mid-dose would explain the gap to the litre. But doses go in at the greenhouse return line, nowhere near the barrel, so nothing we did could have tripped it; if it opened, it opened on its own clock, and that makes the case circumstantial. The other suspect is simply a weak pour. The verdict waits for hardware:

• On order. A pulse water meter on the top-up line, into a counter input. Top-ups become measured events instead of suspects argued from conductivity. This valve has already ruined one calibration by stirring and photobombed a power-cut recovery; it doesn't get to be convicted, or cleared, on vibes.

Another called shot, already landing

Yesterday was a heavy fertiliser day, and overnight the pH slid steadily, the fertiliser's ammonium and phosphate acidity outrunning the crop's usual alkaline drift from nitrate uptake. This morning we posted the mechanism and a prediction on the public chart: the drift reverses within 24–48 hours as the ammonium is consumed. By afternoon it was already turning. Zero-buffer rainwater makes the chemistry fast, but it also makes it legible.

Root verdict, and a tenant who likes it hot

A week after the collar-and-cover retrofit, the channels are also telling a quieter story: the film is running clear, and there's no algae where the light used to leak in. A few dollars of pool noodle continue to outperform their price class.

Next: the stilling well, the water meter, fan stages on the same ladder, and EC's arrival at 1.4.

2026-08-26 · Auckland, New Zealand

Called shots, public notes, and strawberries in the spare holes

Dosing day. Five nutrient doses between breakfast and dinner, EC walked from 0.82 up to 1.02 mS/cm on its way to a new 1.4 target, and every single dose was predicted before it was poured. The +14 µS per 50 ml slope from last week's calibration has now held from 50 ml doses all the way to 280 ml, five for five, most landing within a couple of µS of the forecast.

The event journal is now public

Until today the operator's notes on what was dosed, when and why stayed in the private view, and a visitor watching the public dashboard saw EC steps appear out of nowhere. That's fixed: the on-board event journal now shows on the public curves, flags and all. When we pour, you see the note; when the float valve tops up, the auto-detector writes its own.

Which enables a new sport. The afternoon doses were logged with the prediction in the note, before the dose hit the water: "baseline EC 925, predict +28 to ~953". Two minutes later the curve stopped at 952. The 280 ml evening dose was called at ~1030 and landed at 1024, with the gap expected to close overnight as settled solids dissolve out of the dead zone (the suspension-type concentrate drops a little solid ballast; it re-dissolves slowly once diluted, and we've learned to treat the few-µS creep after each plateau as part of the dose, not a mystery). If you want to audit us, watch the next flag: the number is written down before the curve moves.

Acid respects no calibration, because rainwater has no buffer

The site runs entirely on rainwater, which means zero carbonate alkalinity: nothing in the water pushes back against acid. Back at pH 6.8, 50 ml of dilute acid moved the reservoir −0.3. Today at pH 6.3, 30 ml did −0.33, the same result for barely half the dose. Dose response roughly doubles as pH falls, because what little buffering exists (mostly the phosphate in the nutrients) thins out on the way down. The working rule is now: whatever the calculation says, pour half, wait ten minutes, look at the curve. The calculation said 80–90 ml to reach 5.8; the halved first pour alone landed us at 5.95.

• Bookkeeping detail. Acid moves EC too. The hydrogen ions get absorbed by the phosphate system, but the chloride stays and conducts, worth about +10 µS for a 30 ml dose. Dose nutrients and acid together and your slope audit needs that correction; we found out by wondering why one step ran 5 µS hot.

Strawberries in the spare holes

The channels have more holes than the salad crop needs, and it's bare-root strawberry season here. So four plants came out of the garden bed, got their roots washed completely clean of soil, the one non-negotiable, since soil in a shared reservoir is both a clog and a pathogen inoculum. They went into the bottom channel with the usual foam collars, crowns kept high and dry above the film.

It's a transplant gamble, and we're treating it as one: two weeks of watching for the soil-to-water root conversion, with the greens upstream as the healthy control group. If it works, spring flowers meet a monitored reservoir. If it doesn't, it'll be in these notes too.

Next: the pH night-drift check decides the second acid dose, a vent actuator with a cumulative-exposure setpoint, and strawberry watch, week one.

2026-08-25 · Auckland, New Zealand

Week one: dose curves, a dead zone, and a few dollars of pool noodle

The first entry ended with an open question and 72 freshly planted seedlings. One week in, the question is answered, the reservoir turned out to have a secret, the lettuce held a vote on temperature, and the cheapest part on the whole site fixed a real problem. In order:

The open question, answered

Last time: overnight EC declined in step with air temperature, more than probe temperature compensation should allow. Instrument drift, or something real? The test we were waiting for was the morning warm-up. Drift retraces, biology doesn't.

The answer: air climbed from 11 °C back to 19 °C and EC did not retrace. The decline accelerated, from about −0.5 µS/cm per hour in the middle of the night to −2.5 once light hit the canopy. That's not a coefficient problem; that's plants drinking, on a light schedule. The probes were telling the truth the whole time. No settings were harmed in the resolution of this mystery.

Calibrating the nutrient dose the hard way

With acid dosing already quantified, we did the same for nutrients. The end result: +14 µS/cm per 50 ml of each part (A and B, pre-diluted 1:10, in a 165 L reservoir), and recent doses land within a couple of µS of prediction.

The first attempt taught us more than the number did. Dose poured on the surface: EC spiked for nine minutes, then… vanished. Diluted concentrate is denser than water. It slid straight past the pump inlet (20 cm off the barrel floor) into the still water below it. About a quarter of the reservoir turns out to be a circulation dead zone. Mass balance eventually closed: the "lost" dose leaked back out of the dead zone as a slow +10 µS creep over the whole afternoon. And the rescue attempt, stirring the barrel, sloshed the float valve into topping up ~8 L of fresh water, which the dashboard dutifully flagged and which ruined that calibration run entirely.

• New dosing rule. Pre-dilute, pour slowly, directly above the pump inlet. Three doses since: clean ten-minute steps, no drama.
• Free diagnostic. A dose that "disappears" is a stratification probe: it just measured our dead zone without any extra instrumentation.

Heat, votes, and one-fifth of a door

Midday hit 33.5 °C inside the hoop house. Opening the door one-fifth of the way broke the peak in nine minutes, roughly 2 °C per ten minutes, and held the afternoon in the mid-twenties. Meanwhile the crop voted on what heat means: bok choy shrugged, spinach complained, coriander and lettuce wilted. The log adds a nuance the thermometer alone wouldn't: leaf damage correlates with cumulative hours above 25 °C (2.6 h that day), not with the instantaneous peak. That single observation just promoted ventilation to the top of the automation queue, and gave us the metric the vent controller should actually regulate.

Mechanical day: a few dollars of pool noodle

The channels came with 70 mm planting holes, big enough that sparse young canopies let direct sun down onto the root zone. NFT film has zero thermal mass, so a lit hole is a localised root heater, plus an open invitation to algae. The fix came from the pool section of the hardware store: noodle slices, about 30 mm thick, split as collars around each stem; flat covers over every unplanted hole. Light leak closed, seedlings snug, total spend in single digits.

The week on one screen

The public read-only dashboard is still live. watch the greenhouse here.

Next: seedling sponges and a no-transplant second crop, a stilling well for that float valve, and a vent actuator with a cumulative-exposure setpoint.

2026-08-22 · Auckland, New Zealand

First 72 plants in the water

Our controller platform grew up on the bench. This week it moved outdoors: an NFT hydroponic test site in a hoop house: four channels, a half-buried reservoir for thermal mass, and an Industry 757 with three expansion modules running the instrumentation. On day three we planted the first 72 heads of lettuce, coriander and bok choy.

What 48 hours of data looks like

This isn't a screenshot-only story. The dashboard has a public read-only view, so you can watch the greenhouse live, right now.

A dashboard earns its keep when the curves start telling you things you didn't ask. Some of what this one told us in its first two days:

• Acid dosing, quantified. Bringing the reservoir down from pH 6.8, each 50 ml dose of dilute acid stepped pH down by about 0.3 and took ~30 minutes to stabilise, both probes agreeing within a few hundredths. That's a dosing calibration you get for free from the log.
• A top-up we didn't log. The system did. One afternoon both EC channels stepped down ~57 µS/cm within minutes, water temperature dipped, pH nudged up. That signature is a float valve letting cold fresh water into the reservoir. The cloud now detects this pattern automatically and writes an event into the device's journal, so unattended dilutions never silently skew the nutrient record.
• Thermal mass works. Overnight the air in the hoop house swung from 27 °C down to 10 °C; the half-buried 165 L reservoir only drifted from 21 °C to 15 °C. Free stability, courtesy of a shovel.
• An open question. EC tracks air temperature inversely overnight in a way that probe temperature compensation alone doesn't explain. We're watching whether it retraces on warming (instrument drift) or not (real nutrient change) before touching any coefficient. The data will settle it.

The part where it broke

More notes as the crop, and the platform, grows.