CleverCoffee for Rancilio Silvia: current v4 planning guide
Use this page to understand the current CleverCoffee release, choose a current ESP32 hardware path, identify the Silvia before opening it, and know which source owns each decision. It is not a mains-wiring walkthrough.
What is CleverCoffee today?
CleverCoffee is the current project name in the rancilio-pid GitHub organization. The current releases page lists CleverCoffee v4.0.0 as the latest release when checked on 2026-09-20.
The project has a long ranciliopid / ESP8266 history, but that history should not be used as the default new-build path. The ESP8266 release line now sits on a separate legacy branch: the project labels v3.3.0-esp8266 as the last major release for ESP8266 and says there will be no further feature development on that platform.
What is the current hardware baseline?
The current CleverCoffee hardware repository is built around the ESP32 DevKitC v4. It contains minimal, development and experimental SMD PCB variants rather than one timeless “official board” that HBM can freeze forever.
| Hardware source | Current project note | What HBM does with it |
|---|---|---|
| Minimal PCB | ESP32 DevKitC v4 based; smaller footprint. | Use the current repository/revision, not an old screenshot or BOM. |
| Development PCB | Adds extra feature support; project says development boards remain work in progress. | Do not hard-code pin mapping from an old article. |
| Experimental SMD variants | Additional/alternative headers and layouts. | Keep them separate from the default planning path unless the current project docs say otherwise. |
The hardware repository explicitly warns that some pin mappings can change and tells builders to check the project community for the latest minimal-PCB revision. It also says the project does not want mains-voltage components integrated into these PCB designs for regulatory and safety reasons.
How is current v4 firmware installed and configured?
The current v4 release line supports a browser-based CleverCoffee Web Flasher for ESP32. The v4 beta/release path replaced older “edit source and compile everything” assumptions with web flashing and a JSON-based configuration system.
The current configuration reference documents hardware and software settings in the running firmware, including:
- OLED display support including SSD1306 and SH1106 controller types.
- Configurable relay trigger types for heater, valve and pump outputs.
- Temperature-sensor choices including TSIC 306 and DS18B20.
- Optional pressure sensor.
- Optional scale support, including Bluetooth mode.
- Optional tank sensor and hardware switches.
- MQTT / Home Assistant integration and offline mode.
Those options describe what current firmware can configure. They do not prove that every Silvia revision uses the same physical wiring or that every feature should be enabled on every build.
Why do the manual and release notes need to be read together?
The CleverCoffee manual repository still describes a workflow that includes PlatformIO and implementation steps, while the current v4 release/web-flasher path documents browser flashing and zero compile-time setup for normal firmware installation.
That is a version-drift warning, not a reason to ignore the manual. Use the manual for the implementation chapter that matches your hardware, then cross-check firmware, configuration and board revision against the current release/config/hardware repositories.
Does this page certify every Silvia V1–V6 as one universal build?
No. The old HBM page did exactly that, but the current public project sources checked for this audit do not provide one simple V1–V6 compatibility table that justifies treating all Silvia generations and markets as the same wiring plan.
Before selecting hardware, record:
- the exact Silvia version / rating label;
- market voltage;
- manufacturing period and any region-specific control hardware;
- existing PID, SSR, thermostat, switch, pump or wiring modifications;
- the exact CleverCoffee hardware revision you intend to use.
Then match those facts against the current CleverCoffee manual, wiring diagrams and hardware revision. If the real machine differs from the current diagram, the mismatch must be resolved before installation.
Which features should you plan first?
Plan the smallest useful build first, then add optional features only when the current hardware/config documentation supports them.
| Feature | Current evidence | Planning rule |
|---|---|---|
| Temperature control | Core project purpose; current config exposes brew/steam temperature settings and supported temperature sensors. | Choose the current sensor/hardware path before tuning. |
| OLED | Current config supports SSD1306 / SH1106 options. | Match display type in config rather than assuming one fixed screen. |
| Scale / brew by weight | Current config includes scale support and Bluetooth mode. | Optional. Add only when the scale path you own is supported by the current release. |
| Pressure sensor | Current config exposes it as optional. | Do not confuse software support with a universal Silvia plumbing recipe. |
| MQTT / Home Assistant | Current config exposes both. | Optional network integration; configure after the core controller is stable. |
| Pump / valve control | Current config includes relay/switch settings. | Requires exact hardware/manual evidence; HBM does not publish one universal mains connection map. |
What should you not copy from the old planner?
The previous page made several claims that were too broad or too version-sensitive for a durable planner. Do not carry these forward as current project rules:
- “Every Silvia V1–V6 is universally compatible.”
- One fixed BOM with a specific SSR rating, PSU, optocoupler, sensor, display and connector family.
- A fixed sub-degree machine-stability promise without a controlled, version-locked test.
- “Auto-tune and feedforward should always be enabled.”
- One universal pre-infusion/3-way-solenoid hardware recipe.
- “Buy the official PCB because it eliminates wiring mistakes.”
- One fixed internal-fit claim for every Silvia.
- One fixed reversibility time.
Where the current project publishes a feature or config option, HBM can say it exists. Whether it belongs in your machine is a separate compatibility and implementation question.
How should a new build be planned?
- Freeze the project version. Record the current CleverCoffee release and date you checked it.
- Freeze the hardware revision. Use the current CleverCoffee hardware repository / project channel to identify the PCB revision.
- Identify the Silvia. Record model/version, voltage, market and previous modifications.
- Choose only the features you actually need. Start with core temperature control before optional pressure, scale, valve or network features.
- Use the current manual and wiring diagram. Do not substitute an old NodeMCU forum photo for a current v4 build.
- Save rollback evidence. Photograph the untouched machine and label what you disconnect.
- Keep mains work out of guesswork. If a current diagram and the real machine differ, stop and resolve the difference.
Record the CleverCoffee release and PCB revision you planned against, identify the Silvia, and start with core temperature control before optional extras.
What are the stop conditions?
Stop before installation or commissioning when any of these are true:
Also stop if insulation, earth or connectors are damaged or unclear, or if the current manual and release sources disagree in a way you can't resolve.
- the hardware revision cannot be matched to current project documentation;
- the Silvia wiring/voltage/variant cannot be matched to the diagram you plan to use;
- previous modifications make the stock diagram unreliable;
- insulation, protective earth, connectors or enclosure condition is damaged or ambiguous;
- the current manual and current release/config sources disagree in a way you cannot resolve;
- you would need live mains probing to “figure out” which conductor is which from this web page.
Frequently asked questions
Is ranciliopid still the project name?
The current repositories use CleverCoffee under the rancilio-pid organization. Older ranciliopid/NodeMCU references are part of the project history.
Should a new build use ESP8266?
The project’s ESP8266 v3.3.0 release is explicitly described as the last major ESP8266 release with no further feature development. For a new current-v4 build, use the current ESP32 release/hardware path unless the project documentation for your specific case says otherwise.
Which ESP32 board does the current hardware repository use?
The current hardware repository is based on ESP32 DevKitC v4. It also warns that development-board pin mapping can change, so confirm the current revision rather than copying an old pin table.
Do I need the development PCB?
Not automatically. The repository includes minimal, development and experimental variants. Choose the current design that matches the features you actually need and verify the revision before ordering.
Can I use the old PlatformIO handbook steps with v4?
Some manual material remains useful for implementation, but the current v4 release/web-flasher path changed firmware installation and configuration. Cross-check any handbook chapter against the current v4 release, config reference and hardware revision before treating it as current.
Does this planner cover Gaggia or Quickmill installs?
No. Even if current CleverCoffee software has broader machine support, this page is scoped to Silvia planning. Use the machine-specific current project documentation for other platforms.
A frozen project version before a frozen parts list.
Start from the current release, current PCB revision and exact Silvia. If the manual, hardware and machine do not line up, stop before mains wiring.
If this guide saved you a service call or a wasted bag of beans, you can say thanks with a coffee.
Buy us a coffee