Thank you. Nice work been done. Tip: instead of debugging network packages to find dp_id you can simply get Query Properties under Device Control by using device id.
Wow Tuya Local is really good, with first the try everything works and popup perfectly. had so much challenge with LocalTuya. Thanks for sharing the information and all efforts.
instead of using auto Ip I used the correct Ip and all configurations were loaded by default, no manually finding each value. Thanks for the correct plugin
I’m glad BT isn’t filing issues with my A433 MHz device add-on. I never filed issue for my my devices..I just added each functionality as individual devices. 🤦♂️ Haha. BT, thanks for this. I’m going to try this new one!
Switching to Tuya-Local was also my conclusion after using localtuya, for the reasons you describe, but also for other reasons. I found that most of my 30+ devices under localtuya frequently went to offline state, and when I reloaded the localtuya integration they would come back to the online state, leading to a lot of frustrating manual maintenance and a strained marriage. When I switched to Tuya-Local, the devices mostly remained online, except for the devices that actually did have WiFi connection issues, such as a RGBWW lightbulb in a metal shrouded gooseneck lamp. or devices that presumably had trouble calling home to Tuya's AWS cloud services, and my marriage is back on the rails. (According to the Internet advice on this latter problem, I'm faced with blocking DNS for the Tuya devices to prevent them from getting stuck in the offline state, but that means setting up a VLAN for just those devices, playing with routing tables, etc.) Thank you for providing details about creating custom supports for new devices. I only have lightbulbs and switches currently under Tuya-Local control, though ideally I'd like everything to be independent of the cloud and truly local. Also, as a side note on Tuya-Local, my switches now have their internal timers exposed, and since moving to Tuya-Local they have been behaving erratically - either switching on at random intervals, or switching off at random intervals with no HA automation showing the cause in the logs - this is currently the only conclusion I can make (did Tuya-Local "tickle" the timers' DP IDs when they were first set up?) But maybe it's my misunderstanding of how internal timers are used and I don't yet know how to disable them (there does not yet seem to be a way). Perhaps setting them up as a custom support, as you have demonstrated in the video, or modifying the existing support to expose more DP IDs for timer control will address this problem that I suspect others may be having. Edit: ideally, I'd like to have all these Tuya devices moved over to ESPHome firmware, alas, I only managed to wirelessly update one lightbulb, and firmware flash two others by taking apart the lightbulbs, and the rest of the Tuya devices are on the new hardware that is not compatible with or supported by ESPHome!
Thank you for sharing this! It would be awesome if there would exist good Tuya alternative. HA devs really got burned by the company in terms of support and cooperation unfortunately, but this also translates into trend how the company works - they lack developers for end user part. While I do understand why they operate like that from business perspective, I really don't like it as end-user. One device I got few years back had been happily working with ESPHome, but this solar inverter can't be converted too - same issue as you have. There are companies that could do Zigbee version, but only if they receive large orders . So, stuck with Tuya.
I feel you. I have 40+ tuya 4 touch panels across my house and frequently I see a few being unavailable.. do you think this integration will help? PS : just got married
As a follow-up on my setup, I was able to convert my non-ESP WB2S (Beken BK7231T) based smart plugs to libretuya-esphome using tuya-cloudcutter (firmware uploader option) via the cloudcutter tasmota-like firmware, and I found that I had a lot of TYWE3L (Espressif ESP8266) based lightbulbs that had a Tuya firmware version early enough that I could use tuya-convert on them flash them with the usual tasmota-lite -> tasmota-minimal -> ESPhome update process. So now out of 32 Espressif/Beken devices I have 14 lightbulbs on ESPhome and 5 smart plugs on LibreTuya-ESPhome. The rest of the devices are a mix of tuya-patched firmware ESP lightbulbs, and lightbulbs with WB3L (Beken BK7231T) modules in them, as they are not currently supported by tuya-cloudcutter - though they were detected as "exploitable" so I sent them a binary flash dump to analyze. In Home Assistant, in place of ESPhome, I now use an experimental LibreTuya-ESPhome add-on which uses a fork of ESPhome to include the BK7231 and RTL8710 chips. The fork is typically a week behind ESPhome, so that's good enough for me!
Great helpful and informative video..didn’t even realise there was a Tuya local…been using the local Tuya all this time..now have all the power stats. Thanks very much 🙏🏻🙏🏻
Great video and well explained. My normal cloud tuya no longer worked (unkown error) and with local tuya the colour setting of my RGB lightstrip did not work. Tuya local works perfectly and also easier to set up than local tuya.
First, I love your videos; keep up the amazing work. Do you know if any way to use this integration with bluetooth devices? I have a couple of tuya compatible bulbs but I just can't get them integrated. tuya_ble doesn't work, and the fork that says it does bulbs is broken. The blocker for using tuya-local is that I have to have an IP or hostname.
Will work on this tonight, perfect as I don't mind some of their products. I always got caught out with one of the tuya products not been supported by the other integrations.
Thank you for this. I was about to throw my temperature and humidity sensor out the window, but it integrated with tuya local in seconds. So you saved me €25 :)
After a few litres of Altbier on a business trip I really need sleep however a new BT video… time to watch 👍 Very interesting video, I shall be investigating further when back home.
@@BeardedTinker appreciate the hard work you put into these, I promise to watch back sober👍 interested to see if I can integrate my robot hoovers better, I shall report back
Usually it's not that long, but masking all of the stuff (device IDs, keys, ...) takes a bit more time than I hopped for :) I wish I could grab another beer but need to sleep.
Very clear tutorial.. Happy to be subscribed When trying to add a Wasserstein flood sensor (Tuya based) it said "Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect." Is it because I need to add/request for the integration?
Great video, thanks I have a Tuya smart lock which appears in Smart Life and in the Tuya app in homeassistant but unsupported. I managed to get the device ID and local key and when I input these into Tuya-Local it says it cant find the device. I have added devices successfully. What can i do?
Is the device on supported list? github.com/make-all/tuya-local/blob/main/DEVICES.md If not, have you created costume converter as per video? If yes, I would suggest you open a ticket on Github, post device_id plus other ID's you've gathered and your coustom converter. It should help author add official support.
I am using localtuya and Tuya Local in parallel now, however, I have a Tellur aroma diffuser device which I wanted to integrate using localtuya and when I did, it crashed my other devices (5 window blinds) in a way that they wer unrecoverable. Than I switched to Tuya Local for my aroma diffuser device and it turned out, it is fully supported without tinkering wiith datapoints. Datapoints fishin wouldn't have been a problem, but it ultimately did not work with localtuya. After that, I have migrated my blinds to Tuya Local because I had to reconfigure them anyway, and guess what? They work even better. Now, I have migrated ALL my devices (aroma diffuser, 5 blinds and a CNC energy meter) from localtuya and Tuya Local, and never looked back since. I am keeping the localtuya HACS integration around just in case, but it is not my go-to solution going forward.
Thanks, now have found the IP of the heater with Advanced IP scanner. I now have entered the Device ID, IP address and Local Key in Tuya Local but get the message: 'Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect.'
Excelente video ... migré todos mis dispositivos a local y ahora funciona todo mas rápido.. adicionalmente no tenía compatibilidad con un ventilador y lo pude agregar siguiente la forma "manual" de hacerlo... GRACIAS!.. saludos desde Chile!
Thanks for this video. All my Tuya devices are now in Tuya Local except 4 lights that connect through a BLE Mesh Gateway. I've found the ID and local key of the gateway and the IDs and sub IDs of the 4 lights but Tuya Local doesn't recognise them.
Glad it helped I've never tried adding any Tuya BLE device TBH. I do know that Tuya Local supports also BLE devices, but not sure on how it needs to connect. I usually just use (for supported devices) Bluetooth proxy.
I haven't tested the Tuya devices with the cloud blocked. I heard a rumour that some Tuya devices need to talk to the cloud to keep working, but I have not had definitive proof of that. Tuya-Local looks like a great way to run Tuya devices. It's the local control Tuya promised us they would work on and support from first party, but never really did.
That's Tuya... From what I've heard about them from HA devs, they are really not interested in whatever we do here. And they don't have as many software developers as we would think.
@@BeardedTinker Sounds a bit like a few companies... Switchbot also don't have that many devs. They all seem to be marketing heavy. I guess that is how they get money in......
True, but unlike Tuya, SwitchBot did actively help with integration development - when Bluetooth was improved in HA. I may be completely wrong here, but SwitchBot looks like it wants it's devices getting used, no matter how users decide to use it. While Tuya is interested in getting paid by companies to use their data center. That's why dev costs are so high. They make money off of Tuya device manufacturers 🤣
Thanks for the great tutorial! I think I do understand the basics, but I am struggling to complete the setup of my "YINMIK Water Quality Tester". - This water tester is listed as supported and a YAML file is available for it on the Gighub page - Copied the file to my system (assume this should be on the root?) - I changed the device ID in the sample YAML file - Added the new device in Tuya Local with Device ID and Key >> Success I can add the device, but it shows me still only one weird entity. When checking my device and datapoints online at the Tuya ioT developer point all the DP's are matching with the sample YAML file from GigHub. What I am doing wrong? It looks to me like the YAML file is not used by the system. Would be great if you can give me any advice! Thanks Roland
When you say root folder - is it root where all YAML files for Home Assistant are, or root folder of this custom component. (/custom_components/tuya_local/) - but noth are wrong it should be in devices subfolder - /custom_components/tuya_local/devices/
Great video! Love you content on HA. Unfortunately, I'm getting this error on the configure window - "Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect." I know my Device ID + Local Key is correct because it worked on LocalTuya. I know my IP address is correct since it's from my router. I tried different protocol versions and also left the IP to auto but no luck 😥
Not sure why you get that. You could try looking at GitHub for issues like this one or create a new issue. If the device id, key and IP address are ok, you shouldn't see this error unless your device isn't known/supported.
Is tuya local still the better option over local Tuya in 2024? I'm currently using local Tuya for a single ceiling fan with no issues. I've just purchased another ceiling fan, and having issues adding it to local Tuya. I came across another local Tuya fork that looks like it is frequently updated via github as well
not many Zigbee or Matter devices available outside of specialists here in NZ but many using Tuya so I really hope this does the trick. Have been using the basic cloud Tuya integration but there's something weird going on with the Tuya developer API where it needs the trial extending every month so looking to do this only if I add another Tuya based device. Thank you.
Very helpful video, thank you, device id and keys are unique for each device, or may change at any time. I ask for after obtaining them to save them in case of migration or change of location. thank you.
Not 100% sure. Some other manufacturers keep keys unless you re-pair the device. So I believe that this is the same. It shouldn't change unless in SmartLife add you add them again.
the menu is different. Now in device management "get device details" is not available. In the query device details it looks like this "local_key": "", where can I find the local key ?
Great video as always switched from local tuya and everything works flawlessly but unfortunately on of my devices act feeder cant be integrate any ideas as to why ? Maybe needs an custom yaml file? Thank you in advance
Probably needs custom integration. You can try opening issue on Github, copy there DP ID's and also sharing link to that device. Or you can try customising an existing device yaml for it.
Great Video ... face intermittent problems with Tuya ... I have 30+ devices . Following your video , all devices are on an excel sheet with the Device Id & Local Key . When I tried to add a device on Tuya Local , it was not accepted. Do I need to delete the earlier Tuya Integration ?
@@tempdemp1622 Are you using internal Tuya integration in Home Assistant or Local Tuya integration (older one)? But anyway, according to documentation, only one instance can access device at one time.
Still new to HA, how do you get all that cool stuff in your overview please? lol. PS, I contributed and added my Orison Low Profile Ceiling Fan. Of all the YT videos for "Tuya Local", yours is the best by far. I have several more devices to get added soon :).
Been trying local Tuya for ages but can never get my ASHP into HA tried tuya local got temp and target temp thank you so much. Just need to edit files for mode and on. / off
Thanks for your video. I've successfully set it up in the past, but now I have to do it again and am running into issues. It's annoying all the hoops that have to be jumped through regarding the Tuya IOT platform. But that's not your fault :)
Tuya... I really am not looking forward to adding any devices from them that are not BLE or Zigbee in future. But than again, they have their business model that works by the looks of it.
Thanks for this detailed video, I tried to add my 3 Tuya devices through Tuya Local, unfortunately only one of them was added successfully (Aircon). I also have 2 water heaters that I cannot add with the poll only tick marked or without it, I tried to add the IP address instead of auto and yet I receive the following message: "Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect.". Device ID and Local Key are 100% correct so I don't see how I can move forward with it.
Are your devices listed as supported? If not, did you watch part on how to adapt existing in create for your? If no, you can always try to open issue as suggested on GitHub, submit necessary data and wait for official support.
You should be able to get it via router. I use unify and it identified device there. There is more complicated way by using TinyTuya - github.com/jasonacox/tinytuya but it requires separate installation. Or you can us tool like Angry IP scanner: angryip.org/
While I like this new Integration I have the problem of devices going offline seemingly randomly. Wonder whether others have this as well and how they fixed it. Non-issue in the Tuua Smart app
Not sure why this would happen... Haven't seen this with device I have and other I've tested (don't normally use Tuya WiFi devices) - check issues on github, maybe someone has same problem.
To be honest - I hate Tuya... The only reason I spent time on this is my solar ivnerter as they are only made by Tuya. It's still working great, but...
BeardedTinker thanks for this great tutorial, I followed everything step by step and got my first device added. But what are the steps to add a second device, because I can't do that. Any help is welcome! In local-tuya it went quite smoothly. By clicking Add new device. Sorry for my ignorance and thanks in advance.
@@BeardedTinker I have all local keys device id and ip, but when I choose "Integration". I get the message that the key already exists. Would you be so kind as to briefly indicate the steps I should follow. Does that have to be done via Integration again?
Hope you manage to add it. It's not hard. When I was creating mine, I browsed through the list and copied/pasted from other devices (of course using dp id of device I was adding).
Will moving my 40+ tuya 4 touch switches to this new integration help avoid the unavailable problem? Coz this will take a lot of commitment and a time to do and I want to be sure to invest the same here.
Can't answer you that. Question is why do you get unavailable. For example, my doesn't work during the night, so it has usual unavailable state at that time. If you can try with a device or two and test, that would be best way to go
I want to connect my Eurom Mon Soleil IR panels to HA with Tuya Local. The device ID and Local Key are found but no IP address. How can I find the correct IP address in order to connect to my panels? Thanks Tjerk
I would suggest to try and find it via router or use tool such as IP Angry Scanner to find all IP addresses used. I usually go for router (Mikrotik) and look there at DHCP leases or Unifi for devices connected to WiFi network. In SmartLife app in device information you can see MAC address and this will help you identify correct device.
Unfortunately a couple of my devices are battery powered so I’m stuck with the cloud. If I’d known before hand that battery devices could not be local on Tuya I’d have done things differently, saying that I bought the wrong thing each time anyway. If I have the normal Tuya integration can I run it alongside the Tuya Local integration?
Are they WiFi devices? To be honest, not sure if I've seen Tuya battery WiFi devices - curious what they are. As for the question - not sure - Tuya devices are usually limited to one connection, but if one is cloud, other is local, it should work (mine works like that)
Where in IoT platform is all that Json you show at 11:00? And if that's in there somewhere then why mess about with developer tools and querying every DP ID individually? This Tuya site is a nightmare to navigate, pls inform.
nice video. I have a problem when I make a request for the local key. "msg": "No permissions. Your subscription to cloud development plan has expired." Why should i pay for it, it was for free last month?
I had the same problem. You need to select the Trial Extension option and fill out a small form. Their tech support reviews this and hopefully grants you an extension. Mine took a day or so to grant a 6 month extension. I don't want to do this again in 6 months, hence my interest in tuya-local.
Been using local tuya with a Lefant vacuum and a Tuya zigbee gateway. It worked for the vacuum for a bit, but not for the hub (error in the HA logs states unsupported). I'll have to revisit things and see if I can get things running again. Also, the having to do the reauthorization of the count every 3 months is just awful.
Nice video! My local key shows up as: "local_key": "", and when integrating (Tuya Local) with homeassistant, I get the error:" Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect. " How to solve this problem? Thanks!
Hard to say, it can be anything as it says. Device could be temporarily unavailable or local_key cold be wrong. Are you also using Local Tuya at same time? If yes, than that too can also be an issue.
At first this project make me feel very happy because I could put offline all my tuya devices but after some days, my devices started to go offline of my LAN randomly, very annoying… finally I went back to the cloud tuya integration 😫😫😫
Sorry to hear that - devices I have through it have not gone offline so far and are working nicely. Not sure why this could happen. Maybe network issues or something similar. Try opening an issue on GitHub.
@@BeardedTinker Thanks for your comment, I will open the issue... I have an amplifi router and I can block the internet access of any device, I was thinking that the Tuya devices could have any rule of turn off the wifi if they can't reach some cloud service that they need to work out of the box
@@BeardedTinker I've got 30+ lights and smart plugs working in Local Tuya, just 2 (cheap) string lights refuse to work.... even only turning them off and on would be nice. Using a smart plug to switch a "smart" device on and off is just ....
@@BeardedTinker I can confirm the method in your video works like a charm! My lights were unsupported by both local tuya and tuya local. After making a yaml file for them they now work fine! Thanks for showing us this.
I have no local key in my Response window , for all devices I have in Tuya. This is the reason I quit few month ago and connected tuya trough official integration which does not have all entities
Did you try both under General Device Capabilities and Smart Home Device System in API Explorer. I don't have local key in General section, but I do in Smart Home section. But if you got it working with official Tuya, it's great - at least for now it's available in HA.
Is this truely local when the devices still needs Tuya ioT account to be active and have to be renewed every 6months? I don't know when Tuya will stop the subscription.
tuya decreased validity of the developer account from 1y to 1 or 3 months. One day it will finish and it will become: "cry and pay" - Tuya? thank you - no - thank you
You should only need once to login and get davice id and local key. After that, it should work without account being active. Or you can ask support to extend account. But yes, it's not the best approach, I do agree. Wish there was alternative for only device I need :D
@@BeardedTinker I used to have 40+ Tuya devices. Thanks to ebay I have now 0. Replaced with Athom, Sonoff, DIY, etc. No, no more cloud. Meross even blocked my sockets when they realised they were integrated with HA. No, thank you. There are alternatives
@@BeardedTinker nope, when the trial expires all your local Tuya devices go offline and you need to login back into Tuya account and request a free extension. been there, done that
@@SlackerLabs you did not get my point: from 12m they decreased recently to 3m, some people got only 1m, wait a bit and you will see in the future what is for free from Tuya ;-)
Hi I follow the setup guides and when I try to add "add Device" am getting "add device using smart industry app" when I scan the qr code it ask me to download "smart industry". I already have the tuya app install. any idea what am missing to add the device. ??
hi, is it an active integration yet? I installed the Tuya local, but I can't add the device (smart plug), The IOT platform is changed a bit and I found the local key @ Device Management/Query Device Details in Bulk or is it an wrong place? Merry Xmas!
Once I create the yaml file and add it to the custom_components folder, what do I do? How does it know that the configuration corresponds with my device’s ID?
@@BeardedTinker appreciate the quick response. What I am referring to is the Model field in home assistant is "unknown" where as the original Tuya integration will have this field populated. Want to know how to populate this.
Mine is still working. I think I got 12 months at the time I signed up for it. So can't tell you. With local key, it could work, but you never know with Tuya.
Yes, create file as shown (content) and place it in tuya local folder. Or open issue on GitHub,, post there data, so others can get support for the device too.
amazing! but still I have issue like localTuya, I can't get the local_key from smartmi air purifier p1 and 2. even I see them on tuya app. what can be the problem, I get permission deny on 'get device id'
Try changing category (for example from Smart Home to General Device - or vice versa) i API Explorer list. I know I got same results when playing in one category next category worked OK.
Not 100% sure. I think it will autodiscover it. And there should be only 3 or 4. You can see it in URL of website when you login in the portal. For me it's EU.
I just had to extend my "free" account and I am worried that in 6months when it expires how I will get my local keys easily. Does anyone know of a local network TUYA scanner that can pull these keys?
On adding a custom .yaml device file, do you need to do anything else special for TuyaLocal to find the device? i.e. restart? I am still getting 'device not found' after adding. Is there any logs or diagnostics to debug .yaml files?
if new device yaml has been created, you do need to restart HA I think. Did it some time ago, so sorry if forgot. As for debug, in configuration.yaml file, make sure you have following: logger: default: warn logs: custom_components.tuya_local: debug
@@BeardedTinker thanks BT. Great video by the way. Very clear and concise. From what I can see Tuya Local is more powerful than Local Tuya especially when it comes to devices that don’t fall into the standard light, switch, thermostat etc categories. The Auto IP didn’t work for me. I had to set the devices local ip addresses manually, everything else spot on. Well done.
How do you manage your subscription? i could not find the way to renew my subscription. When trying to get "local_key" i get this error: No permissions. Your subscription to cloud development plan has expired. thank you.
At the time of the recording, subscription was still active. Not it's not anymore and I can't extend it even through standard free extension procedure. But device works with Tuya local even with inactive subscription.
They are not add-ons. No additional docker is needed. But you need to install HACS and then you can install one or the other Here is how to install HACS hacs.xyz/docs/setup/download Select Container type of HA install and you'll have two options for you
I didn't see that behaviour myself. Does the device also lose connectivity if you check SmarLife App? Have colleague who has that problem. The issue was the device itself.
No, the smartlife app doesn't lose connectivity, but this problem has just arisen If the power goes out, it won't connect again. I have to restart the home assistant
I've seen similar with other integration but they usually reconnect after some time. But haven't experienced with this one so far. You could try opening the Issue on GitHub for this.
nice video. but i have a problem: i become this message when i add my device id and local key: Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect. can u help me?
I think it can only talk to one integration at a time - if I remember correctly. I needed to remove device from existing integration before I was able to add it But check documentation to be sure.
You should in Cloud Menu select API Explorer and it should show you this menu. If there is any other method on that site, I'm not sure of that. Localkeys should be in either General Device Capabilities section or mart Home Devices section.
@@BeardedTinker Thank you for your kind answer. Found it! I feel a bit silly, because first I just clicked on the menu entries, but not on that tiny black triangle to unfold the menu in question. How stupid of me.. haha..
They did change menus on web a bit - but if you first pull the device ID, after that, go in API EXploprer and in top left menu, select Smart Home Basic Service - and than under submenu Smart Home Device Management select Get device details, you should see it. Just tested few minutes ago.
iot says my subscription has expired and won't give me the information on my device... when I go to renew... they want $250 for the year or some shit...
you can try creating a new project, it is unlimited but you will either have to renew the free 'subscription' monthly or just create a new one each time (which admittedly sux ballz)
I had the same problem. I sent a message to the support. I said that as a private user I had only 2 plugs. The support gave me some free months more. I saved all keys and datas and bye bye tuya.
@@crashcreeley well it works for me, and others too. Try creating a new project and maybe you will be able to renew afterwards. For projects created before a certain date, the renew option doesnt work.
No, at least, for me, after getting the local key and device id, they continued to work after expiry. I did once again ask them for extension, so it is now active, but it worked
You need to try and renew your free subscription. Mine still hasn't expired so can't tell you exactly how. But you should still be able to do it for free.
I have been in trouble to setup local tuya for days due to various errors
By your intro i have made it done in 5min!!
AWESOME - glad it worked you for you!!!
thanks Mate !! finally a video which show where to get the local key in 2023, loved it 🙂 Thanks Once again
Glad it helped! Thanks for the comment 😃
Thank you. Nice work been done. Tip: instead of debugging network packages to find dp_id you can simply get Query Properties under Device Control by using device id.
Thanks for the tip!
Wow Tuya Local is really good, with first the try everything works and popup perfectly. had so much challenge with LocalTuya. Thanks for sharing the information and all efforts.
Glad it helped! Thank you for the comment!!!
instead of using auto Ip I used the correct Ip and all configurations were loaded by default, no manually finding each value. Thanks for the correct plugin
Glad it's working, thanks for the comment 👍
I haven't dig into Local Tuya or Tuya Local yet, but you tutorial really helps visualize the necessary steps. Good job! Thanks!
Great to hear! Thank you!!!!
I’m glad BT isn’t filing issues with my A433 MHz device add-on. I never filed issue for my my devices..I just added each functionality as individual devices. 🤦♂️
Haha. BT, thanks for this. I’m going to try this new one!
Now that you've summoned me, I'll have to do it 😂
Thanks for the comment Jeff!!!
Switching to Tuya-Local was also my conclusion after using localtuya, for the reasons you describe, but also for other reasons. I found that most of my 30+ devices under localtuya frequently went to offline state, and when I reloaded the localtuya integration they would come back to the online state, leading to a lot of frustrating manual maintenance and a strained marriage. When I switched to Tuya-Local, the devices mostly remained online, except for the devices that actually did have WiFi connection issues, such as a RGBWW lightbulb in a metal shrouded gooseneck lamp. or devices that presumably had trouble calling home to Tuya's AWS cloud services, and my marriage is back on the rails. (According to the Internet advice on this latter problem, I'm faced with blocking DNS for the Tuya devices to prevent them from getting stuck in the offline state, but that means setting up a VLAN for just those devices, playing with routing tables, etc.)
Thank you for providing details about creating custom supports for new devices. I only have lightbulbs and switches currently under Tuya-Local control, though ideally I'd like everything to be independent of the cloud and truly local.
Also, as a side note on Tuya-Local, my switches now have their internal timers exposed, and since moving to Tuya-Local they have been behaving erratically - either switching on at random intervals, or switching off at random intervals with no HA automation showing the cause in the logs - this is currently the only conclusion I can make (did Tuya-Local "tickle" the timers' DP IDs when they were first set up?) But maybe it's my misunderstanding of how internal timers are used and I don't yet know how to disable them (there does not yet seem to be a way). Perhaps setting them up as a custom support, as you have demonstrated in the video, or modifying the existing support to expose more DP IDs for timer control will address this problem that I suspect others may be having.
Edit: ideally, I'd like to have all these Tuya devices moved over to ESPHome firmware, alas, I only managed to wirelessly update one lightbulb, and firmware flash two others by taking apart the lightbulbs, and the rest of the Tuya devices are on the new hardware that is not compatible with or supported by ESPHome!
Thank you for sharing this! It would be awesome if there would exist good Tuya alternative.
HA devs really got burned by the company in terms of support and cooperation unfortunately, but this also translates into trend how the company works - they lack developers for end user part.
While I do understand why they operate like that from business perspective, I really don't like it as end-user. One device I got few years back had been happily working with ESPHome, but this solar inverter can't be converted too - same issue as you have.
There are companies that could do Zigbee version, but only if they receive large orders . So, stuck with Tuya.
I feel you. I have 40+ tuya 4 touch panels across my house and frequently I see a few being unavailable.. do you think this integration will help?
PS : just got married
As a follow-up on my setup, I was able to convert my non-ESP WB2S (Beken BK7231T) based smart plugs to libretuya-esphome using tuya-cloudcutter (firmware uploader option) via the cloudcutter tasmota-like firmware, and I found that I had a lot of TYWE3L (Espressif ESP8266) based lightbulbs that had a Tuya firmware version early enough that I could use tuya-convert on them flash them with the usual tasmota-lite -> tasmota-minimal -> ESPhome update process.
So now out of 32 Espressif/Beken devices I have 14 lightbulbs on ESPhome and 5 smart plugs on LibreTuya-ESPhome. The rest of the devices are a mix of tuya-patched firmware ESP lightbulbs, and lightbulbs with WB3L (Beken BK7231T) modules in them, as they are not currently supported by tuya-cloudcutter - though they were detected as "exploitable" so I sent them a binary flash dump to analyze.
In Home Assistant, in place of ESPhome, I now use an experimental LibreTuya-ESPhome add-on which uses a fork of ESPhome to include the BK7231 and RTL8710 chips. The fork is typically a week behind ESPhome, so that's good enough for me!
Great helpful and informative video..didn’t even realise there was a Tuya local…been using the local Tuya all this time..now have all the power stats. Thanks very much 🙏🏻🙏🏻
Glad you have it working for you!!!! Thanks for the comment!
Great video and well explained. My normal cloud tuya no longer worked (unkown error) and with local tuya the colour setting of my RGB lightstrip did not work. Tuya local works perfectly and also easier to set up than local tuya.
Great to hear!
First, I love your videos; keep up the amazing work.
Do you know if any way to use this integration with bluetooth devices? I have a couple of tuya compatible bulbs but I just can't get them integrated. tuya_ble doesn't work, and the fork that says it does bulbs is broken. The blocker for using tuya-local is that I have to have an IP or hostname.
Thank you!!!
For BLE, they are pointing to github.com/PlusPlus-ua/ha_tuya_ble - so unfortunately, no idea on what to do next.
Will work on this tonight, perfect as I don't mind some of their products. I always got caught out with one of the tuya products not been supported by the other integrations.
Tuya is a bit frustrating sometimes - I do get them, just wish they would have better software development.
Thank you for this. I was about to throw my temperature and humidity sensor out the window, but it integrated with tuya local in seconds. So you saved me €25 :)
That's great - nice it worked out!!!!
After a few litres of Altbier on a business trip I really need sleep however a new BT video… time to watch 👍 Very interesting video, I shall be investigating further when back home.
Enjoy! I just had a beer after 6 hours of editing :)
@@BeardedTinker appreciate the hard work you put into these, I promise to watch back sober👍 interested to see if I can integrate my robot hoovers better, I shall report back
Usually it's not that long, but masking all of the stuff (device IDs, keys, ...) takes a bit more time than I hopped for :) I wish I could grab another beer but need to sleep.
Very clear tutorial.. Happy to be subscribed
When trying to add a Wasserstein flood sensor (Tuya based) it said "Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect."
Is it because I need to add/request for the integration?
Thanks for the sub! Yes, that could be the issue, as it doesn't get recognised.
@@BeardedTinker I see, then I'll need to go through the motions to get it added. Thank you!
Great video, thanks I have a Tuya smart lock which appears in Smart Life and in the Tuya app in homeassistant but unsupported. I managed to get the device ID and local key and when I input these into Tuya-Local it says it cant find the device. I have added devices successfully. What can i do?
Is the device on supported list? github.com/make-all/tuya-local/blob/main/DEVICES.md
If not, have you created costume converter as per video? If yes, I would suggest you open a ticket on Github, post device_id plus other ID's you've gathered and your coustom converter. It should help author add official support.
thank you so much for this.. i was having issues with local tuya but this fixed my problem completely ....
Glad to hear it! Thanks for the comment!
I am using localtuya and Tuya Local in parallel now, however, I have a Tellur aroma diffuser device which I wanted to integrate using localtuya and when I did, it crashed my other devices (5 window blinds) in a way that they wer unrecoverable.
Than I switched to Tuya Local for my aroma diffuser device and it turned out, it is fully supported without tinkering wiith datapoints.
Datapoints fishin wouldn't have been a problem, but it ultimately did not work with localtuya.
After that, I have migrated my blinds to Tuya Local because I had to reconfigure them anyway, and guess what? They work even better.
Now, I have migrated ALL my devices (aroma diffuser, 5 blinds and a CNC energy meter) from localtuya and Tuya Local, and never looked back since. I am keeping the localtuya HACS integration around just in case, but it is not my go-to solution going forward.
Glad everything is working as it should! Thanks for the comment!!!!
Thanks, now have found the IP of the heater with Advanced IP scanner. I now have entered the Device ID, IP address and Local Key in Tuya Local but get the message: 'Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect.'
Great video. If you then disable the tuya IP addresses, will the device continue to report with HA?
Haven't tried TBH, but there should be no reason for this not to work.
Excelente video ... migré todos mis dispositivos a local y ahora funciona todo mas rápido.. adicionalmente no tenía compatibilidad con un ventilador y lo pude agregar siguiente la forma "manual" de hacerlo... GRACIAS!.. saludos desde Chile!
Thanks for this video. All my Tuya devices are now in Tuya Local except 4 lights that connect through a BLE Mesh Gateway. I've found the ID and local key of the gateway and the IDs and sub IDs of the 4 lights but Tuya Local doesn't recognise them.
Glad it helped I've never tried adding any Tuya BLE device TBH. I do know that Tuya Local supports also BLE devices, but not sure on how it needs to connect. I usually just use (for supported devices) Bluetooth proxy.
I haven't tested the Tuya devices with the cloud blocked. I heard a rumour that some Tuya devices need to talk to the cloud to keep working, but I have not had definitive proof of that.
Tuya-Local looks like a great way to run Tuya devices. It's the local control Tuya promised us they would work on and support from first party, but never really did.
That's Tuya... From what I've heard about them from HA devs, they are really not interested in whatever we do here. And they don't have as many software developers as we would think.
@@BeardedTinker Sounds a bit like a few companies... Switchbot also don't have that many devs. They all seem to be marketing heavy. I guess that is how they get money in......
True, but unlike Tuya, SwitchBot did actively help with integration development - when Bluetooth was improved in HA. I may be completely wrong here, but SwitchBot looks like it wants it's devices getting used, no matter how users decide to use it. While Tuya is interested in getting paid by companies to use their data center. That's why dev costs are so high. They make money off of Tuya device manufacturers 🤣
@@BeardedTinker True. Tuya want to collect data and most likely onsell it as this makes them money.
Worked great for me, my devices supported, which where not in "local tuya "
That's great! List has really grown a lot in last few weeks.
Very helpful video, thank you. I have used Local Tuya but have a couple of heaters that are not supported so will definitely try Tuya Local.
Hope it helps!!!
Thanks for the great tutorial! I think I do understand the basics, but I am struggling to complete the setup of my "YINMIK Water Quality Tester".
- This water tester is listed as supported and a YAML file is available for it on the Gighub page
- Copied the file to my system (assume this should be on the root?)
- I changed the device ID in the sample YAML file
- Added the new device in Tuya Local with Device ID and Key >> Success I can add the device, but it shows me still only one weird entity.
When checking my device and datapoints online at the Tuya ioT developer point all the DP's are matching with the sample YAML file from GigHub. What I am doing wrong? It looks to me like the YAML file is not used by the system.
Would be great if you can give me any advice!
Thanks Roland
When you say root folder - is it root where all YAML files for Home Assistant are, or root folder of this custom component. (/custom_components/tuya_local/) - but noth are wrong it should be in devices subfolder - /custom_components/tuya_local/devices/
@@BeardedTinker thanks, I will try
Great video! Love you content on HA.
Unfortunately, I'm getting this error on the configure window - "Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect."
I know my Device ID + Local Key is correct because it worked on LocalTuya. I know my IP address is correct since it's from my router. I tried different protocol versions and also left the IP to auto but no luck
😥
Not sure why you get that. You could try looking at GitHub for issues like this one or create a new issue. If the device id, key and IP address are ok, you shouldn't see this error unless your device isn't known/supported.
@@BeardedTinker Thank you for promptly replying - got it to work eventually with a few more attempts at 'Auto' on Protocol version!
Is tuya local still the better option over local Tuya in 2024? I'm currently using local Tuya for a single ceiling fan with no issues. I've just purchased another ceiling fan, and having issues adding it to local Tuya. I came across another local Tuya fork that looks like it is frequently updated via github as well
not many Zigbee or Matter devices available outside of specialists here in NZ but many using Tuya so I really hope this does the trick. Have been using the basic cloud Tuya integration but there's something weird going on with the Tuya developer API where it needs the trial extending every month so looking to do this only if I add another Tuya based device. Thank you.
Hope it helps. For me it's working flawlessly (for now).
Even with the "Smart Life cloud-assisted device setup." adding of a device is easy.
Very helpful video, thank you, device id and keys are unique for each device, or may change at any time. I ask for after obtaining them to save them in case of migration or change of location. thank you.
Not 100% sure. Some other manufacturers keep keys unless you re-pair the device. So I believe that this is the same. It shouldn't change unless in SmartLife add you add them again.
the menu is different. Now in device management "get device details" is not available.
In the query device details it looks like this "local_key": "",
where can I find the local key ?
Great video as always switched from local tuya and everything works flawlessly but unfortunately on of my devices act feeder cant be integrate any ideas as to why ? Maybe needs an custom yaml file? Thank you in advance
Probably needs custom integration. You can try opening issue on Github, copy there DP ID's and also sharing link to that device. Or you can try customising an existing device yaml for it.
Great Video ... face intermittent problems with Tuya ... I have 30+ devices . Following your video , all devices are on an excel sheet with the Device Id & Local Key . When I tried to add a device on Tuya Local , it was not accepted. Do I need to delete the earlier Tuya Integration ?
Tuya devices do not support two parallel local connections. If you do have already you should remove it from other intergration.
@@BeardedTinker many Thanks ...to try , can I delete a device on my current "Tuya" integration and add it to the new Tuya-Local integration ?
@@tempdemp1622 Are you using internal Tuya integration in Home Assistant or Local Tuya integration (older one)?
But anyway, according to documentation, only one instance can access device at one time.
Still new to HA, how do you get all that cool stuff in your overview please? lol. PS, I contributed and added my Orison Low Profile Ceiling Fan. Of all the YT videos for "Tuya Local", yours is the best by far. I have several more devices to get added soon :).
Puno ti hvala, za tvoj Video!
Nema na čemu! Hvala na komentaru!!!
Been trying local Tuya for ages but can never get my ASHP into HA tried tuya local got temp and target temp thank you so much. Just need to edit files for mode and on. / off
Glad to hear it!!! Thank you!!!
Thanks for your video. I've successfully set it up in the past, but now I have to do it again and am running into issues. It's annoying all the hoops that have to be jumped through regarding the Tuya IOT platform. But that's not your fault :)
Tuya... I really am not looking forward to adding any devices from them that are not BLE or Zigbee in future. But than again, they have their business model that works by the looks of it.
Thanks for this detailed video, I tried to add my 3 Tuya devices through Tuya Local, unfortunately only one of them was added successfully (Aircon). I also have 2 water heaters that I cannot add with the poll only tick marked or without it, I tried to add the IP address instead of auto and yet I receive the following message: "Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect.". Device ID and Local Key are 100% correct so I don't see how I can move forward with it.
Are your devices listed as supported? If not, did you watch part on how to adapt existing in create for your? If no, you can always try to open issue as suggested on GitHub, submit necessary data and wait for official support.
Great Video. Are you able to explain how to get the IP address of a device if not found by the integration.
You should be able to get it via router. I use unify and it identified device there. There is more complicated way by using TinyTuya - github.com/jasonacox/tinytuya but it requires separate installation. Or you can us tool like Angry IP scanner: angryip.org/
While I like this new Integration I have the problem of devices going offline seemingly randomly. Wonder whether others have this as well and how they fixed it. Non-issue in the Tuua Smart app
Not sure why this would happen... Haven't seen this with device I have and other I've tested (don't normally use Tuya WiFi devices) - check issues on github, maybe someone has same problem.
Legend, thank you so much for this, tuya is so common, and so annoying..
To be honest - I hate Tuya... The only reason I spent time on this is my solar ivnerter as they are only made by Tuya. It's still working great, but...
BeardedTinker thanks for this great tutorial, I followed everything step by step and got my first device added.
But what are the steps to add a second device, because I can't do that. Any help is welcome! In local-tuya it went quite smoothly.
By clicking Add new device. Sorry for my ignorance and thanks in advance.
It should be the same. You need once again device id and local key for the device.
@@BeardedTinker I have all local keys device id and ip, but when I choose "Integration". I get the message that the key already exists. Would you be so kind as to briefly indicate the steps I should follow. Does that have to be done via Integration again?
Not sure as I've not seen this error. Are you sure device id and keys are different than the first one?
Now on tuya cloud you have to provide your phone number for verification in order to get the key.
Tuya being Tuya... They don't like people "hacking" products they make.
Waw, great video! Thank you so much BT.
I've got a heater Eurom model not in the list. I'll try to follow your tutorial to add it. 👍👍👍
Hope you manage to add it. It's not hard. When I was creating mine, I browsed through the list and copied/pasted from other devices (of course using dp id of device I was adding).
Will moving my 40+ tuya 4 touch switches to this new integration help avoid the unavailable problem? Coz this will take a lot of commitment and a time to do and I want to be sure to invest the same here.
Can't answer you that. Question is why do you get unavailable. For example, my doesn't work during the night, so it has usual unavailable state at that time. If you can try with a device or two and test, that would be best way to go
I want to connect my Eurom Mon Soleil IR panels to HA with Tuya Local. The device ID and Local Key are found but no IP address. How can I find the correct IP address in order to connect to my panels? Thanks Tjerk
I would suggest to try and find it via router or use tool such as IP Angry Scanner to find all IP addresses used.
I usually go for router (Mikrotik) and look there at DHCP leases or Unifi for devices connected to WiFi network. In SmartLife app in device information you can see MAC address and this will help you identify correct device.
Unfortunately a couple of my devices are battery powered so I’m stuck with the cloud. If I’d known before hand that battery devices could not be local on Tuya I’d have done things differently, saying that I bought the wrong thing each time anyway.
If I have the normal Tuya integration can I run it alongside the Tuya Local integration?
Are they WiFi devices? To be honest, not sure if I've seen Tuya battery WiFi devices - curious what they are.
As for the question - not sure - Tuya devices are usually limited to one connection, but if one is cloud, other is local, it should work (mine works like that)
Where in IoT platform is all that Json you show at 11:00? And if that's in there somewhere then why mess about with developer tools and querying every DP ID individually? This Tuya site is a nightmare to navigate, pls inform.
This JSON was example from GitHub and you can get it when you query every DP ID. AFAIK you can't get whole JSON from just one place.
nice video. I have a problem when I make a request for the local key. "msg": "No permissions. Your subscription to cloud development plan has expired."
Why should i pay for it, it was for free last month?
They expire every few months. You can still extend it for free. Not sure what the procedure is since mine still hasen't expired.
I had the same problem. You need to select the Trial Extension option and fill out a small form. Their tech support reviews this and hopefully grants you an extension. Mine took a day or so to grant a 6 month extension. I don't want to do this again in 6 months, hence my interest in tuya-local.
I got it. Thanks
Been using local tuya with a Lefant vacuum and a Tuya zigbee gateway. It worked for the vacuum for a bit, but not for the hub (error in the HA logs states unsupported).
I'll have to revisit things and see if I can get things running again.
Also, the having to do the reauthorization of the count every 3 months is just awful.
I agree! But hoping for anything better from Tuya, I don't think we will see it anytime soon!
Nice video! My local key shows up as: "local_key": "", and when integrating (Tuya Local) with homeassistant, I get the error:" Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect. " How to solve this problem? Thanks!
Hard to say, it can be anything as it says. Device could be temporarily unavailable or local_key cold be wrong. Are you also using Local Tuya at same time? If yes, than that too can also be an issue.
Thanks, I'm not using Local Tuya.
At first this project make me feel very happy because I could put offline all my tuya devices but after some days, my devices started to go offline of my LAN randomly, very annoying… finally I went back to the cloud tuya integration 😫😫😫
Sorry to hear that - devices I have through it have not gone offline so far and are working nicely. Not sure why this could happen. Maybe network issues or something similar. Try opening an issue on GitHub.
@@BeardedTinker Thanks for your comment, I will open the issue... I have an amplifi router and I can block the internet access of any device, I was thinking that the Tuya devices could have any rule of turn off the wifi if they can't reach some cloud service that they need to work out of the box
Thank you for the video. Viva local tuya.
Thank you 😉
I'm trying to integrate my tuya fan switch using tuyalocal but I'm not getting the switch entity, what should I do
Did you try to create custom converter if device is not recognised? Did you manage to get local password and device ID?
@@BeardedTinker yeah the device was integrated but their was no entity that can be used to control the fan
Great video as always but you forgot to share the github url :)
Fixed :) Thanks for the comment!
Getting old ;)
Is this still the best option for smart micro inverter integration in HA (I have WVC model of micro inverter)?
Unfortunately, yes. I'm still trying to find Zigbee version, as it should be much easier and less reliant on any cloud services, but no luck so far.
i have some unsupported Tuya zigbee devices. They not have local_key and IP. How i can conect to him via Tuya Local ?!
You don't need Tuya Local for Zigbee. For that you need any Zigbee coordinator and ZHA interation of Zigbee2MQTT.
Just use zigbee coordinator, and use ZHA or Zigbee2MQTT integration
I will be trying this for a couple devices!
Keeping fingers crossed. May take a bit of time, but really not hard. You can try reusing parts of the code from other devices that are supported.
@@BeardedTinker I've got 30+ lights and smart plugs working in Local Tuya, just 2 (cheap) string lights refuse to work.... even only turning them off and on would be nice. Using a smart plug to switch a "smart" device on and off is just ....
@@BeardedTinker I can confirm the method in your video works like a charm! My lights were unsupported by both local tuya and tuya local. After making a yaml file for them they now work fine! Thanks for showing us this.
That's great! Thanks for the follow up!
I have no local key in my Response window , for all devices I have in Tuya. This is the reason I quit few month ago and connected tuya trough official integration which does not have all entities
Did you try both under General Device Capabilities and Smart Home Device System in API Explorer. I don't have local key in General section, but I do in Smart Home section.
But if you got it working with official Tuya, it's great - at least for now it's available in HA.
@@BeardedTinker Thanks I found it in General Device information / Get Device Information
Once you put the devices in Tuya local, can you delete them in the Tuya app ?
By the way, great video, I moved completely from Tuya to Tuya local 👍👍👍
Thank you!
Not really sure - haven't tried so far to remove it from the app.
@@BeardedTinker I did, don’t !!!
@@eriksiemens5131 hi, what was the result after adding device to tuya local and deleting from tuya app? Did it work locally?
@@usmangojra no, got in a lot of problems to get it working again 😞
If all the Devices Types I'm getting do not match my actual device, is there anything I can do to fix it?
You can create an Issue on the GitHub repository with your data points and ask for a new device type to be added.
how can i add a bluetooth sensor? I don't have an IP address.
Never tried. For Bluetooth devices, I use Bluetooth proxy and if device is known it should be recognised in HA without issue.
Is this truely local when the devices still needs Tuya ioT account to be active and have to be renewed every 6months? I don't know when Tuya will stop the subscription.
Good point - but it is in a fact local control of device. Even with my subscription expired, I can still control them locally just fine.
Easy to follow steps!
Thank you very much - really much appreciated!!!!
tuya decreased validity of the developer account from 1y to 1 or 3 months. One day it will finish and it will become: "cry and pay" - Tuya? thank you - no - thank you
You should only need once to login and get davice id and local key. After that, it should work without account being active. Or you can ask support to extend account.
But yes, it's not the best approach, I do agree. Wish there was alternative for only device I need :D
@@BeardedTinker I used to have 40+ Tuya devices. Thanks to ebay I have now 0. Replaced with Athom, Sonoff, DIY, etc. No, no more cloud. Meross even blocked my sockets when they realised they were integrated with HA. No, thank you. There are alternatives
@@BeardedTinker nope, when the trial expires all your local Tuya devices go offline and you need to login back into Tuya account and request a free extension.
been there, done that
Yes. But you don’t have to pay. You just enable it. I have to do it once in the last 12 months.
@@SlackerLabs you did not get my point: from 12m they decreased recently to 3m, some people got only 1m, wait a bit and you will see in the future what is for free from Tuya ;-)
No permissions. Your subscription to cloud development plan has expired.
What should I do? help me pls.
You need to have valid (can be free) subscription. Try to contact tuya if it expired to extend it
How i Configure the Custom Components to work?`Must add it to my configuration.yaml
As in custom component for specific device or as in HACS? But none of them need to go to configuration.yaml file.
@@BeardedTinker hey :) after i deleted the old tuya-local Integration + restart. Suddenly the right “type” was selectable.Thank u
Hi I follow the setup guides and when I try to add "add Device" am getting "add device using smart industry app" when I scan the qr code it ask me to download "smart industry". I already have the tuya app install. any idea what am missing to add the device. ??
Not sure if that's the issue with device type you are trying to add maybe? What device is that?
hi,
is it an active integration yet?
I installed the Tuya local, but I can't add the device (smart plug),
The IOT platform is changed a bit and I found the local key @ Device Management/Query Device Details in Bulk or is it an wrong place?
Merry Xmas!
Yes, it is - I'm still using it.
Can I install this on a private VPS? So that I can control it anytime and anywhere through a Restful API.
Once I create the yaml file and add it to the custom_components folder, what do I do? How does it know that the configuration corresponds with my device’s ID?
Hey man. i am having a problem when, in minute 9.53 apear a list.
on my f12 the list never appears
Did you select everything as per video - network tab, list etc. Also, on web page do you see list in Device logs.
got a question.... when creating your own device yaml, how do you get the Model information to populate in HA?
Model name? It was copied from Tuya Web site.
@@BeardedTinker appreciate the quick response.
What I am referring to is the Model field in home assistant is "unknown" where as the original Tuya integration will have this field populated. Want to know how to populate this.
Hi, what if after 6 months the Tuya Services contract expires? Does tuyalocal then continue to run with the keys in HA?
Mine is still working. I think I got 12 months at the time I signed up for it. So can't tell you. With local key, it could work, but you never know with Tuya.
is there a maximum number of devices that can connect to HA using tuya local?
Excellent question - not that I know, but never looked into that one deeper.
Hi, for a new device not compatible, i create a yaml file so? Or need another thing? Thanks
Yes, create file as shown (content) and place it in tuya local folder. Or open issue on GitHub,, post there data, so others can get support for the device too.
amazing! but still I have issue like localTuya, I can't get the local_key from smartmi air purifier p1 and 2. even I see them on tuya app. what can be the problem, I get permission deny on 'get device id'
Try changing category (for example from Smart Home to General Device - or vice versa) i API Explorer list. I know I got same results when playing in one category next category worked OK.
@@BeardedTinker region of my smartmi app, smart life app, tuya cloud account, is important?
Not 100% sure. I think it will autodiscover it. And there should be only 3 or 4. You can see it in URL of website when you login in the portal. For me it's EU.
I just had to extend my "free" account and I am worried that in 6months when it expires how I will get my local keys easily. Does anyone know of a local network TUYA scanner that can pull these keys?
There are few tools, but all of them are currently depending on cloud IoT account. If you find any, drop me a line
On adding a custom .yaml device file, do you need to do anything else special for TuyaLocal to find the device? i.e. restart? I am still getting 'device not found' after adding. Is there any logs or diagnostics to debug .yaml files?
if new device yaml has been created, you do need to restart HA I think. Did it some time ago, so sorry if forgot.
As for debug, in configuration.yaml file, make sure you have following:
logger:
default: warn
logs:
custom_components.tuya_local: debug
@@BeardedTinker thanks BT. Great video by the way. Very clear and concise. From what I can see Tuya Local is more powerful than Local Tuya especially when it comes to devices that don’t fall into the standard light, switch, thermostat etc categories. The Auto IP didn’t work for me. I had to set the devices local ip addresses manually, everything else spot on. Well done.
@@ablazejez Thank you for kind words and glad you got it working.
How do you manage your subscription? i could not find the way to renew my subscription. When trying to get "local_key" i get this error: No permissions. Your subscription to cloud development plan has expired. thank you.
At the time of the recording, subscription was still active. Not it's not anymore and I can't extend it even through standard free extension procedure. But device works with Tuya local even with inactive subscription.
Is it possible to run tuya-local in python? I want to find a way to do all the scripting needed in python if possible
As in custom converters? Not sure, never tried. But you can check on integration Github page. Maybe someone tried it in discussion there.
Off topic: I have the exact same issue you’re having with the Android TV integration. The exact same error too. Any ideas what could be wrong there?
You made me fix it :) For me the issue is that IP address changed. So I just removed existing integration and created new one with new IP address...
@@BeardedTinker the same issue was for me. Thank you!
Any chance to get localtuya or tuyalocal on home assistant in docker container ?
They are not add-ons. No additional docker is needed. But you need to install HACS and then you can install one or the other
Here is how to install HACS hacs.xyz/docs/setup/download
Select Container type of HA install and you'll have two options for you
what do you do if the dev acc is expired i get error msg
“msg”: “No permissions. Your subscription to cloud development plan has expired.”,
Try requesting an extension of subscription. You should get it after few days.
@@BeardedTinker I did yesterday and looked today it was back rewatched your video I am now local👍
I dont get a local_key anymore, did they remove this? How can i now get local keys?
I't still working. Just checked - go through the steps here once again.
ruclips.net/video/apWfjargTpA/видео.html
@@BeardedTinker That´s strange, i get local key on my old devices, but local key field is empty on my new device.
@@Xpl0jd1 did you check in both Get device info places ?
@@BeardedTinker Deleted the device, added it again, now the key show. :o
Is this actually local? It's not as fast as LocalTuya.
Same as Local Tuya - as local as it may be currently...
It used to be fine now after a few hours the devices lose connectivity
I didn't see that behaviour myself. Does the device also lose connectivity if you check SmarLife App? Have colleague who has that problem. The issue was the device itself.
No, the smartlife app doesn't lose connectivity, but this problem has just arisen
If the power goes out, it won't connect again. I have to restart the home assistant
I've seen similar with other integration but they usually reconnect after some time. But haven't experienced with this one so far. You could try opening the Issue on GitHub for this.
nice video. but i have a problem: i become this message when i add my device id and local key: Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect. can u help me?
or must i delete me cloud tuya integration first before it can run?
I think it can only talk to one integration at a time - if I remember correctly. I needed to remove device from existing integration before I was able to add it
But check documentation to be sure.
@@BeardedTinker wow thanks for the fast answer, i did me best
github.com/make-all/tuya-local
Just checked the documentation. It does mention that some devices can talk with only one integration, so try that.
I can not select the menu as shown on 6:24 in your video. So how do I get my local keys?
You should in Cloud Menu select API Explorer and it should show you this menu. If there is any other method on that site, I'm not sure of that.
Localkeys should be in either General Device Capabilities section or mart Home Devices section.
@@BeardedTinker Thank you for your kind answer. Found it! I feel a bit silly, because first I just clicked on the menu entries, but not on that tiny black triangle to unfold the menu in question. How stupid of me.. haha..
No problem! Glad you got it working! That's only thing that matters!!! Have fun with this integration. ;)
Thanks!
It's Device Management > Query Device Details now
If you have the device integrated in local tuya.... you can't add in local tuya.... you must delete the device first.
Yes, that's known limitation of Tuya devices - one of many :) Thanks for pointing it out.
HI! 6:41 on video "local key" - I can't find it... Can you check? 24.11.2023
They did change menus on web a bit - but if you first pull the device ID, after that, go in API EXploprer and in top left menu, select Smart Home Basic Service - and than under submenu Smart Home Device Management select Get device details, you should see it. Just tested few minutes ago.
iot says my subscription has expired and won't give me the information on my device... when I go to renew... they want $250 for the year or some shit...
you can try creating a new project, it is unlimited but you will either have to renew the free 'subscription' monthly or just create a new one each time (which admittedly sux ballz)
I had the same problem. I sent a message to the support. I said that as a private user I had only 2 plugs. The support gave me some free months more. I saved all keys and datas and bye bye tuya.
@@chrisrosenkreuz23 They don't allow a renew... I tried that...
@@blitzpulli Yea, I did the same... no more TUYA in my home... I'll keep the one lightbulb I have left...
@@crashcreeley well it works for me, and others too. Try creating a new project and maybe you will be able to renew afterwards. For projects created before a certain date, the renew option doesnt work.
Thank you sir.
Thank you for watching and comment Ron!
When I try to get the local key I get "msg": "No permissions. Your subscription to cloud development plan has expired.",
You need to request extension of subscription in order to get the key. Usually you get 3-6 months extension free.
@@BeardedTinker Once you get the key and it's working when your account expires again will the device stop working?
No, at least, for me, after getting the local key and device id, they continued to work after expiry. I did once again ask them for extension, so it is now active, but it worked
@6:35 I get "msg": "No permissions. Your subscription to cloud development plan has expired.", 😞
You need to try and renew your free subscription. Mine still hasn't expired so can't tell you exactly how. But you should still be able to do it for free.
still not useblae, how do i get it to work when my 1 mont expired. just throw my devices in trash
there is no way i can get local key now
If you have thrown devices in trash, you'll not need key. If not, you can request extension of free period.
does not work with ir/rf remote controlers
But it does. You can control via IR Hub some air conditioners and heat pumps. Maybe not useful in your case, yet it does work with IR devices