Did you get a chance to look at this. I’m wondering if it might be better to keep the device as a single channel dimmer with the option to select which tasmota channel to use. Thoughts?
can someone put a video of what they can control with the Virtual Air Conditioner (HVAC)?
I have Blitzwolf IR (https://templates.blakadder.com/blitzwolf_BW-RC1.html)
do I need to make any changes or just flash and use the Virtual Air Conditioner (HVAC)?
Anyone got any ideas how to modify the existing single channel dimmer device to support dual channel? Looks like the device responds to standrd tuya commands for power1 power2 channel1 channel2:
20:49:21 CMD: tele/tasmota_57CF7C/STATE
20:49:21 SRC: WebConsole from 192.168.0.6
20:49:21 CMD: Group 0, Index 1, Command “STATE”, Data “”
20:49:21 RSL: stat/tasmota_57CF7C/RESULT = {“Time”:“2020-12-14T20:49:21”,“Uptime”:“7T21:09:32”,“UptimeSec”:680972,“Heap”:26,“SleepMode”:“Dynamic”,“Sleep”:10,“LoadAvg”:99,“MqttCount”:0,“POWER1”:“ON”,“Channel1”:100,“POWER2”:“ON”,“Channel2”:100,“Color”:“FFFF”,“Wifi”:{“AP”:1,“SSId”:“indigo-priv”,“BSSId”:“AC:86:74:EC:66:A3”,“Channel”:11,“RSSI”:62,“Signal”:-69,“LinkCount”:7,“Downtime”:“0T00:04:34”}}
20:49:22 TYA: Send “55aa00000000ff”
It looks like it is possible, however I don’t have any ETA for this.
I just encountered the child device creation issue. It appears ST broke the child device creation. I’ll look into it.
1 Like
Hi, did you ever manage to get any power readings?
I’m having similar issues with an esp8266 set as a generic metering switch,
thanks
Could you update & publish the latest codes? Remove and create the device again. I think it should fix the child device creation issue.
Under http://[Your Tasmota Device IP]/cm?cmnd=status 0
Do you see something similar like this?
Then under http://[Your Tasmota Device IP]/cs?
Do you get similar to this?
I’m not getting similar to that no?
I am using a wemos D1 mini, as Generic (18) with a CT coil on the A0 pin.
The device was getting created and showing up as a hub child device but they were not showing up on home page.
After working with ST support I ended up resolving this issue by deleting my Samsung account and then creating a new one and setting everything up from scratch. Now everything is working correctly.
@Daniel_Paulsen, I’m glad you got this resolved. In my case I avoid deleting and recreating all devices at all costs, since there are near 200.
SmartThings now has the capability of using Sonoff devices that have not been Tasmotized. I just connected a Sonoff Mini to SmartThings. This required 2 steps: First I had to connect the Mini to eWeLink and Second I added my eWeLink devices to SmartThings.
SmartThings lists both Sonoff and eWeLink as brands that work with SmartThings. However, I couldn’t get the Mini to pair directly with SmartThings as a Sonoff device.
1 Like
Thanks for creating this, has been working brilliantly for my tuya and sonoff devices - now I want to attempt something a bit more DIY, some weight scales, as per this hookup video:
Fully supported in Tasmota, but i’m guessing as there is no device handler for it yet wouldn’t work with tasmota connect? is it possible to have a generic device handler that just displays what value the device is sending? ie weight in this case
Hi @hongtat , I created s virtual switch turn on and off my TV. However the command and data are the same (samsung). I wrote the data on the monitoring field to track the device state. It works for turning it on but it doesn’t update for turning it off even though the data is received in the IR Bridge. Any thoughts?
@barrie, thanks, I wasn’t aware of that. Have just read about it at eWeLink has officially integrated with SmartThings
@hongtat, regarding the POW R2, there’s a small piece of functionality that @GaryMilne wrote into his now-defunct DH called “Operating State”, which was very useful for me when used in webCoRE.
It allows for a setting of “standbyThreshold” in watts.
- If the power consumption of the electrical device connected to the POW R2 is zero, the operating state is considered to be Off.
- If the power consumption of the electrical device connected to the POW R2 is above zero but below the standby threshold, the operating state is considered to be Standby.
- If the power consumption of the electrical device connected to the POW R2 is above the standby threshold, the operating state is considered to be On.
If you perchance had the time and inclination to add this to your DH, is this kind of customization even possible in the new ST app?
1 Like
Hello Hongtat,
I am able to successfully setup the tasmota connect with smartthings. one thing that I am looking for is to have multiple schedules during the day but current setup only allows one setting for power on and power off. could you suggest how can I have multiple schedule ?
Today I flash all my shelly with Tasmota firmware, and after add in ST with your best smartapp!
One question, with a standard Shelly I can change light or socket and in ST I see correctly light, but with firmware tasmota and template shelly1 I see socket. Is possible change? Thank you Screenshot_20210103-091907|230x500
Hi @hongtat, one question on those TUYA WIFI Door Sensors. Does the App supports those devices? What type they would be? A On/Off switch? Does it have battery monitoring? The Tasmota firmware have that information for Battery (custom firmware).
tried but I’m not happy, I have a lot of lag on my shellys. Would anyone know how to go back to shelly firmware if possible ??