Quantcast
Channel: ESPHome - Home Assistant Community
Viewing all 1486 articles
Browse latest View live

AHRise AHR-083 Power Strip Tuya-Convert & esphome

$
0
0

@Kip wrote:

Hi All, just want to share a success I had in flashing a fairly inexpensive power strip with 4 controllable outlets, 4 always-on outlets, & 4 always-on USB ports with esphome!


Steps I took are pretty straight forward, if you’re not familiar with tuya-convert, I suggest watching this video to get that working: https://www.youtube.com/watch?v=dyUyewiKpRA

Once you’ve got tasmota on the power strip, you’ll need to create a device in esphome, here’s my code for the power strip:

esphome:
  name: power_strip_1
  platform: ESP8266
  board: esp01_1m

wifi:
  ssid: "WiFi_ssid"
  password: "wifi_password"

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Power Strip 1 Fallback Hotspot"
    password: "generated_password"

captive_portal:

# Enable logging
logger:

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

ota:
  password: "ota_password"
  
switch:
  - platform: gpio
    name: "Relay1"
    id: relay1
    pin:
      number: GPIO13
  - platform: gpio
    name: "Relay2"
    id: relay2
    pin:
      number: GPIO12
  - platform: gpio
    name: "Relay3"
    pin:
      number: GPIO14
    id: relay3
  - platform: gpio
    name: "Relay4"
    id: relay4
    pin:
      number: GPIO15
      
light:
# Blue LED PWM
# GPIO4
  - platform: monochromatic
    name: "PowerStrip-Blue_LED"
    output: output_component_blue

output:
#Blue LED
  - platform: esp8266_pwm
    id: output_component_blue
    pin: GPIO4
    inverted: yes

# Button & Automation to toggle all switches
# GPIO5

binary_sensor:
  - platform: gpio
    pin: GPIO5
    id: button
    name: "PowerStrip_Button"
    on_press:
      - switch.toggle: relay1
      - switch.toggle: relay2
      - switch.toggle: relay3
      - switch.toggle: relay4
    internal: True

Compile and download that from esphome and upload it using tasmota’s web interface for the device and you’ll be all set!

Thanks to @LUNZ for posting the code to a similar device here: https://community.home-assistant.io/t/migrating-tasmota-to-esphome-teckin-ss30-yaml/140447

Cheers!

Posts: 2

Participants: 2

Read full topic


Loop through a comma delimited list

$
0
0

@BrianHanifin wrote:

I need to parse a comma delimited list in ESPHome. Ideally I need to loop through the list to evaluate each item. Specifically I have a list of times stored in a text sensor 09:00,12:00,15:00.

I suspect I need to use lambda code to split the list into something I can loop over. Is lambda arduino code? I’m having a heck of a time searching for code examples.

Posts: 19

Participants: 4

Read full topic

Flash TYWE3L (tuya RGB led strip)

$
0
0

@odechr wrote:

Hi all,

I just installed ESPhome for the first time and was planning to make my first custom firmware for this led strip i got from aliexpress. Its a Tuya brand, the ship is called TYWE3L and is supposed to be a ESP8266?

https://www.aliexpress.com/item/10000013892613.html?spm=a2g0s.9042311.0.0.27424c4deRwZ5e

Module is TYWE3L, In a view it reminded me esp12 module, which is module with esp8266 MCU. Then searched and found that it’s sort of esp8266 type. Then i started looking into PCB and connections. As i found everything pointed, that it is actually esp8266 module and i can program it like ordinary one.

Anyone have any idea how to make that firmware on this one, so i can make a .bin file to flash it trough tuya-convert?

Posts: 4

Participants: 2

Read full topic

Custom Text Sensor Errors

Adafruit VEML6075 UVA UVB and UV Index Sensor

$
0
0

@Johan-Du-Preez wrote:

Did anybody ever get this sensor working in esphome ?

I have tried the following that was posted on github but it just returns 65535 and never changes values

File: veml6070_custom_sensor.h

#include "esphome.h"
#include "Adafruit_VEML6070.h"


class VEML6070CustomSensor : public PollingComponent, public Sensor {
 public:
  Adafruit_VEML6070 uv = Adafruit_VEML6070();
  VEML6070CustomSensor() : PollingComponent(15000) {}
  void setup() override {
    Wire.begin();
    uv.begin(VEML6070_1_T);
  }
  void update() override {
    uint16_t cur_uv = uv.readUV();
    ESP_LOGD("custom", "The value of sensor is: %i", cur_uv);
    publish_state(cur_uv);
  }
};

Espconfig:

esphome:
  name: wetterstation
  platform: ESP8266
  board: esp01_1m
  includes:
    - veml6070_custom_sensor.h
  libraries:
    - "https://github.com/adafruit/Adafruit_VEML6070"

...

i2c:
  sda: GPIO5
  scl: GPIO4

...

sensor:
  - platform: custom
    lambda: |-
      auto veml6070 = new VEML6070CustomSensor();
      App.register_component(veml6070);
      return {veml6070};
    sensors:
      name: "VEML6070 Custom Sensor"

The sensor i got is this one Sensor VEML6075 and on that page they state the library is the following “Library for sensor”

Posts: 1

Participants: 1

Read full topic

Using TTGO epaper display with ESPHome

$
0
0

@stokeymj wrote:

I am something of a newb in the world of Home Assistant, ESPHome and ePaper displays. I thought it might be useful to share my experiences, since my project is now running nicely and doing what I wanted it to do.

The display in question is the LILYGO® TTGO T5 V2.2 ESP32 2.9" EPaper. There is information about the exact model at http://www.lilygo.cn/prod_view.aspx?TypeId=50031&Id=1146 which is of some use, but please note that the Pin Reference Description seems to be largely erroneous. If you are thinking of using the ESP 32 on board for an additional purpose, such as a temperature sensor, and need to know the GPIO pin numbers, you would be advised to consult the schematic at https://github.com/lewisxhe/TTGO-EPaper-Series/blob/3dcb6469715021d1a3c168ad67025b8128af692d/schematic/T5_V2.2.pdf

My starting point was the very helpful description of the Waveshare epaper display at https://esphome.io/components/display/waveshare_epaper.html. As a newb I was puzzled by the mention of 4-wire SPI, and I spent some time trying to find out whether the GPIO pins on my model were the same. It could be that this does not matter, because the pins are assigned by the code, but I inferred that on my device the CLK pin was 18 and the MOSI 23. This seems to work perfectly well for me.

The next question was which ESP32 borad to select when setting up the ESPHome yaml. I have tried both the esp32dev and the ttgo-t1 and they both worked perfectly well.

I set up the yaml with a basic display, with a lot of excellent help from https://esphome.io/components/display/index.html, uploaded it, and had a good OTA set-up. The main challenge for me was to use states from Home Assistant which were strings rather than values. Initially I went down the MQTT route (see https://esphome.io/components/text_sensor/mqtt_subscribe.html), and created an automation in Home Asssistant to publish to MQTT. This worked, but it was laborious and seemed to work against the principles of ESPHome! My son pointed out that in fact it is simple: use the Home Assistant API and then platform: homeassistant within the relevant text sensor statement. This is much cleaner and neater.

My project was to build a display which would give basic weather data plus indoor temperature. My ESPHome code is as follows:

esphome:
  name: epaper2
  platform: ESP32
  board: esp32dev

wifi:
  ssid: "MY_SSID"
  password: "MY PASSWORD"

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

captive_portal:

# Enable logging
logger:


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

ota:
  password: "PASSWORD"

spi:
  clk_pin: 18
  mosi_pin: 23

font:
  - file: "Ldfcomicsans-jj7l.ttf"
    id: font_cs
    size: 20
  - file: "arial_th.ttf"
    id: font_arth
    size: 16

sensor:
  - platform: homeassistant
    entity_id: sensor.sn1_temperature
    id: kit_temp
  - platform: homeassistant
    entity_id: sensor.weathermet_temperature
    id: out_temp
  - platform: homeassistant
    entity_id: sensor.weathermet_feels_like_temperature
    id: feels_like
  - platform: homeassistant
    entity_id: sensor.weathermet_wind_speed
    id: wind_speed
  - platform: homeassistant
    entity_id: sensor.weathermet_wind_gust
    id: wind_gust

  - platform: dht
    pin: 26
    model: "DHT22"
    temperature:
      name: "ePaper Temperature"
      id: eptem
    humidity:
      name: "ePaper Humidity"
      id: ephu
    update_interval: 60s

text_sensor:
  - platform: homeassistant
    entity_id:  sensor.weathermet_wind_direction
    id: wind_dir

display:
  - platform: waveshare_epaper
    cs_pin: 5
    dc_pin: 19
    busy_pin: 4
    reset_pin: 12
    model: 2.90in
    full_update_every: 180
    rotation: 270
    lambda: |-
      it.print(0, 0, id(font_cs), "Conditions:");
      it.printf(0, 42, id(font_arth), "Inside:");
      it.printf(55, 40, id(font_cs), "%.1fc", id(eptem).state);
      it.printf(120, 42, id(font_arth), "Outside:");
      it.printf(170, 40, id(font_cs), "%.1fc", id(out_temp).state);
      it.printf(120, 68, id(font_arth), "feels like:");
      it.printf(178, 68, id(font_arth), "%.1fc", id(feels_like).state);
      
      it.printf(0, 102, id(font_arth), "Wind kph:");
      it.printf(75, 100, id(font_cs), "%.1f", id(wind_speed).state);
      it.printf(105, 100, id(font_arth), " - ");
      it.printf(118, 102, id(font_arth), "%.1f", id(wind_gust).state);
      it.printf(165, 100, id(font_cs), "%s", id(wind_dir).state.c_str());


You will see that I have also included a local temperature/humidity sensor, using the ESP 32. This is a simple DHT22 sensor, using pin 26 (which shows on the manufacturer’s description as IO13 for some reason).

Finally, I housed the display in a freeform stand which I made from thermoplastic and four screws. My only tip to pass on here is that I have found that it helps to put the thermosplastic in the freezer for 15 minutes or so before drilling holes. The drill bit works more cleanly if the material is as rigid as possible.

epaper (2)

That’s it. I hope this can help other newbs like myself, and of course I am more than happy to listen to any suggestions for improvements.

Posts: 1

Participants: 1

Read full topic

Help with condition and time delayed turn on ESPHome

$
0
0

@redeye_joe wrote:

I am trying to make my water valve turn on after a hall float sensor triggers and has been on for a given time. I can manually turn on the switch, but the automation doesnt work. Here is the code I have in my garden.yaml file:

binary_sensor:
  - platform: gpio
    name: "Water Level Low"
    pin:
      number: GPIO35
#      inverted: true
      mode: INPUT_PULLUP  
    id: water_low
    on_state:
      if:
        condition:
          for:
            time: 5min
            condition:
              binary_sensor.is_off: water_low
        then:
          - switch.turn_on: relay_3

Posts: 8

Participants: 3

Read full topic

ESPHome and NodeMCU A0 as DI

$
0
0

@MarkB1 wrote:

As the title suggests the documentation says that the A0 pin can be used as a DI.

A0: This pin can be used as a normal GPIO pin (like D1 etc) but additionally can measure voltages from 0 to 1.0V using the Analog To Digital Sensor.

I configured it as follows.

  - platform: gpio
    
    pin: A0
    name: "INPUT 6"

I tried using a pull down and pull up resistor 10K but no luck.

Do I need a different value or have I missed something?

Regards,

Posts: 1

Participants: 1

Read full topic


433mhz Reciever issue

$
0
0

@Jonas_Lytken wrote:

Hi Everyone,

First, off I want to say I’m new to both Hass & ESPHome, so I’m sorry if my question about ESPHome is a stupid one :slight_smile:

I’m having an issue with my garage door opener, On my remote, I have 4 keys, one to open one to close, and then I want to use one for lights. as a toggle button, the issue I have is when I click the remote it constantly sends the code to the receiver, and so it keeps toggling the switch

Is there a way I can get it to ignore commands for x time or any other solution
So to prevent it from turning off/on constantly?

Example:

remote_receiver:
  pin: D6
  tolerance: 50%
  filter: 10us
  idle: 8ms
  buffer_size: 2kb

binary_sensor:
  - platform: remote_receiver
    name: "Light Remote"
    internal: true
    on_press:
      then:
        - switch.toggle: lights
    rc_switch_raw:
      code: '100101001111001000010001'
      protocol: 1

switch:
  - platform: template
    name: Lights
    id: lights
    icon: "mdi:light"
    optimistic: true
    assumed_state: true

Posts: 1

Participants: 1

Read full topic

Problem with lambdas and strings in ESPHome

$
0
0

@stokeymj wrote:

I wonder if anyone can help me with this.

I am trying to display graphics files on an ePaper device under ESPHome/HA control. The idea is to display a graphic file selected by an integer generated from a sensor in Home Assistant. The graphic files are all named the same, but in numeric sequence, so that graphic01.gif is selected by Int 1 from the sensor, and graphic09.gif is selected by Int 9 from the sensor, etc.

I have produced a lambda which concatenates a string in the following form “graphic0” + string int from sensor + “.gif”. This works fine, and when I output the string result to the logs, it performs exactly as expected. The problem, however, is assigning the string value to the ESP id(my_string) which is needed to select the file and send it to the display.

The following is the part of the code which works perfectly if I comment out the crucial bit, which passes the value back to ESPHome:

image:
  - file: "major-01.gif"
    id: my_image

display:
  - platform: waveshare_epaper
    cs_pin: 5
    dc_pin: 19
    busy_pin: 4
    reset_pin: 12
    model: 2.90in
    full_update_every: 180
    pages:
      - id: tarot1
        lambda: |-
          std::string val = to_string((int)(id(rand_sen).state));
             std::string imagefile = "major-0" + val + ".gif";
             // id(my_image) = imagefile.c_str();
             it.image(0, 0, id(my_image)) ;
          ESP_LOGI("main", "Value of my sensor: %s", val.c_str());
          ESP_LOGI("main", "Value of imagefile: %s", imagefile.c_str());

As I say, the logs display exactly the values I am expecting: the integer returned by the sensor, and the concatenated string which results in major-01.gif, major-09.gif, etc. However, if I remove the comments on the line “id(my_image) = imagefile.c_str();” the compiler produces an error.

src/main.cpp:524:19: error: cannot convert 'const char*' to 'esphome::display::Image*' in assignment
          my_image = imagefile.c_str();
                   ^
*** [/data/epaper2/.pioenvs/epaper2/src/main.cpp.o] Error 1

I have removed the c_str() element, but that does not help. Clearly, the type of string expected by ESPHome is not the same as the string I have generated. Can anybody with greater knowledge of C++ help me out with this?

Many thanks if you can!

Posts: 2

Participants: 2

Read full topic

ESPHome C++ freeing memory

$
0
0

@BrianHanifin wrote:

I took a C class in college in the 90s. For various reasons I have used other languages since. I seem to recall variables had to be cleaned up to free them from memory. Is this true of the C++ code we are using?

I created a couple of functions that are included in my Irrigation Controller project. I am aiming to make this thing reliable so our plants and our pool pump don’t die from lack of water. Is there anything I should do differently with the code below? It doesn’t have to be super optimized, I just don’t want memory to leak until the device becomes unresponsive.

#include "esphome.h"
using namespace std;

// Declare functions before calling them.
bool scheduled_runtime(string);
string update_next_runtime(string);

bool scheduled_runtime(string time) {
  // Retrieve the current time.
  auto time_now = id(homeassistant_time).now();
  int time_hour = time_now.hour;
  int time_minute = time_now.minute;

  // Split the hour and minutes.
  int next_hour = atoi(time.substr(0,2).c_str());
  int next_minute = atoi(time.substr(3,2).c_str());

  //ESP_LOGD("scheduled_runtime()", "now: %i:%i", next_hour, next_minute);
  return (time_hour == next_hour && time_minute == next_minute);
}

string update_next_runtime(string time_list) {
  // Initialize variables.
  vector<string> times;
  vector<string> next_time;
  char * token;

  // Split the list of run times into an array.
  token = strtok(&time_list[0], ",");
  while (token != NULL) {
    times.push_back(token);
    token = strtok(NULL, ",");
  }

  // Stop now if the list does not contain more than one time.
  if (times.size() <= 1) {
    return time_list;
  }

  // Retrieve the current time.
  auto time_now = id(homeassistant_time).now();
  int time_hour = time_now.hour;
  int time_minute = time_now.minute;

  // Initialize variables.
  int next_hour = 0;
  int next_minute = 0;
  int index = 0;
  int loop_count = 0;
  int time_count = times.size()-1;

  // Compare the list of times with the current time, and return the next in the list.
  //ESP_LOGD("update_next_runtime", "now: %i:%i", hour, minute);
  for (string time : times) {
    // Retrieve the next scheduled time from the list.
    next_hour = atoi(time.substr(0,2).c_str());
    next_minute = atoi(time.substr(3,2).c_str());

    //ESP_LOGD("update_next_runtime", "next_hour: %s", time.c_str());
    if (time_hour < next_hour || (time_hour == next_hour && time_minute < next_minute)) {
      // Return this time if the next hour is greater than the current hour.
      return times[loop_count].c_str();
      break;
    // When we reach the end of our schedule for the day, return the first time of tomorrow.
    } else if (time_count == loop_count) {
      return times[0].c_str();
      break;
    }

    // Increment the loop counter and array index.
    loop_count += 1;
    index += 2;
  }

  delete token;
  token = NULL;

  return "unknown";
}

Posts: 3

Participants: 2

Read full topic

BLE presence

$
0
0

@strumf666 wrote:

I set this up to detect my watch in addition to BT running on hassio/rpi which detects my phone. What is the best way to integrate this into hassio/persons? Asaik it only allows devices to be assigned to persons, not binary sensors.

Posts: 1

Participants: 1

Read full topic

Worries of Restore from flash

$
0
0

@fremut wrote:

How could I save my esp8266 flash in case fast updating sensors (flash capacity is 100,000 writes) during restoring from flash?
Is my idea descibed below right? (maybe good point for documentation bettering)

integration sensor (total energy) updated every 1 second (restore: true) broke up this flash limit after 27.8hours
When I use filters with throttle (1hour):
filters:

  • throttle: 1h
    Is it good enough for saving my flash ? Or there is different method?

Thanks for your response

Posts: 3

Participants: 3

Read full topic

Do I need to upgrade platformio separately

$
0
0

@troy wrote:

Hello,

I have just installed ESPHome using a virtualenv.

When I compile firmware with ESPHome I see this message at the end

========================= [SUCCESS] Took 32.51 seconds =========================

********************************************************************************
There is a new version 4.1.0 of PlatformIO available.
Please upgrade it via `platformio upgrade` or `pip install -U platformio` command.
Changes: https://docs.platformio.org/en/latest/history.html
********************************************************************************


********************************************************************************
There are the new updates for platforms (espressif8266)
Please update them via `platformio platform update` command.

If you want to manually check for the new versions without updating, please use `platformio platform update --dry-run` command.
********************************************************************************

I use the following to upgrade ESPHome

pip3 install --upgrade esphome

Should I ever use one of these commands as well?

platformio upgrade
platformio update

Thanks

Posts: 5

Participants: 3

Read full topic

Inverse RGB led values

$
0
0

@huahe wrote:

Hello !

I am trying to use common anode leds with ESPHOME but I can’t get it to work properly. As it is a common anode one I have to inverse the values provided.

I am trying to do something like this:

output:
  - platform: esp8266_pwm
    pin: D0
    id: redgpio
    filters:
      - lambda: return (255-x);
  - platform: esp8266_pwm
    pin: D1
    id: greengpio
    filters:
      - lambda: return (255-x);
  - platform: esp8266_pwm
    pin: D2
    id: bluegpio
    filters:
      - lambda: return (255-x);

light:
  - platform: rgb
    name: "Kitchen Led"
    red: redgpio
    green: greengpio
    blue: bluegpio

But I get an error from ESPHOME.

What am I doing wrong?

Thanks.

Posts: 2

Participants: 2

Read full topic


Specific gpio pins for RF and IR?

$
0
0

@bpmittal wrote:

can anyone tell me if there is any specific gpio pin to be used for RF transmitter and receiver and IR transmitter and receiver in a nodemcu with esp8266 ?

Posts: 1

Participants: 1

Read full topic

Binary sensor for momentary switch - Can I use "on_click" and "on_double_click" in the same automation?

$
0
0

@patfelst wrote:

I have a momentary pushbutton connected to GPIO27 and want to perform different actions (set a global variable value for a countdown timer) depending on whether the button is clicked, or double clicked. A switch is turned on at the first single click, and then off when the countdown reaches zero.

Both single and double click triggers work, but after a double click, a single click is always called immediately after. Single clicks add a number of seconds to a counter, whereas a double click sets it to zero. So I only get the zero value for a very short time.

I’ve tried lengthening the debounce filter time, and have tried many combinations of the min_length and max_length times with no solution.

binary_sensor:
  - platform: gpio
    pin:
      number: GPIO27
      inverted: true
      mode: INPUT_PULLUP
    internal: true # don't publish to Home Assistant
    filters:
      - delayed_on: 60ms
    name: "Push button"

    # Single click
    # User has requested to turn ON the switch, or wants to add some time to the countdown
    on_click:
    - min_length: 20ms
      max_length: 150ms      
      then:
        # Only turn the switch ON if this is the first press (i.e. don't turn on if user is adding time)
        - if:
            condition:
              lambda: 'return id(countdown) == 0;'
            then:
              - homeassistant.service:
                  service: switch.turn_on
                  data:
                    entity_id: $switch_name

        # Is this the first press to turn ON, or does the user want to add time?
        - lambda: |-
            if (id(countdown) == 0) {
              // First press - Turn ON
              id(countdown) = 300;
            }
            else {
              // Switch is on, so add some time to the countdown
              id(countdown) += 10;
            }
        - logger.log: "Short Click"
        - light.turn_on:
            id: neopixel_single_1
            brightness: 50%
            red: 0%
            green: 100%
            blue: 0%        
        - delay: 200ms
        - light.turn_off: neopixel_single_1

    # Double click
    # Let user turn off before countdown is finished
    on_double_click:
    - min_length: 50ms
      max_length: 600ms
      then:
        - homeassistant.service:
            service: switch.turn_off
            data:
              entity_id: $switch_name
        - lambda: |-
            id(countdown) = 1;
        - logger.log: "Long Click"
        - light.turn_on:
            id: neopixel_single_1
            brightness: 50%
            red: 100%
            green: 0%
            blue: 0%        
        - delay: 200ms
        - light.turn_off: neopixel_single_1

I realise there are simpler ways of automating turn off of a switch after a timeout period, but I have an OLED display connected which shows the remaining time.

Posts: 4

Participants: 2

Read full topic

ESPHome ports in use?

$
0
0

@fribse wrote:

I’m moving my ESPHome devices to a seperate VLAN.
I know it uses ports 6053 and 8266 (for OTA), but as I can see it, they are the ports used from HA towards ESPHome.
But what about the other way, from the ESPHome devices to HA?
I’ve gotten a few ESP32 Cams, and I don’t get an image from them if I close down the firewall and only let these two ports be open.
I’ve gotten it to work on a hidden SSID, so that part is solved, now I would like to isolate the VLAN as much as possible.

Posts: 1

Participants: 1

Read full topic

Grove 4way relay using esphome

$
0
0

@Steven_Cruysberghs wrote:

Hi all. Hoping to find some arduino specialists here (warning noob, managed to setup a couple of other esphome based componenets like temp sensor and single relay but no real experience with arduino like devices)


I have this 4way relay board connected to an nodemcu flashed with esphome and connected to home assistant. This is the board : http://wiki.seeedstudio.com/Grove-4-Channel_SPDT_Relay/
I can’t use any of the documented esphome switch configs as it is i2c based.
current config (board flashed and ota updates working)(upload://fNTbOlxZfiU3EZJM9AU3XrsAVMA.jpeg)
esphome:
name: 4wayrelay
platform: ESP8266
board: nodemcuv2

wifi:
ssid: “xxxxxxxxx”
password: “xxxxxxxxxxxxx”

Enable fallback hotspot (captive portal) in case wifi connection fails

ap:
ssid: “4wayrelay”
password: “xxxxxxxxxxxxx”

captive_portal:

Enable logging

logger:

Enable Home Assistant API

api:

ota:

i2c:
sda: D1
scl: D2
scan: True

Log
[14:54:42][C][i2c:028]: I2C Bus:
[14:54:42][C][i2c:029]: SDA Pin: GPIO5
[14:54:42][C][i2c:030]: SCL Pin: GPIO4
[14:54:42][C][i2c:031]: Frequency: 50000 Hz
[14:54:42][I][i2c:033]: Scanning i2c bus for active devices…
[14:54:42][I][i2c:040]: Found i2c device at address 0x11
[14:54:42][C][logger:175]: Logger:
[14:54:42][C][logger:176]: Level: DEBUG
[14:54:42][C][logger:177]: Log Baud Rate: 115200
[14:54:42][C][logger:178]: Hardware UART: UART0
[14:54:42][C][captive_portal:169]: Captive Portal:
[14:54:42][C][ota:029]: Over-The-Air Updates:
[14:54:42][C][ota:030]: Address: 4wayrelay.local:8266
[14:54:42][C][api:095]: API Server:
[14:54:42][C][api:096]: Address: 4wayrelay.local:6053
[14:54:48][D][api.connection:583]: Client ‘Home Assistant 0.104.3 (192.168.0.6)’ connected successfully!
[14:56:16][I][ota:046]: Boot seems successful, resetting boot loop counter.

My guess would be I would have to use a config like this guy https://khaz.me/cheap-and-easy-control-of-8-relays-through-home-assistant/ but I have no idea how to talk to the on-board STM32F030F4P6.

Any tips?

Posts: 1

Participants: 1

Read full topic

TTGO-cam: ... reading incoming messages: Error while receiving data: [Errno 104] Connection reset by peer

$
0
0

@Uwe.Ha wrote:

Hi everyone.
I integrated two TTG-cams into an otherwise more or less empty hass.io setup. Apart from the mentioned cams there are three ESP32-cam devices and four ESP8266 devices integrated. All but one TTG-cam are offline.

The setup is as follows:

  • ESPHome (v1.14.3)
  • hass.io (v 0.105.2)
  • TTGO-cam v17, no SD card inserted
  • setup of the cam as mentioned at TTGO-cam v17

Hass.io runs on an old notebook (Intel® Core™2 Duo CPU T6600 @ 2.20GHz × 2 ) with an up to date Ubuntu 18.04.4 LTS in docker. Unfortunatelly xorg (GUI in other words) is available as I have no other platform available. The error occurs no matter how high the load is.

As a sort of long time test I kept one TTGO-cam online to see how the connectivity is like. The WiFi signal is at -42dB the uptime is increasing.
Nevertheless every 3 hours or so the status of the cam goes to disconnected. In the log file I find entries like this one:
2020-02-09 19:53:12 INFO (MainThread) [aioesphomeapi.connection] l9camttgo01.local: Error while reading incoming messages: Error while receiving data: [Errno 104] Connection reset by peer

Can anybody relate to this?

TIA!

Posts: 1

Participants: 1

Read full topic

Viewing all 1486 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>