[ST Edge] •• Tasmota Edge •• for Sonoff, Tuya & many other ESP WiFi & HTTP devices - over 2000 Tasmota supported devices

Wondering about the virtual air conditioner capability. I successfully tested a virtual fan where I set the code and command strings using the web page provided by the Tasmota Edge driver.

For virtual air conditioners you just select the vendor in the settings. When I press a button on the Toshiba remote I see in the Tasmota log that it receives it as a Midea device (which isn’t a surprise). I also see the raw data displayed in the Received field of the IR Bridge. Pressing any button in the ST interface DOES send a Midea IRHVAC output record.

But, pressing a button on the remote shows the data received as Midea, the code shows in the IR Bridge received field, but none of the attributes in the virtual air conditioner change (power, temperature, mode, fan speed, etc.).

I also tried changing the vendor to Toshiba (which the remote and unit are labeled as) and it does the same - will output an IRHVAC now with Toshiba as the vendor, but doesn’t process the IRRecv.

Is the Virtual Air Conditioner code still under development, or do I have some other problem?

Here are some logcat entries from the Tasmota driver when testing using Midea as the vendor:

2023-07-26T23:44:19.916841068+00:00 PRINT Tasmota Edge [server:post:/j] For “IR Bridge”, Received: “{IrReceived={Data=“0XA10268FFFFE4”}, Mac=“C8C9A3C8B050”}”
2023-07-26T23:44:19.964564151+00:00 PRINT Tasmota Edge [cmd:event] For: “IR Bridge”, DNI: “AS:PHY:5f2ca884-48fc-4e1e-2ae4-a7ba32fb3bc0”, IP: “192.168.86.28”, Parsed: “{mac=“C8C9A3C8B050”, receivedData=“0XA10268FFFFE4”}”
2023-07-26T23:44:19.975464485+00:00 PRINT Tasmota Edge [cmd:event] For: “Virtual Air Conditioner”, Received: “0XA10268FFFFE4”

The child device “Virtual Air Conditioner” receives the code, but doesn’t seem to parse it and update the controls in the device.

Can I have the output of http://<-IP->/cm?cmnd=status 0 ?

The Virtual AC is a 1-way from ST to the AC. It is not able to update the ST AC with the actual state.

sonoff bridge ?
{“Status”:{“Module”:0,“DeviceName”:“Tasmota”,“FriendlyName”:[“Tasmota”],“Topic”:“tasmota_C3B0A3”,“ButtonTopic”:“0”,“Power”:1,“PowerOnState”:3,“LedState”:1,“LedMask”:“FFFF”,“SaveData”:1,“SaveState”:1,“SwitchTopic”:“0”,“SwitchMode”:[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],“ButtonRetain”:0,“SwitchRetain”:0,“SensorRetain”:0,“PowerRetain”:0,“InfoRetain”:0,“StateRetain”:0,“StatusRetain”:0},“StatusPRM”:{“Baudrate”:19200,“SerialConfig”:“8N1”,“GroupTopic”:“tasmotas”,“OtaUrl”:“http://ota.tasmota.com/tasmota/release/tasmota.bin.gz",“RestartReason”:"Software/System restart”,“Uptime”:“0T13:39:52”,“StartupUTC”:“2023-07-26T17:08:29”,“Sleep”:50,“CfgHolder”:4617,“BootCount”:48,“BCResetTime”:“2023-07-03T11:19:40”,“SaveCount”:118,“SaveAddress”:“F4000”},“StatusFWR”:{“Version”:“13.0.0(tasmota)”,“BuildDateTime”:“2023-06-26T10:42:07”,“Boot”:31,“Core”:“2_7_4_9”,“SDK”:“2.2.2-dev(38a443e)”,“CpuFrequency”:80,“Hardware”:“ESP8285N08”,“CR”:“404/699”},“StatusLOG”:{“SerialLog”:0,“WebLog”:2,“MqttLog”:0,“SysLog”:0,“LogHost”:“”,“LogPort”:514,“SSId”:[“MOLEHIYA-IOT”,“”],“TelePeriod”:300,“Resolution”:“558180C0”,“SetOption”:[“10008001”,“2805C80001000600003C5A0A192800000000”,“00000480”,“00006000”,“00004000”,“00000000”]},“StatusMEM”:{“ProgramSize”:634,“Free”:368,“Heap”:23,“ProgramFlashSize”:1024,“FlashSize”:1024,“FlashChipId”:“144051”,“FlashFrequency”:40,“FlashMode”:“DOUT”,“Features”:[“00000809”,“8F9AC787”,“04368001”,“000000CF”,“010013C0”,“C000F981”,“00004004”,“00001000”,“54000020”,“00000080”],“Drivers”:“1,2,3,4,5,6,7,8,9,10,12,16,18,19,20,21,22,24,26,27,29,30,35,37,45,62,68”,“Sensors”:“1,2,3,4,5,6”,“I2CDriver”:“7”},“StatusNET”:{“Hostname”:“RF-BRIDGE”,“IPAddress”:“192.168.2.47”,“Gateway”:“192.168.2.254”,“Subnetmask”:“255.255.255.0”,“DNSServer1”:“1.1.1.1”,“DNSServer2”:“4.2.2.1”,“Mac”:“C4:4F:33:C3:B0:A3”,“Webserver”:2,“HTTP_API”:1,“WifiConfig”:4,“WifiPower”:17.0},“StatusTIM”:{“UTC”:“2023-07-27T06:48:22”,“Local”:“2023-07-27T07:48:22”,“StartDST”:“2023-03-26T02:00:00”,“EndDST”:“2023-10-29T03:00:00”,“Timezone”:“+01:00”,“Sunrise”:“05:17”,“Sunset”:“20:36”},“StatusSNS”:{“Time”:“2023-07-27T07:48:22”},“StatusSTS”:{“Time”:“2023-07-27T07:48:22”,“Uptime”:“0T13:39:53”,“UptimeSec”:49193,“Heap”:24,“SleepMode”:“Normal”,“Sleep”:50,“LoadAvg”:19,“MqttCount”:0,“Wifi”:{“AP”:1,“SSId”:“IOT”,“BSSId”:“7E:8A:20:0F:4C:FB”,“Channel”:6,“Mode”:“11n”,“RSSI”:74,“Signal”:-63,“LinkCount”:4,“Downtime”:“0T00:01:02”}}}

No. I’d would need the output of this device; ultrasonic water level sensor TS-FT002.

Can I flash a shelly 1 with v8.0.1 to the tasmota v13?
I have many shelly 1 with tasmota 8.0.1 and these are no longer controlled by my smartthingshub.
I have already rolled out this edge driver from here and deleted the Shelly 1 but it is no longer found by the st hub.
The Tasmota Edge driver cannot be adjusted.
It always says “this device hasn’t updated all of its status information yet”

Please upgrade the Tasmota firmware to v11 or later. Yes. v13 works.

1 Like

Ok ready Updated to v13 but Smartthings finds nothing and in Tasmota Edge i cant do nothing.

by the way i have many shellys with tasmota 6.6.0 what is the right way to update these?
When i do.Ota Url Update the Version no changes

First of all, thank you for developing the wonderful tasmota edge driver. I have already successfully completed tasmota edge integration for SONOFF THR320D TH switch.

The tasmota firmware (ver.12.5.0) update for SONOFF DUAL R3 was also successfully completed, but it is limited to using edge driver with DUAL R3 in shutter(shade) mode. In the tasmota configuration, the shutter (shade) mode setting and calibration have been completed through the link below.

https://templates.blakadder.com/sonoff_DUALR3_v2.html
https://tasmota.github.io/docs/Blinds-and-Shutters/
Could you please update the edge driver so that DUAL R3 can be used as a shutter (shade) as well as a switch module?

Thanks in advance.

Is there a secret to making this work? Some configuration I am missing?

I have a Tasmota based ceiling fan controller that used to work fine with DTH driver for years but recently the SmartThings integration stopped working. I installed the Edge driver initially, did the search and it did show up, but there were no settings and the devices it allowed me to create were not working. I would expect some place to at least add the IP address of the actual Tasmota device, but I could not even find that. I deleted and re-added it several times. I read up some more and realized that I needed to upgrade my Tasmota firmware and remove the old DTH driver and its devices. I deleted the DTH devices but found no way to remove DTH driver itself, as the old console does not seem to be there anymore and it does not show up in the new console.

Anyway, once I upgraded Tasmota to latest (V13), removed the old devices, and reset the tasmota config - now it does not even show up when trying to add a device and it does not show up as a device brand or type to be added manually. What am I missing?

Thanks

Well, 24 hours later, it suddenly showed up - but the devices I created would not work - show as offline… a few hours later the devices started working, even thought I have not changed anything - but, gift horse, etc. It seems to work now. Thank you.

Has anyone managed to get this sensor running to be able to use in routines?
I’ve been playing around with it for some time now but can’t seem to get it to update. The 3 child sensors are there but unless I restart they don’t update their values. The Tasmota console is running perfectly.

UPDATE 10/08/2023
Today started updating the ST tiles, for no reason I can see here. Hadn’t touched it for nearly a week, don’t know if it was maybe my router that Eero pushed an update to last night.
Great :+1:

Is it possible to have one ESP8266 board assign a smoke sensor and relay capabilities?
I have homebrew integration between a factory security panel and my Tasmota board.
I can assign all switches and relays (and they work), but cannot figure out how to do sensors (particularly a smoke sensor) and switches/relays in one device.

Do you care to share how you did this?

Here is what I configured in the local Tasmota Edge site for the HTTP Switch (which appears in Smartthings):

Thanks for sharing.

I setup an RGB strip and it functions correctly from the controls but when trying to create a routine the color control screen is empty (no color picker or sliders, just a blank page). I can only turn it on and off. Sharptools allows setting colors.

I don’t know if this is a Tasmota issue or ST App problem, has anyone experienced this?

Is the virtual device as a smoke/CO2 sensor not available in the list? I added it as a contact sensor, but it’s not appearing in the list of smoke sensors in SmartThings security. How can I add it as a smoke sensor?

Hello, first of all, thanks for this tasmota edge.
One question, can I put here 2 codes with an “or” or something?
IMG_20230815_121554_186

It appears fine on iOS. Are you using Android? Maybe is ST app problem.

Smoke sensor is available. CO2 is not. There is no CO2 capability that has only detected/clear states. CO2 is a measurement/range level.

Under the Contact Sensor settings, and select profile = smoke detector.

It supports only 1 code. Do you have devices that send more than 1 code?

I don’t have a Dual R3 that I can try. If you can open a port forward to your Dual R3 for me to try, I can take a look.