jonathanadams / esphome-configs Goto Github PK

After getting a good deal of the way through writing an entry for an RGBWW bulb which I've been playing with recently, I went looking at existing configs to see whether any made mention of tuya-convert, as that's the simplest way to get up an running. When I found one which mentions tuya-convert, I realised that the bulb in question seems to be a clone of the one I've been working with!

What's the preferred way to handle this situation? A couple of options (other than adding a whole duplicate config) which spring to mind are:

• Add a config for my bulb, which just lists the name etc (and perhaps includes a photo of the bulb and/or packaging) but simply links to the existing config
• Edit the existing config to add a list of "aliases" or "clones", listing my bulb as one

Kogan-Smarterhome-Smart-Plug-Energy-Meter-5v-24a-Usb-Ports

Just received a delivery and it only has one LED on the unit. This LED is blue and only illuminates when the relay is off (as per the config). No LED illuminates when the device is powered on.

The Kogan website still shows the picture with two LEDs. This picture is the new variant.

Add place for pictures of devices in template.

https://shelly.cloud/product/shelly-2/

Add an page that will display all devices at /devices.

Separate code from markdown to then use esphome to check the configs.

It should make this possible: #27 (comment)

We could use jekyll when generating the site to embed the code in the web page.

At the moment device type pages and device electrical standard pages are generated by creating a file for each type or standed in the relevant collection.

I am looking to possibly automate this via Jekyll Generators to avoid having to create pages for each device type and electrical standard. Instead a generator could possibly look for the type: or standard: in the front matter to generate the pages automatically on build.

My Ruby skills are none existant so help is needed for this.

Hope this helps someone :) But i dont know how to get this in here:

Analog to: https://templates.blakadder.com/gosund_SP111_v1_4.html

substitutions:
  device_name: gosund-sp111-v14
  device_name_upper: "SmartPlug 01"
# Change these to your values
  current_res: "0.0012"
  voltage_div: "771"


#######################
#                 GOSUND SP111              
#######################

# WiFi connection
wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
#  reboot_timeout: 0s
#  ssid: "abc"
#  password: "12345678"
  ap:
    ssid: "${device_name}"
#    password: "12345678"

# Enable Home Assistant API
api:
  password: !secret api_password
  reboot_timeout: 36h

# Enable OTA-Flashing
ota:
  password: !secret ota_password

# Enable Web server
web_server:
  port: 80

# Enable Captive Portal
captive_portal:

# Text sensors with general information
text_sensor:
  - platform: version
    name: ${device_name}_version

# Sync time with Home Assistant
time:
  - platform: homeassistant
    id: homeassistant_time

esphome:
  name: ${device_name}
  platform: ESP8266
  board: esp8285

sensor:
  - platform: hlw8012
    sel_pin:
      number: GPIO12
      inverted: True
    cf_pin: GPIO05
    cf1_pin: GPIO14
    current_resistor: ${current_res}
    voltage_divider: ${voltage_div}
    change_mode_every: 3
#    initial_mode: CURRENT
    update_interval: 5s
    current:
      name: "Current"
      unit_of_measurement: A
      accuracy_decimals: 3
    voltage:
      name: "Voltage"
      unit_of_measurement: V
      accuracy_decimals: 1
    power:
      name: "Wattage"
      unit_of_measurement: W
      accuracy_decimals: 0
   #   filters:
   #   - multiply: 0.5
      id: "Wattage"
  - platform: total_daily_energy
    name: "Total Daily Energy"
    power_id: "Wattage"
    filters:
        # Multiplication factor from W to kW is 0.001
        - multiply: 0.001
    unit_of_measurement: kWh

binary_sensor:
  # Binary sensor for the button press
  - platform: gpio
    name: button
    pin:
      number: GPIO13
      inverted: true
    on_press:
      - switch.toggle: relay

switch:
  # Switch to toggle the relay
  - platform: gpio
    id: relay
    name: relay
    pin: GPIO15
    on_turn_on:
      - light.turn_on: led
    on_turn_off:
      - light.turn_off: led

output:
  # Relay state led
  - platform: esp8266_pwm
    id: state_led
    pin:
      number: GPIO02
      inverted: true

light:
  # Relay state light
  - platform: monochromatic
    output: state_led
    id: led

# Uses the red LED as a ESPhome status indicator
status_led:
  pin:
    number: GPIO00
    inverted: true

Add a field for the version number of ESPHome the device has been tested/used with.

If there are breaking changes between ESPHome releses this will allow people to see if the device has been used/tested with their version. However this will require the device configurations to be kept up to date.

Hi,

Bought 4 lonsonho bulbs from the link you have in the doc and failing with tuya-convert. It's looping with:

SmartConfig complete.
Resending SmartConfig Packets

Found in smarthack-web.log this:
WARNING: it appears this device does not use an ESP82xx and therefore cannot install ESP based firmware

Kinda disappointing as I was keen to integrate it into my Home Assistant as ESPHome device. SmartLife app is fine and has IFTTT to fiddle with but still...

Can't seem to remove the internals yet but do you think it's possible to flash Tasmota via serial connection?

Opened one bulb: https://imgur.com/gallery/Lkg8xtP Looks like ESP chip, tbh, but can't be sure until I take it out

https://shelly.cloud/shelly-25-wifi-smart-relay-roller-shutter-home-automation/

Hi, I'm adding a Aoycocr X10S to ESPHome.
I find that the power measurements do not match those reported by my PR10 power meter.

Per the comments the hlw8012 resistor and divider values were copied from the AWP04L template.
I wonder if the Teckin SP20 may not be a better match, or if a bit of reverse engineering with actual measured component values is required?

Compare:
https://esphome-configs.io/devices/teckin-sp20/
https://github.com/jonathanadams/esphome-configs/blob/master/_devices/Teckin-SP20/Teckin-SP20.md
and
https://esphome-configs.io/devices/aoycocr-x10s/
https://github.com/jonathanadams/esphome-configs/blob/master/_devices/Aoycocr-X10S-Plug/Aoycocr-X10S.md

Maybe @akennerly can advise, as he did the integration?

Hello @jonathanadams,

Thank you for all your effort on this great resource to the ESPHome community!

I wanted to start an issue on this repo to about forking this project. ESPHome is moving at a very fast pace and it's my goal to open the project up to a larger set of maintainers who can more actively manage this great resource. I have been discussing with the ESPHome community on Discord and to start, we would really like to create a new github org for this project, so we can invite a group of moderators to more actively maintain the content.

-Ryan

Hi, Thx for you work with the Arlec-Grid-Connect-Smart_LED-Globe-CWWW config. I've flashed my light with it and can now do transitions, but when I try to turn it off using the Homes Assistant entity the log shows
[11:53:48][D][light:273]: State: OFF
[11:53:48][D][light:303]: Transition Length: 1.0s
but nothing happens. It just stays on.

Recently added devices list on the homepage does not display in order.

• Requires the addition of a date/time field option to the front matter on the devices files.
• Existing devices will need updating with new field.
• The adding new devices page will need updating.

Hi and first thanks for proposing this!

The Lonsonho-9W-E27-RGBWW-bulb.md (almost) works with these light bulbs: https://www.kogan.com/au/buy/kogan-smarterhome10w-rgb-cct-colour-warmcool-white-smart-bulb-e27-pack-2/

There is 1 glitch: in Home Assistant the "Brightness" and "Light Value" sliders need to be swapped. Sliding the brightness slider currently makes the light warmer/whiter, and sliding the light value one makes it more or less white.

I'm not sure how to fix this, can you please advise how to edit the .yaml?

https://shelly.cloud/shelly-1pm-wifi-smart-relay-home-automation/

I recently submitted two devices to the repo, the QIACHIP and KTNNKG RF relays. Both of them had a picture in them called 'top.jpg.' It looks like the top.jpg from the QIACHIP folder appears on both the QIACHIP and KTNNKG pages.

https://esphome-configs.io/devices/qiachip-smart-switch/
https://esphome-configs.io/devices/ktnnkg-wifi-kg2201-w/

Maybe just not having two top.jpg files in separate folders is the best option here, but this wasn't obvious when I first made the pull request.

Thanks for the great resource. As noted, I used the configuration from MJ-SD01 and applied it as is to the Tessan Dimmer (MJ-SD02).

Everything seems to be a perfect mapping. However I noticed that in the "off" state, the LEDs flicker, which I did not notice on the MJ-SD01.

In looking at the configuration, I believe the issue is caused by the lack of nesting of the if statements in the interval:

         if (dimmer_vals.is_on()) {
            id(dimmer_lvl) = dimmer_vals.get_brightness();
          }
          if (id(dimmer_lvl) > .19) { id(led2).turn_on(); }
          if (id(dimmer_lvl) < .20) { id(led2).turn_off(); }
          if (id(dimmer_lvl) > .39) { id(led3).turn_on(); }
          if (id(dimmer_lvl) < .40) { id(led3).turn_off(); }
          if (id(dimmer_lvl) > .59) { id(led4).turn_on(); }
          if (id(dimmer_lvl) < .60) { id(led4).turn_off(); }
          if (id(dimmer_lvl) > .79) { id(led5).turn_on(); }
          if (id(dimmer_lvl) < .80) { id(led5).turn_off(); }
          if (!dimmer_vals.is_on()) {
            id(led2).turn_off();
            id(led3).turn_off();
            id(led4).turn_off();
            id(led5).turn_off();
          }

Because the if (id(dimmer_lvl) > .19) { id(led2).turn_on(); } statements are not in the if (dimmer_vals.is_on()) block the LED lights are briefly toggled on prior to being turned of in the if (!dimmer_vals.is_on()).

This reorganization addresses the flickering, at least in my case.

          if (dimmer_vals.is_on()) {
            id(dimmer_lvl) = dimmer_vals.get_brightness();
            if (id(dimmer_lvl) > .19) { id(led2).turn_on(); }
            if (id(dimmer_lvl) < .20) { id(led2).turn_off(); }
            if (id(dimmer_lvl) > .39) { id(led3).turn_on(); }
            if (id(dimmer_lvl) < .40) { id(led3).turn_off(); }
            if (id(dimmer_lvl) > .59) { id(led4).turn_on(); }
            if (id(dimmer_lvl) < .60) { id(led4).turn_off(); }
            if (id(dimmer_lvl) > .79) { id(led5).turn_on(); }
            if (id(dimmer_lvl) < .80) { id(led5).turn_off(); }
          }
          if (!dimmer_vals.is_on()) {
            id(led2).turn_off();
            id(led3).turn_off();
            id(led4).turn_off();
            id(led5).turn_off();
          }

Hope this is helpful.

Again, great resource.

This is a classical tuya based device. I don't see any config using the tuya component (tuya:).
Is there any reason to avoid it ?
Do not hesitate to reject pull request and close issue if this is not relevant.