Hi im having an issue with rf ive created an rf momentry button and added the remote code but when i press it nothing happens. Any help would be great .
Thanks
Martin
@v.porsio @bega00 @macazzlst - A recent change on the ST platform breaks it. A fix for this issue has been pushed and you should receive the update soon. Thanks for reporting the issue.
2 Likes
Temperature control in the virtual AC is working now 
I started getting this issue in the last few days, it seems that overnight it starts showing the error “RESULT = {“WebQuery”:“Connect failed”}”, I then reboot the HUB and a new port is assigned an all works as expected for the next day or so and then the issue reoccurrs. Trying to access the driver from a web browser as hubIP:port also fials until the new port is assigned by the reboot. This has been happening for the past week.
Hello @hongtat, now the commands works but the display of my ac is off. Do you think that could be possible to edit the commands setting the “light” as on?
Thx
I have the same issue. Using it as contact sensors for doors and windows, and I’m starting to think of another solution as it is happening too often. @hongtat said this is a problem with ST and there is nothing he can do to fix it. @nayelyz ST needs to fix their end?
Hello, could you add/modify the SCD40 in sensors?
Your driver correctly generate 5 child devices (I have 2 sensors installed) but CarbonDioxide and eCO2 are created both like CO2, and the eCO2 child device doesn’t work properly, it show the value some times and mainly are in “connected” status without any value:
this is the log:
{“Status”:{“Module”:18,“DeviceName”:“Tasmota”,“FriendlyName”:[“Tasmota”],“Topic”:“tasmota_1ADF0C”,“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”:115200,“SerialConfig”:“8N1”,“GroupTopic”:“tasmotas”,“OtaUrl”:" “,“RestartReason”:“External System”,“Uptime”:“0T00:22:02”,“StartupUTC”:“2023-05-20T15:48:12”,“Sleep”:50,“CfgHolder”:4617,“BootCount”:19,“BCResetTime”:“2023-03-29T20:38:31”,“SaveCount”:350,“SaveAddress”:“F6000”},“StatusFWR”:{“Version”:“12.4.0.4(allsensors)”,“BuildDateTime”:“2023-03-27T14:34:59”,“Boot”:31,“Core”:“2_7_4_9”,“SDK”:“2.2.2-dev(38a443e)”,“CpuFrequency”:80,“Hardware”:“ESP8266EX”,“CR”:“369/699”},“StatusLOG”:{“SerialLog”:2,“WebLog”:2,“MqttLog”:0,“SysLog”:0,“LogHost”:”“,“LogPort”:514,“SSId”:[“ASUS”,”“],“TelePeriod”:300,“Resolution”:“558180C0”,“SetOption”:[“00008009”,“2805C80001000600003C5A0A192800000000”,“00000080”,“00006000”,“00004000”,“00000000”]},“StatusMEM”:{“ProgramSize”:743,“Free”:260,“Heap”:14,“ProgramFlashSize”:1024,“FlashSize”:4096,“FlashChipId”:“16405E”,“FlashFrequency”:40,“FlashMode”:“DOUT”,“Features”:[“00000809”,“8F909787”,“04046001”,“FFFFB7CF”,“8F7417FB”,“303E0AD3”,“1159785A”,“26204FFF”,“5408F0F3”,“00000080”],“Drivers”:“1,2,3,4,7,8,9,10,12,14,15,20,24,28,29,34,43,47,50,60,62,63,66”,“Sensors”:“1,2,3,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,24,26,27,29,30,31,32,38,40,41,42,44,45,46,50,51,54,55,56,57,58,59,63,64,65,66,67,70,71,72,73,74,75,76,78,79,81,82,85,86,88,89,90,91,92,93”,“I2CDriver”:“1,!2,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,28,29,30,31,32,34,35,36,40,41,42,43,44,45,46,48,49,50,51,52,53,55,56,58,60,61,62,63”},“StatusNET”:{“Hostname”:“tasmota-1ADF0C-7948”,“IPAddress”:“192.168.66.153”,“Gateway”:“192.168.66.254”,“Subnetmask”:“255.255.255.0”,“DNSServer1”:“192.168.66.254”,“DNSServer2”:“0.0.0.0”,“Mac”:“80:7D:3A:1A:DF:0C”,“Webserver”:2,“HTTP_API”:1,“WifiConfig”:4,“WifiPower”:17.0},“StatusMQT”:{“MqttHost”:”“,“MqttPort”:1883,“MqttClientMask”:“DVES_%06X”,“MqttClient”:“DVES_1ADF0C”,“MqttUser”:“DVES_USER”,“MqttCount”:0,“MAX_PACKET_SIZE”:1200,“KEEPALIVE”:30,“SOCKET_TIMEOUT”:4},“StatusTIM”:{“UTC”:“2023-05-20T16:10:14”,“Local”:“2023-05-20T17:10:14”,“StartDST”:“2023-03-26T02:00:00”,“EndDST”:“2023-10-29T03:00:00”,“Timezone”:”+01:00",“Sunrise”:“05:02”,“Sunset”:“20:30”},“StatusSNS”:{“Time”:“2023-05-20T17:10:14”,“SCD40”:{“CarbonDioxide”:1170,“eCO2”:1244,“Temperature”:24.8,“Humidity”:55.6,“DewPoint”:15.3},“TempUnit”:“C”},“StatusSTS”:{“Time”:“2023-05-20T17:10:14”,“Uptime”:“0T00:22:02”,“UptimeSec”:1322,“Heap”:14,“SleepMode”:“Dynamic”,“Sleep”:50,“LoadAvg”:19,“MqttCount”:0,“Wifi”
Could you add microwave distance sensor LD2410?
your driver generate a child device called Distance LD2410 but doesnt get the value.
there 3 values in tasmota UI:
this is the log:
{“Status”:{“Module”:18,“DeviceName”:“Tasmota”,“FriendlyName”:[“Tasmota”],“Topic”:“tasmota_578BDC”,“ButtonTopic”:“0”,“Power”:0,“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”:255900,“SerialConfig”:“8N1”,“GroupTopic”:“tasmotas”,“OtaUrl”:“”,“RestartReason”:“External System”,“Uptime”:“0T01:07:43”,“StartupUTC”:“2023-05-20T15:27:49”,“Sleep”:50,“CfgHolder”:4617,“BootCount”:5,“BCResetTime”:“2023-05-20T12:20:08”,“SaveCount”:15,“SaveAddress”:“F9000”},“StatusFWR”:{“Version”:“12.5.0(TasmoCompiler-esp82664M)”,“BuildDateTime”:“2023-05-20T11:02:16”,“Boot”:31,“Core”:“2_7_4_9”,“SDK”:“2.2.2-dev(38a443e)”,“CpuFrequency”:80,“Hardware”:“ESP8266EX”,“CR”:“368/699”},“StatusLOG”:{“SerialLog”:0,“WebLog”:2,“MqttLog”:0,“SysLog”:0,“LogHost”:“”,“LogPort”:514,“SSId”:[“”,“”],“TelePeriod”:300,“Resolution”:“558180C0”,“SetOption”:[“00008009”,“2805C80001000600003C5A0A192800000000”,“00000080”,“00006000”,“00004000”,“00000000”]},“StatusMEM”:{“ProgramSize”:924,“Free”:1120,“Heap”:14,“ProgramFlashSize”:4096,“FlashSize”:4096,“FlashChipId”:“16405E”,“FlashFrequency”:40,“FlashMode”:“DOUT”,“Features”:[“00000410”,“8F8A458F”,“04260001”,“7FFE37CF”,“5F6C13F5”,“D83EFCC1”,“0A6D78DE”,“00201000”,“5400E0E0”,“00008480”],“Drivers”:“1,2,3,4,5,6,8,9,10,12,18,19,22,24,26,29,30,35,37,38,45,50,62”,“Sensors”:“1,2,3,4,5,6,7,8,9,10,11,14,15,16,17,18,19,20,21,22,24,26,27,29,31,38,39,41,42,44,45,46,47,55,56,57,58,59,63,64,65,66,67,70,71,72,73,74,76,77,88,89,91,92,93,102,103”,“I2CDriver”:“7,8,9,10,11,12,15,16,17,18,19,20,21,22,24,28,29,30,31,32,36,40,41,42,43,45,46,48,49,50,51,52,54,60,61,62,63,76”},“StatusNET”:{“Hostname”:“tasmota-578BDC-3036”,“IPAddress”:“192.168.66.150”,“Gateway”:“192.168.66.254”,“Subnetmask”:“255.255.255.0”,“DNSServer1”:“192.168.66.254”,“DNSServer2”:“0.0.0.0”,“Mac”:“48:3F:DA:57:8B:DC”,“Webserver”:2,“HTTP_API”:1,“WifiConfig”:4,“WifiPower”:17.0},“StatusMQT”:{“MqttHost”:“”,“MqttPort”:1883,“MqttClientMask”:“DVES_%06X”,“MqttClient”:“DVES_578BDC”,“MqttUser”:“DVES_USER”,“MqttCount”:0,“MAX_PACKET_SIZE”:1200,“KEEPALIVE”:30,“SOCKET_TIMEOUT”:4},“StatusTIM”:{“UTC”:“2023-05-20T16:35:32”,“Local”:“2023-05-20T17:35:32”,“StartDST”:“2023-03-26T02:00:00”,“EndDST”:“2023-10-29T03:00:00”,“Timezone”:“+01:00”,“Sunrise”:“05:02”,“Sunset”:“20:30”},“StatusSNS”:{“Time”:“2023-05-20T17:35:32”,“LD2410”:{“Distance”:[216.0,222.0,199.0],“Energy”:[0,100]}},“StatusSTS”:{“Time”:“2023-05-20T17:35:32”,“Uptime”:“0T01:07:43”,“UptimeSec”:4063,“Heap”:15,“SleepMode”:“Dynamic”,“Sleep”:50,“LoadAvg”:28,“MqttCount”:0,“Wifi”:
thanks
1 Like
Would be great, as this sensor could be really useful.
Slightly off thread, but I haven’t been able to see that much in Tasmota. How did you implement the integration?
I just compiled a bin using tasmocompiler and adding the instruction to use the LD2410
Very simple
Ok, I’ve seen some references to that, but I need to do some more homework there! I have one in the drawer, awaiting for it to be included in the all-sensors-bin (!). As all the sensors I’ve bought have worked so well with the Tasmota Edge driver, for the price, and the feedback it has, it seemed obviously worth trying.
I can send my bin if you want
1 Like
That would be great. Much appreciated Vincenzo!
Are there any plans to allow sensors, such as DHT only devices, to be added without a switch? I see only two options today for a device with only a single sensor using AM2301. Neither of the solutions are ideal.
- Add a TH Switch and then just ignore the switch, but you can still use the sensor values for automation rules
- Check the box to discover sensors, which will add a device that is only the temperature sensor, but you still have a switch that isn’t useful.
Can you add a device like when the temperature sensor is discovered, but just the sensor device without adding a dummy switch? I understand you might need a parent device for the settings, but being a switch means it shows up in Alexa and Google Home as well. Some sort of custom sensor detection device maybe?
That worked!
Thank you
Does it work if you send the code directly on the RF bridge?
Does it work if you connect just one of the sensors (CO2 or eCO2) ?
It reads a single Distance, e.g. {“Distance”:216}. It doesn’t support {“Distance”,[216,222,199]}. Are you able to split them into “LD2410-1”:{“Distance”:216}, “LD2410-2”:{“Distance”:222},“LD2410-3”:{“Distance”:199}…
The SCD40 provide these data togheter, I can’t choose to use only one of them
I don’t have the skills to do that, but could be possible to split them in tasmota firmware?
thanks
@hongtat I got the IR bridge working, trying to get the IR Virtual Air Conditioner to work but running into issues.
I have a Carrier AC unit – the selection Carrier_AC64 does not work. However, strangely enough the selection following on the list Coolix does work!?? Is there possibly some index that’s off by 1 in your code?
Also I don’t understand why there is only one Carrier selection in your software. It seems that there are multiple codes in the CrankyOldGit library that is being used.
The Tasmota IR Bridge code I am using is 12.5.0 on ESP8266
Hi @hongtat
Works great the Dust Sensor, but in Tasmota with Vindriktning it’s possible to have 3 readings, PM1, PM2.5 and PM10,
{“Time”:“2023-05-30T13:46:46”,“ANALOG”:{“Range”:42},“VINDRIKTNING”:{“PM1”:2178,“PM2.5”:311,“PM10”:396}}
Any chance of seeing them all?
1 Like
