I Used a Grok Bot and Jev to Put My Mushroom Chambers on Autopilot

Part of: The OpenShrooly Journey

How I used Shroominator, a Grok Bot, plus OpenShrooly firmware and TypeSafe's Jev model to revive dead Shrooly growers and run them on autopilot.

As an Amazon Associate I earn from qualifying purchases.

I used a Grok Bot named Shroominator, Graham Stewart’s OpenShrooly firmware, and a decision model called Jev to bring my mushroom grow chambers back from a dead vendor cloud and put them on autopilot. The hardware was never the problem. The app was. The chambers now run locally on open firmware, and shroomlabs.io can steer them toward a grow profile without my laptop staying awake.

This is the long version of that build: what broke, what we actually flashed, what the AI did versus what I did, the dead ends, and how the hardware and the models fit together. It follows episode 1 of the OpenShrooly journey, where I first plugged a Shrooly into the laptop and found the ESP32-S3 inside.

A supplies section near the end has Amazon affiliate links for North Spore grow bags, gourmet grow kits, and substrate. As an Amazon Associate I earn from qualifying purchases. I do not list live prices.

What actually happened to these mushroom machines?

Shrooly is a compact, sensor-driven mushroom grow chamber. It has a humidifier, a fan, lights, and a small screen, and it was sold as an app-guided box. The hardware is real. The catch is the same catch a lot of smart appliances have: a new grow, on stock software, wanted the company’s app and cloud.

I could not find a public shutdown notice from the company, and shrooly.com still loads. What I can stand behind is the public record we collected on What happened to Shrooly. The last customer update on their index is dated July 31, 2025. From August 2025, owners on r/shrooly started reporting that the app showed a no-internet error at sign-in, even on working Wi-Fi, and that support went quiet. Graham Stewart, who started OpenShrooly, wrote that as of September 2025 the company appeared to have gone out of business. I am not going to say more than that, because I cannot confirm a bankruptcy filing or a formal closure.

Owners still had a box on the counter that could hold humidity and air. They just could not start a guided grow the way the product was sold. That is the situation I was in, and it is the situation Shroom Labs is built for: reuse the hardware you already own.

Who is Shroominator, and what did I ask it to do?

Shroominator is a Grok Bot I set up as the assistant on this project. I did not ask it for mushroom recipes and walk away. I pointed it at the existing open firmware and told it we were going to build on it.

My first instruction was blunt. I sent it openshrooly.com and said: fork the repo. “We’re going to improve it beyond reason. Like I want to save mushroom profiles, manage multiple shrooly’s, handle a community db for this. They got basic control, I want to build the community.”

That is still the brief. Graham already had working firmware and a local web UI. I wanted saved profiles, more than one chamber, and a community layer on top, without turning the box back into something that dies when a vendor disappears.

The design constraints came in the same sitting. “Creating a world class community app should be simple and cheap with good firmware.” The site should be a free service with small paid recipes and affiliate links for supplies, not a pile of infrastructure. The firmware had to keep working with no hub and no internet. That last rule is the one I will not bend. If Shroom Labs vanished tomorrow, the chamber should still grow mushrooms from its own web page.

Shroominator forked Graham’s repo to themsquared/openshrooly, kept the MIT license, and started building the profiles, the site, and the control path around that firmware. I stayed in the loop on every flash, every product decision, and every time something was about to be written to a live chamber. The bot did the repo work, the installs, the backups, the serial work, and a lot of the debugging. I plugged the cables in, made the calls, and told it when the screen looked wrong.

What did we find when we plugged the Shrooly into the laptop?

I have already written the first hour of this as I Plugged a Mushroom Grower Into My Laptop. The short version is worth repeating, because this is where a lot of people get stuck.

I told Shroominator the Shrooly was on the machine over USB, as TTY and JTAG. The Mac saw an Espressif “USB JTAG serial debug unit.” That is the ESP32’s own USB port, not a separate adapter. We installed esptool, the Espressif flashing tool, in its own Python environment so it was not loose on the system. The first flash_id call failed with “No serial data received,” even after a forced reset, and nothing else was holding the port.

The fix was not a special strap or a driver hunt. I unplugged the cable and plugged it back in. “Oh it works. lol Replugged yo.” Then I pointed the bot at the OpenShrooly manual install docs. If a replug is not enough on your unit, those docs are the next place to go, including holding the BOOT control while you reconnect.

Once the chip answered, esptool reported an ESP32-S3 with 16MB of flash and 2MB of PSRAM, plus Wi-Fi and Bluetooth LE. That is a serious little computer for a kitchen box. The chip also reports a MAC address. I am not posting mine, and you should not post yours.

What was on the flash when we backed it up?

The next step is the one you should never skip. We read the full 16MB flash to a backup file before anything was written. esptool can do that with read_flash, and Graham’s manual install guide starts there for a reason: that file is your way back.

The surprise was that this unit was not on stock Shrooly firmware. It was already running OpenShrooly v1.0.2, built on ESPHome 2026.7.3. So the backup is a restore point for that OpenShrooly build, not a copy of the original vendor image. If you still have a stock chamber and you might want the official software back, back it up before you install anything else. The browser installer on the Shroom Labs install page does not save the original for you.

That matters more than it sounds. “Flash the open firmware” is the headline. “Know exactly what you are about to overwrite” is the work.

What firmware runs the chamber now?

OpenShrooly is Graham Stewart’s project. It replaces the stock software so the chamber joins your Wi-Fi, serves its own web page, and can talk to Home Assistant. It is built on ESPHome, which is the right tool for this job: you describe the sensors and actuators, you get a control loop that runs on the device, and you can still extend it.

Shroom Labs builds on that firmware rather than replacing it. Releases on shroomlabs.io/install are signed, and the browser checks the signature before anything is sent to the chamber. You install from Chrome or Edge with a USB-C data cable in about five minutes. After install, you can set Wi-Fi from the same page. If the screen does not change, the recover step is simple and a little annoying: unplug both USB and power, wait ten seconds, and plug in power only.

Once it is running, the chamber is a local device first:

  • Its own web page sets temperature, humidity, fresh air, and light.
  • It keeps working with no account and no cloud.
  • Later builds can take signed updates over Wi-Fi, and they keep the current version if an update looks wrong.
  • From firmware 1.0.6-sl.1, you can press button 4 on the chamber, choose “Link this device,” and scan a QR code to hang it on a free shroomlabs.io account if you want the phone dashboard.

I also have a Lykyn Smart Mushroom Grow Box in the same fleet. That one is a different machine: an ESP32-C3 with 4MB of flash, an SHT3x temperature and humidity sensor, inlet and outlet fans, a humidifier, and an LED strip. We took a verified backup of the stock image, then flashed our own firmware from themsquared/lykyn-firmware. I am calling that out because “open firmware for a Shrooly” and “a second brand of chamber on the same control plane” are two different claims. The shared idea is the same. The box should speak a common status API, take a grow profile, and keep working if the site is down.

Flash budget is tight on both, and tighter on the Shrooly once you start adding a richer on-device page, a cloud link, and Autopilot. We had builds that took the Shrooly past 97 percent of its OTA slot. When that happens, you stop adding features and you start cutting, because a firmware update that does not fit is not an update.

How did Autopilot go from my laptop to the site?

The original architecture was a local hub, the kind of thing you would run on a Raspberry Pi, talking to every chamber on the LAN and syncing profiles to a community site. That is still a good design, and it is still on the journey tracker. It is not what ended up steering my chambers day to day.

The first working Autopilot path used my MacBook as a bridge on the same network. The site could plan a change, but a process on the laptop had to reach the chamber and apply it. That works until you close the lid, leave the house, or the laptop sleeps. It also makes “the cloud is optional” feel fake, because the steering still depended on a computer I had to keep around.

The next step was to make Autopilot a website feature. The chamber already had a way to check in, pick up a queued command, and acknowledge it. We used that inbox. shroomlabs.io plans the change within the same limits a person would get on the device page, puts it in the queue, and the chamber applies it. The first time the site ran that loop on its own, it moved a chamber’s temperature from 21 to 20 °C at 12:05 PM Pacific, and the chamber confirmed it had applied. My laptop was no longer controlling anything.

We had to earn that. Early Autopilot could only move some of the knobs. I said the quiet part out loud: half the knobs is not really Autopilot. The firmware had to let the site set fresh air timing, the light schedule and mix, and the grow stage, not just temperature and humidity. Autopilot now checks each stage’s limits on the server before it changes anything.

There were also boring bugs that would have made a pretty demo and a bad grow. After a restart, one firmware path never started sending regular readings to the site. Autopilot cannot steer blind, so we held the cutover until that was fixed. After you first link a chamber, it used to wait a full 15 minutes before the first check-in, which made a successful link look like an offline device. We changed that to about 30 seconds and fixed the wording on the page. If a chamber goes offline, Autopilot pauses itself and does not turn back on by itself. That is deliberate. I would rather start it again than have it catch up with a stale command.

What is Jev, and why did we put it on Autopilot?

This is the part people asked about, so I want to be precise.

Autopilot did not start as an AI loop. It started as plain code. It reads the chamber’s recent temperature, humidity, light, fan, and water, compares them to the current stage targets, and nudges the setpoints toward those targets inside hard limits. That costs nothing to run, and it is rigid on purpose.

I pointed Shroominator at Jev and said, “If we need to use Jev for autopilot, that may be the cheapest option for us.” The bot had not heard of it yet. I sent the launch post: Introducing System One Models and Jev, published September 15, 2026 by TypeSafe AI.

Jev is not a chatbot. TypeSafe calls it a System One model: unstructured state in, typed decisions out, with a confidence score on every answer, and no string generation. Their public price at launch was about four cents per million input tokens, with output too cheap to meter. The idea is that you can put a frontier-level decision inside ordinary software, the way you would call a function, instead of waiting on a long text completion and then parsing it.

My read was the same as the job we actually had. “SystemOne model that makes decisions. Simple loops, simple decisions. This isn’t rocket science, it’s nudging.” We could “feed timeseries for all feeds (temp, light, humidity, fan, etc) to get decisions.”

That is what we built. Jev sees the recent readings and the stage targets. It can recommend a small change, such as whether humidity is trending low for this stage and whether to bump the fan. It cannot blow past the safety limits, because those stay in code. It is capped at one call every 30 minutes per chamber. If it is slow, errors out, or is not confident, Autopilot falls back to the rules. In a replay of 12 hours of my main chamber, it matched the rules on humidity and fan every time, mostly wanted to hold light where the rules had dimmed slightly, and wanted to go lower on temperature when the chamber was reading 20 to 22 °C against a 17 °C target. It still had to move one small step at a time.

Once that look-back seemed sane, we turned Jev on. Each decision costs about a hundredth of a cent. At that cap, it works out to roughly 16 cents a month per chamber. The Grow Coach feed labels whether Jev or the rules made the call, including a confidence like “Jev, 82% sure.”

I had already spent time asking whether Jev’s confidence score is worth routing on, in a different domain. That work is in I Benchmarked Jev on Agent Tool-Call Risk and Is Jev Actually Calibrated?. Those posts are about classifying tool-call risk, not about humidity control. I am not going to pretend a 91.7 percent score on one benchmark answers this grow loop. The reason I was willing to put Jev here is narrower: the output is a typed nudge, the code still owns the limits, and a miss falls back to rules I can read.

How does the hardware and the AI actually fit together?

People hear “AI mushroom farm” and picture a model running the fans directly. That is not this system, and I would not want it to be.

The loop has four layers, and each one has a job it is allowed to do.

The hardware is still a box. On a Shrooly, that means an ESP32-S3, 16MB of flash, a humidity and temperature sensor, a humidifier, a fan, and lights. On the Lykyn, it means an ESP32-C3, an SHT3x on the I2C pins, PWM fans, a simple on/off humidifier, and an LED ring. The physics do not change because a model is involved. If the humidifier is off and the fan is stuck, no amount of Autopilot helps.

The firmware is the real-time loop. ESPHome and the OpenShrooly (or Lykyn) firmware read the sensor, apply the current setpoints, run the fresh-air cycle, and keep the on-device page working. This layer has to be safe even when every network path is gone. It is also the layer that talks USB for backup and flash, through esptool.

The site is the optional brain with a longer memory. shroomlabs.io holds grow profiles, stage recipes, the Coach view, and the Autopilot queue. A profile is not a vibe. It is a set of stage targets for temperature, humidity, light, and fresh air, plus a start date, for a gourmet variety such as lion’s mane, oyster, or enoki. When I said I had no idea what was growing, Autopilot had already put a chamber on lion’s mane fruiting settings and the page was leading with the word “Fruiting.” That was a product bug, not a model bug. The chamber page now leads with the mushroom, a photo, and the stage underneath.

Jev sits beside the rules, not above the firmware. It sees a window of telemetry and the targets, and it proposes a small correction. The site still has to accept that correction, clamp it, and send it. The chamber still has to apply it and acknowledge it. If the command is late, the site should drop it rather than apply yesterday’s weather to this afternoon’s grow.

The shared language across chambers is percent, not a raw hardware unit. 100 percent light means that chamber’s brightest output, which is not the same number of lux on a Shrooly and a Lykyn. Coach and the profiles speak percent. Each firmware turns that into its own pins. We had to learn that the hard way, including a stretch where one chamber’s on-device screen still showed lux while the site had moved to percent.

As of mid-November 2026, that loop is running on three chambers: two Shroolys and the Lykyn. The gourmet grows on them have included lion’s mane, enoki, and black oyster. I still do the grower’s job. I load the block, I look at the pins, I decide when a flush is done. The machines keep the climate in range while I am at work.

What went wrong, and what did we change because of it?

A clean narrative would skip this section. The useful one cannot.

The first connection failed until a physical replug. That is in episode 1, and it is still the first thing I tell people who think they need a special cable adapter. You may need a data-capable USB-C cable, though. A charge-only cable will fool you.

The first backup was not a stock image. If we had treated it like one, a “restore to factory” story would have been wrong.

Autopilot on a laptop is a prototype, not a product. Closing the lid should not pause a grow.

A chamber that does not report readings after a reboot is worse than a chamber that is slightly off target, because the steering system will invent confidence it should not have. We did not hand Autopilot to the site until that was fixed.

A “Live” badge that means “the web page has a socket” is not the same as “the chamber checked in.” Wording bugs like that waste hours of human trust.

Stage names have to match what a given firmware will actually accept. One chamber used “Colonizing” and another wanted “Colonization.” If you send the wrong word, the card on the site can say one stage while the box runs another. That is not a small typo when the recipe for colonization and fruiting are different.

Commands cannot sit in a queue forever. A change that made sense 20 minutes ago can be the wrong change now. We added expiry so late commands get dropped instead of landing late.

Flash space is a product constraint, not an implementation detail. If the next feature does not fit next to a safe OTA slot, the feature waits.

And “the deploy finished” is not the same as “the live page is the new page.” More than once, a ship looked done until we loaded the actual device page and found the old layout, a missing graph, or a service worker holding a stale copy. The rule I now use is the unromantic one: nothing that touches Coach or the devices is done until it has been checked on the live chamber, and the path between Coach and the device needs tests that act like the real firmware, including late commands and dropped connections.

None of that is glamorous. It is the difference between a weekend demo and a box you will let run overnight.

What can you flash, and what can you buy, if you want to try this?

If you already have a Shrooly, start with the software, not a new box.

You do not need my site to grow. You do need a data-capable USB-C cable, and you should write down your current temperature and humidity settings before you flash.

If you want something to grow in the chamber, official Shrooly refill pods are the awkward part. I could not verify a current Amazon listing for those pods, so I am not going to invent a link. What I could confirm are live listings for North Spore grow bags, gourmet grow kits, and hardwood substrate.

The product I would start with, if you are packing your own grows, is North Spore’s ShroomTek all-in-one grow bags. The listing is a 4-pack of 3 lb bags. Each bag comes with sterilized substrate, a filter patch, and a self-healing injection port, and you inoculate it yourself. These are not official Shrooly pods, and they are not an empty bag you fill from scratch.

North Spore ShroomTek all-in-one mushroom grow bags, 3 lb each, 4-pack, on Amazon

A window-sill spray kit is not the same thing as a Shrooly pod. A colonized block is closer to what you would actually run in a chamber, and a sterilized substrate bag is for when you are adding your own spawn. I have not run these specific Amazon products inside my chambers. They are starting points I could verify as real product pages.

North Spore Organic Lion's Mane Spray & Grow Kit (4 lb) on Amazon Back to the Roots Organic Mushroom Grow Kit 3-Pack on Amazon North Spore Mastr Mix sterilized hardwood substrate (5 lb) on Amazon North Spore organic sterilized grain spawn bag (3 lb) on Amazon

If you are shopping for the holidays, a North Spore grow bag or a gourmet kit also makes a good gift for the curious maker in your life. Treat it as a project, not as something that fruits itself while it sits under the tree.

This post contains affiliate links. If you buy through one, this site earns a commission at no extra cost to you. As an Amazon Associate I earn from qualifying purchases. I do not list live prices, because those move.

What did I not verify?

I want this part in the open, the same way I try to write the rest of this site.

I have not independently confirmed that the Shrooly company is legally out of business. I am repeating what public pages and owner reports show, and I am leaving the rest unmarked.

I have not verified a current official Shrooly pod listing on Amazon.

I have not published a Jev accuracy study on this grow-control task. The calibration numbers in my earlier Jev posts are about tool-call risk, not about a fruiting chamber.

I am not calling a harvest complete on the current grows. The chambers are running, and the climate loop is the part I am writing about.

The Raspberry Pi hub from the original plan is not what runs Autopilot today. The production path is the chamber’s own firmware, plus an optional link to shroomlabs.io.

Some of the Coach-to-device behavior is still being tightened, including end-to-end tests that should fail a ship if the site and the chamber disagree on stage or apply a stale command. I would rather tell you that is ongoing than pretend the last bug has already been found.

Frequently asked questions

What happened to Shrooly, and can the hardware still run?

The company that made Shrooly has not posted a public shutdown notice, and its website still loads, but its last customer update was July 31, 2025. From August 2025 on, many owners reported that the app would not sign in and that support went quiet. The chamber itself is still a sensor-driven box with a humidifier, fan, lights, and an ESP32. Open replacement firmware can run that hardware on your own Wi-Fi, with no Shrooly app.

What is OpenShrooly, and who made it?

OpenShrooly is open source replacement firmware for Shrooly chambers, created by Graham Stewart and released under the MIT license. It is built on ESPHome, gives the chamber a local web page, and works with Home Assistant. Shroom Labs, the project I run at shroomlabs.io, builds on his work with grow profiles, a browser installer, and an optional dashboard. We are not affiliated with the company that made the hardware.

What is Jev, and why use it on a mushroom chamber?

Jev is TypeSafe AI’s first System One model, announced on September 15, 2026. It is not a chat model. You give it unstructured state and it returns typed decisions with calibrated confidence, fast enough to sit inside a control loop. Autopilot on my chambers already had plain rules that nudge temperature, humidity, light, and fan toward each grow stage’s targets. Jev adds judgment on top of those rules, for example whether humidity is trending low and whether to bump the fan. Hard safety limits stay in code. If Jev is slow, errors out, or is not confident, the rules take over.

Does the chamber still work if the cloud or the laptop is off?

Yes. A hard rule for this project is that the firmware keeps working fully offline. The chamber’s own web page can set temperature, humidity, fresh air, and light with no account and no internet. Autopilot on shroomlabs.io is optional. It used to depend on a laptop on the same network acting as a bridge. After a firmware update, the site can queue a change on the chamber’s inbox itself, so the laptop is no longer required for steering.

What firmware and tools do I need to reuse a Shrooly?

You need a computer with Chrome or Edge, a USB-C data cable (not a charge-only cable), and about five minutes. Back up the flash first if you might want the original software back, because the browser installer does not do that for you. The official OpenShrooly manual uses esptool to read the full 16MB. You can then install a signed OpenShrooly build from the Shroom Labs install page, or follow Graham Stewart’s manual install guide. The chip inside a Shrooly is an ESP32-S3 with 16MB of flash and 2MB of PSRAM.

Did you find official Shrooly pods on Amazon?

No. I could not verify a current Amazon listing for official Shrooly refill pods, so this post does not link any. The North Spore ShroomTek grow bags, grow kits, and substrate linked below are live listings I could confirm, and they are a starting point for gourmet grows, not a claim that they are drop-in Shrooly pods. I have not run those specific Amazon products inside my chambers.

The work continues in public on the OpenShrooly journey hub, and the chambers keep running at shroomlabs.io. Credit for the firmware that made any of this possible still goes first to Graham Stewart.

Frequently asked questions

What happened to Shrooly, and can the hardware still run?

The company that made Shrooly has not posted a public shutdown notice, and its website still loads, but its last customer update was July 31, 2025. From August 2025 on, many owners reported that the app would not sign in and that support went quiet. The chamber itself is still a sensor-driven box with a humidifier, fan, lights, and an ESP32. Open replacement firmware can run that hardware on your own Wi-Fi, with no Shrooly app.

What is OpenShrooly, and who made it?

OpenShrooly is open source replacement firmware for Shrooly chambers, created by Graham Stewart and released under the MIT license. It is built on ESPHome, gives the chamber a local web page, and works with Home Assistant. Shroom Labs, the project I run at shroomlabs.io, builds on his work with grow profiles, a browser installer, and an optional dashboard. We are not affiliated with the company that made the hardware.

What is Jev, and why use it on a mushroom chamber?

Jev is TypeSafe AI’s first System One model, announced on September 15, 2026. It is not a chat model. You give it unstructured state and it returns typed decisions with calibrated confidence, fast enough to sit inside a control loop. Autopilot on my chambers already had plain rules that nudge temperature, humidity, light, and fan toward each grow stage’s targets. Jev adds judgment on top of those rules, for example whether humidity is trending low and whether to bump the fan. Hard safety limits stay in code. If Jev is slow, errors out, or is not confident, the rules take over.

Does the chamber still work if the cloud or the laptop is off?

Yes. A hard rule for this project is that the firmware keeps working fully offline. The chamber’s own web page can set temperature, humidity, fresh air, and light with no account and no internet. Autopilot on shroomlabs.io is optional. It used to depend on a laptop on the same network acting as a bridge. After a firmware update, the site can queue a change on the chamber’s inbox itself, so the laptop is no longer required for steering.

What firmware and tools do I need to reuse a Shrooly?

You need a computer with Chrome or Edge, a USB-C data cable (not a charge-only cable), and about five minutes. Back up the flash first if you might want the original software back, because the browser installer does not do that for you. The official OpenShrooly manual uses esptool to read the full 16MB. You can then install a signed OpenShrooly build from the Shroom Labs install page, or follow Graham Stewart’s manual install guide. The chip inside a Shrooly is an ESP32-S3 with 16MB of flash and 2MB of PSRAM.

Did you find official Shrooly pods on Amazon?

No. I could not verify a current Amazon listing for official Shrooly refill pods, so this post does not link any. The North Spore ShroomTek grow bags, grow kits, and substrate linked below are live listings I could confirm, and they are a starting point for gourmet grows, not a claim that they are drop-in Shrooly pods. I have not run those specific Amazon products inside my chambers.

Disagree or have a war story? Reply on X