@sparkydave Yeah, use Tasmota
after the debacle with 1.14.x I’m not touching Esphome unless there is no other way. That nodemcu STILL won’t work on Esphome and no one seems interested in fixing it.
Zac I have also got a kogan kettle and have got it updating in HA as sensor in degress celcius.
I am getting some blank periods pop up as it looks like I get three different MQT result in HA
dpid1 - I can get the temp from this result
dpid5 - I can get the temp from this result
the last one has no dpid associated its just the standard {“TuyaReceived”:{“Data”:“55AA000000010101”,“Cmnd”:0,“CmndData”:“01”}}
Also all I have done in the Tasmota console is “setoption66 1” running tasmota 7.1.2 standard
Just wondering if you get three different MQT responses as above
Have a look at the template, I updated it.
55AA000000010101 is just heartbeat.
I use dpid 5 as it will publish every time temp changes, whereas dpid 1 is every 5 seconds.
Let me know if you need more help
Hi all. I have a Kogan video doorbell. I’m trying into add it to the Tuya app but can find it when I select add device. Should I select camera under security
Anyone tried the new rgb ± cct bulbs?
I added my Kogan AC to the Tuya app and it is appearing in HA. The only issue is that it shows the temp as 240c, which is obviously wrong
Anyone had this issue?
I recently converted all my Kogan Smart Plugs (both new and old type) into ESPHome and calibrated them using a fixed draw incandescent bulb and an in-line power meter for accurate readings (~+/- 2v, +/- 0.1W). The only things that don’t work properly are the LEDs, but I don’t care about those. For anyone interested, the ESPHome configurations are below:
Old Kogan Plugs (thicker size, no USB):
substitutions:
devid: <DEVICEID>
devname: <DEVICENAME>
devicon: <DEVICEMDIREF>
esphome:
name: $devid
platform: ESP8266
board: esp8285
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_pass
# Enable logging
logger:
# Enable Web Server (optional)
web_server:
port: 80
# Enable Home Assistant API
api:
ota:
switch:
- platform: gpio
id: led
pin:
number: GPIO13
inverted: true
- platform: gpio
name: $devname
pin: GPIO14
id: relay
icon: $devicon
time:
- platform: homeassistant
id: homeassistant_time
sensor:
- platform: hlw8012
sel_pin:
number: GPIO12
inverted: true
cf_pin: GPIO4
cf1_pin: GPIO5
current:
name: $devname Current
unit_of_measurement: A
voltage:
name: $devname Voltage
unit_of_measurement: V
power:
name: $devname Power
unit_of_measurement: W
### HIGHER VALUE GIVES LOWER WATTAGE
current_resistor: 0.000812
### LOWER VALUE GIVES LOWER VOLTAGE
voltage_divider: 2100
New Kogan Plugs (2x 2.4a USB):
substitutions:
devid: <DEVICEID>
devname: <DEVICENAME>
devicon: <DEVICEMDIREF>
esphome:
name: $devid
platform: ESP8266
board: esp8285
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_pass
# Enable logging
logger:
# Enable Web Server (optional)
web_server:
port: 80
# Enable Home Assistant API
api:
ota:
switch:
- platform: gpio
id: led
pin:
number: GPIO13
inverted: true
- platform: gpio
name: $devname
pin: GPIO14
id: relay
icon: $devicon
time:
- platform: homeassistant
id: homeassistant_time
sensor:
- platform: hlw8012
sel_pin:
number: GPIO12
inverted: true
cf_pin: GPIO4
cf1_pin: GPIO5
current:
name: $devname Current
unit_of_measurement: A
voltage:
name: $devname Voltage
unit_of_measurement: V
power:
name: $devname Power
unit_of_measurement: W
### HIGHER VALUE GIVES LOWER WATTAGE
current_resistor: 0.00215
### LOWER VALUE GIVES LOWER VOLTAGE
voltage_divider: 799
Has anyone managed to get working ESPHome config for the smart kettle?
You should be able to ‘convert’ the Tasmota template posted above to work out the GPIO and create the ESPhome config. I did this once for a different device
See here:
Hey all,
I’m having a bit of trouble getting the temperture information included in the mqtt output. I’ve compiled Tasmota firmware with Option66 enabled, but that doesn’t seem to have done the trick.
I’ve had a ready through the comments above and can’t work out what I’m missing.
Is there an extra step that I’ve missed?
Thanks in advance.
Hey Zacnut,
Did you make any changes to the firmware config before compiling it? I have the same kettle but am struggling to get the current temperature out of it. I enabled setoption66 but the temp isn’t being output to mqtt. It’s also not displayed in the web ui.
Hey trankillity, you mention the LEDs not working, but do your physical buttons work on the new 2x USB plugs? No matter what I try, I can’t seem to get these to function.
Haven’t checked in a while, but I believe so.
Judging by my code above, GPIO14 is the relay.
- platform: gpio
name: $devname
pin: GPIO14
id: relay
icon: $devicon
Yeah I have the same. Unfortunately not working…
binary_sensor:
- platform: gpio
id: toggle
pin:
number: GPIO0
mode: INPUT_PULLUP
inverted: true
internal: true
on_press:
then:
- switch.toggle: relay
- - -
- platform: gpio
name: "$device"
pin: GPIO14
id: relay
icon: "$icon"
restore_mode: "$restore_mode"
Hi all, I got these light bulbs that I flashed using ESPHome and tuya-covert, here is the .yaml:
output:
- platform: esp8266_pwm
id: red
pin: GPIO4
- platform: esp8266_pwm
id: green
pin: GPIO12
- platform: esp8266_pwm
id: blue
pin: GPIO14
- platform: esp8266_pwm
id: cold_white
pin: GPIO5
- platform: esp8266_pwm
id: warm_white
pin: GPIO13
Brightness and Color picker work outside of the box in HA but not the Color Temperature feature:
Welcome to the forum
did you set the light as rgbw in the ESPhome yaml file?
eg:
light:
- platform: rgbw
name: Ensuite Downlight
red: output_red
green: output_green
blue: output_blue
white: output_white
Thanks for the quick reply and sorry for my ignorance, just discovered the difference between rgbw and rgbww!
I flashed it as a “custom rgbww” I think, like this:
Inspired by the /cw-ww-and-colour-temperature-slider-support-in-custom-light-output/148098/10 thread I can only put 2 links in a post
try the code I provided, modified to suit your name and ID’s