hello everyone!
Someone was able to configure the Moess 3 way switch with Tasmota in ST?
If it works with Tasmota, it would work with Tasmota in ST. There is no difference, the firmware is the same. What is not working for you?
When I use the Moess 3 way SS01-1 Template and create a generic switch (1ch) in smartthings, the switch does not turn on or off the ligh and I can’t handle the real state of the light
Tasmota (Connect) is using Rule1 & Rule2. So, you’d have to use Rule3 in your rule set.
I am using tasmota connect with the Sonoff RF Bridge. I have 2 questions:
- How many devices can one Sonoff RF Bridge support?
- What Sonoff or other product can I use as a switch with the RF Bridge?
- I believe no limit.
- Most 433MHz
#[ST Offline] 5 sec lag between physical button trigger and actual switch response;
Preconditions:
- Samsung SmartThings Hub v3; v000.036.00005;
- Sonoff mini - Tasmota 9.3.1;
- App: Tasmota Connect 1.1.2;
Steps to reproduce:
- Connect Sonoff mini to Smartthings hub using Tasmota Connect app;
- Make ST hub offline;
- Trigger physical switch of Sonoff mini few times with less than 4 sec between clicks;
Expected result: No lag when using physical switch when ST hub is offline;
Actual result: 5 sec lag between physical button trigger and actual switch responce;
Log:
16:57:01.575 RSL: RESULT = {“Rule2”:“ON”,“Once”:“OFF”,“StopOnError”:“OFF”,“Length”:383,“Free”:128,“Rules”:“ON Power5#state DO WebSend [192.168.0.10:39500] /?json={“StatusSTS”:{“POWER5”:”%value%"}} ENDON ON Power6#state DO WebSend [192.168.0.10:39500] /?json={“StatusSTS”:{“POWER6”:"%value%"}} ENDON ON Power7#state DO WebSend [192.168.0.10:39500] /?json={“StatusSTS”:{“POWER7”:"%value%"}} ENDON ON Power8#state DO WebSend [192.168.0.10:39500] /?json={“StatusSTS”:{“POWER8”:"%value%"}} ENDON"}
16:57:01.730 RSL: STATUS11 = {“StatusSTS”:{“Time”:“2021-04-11T16:57:01”,“Uptime”:“0T00:34:49”,“UptimeSec”:2089,“Heap”:25,“SleepMode”:“Dynamic”,“Sleep”:50,“LoadAvg”:21,“MqttCount”:0,“POWER”:“ON”,“Wifi”:{“AP”:1,“SSId”:“Zhu”,“BSSId”:“52:FF:20:57:11:D1”,“Channel”:8,“RSSI”:100,“Signal”:-41,“LinkCount”:1,“Downtime”:“0T00:00:03”}}}
16:57:08.067 RSL: RESULT = {“POWER”:“OFF”}
16:57:08.070 RSL: POWER = OFF
16:57:08.100 RUL: POWER1#STATE performs “WebSend [192.168.0.10:39500] /?json={“StatusSTS”:{“POWER1”:“0”}}”
16:57:08.437 RSL: RESULT = {“WebSend”:“Done”}
16:57:20.425 RSL: STATE = {“Time”:“2021-04-11T16:57:20”,“Uptime”:“0T00:35:08”,“UptimeSec”:2108,“Heap”:27,“SleepMode”:“Dynamic”,“Sleep”:50,“LoadAvg”:19,“MqttCount”:0,“POWER”:“OFF”,“Wifi”:{“AP”:1,“SSId”:“Zhu”,“BSSId”:“52:FF:20:57:11:D1”,“Channel”:8,“RSSI”:100,“Signal”:-39,“LinkCount”:1,“Downtime”:“0T00:00:03”}}
16:57:20.435 RSL: SENSOR = {“Time”:“2021-04-11T16:57:20”,“Switch1”:“ON”}
16:59:11.841 RSL: RESULT = {“POWER”:“ON”}
16:59:11.844 RSL: POWER = ON
16:59:11.860 RUL: POWER1#STATE performs “WebSend [192.168.0.10:39500] /?json={“StatusSTS”:{“POWER1”:“1”}}”
16:59:16.912 RSL: RESULT = {“WebSend”:“Connect failed”}
16:59:16.999 RSL: RESULT = {“POWER”:“OFF”}
16:59:16.001 RSL: POWER = OFF
16:59:17.014 RUL: POWER1#STATE performs “WebSend [192.168.0.10:39500] /?json={“StatusSTS”:{“POWER1”:“0”}}”
16:59:22.035 RSL: RESULT = {“WebSend”:“Connect failed”}
16:59:40.485 RSL: RESULT = {“POWER”:“ON”}
16:59:40.488 RSL: POWER = ON
16:59:40.504 RUL: POWER1#STATE performs “WebSend [192.168.0.10:39500] /?json={“StatusSTS”:{“POWER1”:“1”}}”
16:59:45.587 RSL: RESULT = {“WebSend”:“Connect failed”}
16:59:47.017 RSL: RESULT = {“POWER”:“OFF”}
16:59:47.020 RSL: POWER = OFF
16:59:47.036 RUL: POWER1#STATE performs “WebSend [192.168.0.10:39500] /?json={“StatusSTS”:{“POWER1”:“0”}}”
16:59:52.264 RSL: RESULT = {“WebSend”:“Connect failed”}
17:02:16.963 RSL: RESULT = {“POWER”:“ON”}
17:02:16.966 RSL: POWER = ON
17:02:16.986 RUL: POWER1#STATE performs “WebSend [192.168.0.10:39500] /?json={“StatusSTS”:{“POWER1”:“1”}}”
17:02:22.055 RSL: RESULT = {“WebSend”:“Connect failed”}
17:02:22.435 RSL: RESULT = {“POWER”:“OFF”}
17:02:22.438 RSL: POWER = OFF
Any ideas how to avoid this lag?
It requires a hub to send & receive events. It wouldn’t work if you turn off the hub.
Thats clear. But is there a way to avoid timeout? Just send an event without waiting for response.
5 sec wait is configured somehow?
I just connected a 433 Mhz button with Tasmota connect that is used with an RF tasmotized Bridge. These buttons are such a good deal. 433 Mhz has proven to have an excellent range. I also ordered a dual relay unit that came with it. However the relay only had momentary capability and I wanted latching which it was supposed to have. Thank you Hong Tat for making this possible.
@hongtat Thank you for your amazing work and for your incredible assistance to all the questions here!
Please excuse my naivety over my own questions
I have a Sonoff ZBBridge - I wanted to use Aqara Door/Window sensors as they are a bit more compact than the Sonoff.
As is - the Aqara sensors appear to link to the Bridge - it appears in the subdevices list in the eWeLink app and the Sonoff gives a green LED Pulse as you open/close the sensor. However it does not show a change of state on the sensor in the app.
Also, in SmartThings, it does ‘find’ the Sensor when the eWeLink app is linked.
But again, the sensor does not change state when actuated.
My understanding is that if I Tasmotize the ZBBridge, then the Aqara sensor will pair properly to it.
But then how do I get it into ST - will your app work for this? (I don’t see any references to ZBBridge in the thread)
Note that I do not have an ST Hub currently, all my devices are currently connected directly into the App.
So can the Tasmotize of the ZBBridge work and then utilize your app to get it into ST?
Or should I just get Sonoff sensors instead!
This is for Wifi devices only and it requires a ST hub.
It doesn’t support Zigbee devices & bridge. It’s better to pair Zigbee sensors to a ST hub.
OK, thank you
i have some problem to use tasmota-connect.
i got sonoff basic with additional relay module on it (using gpio2).
in the tasmota web UI, I can control both of them but i can see only 1 switch in the ST.
i tried it with generic switch 1ch, 2ch but i couldnt make it.
the additional relay doesnt work with tasmota-connect??
thx for reading
It is not supported.
I flashed a Sonoff TH16 successfully and went to add tasmota-connect to my Smartthings via the IDE. I used the github repository method which completed and shows it was published however when I go to the phone app (latest version for IOS) I don’t see the smartapp listed. What’s strange is that I see it listed in the “My SmartApps” section of the webpage, but if I go to My Locations->Installed SmartApps it doesn’t appear there. I’ve tried adding a Category “Convenience” to the code, tried deleting and re-adding but with no success. The data handlers show up but not the SmartApp. I’ve added SmartApps before so I’m not sure what I could be missing here. I thought this would be the simplest part of the flash/add process but now I’m stumped. Appreciate any ideas or direction. Thank you!
Update: I tried to add the smartapp manually, I changed the name to “tasmota (Connect)2” just so I could visually see it and added a category line to the code set to “Convenience”. This time I the smartapp showed up in the “+” on my IOS app to add it, but when I chose it, it now doesn’t show in either the phone’s smartapps OR as a choice to add new. Just wanted to share that further analysis.
Please delete and reinstall the app again.
In the ST app,
- Under “Menu” > top right “settings” gear icon,
- Tap & hold “About SmartThings” for 5 seconds, the ST app should restart
- Under “Menu” > top right “settings” gear icon,
- Under “About SmartThings”, you will find “Developer mode”, enable it.
- You should be able to add custom smartapps now.
