I was wondering if the portisch firmware on the RF (433mhz) Sonoff Bridge with tasmota firmware is compatible with Smartthings? I’m reluctant to install portisch if it’s going to break the edge driver compatibility. I have several devices that are not showing up and I read that the portisch firmware allows for a greater frequency map.
No. It doesn’t. This Human Presence Sensor is using ESPhome firmware (not Tasmota).
Yes. It is compatible.
2 Likes
FYI - It’s a bug in the new ST Advanced user app.
2 Likes
Thank you for your prompt response. I update to the Portisch firmware but now I need to enter Rfraw 177 code at the console for my remotes to even register the signal. This has to be done every so often. Is there a solution to this or will I need to go back to the original tasmota sonoff firmaware. If so where could find that firmware file. Thanks again for your help!
This is the expected procedure for using Portisch firmware in Tasmota.
Please follow the commands in the Tasmota docs - Commands - Tasmota
1 Like
Awesome, thank you so much! I’m now running a web request to ensure rfraw is always running. The old code in the gateway specifically the " Code that represents the “Button 1” state" no longer seems to work. I updated it to the new rfraw code and that still doesn’t work. Is there something I’m not doing right? I think I’m missing something. thanks again for all your help.
The “code that represents the button” state has to be the Itead default firmware code for it to work. It doesn’t work with RFraw code.
You have to disable it after sending RFraw code, so that the Itead default firmware code will work.
Example:
Backlog RfRaw AAb0....55; RfRaw 0
Celsius:off does indeed match the Fahrenheit setting in the app.
I noticed when you switch the setting in the Settings of the driver, it doesn’t convert from what you had there. You can see on your own example this happened.
Obviously you had just switched from C to F, and the value for Temp remained the same. When the switch from F to C happens, the app shows a wildly high temperature reading right after you switch - just an FYI.
OK – so, I guess I still have more Tasmota debugging to do with the HVAC… must be something in the IR commands getting ignored for the celsius setting. I’m going to have to post on the library Tasmota uses (crankyoldgit) for more clarification as to what is happening with my particular HVAC model from Carrier, and why his Carrier IR doesn’t work… Thanks!
Modifying the setting doesn’t change or trigger anything, you’ve to manually trigger an action on the app to take effect.
@MagicMike @ragoss @pmd2003 @Robie @JuvsGamer @W5LZR @Andy_Barac @Cesar_Novo @k0jdd @Avron and other users.
Can I check with you whether the new ST firmware 0.48.05 is able to resolve your unresponsive Tasmota devices issue.
ST firmware has this fix -
Fixed a rare issue where LAN Drivers/Devices become unresponsive. If you had encountered this issue, you would have needed to reboot your Hub to fix the problem.
Yes it seems to have fixed the issue.
I never saw this a rare occurrence as it was happening daily.
Update was pushed to me on Wednesday July 5.
So far all is well. If anything changes I will report back.
- K0JDD
| hongtat HONGTAT TAN
July 7 |
- | - |
@MagicMike @ragoss @pmd2003 @Robie @JuvsGamer @W5LZR @Andy_Barac @Cesar_Novo @k0jdd @Avron and other users.
Can I check with you whether the new ST firmware 0.48.05 is able to resolve your unresponsive Tasmota devices issue.
ST firmware has this fix -
Fixed a rare issue where LAN Drivers/Devices become unresponsive. If you had encountered this issue, you would have needed to reboot your Hub to fix the problem.
The ‘rare issue’ seems to be fixed now. Thanks.
It seems to be fixed…
Thanks!
hello, would there be a way to add a code for AC?
Thanks in advance
Hi, no.
Is your AC listed here ? The virtual AC uses the Tasmota IRHVAC command to control your AC.
If your AC is not supported, then you’d have to submit your AC codes here, which will be pulled into Tasmota firmware, and you can use it.
seems fixed too… thanks!
Thank you, i’ll try
Seems to be working. I removed all but one device in the meantime.