I’ve been trying to get this going for a few days. Today, I was able to get the sensors connected initially, however after they initially connected and reported back they stopped and became unavailable. I have a Stampede RT-590 But all of the DPS numbers were the same as yours @mclever. So, I followed your configuration to a T. Now on the entities screen the entities report back “Not Provided”. The logs show Disconnected - waiting for discovery broadcast. When I setup the device I configured it under protocol version 3.3 as nothing else would work. I did not configure the “DPIDs to send in RESET command” field. I did not know if that was something I should do or not.
only protocol 3.3 would work for me this is how each modify device screen looks for me, hope this helps
and after making changes I did need to restart HA, the localtuya integration wouldn’t reload for me
I had an issue where most of my entities read in just fine, but for some reason, my set temp and actual temps never read in correctly. So here’s a tip for anyone else in the situation:
Instead of following the normal instructions provided at the beginning of this thread (step 5 to be specific), don’t set up your smoker temp(s) as climate. Instead, set up your Set Temp as a Number type and your Actual Temp as a Sensor. You can no longer use a typical climate card to adjust and view your set/actual temp, but you can easily drop in a number input card and a gauge card. A little extra work, but so much better than just seeing “Unavailable” on a climate card.
I got this working via LocalTuya today on my RT-B380X, and just now found this thread. I tried to document my whole process in this gist which might be helpful for others which run into trying to do this in the future. Last year when I tried to use this repo I wasn’t able to get it working. LocalTuya made it pretty easy IMO and I was able to confirm my grill’s DPs match contractcr’s.