Well I installed local tuya and it had some error about no data points found, so in this thread I found someone who broke down what the DPS were and I did a manual configuration of adding it all in, seems to work although for some reason if you turn it off using the tuya app you can’t turn the device back on. If I power cycle it then I can turn it back on, so I have it on a smart plug for now if need be. Does anyone have an ideas about the data points missing, not able to turn on remotely after turning off remotely, and also is there anyway to get around the user confirmation bug?
I have tried turning it on using the preheat function and that doesnt turn it on, nor does the setting the level.
I’m pretty sure that you need to pretty much ditch the Tuya app if you are trying to do local control. This means really killing the app on all of your devices. The local control relies on a rather marginally reliable UDP based system. With your local software and the Tuya app both sending and monitoring these, even when no control is being done.
I have one of these Mattress Pads running for over a year with local control (custom python based on very good TinyTuya github project) with very good reliability. All functions work including preheat. Interface to Home Assistant is via MQTT.
Pretty sure the chip in this device is not supported by either TinyLibre or OpenBeken, I have opened the controller and route of replacing the Tuya chip with a ESP chip is a possibility, would take some reverse engineering to get the serial control commands/status between the Tuya wifi chip and the Tuya MCU that does the actual control of the functions. It’s on my too long todo list, that said I have a TinyTuya project based python mqtt controller for the mattress pad that has been running very well for over a year.
the tuya app is force closed so it’s not doing anything at this point for me, it was just for testing really to make sure that the issues I was seeing in HA was the same in the tuya app (which they are).
Late to the game: Just pulled out the mattress pad out of the box.
As most (if not all) of you I would love to avoid Tuya app and account.
Is there a way around or do I need to take that path (if nothing else) to connect the device to my WiFi? The controller has (as per usual) an unprotected wifi and is sitting on 192.168.175.1. However, there is nobody listening on :80
Any info whether there is a www configuration interface at some port or perhaps a telnet console?
If Tuya is it for initial setup I will give it a try. Hope the above (super nice!) instructions from 2022 are still applicable to what ships these days.
Thanks!
Got the integration working for the Sunbeam Bedding Single - S1 (Full size)
Most of the “Side A” properties are applicable to the single version with few exceptions:
1: - No master power switch
4: - No master heat level
There are also three new (sensor?) properties: 103: with raw states “45_Minutes_Before” and “User_Confirmation” (that I have yet to understand) 102: Remaining Preheat time [s] (count-down from 1800s) 13: ??? so far Raw_state=0
Just in case someone has the same version.
BTW: Unfortunately YAML was deprecated as configuration method for LocalTuya so all editing was in the UI
The dual controls are a bit different.
104 is the user confirmation and
103 looks to be a timer that is set to 1800 anytime any setting is changed via HA
You need to make sure the temperature levels and time settings are exactly correct in the configuration. As an example if you use Level vs level it will put the blanket in a mode where it needs to be power cycled to work again. MrWhite49 has the correct variables listed above.
Just wanted to say there was an update to tuya local by the repo posted in here and it broke my Sunbeam, I rolled back and I messed up and accidentally deleted my device and instead of trying to manually configure it (all over again) I stumbled upon this repo (see below) and it had support however there was an issue with mine for some reason because it was DUAL and the repo owner fixed their code and I had a new yaml for it, updated the local file, added it in and it worked like a f’n champ. No messing around with DPS and all that.
Just purchased this and set it up yesterday. Some differences compared to what other people were seeing. Potentially a firmware update?
There is another ‘safety’ feature that won’t let you control the pad remotely for 2 hours if you turn it off remotely. It mentions this in the tuya app when you are about to turn it off. You can cycle this by turning it on and off again on the hand remote (or unplugging it). While this was annoying during initial testing (I thought it was broken), it doesn’t seem to impact our day to day usage of it. Worst case, I could throw an outlet on it anytime I issue an ‘on’ command, just have to wait the 10ish seconds for it to connect to wifi.
I was unable to ‘bypass’ the safety lowering the heat after the set time. Using tuya-local to only turn on preheat or set the heat level doesn’t actually turn on the pad.
So I was planning on replacing the WBR3 with an ESP-12 and integrating
it via that way… I got bored waiting for parts and wired in an ESP-01 to pull the ‘safety’ (check) switch low. It holds the button for 2 seconds every 5 seconds (7 second cycle). This allows me to bypass the 1 hour preheat timer and the 2 hour remote control timer.
I’ve been able to get the Side A turned on at 6pm but cannot figure out how to set the heat level at 6. Below is my yaml. Any thoughts on what the correct entry/syntax shoudl be?
I’ve worked through all of the fantastic instructions in the above and I think I’m almost there (the Tuya IoT portal stuff was unreasonably complicated…). But i’m stuck on adding the device into LocalTuya. I can SEE the device, but none of the device types look right and when I try one nothing matches with the instructions above on setting the configuration. Can someone give me a quick pointer to finish this (hopefully) last step (like, which device type to select)?
I appreciate all the work in this thread, and am hoping someone can help me get the last piece figured out for me. I can’t get the ‘select’ entities configured properly. Here’s the error I get, and the syntax I used. What did I do wrong when creating the entity ??
