Thanks for thinking along, @Tom_ten_Den ! In the end it worked! I did exactly the same as what I mentioned before, but for some reason now it did work. And yes, it is as simple as adding two IDs and deploying the app.
For some reason I bought a 2 gang switch, so I now have two switches in Homey whereas I only need one. If I delete the second switch from Homey, they’re both gone. So I guess, I’ll have to live with that.
I try to add a Tuya zigbee temperature and humidity sensor using the Tuya Zigbee app on a Homey Pro.
The manufacturer and product id are listed in the app as supported:
_TZE200_a8sdabtg
TS0601
Nonetheless, the device is added as a unknown Zigbee device.
Any suggestions?
First of all, welcome to the Homey Community!
To make sure you are aware of the forum rules, please read the Welcome to the forum! post here.
As for your question, the answer lies in the first of this topic.
So i tried adding the device to my own fork of the project and added it as an app in Homey. I can get the door and window sensor to work, but the RGB spot does not work properly. I can change colour but dimming and colour temp does not work. I tried the spot at a friend with Home assistant, and there the dimmin and the colour temp works. Any idea if there is something more I need to change to get it to work?
The fork can be found here: GitHub - antonhagg/com.tuya.zigbee
“ids”: {
“modelId”: “TS0505B”,
“manufacturerName”: “_TZ3210_bfwvfyx1”
},
“endpoints”: {
“endpointDescriptors”: [
{
“endpointId”: 1,
“applicationProfileId”: 260,
“applicationDeviceId”: 269,
“applicationDeviceVersion”: 0,
“_reserved1”: 1,
“inputClusters”: [
0,
3,
4,
5,
6,
8,
768,
4096,
61184
],
“outputClusters”: [
10,
25
]
},
{
“endpointId”: 242,
“applicationProfileId”: 41440,
“applicationDeviceId”: 97,
“applicationDeviceVersion”: 0,
“_reserved1”: 0,
“inputClusters”: ,
“outputClusters”: [
33
]
}
],
“endpoints”: {
“1”: {
“clusters”: {
“basic”: {
“attributes”: [
{
“acl”: [
“readable”
],
“id”: 0,
“name”: “zclVersion”
},
{
“acl”: [
“readable”
],
“id”: 1,
“name”: “appVersion”
},
{
“acl”: [
“readable”
],
“id”: 2,
“name”: “stackVersion”
},
{
“acl”: [
“readable”
],
“id”: 3,
“name”: “hwVersion”
},
{
“acl”: [
“readable”
],
“id”: 4,
“name”: “manufacturerName”
},
{
“acl”: [
“readable”
],
“id”: 5,
“name”: “modelId”
},
{
“acl”: [
“readable”
],
“id”: 7,
“name”: “powerSource”
},
{
“acl”: [
“readable”,
“writable”
],
“id”: 18,
“name”: “deviceEnabled”
},
{
“acl”: [
“readable”
],
“id”: 16384,
“name”: “swBuildId”
},
{
“acl”: [
“readable”,
“writable”
],
“id”: 65502
},
{
“acl”: [
“readable”
],
“id”: 65533,
“name”: “clusterRevision”
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“identify”: {
“attributes”: [
{
“acl”: [
“readable”,
“writable”
],
“id”: 0,
“name”: “identifyTime”,
“value”: 0
},
{
“acl”: [
“readable”
],
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“groups”: {
“attributes”: [
{
“acl”: [
“readable”
],
“id”: 0,
“name”: “nameSupport”,
“value”: {
“type”: “Buffer”,
“data”: [
0
]
}
},
{
“acl”: [
“readable”
],
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“scenes”: {
“attributes”: [
{
“acl”: [
“readable”
],
“id”: 0
},
{
“acl”: [
“readable”
],
“id”: 1
},
{
“acl”: [
“readable”
],
“id”: 2
},
{
“acl”: [
“readable”
],
“id”: 3
},
{
“acl”: [
“readable”
],
“id”: 4
},
{
“acl”: [
“readable”
],
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“onOff”: {
“attributes”: [
{
“acl”: [
“readable”,
“reportable”
],
“id”: 0,
“name”: “onOff”,
“value”: true,
“reportingConfiguration”: {
“status”: “NOT_FOUND”,
“direction”: “reported”
}
},
{
“acl”: [
“readable”
],
“id”: 16384
},
{
“acl”: [
“readable”,
“writable”
],
“id”: 16385,
“name”: “onTime”,
“value”: 0
},
{
“acl”: [
“readable”,
“writable”
],
“id”: 16386,
“name”: “offWaitTime”,
“value”: 0
},
{
“acl”: [
“readable”,
“writable”
],
“id”: 16387
},
{
“acl”: [
“readable”,
“writable”
],
“id”: 32770
},
{
“acl”: [
“readable”,
“writable”
],
“id”: 53296
},
{
“acl”: [
“readable”,
“writable”
],
“id”: 32769
},
{
“acl”: [
“readable”,
“writable”
],
“id”: 32768
},
{
“acl”: [
“readable”
],
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“levelControl”: {
“attributes”: [
{
“acl”: [
“readable”,
“reportable”
],
“id”: 0,
“name”: “currentLevel”,
“value”: 248,
“reportingConfiguration”: {
“status”: “NOT_FOUND”,
“direction”: “reported”
}
},
{
“acl”: [
“readable”
],
“id”: 1,
“name”: “remainingTime”,
“value”: 29026
},
{
“acl”: [
“readable”,
“writable”
],
“id”: 16384
},
{
“acl”: [
“readable”
],
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“colorControl”: {
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“touchlink”: {
“attributes”: ,
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
}
},
“bindings”: {
“time”: {
“attributes”: ,
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“ota”: {
“attributes”: ,
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
}
}
},
“242”: {
“clusters”: {},
“bindings”: {}
}
}
}
Ok, I did some research and this device specify these clusters: 0,3,4,5,6,8,768,4096,61184 where the device that was previous implemented (the Gu10 device) had these specified in the code: “clusters”: [0, 3, 4, 5, 6, 8, 768], will this make any difference? There seems to be alot of custom clusters and attributes : Lighting Products-Gateway Connectivity-Tuya Developer
Read the first post, your device is probably not in the app yet. Last update was 7 months ago and the names change constantly on Tuya products. You can also get the app from Github yourself and modify it.
We agree this is absolutely not for everyone?
You’re right, this requires some knowledge, but you can learn it.
It’s pretty easy if you have some step by step guidance. At some points I didn’t really understand what I was doing. But if it works…
I have seen some people mention the Plant Soil sensor might work, or might not, has anyone got one working from aliexpress and can confirm it works within this app without need of another hub? I see some look like this (bluetooth and or wifi they say): https://nl.aliexpress.com/item/1005007422726976.html and https://nl.aliexpress.com/item/1005007329498149.html and this one has a selection between TUYA or ZIGBEE versions: https://nl.aliexpress.com/item/1005007443398328.html
I have this one and it works very well. Temperature and humidity with Zigbee connectivity. It’s a bit more than the one you were looking at though, but it offers soil temperature in addition.
Thanks, does that work without a hub tho? On the AliExpress site they say it needs a hub for setup
Hi that’s where your Homey is for, you don’t need an extra Zigbeehub.
Best regards Peter.
Right, it’s a Zigbee device, so it works with Homey (which is a Zigbee hub) and it’s a Tuya white label device so it works with the Tuya app (well, that’s not a given, but in this case it’s supported).
Valve Controller
where i can find one from the list wchich will pair with homey?
Hi, I am quite new on the whole Homey Pro thing. I have bought a Tuya Zigbee door sensor and in both versions of the Tuya Zigbee app, it shows me a generic Zigbee device which is unusable.
I also have a Tahoma and if I try there, the door sensor is added perfectly and works fine.
So now I tried to use the Tahoma app but there the door sensor is not listed. So what should I do now?
the ID is _TZ3000_au2o5e6q
Product ID TS0203
Sorry, I just noticed, I do not know how but there was a problem installing the experimental version.
Now I have nicely cleaned up the app and installed the experimental version again and now everything works fine!
Kudos to the developer !!!
Smart air box no data
Hi @johan_bendz
just instaled the alrbox for the forst time. This went well but it dos not give any data. Already restart the app ene restarted Homey but this dos not help.
Tuya version: v0.2.73
Homey version: 12.4.5![image]
Log:
f5cfa2b0-aca4-41da-8fde-526f5c3920b7
@johan_bendz , any plans in the future? or it’s dead in the ditch?
