@tbuyvoets wrote:

I want to connect my lsc pir sensor to homeassistant. I have flashed it with a temporary configuration via tuya-convert. This was succesful.

Does anobody know what the pin is where the pir is connected? Or does anybody has an sample configuration yaml?

Thanks for helping me out.

Kind regards,
Tom

Posts: 2

Participants: 2

Read full topic

@enghult wrote:

Hello!
I have a Sonoff Basic R2 with a AM 312 motion sensor and my goal is to let the motion sensor turn on the switch for 5 minutes as long as there is motion detected,
So if motion is detetcted after 3 minutes, it should keep the switch on for another 5 minutes,

This is my current code:

esphome:
  name: sonoffbasic5
  platform: ESP8266
  board: esp01_1m

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

# Enable logging
logger:

# Enable Home Assistant API
api:
  password: !secret http_password

ota:
  password: !secret http_password

binary_sensor:
  - platform: gpio
    pin: GPIO3
    name: "PIR Sensor sbasic5"
    id: pirsbasic5
    device_class: motion
    on_press:
      then:
       - switch.turn_on: relay
       - delay: 300s
       - swith.turn_off: relay

switch:
  - platform: gpio
    name: "sbasic5"
    pin: GPIO12
    id: relay


status_led:
  pin:
    number: GPIO13
    inverted: yes

It only works the first 5 minutes.

Do I need somehing like this?

#  - platform: template
#    lambda: 'return id(pirsbasic5).state;'
#    filters:
#      - delayed_off: 5min
#    on_release:
#      then:
#        - switch.turn_off: relay

Posts: 1

Participants: 1

Read full topic

@ageurtse wrote:

Someone manage to control one of these from within ESPHOME, if so please share config file.

https://templates.blakadder.com/moes-MS-104B.html

Posts: 2

Participants: 2

Read full topic

@DrakeColdwinter wrote:

I’m having troubles using wemos d1 mini with OLED Shield and BME280.

My yaml:
#i2c bus definitions
i2c:

• id: bus_a
  sda: D1
  scl: D2
  scan: True
• id: bus_b
  sda: D3
  scl: D4
  scan: True

Example configuration entry

sensor:

• platform: bme280
  i2c_id: bus_b
  temperature:
  id: temp
  name: “BME280 Temperature”
  oversampling: 16x
  pressure:
  id: pres
  name: “BME280 Pressure”
  humidity:
  id: hum
  name: “BME280 Humidity”
  address: 0x76
  update_interval: 60s

Example configuration entry

display:

• platform: ssd1306_i2c
  i2c_id: bus_a
  model: “SSD1306 64x48”
  address: 0x3C
  lambda: |-
  it.printf(0, 5, id(font1), “Temp : %.1fc”, id(temp).state);
  it.printf(0, 20, id(font1), "Humi : %.1f ", id(hum).state);
  it.printf(0, 35, id(font1), "Pres : %.1f ", id(pres).state);

The trouble I’m having is that it would seem it only detects the last i2c bus. If I use the config up here, Then the bme280 works but not the screen. If I do this:

i2c:

• id: bus_b
  sda: D3
  scl: D4
  scan: True
• id: bus_a
  sda: D1
  scl: D2
  scan: True

Then the screen will work but not the BME280…

Posts: 4

Participants: 3

Read full topic

@dansharpy wrote:

Hi, I’m fairly new to HA and very new to esphome and development boards! Firstly I’ll explain what I’m trying to create (apologies if this is something very simple!) I want a Reed switch on the back door which is connected to a nodemcu v3 board which is powered by batteries. When the door is open it shows as ‘open’ in HA and when it’s closed it shows as ‘closed’ in HA so I can create automations based off the state. I don’t need the battery level or anything else reported as I’ve got an automation set up to alert me if the sensor is unavailable (IE batteries are dead so need to be changed!)

So far I’ve got everything wired up so it runs fine but only lasts about 24hours on the battery (18650) eventually I’ll wire up a 2 cell battery holder in parallel so it’ll last even longer but I think I need to venture into the world of deep sleep!

From what I’ve read I need to connect the rst pin to the switch wiring so when the door opens the rst pin goes low and resets the board. I’m fine with the wiring side of things but the coding I’m all a bit confused with!

Can anyone help please?
Thanks in advance!

Posts: 4

Participants: 2

Read full topic

@Brett_C wrote:

Hi all,

After running HA in a venv for the past few years, I’m in the process of moving to a docker install. Got everything up and running with a notable exception of esphome. I already had esphome devices setup via the integration, but after starting the HA docker container, I’m getting the error message below. Not sure what I’m missing or why the built in integration would have issues installing itself?

ImportError: Error loading shared library ld-linux-x86-64.so.2: No such file or directory (needed by /config/deps/lib/python3.7/site-packages/google/protobuf/pyext/_message.cpython-37m-x86_64-linux-gnu.so)

Thanks for any help!

Posts: 1

Participants: 1

Read full topic

@mrrodge wrote:

Looking to trigger an automation to so something (inside ESP, not a HA automation) when wifi connection is lost. I’ve seen the wifi signal sensor, but what’s the value I’m looking for when signal is gone?

Thanks!

Posts: 1

Participants: 1

Read full topic

@kasparsv wrote:

Hello!

I’m using substitutions in esphome such as follows:

substitutions:
  project: "My reactor"
  temp_cutoff: "38"

Is there a way to access the value temp_cutoff in lambda code? id(temp_cutoff).state does not work. Any ideas?

Posts: 1

Participants: 1

Read full topic

@weado wrote:

Hello,

I’m beginning on ESPHOME, no on HA and I would like to use my SDS011 with ESPHOME.

After installed my ESPHOME on docker, I create a new device (based on Nodemcu) and I completed my config file for the SDS011 (as you see below), compile and flash my nodemcu with the bin file. But when I add my esphome on HA, the state through from available to unknow but my nodemcu is correctly connect and I don’t understand why it doesn’t work. Could you help me ?
For information, I listen the SDS011 fan work each 5 minutes and I don’t have more information on my log and I tried to invert my pin (D7 and D8 to try) and it’s the same with D6 and D7 (with change the config file and upload of course)

esphome:
  name: sds011
  platform: ESP8266
  board: nodemcuv2

wifi:
  ssid: "Wifi"
  password: "password"
  manual_ip:
    static_ip: 192.168.1.76
    gateway: 192.168.1.1
    subnet: 255.255.255.0

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:

# Example configuration entry
uart:
  rx_pin: D8
  tx_pin: D7
  baud_rate: 9600

sensor:
  - platform: sds011
    pm_2_5:
      name: "Part. 2.5"
    pm_10_0:
      name: "Part. 10"
    update_interval: 5min

image904×147 14 KB

Posts: 2

Participants: 1

Read full topic

@DOttJr wrote:

(topic withdrawn by author, will be automatically deleted in 24 hours unless flagged)

Posts: 1

Participants: 1

Read full topic

@Ilmisu wrote:

Hi all,

I ahve a problem with the xiaomi temperature and humidity BLE sensor from xiaomi.
I’ve done all esphome configuration and upload into a ESP32 controller, this by logs finds and send infos about temperature, humidity and battery from the sensor in hassio, but hassio itself does not update values on frontend accordingly to what EspHome sends to him.
any helps? thanks a lot.

Stefano.

Posts: 1

Participants: 1

Read full topic

@sathish wrote:

Hello,
I’m trying to create a switch board with 4 relays and momentary switches. But after configuration, 2 relays are working but 2 relays are not turning on but their light indicators are turning on. Is it a voltage issue? or circuit issue? I’m using a d1mini connected to 5V 4 channel relay board powered by Hi-Link power supply 5V-0.6A (3 watts).

my ESPhome yaml,

esphome:
  name: bathroom
  platform: ESP8266
  board: d1_mini

wifi:
  ssid: "xx"
  password: "xx"
  fast_connect: true
  # Optional manual IP
  manual_ip:
    static_ip: 192.xxx.xx.xx
    gateway: 192.xxx.xx.x
    subnet: 255.xxx.xxx.x
  ap:
    ssid: "xx"
    password: "xx"

captive_portal:

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:

web_server:

# Relays
switch:
  - platform: gpio
    name: "Bathroom Light"
    icon: 'mdi:lightbulb'
    id: relay1
    pin:
      number: D1
      # One of INPUT, INPUT_PULLUP or OUTPUT
      mode: OUTPUT
      inverted: True

  - platform: gpio
    name: "Bathroom Exhaust Fan"
    icon: 'mdi:fan'
    id: relay2
    pin:
      number: D2
      mode: OUTPUT
      inverted: True

  - platform: gpio
    name: "Bathroom Boiler"
    icon: 'mdi:water-boiler'
    restore_mode: RESTORE_DEFAULT_OFF
    id: relay4
    pin:
      number: D4
      mode: OUTPUT
      inverted: True

  - platform: restart
    name: "Bathroom Panel REBOOT"

# Switches
binary_sensor:
  - platform: gpio
    pin:
      number: TX
      mode: INPUT_PULLUP
      inverted: True
    name: "Bathroom Light"
    on_press:
      - switch.toggle: relay1
    internal: True
  - platform: gpio
    pin:
      number: RX
      mode: INPUT_PULLUP
      inverted: True
    name: "Bathroom Exhaust Fan"
    on_press:
      - switch.toggle: relay2
    internal: True
  - platform: gpio
    pin:
      number: D7
      mode: INPUT_PULLUP
      inverted: True
    name: "Bathroom Boiler"
    on_press:
      - switch.toggle: relay4
    internal: True

I’ve tested wit 4 channel, relay 3 is working. But as I don’t need 4 relays, only need 3, I’m trying to resolve the issue that happened to those 2 relays not working.

Posts: 10

Participants: 2

Read full topic

@truxntrax wrote:

I have a nodemuc v3, with a couple of binary sensors. Whichever binary sensor I put second in my YAML file doesn’t have a state associated with it? Any ideas what I’m doing wrong? If I change the order of the binary_sensor in the yaml file then the (new) first sensor has a state, but the (new) second sensor does not.

Here is an extract from my yaml:

binary_sensor:
  - platform: gpio
    name: "Alarm siren and strobe"
    pin:
      number: 12
      inverted: True
  - platform: gpio
    name: "Alarm Set Status"
    pin: D0

Screenshot from 2020-02-20 13-58-12389×508 33.4 KB

Any help is much appreciated!

John

Posts: 1

Participants: 1

Read full topic

@fribse wrote:

I have this is my config:

  on_boot:
    then:
      - switch.turn_on: relay

On quite a few items, but this causes the relay to ‘flick’ off/on when it reboots. As it keeps rebooting if I work on the network, and the wifi is gone, it will make this flicker every few minuttes.

I would very much like to keep the possibility to have the items ‘always on’ after a boot, but at the same time I don’t want them to do the flick, as at some point some switchmode psu are going to die from this.

So is there a way to modify the ‘on_boot’ so that it only turns the relay on, if it’s off?

Posts: 4

Participants: 3

Read full topic

@integray182 wrote:

Hi all,

Earlier today I flashed one of my two ESP8266 plugs with ESPhome successfully. I loaded Tasmota on the second one, and after playing around with it, wanted to put ESPhome on that one as well. In my excitement, I accidentally flashed the second plug with the same .bin file as the first plug, so now it’s basically showing up as two different devices with the same name. I flashed both via the OTA method and tuya-convert, so is there a way to “start fresh” on the second plug without the use of an FTDI adapter/serial connection? Or somehow flash the second plug with another bin?

Posts: 3

Participants: 3

Read full topic

@thebogeyman wrote:

Hi there,

I just started with Tasmota and ESPHome. I have a power plug that I flashed with Tasmota using TuyaConvert, configured with this template: https://templates.blakadder.com/aisirer_AWP07L.html

It’s working great, but I tried to experiment a bit with ESPHome, so I wanted to convert the above template to a YAML for ESPHome and I was asking myself some questions:

1. Is there a similar database for ESPHome configurations?
2. How do I convert any Tasmota template to an ESPHome configuration. Is there any convenient way, since a database for Tasmota already exists?

Besides the common settings (like wifi, logger, api, ota) I need to configure the correct switches and binary sensors and I have no idea how to use the information from the Tasmota database to create a working ESPHome configuration.

Do you have any ideas?

Posts: 4

Participants: 4

Read full topic

@rjalex wrote:

Dear friends,
after one day of experimenting succesfully with ESPHome with a NodeMCU ESP32S-WROOM board I am not sure as to what happened but I am not able to connect to my wifi anymore. Tried TONS of reflashing, recompiling, connecting to other APs but no luck. Ideas. Follow with data and logs. Thanks

Flashing host: Mac on Sierra with Python 3.7.6

bath.yaml

esphome:
  name: bath
  platform: ESP32
  board: nodemcu-32s

wifi:
  ssid: "rjanet"
  password: "12345678"

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

captive_portal:

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:

ouput from the CLI:

(bath) (base) iMac:iot bob$ esphome bath.yaml run
INFO Reading configuration bath.yaml...
INFO Generating C++ source...
INFO Compiling app...
INFO Running:  platformio run -d bath
********************************************************************************
Obsolete PIO Core v4.0.3 is used (previous was 4.2.1)
Please remove multiple PIO Cores from a system:
https://docs.platformio.org/page/faq.html#multiple-pio-cores-in-a-system
********************************************************************************
Processing bath (board: nodemcu-32s; framework: arduino; platform: espressif32@1.11.0)
--------------------------------------------------------------------------------
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
Dependency Graph
|-- <AsyncTCP-esphome> 1.1.1
|-- <ESPmDNS> 1.0
|   |-- <WiFi> 1.0
|-- <FS> 1.0
|-- <ESPAsyncWebServer-esphome> 1.2.6
|   |-- <AsyncTCP-esphome> 1.1.1
|   |-- <FS> 1.0
|   |-- <WiFi> 1.0
|-- <DNSServer> 1.1.0
|   |-- <WiFi> 1.0
|-- <Update> 1.0
|-- <WiFi> 1.0
Compiling .pioenvs/bath/src/main.cpp.o
Linking .pioenvs/bath/firmware.elf
Retrieving maximum program size .pioenvs/bath/firmware.elf
Building .pioenvs/bath/firmware.bin
Checking size .pioenvs/bath/firmware.elf
DATA:    [=         ]  12.9% (used 42320 bytes from 327680 bytes)
PROGRAM: [=====     ]  53.1% (used 870398 bytes from 1638400 bytes)
========================= [SUCCESS] Took 8.95 seconds =========================
INFO Successfully compiled program.
Found multiple options, please choose one:
  [1] /dev/cu.SLAB_USBtoUART (CP2102 USB to UART Bridge Controller)
  [2] Over The Air (bath.local)
(number): 1
INFO Running:  platformio run -d bath -t upload --upload-port /dev/cu.SLAB_USBtoUART
********************************************************************************
Obsolete PIO Core v4.0.3 is used (previous was 4.2.1)
Please remove multiple PIO Cores from a system:
https://docs.platformio.org/page/faq.html#multiple-pio-cores-in-a-system
********************************************************************************
Processing bath (board: nodemcu-32s; framework: arduino; platform: espressif32@1.11.0)
--------------------------------------------------------------------------------
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
Dependency Graph
|-- <AsyncTCP-esphome> 1.1.1
|-- <ESPmDNS> 1.0
|   |-- <WiFi> 1.0
|-- <FS> 1.0
|-- <ESPAsyncWebServer-esphome> 1.2.6
|   |-- <AsyncTCP-esphome> 1.1.1
|   |-- <FS> 1.0
|   |-- <WiFi> 1.0
|-- <DNSServer> 1.1.0
|   |-- <WiFi> 1.0
|-- <Update> 1.0
|-- <WiFi> 1.0
Retrieving maximum program size .pioenvs/bath/firmware.elf
Checking size .pioenvs/bath/firmware.elf
DATA:    [=         ]  12.9% (used 42320 bytes from 327680 bytes)
PROGRAM: [=====     ]  53.1% (used 870398 bytes from 1638400 bytes)
Configuring upload protocol...
AVAILABLE: esp-prog, espota, esptool, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa
CURRENT: upload_protocol = esptool
Looking for upload port...
Use manually specified: /dev/cu.SLAB_USBtoUART
Uploading .pioenvs/bath/firmware.bin
Serial port /dev/cu.SLAB_USBtoUART
Connecting........_
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
MAC: 24:6f:28:a1:bd:a4
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Auto-detected Flash size: 4MB
Compressed 15872 bytes to 10319...

Writing at 0x00001000... (100 %)
Wrote 15872 bytes (10319 compressed) at 0x00001000 in 0.2 seconds (effective 516.7 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 143...

Writing at 0x00008000... (100 %)
Wrote 3072 bytes (143 compressed) at 0x00008000 in 0.0 seconds (effective 1436.8 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 47...

Writing at 0x0000e000... (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.0 seconds (effective 5233.7 kbit/s)...
Hash of data verified.
Compressed 870512 bytes to 486010...

Writing at 0x00010000... (3 %)
Writing at 0x00014000... (6 %)
Writing at 0x00018000... (10 %)
Writing at 0x0001c000... (13 %)
Writing at 0x00020000... (16 %)
Writing at 0x00024000... (20 %)
Writing at 0x00028000... (23 %)
Writing at 0x0002c000... (26 %)
Writing at 0x00030000... (30 %)
Writing at 0x00034000... (33 %)
Writing at 0x00038000... (36 %)
Writing at 0x0003c000... (40 %)
Writing at 0x00040000... (43 %)
Writing at 0x00044000... (46 %)
Writing at 0x00048000... (50 %)
Writing at 0x0004c000... (53 %)
Writing at 0x00050000... (56 %)
Writing at 0x00054000... (60 %)
Writing at 0x00058000... (63 %)
Writing at 0x0005c000... (66 %)
Writing at 0x00060000... (70 %)
Writing at 0x00064000... (73 %)
Writing at 0x00068000... (76 %)
Writing at 0x0006c000... (80 %)
Writing at 0x00070000... (83 %)
Writing at 0x00074000... (86 %)
Writing at 0x00078000... (90 %)
Writing at 0x0007c000... (93 %)
Writing at 0x00080000... (96 %)
Writing at 0x00084000... (100 %)
Wrote 870512 bytes (486010 compressed) at 0x00010000 in 11.6 seconds (effective 602.6 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
========================= [SUCCESS] Took 21.34 seconds =========================
INFO Successfully uploaded program.
INFO Starting log output from /dev/cu.SLAB_USBtoUART with baud rate 115200
[09:20:39][I][logger:156]: Log initialized
[09:20:39][C][ota:364]: There have been 0 suspected unsuccessful boot attempts.
[09:20:39][I][app:028]: Running through setup()...
[09:20:39][C][wifi:033]: Setting up WiFi...
[09:20:40][D][wifi:304]: Starting scan...
[09:20:41][D][wifi:319]: Found networks:
[09:20:41][I][wifi:365]: - 'rjanet' (94:91:7F:6A:09:63) ▂▄▆█
[09:20:41][D][wifi:366]:     Channel: 1
[09:20:41][D][wifi:367]:     RSSI: -55 dB
[09:20:41][D][wifi:369]: - 'WOW FI - FASTWEB' (62:91:7F:6A:09:60) ▂▄▆█
[09:20:41][D][wifi:369]: - 'DIRECT-2B-HP OfficeJet 3830' (C8:D9:D2:44:A6:2C) ▂▄▆█
[09:20:41][D][wifi:369]: - 'Zamunda Fibra' (A4:91:B1:39:6E:53) ▂▄▆█
[09:20:41][D][wifi:369]: - 'TIM-53331562' (78:81:02:99:F8:FB) ▂▄▆█
[09:20:41][D][wifi:369]: - 'TIM-53331562_2GEXT' (B0:39:56:B7:A0:F3) ▂▄▆█
[09:20:41][D][wifi:369]: - 'Zamunda Fibra' (18:A6:F7:F4:09:80) ▂▄▆█
[09:20:41][I][wifi:193]: WiFi Connecting to 'rjanet'...
[09:20:43][W][wifi_esp32:336]: Event: Disconnected ssid='rjanet' bssid=94:91:7F:6A:09:63 reason='Auth Expired'
[09:20:43][W][wifi:451]: Error while connecting to network.
[09:20:43][W][wifi:488]: Restarting WiFi adapter...
[09:20:43][I][wifi:193]: WiFi Connecting to 'rjanet'...
[09:20:45][W][wifi_esp32:336]: Event: Disconnected ssid='rjanet' bssid=94:91:7F:6A:09:63 reason='Auth Expired'
[09:20:45][W][wifi:451]: Error while connecting to network.
[09:20:45][W][wifi:488]: Restarting WiFi adapter...
^C(bath) (base) iMac:iot bob$

Posts: 1

Participants: 1

Read full topic

@AlanQ wrote:

I hope I’m not breaking any forum rules by posting this. I’m a recent convert to Home Assistant and have been using ESPhome to configure some add-ons. I found it really useful to integrate the relay outputs from my security cameras, much more useful than a certain alarm panel board that I imported from the US. The only part I didn’t like was using a breadboard with jumper wires for something that I wanted to rely upon. I co-own a small electronics company so we looked at creating a PCB to meet my own needs and several versions later we have a small run for sale if anyone else is interested. It just runs each GPIO out to a screw terminal and the whole lot can fit into a Hammond project case if you like. Details here

Posts: 3

Participants: 2

Read full topic

@henaa wrote:

Hi
I have some issue
When i try turn the switch ON via the HA - is success , i saw it into the adafruit site.
When i try turn the switch IN via the Adafruit - i not see the state change in the HA
How fix it ?

substitutions:
  device_name: feather_bme280
  io_username: henadarr
  io_key: aio_MzVJ8**************
  update_interval: 30s
esphome:
  name: ${device_name}
  platform: ESP8266
  board: d1_mini_pro
wifi:
  ssid: '123456789'
  password: '123456789'
mqtt:
  broker: 'io.adafruit.com'
  username: ${io_username}
  password: ${io_key}
  topic_prefix: 'henadarr/feeds/relay1'
  birth_message:
    topic: 'henadarr/feeds/relay1'
    payload: 'ON'
  will_message:
    topic: 'henadarr/feeds/relay1'
    payload: 'OFF'
api:
ota:
logger:
switch:
  - platform: gpio
    pin: D1
    name: "relay1"
    state_topic: 'henadarr/feeds/relay1'
    internal: True

I add the next photo to demonstrate the issue

image1024×211 8.84 KB

Posts: 1

Participants: 1

Read full topic

@Eldudemeister wrote:

Hi,
Does anyone have a working config for the 2nice smart plug, every one that I have tried comes back with a not compatible error. I’ve flashed tasmota onto the plug with no issues but want to try esphome. I think the plug is based on the teckin sp20 but I keep getting an upload failed.
Thanks,
Matt

Posts: 7

Participants: 3

Read full topic