Anyone have included Nedis smart ip cameras, smoke detektors og smart plugs into Homey?
Nedis is a Tuya product, but has its own app.
1 Like
Do you know if Nedis smart PIR is supported in Homey?
@Tirrazo
You can try the Tuya Zigbee app. If you have a Homey Pro.
https://homey.app/nl-nl/app/com.tuya.zigbee/Tuya-Zigbee/
1 Like
They also have wifi based PIR. Then youâd give Homey Tuya Cloud app a go (like Mike wrote, this is also only available for Homey Pro atm).
1 Like
I bought the Nedis smart PIR motion sensor (Zigbee) and it is possible to add it directly to Homey through Tuya Zigbee.
The only problem is that Homey think this is a switch and not a sensor.
Tuya Cloud, isnât that only Wifi based components?
Not if you use a Tuya zigbee hub, and add the devices to Tuya Smart mobile app. Then they become available in Tuya Cloud. Probably usable through tap-to-run scenes and / or by Raw commands
Howto:
1 Like
Thank you for this information!
The way you explain how to get text messages from the devices takes to much time for me now.
When I bought Homey Pro, I thought you never had to have any extra hub/gateway since Homey says they are supporting Zigbee for instance.
But if I buy the Tuya Zigbee hub, would that only recognize Tuya Zigbee devices?
I have another brand called Nedis which communicates through Zigbee. Nedis also have a gateway.
So either you have to stick to one brand, one type of communication protocol if a Zigbee gateway canât connect with different brands.
And Homey have to support this brand, for instance the Tuya or Nedis Zigbee gateway.
Well, thatâs the marketing language.
In the real world, for a lot of / almost all devices it is needed theyâre have to be supported by an app. And someone has to write and support that app. Like, Athom, or the brand itself, or a community developer (unpaid volunteers).
So as you noticed, thereâs luckily some workarounds here and there, but youâll have to put in some effort.
So, some gear is plug and play (pray), and some is not but Homey can still control it
What Iâd like to advice: before you buy any smart gear to use with Homey, check the app store if your device is supported.
Lots of brands sell re-branded Tuya devices. With zigbee is the problem brands can adjust the driver a bit, to their flavour (to force you to buy only their brand).
I donât know if thereâs an overview somewhere, but Iâm under the impression Aquara, Ikea and Hue for instance, donât work, or not for 100% with Tuya zigbee hub.
A Hue hub / Ikea hub probably doesnât work Tuya zigbee devices.
I have Ikea, Aqara and Tuya (Neo coolcam) zigbee gear at my Homey, and it runs pretty stable:
Yes, there is sooooo much different gear for sale, itâs impossible to support all
The Tuya Zigbee app f.i. is pretty amazing however, when you see the list of devices it already supports.
Did you install the test version by the way? It becomes available in the app store when you add /test to the url.
1 Like
Thank you very much Peter!
The digital world can be very helpful, simple and easy to use. But it canât also be complicated, frustrating and not joyful at all.
This topic is interesting and the idea to make the IoT really work is possible, but since there is so much competition, there will still be a lot of different charger types, different software communicating through the same protocol and make you buy all the bridges and all the gateways to make their component work. This also results in more waste and more plastic and stuff when you have the obstacles.
I havenât had the time to look at the test version yet. Will absolutely do it, maybe through the weekend.
You and the other persons here that are helpful and develop apps and possibilities are very much appreciated for the support and care for the evolving of this community and to help other people understand.
1 Like
YW!
Afaik:
I have to say z-wave is a licensed, brand independent standard protocol (but with different frequencies in other regions) and devices are in general the most expensive, b/c the licence fee.
But Iâm not sure any brand will mix 100%
Wifi and Ble are also standard, brand independent.
But in general, for many things thereâs mostly some standards than the standard because of competition
Where did u get that picture from all your devices?
Is it possible to scan the Zigbee network like Wifi?
I have now tested the Tuya Zigbee Test app.
When I am adding the Nedis smart PIR Zigbee to this app, it looks like this:
This is how we want it to be, but after 5 seconds it looks like this:
These are the properties:
So it seems like itâs a match for 5 seconds, and then itâs not working ;/
https://tools.developer.homey.app/tools/zigbee
There are 3rd party zigbee sniffers available, but theyâre not cheap I think.
Your device is supported, but probably needs a real battery, or itâs too far away from Homey or zigbee routers. Try to restart the app as well.
If that doesnât help, I suggest to report the issue to Johan by posting a message here (click on link to open):
2 Likes
I have posted images and wrote to Johan in the right conversation.
How is it possible to see all the devices that is supported by this app?
My brandâs name is Nedis and have a product ID called RH3040.
I found my device in the list above:
- TUYATEC-bd5faf9p / RH3040 (Nedis) (Test version only)
This device should be working, right?
I have still not heard from Johan either on Github or here.
There are other people also asking about the same issues ;/
Keep in mind Johan is a 3rd party developer with a life of his own, so, just wait⌠What you wrote ainât helping.
Also, what about if he just got paid for his work (or you wire him $6000.-):
You got that right, thatâs why Iâm not hijacking the official thread 
I hope several people can wire him some, not one person to wire for all.
1 Like
Thatâs the idea. I heard from a dev one app of his has 2100 installs. What if everyone donates 2 euroâs for an app.
The problem is though, time. No one can quit his/her dayjob or contracts for a decent income.
Yes, that would be a very good deal, indeed
But Athom is not paying any1 for making apps and attracting new users?
I saw it was possible to add Zigbee devices through Homey itself.
Doing this with the sensor in the same room at the Homey makes no difference. So the distance is not a problem.
Also, it recognizes the device as soon as I put it in pairing mode, but it still says it is unsupported.
I was able to interview it aswell, result:
What does this tell me?
"ids": {
"modelId": "RH3040",
"manufacturerName": "TUYATEC-bd5faf9p"
},
"endpoints": {
"endpointDescriptors": [
{
"endpointId": 1,
"applicationProfileId": 260,
"applicationDeviceId": 1026,
"applicationDeviceVersion": 0,
"_reserved1": 0,
"inputClusters": [
0,
1,
3,
1280
],
"outputClusters": []
}
],
"endpoints": {
"1": {
"clusters": {
"basic": {
"attributes": [
{
"acl": [
"readable",
"reportable"
],
"id": 0,
"name": "zclVersion",
"value": 1
},
{
"acl": [
"readable",
"reportable"
],
"id": 1,
"name": "appVersion",
"value": 72
},
{
"acl": [
"readable",
"reportable"
],
"id": 2,
"name": "stackVersion",
"value": 0
},
{
"acl": [
"readable",
"reportable"
],
"id": 3,
"name": "hwVersion",
"value": 1
},
{
"acl": [
"readable",
"reportable"
],
"id": 4,
"name": "manufacturerName",
"value": "TUYATEC-bd5faf9p"
},
{
"acl": [
"readable",
"reportable"
],
"id": 5,
"name": "modelId",
"value": "RH3040"
},
{
"acl": [
"readable",
"reportable"
],
"id": 6,
"name": "dateCode",
"value": "20180512"
},
{
"acl": [
"readable",
"reportable"
],
"id": 7,
"name": "powerSource",
"value": "battery"
},
{
"acl": [
"readable",
"reportable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": [],
"commandsReceived": [
"factoryReset"
]
},
"powerConfiguration": {
"attributes": [
{
"acl": [
"readable",
"reportable"
],
"id": 0
},
{
"acl": [
"readable",
"reportable"
],
"id": 32,
"name": "batteryVoltage",
"value": 30
},
{
"acl": [
"readable",
"reportable"
],
"id": 33,
"name": "batteryPercentageRemaining",
"value": 200
},
{
"acl": [
"readable",
"reportable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": [],
"commandsReceived": []
},
"identify": {
"attributes": [
{
"acl": [
"readable",
"writable",
"reportable"
],
"id": 0
},
{
"acl": [
"readable",
"reportable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": [
0
],
"commandsReceived": [
0,
1
]
},
"iasZone": {
"attributes": [
{
"acl": [
"readable",
"reportable"
],
"id": 0,
"name": "zoneState",
"value": "notEnrolled"
},
{
"acl": [
"readable",
"reportable"
],
"id": 1,
"name": "zoneType",
"value": "motionSensor"
},
{
"acl": [
"readable",
"writable",
"reportable"
],
"id": 2,
"name": "zoneStatus"
},
{
"acl": [
"readable",
"writable",
"reportable"
],
"id": 16,
"name": "iasCIEAddress",
"value": "00:00:00:00:00:00:00:00"
},
{
"acl": [
"readable",
"reportable"
],
"id": 17,
"name": "zoneId",
"value": 255
},
{
"acl": [
"readable",
"reportable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": [
"zoneStatusChangeNotification",
1
],
"commandsReceived": [
"zoneStatusChangeNotification"
]
}
},
"bindings": {}
}
}
}
