@laca75tn wrote:

I have the following code on my esphome yaml file:

globals:
   - id: servo_level
     type: float
     restore_value: no
     initial_value: '0'

api:
  services:
    - service: control_servo
      variables:
        level: float
      then:
        - servo.write:
            id: blind_1_servo
            level: !lambda 'return level / 100.0;'
        - lambda: 'id(servo_level) = level;'    
        - delay: 1000ms
        - servo.detach: blind_1_servo   
sensor:
  - platform: template
    name: "${devicename_friendly} Servo Value"
    update_interval: 60s
    lambda: |- 
      return servo_level; 
       

I am getting the following error:

src/main.cpp:304:14: error: could not convert ‘servo_level’ from ‘esphome::globals::GlobalsComponent*’ to ‘esphome::optional’

Thanks for your help!

Posts: 2

Participants: 1

Read full topic

@finity wrote:

I’m trying to transition my wifi AP’s to different SSID’s. So I’m trying to make sure the ESPHome nodes can connect to the new one before I remove the old so I figured I’d set up the Sonoff to use multiple networks.

Per the docs the config is:

wifi:
  networks:
    - ssid: !secret wifi_ssid
      password: !secret wifi_pwd
    - ssid: !secret wifi_ssid_2
      password: !secret wifi_pwd

But for some reason it won’t connect to either SSID.

I have validated the config and it is valid.

If I remove the second SSID and reflash everything works fine.

So this works:

wifi:
  networks:
    - ssid: !secret wifi_ssid
      password: !secret wifi_pwd
    #- ssid: !secret wifi_ssid_2
    #  password: !secret wifi_pwd

Am I missing something?

Posts: 2

Participants: 1

Read full topic

@Linwood wrote:

I did several LED controllers with esphome, and it’s simple and fast and easy and has been dead reliable.

I want to do some kind of landscape lighting, but I do not think I want tape lighting even if I can get everything waterproof.

Are there ESPHome, or similar cloud-free Wifi (or even zwave) landscape lights, preferably RGB capable so on holidays I can do some special color programs.

I’ve found quite a few that work with cloud accounts, e.g. tuya but also a ton of knockoffs, but I really don’t want to depend on someone’s cloud (whether or not free), I want it to be local only.

Linwood

Posts: 1

Participants: 1

Read full topic

@CMDK wrote:

Hi all,

I’m trying make an IR receiver to control an audio-matrix, and I want to be able to control multiple zones from each receiver in the house.

My ‘fixed’ UART commands work, but I want to be able to change zone on the fly, e.g. press cifre 4 to control zone 4. Therefor I’m trying to use globals to to that, which I’m then converting in to a text_sensor.

Now, my problem is that I cannot get the content of the text_sensor to be sent using the uart.write function. Can anyone tell me if it is even possible, or if I’m just doing it wrong? Thanks!

globals:
### this value changes when I press a cifre on my remote
  - id: zone
    type: int
    restore_value: yes
    initial_value: '2'

esphome:
  name: esp8266_ireye_audac_zone
  platform: ESP8266
  board: d1_mini
    
wifi:
  networks:
  - ssid: xxxxxxxx
    password: xxxxxxxx
  
# Enable logging
logger:
  baud_rate: 0

# Enable Home Assistant API
api:

ota:

text_sensor:
### This gives me the entire command string using the global value
  - platform: template
    name: "playstring"
    lambda: !lambda |-
      int a = id(zone);

      std::string beginning ("#|X001|web|SVU0");
      std::string commandvar = to_string(a);   
      std::string end ("|0|U|");
      std::string command;
      
      command = beginning + commandvar + end;
      return command;
    update_interval: 10s
    id: play_str

uart:
  tx_pin: GPIO01
  rx_pin: GPIO03
  baud_rate: 19200

binary_sensor:
  - platform: remote_receiver
    name: "PLAY"
    raw:
      code: [52, -51, 310, -112, 52, -155, 258, -60, 52, -103, 310, -60, 52, -51, 258, -52, 52, -60, 413, -112, 52, -51, 362, -60, 52, -52, 51, -155, 52, -163, 155, -104, 51, -52, 103, -62]
    filters:
      - delayed_off: 50ms 
    on_press:
      then:
        - logger.log: "Play"
        - uart.write: id(play_str)
        - delay: 10ms
        - uart.write: [0x0D, 0x0A]

Posts: 1

Participants: 1

Read full topic

@drogfild wrote:

Hi,

I have two specific questions about ESPHome deep sleep. I’m trying to make a remote that has three buttons and ESP32. And naturally it should wake up from sleep on any of those and then send mqtt event to Home Assistant.

Currently it sleeps well and wakes up just fine. But I haven’t found a way to tell if it woke up by timer or button. And which button it was. Is there a way to know what input it was?

Second question is about multiple wake up sources. There’s advanced option esp32_ext1_wakeup and it has option pins. But there isn’t any example how multiple pins should be entered in yaml.

Thanks in advance!

Posts: 4

Participants: 2

Read full topic

@SagiRo wrote:

Hello everyone,

since 2 days ago, when I updated my hassos and hassio to 0.104.3 and hassos 3.8, I can’t seem to get any of the nodes to connect. I read in the release notes that there are some breaking changes with the MQTT but I don’t know what should I do now in order for the nodes to connect.

If you had the same problem or still have it please let me know what should I do to fix it.

Thank you in advance.

Posts: 3

Participants: 3

Read full topic

@Lijah wrote:

Hi,

I create a custom switch component in ESPHome to drive my Livolo switches.

Livolo switch with the RF 433 option use a no standard protocol. I didn’t succeed to adapt existing core RF Transmitter protocol to use them so i create a custom switch component.

GitHub - Livolo Switch

For my test i use the Sonoff RF transmitter with the hardware Hack , i will try without the hack shortly.

Posts: 1

Participants: 1

Read full topic

@laca75tn wrote:

Since I upgraded my nodes to 1.14.3 my text_sensor: platform: wifi_info (ip address and ssid) show unavailable. WiFi signal works and node is connected to Internet. Any ideas? The nodes on version 1.13 show the information correctly.

Posts: 1

Participants: 1

Read full topic

@D4VEW557 wrote:

Hi all,

I am trying to use a rotary encoder to control a cover position. I am able to achieve this using several automation’s but I’m sure there must be a shorter way to do using lambas which I have no experience with.

Looking around this forum I have came up with the below code which does not work.

esphome:
  name: rotary_test
  platform: ESP8266
  board: esp01_1m

wifi:
  ssid: "xxxxxxx"
  password: "xxxxxxx"

  ap:
    ssid: "Rotary Test Fallback Hotspot"
    password: "xxxxxxxx"

captive_portal:

logger:

api:
  password: "xxxxxxxxx"

ota:
  password: "xxxxxxxx"

sensor:
  - platform: rotary_encoder
    name: "Rotary Encoder"
    pin_a: 0
    pin_b: 2

    filters:
     - or:
        - debounce: 0.1s
        - delta: 3
    resolution: 1
    min_value: 0
    max_value: 10
    on_value:
      then:
        - homeassistant.service:   
            service: cover.set_cover_position    
            data_template:
              entity_id: cover.front_blinds
              position: "{{ position_1 | int }}"
            variables:
              position_1: 'return id(Rotary Encoder).state * 4;'

I’m sure there is something I am missing that someone could help me with.

Thanks in advance

Posts: 1

Participants: 1

Read full topic

@jjross wrote:

Is there a wiki or website I can go to so I can figure out what the best devices are?

I’m looking for some colour bulbs but I’m hoping to get some that are easy to flash and use. Ideally something I can flash OTA (is that even possible)?

Posts: 3

Participants: 2

Read full topic

@JamesT42 wrote:

Hi!
I’m trying to implement a display with infos regarding the api state. It should display something like online/offline. For this i’m using a lambda. But I’m unable to get it to work as I can not find the correct command. This is what I have:

display:
  - platform: ssd1306_i2c
    model: "SSD1306 128x64"
    address: 0x3C
    update_interval: 2s
    lambda: |-
      if (api.connected()) {
      it.printf(127, 0, id(font3), TextAlign::TOP_RIGHT, "online");
      }
      else {
      it.printf(127, 0, id(font3), TextAlign::TOP_RIGHT, "offline");
      }

which produces this comlilation error

src/main.cpp: In lambda function:
src/main.cpp:678:14: error: expected primary-expression before '.' token
       if (api.connected()) {
              ^

So api.connected() is not correct. Can anyone give me a tip how to correct this?

Cheers
James

Posts: 1

Participants: 1

Read full topic

@truglodite wrote:

I’m having trouble getting esphome to compile with a custom sensor I’m trying to implement (for an ms5611 baro). The default library esphome uses for that results in erroneous baro readings (prom read issues I think). I previously had the same esp8266+ms5611 sensor working perfectly for several years using a different library (MS5xxx.h). So I am just trying to get esphome to compile with this library instead.

A simplified version of my original .ino code looks like this:

#include <Wire.h>
#include <MS5xxx.h>

MS5xxx sensor(&Wire);

void setup() {
  sensor.connect();
}

void loop() {
  sensor.ReadProm();
  sensor.Readout();
  Serial.print("Pressure [Pa]: ");
  Serial.println(sensor.GetPres());
  delay(500);
}

My attempt to make a custom sensor looks like this:

ms5611trug.h:

#include "esphome.h"
#include "MS5xxx.h"
#include "Wire.h"

class ms5611trug : public PollingComponent, public Sensor {
	public:
		MS5xxx baro(&Wire);

	ms5611trug() : PollingComponent(60000) {}

	void setup() override {
		// This will be called by App.setup()
		Wire.begin(5,4);
		baro.connect();
	}
	void update() override {
		// This will be called by App.loop() 
		baro.ReadProm();
		baro.Readout();                   // Update MS5611 sensor
		float pressure = baro.GetPres()/100.0;
		publish_state(pressure);
	}
};

…and the relevant yaml:

esphome:
  includes:
    - ms5611trug.h
  libraries:
    - "MS5xxx"
	- "Wire"
	
sensor:
- platform: custom
  lambda: |-
    auto barometer = new ms5611trug();
    App.register_component(barometer);
    return {barometer};

  sensors:
    name: "Barometer"
    unit_of_measurement: hPa
    accuracy_decimals: 0

I’m pretty sure my problem is the MS5xxx baro(&Wire);. I’m sure the fix is simple, but I’m fairly wet behind the ears when it comes to the ++ part of C++.

I appreciate any pointers to get this working, gentle or not.

Here is the compiler error messages:

src/ms5611trug.h:7:15: error: expected identifier before '&' token
   MS5xxx baro(&Wire);
               ^
src/ms5611trug.h: In member function 'virtual void ms5611trug::setup()':
src/ms5611trug.h:14:7: error: '((ms5611trug*)this)->ms5611trug::baro' does not have class type
   baro.connect();
       ^
src/ms5611trug.h: In member function 'virtual void ms5611trug::update()':
src/ms5611trug.h:18:7: error: '((ms5611trug*)this)->ms5611trug::baro' does not have class type
   baro.ReadProm();
       ^
src/ms5611trug.h:19:7: error: '((ms5611trug*)this)->ms5611trug::baro' does not have class type
   baro.Readout();                   // Update MS5611 sensor
       ^
src/ms5611trug.h:20:24: error: '((ms5611trug*)this)->ms5611trug::baro' does not have class type
   float pressure = baro.GetPres()/100.0;
                        ^
Archiving /data/garage/.pioenvs/garage/lib964/libWire.a

Posts: 6

Participants: 2

Read full topic

@bphillips921 wrote:

I’m trying to flash ESPHome onto this Nodemcu-32S board. I go through all the normal steps to flash the device but end up with this error:

A fatal error occurred: Failed to connect to ESP32: Invalid head of packet (0x1B)
*** [upload] Error 2

I’ve tried 3 different times. I’ve tried rebooting HA, and erasing then reinstalling the ESPhome config for the device. When the Nodemcu-32s is plugged in to the USB port the LED on the board is red, in case that matters.

Any ideas how to get past this?

Posts: 4

Participants: 2

Read full topic

@truglodite wrote:

I am proposing a change to the esphome pir documentations…

The docs indirectly suggest that the HC-SR501 pir sensor is well suited for use with esphome. The page doesn’t explicitly state this by containing links to purchase or otherwise mentioning the part #, however common sense says most folks finding that tutorial will end up with HC-SR501’s wired to their esp8266 devices. Why is that a problem?

The 501 is a good module for non-wifi stuff, because it is cheap, adjustable, and has fairly low idle current. However, if you have ever tried to pair one of those with an esp8266 module, there’s a 80% chance you gave up after dealing with false triggers (that’s my statistic anyways, 2 of 10 wifi+501 projects actually worked). Why? The HC-SR501, which uses the biss0001 sensor, is very susceptible to wifi rfi!

So what?

I found another much better sensor for esphome pir use… the AM312:

This sensor does not have the adjustable on time and sensitivity of the 501, however it is pretty much immune to wifi noise and as such works well with esphome (I have no false triggers on any devices that use it). It works fine for most situations… triggering reliably inside my home from up to 40’ away. It’s also a lot smaller, and it only draws 15uA both active and inactive, compared to the usual 501 which burns 35uA inactive, and 77uA active. Since it’s not adjustable, you are stuck with a trigger reset time of 2.5sec (stays on for only 2.5sec unless it sees continuous motion… it toggling every 2.5sec is possible so HA would have to be able to handle that). That said, most folks can find an easy way to use that in automations… much better than false triggering for sure!

There is one potential caveat for advanced users though. Unfortunately due to hardware details, the am312 is not able to properly wake an esp through ch_pd, which is a common hardware design method to make battery esp devices last longer. I solved this problem by adding a buffer chip a while back, and wrote up some detailed info on how do this modification for ch_pd wake circuits (soldering not for the faint of heart):
https://www.esp8266.com/viewtopic.php?f=11&t=4458&start=72

With that mod, I’ve got an 18650 powered 8266 pir sensor that lasts years on a charge, triggered a few times a day. Even without the ch_pd mod (which is something 99% of folks reading that page would never need), the am312 is a better suited sensor though, where as the 501 is a bad choice for use near wifi antennae.

So I think the docs should be updated at least to show images/pinouts on an am312 instead of a 501.
Thoughts?

Posts: 1

Participants: 1

Read full topic

@Stepan wrote:

Hi all!
I got stucked with my first custom integration.
I want to integrate a rfid reader.

I have use the code from gdoerr
The code has been successfully read with my rfid reader and printed in the ESPhome logger

Now I have two choices.
1. I can publish the code to my “controlAccess” topic which has a script to check the access permission of the code. But my problem is I need 3 variables to complete the logic proccess:
payload= {
‘id’: ‘door’,
‘code’: wiegand_code,
‘timeStamp’: now()
}
and I dont know if would be possible to build in my esphome.yalm this structure and publish the json directly from the device in to the topic.

2. I could call a script which process the code and build the complete payload.
My problem is that the the script is not tiggered with this config and I dont know why.
My ESPhome yaml is:

custom_component:
  - lambda: |-
       auto wiegand = new WiegandReader(21, 23, "python_scripts.door_mqtt_publish.py");
       return {wiegand};

in config/python_scripts/door_publish_mqtt.py I have a simple code just to test it

logger.info("PYTHON SCRIPT CALLED")
name = data.get('code')
logger.info("HELLOOOOOOOOO %s", name)
hass.bus.fire(name, {"test": "from a Python script!"}
)

and I think that services is not mandatory, anaway:
config/python_scripts/services.yaml

door_mqtt_publish:
  description: publish a rfid code
  field:
    code:
      description: code format
      example: 9451293

In the ESP home logger I can see that the code is read perfectly but I can not trigger the python script to send the payload with the code on it. After read a code nothing appears in the HA logger.

HA logger:

2020-02-03 12:25:05 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2020-02-03 12:25:05 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for customizer which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2020-02-03 12:25:36 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.1908784496] Error handling message: Unauthorized

Posts: 2

Participants: 1

Read full topic

@Omerdagan wrote:

Hello,

As a part of my on going project of building the ultimate HA&ESPhome Aquarium controller,I need to control a peristaltic pump controlling fertilizer dosing to the system.
the pump is connected to a relay,and has a constant flow rate of 0.5mL/Sec.
I want to be able to control the dosing amount with a slider/input box so i need to multiply the time/ml (for example, 5 ml is 10 sec for the relay to work). can I achieve this using only ESPhome? or do i have to include automatons in HA?
at any case, an example for a suitable code world be much appreciated(ESPhome+HA/ESPhome only)

my current ESPhome YAML(without any preparation for the “timed” element)

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

wifi:
  ssid: "ssid"
  password: "password"

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

captive_portal:

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:

dallas:
  pin: GPIO4
  update_interval: 30s
# Individual sensors

sensor:

## Temp sensor 
  - platform: dallas
    address: 0xED011452C0E8AA28
    name: "Aquarium Water Temp"
  - platform: dallas
    address: 0xDD0000031EFB0428
    name: "Aquarium Air Temp"  
    
## pH Sensor    
  - platform: adc
    pin: GPIO35
    id: ph
    name: "pH Level"
    icon: "mdi:mdi-flask-outline"
    update_interval: 1s
    unit_of_measurement: pH
    filters:
      - median:
          window_size: 7
          send_every: 4
          send_first_at: 3
      # Measured voltage -> Actual pH (buffer solution)
      - calibrate_linear:
          - 0.59 -> 7.0
          - 0.71 -> 4.0
  
switch:
  - platform: gpio
    name: "Filter"
    icon: "mdi:air-filter"
    pin: GPIO15
  - platform: gpio
    name: "Heater"
    icon: "mdi:coolant-temperature"    
    pin: GPIO2
  - platform: gpio
    name: "Air Pump"
    icon: "mdi:air-purifier"    
    pin: GPIO0
  - platform: gpio
    name: "Back Light"
    icon: "mdi:led-variant-on"    
    pin: GPIO5
  - platform: gpio
    name: "Main Light"
    icon: "mdi:lightbulb"    
    pin: GPIO14
  - platform: gpio
    name: "Fertilizer Pump"
    icon: "mdi:sprout"    
    pin: GPIO12
  - platform: gpio
    name: "CO2 Reactor"
    icon: "mdi:periodic-table-co2"    
    pin: GPIO13 
  - platform: gpio
    name: "Cooling Fans"
    icon: "mdi:fan"    
    pin: GPIO13
    

Posts: 1

Participants: 1

Read full topic

@mauog wrote:

I read that ESPHome can support serial trough USB connection to upload firmware to ESP32 device,
Unfortunately I can see only the OTA function on the ESPhome GUI in HA.
I already tried to change the USB cable and to replug and restart the add on.
I cannot see anything on the ESP log.
How can I dig in this tissue?

Thank You

Posts: 4

Participants: 3

Read full topic

@fylo wrote:

Hello,
i have an simple setup: ESP 8266 with several DS18B20 sensors. I use ESPHome and the API connection to Home Assistant.

Everything works well:

But every 20 sec the data of all sensors is set to yellow:

And after a minimal amount of time the display swith to normal.

The Update intervall of the Dallas Component is set to 15 sec.

What can i do to change this behavior?

This is my config:

esphome:
  name: heizung
  platform: ESP8266
  board: nodemcu

wifi:
  ssid: "SSID"
  password: "passwd"

logger:

api:

ota:

time:
  - platform: homeassistant
    id: esptime

dallas:
  - pin: D2
    update_interval: 15s

sensor:
  - platform: dallas
    address: 0x4301144FAB2DAA28
    name: "Temp Heizkörper Vorlauf"
    id: temp_heizkorper_vorlauf
  - platform: dallas
    address: 0x620114500249AA28
    name: "Temp Heizkörper Rücklauf"
    id: temp_heizkorper_rucklauf
  - platform: dallas
    address: 0x0401144FA6CDAA28
    name: "Temp Kessel Bypass"
    id: temp_kessel_bypass

Posts: 3

Participants: 2

Read full topic

@mpaneth wrote:

I currently have an ESP32 using DHCP to get its IP address and now want to give it a different fixed address in the same subnet.

Is there a way to recompile with the new fixed address and reprogram OTA?

When I try to set the IP address to 192.168.0.221 (was 192.168.0.21), I generate the following log

INFO Reading configuration /config/esphome/temp.yaml…
INFO Detected timezone ‘AEST’ with UTC offset 10 and daylight savings time from 04 October 02:00:00 to 04 April 03:00:00
INFO Generating C++ source…
INFO Compiling app…
INFO Running: platformio run -d /config/esphome/temp
Processing temp (board: d1; framework: arduino; platform: espressif8266@2.2.3)

HARDWARE: ESP8266 80MHz, 80KB RAM, 4MB Flash
Dependency Graph
|-- 1.2.2
| |-- 1.0
|-- 1.0
|-- 1.2
| |-- 1.0
|-- 1.0
Compiling /data/temp/.pioenvs/temp/src/main.cpp.o
Linking /data/temp/.pioenvs/temp/firmware.elf
Retrieving maximum program size /data/temp/.pioenvs/temp/firmware.elf
Checking size /data/temp/.pioenvs/temp/firmware.elf
Building /data/temp/.pioenvs/temp/firmware.bin
DATA: [===== ] 46.2% (used 37888 bytes from 81920 bytes)
PROGRAM: [==== ] 40.1% (used 419044 bytes from 1044464 bytes)
Creating BIN file “/data/temp/.pioenvs/temp/firmware.bin” using “/data/temp/.pioenvs/temp/firmware.elf”
========================= [SUCCESS] Took 34.69 seconds =========================
INFO Successfully compiled program.
INFO Connecting to 192.168.0.221
ERROR Connecting to 192.168.0.221:8266 failed: [Errno 113] No route to host

Mike

Posts: 2

Participants: 2

Read full topic

@klogg wrote:

I’ve flashed a few devices in the past with no problems but today I am getting this error when using
esphomeflasher.

Using 'COM8' as serial port.
Connecting........_____....._____....._____....._____....._____....._____....._____
Unexpected error: ESP Chip Auto-Detection failed: Failed to connect to Espressif device: Timed out waiting for packet header

It’s a simple config, just to get it on-line.

Can anyone help please?

substitutions:
  board: mhetesp32devkit
  device_name: esp32_01
  friendly_name: Garden Irrigation Controller

esphome:
  name: ${device_name}
  platform: ESP32
  board: ${board}

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

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Garden Irrigation Controller"
    password: "xxxxxxxxxxxx"

captive_portal:

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:

# Sensors
text_sensor:
  # ESPHome Version
  - platform: version
    name: ${friendly_name} ESPHome Version

sensor:
  # Uptime
  - platform: uptime
    name: ${friendly_name} Uptime

  # WiFi Signal
  - platform: wifi_signal
    name: ${friendly_name} WiFi Signal
    update_interval: 60s

# Switches
switch:
  # Reboot
  - platform: restart
    name: ${friendly_name} Reboot
    id: reboot

Posts: 2

Participants: 1

Read full topic