patrickcollins12/esphome-fan-controller

ESPHome Fan Controller

esphome-fan-controller's Issues

Offline capability

Hi Patrick
cool project !
Is there a way to make the setup offline resilient ?

• insure the fan regulates the temperature, even if there is no wifi connection, or homeassistant not available

mercimille
Christoph

Tacho connection in documentation

Hi, isn't there a mistake in the documentation? You mean that the green line is the rpm sensor that needs one GPIO per fan but the green line seems to be the PWM in fact (as it is connected together from both fans to one GPIO). IMHO the blue one seems to be the rpm sensor on the picture.

DHT11 temperature stops updating periodically

Thanks for sharing this project. I recently set this up for my new network cabinet, but found that DHT11 temperature sensor stops updating its temp values periodically for 30-45 minutes at a time:

Without the temperature input, the fan speed also stays steady, then kicks up to catch up once the temperature updates again.

The logs during these states display the DHT11 returns the exact same value repeatedly, without error.

[00:05:14][D][sensor:094]: 'Temperature': Sending state 31.80000 °C with 3 decimals of accuracy
[00:05:14][D][sensor:094]: 'Fan Speed (PWM Voltage)': Sending state 85.48193 % with 1 decimals of accuracy
[00:05:14][D][sensor:094]: 'Humidity': Sending state 32.00000 % with 0 decimals of accuracy
[00:05:15][D][sensor:094]: 'Temperature': Sending state 31.80000 °C with 3 decimals of accuracy
[00:05:15][D][sensor:094]: 'Fan Speed (PWM Voltage)': Sending state 85.47862 % with 1 decimals of accuracy
[00:05:15][D][sensor:094]: 'Humidity': Sending state 32.00000 % with 0 decimals of accuracy
[00:05:17][D][sensor:094]: 'Temperature': Sending state 31.80000 °C with 3 decimals of accuracy
[00:05:17][D][sensor:094]: 'Fan Speed (PWM Voltage)': Sending state 85.47533 % with 1 decimals of accuracy
[00:05:17][D][sensor:094]: 'Humidity': Sending state 32.00000 % with 0 decimals of accuracy
[00:05:18][D][sensor:094]: 'Temperature': Sending state 31.80000 °C with 3 decimals of accuracy
[00:05:18][D][sensor:094]: 'Fan Speed (PWM Voltage)': Sending state 85.47204 % with 1 decimals of accuracy
[00:05:18][D][sensor:094]: 'Humidity': Sending state 32.00000 % with 0 decimals of accuracy
[00:05:19][D][sensor:094]: 'Temperature': Sending state 31.80000 °C with 3 decimals of accuracy
[00:05:19][D][sensor:094]: 'Fan Speed (PWM Voltage)': Sending state 85.46874 % with 1 decimals of accuracy
[00:05:19][D][sensor:094]: 'Humidity': Sending state 32.00000 % with 0 decimals of accuracy
[00:05:21][D][sensor:094]: 'Temperature': Sending state 31.80000 °C with 3 decimals of accuracy
[00:05:21][D][sensor:094]: 'Fan Speed (PWM Voltage)': Sending state 85.46545 % with 1 decimals of accuracy
[00:05:21][D][sensor:094]: 'Humidity': Sending state 32.00000 % with 0 decimals of accuracy
[00:05:22][D][sensor:094]: 'Temperature': Sending state 31.80000 °C with 3 decimals of accuracy
[00:05:22][D][sensor:094]: 'Fan Speed (PWM Voltage)': Sending state 85.46216 % with 1 decimals of accuracy
[00:05:22][D][sensor:094]: 'Humidity': Sending state 32.00000 % with 0 decimals of accuracy
[00:05:23][D][sensor:094]: 'Temperature': Sending state 31.80000 °C with 3 decimals of accuracy
[00:05:23][D][sensor:094]: 'Fan Speed (PWM Voltage)': Sending state 85.45885 % with 1 decimals of accuracy
[00:05:23][D][sensor:094]: 'Humidity': Sending state 32.00000 % with 0 decimals of accuracy
[00:05:24][D][sensor:094]: 'Temperature': Sending state 31.80000 °C with 3 decimals of accuracy

I have yet to look into the signal integrity on the data line from the DHT11. But I have tried to swap sensors and got similar behavior. The only other things I could think of is connecting directly to the header on the ESP rather than the 3-pin JST header, or trying shorter wires to the sensor. Is a pullup resistor required on the data line?

Any other insights would be appreciated.

Need advice: Still high temps. What RPM is good?

Thanks for this great project first of all.

Can I ask you all what RPM you are using?
My 6RU Server rack is at 40 degree celsius with 100% voltage and 1150 RPM.
Might have to use a stronger fan.

Also, what causes the fan to run at 1150 RPM even though it can do 1500?

Thanks for your hep

Set the target temperature from an automation

I installed your fan-project in my NAS cabinet with two compartments. I have the temperature sensor at the top, because that's where my NAS is, which runs during the day. Below I have my backup NAS and my Raspberry.
I know, I just can install a second thermostat and use it. But I just want to monitore the system and HDD temperatures and want to set the PWM to ~100% or the target temperature to 20° just in case of an emergency. I don't think I'll need it, but having is better than needing.
So I wanted to ask if I can change the PWM. Since it would probably be constantly overwritten by the controller, lowering the target temperature is probably a better choice.
However, I couldn't find it. Is there a way to do this that I've just overlooked?

Thanks in advance!

Additional fans

Not sure this is an issue as I haven't actually started work on it. But I want to be able to connect 3 pwm fans and be able to read their rpm etc.

I have looked over the yaml and I assume I just copy the portion of code that specifies the ledc platform but change the gpio

If any one has a config for 2 or more fans that would be amazing.

No Integration in Home Assistant

Hello,

I have followed your documentation ans installed the fan controller,
The controler and all other work perfekt, only my Home Assistant show no new integration.

Hope you have a solution for that.

One console with two separate connected fans

Hello,

first of all respect and thanks for the guide! It was fun building it.
I connected two fans (one for in, one for out) to different pins. - I know I could have just soldered them together, but I didn't want to. - I can now control both separately and also get all sensor values output separately.

But I would like to specify only one target temperature value via the console and this should be given to both output IDs.

Is this possible? As far as I understand, I would have to specify both IDs of the "cool_output" here in the code. But I can't find the syntax for it.

climate:
  - platform: pid
    name: "Console Fan Thermostat Out"
    id: console_thermostat_out
    sensor: console_fan_temperature

    # It is summer right now, so 30c is a decent target.
    default_target_temperature: 30°C
    cool_output: console_fan_speed

+/- in wiring

Hi, awesome little project !

But for me it looks like your schematic has a little error with plus and minus switched on the stepdown side and the bridge to ground on 3.3...

s

cool setup just what i was looking for but my fan does not shut off totally

i set the fan at 0% and 50% but still it wont stop running totally, do you know what i can do

Offset ?

I have finished my solar batter heater design and it's been running for several days now. The only issue I see is the offset.

I've tried various values and none seem to make any difference... so I just set the temp 2-3 degrees above where I want it. So strange.

I have 2 sensors, a probe that always works but isn't exact and the actual BMS temp as a primary. if the BMS temp becomes unavailable (Solar Assistant Pi crashes, HA crashes,etc), the probe temp is used instead. Everything is contained within the esp and ESPHome.

overall I'm very happy with the results!

Manual and thermostat fan control

Hi Patrick @patrickcollins12 ,
I am new to Github and I am not sure, whether this is the right place to ask you this.
I had been using your project quite successfully a few weeks ago (I want to use the warm air from an PV-inverter to warm my PV battery during the cold and humid winter months in my garage). I had uncommented the part for the manual control of the fan speed and - as you said in the readme - switched OFF the thermostat when I wanted to control the fan manually. This worked well until a few days ago. Now, even when I switch the thermostat OFF, the manual control only gives a short increase in rpm and then the rpm of the fan go back to zero, as if the thermostat was not switched OFF. I suspect that there was an update of the platforms somewhere which broke this. If I delete all the thermostat code from your project, I can control the fan manually without problems as before. Do you have any advise how I can have the option again to use both thermostat and manual control together as before?
Thank you very much for this project. It's my first Home Assistant/ESPHome project and I am having fun because of your great work.
Klaus

No longer able to compile.

I was trying to change some of the code and whenever i try to upload to the esp i get the following error.. it happens on 2 different boards. i also would like to make another one but cant if it wont upload. could you provide any help? i love this project and i get ALOT of use out of it.

I think it happened after an update and i feel like a url or dependency is no longer available.im completely unsure,

Processing aquariumcooler (board: esp32dev; framework: arduino; platform: platformio/espressif32 @ 5.2.0)

HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash

• toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch3

warning: Calling missing SConscript without error is deprecated.
Transition by adding must_exist=False to SConscript calls.
Missing SConscript '/data/cache/platformio/packages/framework-arduinoespressif32/tools/platformio-build.py'
File "/data/cache/platformio/platforms/espressif32/builder/frameworks/arduino.py", line 41, in
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
Library Manager: Installing FS
Warning! Could not find the package with 'FS' requirements for your system 'linux_x86_64'
Library Manager: Installing Update
Warning! Could not find the package with 'Update' requirements for your system 'linux_x86_64'
Library Manager: Installing ESPmDNS
Warning! Could not find the package with 'ESPmDNS' requirements for your system 'linux_x86_64'
Dependency Graph
|-- AsyncTCP-esphome @ 1.2.2
|-- WiFi @ 1.2.7
|-- ESPAsyncWebServer-esphome @ 2.1.0
| |-- AsyncTCP-esphome @ 1.2.2
|-- DNSServer @ 1.1.0
|-- noise-c @ 0.1.4
| |-- libsodium @ 1.10018.1
Compiling /data/aquariumcooler/.pioenvs/aquariumcooler/src/esphome/components/adc/adc_sensor.cpp.o
Compiling /data/aquariumcooler/.pioenvs/aquariumcooler/src/esphome/components/api/api_connection.cpp.o
In file included from src/esphome/components/adc/adc_sensor.h:4,
from src/esphome/components/adc/adc_sensor.cpp:1:
src/esphome/core/hal.h:14:10: fatal error: esp_attr.h: No such file or directory

---

• Looking for esp_attr.h dependency? Check our library registry!
• CLI > platformio lib search "header:esp_attr.h"
• Web > https://registry.platformio.org/search?q=header:esp_attr.h

---

#include <esp_attr.h>
^~~~~~~~~~~~
compilation terminated.
*** [/data/aquariumcooler/.pioenvs/aquariumcooler/src/esphome/components/adc/adc_sensor.cpp.o] Error 1
In file included from src/esphome/components/socket/socket.h:5,
from src/esphome/components/api/api_frame_helper.h:13,
from src/esphome/components/api/api_connection.h:3,
from src/esphome/components/api/api_connection.cpp:1:
src/esphome/components/socket/headers.h:116:10: fatal error: sys/ioctl.h: No such file or directory
#include <sys/ioctl.h>
^~~~~~~~~~~~~
compilation terminated.
*** [/data/aquariumcooler/.pioenvs/aquariumcooler/src/esphome/components/api/api_connection.cpp.o] Error 1
========================== [FAILED] Took 1.99 seconds ==========================

Problems using Dallas sensor

I have this controller working well on my Solar battery heater application. I use it with a Pwm dimmer to control the heating pads and I use a temp sensor from the battery BMS software that is exposed via a homeassistant sensor. It's all detailed in this Solar forum:

https://diysolarforum.com/threads/new-battery-heater-controller-home-assistant-and-esphome.53665/#post-685275

however, I have noticed that there are dropouts of that sensor when home assistant becomes unavailable for any reason which results in the battery either not being heated or being heated too much. So I am trying to add a local Dallas temp probe that I can sandwich between the batteries and have a self contained system running completely in ESPHome on one chip.

The problem is whenever the Pwm dimmer is ON (even at 1%), the Dallas temp sensor throws "Scratch pad checksum invalid!" errors and can't be read.

I'm no stranger to this approach in ESPHome or these sensors. I have several in use in my greenhouse and other areas. I've tried shielding the sensor wires, and even tried every available GPIO for the sensor and even watched the Dallas waveform on my scope when adjusting the pull-up resistor, all to no avail.

using a DHT type sensor isn't an option due to the way the batteries are mounted. It really needs to be a "probe" type sensor.

Any pointers or ideas to solve this are welcome!

Reduce flash writes?

As far as I can tell the config you have writes a couple of parameters to flash every minute, amounting to ~0.5m writes per year. From what I've read the flash memory in ESP32 is expected to last 100k-1m write operations. I don't know if there's wear leveling in an ESP (guess not), so it might make sense to reduce writing the parameters to the ESP every 15min or so?

Fan Override does not work

When setting the Fan to On (while disabling the thermostat) and setting a value the fans do spin up but go down again as soon as the next temperature reading comes in. So the override does not seem to be stable or I am doing it wrong?

Cool project!

Nice job on this! I'm totally stealing your PID efforts for 2 of my projects.

The first (and easier) is for my solar battery heaters. I just finished getting a dimmer circuit working for 4 heating pads.
https://diysolarforum.com/threads/new-battery-heater-controller-home-assistant-and-esphome.53665/
I just got the ESPHome file to compile with all your PID stuff and added all the sensors to home assistant. It's late and I'll head to my shop in the AM to try and understand how this cool PID controller works.

The second, and far more advanced use case, is for my Smart Wood Pellet Stove project. I finally have victory over this pellet stove after a year of slogging it to make it actually smart with 685 lines of ESPHOME code to control every aspect of it.
https://github.com/jazzmonger/wood-stove-with-TYWE1S-Tuya-chip

My plan is to employ the PID component to control the Auger feed motor control for the pellets to barely keep the stove lit so the house doesn't overheat and the stove doesn't have to cycle on and off, requiring constant relighting and burning out $50 igniters every few months. In the graph, you can see the fire burning and cooling and burning and cooling, etc, etc as pellets are added and then backed off.

The idea is to maintain a constant LOW target burn temp that I can set. Minimum is about 190C, which I've found by trial and error and keeps the stove on. This barely keeps the pellets burning and minimal heat output, perfect as the weather gets gradually warmer outside. I'd increase that a bit when outside temps drop and the stove has to work harder to keep the room warm.

jazzmonger/wood-pellet-stove-with-TYWE1S-Tuya-chip#28

I'm pondering what params to play with to use for the PID control line.
I have a few options:
Auger on time ( this is tricky as too little and fire goes out, too much and u get smoke)
Auger off time - how long before more pellets are added
Stoking temp - how low the exhaust temp goes before manually stoking the fire w more pellets

I you have any thoughts on this after the dozens of hours you probably spent on figuring out the PID stuff, I'm all ears!

This is so cool! But...couple of questions?

Hi,

I have this running to control three fans on my inverter. Soon I will expand to cover a second inverter with a second set of fans (once I move out of breadboard stage). You made it so super easy to get up and running!

Question 1:
The main issue with inverter cooling is that I need a responsive cooling system but one that is skewed - I need a fast(ish) response and the long slow tail....is this where kd comes in?

Question 2:
I have a DHT dangling over the back of the inverter radiator to read the air temperature, but really I need something better to read the radiator fin temperature directly, or a way of pushing the inverter internal temperature (which HA knows) to the fan controller...but with the option to still use DHT incase HA fails for some reason. That is, use inverter internal temp reading and if null revert to DHT temperature. Is this possible? if so how the heck could I pull that off?

Question 3:
I'd really like to bring in the tachometer data so that I can detect fan failure. I can do all the logic in HA/NodeRed, just need to plumb up the pins and get a reading....any tips? I've seen a few ways of doing it with resistors, logic level shifters, capacitors etc....but it seems a little complicated? From the looks of things I have exactly the same fans as you... :-)

Thanks heaps!

CP.

constantly reboots

Hello Patrick,

thanks for that repo. It is perfect for my need to cool the technic cupboard for DSL Router, NAS and these things in my livingroom.

To customize the project for my need without homeassistant but with node-red i disabled the HA API and enabled MQTT. I tried to add a 2nd temperature sensor but whatever i did it never had a value. So trying differenz GPIOs Pins, changing the sensor or add a pullup resistance it never worked. But thats not the question.

I think, in general, i havn't changed alot in your code but the scetch is never stable. Sometimes the ESP32 is running for 10 hours, sometimes only for 15min.
The reset reason is always Software Reset CPU

Any ideas what the problem could be or how to debug it?

Thanks

Reading multiple tacho signals separate

Have you ever tried to read multiple tacho signals to check individual fans RPMs?

Fritzing Img ESP Pinouts?

Hi @patrickcollins12 - thanks for the awesome project! This has been on my to-do list for months, although I'm intending to modify it (or at least try to!) to control speed with humidity (drying cupboard use-case!)... Although just noticed I'm also going to have the 0% PWM / fan off issue too...

However, just as I was about to get going, it seems that the Fritzing diagram of the ESP pinouts don't match my ESP (Firebeetle), is the diagram intended to be correct or is it more a rough guide and should follow the descriptions? For example, your description and code use GPIO25, but I don't believe that's the pin shown on the fritzing?

Thanks again...

question about external temperature instead of built in dht

hi, this project is cool
I am not super fluent in ESPhome - would someone help me modifying the code so that PID controller reacts on external temperature provided by the sensos that is already on Home Assistant, i.e. entity_id: sensor.external_cpu_temperature

I am not sure where in this yaml to include the temperature provided by this sensor (external_cpu_temperature) - it will be provided every few seconds if that matters.

thank you

Two Sensors

Hey Patrick

I used yours as an example to build a fan temperature control for my network cabinet. Used a WT32-ETH01.

I was thinking of using two temperature sensors. One inside and another outside. Use the one outside + x °C as the set-point. Thus doesn't matter what the room temperature it will only be a few degrees more inside the cabinet. Any thoughts?

My config at the moment based on yours:

#https://github.com/patrickcollins12/esphome-fan-controller/blob/master/console-fan.yaml

substitutions:
device_name: networkcabinet
friendly_name: "Network Cabinet"
device_ip: !secret networkcabinet_ip

###############################################################################

esphome:
name: ${device_name}
platform: ESP32
board: esp-wrover-kit

###############################################################################

preferences:
flash_write_interval: 15min

###############################################################################

ethernet:
type: LAN8720
mdc_pin: GPIO23
mdio_pin: GPIO18
clk_mode: GPIO0_IN
phy_addr: 1
power_pin: GPIO16
manual_ip:
static_ip: ${device_ip}
gateway: !secret localgateway
subnet: !secret localsubnet
dns1: !secret localdns1
dns2: !secret localdns2

###############################################################################

Enable logging

logger:

###############################################################################

Enable Home Assistant API

api:
encryption:
key: !secret apikey
ota:
password: !secret otapass

###############################################################################

Time

time:

• platform: homeassistant
  id: esptime

###############################################################################

i2c:
sda: 33
scl: 32
scan: true
frequency: 800kHz

###############################################################################

text_sensor:

Send Uptime in raw seconds

• platform: template
  id: uptime_human
  icon: mdi:clock-start
  internal: true

###############################################################################

switch:

• platform: restart
  name: "${friendly_name} Reboot"

###############################################################################

sensor:

• platform: bme280
  temperature:
  name: "${friendly_name} Amb Temp"
  id: bme280_temperature
  oversampling: 1x
  pressure:
  name: "${friendly_name} Amb Press"
  id: bme280_pressure
  humidity:
  name: "${friendly_name} Amb Hum"
  id: bme280_humidity
  address: 0x76
  iir_filter: 16x
  update_interval: 5s

RPM Signal from Fan A

• platform: pulse_counter
  pin:
  number: 36
  name: ${friendly_name} Fan A Speed
  id: fan_a_pulse
  unit_of_measurement: 'RPM'
  filters:
  • multiply: 0.5
    count_mode:
    rising_edge: INCREMENT
    falling_edge: DISABLE
    update_interval: 5s
    accuracy_decimals: 0

RPM Signal from Fan B

• platform: pulse_counter
  pin:
  number: 39
  name: ${friendly_name} Fan B Speed
  id: fan_b_pulse
  unit_of_measurement: 'RPM'
  filters:
  • multiply: 0.5
    count_mode:
    rising_edge: INCREMENT
    falling_edge: DISABLE
    update_interval: 5s
    accuracy_decimals: 0

Uptime

• platform: uptime
  name: $friendly_name Uptime
  id: uptime_sensor
  update_interval: 60s
  on_raw_value:
  then:
  - text_sensor.template.publish:
  id: uptime_human
  # Custom C++ code to generate the result
  state: !lambda |-
  int seconds = round(id(uptime_sensor).raw_state);
  int days = seconds / (24 * 3600);
  seconds = seconds % (24 * 3600);
  int hours = seconds / 3600;
  seconds = seconds % 3600;
  int minutes = seconds / 60;
  seconds = seconds % 60;
  return (
  (days ? to_string(days) + "d " : "") +
  (hours ? to_string(hours) + "h " : "") +
  (minutes ? to_string(minutes) + "m " : "") +
  (to_string(seconds) + "s")
  ).c_str();

• platform: template
  name: $friendly_name p term
  id: p_term
  unit_of_measurement: "%"
  accuracy_decimals: 2

• platform: template
  name: $friendly_name i term
  id: i_term
  unit_of_measurement: "%"
  accuracy_decimals: 2

• platform: template
  name: $friendly_name d term
  id: d_term
  unit_of_measurement: "%"
  accuracy_decimals: 2

• platform: template
  name: $friendly_name output value
  unit_of_measurement: "%"
  id: o_term
  accuracy_decimals: 2

• platform: template
  name: $friendly_name error value
  id: e_term
  accuracy_decimals: 2

• platform: template
  name: $friendly_name is in deadband
  id: in_deadband_term
  accuracy_decimals: 0

###############################################################################
output:

• platform: ledc
  id: coolingfan
  pin: 15
  frequency: 25000 Hz
  min_power: 0.2
  max_power: 1.0

###############################################################################

number:

KP

• platform: template
  name: "${friendly_name} kp"
  icon: mdi:chart-bell-curve
  restore_value: true
  initial_value: 0.3
  min_value: 0
  max_value: 50
  step: 0.001
  set_action:
  lambda: |-
  id(${device_name}_pid).set_kp( x );

KI

• platform: template
  name: "${friendly_name} ki"
  icon: mdi:chart-bell-curve
  restore_value: true
  initial_value: 0.0015
  min_value: 0
  max_value: 50
  step: 0.0001
  set_action:
  lambda: id(${device_name}_pid).set_ki( x );

KD

• platform: template
  name: "${friendly_name} kd"
  icon: mdi:chart-bell-curve
  restore_value: true
  initial_value: 0.0
  min_value: -50
  max_value: 50
  step: 0.001
  set_action:
  lambda: id(${device_name}_pid).set_kd( x );

Set threshold low

• platform: template
  name: "${friendly_name} Deadband Threshold Low"
  icon: mdi:chart-bell-curve
  restore_value: true
  initial_value: -1.0
  min_value: -20
  max_value: 0
  step: 0.1
  set_action:
  lambda: id(${device_name}_pid).set_threshold_low( x );

Set threshold high

• platform: template
  name: "${friendly_name} Deadband Threshold High"
  icon: mdi:chart-bell-curve
  restore_value: true
  initial_value: 0.4
  min_value: 0
  max_value: 20
  step: 0.1
  set_action:
  lambda: id(${device_name}_pid).set_threshold_high( x );

Set ki multiplier

• platform: template
  name: "${friendly_name} Deadband ki Multiplier"
  icon: mdi:chart-bell-curve
  restore_value: true
  initial_value: 0.04
  min_value: 0
  max_value: .2
  step: 0.01
  set_action:
  lambda: id(${device_name}_pid).set_ki_multiplier( x );

###############################################################################

climate:

• platform: pid
  id: ${device_name}_pid
  name: "${friendly_name} Temp Controller"
  visual:
  min_temperature: 20.00 °C
  max_temperature: 50.00 °C
  temperature_step: 0.1 °C
  sensor: bme280_temperature
  default_target_temperature: 28.00 °C
  cool_output: coolingfan
  control_parameters:
  kp: 0.3
  ki: 0.0015
  kd: 0.0
  max_integral: 0.0
  output_averaging_samples: 1
  derivative_averaging_samples: 5
  deadband_parameters:
  threshold_high: 0.4°C
  threshold_low: -1.0°C
  kp_multiplier: 0.0
  ki_multiplier: 0.04
  kd_multiplier: 0.0
  deadband_output_averaging_samples: 15
  on_state:
  • sensor.template.publish:
    id: p_term
    state: !lambda 'return -id(${device_name}_pid).get_proportional_term() * 100.0;'
  • sensor.template.publish:
    id: i_term
    state: !lambda 'return -id(${device_name}_pid).get_integral_term()* 100.0;'
  • sensor.template.publish:
    id: d_term
    state: !lambda 'return -id(${device_name}_pid).get_derivative_term()* 100.0;'
  • sensor.template.publish:
    id: o_term
    state: !lambda 'return -id(${device_name}_pid).get_output_value()* 100.0;'
  • sensor.template.publish:
    id: in_deadband_term
    state: !lambda 'return id(${device_name}_pid).in_deadband();'
  • sensor.template.publish:
    id: e_term
    state: !lambda 'return -id(${device_name}_pid).get_error_value();'

LED strip control

Hi.

Really great project! It seems to be exactly what I'm looking for. I found it while searching for ways to make a 3D printer enclosure, like this: https://www.reddit.com/r/3Dprinting/comments/10io7st/how_the_ikea_platsa_3d_printer_enclosure_looks/

So, in the enclosure I would use your project to add a bit of active cooling / stabilize temperature. However, I would also like to add some lights in there - like the linked enclosure.

So, I figured the ESPHome would be able to control the lights, but to simplify the project I wanted to avoid also needing a 5V rail - So, I found these LED-strips: WS2815.

I was wondering if you knew whether it would be as simply as adding them to the 12V rail and adding them in the ESPHome component?

I realize this project isn't about lighting via ESPHome and it might not be needed in most peoples "media console housing", but I figured I would ask here since I consider my idea/thought an extension of your project.

Thank you for any input you could provide :)

3 wire fan

Hi, is it going to operate with 3 wire fan? I have two of these and would lik to try. I assume the fourth pin that is missing is tachometer pin,so i will miss the feedback

[Request] Possible to use two temperature sensors?

Thanks for this repo.. the code and schematics work great for me. My prototype is working great however I have a question.. is it possible to add another DHT temperature probe? My AV cabinets have two zones and I've added a fan in each. One is for the AV Receiver (always on when using TV) and the other is for gaming consoles (only on sometimes). I'd rather not build two separate fan controllers for two compartments. I don't mind both sides spinning faster when only one zone is needing more cooling (e.g. the gaming side being cooled even if there are no consoles active).

I had to reassign the DHT to GPIO23 on my nodemcu-32s board else it wouldn't work. PWM is on GPIO15. I've looking at the code as to what would be needed to support a 2nd DHT but the code is a bit too advanced for me. Ideally it would report two temperature values to Home Assistant as well and act on the worst one. But I would be more than pleased to get the worst value of the two as well. (one being 29c and the other 35c.. having it act like it's 35c and adjust fan accordingly).

Could you help with this? Many thanks.

Can I do this project with a fan control with potentiometer?

Hi, I bought a ventilation kit with potentiometer from Aliexpress,

now I can integrate it into the home assistant with a smart socket, is it possible to connect this potentiometer to esp32?

thank you for your availability and kindness

Fan Connector Type Doesn't Seem Right

I wanted to do this project to cool my electronics closet. I'm not an EE and haven't done electronics in ages so I could be wrong about this.

I bought the same Corsair fans as you specified (LM 120). In you image, you specify a JST connector. My research shows that the connector on the fan connects to a Molex 0470531000. It has a 2.54mm pitch as opposed to the 2.5mm of the JST connectors. There appear to be 4 different types, all 2.5mm. I'm going to go with the Molex as I'm going to build it on a solder breadboard.

The other confusing item is the pin out for the fan. Your wiring diagram shows using the first three pins. The third pin is Tach. In you description, you mention not using this. The web documentation I've found says pin 4 is control/PWM. I'm assuming that's the one you meant.

Thanks for posting this project. I've been thinking about how I could do something similar for quite some time. Now I have a solution.

make fan stop spinning at zero

Hello, I just installed a Corsair ML120 fan as you say and it works well except for the one when it reaches the stop temperature and it keeps turning at 1400 RPM. Could you help me create a stop or what parameters can I change to make it stop? the adjustments that you had at 13% the stop changed it to 0% but it continues turning. could you help me?? thank you.