@Capn_jimbo wrote:

Hi There ,

I have a D1 Mini connected to a Ultrasonic distance measurement in my oil tank to check my oil level. as the tank is at a distance from the house I need it to run on batteries.

I have a following yaml

esphome:
  name: test
  platform: ESP8266
  board: d1_mini

wifi:
  ssid: "XXXXXXX"
  password: "XXXXXXXXX"

mqtt:
  broker: 192.168.1.XX
  username: XX
  password: XX

# Enable logging
logger:

# Enable Home Assistant API
#api:
#  password: "1234"

ota:
  password: "1234"
  

binary_sensor:

  - platform: status
    name: US Status

sensor:
  - platform: ultrasonic
    trigger_pin: D1
    echo_pin: D2
    update_interval: 5s
    name: "Ultrasonic Sensor"
    id: us01

deep_sleep:
  run_duration: 40s
  sleep_duration: 60s

Log reads

[12:08:09][C][wifi:372]: WiFi:
[12:08:09][C][wifi:254]: SSID: [redacted]
[12:08:09][C][wifi:255]: IP Address: 192.168.1.11
[12:08:09][C][wifi:257]: BSSID: [redacted]
[12:08:09][C][wifi:258]: Hostname: ‘test’
[12:08:09][C][wifi:262]: Signal strength: -49 dB ▂▄▆█
[12:08:09][C][wifi:263]: Channel: 4
[12:08:09][C][wifi:264]: Subnet: 255.255.255.0
[12:08:09][C][wifi:265]: Gateway: 192.168.1.1
[12:08:09][C][wifi:266]: DNS1: 192.168.1.1
[12:08:09][C][wifi:267]: DNS2: 0.0.0.0
[12:08:09][C][logger:137]: Logger:
[12:08:09][C][logger:138]: Level: DEBUG
[12:08:09][C][logger:139]: Log Baud Rate: 115200
[12:08:09][C][logger:140]: Hardware UART: UART0
[12:08:09][C][status:034]: Status Binary Sensor ‘US Status’
[12:08:09][C][status:034]: Device Class: ‘connectivity’
[12:08:09][C][ultrasonic.sensor:035]: Ultrasonic Sensor ‘Ultrasonic Sensor’
[12:08:09][C][ultrasonic.sensor:035]: Unit of Measurement: ‘m’
[12:08:09][C][ultrasonic.sensor:035]: Accuracy Decimals: 2
[12:08:09][C][ultrasonic.sensor:035]: Icon: ‘mdi:arrow-expand-vertical’
[12:08:09][C][ultrasonic.sensor:036]: Echo Pin: GPIO4 (Mode: INPUT)
[12:08:09][C][ultrasonic.sensor:037]: Trigger Pin: GPIO5 (Mode: OUTPUT)
[12:08:09][C][ultrasonic.sensor:038]: Pulse time: 10 µs
[12:08:09][C][ultrasonic.sensor:039]: Timeout: 11661 µs
[12:08:09][C][ultrasonic.sensor:040]: Update Interval: 5.0s
[12:08:09][C][ota:029]: Over-The-Air Updates:
[12:08:09][C][ota:030]: Address: test.local:8266
[12:08:09][C][ota:032]: Using Password.
[12:08:09][C][mqtt:051]: MQTT:
[12:08:09][C][mqtt:053]: Server Address: 192.168.1.XX:1883 (192.168.1.XX)
[12:08:09][C][mqtt:054]: Username: [redacted]
[12:08:09][C][mqtt:055]: Client ID: [redacted]
[12:08:09][C][mqtt:057]: Discovery prefix: ‘homeassistant’
[12:08:09][C][mqtt:058]: Discovery retain: YES
[12:08:09][C][mqtt:060]: Topic Prefix: ‘test’
[12:08:09][C][mqtt:062]: Log Topic: ‘test/debug’
[12:08:09][C][mqtt:065]: Availability: ‘test/status’
[12:08:09][C][mqtt.binary_sensor:018]: MQTT Binary Sensor ‘US Status’:
[12:08:09][C][mqtt.binary_sensor:019]: State Topic: ‘test/status’
[12:08:09][C][mqtt.sensor:024]: MQTT Sensor ‘Ultrasonic Sensor’:
[12:08:09][C][mqtt.sensor:028]: State Topic: ‘test/sensor/ultrasonic_sensor/state’
[12:08:09][C][deep_sleep:020]: Setting up Deep Sleep…
[12:08:09][C][deep_sleep:023]: Sleep Duration: 60000 ms
[12:08:09][C][deep_sleep:026]: Run Duration: 40000 ms
[12:08:11][D][sensor:092]: ‘Ultrasonic Sensor’: Sending state 0.04768 m with 2 decimals of accuracy
[12:08:11][D][ultrasonic.sensor:030]: ‘Ultrasonic Sensor’ - Got distance: 0.05 m
[12:08:11][D][sensor:092]: ‘Ultrasonic Sensor’: Sending state 0.04768 m with 2 decimals of accuracy
[12:08:16][D][sensor:092]: ‘Ultrasonic Sensor’: Sending state 0.04305 m with 2 decimals of accuracy
[12:08:16][D][ultrasonic.sensor:030]: ‘Ultrasonic Sensor’ - Got distance: 0.04 m
[12:08:16][D][sensor:092]: ‘Ultrasonic Sensor’: Sending state 0.04305 m with 2 decimals of accuracy
[12:08:21][D][sensor:092]: ‘Ultrasonic Sensor’: Sending state 0.04305 m with 2 decimals of accuracy
[12:08:21][D][ultrasonic.sensor:030]: ‘Ultrasonic Sensor’ - Got distance: 0.04 m
[12:08:21][D][sensor:092]: ‘Ultrasonic Sensor’: Sending state 0.04305 m with 2 decimals of accuracy
[12:08:26][D][sensor:092]: ‘Ultrasonic Sensor’: Sending state 0.04270 m with 2 decimals of accuracy
[12:08:26][D][ultrasonic.sensor:030]: ‘Ultrasonic Sensor’ - Got distance: 0.04 m
[12:08:26][D][sensor:092]: ‘Ultrasonic Sensor’: Sending state 0.04270 m with 2 decimals of accuracy
[12:08:31][D][sensor:092]: ‘Ultrasonic Sensor’: Sending state 0.04305 m with 2 decimals of accuracy
[12:08:31][D][ultrasonic.sensor:030]: ‘Ultrasonic Sensor’ - Got distance: 0.04 m
[12:08:31][D][sensor:092]: ‘Ultrasonic Sensor’: Sending state 0.04305 m with 2 decimals of accuracy
[12:08:36][D][sensor:092]: ‘Ultrasonic Sensor’: Sending state 0.04305 m with 2 decimals of accuracy
[12:08:36][D][ultrasonic.sensor:030]: ‘Ultrasonic Sensor’ - Got distance: 0.04 m
[12:08:36][D][sensor:092]: ‘Ultrasonic Sensor’: Sending state 0.04305 m with 2 decimals of accuracy
[12:08:41][D][sensor:092]: ‘Ultrasonic Sensor’: Sending state 0.04305 m with 2 decimals of accuracy
[12:08:41][D][ultrasonic.sensor:030]: ‘Ultrasonic Sensor’ - Got distance: 0.04 m
[12:08:41][D][sensor:092]: ‘Ultrasonic Sensor’: Sending state 0.04305 m with 2 decimals of accuracy
[12:08:46][D][sensor:092]: ‘Ultrasonic Sensor’: Sending state 0.04305 m with 2 decimals of accuracy
[12:08:46][D][ultrasonic.sensor:030]: ‘Ultrasonic Sensor’ - Got distance: 0.04 m
[12:08:46][D][sensor:092]: ‘Ultrasonic Sensor’: Sending state 0.04305 m with 2 decimals of accuracy
[12:08:49][I][deep_sleep:067]: Beginning Deep Sleep

problem is that after entering Deep sleep it does not wake up

D1 mini RST is connected to GPIO16

anything I am not getting right ???

Thank you in advance

Posts: 2

Participants: 2

Read full topic

@rickbell wrote:

Show me the code for a SH1106 OLED Display in ESPHome

Posts: 5

Participants: 5

Read full topic

@bednim wrote:

hey guys,
ive set up my esp32 board to do quite a lot (?) of things - measure temp, ultrasonic sensor, 4 relay switch board and 3 buttons. so the sensors are working fine, but im having problems with random relay switch tiggered by button that is not even touched at all (even changed). please, could you check my config?

im not using any physical resistors, just enabled pulldown in config.

switches were connected to GND + GPIO and then later changed to 3v3 + GPIO.
relays are connected to 5V + GND. tried them with 3v3 but made no difference.
sensors are 5v and works fine.

please - if youve got any ideas - please comment below

Thank you!

esphome:
  name: garaz_barak_esp32
  platform: ESP32
  board: esp-wrover-kit

wifi:
  ssid: "wifi"
  password: "pass"
  reboot_timeout: 0s
  manual_ip:
    static_ip: 192.168.1.119
    gateway: 192.168.1.1
    subnet: 255.255.255.0  
# Enable logging
logger:

# Enable Home Assistant API
api:
 reboot_timeout: 0s

sun:
  latitude: 50.6
  longitude: 17.8

# At least one time source is required
time:
  - platform: homeassistant
  
  
ota:


switch:
  - platform: gpio
    name: "wolny_relay"
    pin: 
      number: GPIO27

    id: wolny_relay
    inverted: yes
    restore_mode: RESTORE_DEFAULT_OFF 

    
  - platform: gpio
    name: "gniazdo_lewe"
    pin: 
      number: GPIO26
  
    id: gniazdo_lewe
    inverted: yes
    restore_mode: RESTORE_DEFAULT_OFF 

  - platform: gpio
    name: "gniazdo_prawe"
    pin: 
      number: GPIO33
  
    id: gniazdo_prawe
    inverted: yes
    restore_mode: RESTORE_DEFAULT_OFF
  - platform: gpio
    name: "garaz_swiatlo"
    pin: 
      number: GPIO25
    id: swiatlo
    inverted: yes
    restore_mode: RESTORE_DEFAULT_OFF  
    
binary_sensor:
  - platform: gpio
    pin:
      number: GPIO15
      mode: INPUT_PULLDOWN
    name: "GUZIK"
    on_press:
      then:
      - switch.toggle: swiatlo

     
  - platform: gpio
    pin:
      number: 22
      mode: INPUT_PULLDOWN 
      inverted: true
    name: "drzwi_garaz"
    device_class: garage_door
    on_press:
    - if:
         condition:
          - sun.is_below_horizon:
         then:
           - switch.turn_on: swiatlo
           - delay: 180s  
           - switch.turn_off: swiatlo
    on_release:
      then:
      - switch.turn_off: swiatlo


  - platform: gpio
    pin:
      number: GPIO34
      mode: INPUT_PULLDOWN 
      inverted: true
    name: "szopa_drzwi"
    device_class: door



        
sensor:



  - platform: ultrasonic
    trigger_pin: 19
    echo_pin: 21
    name: "garaz_ultrasonic_sensor"
    update_interval: 5s
    pulse_time: 2s
    filters:
      - filter_out: nan

  - platform: dht
    model: DHT22
    pin: GPIO23
    temperature:
      name: "Garage Temperature"
    humidity:
      name: "Garage Humidity"
    update_interval: 60s

Posts: 13

Participants: 3

Read full topic

@depen wrote:

Anyone using Esphome on Blitzwolf SHP5 who could share the config?

Posts: 2

Participants: 2

Read full topic

@ohj wrote:

I’ve got an ESP8266 that monitors the state of my garage door. I’d like the ESP8266 to check the pin state on a regular interval (e.g. every hour or something) and send its value. I see that the binary_sensor earlier had a heartbeat filter that I believe did this. Right? But it was removed not too long ago? Why was this? And how can I then achieve the wanted behavior?

Posts: 1

Participants: 1

Read full topic

@fnts wrote:

Hi,
I am using LEDs connected to ESPHome NodeMCU 8266 to indicate Arm (Red) & Disarm (Green) state of my manual alarm. The issue is that the LEDs randomly become unavailable and goes off. Logbook:

7:54 AM [Red LED] turned off
7:54 AM [Green LED] turned off
7:54 AM [Red LED] changed to unavailable
7:54 AM [Green LED] changed to unavailable
7:27 AM [Red LED] turned off
7:27 AM [Green LED] turned off
7:27 AM [Red LED] changed to unavailable
7:27 AM [Green LED] changed to unavailable

Below is the configuration file (.yaml)
. . .
esphome:
name: hallway
platform: ESP8266
board: nodemcuv2

wifi:
ssid: “my_ssid”
password: “my_password”
fast_connect: true
manual_ip:
static_ip: 192.168.1.151
gateway: 192.168.1.1
subnet: 255.255.255.0
dns1: 192.168.1.1

output:

• platform: gpio
  pin: D1
  id: ‘red_led’
• platform: gpio
  pin: D2
  id: ‘green_led’

light :

• platform: binary
  name: “Red LED”
  output: ‘red_led’
  restore_mode: ALWAYS_OFF
• platform: binary
  name: “Green LED”
  output: ‘green_led’
  restore_mode: ALWAYS_OFF
  . . .
  Any advise what’s going wrong here. I am using Call Service (through Node-Red) to switch LEDs on/off.

Thanks,

Posts: 7

Participants: 3

Read full topic

@Rdoull wrote:

hi,

i’m looking for some help.

I’ve got a ESP32 NodeMCU development board and I’m trying to set up a light sensor using the TEMT6000 ground is set to ground, V is set to 3v and data is to p32

the readings i am getting are

[21:31:22][D][adc:056]: 'Testing Brightness': Got voltage=0.53V
[21:31:22][D][sensor:092]: 'Testing Brightness': Sending state 105.46032 lux with 2 decimals of accuracy
[21:31:23][D][adc:056]: 'Testing Brightness': Got voltage=0.81V
[21:31:23][D][sensor:092]: 'Testing Brightness': Sending state 162.19292 lux with 2 decimals of accuracy
[21:31:24][D][adc:056]: 'Testing Brightness': Got voltage=0.14V
[21:31:24][D][sensor:092]: 'Testing Brightness': Sending state 28.84982 lux with 2 decimals of accuracy
[21:31:24][D][sensor:092]: 'Testing uptime do not use': Sending state 39.75800 s with 0 decimals of accuracy
[21:31:24][D][text_sensor:015]: 'Testing Uptime': Sending state '0d 00h 00m 39s'
[21:31:25][D][adc:056]: 'Testing Brightness': Got voltage=0.00V
[21:31:25][D][sensor:092]: 'Testing Brightness': Sending state 0.00000 lux with 2 decimals of accuracy
[21:31:26][D][adc:056]: 'Testing Brightness': Got voltage=0.11V
[21:31:26][D][sensor:092]: 'Testing Brightness': Sending state 21.81197 lux with 2 decimals of accuracy
[21:31:27][D][adc:056]: 'Testing Brightness': Got voltage=0.80V
[21:31:27][D][sensor:092]: 'Testing Brightness': Sending state 159.02321 lux with 2 decimals of accuracy
[21:31:28][D][adc:056]: 'Testing Brightness': Got voltage=0.62V
[21:31:28][D][sensor:092]: 'Testing Brightness': Sending state 124.63981 lux with 2 decimals of accuracy
[21:31:29][D][adc:056]: 'Testing Brightness': Got voltage=0.20V
[21:31:29][D][sensor:092]: 'Testing Brightness': Sending state 40.40049 lux with 2 decimals of accuracy
[21:31:30][D][adc:056]: 'Testing Brightness': Got voltage=0.74V
[21:31:30][D][sensor:092]: 'Testing Brightness': Sending state 147.25764 lux with 2 decimals of accuracy
[21:31:31][D][adc:056]: 'Testing Brightness': Got voltage=0.42V
[21:31:31][D][sensor:092]: 'Testing Brightness': Sending state 84.18559 lux with 2 decimals of accuracy
[21:31:32][D][adc:056]: 'Testing Brightness': Got voltage=0.00V
[21:31:32][D][sensor:092]: 'Testing Brightness': Sending state 0.00000 lux with 2 decimals of accuracy
[21:31:33][D][adc:056]: 'Testing Brightness': Got voltage=0.81V
[21:31:33][D][sensor:092]: 'Testing Brightness': Sending state 162.51527 lux with 2 decimals of accuracy
[21:31:34][D][adc:056]: 'Testing Brightness': Got voltage=0.66V
[21:31:34][D][sensor:092]: 'Testing Brightness': Sending state 132.96704 lux with 2 decimals of accuracy
[21:31:35][D][adc:056]: 'Testing Brightness': Got voltage=0.36V
[21:31:35][D][sensor:092]: 'Testing Brightness': Sending state 71.07693 lux with 2 decimals of accuracy
[21:31:36][D][adc:056]: 'Testing Brightness': Got voltage=0.00V
[21:31:36][D][sensor:092]: 'Testing Brightness': Sending state 0.00000 lux with 2 decimals of accuracy
[21:31:37][D][adc:056]: 'Testing Brightness': Got voltage=0.30V
[21:31:37][D][sensor:092]: 'Testing Brightness': Sending state 60.17094 lux with 2 decimals of accuracy
[21:31:38][D][adc:056]: 'Testing Brightness': Got voltage=0.51V
[21:31:38][D][sensor:092]: 'Testing Brightness': Sending state 102.66666 lux with 2 decimals of accuracy
[21:31:39][D][adc:056]: 'Testing Brightness': Got voltage=0.06V
[21:31:39][D][sensor:092]: 'Testing Brightness': Sending state 12.35653 lux with 2 decimals of accuracy
[21:31:39][D][sensor:092]: 'Testing uptime do not use': Sending state 54.76800 s with 0 decimals of accuracy
[21:31:39][D][text_sensor:015]: 'Testing Uptime': Sending state '0d 00h 00m 54s'
[21:31:40][D][adc:056]: 'Testing Brightness': Got voltage=0.00V
[21:31:40][D][sensor:092]: 'Testing Brightness': Sending state 0.00000 lux with 2 decimals of accuracy
[21:31:41][D][adc:056]: 'Testing Brightness': Got voltage=0.24V
[21:31:41][D][sensor:092]: 'Testing Brightness': Sending state 48.62027 lux with 2 decimals of accuracy
[21:31:42][D][adc:056]: 'Testing Brightness': Got voltage=0.79V
[21:31:42][D][sensor:092]: 'Testing Brightness': Sending state 158.64713 lux with 2 decimals of accuracy

in this instance the sensor was in a dimly lit room, but I get similar readings if I put the sensor in a box void of any light or under a lamp and pointing directly at the sensor.

this is my yaml in total

esphome:
  name: testing
  platform: ESP32
  board: esp-wrover-kit

wifi:
  networks:
  - ssid: !secret ssid
    password: !secret wifi_password
  - ssid: !secret sky-ssid
    password: !secret sky-password
  manual_ip:
    static_ip: 192.168.0.41
    gateway: 192.168.0.1
    subnet: 255.255.255.0
    dns1: 192.168.0.1
    dns2: 192.168.0.1

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:

# Enable Web server.
#web_server:
#  port: 80
  
sensor:
  - platform: adc
    pin: GPIO32
    name: "Testing Brightness"
    update_interval: 1s
    attenuation: 11db
    unit_of_measurement: lux
    filters:
      - lambda: |-
          return (x / 10000.0) * 2000000.0;
  - platform: wifi_signal
    name: "Testing WiFi signal"
    update_interval: 300s

  - platform: uptime
    name: "Testing uptime do not use"
    id: testing_uptime
    update_interval: 15s

text_sensor:
  - platform: version
    name: "Testing ESPHome version"
    
  - platform: template
    name: "Testing Uptime"
    lambda: |-
      uint32_t dur = id(testing_uptime).state;
      int dys = 0;
      int hrs = 0;
      int mnts = 0;
      if (dur > 86399) {
        dys = trunc(dur / 86400);
        dur = dur - (dys * 86400);
      }
      if (dur > 3599) {
        hrs = trunc(dur / 3600);
        dur = dur - (hrs * 3600);
      }
      if (dur > 59) {
        mnts = trunc(dur / 60);
        dur = dur - (mnts * 60);
      }
      char buffer[17];
      sprintf(buffer, "%ud %02uh %02um %02us", dys, hrs, mnts, dur);
      return {buffer};
    icon: mdi:clock-start
    update_interval: 15s

switch:
  - platform: restart
    name: Testing Restart

all help appreciated thank you

Posts: 25

Participants: 2

Read full topic

@shalamakooky wrote:

I’m having trouble getting my Sonoff Basic LED to turn on/off with the relay. I can turn the relay on/off and the LED on/off. What I want is for the LED to turn on when the relay is switched on, and off when the relay is switched off.
My sonoff config:

switch:
  - platform: gpio
    name: "Sonoff 1 Relay"
    pin: GPIO12
    id: relay
  - platform: template
    name: "Sonoff 1 relay"
    optimistic: true
    id: relayandled
    turn_on_action:
    - switch.turn_on: relay
    - light.turn_on: led
    turn_off_action:
    - switch.turn_off: relay
    - light.turn_off: led      
    
output:
  - platform: esp8266_pwm
    id: sonoff_1_led
    pin:
      number: GPIO13
      inverted: True

light:
  - platform: monochromatic 
    name: "Sonoff 1 Green LED"
    output: sonoff_1_led
    id: led

Posts: 4

Participants: 2

Read full topic

@helgemor wrote:

Has anyone found a way to make esphome/esp32’s connect actively to the mi flora plant sensors?
I have a lot of sensors, and several esp32’s to read from them because they’re far apart.
Some of the esp32’s run on batteries, and as usual, they just listen passively to the readings.
Because of this, I have to keep the esp32’s powered for long periods of time, or have some automation on the HA or esp32 side counting measurements until I have all that I need.
What I need is an active esp32 based reader, so that I can wake it up every 6 hours, collect readings from it’s sensors, and then go back to sleep.

Posts: 1

Participants: 1

Read full topic

@laca75tn wrote:

I have my bathroom fans connected with sonoffs and DHTs and they turn on/off automatically based on the humidity. Everything works great. However, some times the fans turn on in the middle of the night and that gets annoying. I am trying to find an automation that restricts the fan turning on by time. How can I add a time condition where the fan only turns on between 7 am and 10 pm?

Any help would be appreciated. Thanks,

  - platform: dht
    pin: GPIO3 
    model: DHT11
    temperature:
      name: "${devicename} Temperature"
      #id: ${devicename}_temperature
    humidity:
      name: "${devicename} Humidity"
      #id: ${devicename}_humidity
      on_value_range:
       - above: 66.0
          then:
            - switch.turn_on: switch_relay
        - below: 65.0
          then:
            - switch.turn_off: switch_relay
    update_interval: 60s

Posts: 5

Participants: 2

Read full topic

@TheCosmicGate wrote:

At the moment i’am running ESPHome on a WeMos D1 , with a connected NPN inductive sensor .
This sensor read’s the pulse on the Elster water meter .
I think al few others ( Dutch guys) running the same config , coud you help me sharing you’re sensor’s / config ?
I would be nice to read out this : current L used , L(iters) used today, and probably L/hour (flow).
At the moment i only get this last sensor running, using this in de yaml:

sensor:
  - platform: pulse_counter
    name: "waterverbruik L/hr"
    pin: GPIO4
    update_interval: 30s
    filters:
    - lambda: return (x / 27.0) * 60.0;
    unit_of_measurement: "L/hr"

Posts: 2

Participants: 2

Read full topic

@prankousky wrote:

Hi everybody,

is it possible for me to use ESPHome Dashboard and/or manually flash ESPHome to a device from my regular computer, but then have it show up in ESPHome Dashboard on my home server (running Home Assistant in a docker container)? If so, can you please tell me how to do this?

Thing is, each nodeMCU, ESP8266, etc. device shows up as a different device under /dev/serial/by-id (obviously!). I cannot just use /dev/ttyUSB0 or similar, as this is used by a CC2531 zigbee router and when I reboot, sometimes those devices get messed up (so neither zigbee2mqtt nor ESPHome Dashboard will work).

If I could initially set up any new ESPHome device from my regular pc, then upload changes etc. via ESPHome Dashboard from within Home Assistant (I have it running on that same machine and linked it as a custom panel), it would be the easiest way and definitely the best way to avoid any problems with linking devices to docker containers.

Thank you for your ideas

Posts: 2

Participants: 2

Read full topic

@tamino wrote:

Hi…

I’ve got a strange problem.

I have two ESP8266 for testing on a breadboard, a Wemos D1 Mini and a NodeMCU.
A cuple of days ago I put together a NodeMCU (1 DHT22 for indoor temp, and one Dallas 18B20 for outside temp) for my living room. First i put everything together on the breadboard to get the dallas ID, and see that it worked. No problems.

Then I took the config and copy / pasted it to the new “live” one. But the names where wrong, so i changed them after I’ve added it to integrations in HA.

The indoor temp / hygrometer works fine, but the outside temp dosent work in HA. When i upload a new firmware i get the temp from the sensor, with the new name.
When i go to Configuration - Integrations - Livingroom ESP i see the sensors, but the Outside temp has the old name, and won’t recieve the temp.

image.png364×619 17.4 KB

I’ve tried to upload new firmware to the NodeMCU, tried cliean build, tried restarting the HA-server.
Any ideas?

Thanks…

Posts: 5

Participants: 3

Read full topic

@zahk wrote:

hey
Wemos d1 mini pro is really nice looking PCB.

Is that possible to use it with esphome? Like nodemcu for example?

thank you

Posts: 5

Participants: 2

Read full topic

@nickrout wrote:

Thank you @ottowinter and all the contributors.

Posts: 11

Participants: 8

Read full topic

@raul wrote:

I was flashing an new smart plug, but something went wrong when migrating from tasmota.

The new fallback hotspot is showing up as a wifi network, but I can also see the device connected to my router.

The wifi hotspot is secured, and I have no idea what the password would be (deleted yaml to reconfigure another plug). It is lists the ESPhome name in the ssid - ESPhome Switch Fallback Hotspot

The weirder thing is I can still see the device listed as a client on my router. The IP is inaccessible and it is still named ‘sonoff-4761’ leftover from the tasmota config.

Is there a default password for the captive portal? If not is there a way to reset the switch or reflash it OTA? I jut about destroyed one of these plugs trying to open it when I was having tuya-convert issues so I would prefer not having to crack it open.

Posts: 4

Participants: 4

Read full topic

@arc2v wrote:

Hi all,
I recently updated Hassio and ESPhome to the latest versions and since then none of my ESP sensors are showing up in HA.

ESPHome shows the devices and I can see them updating values and states, but on HA the status is always unavailable for both binary and temp/humidity.

I recompiled and rebooted and still nothing. I have not tried reverting yet since I’d like to keep everything up to date if I can.

Thanks.

Posts: 6

Participants: 2

Read full topic

@fribse wrote:

So I did the update to ESP 1.14.
After doing that, almost all esphome devices are shown as offline.
They still react in Home Assistant, but is shown as offline in ESPHome.
They are all configured as dynamic IP.

I’ve started converting them to static IP, and with a static IP they are all online (I can still do OTA via esphome in HA)

Posts: 4

Participants: 2

Read full topic

@dariusz wrote:

How I can change in ‘.yaml’ of ESPHome ‘network’ device name?
In my case it is shown on the ‘router’ as ‘ESP_E2A8B3’ and I would like to change that name to more friendly name…
Is that any ‘ESPHome’ ‘configuration variable’ to do that…?

ESPHome device name.png755×70 2.68 KB

Posts: 2

Participants: 2

Read full topic

@Piwek wrote:

Is it possible to get similar effect on esphome?

Posts: 3

Participants: 2

Read full topic