Does anyone know if this switch can be flashed to ESPHome?
https://github.com/arendst/Sonoff-Tasmota/issues/4003
I have it using Tasmota right now however I keep having disconnect issues so I am looking to try something different without needing to use MQTT.
From what I have read I guess it is basically a Generic ESP8266, but as ESPHome doesn’t have pre-compiled binaries I am not really sure how I would go about setting up the correct gpio pins.
calica
(Carlo J Calica)
April 13, 2019, 9:59pm
2
Lookup the template for the device. You can decide which pins are which with this wiki page
Alternative firmware for ESP8266 with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full do...
On that page is a link to the template DB too. If you need more help, let me know.
Hi Calica,
Thanks for the reply.
Looking at what I currently have selected in Tasmota,
GPIO13 is set to Tuya RX (108)
GPIO15 is set to Tuya Tx (107)
Does that mean I just need to add to the yaml?
switch:
- platform: gpio
name: "Basement"
pin: 13
- platform: gpio
pin: 15
These are dimmable switches but I don’t see anything that mentions dimming int ESPHome
calica
(Carlo J Calica)
April 21, 2019, 6:44am
4
Sorry looks like I was wrong. Seems Tuya has a separate microcontroller that handles dimming functions and the ESP talks to that via the pins you specified. ESPHome doesn’t support this. Probably wouldn’t be too difficult to add, given that Tasmota supports it. Relevant code:
https://github.com/arendst/Sonoff-Tasmota/blob/development/sonoff/xdrv_16_tuyadimmer.ino
That’s quite a bit of effort tho.
Also, dimming is handled by light components.
if you’re still interested i got it working using the following:
# MS-105 serial communication
uart:
rx_pin: GPIO13
tx_pin: GPIO15
baud_rate: 9600
# Register the Tuya MCU connection. Check your log for the correct values
tuya:
light:
- platform: "tuya"
name: "your_friendly_name"
dimmer_datapoint: 3
switch_datapoint: 1
min_value: 25
max_value: 255
How did you get this to work given that the TUYA MCU component in ESPHome is unidirectional except for ON/OFF???
I’ve requested a new feature to support this.
opened 03:10PM - 12 Nov 22 UTC
integration: tuya
<!-- READ THIS FIRST:
- This is for feature requests only, for issues please g… o to the issues repository.
- Please be as descriptive as possible, especially use-cases that can otherwise not be solved boost the problem's priority.
DO NOT DELETE ANY TEXT from this template! Otherwise the issue may be closed without a comment.
-->
**Describe the problem you have/What new integration you would like**
Add support to Tuya MCU to write to datapoints just like the Tuya iOT servers and Tasmota TuyaMCU can
OR Just like Tasmota can. Tragically, I've had to reflash away from ESPHome to Tasmota, because Tasmota supports this function. Not that I don't think Tasmota is useful, but mostly for lights and switches, not more complex devices like a Wood Pellet Stove. ESPHome is my GO TO Software for all things iOT. Or at least it used to be.
DP NUMBERS AND THEIR FUNCTION ON MY STOVE:
1 - Power on (Heat). <--- writable now
4 - Mode P1/P2/P3P4 <--- NOT writable but needs to be
101 - ECO1/ECO2 <--- NOT writable but needs to be
104 - Error Code <- READ ONLY
106 - Set Temp <--- NOT writable but needs to be
107 - Current Temp <- READ ONLY
108 - Pipe Temp <- READ ONLY
109 - Protect Temp <- READ ONLY
-----------------
TuyaSend Command[~](https://tasmota.github.io/docs/TuyaMCU/#tuyasend-command)
Command TuyaSend is used to send commands to dpId's. It is required for dpId's that shouldn't be mapped to a fnId.
With this command it is possible to control every function of the dpId that is controllable, providing you know its data type and data length. With them provided, the rest of the protocol command is calculated.
Command's value consists of two comma separated parameters: dpId and data.
TuyaSend<x> dpId,data**
----------------
**Please describe your use case for this integration and alternatives you've tried:**
I have a newly reflashed TYWE01 Tuya module on my misbehaving wood pellet stove (the oem vendor app has serious bugs) and the set temp dp controls the stove. It's the only way to set a desired temp on the stove. But there is no way to do this as dps are read only... climate controls don't work because there is no way to set the target temp inside the MCU of the stove. The only function that is bidirectional is the ON/OFF Switch which is dp 1. If you can do it for dp 1, why not the rest of them????
**Additional context**
The same issue exists with ECO Mode (0 & 1) and the P1-P4 (0-3) power levels. I can read those values set via the front panel of the stove thru Tuya MCU in ESPHome, but there is no way to set them like the vendor app can up to the tuya data points in the Tuya servers and then back to the stove. Tuya MCU is unidirectional only, and limited by design.
the hesterysis of the stove is 3 degrees below set temp and 1 degree above. So I physically have to touch the buttons on the stove to control anything but on/off.