If you add the Homey skill to Alexa you will get duplicate devices, but that’s not what you want to do because the skill adds Homey devices to Alexa, not the other way around.
There are two Homey Alexa/Echo apps. The ‘Amazon Echo’ one works the best for me. It gives you the option to add Alexa routines (and, via routines, scenes) to Homey. From memory, the ‘Amazon Alexa’ one allows you to add Alexa-attached devices to Homey. You add only the ones you want.
Another option is the free Voice Monkey skill and web site that allows you to run Alexa routines via a web call, which Homey routines can do.
The control of my heatpump by the “official” Tuya-app is still going strong. No indication of a closing day yet. I consider myself a lucky guy, hopefully it stays that way
This morning I received the following message. Most likely it will not affect this app, but it will perhaps affect the community app that a lot of people are still using. If that becomes unusable because of this measure, it will increase the importance of an official app. Good luck @Doekse !
Dear Developers,
Hello! We’ve noticed that during the firmware development process, some developers have set up an unreasonable message reporting logic, resulting in an excessive amount of data. This not only increases device power consumption and affects the stability of device control, but also leads to an increase in consumer complaints and after - sales costs.
To optimize the message reporting mechanism and ensure service stability, we issued an announcement regarding the limitation of message reporting data volume in July 2024. According to the original plan, starting from August 5, 2024, we would stop the free policy for message reporting data exceeding the daily limit. However, considering that some developers may not have fully noticed this change, we have decided to provide a certain transition period.
After careful consideration, we have decided to postpone the implementation time of this policy adjustment to January 1, 2025. That is, for products newly created after this time point and the corresponding newly ordered and authorized devices, if the number of message reports exceeds the daily limit, they will no longer enjoy free services. If developers have special business - scenario requirements, they can purchase additional message reporting volume as needed. Products created and devices authorized before this date will not be affected.
We sincerely hope that developers can make use of this transition period to reasonably optimize the message reporting logic and jointly improve the user experience.
I struggle with creating the Virtual Device. I installed the “Device Capabilities” app and select the Advance Virtual Device. I can select an empty advance virtual device or from a template.
Since a week I have gotten the code (1010) with Tuya official app. Can’t login Tuya on Homey anymore. I still had a Home Assistant as redundant system where Tuya still works.
Also, can’t connect with the Tuya community app. It says “Permission denied”.
I think your best option is to raise this in the Tuya Cloud (community app) topic.
At first glance I think something with your Tuya IOT project hasn’t been setup properly
Any updates on this topic? Tuya signed the “Talks With Homey” program but the App is clearly broken. At the same time the community app is unsuported (although I’m super grateful for all the effort Jürgen put into that app). I have around 30 Wifi devices that are living a bit dangerously if this cannot get solved in an “official way”.
There must be another way to get Wifi devices directly into Athom/Homey without going through Tuya?
Yeah I don’t understand really. Because IOT is already active and renewed. Its works in Home Assistant tho. It has been a week since Tuya Official and Tuya community stopped working. I just can’t get it to work.
The few Tuya devices that I still use (4x recessed downlights, 2x wireless switches, 3x lamp bulbs) still work with the official app, but it does seems to be slower since last summer.
No issues since I switched over to Matter over WiFi Sonoff relays to control all of the lights with dumb toggle switches though. In fact, that’s been pretty amazing.
Same here. Could someone help me somehow with that? I just renewed my flat, bought Homey and putted some devices and also tuya ziggbe switch modules and it’s not working for me, so Homey is a little useless for now.
I posted this in the wrong topic: @Doekse urged us not to assume too much. We should be patient and wait for news to come. For some reason he had high hopes on an accidental meet up with the people from Tuya at CES. Perhaps it is because the setting is then somewhat more informal. I don’t know.
Anyway… I think we’ve been patient for a while now and an update is appreciated
Unfortunately, I didn’t end up meeting with Tuya at CES. However, I did reconnect with my previous point of contact from Tuya, who is now working with a different company. This person was previously part of Tuya’s partnerships team and shared some insight into the situation.
Apparently, there was internal debate at Tuya between the partnerships and sales teams. The partnerships team aimed to expand Tuya’s presence across other ecosystems, while the sales team preferred a revenue-driven approach by charging for integrations. After my contact left, the sales team took control, pushing for a pay-to-play model instead. A disappointing turn of events, in my opinion.
To make matters worse, Tuya has not been responding to any of our recent inquiries, which makes it unlikely this issue will be resolved in the near future.
Tuya’s push towards their CUBE API is not something we can align with. If we were to adopt their approach, it would mean setting up our own Tuya Cloud, requiring every customer to first connect their Tuya-based devices through a Homey-branded Tuya app. Only after that would they be able to connect the devices to Homey as they could previously. From a user experience (UX) perspective, this would be far from ideal—arguably the worst-case scenario. Especially if we end up being the ones paying Tuya for a CUBE API license, while also covering the costs of running the cloud infrastructure and funding all the development efforts.
We’re open to discussions about regaining access to the IoT core we had before. However, Tuya has made it clear that this option “will only become more expensive in the future.”
Their business strategy seems apparent. Tuya has likely realized that selling devices without ongoing revenue from cloud services isn’t sustainable. That part makes sense—they’re transitioning to a model where partners pay a license fee and take on all cloud hosting and associated costs. While this might work from a business standpoint, it offers no tangible benefit to the end consumer and only adds unnecessary complexity, in my opinion.
In that case perhaps it is best to pull the pin and just remove the app completely.
This is very disappointing though. I understand Tuya also want to have some profit, but this is just unfortunate.
As the Tuya Cloud app is not actively being maintained anymore, is it an option that Athom puts some developers on that app? Or perhaps even the Tuya Zigbee app (there is also some back log in adding devices)
