Hello
Is it possible to control devices which are connected to smart life or tuya cloud?
Thanks to all
Hello
Is it possible to control devices which are connected to smart life or tuya cloud?
Thanks to all
Welcome to the Make community!
Make doesn’t have an integration for this third-party service.
If the external service has a Developer API Reference/Documentation then you should be able to integrate the endpoints in Make using the generic HTTP “Make a request” module.
If the external service allows you to register webhooks, then you can create a trigger to wait for incoming webhook requests in Make using the generic Webhook “Custom webhook” module.
You can also suggest for it to be made in the Idea exchange. Don’t forget to search for it first, in case someone already suggested it!
Ttlock , tuya and smart life are biggest hardware acces clouds on world.
Why u don’t have tight integration ?
I use beds24 and want to control all this elements for our hotels. Beds24 I see u have in your list
So it’s not plug and play as I understood
Thanks Alex
You might want to reach out to Tuya and ask them to create some apps in Make for their architecture.
Or, as Sam indicated, you’ll need to track down their API and interact with it using the HTTP modules in Make.
Because nobody supported/voted for this feature in the Idea exchange, so it is currently a low-priority request.
Even Zapier doesn’t have a Tuya integration.
The more users suggest/vote for a certain feature request, the higher priority it gets from the Make dev team.
What about iobroker?
Can you connect there?
Over iobroker I could connect tuya then
I’m something of a home automation nerd outside of work - so the following is my own experience and opinions!
Tuya is tricky to work with. Their business model is in getting the device makers who embed Tuya functionality to pay them $$ (sounds reasonable!). If the device maker wants to embed more features, they have to pay more. Unfortunately, as a lot of the device makers are listing on Aliexpress where price is paramount, they go for bottom dollar every time.
Device makers have to pay to expose Alexa, Google Assistant, IFTTT and SmartThings controls. So the upshot is that not every device will support all of these.
Make has an App for IFTTT and for SmartThings, so if you’re lucky you might be able to use either of those as a gateway. To check, open each device in the SmartLife/Tuya app and hit the edit icon (pencil). It will then list the “3rd party controls” that are available for that device.
@Drago1009 I should add - although it has a REST API, iobroker runs on your local network, inside your firewall (as does Home Assistant).
The only way for a cloud service like Make to communicate with iobroker would be for you to open a port on your router for port forwarding. This isn’t generally a good idea as it opens up your home network to security risks.
The only realistic option is to use a cloud service that can connect to Tuya Cloud, such as Smart Things or IFTTT, if supported by your devices.
I’m completely new to Make. I had looked at it back when it was recommended by Jason Snell on MBW 855 back in January. I couldn’t find an integration between Make and Wyze, Kasa, Feit or Stream Deck. I’d like to automate plugins/lights in a home studio.
I dropped back in today to see where things are and ran right into this timely thread to find status quo on the above.
@DavidGurr_Make As a home automation enthusiast, I’m guessing you’d be pushing for Make to compete with IFTTT in these areas. Is there just no interest?
I’m thinking Make would pull IFTTT users in if it could compete in home automation. On the other hand, maybe Make is interested in less in the studio/home office crowd and more in the… “larger” small business segment?
Unless I’m already working inside of Make, I’m not sure why I would use Make as a middleman App if IFTTT already has a direct integration to the end result.
You would need to use Make, or a similar tool, if IFTTT was unable to do something Make can.
Hi @AdamEsq. Welcome to the Community!
The following is just my opinion rather than the company line …
The main reason is that Home automation is best done as close to the device being automated as possible. To be seamless, home tech has to be as reliable as the phone service or your TV. If it’s not, it just generates more frustration. This usually means making it tolerant of Internet disconnects and even local WiFi disconnects. In my home automation setup, I have timers running in the devices themselves. The timer values are set by my openHAB home automation server that’s running inside my network. If the internet goes out, it doesn’t affect that. If the WiFi goes out, the timers continue to run.
My own usage with Make is one thing only … as I work from home, I have an IoT light bulb outside my office door to let the rest of the family know if I’m available to be disturbed. I have a scenario that receives a Webhook from Zoom when my presence status changes - if I’m in a meeting the light is red, if I’m in focus time it’s yellow, and otherwise it’s green.
Everything else runs inside my own network.