Serial MCU controlled relay/switch

Message

saundersrg · #51 Post by **saundersrg** » 16 Dec 2017, 06:35

enesbcs wrote: ↑13 Dec 2017, 17:16

If you have a Sonoff Dual R2 there are no more MCU, relays are directly attached to 8285 GPIO, you have to choose R2 modell in Tasmota, or use GPIO directly in ESPEasy
https://github.com/arendst/Sonoff-Tasmo ... nd-Dual-R2

If you have an old Sonoff Dual, then please read the first post of this thread, and use the binary attached to it. If it is not working for some reason and this board is definitely is not an R2, then you can test with ESPEasy+SER2NET plugin the serial status messages, that this board reply when you short the onboard button0 and button1 pins.
[/quote]

Well, from what I've seen it's a V2 not R2. Compiled the binary into Dev 11, no luck. Will try out SER2NET in the next couple of days. Thanks!

saundersrg · #52 Post by **saundersrg** » 16 Dec 2017, 06:37

grovkillen wrote: ↑13 Dec 2017, 13:34
If you take a picture of the board we might see if the ESP MCU is doing the actual pulling of the relay or if they (itead) has started to put in a middle hand MCU which is controlled via the ESP MCU.

EDIT: sorry, I see that it is in fact discussed in this thread. It i a serial controlled MCU. So how are you trying to make the relay trigger? Using serial commands?

Not able to trigger at all, it's like the relays are disconnected entirely. Have tried 3 different firmwares and none work.

Will try the suggestion of SER2NET and see what I can get.

saundersrg · #53 Post by **saundersrg** » 16 Dec 2017, 07:39

saundersrg wrote: ↑16 Dec 2017, 06:35
Well, from what I've seen it's a V2 not R2. Compiled the binary into Dev 11, no luck. Will try out SER2NET in the next couple of days. Thanks!

SER2NET sadly returns absolutely nothing. The LED changes on the unit when closing button 0 / 1 jumpers, but the relays themselves don't seem to fire.

enesbcs · #54 Post by **enesbcs** » 16 Dec 2017, 09:50

saundersrg wrote: ↑16 Dec 2017, 07:39 SER2NET sadly returns absolutely nothing. The LED changes on the unit when closing button 0 / 1 jumpers, but the relays themselves don't seem to fire.

If the relay do not fire when you physically close button jumpers, i think it is simply a faulty one.

Was it worked with the original firmware? I always try every Sonoff that i get with the original firmware, before i flash it. Can you post pictures from the panel (back&front)?

mixycsabi · #55 Post by **mixycsabi** » 19 Dec 2017, 11:49

Same situation here...

[Edit]
Sorry, my mistake... I used wrong bin file.
After when I chose a good file, everything works fine

saundersrg · #56 Post by **saundersrg** » 29 Dec 2017, 15:21

enesbcs wrote: ↑16 Dec 2017, 09:50 If the relay do not fire when you physically close button jumpers, i think it is simply a faulty one.
Was it worked with the original firmware? I always try every Sonoff that i get with the original firmware, before i flash it. Can you post pictures from the panel (back&front)?

In a sad twist, the dual was the only one that I a) didn't test beforehand and b) didn't dump the original firmware beforehand.

I will perhaps fiddle again sometime, for now it's been packed in a box.

Images here:

Chips to right of ESP8266EX are as follows from what I can see.

XTX
BN25F08
1(?)644Q0R

SIL
F330
B0GAZ
1624+

itanczos · #57 Post by **itanczos** » 25 Jan 2018, 12:24

Hello nesbcs!

Is it possible to use button1 or button2 input for pulse counting? Or is it possible to count impulse with Sonoff Dual?

(Van arra lehetőség, hogy a 2 gomb bemenetet figyeljük és impulzus számlálásra használjuk? Vagy egyéb más lehetőség Sonoff Dual-lal? A lefordított binárisban benne van az impulzus számláló plugin?)

enesbcs · #58 Post by **enesbcs** » 25 Jan 2018, 18:47

itanczos wrote: ↑25 Jan 2018, 12:24 Hello nesbcs!

Is it possible to use button1 or button2 input for pulse counting? Or is it possible to count impulse with Sonoff Dual?

(Van arra lehetőség, hogy a 2 gomb bemenetet figyeljük és impulzus számlálásra használjuk? Vagy egyéb más lehetőség Sonoff Dual-lal? A lefordított binárisban benne van az impulzus számláló plugin?)

I am not familiar with the P003 Pulse plugin, however, it is compiled in the binary. If P003 is not watching GPIO's but device variables, it can work... but because the serial communication, i doubt that it will be fast.

riker1 · #59 Post by **riker1** » 28 Jan 2018, 15:31

@enesbcs,

just to let you knwo lc tech is also available with 2 relais

http://www.chinalctech.com/index.php?_m ... &p_id=1261

mabye you can update your plugin to support 2 releais.

Thanks T

enesbcs · #60 Post by **enesbcs** » 28 Jan 2018, 21:17

riker1 wrote: ↑28 Jan 2018, 15:31 @enesbcs,
just to let you knwo lc tech is also available with 2 relais

http://www.chinalctech.com/index.php?_m ... &p_id=1261

mabye you can update your plugin to support 2 releais.
Thanks T

Good to know, LCTECH 2 relay support added, i compiled binaries for ESPEasy Mega, R147 and R120 for testing, attached to this post.

riker1 · #61 Post by **riker1** » 29 Jan 2018, 07:57

perfect thanks
will try to test

riker1 · #62 Post by **riker1** » 29 Jan 2018, 15:18

Hi
I tried the R147 but did not manage to switch the relay.

as there are 3 relays , I assume only first 2 are mapped to LCTech .

but cmd=relay,0,1 does not switch anything.

any way to monitor debug this?

if I http://192.168.0.143/control?cmd=relay,1,1 then in relay1 in device overview it is not reflected. relay1 is still 0
it is only working for relay0, showing 1 , after switching. (but not the relay itself).

how do serial definition interact?

maybe it should be good to have a variable baud rate also in the plugin.

enesbcs · #63 Post by **enesbcs** » 29 Jan 2018, 19:47

riker1 wrote: ↑29 Jan 2018, 15:18 Hi
I tried the R147 but did not manage to switch the relay.

as there are 3 relays , I assume only first 2 are mapped to LCTech .

but cmd=relay,0,1 does not switch anything.

any way to monitor debug this?

if I http://192.168.0.143/control?cmd=relay,1,1 then in relay1 in device overview it is not reflected. relay1 is still 0
it is only working for relay0, showing 1 , after switching. (but not the relay itself).

how do serial definition interact?

maybe it should be good to have a variable baud rate also in the plugin.

You can see the ESPEasy log about details.

Th plugin sends the following commands:
relay,0,1 = A0 01 01 A2
relay,0,0 = A0 01 00 A1
relay,1,1 = A0 02 01 A3
relay,1,0 = A0 02 00 A2

In the documentation, i found 115200 as the recommended speed. It is weird, it was 9600 in the one relay version. Now i made the speed selectable in the plugin.
New test version attached to this post. I made some nasty mistakes in the previous binary, as this plugin created for ESP Mega WEBFORM LOAD/SAVE versions originally. I think i corrected it, sorry.

riker1 · #64 Post by **riker1** » 30 Jan 2018, 08:37

Hi

thanks a lot for the fast support.

a lot of progress.

Now I can switch relay with 115200 baut.

Problem is:
relais open and close directly with command relay,0,1 : open and immediate close after half a second without any command.

Do you have and idea?

Thanks a lot

enesbcs · #65 Post by **enesbcs** » 30 Jan 2018, 19:19

riker1 wrote: ↑30 Jan 2018, 08:37 Problem is:
relais open and close directly with command relay,0,1 : open and immediate close after half a second without any command.

Do you have and idea?

The LCTECH 1 relay version is reported to be veery slow, so i send every on and off command twice, this worked until now. It seems that this 2relay version is faster, and maybe does not tolerate multiple ON commands? Anyway i compiled a new binary with a new option "Use command doubling". (attached) Please make sure to set it off, and reboot the ESP if needed. In the ESPEasy Tools->Log menu you can see the sent commands.
I have no more idea at software level.

On hardware side:
The device has a chinese documentation, describing the S1 and S2 buttons, and below that some text says - according to Google Translator - that Mode2 is the phone mode, when these serial commands can be executed. Also this panel has some undocumented jumpers...
This LCTech 2 relay module is a strange thing, the original Itead module have a button that can choose between inching/self-lock mode:
https://www.itead.cc/inching-self-locki ... witch.html

riker1 · #66 Post by **riker1** » 30 Jan 2018, 20:01

Hi
I tested it, but not really a difference.

I tried mode 1 and 2 , no change

same with the jumper, without jumpers, no switching at all.

Vendor is saying: Under normal conditions, the Jumpers should be plug on the board. You'd better unplug the jumpers when you need send AT conmand to debug the ESP8266, the function of the jumpers is avoid the UART disturbance that from STM8S003/N76E003

with AT Firmware ,
switching : echo -e '\xA0\x01\x01\xA2' | nc -q 1 192.168.0.143 8080
the relay persists in position open .

all strange.

Thanks for your help

enesbcs · #67 Post by **enesbcs** » 30 Jan 2018, 21:09

riker1 wrote: ↑30 Jan 2018, 20:01 with AT Firmware ,
switching : echo -e '\xA0\x01\x01\xA2' | nc -q 1 192.168.0.143 8080
the relay persists in position open .

all strange.

Strange indeed.
In ESPEasy under Tools->Advanced, the Enable serial port is unchecked and Serial log level is 0?

There are also a P020 Serial Server plugin in ESPEasy, that you can test directly with nc.

(I am using 2.4.0-rc2 core to compile, so if in my binary the P020 plugin also does not works, than maybe R147 needs to be compiled with 2.3.0)

riker1 · #68 Post by **riker1** » 01 Feb 2018, 12:18

Hi
nc is not working with serial server for this relay. Not sure why.

disable command doubling option does not help. relay is closing immediatly.

I follow two approaches:
AT-Firmware
and EspEasy.

Now I recognized that relay is rebooting the ESP (with AT Frimware) after switching a relay. this is not stable.

I think I throw this out of the window. LC Tech is not supporting and relay is instable

Thanks for your work

cheers T

enesbcs · #69 Post by **enesbcs** » 01 Feb 2018, 17:39

riker1 wrote: ↑01 Feb 2018, 12:18 Now I recognized that relay is rebooting the ESP (with AT Frimware) after switching a relay. this is not stable.

It's very sad, i am very curious about new gadgets.

There were no such errors with the LCTech 1 relay version.. maybe the relays draw to much current + the power supply is not stable enough. Perhaps you can try to apply a 1000uf capacitor between the ESP 3.3V power line and GND to stabilize.
https://iot-playground.com/images/artic ... titled.png

TD-er · #70 Post by **TD-er** » 01 Feb 2018, 19:36

enesbcs wrote: ↑01 Feb 2018, 17:39
riker1 wrote: ↑01 Feb 2018, 12:18 Now I recognized that relay is rebooting the ESP (with AT Frimware) after switching a relay. this is not stable.
It's very sad, i am very curious about new gadgets. There were no such errors with the LCTech 1 relay version.. maybe the relays draw to much current + the power supply is not stable enough. Perhaps you can try to apply a 1000uf capacitor between the ESP 3.3V power line and GND to stabilize.
https://iot-playground.com/images/artic ... titled.png

Please note that an empty capacitor will draw as much current as it can get.
Depending on the capacity of the capacitor, it may take some time.
So if you're using bigger capacitors, it may very well be you can overload (damage) the power regulator that stabilizes the 3.3V.
Those 3V3 versions are often not the most powerful ones.
When a separate 3V3 line is present, which powers the ESP, you may want to add a small resistor (order of 1 ... 10 Ohm) between the power and the ESP and put such a capacitor directly over the Vcc and GND lines of the ESP.

If the 3V3 comes from an onboard stabilizer, like on a NodeMCU, I would suggest to add the capacitor over de 5V line instead.

riker1 · #71 Post by **riker1** » 02 Feb 2018, 08:30

Hi
I am using a b3603 buck converter.
showing esp01 only on 80mA and additional 50 mA for each relay. Power should be stable.

I set input power to 5 V 1 A, when 2 Relay were open, current was 200mA.

Hard to put resistors and capacitator in the relay ESP is onboard plugged on.

maybe it is also possible to control / program the onboard STM8S003 SWIM.

hard to give up....

riker1 · #72 Post by **riker1** » 05 Feb 2018, 15:34

Hi
good news,

problem was related to power supply via breadboard.

all working now. Thanks for your support.

will p165 be part of a normal release?

compiling a release myself failed with always different errors....

TD-er · #73 Post by **TD-er** » 05 Feb 2018, 17:08

riker1 wrote: ↑05 Feb 2018, 15:34 [...]
will p165 be part of a normal release?

compiling a release myself failed with always different errors....

If it is considered stable, you can always make an issue for it on Github.
I think there are lots of plugins on the playground which may benefit others.

enesbcs · #74 Post by **enesbcs** » 05 Feb 2018, 18:45

TD-er wrote: ↑05 Feb 2018, 17:08
riker1 wrote: ↑05 Feb 2018, 15:34 [...]
will p165 be part of a normal release?

compiling a release myself failed with always different errors....
If it is considered stable, you can always make an issue for it on Github.
I think there are lots of plugins on the playground which may benefit others.

Plugin is currently working only with Arduino core 2.4.0-rc or newer, so compilation with default settings is not straightforward. I think the plugin status is better than "DEVELOPMENT", but reported to run out of memory on Sonoff Dual after a month uptime. On my Tuya wall light switch, i have no such problems, but it is moderately used by me. So i guess my plugin falls under "TESTING" category.
The supported 3 type of hardware: Sonoff Dual, Tuya touch light switch and LCTech relays is not typically used as sensors (only a few GPIOs accessible) so i remove a lots of plugin before compiling it, for speed and size reasons.
I think i will offer pre-compiled binaries in 3 versions for users who have problems with compilation:
1. ESPEasy Mega 4MB/1MB SPIFFS
2. ESPEasy Mega 1MB/128k SPIFFS
3. ESPEasy R147 1MB/64k SPIFFS (legacy version for PUYA - SPIFFS not used in this release, but checked by ESPEasy to be greater than 0 for some reasons)

In these binaries i will include the following:
Controllers: All (C001-C011)
Notification plugins: All (N001-N002)
Plugins: P165 SerSwitch, P001 Switch, P002 ADC, P003 Pulse, P020 Ser2Net (for debugging purposes), P021 Level, P026 Sysinfo, P029 Output, P033 Dummy, P037 MQTTImport, P043 ClkOutput (not sure if it can be useful for this devices), and for in case also including my Modemsleep plugin P166 just in case.

If anyone has other needs, write it.

riker1 · #75 Post by **riker1** » 05 Feb 2018, 19:48

Hi
that sounds great.

one hint maybe.

looks like for lc Tech relays with 2 relays, only statsu of 1. rleay is send to fhem

message is rel:on rel:off

but only for first relay0 not relay1

thanks Thomas

enesbcs · #76 Post by **enesbcs** » 05 Feb 2018, 22:24

riker1 wrote: ↑05 Feb 2018, 19:48 one hint maybe.

looks like for lc Tech relays with 2 relays, only statsu of 1. rleay is send to fhem

message is rel:on rel:off

but only for first relay0 not relay1

Yes from the beginning this device reports itself as SWITCH, and in ESPEasy it can report exactly one value, the first. This is why i am using Rules, to report back each relays separately, as this mentioned in the first post.
To address this issue, now i changed it to SENSOR_TYPE_TRIPLE and tried to change it according the selected number of buttons.
Hint: if selecting the LCTECH type for the first time in the device settings, please refresh the page and Submit another time, after selecting the number of buttons, and other options, to make sure to save it.
Binary attached to the first post of this thread:
download/file.php?id=1930

riker1 · #77 Post by **riker1** » 06 Feb 2018, 07:38

Hi

ok top thanks

will try

it is working,
only small thing. relay names must be short to be distinguished in fhem:
fhem is showing Rel: 0 Rel: 0

changed in EasyESP : shorter names : R1: 0 R2: 0 appears in fhem

Thanks

dent · #78 Post by **dent** » 01 Mar 2018, 18:30

Hi!

Thank you very much taking the time to produce this. I admire your work here and greatly appreciate what you accomplished.

I have recently purchased a Tuya clone 1-gang wall switch from aliexpress. I like them since they don’t have any branding in the glass pane like sonoff and their glass cover color matches the case color.

I’ve disassembled the switch, luckily I saw the pins out there with labels on the back.

I am quite new to these things and don’t have any electronics background but have some programming knowledge. I had previously flashed sonoff devices with tasmota with success and have embedded them into my home assistant network running on a raspberry pi 3. On the other hand, I have tried to use your firmware but to no luck. I have listed the steps I have followed below. I will be glad if you can help me figure out how to make it work with the device I have.

1) I connected the ESP8266 module to a raspberry pi 3 running on raspbian in flashing mode. I don’t have a USB-UART device, so I am limited to using linux based solutions for flashing
2) I downloaded the compiled version of your plugin for Tuya
3) I backed up the existing firmware using esptool.py (just in case I need to revert to the original firmware in the future)
4) power cycled, erased the existing firmware
5) power cycled, uploaded the new firmware, namely ESPEasy_Mega_P165_4M_1MS.bin from the zip file in the first post.
6) exited flashing mode (disconnected GPIO0 from ground) and power cycled
7) I was now able to see ESP_XXXX access point available in the wireless networks list. However, when I connected, I was unable to open the webpage on 192.168.4.1. I tried to ping and it worked, but the webpage did not show up
8) Still connected to raspberry pi, I ran miniterm.py to listen to the serial log. See the log output below. Seems like ESP was constantly rebooting itself due to an error (which I cannot figure out) and repeats the same error message continously.
9) I also tested powering the switch from a wall plug instead of raspberry pi, but the results were the same/

Any ideas how I can make this work? Is there something that I am missing?
By the way, the product works fine with the vendor app and other third party software on its original firmware.

Thanks!

ets Jan 8 2013,rst cause:2, boot mode:(3,7)

load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v4ceabea9
~ld
�U

INIT : Booting version: (custom)
INIT : Warm boot #10
FS : Mounting...
FS : Mount failed
FS : Mount failed
RESET: Resetting factory defaults...
RESET: Warm boot, reset count: 3
RESET: Too many resets, protecting your flash memory (powercycle to solve this)
CRC : No program memory checksum found. Check output of crc2.py
FS : Error while reading/writing config.dat in 1091

PID:0
Version:0
INIT : Incorrect PID or version!
RESET: Resetting factory defaults...
RESET: Warm boot, reset count: 3
RESET: Too many resets, protecting your flash memory (powercycle to solve this)

Exception (0):
epc1=0x4000e25d epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

ctx: cont
sp: 3fff3bf0 end: 3fff3e50 offset: 01a0

>>>stack>>>
3fff3d90: 3fff4e8c 00000100 00000001 40201980
3fff3da0: 40202a82 3fff4ebc 00000001 40202b88
3fff3db0: 00000000 0000001c 00000003 3fff4ea4
3fff3dc0: 3fffdad0 3fff2e20 3fff2d60 3fff2e20
3fff3dd0: 3fffdad0 00000001 3fff2d60 4022d0f8
3fff3de0: 00000000 0000001c 00000000 40202932
3fff3df0: 402018b6 3fff2d60 3fff1d48 40207e61
3fff3e00: 3fffdad0 3fff2d60 3fff1d48 402251ac
3fff3e10: 00000000 00000000 00000000 3fff4fc4
3fff3e20: 0000002f 00000014 feefeffe feefeffe
3fff3e30: 3fffdad0 00000000 3fff2e1a 4022ee20
3fff3e40: feefeffe feefeffe 3fff2e30 40100710
<<<stack<<<

itanczos · #79 Post by **itanczos** » 01 Mar 2018, 18:57

dent wrote: ↑01 Mar 2018, 18:30 ...
5) power cycled, uploaded the new firmware, namely ESPEasy_Mega_P165_4M_1MS.bin from the zip file in the first post.

Please try the ESPEasy_Mega_P165_1M_128kS.bin flash image.
I think this ESP module has only 1MB of flash.

itanczos · #80 Post by **itanczos** » 01 Mar 2018, 19:02

I'm using the downloadable P165_18 version.
The problem is that if I restart the router, it will not re-connect the ESPEasy to the router, but switch to the AP mode.
The rest of ESPEasy will re-connect to the router.

dent · #81 Post by **dent** » 01 Mar 2018, 19:25

Thanks for the quick response! I was able to connect to the device using the 1M version. Now it’s time to figure out the correct settings...
By the way, the physical button does not function at all after the flash. Does it have to do with the settings?

itanczos wrote: ↑01 Mar 2018, 18:57
dent wrote: ↑01 Mar 2018, 18:30 ...
5) power cycled, uploaded the new firmware, namely ESPEasy_Mega_P165_4M_1MS.bin from the zip file in the first post.
Please try the ESPEasy_Mega_P165_1M_128kS.bin flash image.
I think this ESP module has only 1MB of flash.

itanczos · #82 Post by **itanczos** » 01 Mar 2018, 19:43

Of course!
You must also set the button as an input device.

dent wrote: ↑01 Mar 2018, 19:25 Thanks for the quick response! I was able to connect to the device using the 1M version. Now it’s time to figure out the correct settings...
By the way, the physical button does not function at all after the flash. Does it have to do with the settings?

enesbcs · #83 Post by **enesbcs** » 01 Mar 2018, 22:44

This Kinco switch seems very interesting, on the Yewelink the main button works all the time, because that was hardwired to the MCU. Are you sure, that this switch communicates serially with an MCU?
If it is, you can try to enable all 3 button in the Serial MCU settings, then do a soft reboot and see if anything shows in log when you press the main button. And also see if relay,0,1 or relay,1,1 commands doing anything with the relay.
FYI there are some Tuya clone which does not use the serial API, instead using direct GPIO-s: (in this case buttons are controlled by the ESP and you have to code some logic (Rules) in the same way like the Sonoff Touch)
such as GPIO-12=RELAY,GPIO-5=PWR LED

barrymossel · #84 Post by **barrymossel** » 06 Mar 2018, 09:01

I ordered the Kinco switch yesterday and want to flash it to be used through Domoticz when it arrived. How would I know if this will work with any firmware?

---edit---
Hmm, the description on AliExpress says it uses the eWeLink app, just like Sonoff. Wouldn't that mean they function quite like the Sonoffs? So through the GPIO's?

enesbcs · #85 Post by **enesbcs** » 06 Mar 2018, 17:29

barrymossel wrote: ↑06 Mar 2018, 09:01 I ordered the Kinco switch yesterday and want to flash it to be used through Domoticz when it arrived. How would I know if this will work with any firmware?

---edit---
Hmm, the description on AliExpress says it uses the eWeLink app, just like Sonoff. Wouldn't that mean they function quite like the Sonoffs? So through the GPIO's?

I am afraid there are absolutely zero informations about Kinco switches, you can be the first who take apart one, measure with multimeter that which GPIO's connected to which relay if any.. as i do with my own switch.

1/ If you are lucky, the ESP GPIO's are connected directly to the relays, and can be used simply with some Rules in ESPEasy.
2a/ If not, you have to listen the serial communication between the ESP and the MCU modul (i did it with P20 Serial server plugin), if the packages starting with 0x55aa then they are using the Tuya protocol, and P165 plugin can be used. (Yewelink/TUYA) Tuya has published it's official serial API that is licensed by Yewelink, so it has to work.
2b/ If the packages starting with 0xA004 or 0xA000 then it is using the Sonoff protocol and can be used as a Sonoff Dual device also supported by this plugin.
3/ If none of the above then you are on your own.

barrymossel · #86 Post by **barrymossel** » 07 Mar 2018, 10:00

We will just have to wait I guess

But I can imagine that as it uses the same app as Sonoff (T1) switches, it might be compatible with ESPEasy + some rules.

I will take it apart as soon as I receive it!

enesbcs · #87 Post by **enesbcs** » 07 Mar 2018, 18:31

barrymossel wrote: ↑07 Mar 2018, 10:00 We will just have to wait I guess

But I can imagine that as it uses the same app as Sonoff (T1) switches, it might be compatible with ESPEasy + some rules.

I will take it apart as soon as I receive it!

The Sonoff Dual also uses EweLink app, but do not use direct GPIO controlling.. but hope dies last.

barrymossel · #88 Post by **barrymossel** » 07 Mar 2018, 19:47

Haha, let's keep hoping...

dent · #89 Post by **dent** » 13 Mar 2018, 20:14

I have managed to figure out that the Kinco switch uses the GPIO pin 4 to manage the relay.
I can turn it on and off using the commands but I am struggling with operating the physical button still. My initial idea was that it would be linked to one of the GPIO pins and I would be able to program a trigger that switches GPIO4 when the button is pressed.
I am checking the values of all GPIO pins and then pressing the button and then checking again. However, I don’t see any change in GPIO values.

Any thoughts how I can capture the physical button press?

enesbcs · #90 Post by **enesbcs** » 13 Mar 2018, 20:36

dent wrote: ↑13 Mar 2018, 20:14 I am checking the values of all GPIO pins and then pressing the button and then checking again. However, I don’t see any change in GPIO values.

Any thoughts how I can capture the physical button press?

If i were you, i would set up switches in ESPEasy to "Switch" devices for the following GPIO's:
GPIO-0
GPIO-2
GPIO-4
GPIO-5
GPIO-12
GPIO-13
GPIO-14
GPIO-15

Then when you touch the button, it will be in the ESPEasy logs.

dent · #91 Post by **dent** » 13 Mar 2018, 21:00

I did the following

: gpio setup.jpg (178.44 KiB) Viewed 113561 times

but can't see anything in the log when I press the button. any other thoughts?

enesbcs · #92 Post by **enesbcs** » 13 Mar 2018, 21:33

dent wrote: ↑13 Mar 2018, 21:00 I did the following

but can't see anything in the log when I press the button. any other thoughts?

I only see 4 gpio's on the picture. Can be GPIO12-GPIO13-GPIO14?
When you said "GPIO pin 4" you referring GPIO-4 as the picture below?

Perhaps you can trace back the GPIO's from ESP to the touch with a multimeter...

Also there is a CR302..whatever chip with 16 legs on the back side i can not read every letter from the picture, maybe the central K2 touch is connected to it's R2?? Could you find out what's this chip full name?

dent · #93 Post by **dent** » 13 Mar 2018, 21:47

Rest of the GPIOs were on the next page. Didn't take a screenshot of that. I have all the GPIO pins that are available defined as switches.

By GPIO4 I mean using the command - GPIO,4,0

Regarding the multimeter - I haven't used it for this purpose before. Should I connect the black line of multimeter to ground pin of ESP and test the red line with the other pins while pressing the button on and off? Or should I use the continuity mode somehow?

dent · #94 Post by **dent** » 13 Mar 2018, 22:00

enesbcs wrote: ↑13 Mar 2018, 21:33
dent wrote: ↑13 Mar 2018, 21:00 I did the following

but can't see anything in the log when I press the button. any other thoughts?
I only see 4 gpio's on the picture. Can be GPIO12-GPIO13-GPIO14?
When you said "GPIO pin 4" you referring GPIO-4 as the picture below?

Perhaps you can trace back the GPIO's from ESP to the touch with a multimeter...

Also there is a CR302..whatever chip with 16 legs on the back side i can not read every letter from the picture, maybe the central K2 touch is connected to it's R2?? Could you find out what's this chip full name?

it says:
CR302
B747U005PG4

nothing pops out in google when I search for it

enesbcs · #95 Post by **enesbcs** » 13 Mar 2018, 22:37

dent wrote: ↑13 Mar 2018, 22:00 it says:
CR302
B747U005PG4

nothing pops out in google when I search for it

It's a bit confusing, if the touch sensors not wired to ESP, than maybe it's some sort of touch controller (CR302) which is wired to ESP8266 serial/I2C/SPI i can not tell it from pictures.

I used the multimeter continuity function to backtrace wiring, more or less success.

Multiple layered PCB's are hard to backtrace.

enesbcs · #96 Post by **enesbcs** » 14 Mar 2018, 10:40

Attachments updated in the first post, plugin compiled against the new TurboCharge 20180311 ESPEasy Mega
viewtopic.php?f=6&t=3245&start=90#p16998

dent · #97 Post by **dent** » 14 Mar 2018, 23:42

I used a multimeter to measure the changes in voltage on my kinco touch switch and figured out that the voltage on the serial pin market with R changes (goes down to 0 depending on how long I press) when I touch the physical button. I guess now I have to figure out how to read serial pin values. I am quite new to the esp easy firmware, please forgive me if this is something trivial.

enesbcs · #98 Post by **enesbcs** » 15 Mar 2018, 09:07

dent wrote: ↑14 Mar 2018, 23:42 I used a multimeter to measure the changes in voltage on my kinco touch switch and figured out that the voltage on the serial pin market with R changes (goes down to 0 depending on how long I press) when I touch the physical button. I guess now I have to figure out how to read serial pin values. I am quite new to the esp easy firmware, please forgive me if this is something trivial.

Nice work, you are in the right direction.
Easy and ugly way if you have only one button on the Kinco:

In ESPEasy menu:
Tools->Advanced->Enable serial port (check box unticked - so disable!)
Tools->Advanced->Serial log level: None

Now you are able to create a Switch device on RX it's GPIO3, and see if it changes state in the log.

The harder way:
- Enable serial port usage, but disable serial logging, also disable all plugin (P165) and device that using serial pins.
- Setup "Communication - Serial Server" plugin for debugging (port 23, baud 9600, 8n1)
https://www.letscontrolit.com/wiki/index.php/Ser2Net
- install Realterm to your PC, setup for displaying in hexadecimal in Display menu, in Capture write the ESP device IP address and port (23) and set the serial settings that matches with the ESP Ser2Net plugin

In that way when you press the touch, you have to see the same Hex byte array - maybe two different: one when switching off, another when switching on. If you see only garbage or not the same numbers every time, you have to change bitrate on each of them and retry. If you can provide the correct hex array i can include in this plugin.

barrymossel · #99 Post by **barrymossel** » 17 Mar 2018, 08:59

It appears that the one I received is a bit different than the one posted before:

Also it doesn't use the EweLink app as described but the (Tuya?) SmartLife app. I am willing to open it up and experiment with it, but first I'll wait off the dispute with the seller as the front (the only reason why I bought this particular one) is different from the pictures (icons of lamps and can only be placed with the buttons op top of each other instead of next to each other).

dent · #100 Post by **dent** » 21 Mar 2018, 21:28

enesbcs wrote: ↑15 Mar 2018, 09:07
dent wrote: ↑14 Mar 2018, 23:42 I used a multimeter to measure the changes in voltage on my kinco touch switch and figured out that the voltage on the serial pin market with R changes (goes down to 0 depending on how long I press) when I touch the physical button. I guess now I have to figure out how to read serial pin values. I am quite new to the esp easy firmware, please forgive me if this is something trivial.
Nice work, you are in the right direction.
Easy and ugly way if you have only one button on the Kinco:

In ESPEasy menu:
Tools->Advanced->Enable serial port (check box unticked - so disable!)
Tools->Advanced->Serial log level: None

Now you are able to create a Switch device on RX it's GPIO3, and see if it changes state in the log.

The harder way:
- Enable serial port usage, but disable serial logging, also disable all plugin (P165) and device that using serial pins.
- Setup "Communication - Serial Server" plugin for debugging (port 23, baud 9600, 8n1)
https://www.letscontrolit.com/wiki/index.php/Ser2Net
- install Realterm to your PC, setup for displaying in hexadecimal in Display menu, in Capture write the ESP device IP address and port (23) and set the serial settings that matches with the ESP Ser2Net plugin

In that way when you press the touch, you have to see the same Hex byte array - maybe two different: one when switching off, another when switching on. If you see only garbage or not the same numbers every time, you have to change bitrate on each of them and retry. If you can provide the correct hex array i can include in this plugin.

I tried your suggestions and I am now able to command the switch and the leds on it trough GPIO commands. I set some rules, installed mqtt and now I am able to control the whole thing both physically and wireless.

I have also tried the 'hard way'. The hex output I see is "00" almost all the time when I press or hold the button. Is this normal or is "00" an error of some sort?
I have also purchased 2 and 3 gang versions and waiting for their delivery. I will let you know when I get them and try to find out their hex outputs.

Who is online