Perhaps Athom needs to close this thread for further responses until (if ever) the issue with the app is resolved.
So how do I fix my broken devices then? Because itâs not working anymore after using it from Juli 2024⊠Restarting the app, does not fix it (it did the first time but some days later they are again unavailable).
You donât.
It is not really clear in the first post, but basically this is the situation: Tuya wants Athom to work in a different way than using the basis on which the âofficialâ app is currently setup. Athom doesnât agree with that.
So, Tuya decided to break the current app from their end while still keeping the option open for Athom to use the different way to create an app.
If the old âofficialâ app still works, your in luck. If it stops working, youâll have to look for other solutions.
Okay clear. Maybe the official statement from Athom can also be posted/edited in the first post of this topic because you canât find this info over there.
Where can these reasons be found?
In this thread.
There you go. This is the best explanation of the current situation. This message should be added to the first post
Iâve just updated the first post in this thread with our official statement. Weâll also be adding it to the news article on our website.

Update February 2025: In 2024, we proudly announced our partnership with Tuya to enhance device support within the Homey ecosystem. However, Tuya unexpectedly revoked API access, breaching our agreement and leaving a lot of smart homes in the dark.
Over the past several months, weâve diligently attempted to resolve this issue with Tuya. Unfortunately, it has become evident that a resolution is unlikely in the near future, if at all. Tuyaâs proposed solution involves adopting their TUYA CUBE API; a self-hosted Tuya cloud requiring a paid license. This differs significantly from the TUYA IoT Core we previously accessed. Due to the substantial costs involved and the considerable effort required to implement this solution, we find it unfeasible to proceed under these terms.
As a result, the official Tuya App for Homey is currently non-functional for new users (and might also stop working for current users in the future), displaying an error message stating, âNo matching app user information.â We have ceased development on this app and have removed it from the Homey App Store. For users seeking alternatives, the community-developed Tuya Cloud app remains available, though it requires creating a developer account and may involve additional setup steps.
At Homey, our goal is to work together with partners to make the smart home better together. We are doing this with over 250 official Works with Homey partners and hope that Tuya will reconsider and join us again on this mission in the future.
The best way to solve this issue is to athom directly implement on the homey device an mqtt brocker and add natively zigbee2mqtt who support a lot of devices from tuya.
All this feature without any external devices like an raspberry pi.q
There were proposals like this but ignored for some reason
I am not sure it has something to do with a license since Homey SDK is open source and integrating this implementation with open source is not a problem (?)
That would really help to bypass many problems
Zigbee2MQTT doesnât help with communication to the Tuya Cloud, unfortunately.
But can do all tuya support localy.
With zigbee2MQTT, you can connect any Zigbee device locally. However, Tuya WiFi devices require a connection to the Tuya Cloud and cannot operate locally.
So its a good idea to directly host or implement an zigbee2mqtt broker on the Homey app and to conect it natively with the homey zigbee implémentation.
For the purpose of this discussion, Tuya makes two different types of devices: ones that work with WiFi, and ones that work with Zigbee.
Those are two completely different protocols, and Zigbee2MQTT only works with the Tuya Zigbee devices, not with Tuya WiFi devices (which this thread is about).
Besides that, Zigbee2MQTT wonât work directly on Homey anyway as it doesnât work with multiprotocol firmware.
Many WiFi devices have a Zigbee counterpart so it would still be super beneficial
Thatâs ok I think
It could be a part of Experiments (wipe old implementation completely/switch FW)
But I do understand it is a dream, sorry for going offtopic
Tuya WiFi devices have completely different internal components than Zigbee devices, itâs not a matter of âjustâ switching firmware.
Isnât this just about protecting their own eco system and selling their own hubs in stead of us buying loose devices and connecting them to third party hubs like homey?
What hubs?