@GGexe wrote:

Hi there,

First time using esphome, i used it for leds and it was awesome
Im am looking to press a button (very similar to a arduino pushbutton) using a Solenoid Electromagnet Push Pull

• Does anyone know what kind of config i can use to control this via esphome?
• also any help with a diagram to wire?
• Is this the right module to use for this use case ? soldering on the pcb is a nono at the moment

i will be using a esp8266

Thanks

Posts: 4

Participants: 4

Read full topic

@fribse wrote:

When I compile my sketch for the ESP32-cam I see these warnings:

Compiling /data/camera_hallway/.pioenvs/camera_hallway/src/esphome/components/light/addressable_light.cpp.o
src/esphome/components/esp32_camera/esp32_camera.cpp: In member function 'virtual void esphome::esp32_camera::ESP32Camera::dump_config()':
src/esphome/components/esp32_camera/esp32_camera.cpp:54:10: warning: enumeration value 'FRAMESIZE_QXGA' not handled in switch [-Wswitch]
   switch (this->config_.frame_size) {
          ^
src/esphome/components/esp32_camera/esp32_camera.cpp:54:10: warning: enumeration value 'FRAMESIZE_INVALID' not handled in switch [-Wswitch]

I see video streams in HA, so that part is working for two of my three cameras, I think the last one is defective.

Posts: 2

Participants: 2

Read full topic

@shogor wrote:

Hello everybody

Could you possibly help me with ESPhome configuration for sonoff basic (mini).

I tried hard to get the same behavior as i have in the tasmota: (Power on state : toggle.)

I tried to use “restore mode” but it doesn’t have option - toggle.

I need to toggle the sonnoff relay from the previous state when i cut the power for a short period of time using the self returning wall switch.

Thanks in advance

Posts: 7

Participants: 2

Read full topic

@Gazza wrote:

Hi,
I am trying to use a diffused LED (red) to indicate when my garage is open. LED on when open, closed = off. I am using a NodeMCU with ESPHome. I am really battling to get the bulb to light up like a light would. Could someone please point me in the right direction. Many thanks.

Posts: 4

Participants: 2

Read full topic

@tom_l wrote:

I am going to replace one of my ESP8266 boards with an ESP32 so as to add some bluetooth sensors. I want to keep the existing sensors from the ESP8266 as well and will transfer the config for them to the new board.

What is the best way to go about this?

Will deleting the ESP8266 integration and restarting HA before configuring the ESP32 board be enough to prevent a whole bunch of duplicate sensors like sensor.xyz_02 ?

Posts: 1

Participants: 1

Read full topic

@Rimnotatakushi wrote:

Hi all

I have two NodeMCU ESP8266 devices running ESPHome.

1st device is a NodeMCU with a DHT22 sensor in the study. Working great and I get constant readings on the temp and humidity, as long as the 2nd node is offline/getting a reading from it’s sensor.

2nd device is a NodeMCU with an Ultrasonic senor (the type with a trigger and echo pin). Now this device is battery powered and not working as it should (I’m working on it) but I think the Ultrasonic sensor I’m using is a 5V device thus running off a 18650 Li-ion cell, it works up to about 3.8V then the Ultrasonic senor stops working.

Now this is where it gets weird, as soon as the 2nd nodeMCU looses the ultrasonic sensor readings, the 1st NodeMCU’s values is unavailable as well in Home Assistent. No temp or humidity readings and this NodeMCU is not powered of batteries, so definitely not a power issue.

Why would one faulty sensor on a separate NodeMCU effect a completely different NodeMCU’s sensor’s readings in Hassio?

Here is my yaml:

1st NodeMCU

esphome:
  name: test_controller_dht22
  platform: ESP8266
  board: nodemcuv2

wifi:
  ssid: "xx"
  password: "xx"
  power_save_mode: none #NONE, LIGHT, HIGH

# Enable logging
logger:
# Enable Home Assistant API
api:

# Example configuration entry
text_sensor:
  - platform: version
    name: "DHT22 ESPHome Version"

ota:

status_led:
  pin: GPIO2

binary_sensor:
  - platform: status
    name: "Test Controller - DHT22"

switch:
  - platform: restart
    name: "DHT22 Test Controller Restart"
  - platform: shutdown
    name: "DHT22 Test Controller Shutdown"
    icon: "mdi:shutdown"    

sensor:
  - platform: wifi_signal
    name: "DHT22 Test Conroller"
#    update_interval: 60s
  - platform: adc
    pin: VCC
    name: "DHT22 Vcc Voltage"
  - platform: dht
    pin: D2
    temperature:
      name: "Study Temperature"
    humidity:
      name: "Study Humidity"
#    update_interval: 60s

2nd NodeMCU

esphome:
  name: h2o_tank_1
  platform: ESP8266
  board: nodemcuv2

wifi:
  ssid: "xx"
  password: "xx"
#  manual_ip:
#    static_ip: 192.168.8.15
#    gateway: 192.168.8.1
#    subnet: 255.255.255.0
  power_save_mode: none #NONE, LIGHT, HIGH

# Enable logging
logger:
# Enable Home Assistant API
api:

# Example configuration entry
text_sensor:
  - platform: version
    name: "Tank lvl ESPHome Version"

ota:

binary_sensor:
  - platform: status
    name: "H2O Tank 1 Controller"

status_led:
  pin: GPIO2
  
switch:
  - platform: restart
    name: "H2O Tank 1 Controller Restart"

sensor:
  - platform: wifi_signal
    name: "H2O Tank 1"
    update_interval: 30s
  - platform: ultrasonic
    trigger_pin: D1
    echo_pin: D2
    name: "Water Level"
    update_interval: 30s
    timeout: 3m
  - platform: adc
    pin: A0
    name: "Battery Voltage"
    filters:
      - multiply: 4.2
    
#deep_sleep:
#  run_duration: 300s
#  sleep_duration: 10min

Posts: 1

Participants: 1

Read full topic

@simfun wrote:

Has anybody tried intercepting packets with ESP32/ESPHome using LYWSD03MMC device?
Device link is here: [Newest Version] XIAOMI Mijia Bluetooth Thermometer 2 Wireless Smart Electric Digital Hygrometer Thermometer 1Pcs Health Management from Health & Beauty on banggood.com
https://banggood.app.link/3Wl0u7oHN1

Not sure if direct links are permitted here. If not please advise to remove it.

Posts: 3

Participants: 3

Read full topic

@Capn_jimbo wrote:

Hi everyone …
I recently bought one of these to test it out … but I’m stuck …
Integration with ESPHOME works (connect to WiFi) but not able to send or receive SMS …
I checked the sim on a 2g phone , it is able to send and receive SMS …
If anyone has any success with this I would be really grateful for any advice or working yaml …

Thanks in advance

e7772929-ba65-48d7-98d5-8d480a208302.jpg1000×1000 141 KB

Posts: 2

Participants: 2

Read full topic

@DeanoX wrote:

I 1st grabbed a couple of these some months ago - and had limited success as at the time Tuya-convert wasnt working. I got one flashed - but had to do it via Serial and it never worked properly - though I was able to sniff the Serial comms to the MCU that controls the dimmer.

I have just bought a fresh couple to try again. Tuya-convert worked like a dream and I now have a working yaml for ESPHome including dimming via the push button. They are a perfect replacement like this for old X10 LD11 dimmer modules that also use a hard wired momentary switch.

There’s lots of very good info here :-
https://blakadder.github.io/templates/qs-wifi_D01_dimmer.html

Original tasmota thread :-

related thread on ESPHome git

My Yaml…

key features…

• Exposes the light to HA
• Push Button - Single Click = Toggle Light
• Push Button - Hold = Cycles through Dim->Bright->Dim etc.
• No custom components required

esphome:
  name: esp_dim01
  platform: ESP8266
  board: esp01_1m

wifi:
  domain: .local
  ssid: "xxxxxx"
  password: "xxxxx"
  manual_ip:
    static_ip: 192.168.1.69
    gateway: 192.168.1.254
    subnet: 255.255.255.0

# Enable logging
logger:
  baud_rate: 0
  level: DEBUG
  logs:
    sensor: ERROR
    duty_cycle: ERROR
    binary_sensor: ERROR
    light: ERROR

# level: VERBOSE
# Enable Home Assistant API
api:

ota:

web_server:

time:
  - platform: homeassistant

substitutions:
  switch_id: "dim_01"

# globals:
# Dummy light brightness tracker Global

globals:
  # Dim direction for Switch 1: 0=Up (brighten) 1=down (dim)
  - id: g_direction_1
    type: int
    restore_value: no
    initial_value: "1"
  # Counter for time pressed for switch 1
  - id: g_counter_1
    type: int
    restore_value: no
    initial_value: "0"
  # initial brightness

# Uart definition to talk to MCU dimmer
uart:
  tx_pin: GPIO1
  rx_pin: GPIO3
  stop_bits: 1
  baud_rate: 9600

sensor:
  - platform: wifi_signal
    name: "${switch_id} WiFi Signal Sensor"
    update_interval: 60s
  # Primary template sensor to track Brightness of light object for "on_value" sending to MCU dimmer
  - platform: template
    name: "${switch_id} Brightness Sensor"
    id: sensor_g_bright
    internal: true
    update_interval: 20ms
    # Ensure on_value only triggered when brightness (0-255) changes
    filters:
      delta: 0.8
    # Read brightness (0 - 1) from light , convert to (0-255) for MCU
    lambda: |-
      if (id(light_main).remote_values.is_on()) {
        return (int(id(light_main).remote_values.get_brightness() * 255));
      }
      else {
        return 0;
      }
    # On Change send to MCU via UART
    on_value:
      then:
        - uart.write: !lambda |-
            return {0xFF, 0x55, (char) id(sensor_g_bright).state, 0x05, 0xDC, 0x0A};
        - logger.log:
            level: INFO
            format: "Sensor Value Change sent to UART %3.1f"
            args: ["id(sensor_g_bright).state"]
  # Sensor to detect button push (via duty_cycle of 50hz mains signal)
  - platform: duty_cycle
    pin: GPIO13
    internal: true
    id: sensor_push_switch
    name: "${switch_id} Sensor Push Switch"
    update_interval: 20ms

binary_sensor:
  #Binary sensor (on/off) which reads duty_cyle sensor readings.
  - platform: template
    id: switch1
    internal: true
    name: "${switch_id} Switch Binary Sensor"
    # read duty_cycle, convert to on/off
    lambda: |-
      if (id(sensor_push_switch).state < 95.0) {
        return true;
      } else {
        return false;
      }
    # Short Click - toggle light only
    on_click:
      max_length: 300ms
      then:
        light.toggle: light_main
    # Generic On_Press - log press, toggle DIM Direction and reset press interval counter
    on_press:
      then:
        - logger.log: "Switch 1 Press"
        - lambda: |-
            if (id(g_direction_1) == 0) {
              id(g_direction_1) = 1;
            } else {
              id(g_direction_1) = 0;
            }
            id(g_counter_1) = 0;

# Dummy light output to allow creation of light object
output:
  - platform: esp8266_pwm
    pin: GPIO14
    frequency: 800 Hz
    id: dummy_pwm

# Primary Light object exposed to HA
light:
  - platform: monochromatic
    default_transition_length: 20ms
    name: "${switch_id} Light"
    output: dummy_pwm
    id: light_main

switch:
  - platform: restart
    name: "${switch_id} Restart"

# Polling object for long press handling of switch for dim/brighten cycle
interval:
  - interval: 20ms
    then:
      - if:
          condition:
            binary_sensor.is_on: switch1
          then:
            # Ramp rate for dim is product of interval (20ms) * number of intervals
            # Every 20ms Dimmer is increased/decreased by 2/255
            # Lower limit = 10%
            # Upper limit = 100%
            # 100% - 10% = 90% = 230/255. Therefore 230/2 * 20ms = 2.3 seconds for full range
            # At full/min brightness - further 16x20ms = 0.32 Seconds "dwell" by resetting counter to 0
            # Initial pause for 16x20ms = 0.32s to allow "on_click" to be discounted 1st
            # g_direction_1 = 0 (Increasing brightness)
            # g_direction_1 = 1 (decreasing brightness)
            # g_counter_1 = Interval pulse counter

            lambda: |-
              float curr_bright = id(light_main).remote_values.get_brightness();
              id(g_counter_1) += 1; 

              // If max bright, change direction
              if (curr_bright >= 0.999 && id(g_direction_1) == 0) {
                id(g_direction_1) = 1;
                id(g_counter_1) = 0;
              }

              // If below min_bright, change direction
              if (curr_bright < 0.1 && id(g_direction_1) == 1) {
                id(g_direction_1) = 0;
                id(g_counter_1) = 0;
              }

              if (id(g_direction_1) == 0 && id(g_counter_1) > 15) {
                // Increase Bright
                auto call = id(light_main).turn_on();
                call.set_brightness(curr_bright + (2.0/255.0));
                call.perform();
              }

              else if(id(g_direction_1) == 1 && id(g_counter_1) > 15) {
                // Decrease Bright
                auto call = id(light_main).turn_on();
                call.set_brightness(curr_bright - (2.0/255.0));
                call.perform();
              }

Posts: 2

Participants: 2

Read full topic

@risk wrote:

Apparently it has the ADE7953 inside, same as Shelly 2.5, which is supported.

I haven’t found anyone sharing their ESPhome config for it.

Is it the same gpio pins used for SPI with ade7953 ?, what about the relay pins?

Posts: 3

Participants: 2

Read full topic

@elkropac wrote:

Hi,
i bought this smart plug

When searching for flash instructions, i found out, it’s probably this one

I have succesfuly flashed it using tuya-convert with tasmota. I played with several templates, could not find the right one. I decided to swtich to esphome for debuging.

This is my latest config

substitutions:
  dev_name: avatto_plug_rgbw_001

esphome:
  name: ${dev_name}
  platform: ESP8266
  board: esp01_1m

wifi:

# Enable logging
logger:
  level: DEBUG
  
# Enable Home Assistant API
api:

ota:


switch:
#found
  - platform: gpio
    name: "${dev_name}_relay"
    pin: GPIO15
    id: relay
  - platform: shutdown
    name: "${dev_name}_shutdown"
  - platform: restart
    name: "${dev_name}_restart"

output:
#found - red
  - platform: esp8266_pwm
    pin: GPIO05
    frequency: 1000 Hz
    id: output_red
#found - blue
  - platform: esp8266_pwm
    pin: GPIO12
    frequency: 1000 Hz
    id: output_blue
#found - white
  - platform: esp8266_pwm
    pin: GPIO04
    frequency: 1000 Hz
    id: output_white
#  - platform: esp8266_pwm
#    pin: GPIO14
#    frequency: 1000 Hz
#    id: output_green


#status_led:
#  pin:
#    number: GPIO09
#    inverted: True

light:
  - platform: monochromatic
    name: "${dev_name}_led_red"
    output: output_red
  - platform: monochromatic
    name: "${dev_name}_led_blue"
    output: output_blue
  - platform: monochromatic
    name: "${dev_name}_led_white"
    output: output_white
  - platform: monochromatic
    name: "${dev_name}_led5"
    output: output_green

binary_sensor:
#found
  - platform: gpio
    pin:
      number: GPIO13
      mode: INPUT_PULLUP
      inverted: True
    name: "${dev_name}_button"
    on_press:
      - switch.toggle: relay

sensor:
#  - platform: hlw8012
#    sel_pin: 
#      number: GPIO03
#      inverted: True
#    cf_pin: GPIO02
#    cf1_pin: GPIO14
#    current_resistor: 0.0025
#    voltage_divider: 840
#    current:
#      name: "${dev_name}_current"
#      unit_of_measurement: A
#    voltage:
#      name: "${dev_name}_voltage"
#      unit_of_measurement: V
#    power:
#      name: "${dev_name}_power"
#      id: power
#      unit_of_measurement: W
#    change_mode_every: 1
#    update_interval: 10s
  - platform: wifi_signal
    name: "${dev_name}_wifi_signal"
    update_interval: 30s
  - platform: uptime
    name: "${dev_name}_uptime"
    update_interval: 120s

text_sensor:
  - platform: version
    name: "${dev_name}_version"

I had some boot problems when i was trying GPIO09 as LED PWM pin. But i managed to recover.
Now, it seems to be bricked after trying the same thing with GPIO14. It does not ping.

I also did no manage to find the power monitoring chip, yet.

So i guess, i will have to pry it open. Or is there another way to flash it again using tuya-convert?

Posts: 1

Participants: 1

Read full topic

@chocolatejoe wrote:

I have a water proof ultrasonic sensor (A02YYUW) which i would like to add to a project built in esphome.

It outputs via UART and there is a sample code in the data sheet.

is it possible to integrate this code directly as a custom component in esp home or am I barking up the wrong tree

Any help is appreciated.

/*
  *@File  : DFRobot_Distance_A02.ino 
  *@Brief : This example use A02YYUW ultrasonic sensor to measure distance
  *         With initialization completed, We can get distance value 
  *@Copyright [DFRobot](http://www.dfrobot.com),2016         
  *           GUN Lesser General Pulic License
  *@version V1.0           
  *@data  2019-8-28
*/

#include <SoftwareSerial.h>

SoftwareSerial mySerial(11,10); // RX, TX
unsigned char data[4]={};
float distance;

void setup()
{
 Serial.begin(57600);
 mySerial.begin(9600); 
}

void loop()
{
    do{
     for(int i=0;i<4;i++)
     {
       data[i]=mySerial.read();
     }
  }while(mySerial.read()==0xff);

  mySerial.flush();

  if(data[0]==0xff)
    {
      int sum;
      sum=(data[0]+data[1]+data[2])&0x00FF;
      if(sum==data[3])
      {
        distance=(data[1]<<8)+data[2];
        if(distance>30)
          {
           Serial.print("distance=");
           Serial.print(distance/10);
           Serial.println("cm");
          }else 
             {
               Serial.println("Below the lower limit");
             }
      }else Serial.println("ERROR");
     }
     delay(100);
}

Posts: 3

Participants: 2

Read full topic

@deet wrote:

Question: how can I change the state_topic of a sensor on a button press?

Background: I have multiple ESP8266 boards that publish data to a central RPi running InfluxDB over MQTT. To distinguish the boards I encode location info in the state topic, e.g.

state_topic: influx/environv3/location/mobile/value/state

where the topis parsed by a MQTT listener script as follows:

influx/<measurement>/[<tagname>/<tagvalue>/]*<field>/state

The problem I have: one board I use in multiple locations (fine dust measurement), so I want to change the state topic on the fly. I have a button on this board which I hope to use to change the state_topic. In pseudo-code, I’m looking for something like:

globals:
 - id: location_state
   type: int
   restore_value: no
   initial_value: '0'

sensor:
  - platform: sds011
    pm_2_5:
      state_topic: influx/environv3/location/home/value/state
      id: mypm25

binary_sensor:
  - platform: gpio
    on_press:
      then: 
      - lambda: |-
          if (id(initial_value) == 0) {
            id(mypm25).state_topic = "influx/environv3/location/mobile/value/state"
            id(initial_value) += 1;
          } if (id(initial_value) == 1) {
            id(mypm25).state_topic = "influx/environv3/location/office/value/state"
            id(initial_value) += 1;
          } else {
          	id(mypm25).state_topic = "influx/environv3/location/home/value/state"
          	id(initial_value) = 0;
          }

Unfortunately, .state_topic is not a member of the sensor that I can change. Does anyone have any ideas?

Posts: 1

Participants: 1

Read full topic

@ferbar wrote:

I don’t know if someone else is interested in playing sounds with ESPHome
TLTR: https://www.youtube.com/watch?v=RI8nUdsZprM

The hardware I’m using is an ESP8266 / D1 mini, a BC338 and a 470ohm resistant. The xtensia arduino plugin is 2.5.2 and ESP8266Audio 1.1.3 with my patch - https://github.com/earlephilhower/ESP8266Audio/pull/224. In addition to my patch I had to comment-out AudioFileSourceSD in the .h and .cpp file.
Until now I didn’t manage to play a mp3 - not enough free ram …
My hint: disconnect the speaker while flashing the esp

esphome:
  name: $devicename
  platform: ESP8266
  board: nodemcuv2
  arduino_version: 2.5.2
  libraries:
    - esp8266Audio
  includes:
    - EsphomeAudio.h

switch:
  - platform: custom
    lambda: |-
      auto esphomeAudio = new EsphomeAudio();
      App.register_component(esphomeAudio);
      return {esphomeAudio};
    switches:
      name: "Play Sound"

EsphomeAudio.h:

#include "esphome.h"

#include <alloca.h>

#include <AudioFileSourceSPIFFS.h>
#include "AudioFileSourceHTTPStream.h"
#include "AudioGeneratorWAV.h"
#include "AudioOutputI2SNoDAC.h"
#include "AudioFileSourceBuffer.h"
#include "AudioGenerator.h"

static const char *TAG = "audio";

#define DEBUGf(format, ...) Serial.printf(format "\n", ##__VA_ARGS__)

/**
 * im cbData muss das TAG stehn - vom regster
 */
void statusCBFn(void *cbData, int code, const char *message) {
        // PROGMEM vs RAM
        if (message >= (const char *)0x40000000) {
                char *s=(char *) alloca(strlen_P(message));
                strcpy_P(s, message);
                message=s;
        }
        DEBUGf("'%s': code:%d statusCBFn: %s", (char *) cbData, code, message);
}

// == RX
#define I2SO_DATA 3

class EsphomeAudio : public Component, public Switch {
public:
        EsphomeAudio() : wav(NULL), file(NULL), out(NULL), buff(NULL) {}
        void setup() override {
                pinMode(I2SO_DATA, OUTPUT);
                digitalWrite(I2SO_DATA,false);
        }
        void loop() override {
                if (this->wav && this->wav->isRunning()) {
                        if (!this->wav->loop()) {
                                this->wav->stop();
                                delete(this->wav); this->wav=NULL;
                                delete(this->buff); this->buff=NULL;
                                delete(this->out); this->out=NULL;
                                delete(this->file); this->file=NULL;
                                pinMode(I2SO_DATA, OUTPUT);
                                digitalWrite(I2SO_DATA,false);
                                this->publish_state(false);
                        }
                } 

        }

        void write_state(bool state) override {
                if(state && !this->file) {
                        DEBUGf("%s: init i2s %s", this->get_name().c_str(), state ? "ON" : "OFF");
                        this->file = new AudioFileSourceHTTPStream("http://home-assistant/old-car-engine_daniel_simion.wav");
                        this->file->RegisterStatusCB(statusCBFn, (void *) "AudioFileSourceHTTPStream");
                        // Create a buffer using that stream
                        this->buff = new AudioFileSourceBuffer(this->file, 2048);
                        this->buff->RegisterStatusCB(statusCBFn, (void *) "AudioFileSourceBuffer");
                        this->out = new AudioOutputI2SNoDAC();
                        this->out->RegisterStatusCB(statusCBFn, (void *) "AudioOutputI2SNoDAC");

                        this->wav = new AudioGeneratorWAV();
                        this->wav->RegisterStatusCB(statusCBFn, (void *) "AudioGeneratorWAV");

                        uint32_t free = ESP.getFreeHeap();

                        DEBUGf("%s:wav->begin, free=%d", this->get_name().c_str(), free);
                        if(this->wav->begin(this->buff, this->out)) {
                                DEBUGf("%s: started playing", this->get_name().c_str());
                        } else {
                                DEBUGf("%s: failed to play", this->get_name().c_str());
                        }
                        this->publish_state(state);
                }
        }

        ~EsphomeAudio() {
                DEBUGf("%s:~EsphomeAudio", this->get_name().c_str());
                if(this->file)
                        this->file->RegisterStatusCB(NULL, NULL);

        }
private:
        AudioGeneratorWAV *wav;
        AudioFileSourceHTTPStream *file;
        AudioOutputI2SNoDAC *out;
        AudioFileSourceBuffer *buff;

};

Posts: 1

Participants: 1

Read full topic

@Klagio wrote:

I am using an AIMesh system, so I have various routers with the same SSID but of course each router has a different MAC.

Is it possible to tell to connect to that specific router instead of choosing it random?

Posts: 5

Participants: 3

Read full topic

@Klagio wrote:

Anyone did this? My opengarage works pretty well, exept I can’t receive info on the WiFi signal, and wish to integrate all my projects under ESPhome

Posts: 1

Participants: 1

Read full topic

@LUNZ wrote:

I saw this project for a WiFi Duck where you can use a small esp8266 as a usb keyboard to send keyboard commands to a computer using ducky script. I thought maybe this functionality to use an esp8266 as a usb HID keyboard could eventually be implemented in ESPHome. Combined with AutoHotKey, this could create some really powerful automations on your computer.

There is already this software to control a Windows PC over MQTT but the downside is that you have to install it on the PC and there are some limitations on what you can run or execute.

What are some cool automations or use-cases for a USB keyboard emulator can you think of?

Posts: 2

Participants: 2

Read full topic

@GleDel wrote:

Hello, I have these old Christmas lights lying around that look like this:

IMG_20191126_084420.jpg4608×2112 1.06 MB

Would it be possible to just cut the wire and put a sonof basic inbetween? Or does sonof require a higher voltage?

Also, the adaptor has a built in button to change the lights pattern.

Posts: 2

Participants: 2

Read full topic

@thatguy_za wrote:

Hello

I’ve setup esphome on a WeMos D1 mini with a CT clamp on A0 but the calibration doesn’t seem to be working. I’ve pretty much copied and pasted the code from the example. My readings currently bounce between 0 and 0.12 and don’t change if I remove the calibration.

sensor:
  - platform: ct_clamp
    sensor: adc_sensor
    name: "Measured Current"
    update_interval: 60s
    filters:
      - calibrate_linear:
          - 0 -> 0
          - 0.12 -> 18

TIA!

Posts: 4

Participants: 2

Read full topic

@Benedev wrote:

Hi everyone,

I bought a cheap WiFi Light Bulb a few days ago. It uses the “Lumary” app which I found out to be identical to Tuya or Smart Life, so I tried to flash a custom firmware using tuya-convert. And voíla, it worked right away. After finding out the correct GPIO Pins (it uses an ESP8266) using Tasmota, I flashed ESPHome with the RGBWW component (the bulb supports warm and cold white). My ESPHome config looks as follows:

  
light:
  - platform: rgbww
    name: "Schreibtischlampe"
    red: output_red
    green: output_green
    blue: output_blue
    cold_white: output_coldwhite
    warm_white: output_warmwhite
    cold_white_color_temperature: 7000 K
    warm_white_color_temperature: 2700 K
  
output:
  - platform: esp8266_pwm
    id: output_red
    pin: GPIO5
  - platform: esp8266_pwm
    id: output_green
    pin: GPIO4
  - platform: esp8266_pwm
    id: output_blue
    pin: GPIO13
  - platform: esp8266_pwm
    id: output_coldwhite
    pin: GPIO14
  - platform: esp8266_pwm
    id: output_warmwhite
    pin: GPIO12

The integration to Home Assistant works, however, and that is my problem, there seems to be a bug (or I missed some config, however the Docs don’t show many options). When setting the bulb to white, I can’t adjust the brightness. It kind of changes the color temperature, but not the brightness when adjusting the brightness slider. A similiar issue has been reported here long time ago, however no answer was provided.

Brightness changing works btw fine when setting any other color than white.

Hope somone can help, thanks in advance

Posts: 1

Participants: 1

Read full topic