@CeeWeee wrote:

Hi,

I have a capacitive sensor measuring moisture in a plant.

sensor:
  - platform: adc
    pin: 36
    attenuation: 11db
    name: "Kontor Plante Fugtighed"
    update_interval: 60s

It provides fine readings, but of course a Voltage reading. I guess 3.3v for 0% moisture, and 0.0v for 100% moisture.

40888×152 8.62 KB

Question is if there is a kind of mapping parameter I can use to get this displayed as the % moisture?

In Arduino code I would use

map(value, fromLow, fromHigh, toLow, toHigh)

Does this exist? What should I add to my code?

Thanks!

Posts: 2

Participants: 2

Read full topic

@Rdoull wrote:

Hi all,

I’m trying to install ESPhome from Hass.io add-on store but it wont install for some reason…

I’m running a Raspi 3+ b with Hass.io I have Home Assistant 0.103.6 installed internet is via Ethernet cable and power is a 5v 3a supply

I have followed the instructions to the letter (as far as I know) and get as far as clicking “install” then the button fades, I get a progress circle for about 2 seconds and it all reverts back to normal… the instructions said it could take a while, so I left everything alone (thinking its working in the background) walked away from the computer and left it, watched some tv, came back about 2 hours later (plenty of time I thought) but still not installed… can anyone help me please?

thank you in advance

Robin

edit: I dont have ssh on the is pi as I dont need it so my config for ESPhome is empty… is that the problem? if so, what should I put in here?

Posts: 14

Participants: 6

Read full topic

@DeeBeeKay wrote:

Hi all,

I don’t know if this is the best place to post this, since I don’t even have a yaml to share yet, but anyway.

I would like to build a device that opens a windows, and integrate it into HomeAssistant using ESPHome. Used with my existing temperature sensors, it could open windows strategically to create a through-draft, and used with my existing wind and rain sensors, it could close windows when a storm is brewing.

I am aware that commercial options for this exist, but they are terrifyingly expensive, and none that I have found online are available in my country anyway. So I have to DIY it if I want this. Also, it cannot be terribly ugly, or my wife will press the abort button.

Now, all of my windows look like this: https://imgur.com/TxuUX1p

There is a handle mechanism for closing it, which I will probably just remove. But at the bottom, there is an arm. When you open the window, it slides along a rail, and you tighten a screw to hold the window open. I don’t remember seeing windows like these any time I was overseas, but they are standard here.

Now, it seems to make the most sense to me to add a motor to the existing hardware, or at least, to piggyback on the existing concept. The reason for this is that the mounting points for this hardware are standardised and built into every windowframe in my house, so there are points I can pass bolts through without modifying the windowframe.

What I have thought of doing is this: put a servo motor at the fulcrum, like this: https://imgur.com/NbaiWul

It will swing the arm outward, sliding the locking head along the rail and pushing the window open. Given the dodgy state of the brass, it may be that friction will be too high to work well, but I can easily replace the old rail with a smooth rod - or even a linear rail.

I have a couple of metal gear servos that I picked up on sale a few months ago that apparently have 20kg/cm of torque, which seems like it should be powerful enough to move the window. However, what I am concerned about is that a servo would get wrecked doing this kind of work regularly. Surely it would need to remain powered the whole time if it is to hold the window open? Wouldn’t the stress of wind on the armature translate to stress on the gears?

Is there a more suitable (affordable) motor to use? Or a better way of opening the window entirely?

Or a method of relieving stress on the armature? I thought of using a second small motor to turn the screw of the locking mechanism, or replacing the locking mechanism with something mechanically similar like a peg through a hole in the sliding arm, which could be inserted/retracted with a solenoid.

Any kind of input or ideas would be appreciated, I’m spitballing here.

Posts: 10

Participants: 3

Read full topic

@mrwsl wrote:

Hey there,

I was thinking about replacing one of my corridor switches with a Sonoff T1 but before I buy it I wanted to ask if someone has experience with a similar setup.

My corridor has two switches or buttons to be more specific. They both control one relay that is turning the lights on and off. Whenever one of them is pressed they revert the current state of the light (on -> off; off -> on).
My plan is to replace one of them with a Sonoff T1. Now my question is: is there any way for the Sonoff/esphome to know what state the light has? If I press the old, not-smart switch, is there any way for the Sonoff to recognize the state change?

Posts: 3

Participants: 3

Read full topic

@slindberg wrote:

Hey

I have build a simple weather station with a Nodemcu esp32s board running esphome and with a AM2301 temp & humidity sensor.

In the moment the code are setup to send sensor data to home assistant and after send the state data back to nodemcu esp32s for to print it to the lcd display.

I would like to skip the home assistant step and directly let nodemcu esp32s send the temp & humidity sensor data to the display locally.

How could the code look out ?

I post here my code as it is in the moment then its stille are running together with home assistant.

# | Sensorer |
sensor:
  - platform: dht
    pin: 27
    model: dht22 
    id: temp
    temperature:
      name: "SenseNode Temp"
    humidity:
      name: "SenseNode Humidity"
    update_interval: 25s

display:
  - platform: lcd_pcf8574
    dimensions: 20x4
    address: 0x27
    lambda: |-
      // Print office temperature (from homeassistant sensor)
      it.print(0, 0, "VEJRSTATION:"); it.print(0, 1, "Temp:"); it.print(0, 2, "Humidity:");
      if (id(sensenode_temp_2).state == id(sensenode_temp_2).state) 
      it.printf(5, 1,"%.1fC", id(sensenode_temp_2).state);
      if (id(sensenode_humidity_2).state == id(sensenode_humidity_2).state) {
      it.printf(9, 2,"%.1f%%\n", id(sensenode_humidity_2).state);
      it.printf(0, 3,"", id(my_time));
      it.strftime(0, 3, "%H:%M:%S %d.%m.%Y", id(my_time).now());
      } else {
      it.print(4, 3, "Loading Wait!");
      }
     

# Home assistant Sensor    
  - platform: homeassistant
    id: sensenode_temp_2
    entity_id: sensor.sensenode_temp_2
    internal: true 
    
  - platform: homeassistant
    id: sensenode_humidity_2
    entity_id: sensor.sensenode_humidity_2
    internal: true    

Best regards slindberg

Posts: 2

Participants: 2

Read full topic

@slarti wrote:

Hi

I’ve been at this for a couple of days. I’m trying to control my mini-blinds (venetian blinds) with a servo using Esphome. I’ve done this a few times over the years with arduino but now I’d like to do it with a Wemos D1 mini and add some functionality. I’ve used MySensors and Domoticz but now I’m considering moving to Home Assistant and Esphome.

My goal:

To have a rotary encoder that gradually moves the servo to open/close the slats while the state is reported back to HA and if the state (including position, not just OPEN/CLOSED) is changed in HA, move the servo accordingly.

Where I’m now:

I have a ton of YAML (which is NOT growing on me…) which does pretty much everyhing I just described except for the position adjustment when called from Home Assistant. Open/close works even from there.

esphome:
  name: test
  platform: ESP8266
  board: d1_mini

wifi:
  ssid: xxx
  password: xxx

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Test Fallback Hotspot"
    password: ...

captive_portal:

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:

globals:
  - id: my_pos
    type: float

     
script:
  - id: move_servo
    then:
      - servo.write:
          id: my_servo
          level: !lambda "return id(my_pos);"
      - delay: 1s
      - servo.detach: my_servo
      - cover.template.publish:
          id: pub_pos
          position: !lambda "return id(my_pos) / 2 + 0.5;"
      - logger.log:
          format: "position: %.2f"
          args: ['id(my_pos)']

sensor:
  - platform: rotary_encoder
    name: "Rotary Encoder"
    id: knob
    pin_a: D8
    pin_b: D6
    min_value: -1
    max_value: 1
    on_value:
      then:
          - lambda: !lambda |-
                if (id(my_pos) > -0.9 && id(my_pos) < 0.9) {
                id(my_pos) += id(knob).state * 0.1;
                }
                else if (id(my_pos) <= -0.9 && id(knob).state == -1 && id(my_pos) > -1) {
                id(my_pos) = -1;
                }
                else if (id(my_pos) >= 0.9 && id(knob).state == 1 && id(my_pos) < 1) {
                id(my_pos) = 1;
                }
                else if (id(my_pos) == 1 && id(knob).state == -1) {
                id(my_pos) += id(knob).state * 0.1;
                }
                else if (id(my_pos) == -1 && id(knob).state == 1) {
                id(my_pos) += id(knob).state * 0.1;
                }            
          - script.execute: move_servo
          - sensor.rotary_encoder.set_value:
              id: knob
              value: 0         


binary_sensor:
  - platform: gpio
    pin:
      number: D7
      mode: INPUT_PULLUP
    id: knob_button

    
servo:
  - id: my_servo
    output: pwm_output
    
output:
  - platform: esp8266_pwm
    id: pwm_output
    pin: D5
    frequency: 50 Hz
         
cover:
  - platform: template
    name: "Blinds"
    id: pub_pos

    open_action:
      - lambda: |-
          id(my_pos) = 1;
      - script.execute: move_servo

    close_action:     
      - lambda: |-
          id(my_pos) = -1;
      - script.execute: move_servo

    stop_action:
      - servo.detach: my_servo
    
    position_action:
      - logger.log:
          format: "position_action_position: %.2f"
          args: ['id(pub_pos).position']      
      - lambda: |-
          id(my_pos) = 2 * (id(pub_pos).position) - 1.0;
      - script.execute: move_servo

The log tells me that when a position command comes in from HA id(pub_pos) is not a float but something very large and it’s not mapped to the variable (my_pos) which would drive the servo script.

This is probably some sort of a bug in Esphome but as this is a little convoluted to write in YAML, I was wondering if anyone has made a custom cover component that writes values directly to a servo? Without going through the change global variable -> script - servo component - output component hoops?

Posts: 1

Participants: 1

Read full topic

@Ralf wrote:

Hello,

Already searched for keywords „water leak“ but not really found s.th. Here, so asking:

did someone of you have a water leak sensor with esp already and would share setup of hardware, esp code and maybe ha integration here?

Thanks in advance,
Ralf

Posts: 2

Participants: 2

Read full topic

@accelle wrote:

I’m trying to modify glade air freshener by attaching d1 mini on it.
However, it looks like I need to replace the original board (motor driver) with d1 mini
motor shield.

With esphome, how do you control this kind of motor driver? I tried the following config but it doesn’t work:

output:
 - platform: gpio
   pin: D2
   id: direction_pin
 - platform: esp8266_pwm  # or ledc if on ESP32
   pin: D3
   id: speed_pin
switch:
  - platform: template
    name: "Kitchen Glade"
    turn_on_action:
     - output.turn_on: direction_pin
     - output.set_level:
        id: speed_pin
        level: 100%
     - delay: 1000ms
     - output.turn_off: speed_pin
     - output.turn_off: direction_pin
     - output.set_level:
        id: speed_pin
        level: 100%
     - delay: 1000ms
     - output.turn_off: speed_pin

Posts: 1

Participants: 1

Read full topic

@kolovsky wrote:

Good day!
I am new to ESPHome. Need some help from experts.
Sorry in advance for spelling.

Tasks: I want to achieve two things:
1 ) Dimm led’s (than are in tactile wall switches) then I click it.
2) Adjusting brightness of those led’s (all together - 12 nods) depending on Lux sensor.

I started up with this configuration. All worked fine except I could not find a way how to control Leds brightness automatically from frontend.

output:
  - platform: gpio
    pin: 16
    id: rel1
    
##### LEDS
  - platform: esp8266_pwm
    pin: GPIO5
    frequency: 400 Hz
    id: pwm_rel1
    min_power: 0.0
    max_power: 0.85
    inverted: true
    
  ##         FRONTEND

light:
  - platform: binary
    name: "Boiler room"
    output: rel1
    id: light1
 
  - platform: monochromatic
    name: "led1"
    output: pwm_rel1
    

binary_sensor: 
  - platform: gpio
    internal: true #Mark this component as internal. Internal components will not be exposed to the frontend (like Home Assistant). Only specifying an id without a name will implicitly set this to true.
    name: "in1"
    #id: "in1"
    filters:
      - delayed_on: 10ms
      - delayed_off: 10ms
    pin:
      number: 14
      mode: INPUT_PULLUP
      inverted: true
    on_multi_click:
    - timing:
        - ON for at most 1s
        - OFF for at most 1s
        - ON for at most 1s
        - OFF for at least 0.2s
      then:
        - fan.toggle: vent2
        - logger.log: "Double click"
       - timing:
        - ON for at most 1s
        - OFF for at least 0.5s
      then:
        - light.toggle: light1
        - logger.log: "Single Click"
#        - output.set_level:  #ne obnowlayet frontend
#            id: pwm_rel1
 #           level: 20%

When I switch Light from HA - how can I control PWM value in ESP node?

2)Than I did so:

############################################This is an output component and will not visible from the frontend    RELAys
output:
 
  - platform: esp8266_pwm
    pin: GPIO5
    frequency: 400 Hz
    id: pwm_rel1
    min_power: 0.0
    max_power: 0.85
    inverted: true

  - platform: esp8266_pwm
    pin: GPIO4
    frequency: 400 Hz
    id: pwm_rel2
    min_power: 0.0
    max_power: 0.85
    inverted: true


#####################         FRONTEND

light:    
  - platform: monochromatic
    id: "led1"
    name: Led1
    output: pwm_rel1
#    internal: true
    
  - platform: monochromatic
    id: "led2"
    name: Led2
    output: pwm_rel2   
#    internal: true 

switch:
  - platform: gpio
    name: "Boiler room"
    pin: 16
    id: rel1
    restore_mode: always off
    icon: mdi:lightbulb
    on_turn_on:
     - light.dim_relative: 
         id: led1
         relative_brightness: -70%
    on_turn_off:
     - light.dim_relative: 
         id: led1
         relative_brightness: 70%
         
  - platform: gpio
    name: "Fan G"
    pin: 12
    id: rel2
    restore_mode: always off
    icon: mdi:fan
    on_turn_on:
     - light.dim_relative: 
         id: led2
         relative_brightness: -70%
    on_turn_off:
     - light.dim_relative: 
         id: led2
         relative_brightness: 70%
    


binary_sensor:
  - platform: gpio
    #name: test in1
    #internal: true #Mark this component as internal. Internal components will not be exposed to the frontend (like Home Assistant). Only specifying an id without a name will implicitly set this to true.
    id: "in1"
    filters:
      - delayed_on: 10ms
      - delayed_off: 10ms
    pin:
      number: 14
      mode: INPUT_PULLUP
      inverted: true
    on_multi_click:
    - timing:
        - ON for at most 1s
        - OFF for at most 1s
        - ON for at most 1s
        - OFF for at least 0.2s
      then:
        - switch.toggle: rel2
        - logger.log: "Double click"

    - timing:
        - ON for 1s to 2s
        - OFF for at least 0.5s
      then:
        - logger.log: "Single Long Click"

    - timing:
        - ON for at most 1s
        - OFF for at least 0.5s
      then:
        - switch.toggle: rel1
        - logger.log: "Single Click"
        
  - platform: gpio
    id: "in2"
    filters:
      - delayed_on: 10ms
      - delayed_off: 10ms
    pin:
      number: 13
      mode: INPUT_PULLUP
      inverted: true

Yet, works like it should but I can’t still implement brightness adjustment based on Lux sensor values. Is there any possibility to adjust reference value (which will be for example Lux/10) and than add or subtract from it ±70% ?

I think it should be something around global variables, but still no luck. …

Posts: 3

Participants: 2

Read full topic

@DeeBeeKay wrote:

Hi all,

In my quest to improve presence and occupancy detection, I was thinking about a sensor device that can detect which direction a person is moving. Basically it’s two photoresistors spaced about 8cm apart on one side of a doorway, with either lasers or bright LEDs or something pointed directly at them from the other side.

When a person walks through the doorway, they break the beams in a particular order that indicates if they are entering or leaving the room. This would be super useful, because you can assume a room is occupied if someone walked into it but hasn’t left, even if there’s no motion (eg they sat down and read a book).

Now, I’ve mocked up a prototype on a breadboard, and it works quite well. To pass WAF I will need to 3D print a nice acetone-smoothed case and somehow come up with a method of mounting it in the doorframe that is not ugly.

However, I’m struggling with the code.

I can think of how I might code it up in the Arduino IDE. Far easier, I can think of how I’d do it in Node-RED. But I can’t for the life of me think how I’d do it in ESPHome, because to my knowledge, ESPHome doesn’t have the equivalent of a loop method.

The logic is something like this.

Wait for one of the sensors to change from ON to OFF. On state change, check to see if the other sensors changes state too, within about a second. If it does, report direction of travel. If it doesn’t, it’s either a false alarm or someone lurking in the doorway without actually going through, and we don’t need to report anything.

In the IDE I’d probably do it by having two methods called checkSensorOne() and checkSensorTwo(), basically identical but for the sensor names, and call the methods one after the other on loop. I could probably do the checking in a lambda, but I can’t think how I’d loop it.

Is there a way to do this in ESPhome? I really like the API integration, and otherwise I’ll have to do this with MQTT, which I have mostly forgotten. Can you point me at any code examples, even if they are for doing other things, that have a loop-style functionality in ESPHome?

Posts: 5

Participants: 4

Read full topic

@Stepan wrote:

I am staked with this camera.
The history of this camera starts with two versions (at least) and you can distinguish them for the microphone. All the pinout changes from one to another, this is the funny point!
So I tried to copy the ESPHOME.yaml for this camera changing the PINs and I dind’t get it to work.
Minutes later I started a search in google and I found this github issue where in brief they said that you should change the pins moreover add the these sentences to the main.cpp:

V1:

    pinMode(13, INPUT_PULLUP);
    pinMode(14, INPUT_PULLUP);
    pinMode(15, INPUT_PULLUP);

V2:

    pinMode(12, INPUT_PULLUP);
    pinMode(13, INPUT_PULLUP);
    pinMode(14, INPUT_PULLUP);
    pinMode(15, INPUT_PULLUP);

with this two modifications you should have your camera working almost in stability conditions.

So I tried everything, also changing the board from
esp-wrover-kit
to esp32dev as says in the official documentation

The only thing that I can do now is work with Arduino versions but I dont know if would work or maybe have no sense.

So here you have my cam.yaml

substitutions:
  devicename: ttgocam
  friendly_name: test esp32cam

esphome:
  name: $devicename
  platform: ESP32
  board: esp-wrover-kit #also tested esp32dev
  #arduino_version: 1.0.2 maybe play with this?

wifi:
  ssid: "FF"
  password: ""

# Enable logging
logger:

# Enable Home Assistant API
api:
  password: "t1234!"

ota:
  password: "t1234"

binary_sensor:
  - platform: gpio
    pin: GPIO19
    name: $friendly_name PIR
    device_class: motion

  - platform: gpio
    pin:
      number: GPIO00
      mode: INPUT_PULLUP
      inverted: True
    name: $friendly_name Button

  - platform: status
    name: $friendly_name Status

sensor:
  - platform: wifi_signal
    name: $friendly_name WiFi Signal
    update_interval: 10s
  - platform: uptime
    name: $friendly_name Uptime

esp32_camera:
  name: $friendly_name Camera
  external_clock:
    pin: GPIO04
    frequency: 20MHz
  i2c_pins:
    sda: GPIO13
    scl: GPIO12
  data_pins: [GPIO34, GPIO13, GPIO14, GPIO35, GPIO39, GPIO12, GPIO15, GPIO36]
  vsync_pin: GPIO05
  href_pin: GPIO27
  pixel_clock_pin: GPIO25
  #power_down_pin:  doesnt have
  max_framerate: 10 fps
  idle_framerate: 0.1 fps
  resolution: 640x480
  jpeg_quality: 10
  vertical_flip: true
  horizontal_mirror: false

i2c:
  sda: GPIO21
  scl: GPIO22

font:
  - file: "fonts/times-new-roman.ttf"
    id: tnr1
    size: 20
  - file: "fonts/times-new-roman.ttf"
    id: tnr2
    size: 35

time:
  - platform: homeassistant
    id: homeassistant_time

display:
  - platform: ssd1306_i2c
    model: "SSD1306 128x64"
    address: 0x3C
    lambda: |-
      it.strftime(64, 0, id(tnr1), TextAlign::TOP_CENTER,"%d-%m-%Y", id(homeassistant_time).now());
      it.strftime(64, 64, id(tnr2), TextAlign::BASELINE_CENTER, "%H:%M", id(homeassistant_time).now());

and with this configuration and V1 / V2 of the main.src and both board types I get the same error in the serial logger:

[12:00:22][E][esp32_camera:091]: Setup Failed: ERROR

and my loverlace yalm is:

    cards:
      - type: 'custom:camera-card'
        entity: camera.test_esp32cam_camera
        name: cameratest

The home assistant output:

101488×1120 53.9 KB

and in the UI

(I just can post one image)

Thanks! I hope to solve it!

Posts: 1

Participants: 1

Read full topic

@ajcooper72 wrote:

Just getting started with ESPHOME and I’ve managed to get a Wemos D1 running with a couple of LED’s that I can control from HA. However, I wanted to swap them over to a RGB LED similar to the following

I haven’t been able to find any examples other than setting up LED strips. I’ve configured switches so far for the standard LED’s similar to the following;

switch:
  - platform: gpio
    pin: D1
    name: "Playing VR"
  - platform: gpio
    pin: D2
    name: "Playing Game"    

This exposes two switches in HA which I can control.

Would appreciate if someone could give me some pointers on how to set up the RGB LED.

Thanks

Posts: 3

Participants: 2

Read full topic

@Rdoull wrote:

Hi all,

i’m looking to get the sonoff T4EU1C light switch for my house but I’d like to use it with ESPhome and was wondering if anyone has managed to do this?

thanks

Robin

Posts: 1

Participants: 1

Read full topic

@truglodite wrote:

Hi all, I have had an ms5611 baro sensor installed on a bare esp8266 setup for several years without issue. Probably doesn’t matter, but it was using mqtt to talk to ha. A couple days ago I decided to swap out my DIY firmware with esphome. All seemed to be going fine until yesterday, when I observed a sudden jump in pressure values. The pic below shows the problem:

temp864×1024 123 KB

The initial jump in the line was when I noticed the problem (~30hPa too high). I then used a template to bring it down to actual pressure (first step down). Then in the middle of the night it drops about 10hPa. This morning, I got rid of the template offset and started playing with i2c speeds, with no good result… pressure still reads ~30hPa too high. Severall reboots of the device didn’t work, and neither did trying to let the sensor cool off for 10min.

I suspect my ms5611 may be near it’s EOL, and it was just a coincidence it happened a day after switching to esphome. I figured I should ask here first, before I just go order a replacement sensor. Has anyone else seen this with i2c sensors on esphome? I have read about a possibility that the esp could be reading the PROM calibraiton incorrectly, but I doubt it since it seems to be working well otherwise (smooth curve changing properly relative to actual pressure).

[edit: Just now, it jumped up another 10hPa… reading almost 1060, actual is ~1020.]

Posts: 1

Participants: 1

Read full topic

@shanem wrote:

I just flashed my first Sonoff with ESP home and integrated it into Home Assistant and I could control it, but when I unplugged the usb ftdi converter and put my 12v 1amp power supply into the input, and nothing happens.

So i get a second one, flash it with the same image, nothing happens.

So i know I didn’t just get a defective one. I don’t want to try it on any more in case i just break them with my power supply. is it too much?

I don’t know much about electricity, is the power supply too much for the sonoff basic? I’ve seen many people looking for help online but they never get answered.

Please let me know if i did something wrong, thanks.

Posts: 3

Participants: 2

Read full topic

@Todilo wrote:

I am gathering all info to see what I need to make this happen. Is it possible to make a configuration where I can have like 1 lightgroup (or what is it called) for each step in my staircase? I was first considering a ws2812 but got the suggestion to go for the SK6812 to get white light possibility, does that work with HA and a nodemcu?

Posts: 3

Participants: 2

Read full topic

@fitim wrote:

Hey, guys…

I’m really new to ESPHome and all the Arduino Stuff. I tried to search in the web, but didn’t find any satisfying solution, so you are my last help.

Im trying to build a Lux Sensor with a BH1750. The most important thing is, that I can use it with a battery ( I already built a wired lux sensor with a sonoff basic). I found a few guides how to connect a BH1750 to a wemos d1 mini or other stuff, but nothing decent for battery usage. It looks like the main problem is that a demos d1 mini drains the battery to fast (also with deep sleep).

Do you have any ideas how to realize that? I could use Wifi or a RF-Bridge for connection.

Im really stuck atm, and appreciate any help!

Posts: 11

Participants: 4

Read full topic

@yuvalabou wrote:

Hi
I am having difficulties understanding the terminology of esphome template sensor.
i have this one and i am trying to move it from my hass sensors to the node itself.

this sensor takes the estimated advertized power usage and combine it with the uptime sensor to give me an estimation of the power used.

- platform: template
  sensors:
    shabat_plate_kwh:
      friendly_name: 'Shabat Plate Power consumption'
      entity_id: sensor.shabat_plate_power_time
      # Multiply total time 'on' by the 400w advertized power consumption of the plate
      value_template: "{{ states('sensor.shabat_plate_power_time')|float * 400 * 0.001 }} kW/h"
      device_class: power

Posts: 1

Participants: 1

Read full topic

@bpmittal wrote:

I have seen a video in which it shows that we can use our existing esp8266 or esp32 nodes as mesh network routers in repeater mode,

I want to ask esphome developers if it is possible to integrate this function with our existing esphome nodes ?

That will be very useful as we are using lots of nodes in our home and many routers are also being used saperately yet there are many area where there is low signal .

Posts: 1

Participants: 1

Read full topic

@hipsi wrote:

Hi all, I’ve converted a couple of tunable globes to ESPHome. I like the ability to set it to turn on when the physical power is turned off and then on again. Problem is by default they come on in Cool White mode, whereas I’d like them to come on in Warm White mode. I can’t find out how to set this specifically, but have managed to find a bit of a work around by using restore mode only on the gpio output used for Warm White.
The only problem here is that doing it this way doesn’t report it to Home Assistant because it doesn’t have a name.

Does anyone have any suggestions?

output:
  - platform: esp8266_pwm
    id: output_warm_white
    pin: GPIO12
  - platform: esp8266_pwm
    id: output_cold_white
    pin: GPIO14

light:
  - platform: cwww
    name: "Mirabella Genio Smart Bulb"
    id: light_1
    cold_white: output_cold_white
    warm_white: output_warm_white
    cold_white_color_temperature: 6500 K
    warm_white_color_temperature: 2700 K
  - platform: binary
    id: led_warm_white
    # Ensure the light turns on by default if the physical switch is actuated.
    restore_mode: ALWAYS_ON
    output: output_warm_white

Posts: 1

Participants: 1

Read full topic