I did the same things as some other members did here. Created a virtual Tuya device with the QR code, made a flow checking every 15 minutes switching it on or off and when that results in an error the Tuya app is restarted. Depending on the status of every step I get a different message on the timeline so I can follow along.
I saw that last night the app has restarted 3 times. I randomly check some Tuya devices that didn’t work the last week and hooray , they do actually work now! Seems this is a working workaround.
I personally haven’t experienced any issues with running it every 30 minutes. I also don’t think this flow puts much load on Homey, since it’s quite a simple flow.
As a small update: last night, the app restarted at 5:01 AM, 5:31 AM, and 6:01 AM, so that’s three restarts in a row, exactly 30 minutes apart.
So far, 30 minutes seems to work perfectly fine for me, and I haven’t noticed any performance issues with Homey. I would personally stick with the 30-minute interval.
I have now to restart about once a day. I first see no reaction and 10s timeout. When restart your app it works again. This follows all the messages I read here and people creating a flow checking every 15 minutes and restart the app. It can work but to me a very strange solution, is this the only way ?
Wow people, aren’t we all a bit impatient? @Drenso stated that they are aware of the issue, and that the reboot is a temporary thing until Tuya sorts the rate limit issues. In the meantime they are also working on another update to further streamline the app implementation (they mentioned that in the support ticket I have).
In any case, I am will be looking into transferring the devices to local control, and if not possible throw them out. Don’t want to rely on this Chinese cloud connected crap anyways…
Why? Tuya ran without any issues for the last 7 years in my smart home at least. Only today do we have an outage, which isn’t even Tuya’s fault either, since they already mentioned there’s a bug in the Homey app that spams their API.
I try to run as many devices via the cloud as possible, it’s way more secure than allowing all the cheap and insecure devices to communicate with other LAN devices and infect other devices in the network with malware. If you enable Client Isolation and block all LAN connections (at least in IoT network I would highly recommend this, especially with setups like mine where I use many outdated and insecure devices from the less reputable manufacturers/backends as well), all local connections get blocked and if a device ever gets hacked, at least it stays at that device. It can’t spread through the network since the devices don’t have access to other network resources.
Well, that is not possible with Homey and this app
In any case, you are missing the last step: not allowing internet access at all. If your device gets hacked, it can still participate in ddos attacks, oversaturate your WiFi network causing local outages and what not. Having something connected with the internet is a sizable attack vector.
Internet connected IoT devices are basically bad practice, especially if they are not updated frequently (which is the case for almost all brands). Sadly enough, this also holds for a lot of consumer routers, which are not updated etc.
Having local only connectivity without internet is the only safe way to do things.
Hi, except ‘switch’ still no codes available to work with.
But the good news is that with help from ChatGPT I now pull the data (e.g. status info, temperature, mode, etc.) directly from the Tuya Cloud (IoT platform). Work really well!
That’s true, it was about the Tuya devices in general (also before I had Homey, was just using Google Home at the time that I bought my first Tuya device).
Yes, it is an attack factor, but every device is connected to the internet nowadays, even the devices that aren’t specifically “smart” devices (like my NAS, WiFi AP and printer can also all be controlled remotely via the server). Also a smart home is pointless without it IMO, I mean why do you even need smart devices at all if nothing can be controlled remotely? So having local connections blocked is a safe method that protects your local network against attacks originating from external sources (f.e. the manufacturer’s relayserver or an outdated Bluetooth stack) while still offering the convenience of a smart home that you’re used to.
Also, even local-only devices can compromise other devices in the network, for example the T95 Android TV boxes are pre-loaded with malware from the factory. Or the devices can get taken over via Bluetooth by someone nearby if the device has a vulnerability (which is even more likely if you block internet access, since the device can’t auto-update in that case).
That’s usually the user’s fault. They don’t update their router, probably because most don’t even know what a “router” is (and just see it as “the thing that runs the Wifi”). However, more and more routers have auto update now (f.e. Deco, which are very popular here in the Netherlands) which automatically download updates from the internet without the user having to do anything, which is a good practice for any device really to update them regularly.
That’s where you are wrong; this is exactly where Homey comes in so you only have one entrypoint for your smart home, and not several.
That completely depends on your device choice. Safe devices should not have their Bluetooth running continuously, but only during fixed initialisation windows. This is actually part of EU legislation.
I do not think random Chinese boxes from an unknown supplier are a very good choice.
No, this is mostly because devices don’t get updates (at all or too late) from their manufacturers. They tend to only push updates once it is already abused in the wild, and sometimes this is just because they simply do not update their dependencies regularly. Unfortunately, Athom also does not update their dependencies regularly; if you use the CLI you always see NPM audit errors for example.
If internet connected, yes. If not internet connected and properly secured there is no real need.
What a discussion. Maybe it’s best to stay on Tuya topic?
Quick notification from our side: we just released an update which refactors some token handling, which in turn should hopefully resolve the lockup issue some people are experiencing. Love to hear if that is indeed the case!
For me the app runs fine and devices can be controlled fine, but the door sensor connected via the Tuya Zigbee hub does not report its status. V1.5.6 Tuya | Homey
Thank you for answer and heling,
It’s now fixed. I de- and /reinstalling Tuya, add new all my (working) devices and and now it’s running. Not so funny…
, they do actually work now! Seems this is a working workaround.
I try to do the same, just no cloud if possible
