I have two Temperature and Humidity Sensor that acts as a motion sensor. I bought a new one and that one gets recognized as a Temperature and Humidity Sensor. I don’t get the battery info though…
Hi, can you please interview the unit and post the data here?
"id"s: {
"modelId": "TH01",
"manufacturerName": "eWeLink"
},
"endpoints": {
"endpointDescriptors": [
{
"endpointId": 1,
"applicationProfileId": 260,
"applicationDeviceId": 770,
"applicationDeviceVersion": 0,
"_reserved1": 0,
"inputClusters": [
0,
3,
1026,
1029,
1
],
"outputClusters": [
3
]
}
],
"endpoints": {
"1": {
"clusters": {
"basic": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"identify": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"temperatureMeasurement": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"relativeHumidity": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"powerConfiguration": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
}
},
"bindings": {
"identify": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
}
}
}
}
}
This is quite an old post but I’m looking for such an occupancy sensor. One that triggers when a person is detected and goes off when no one is detected anymore.
Is there a cooldown period before triggering again? Do you have to keep moving to keep it triggered?
Hi, I have installed 5 sznb-04 sensors at home and sometimes one of the sensors (not always the same, but always only one) stops reacting to contact, remaining stuck on a status. It often happens with the last sensor associated with Homey, I don’t know if this is a coincidence or not. The zigbee signal is well distributed around the house with routers, so I don’t think it’s a coverage problem. I tried to uninstall the app, I reset the zigbee network but nothing has changed, after a few days, the last of the associated sensors stops working. Does the same thing happen to you?
Unfortunately the problem persists. I don’t think it’s a sensors’ issue, i tried to replace them with new ones but after a while the same problem occurs. At first I thought it was just an issue of the last sensors added to the network but I now realized that even sensors that were initially working are presenting the same problem. If I disconnect them and connect them back they iniitally work just to freeze again after a while. @johan_bendz , any word of advice for me?
Any news on supporting Bridge?
2 Likes
I have been using the Motion Sensor - SNZB-03 since 4 months without problem. About a week ago they both stopped working and I can no longer pair them with Homey Pro. Is this due to a software update ? Will there be a resolution or do I have to write them off and look for an alternative?
Hi @Jeffrey_Ellenburg, nothing should have changed that would cause this. Can you please try disabling the app and pair them as generic Zigbee? If this does not work the issue is with Homey and not the app. If you are able to pair the units as generic devices please interview them, delete them, enable the app and then try adding them correctly again.
Hi @Fredrik_Edenlind, sorry for the late answer. Athom have some restrictions for who can release an app to the cloud/bridge and when, I am looking to have all my apps approved but it will take some time.
1 Like
Ok , thx Johan
Did Your sensor become completely unresponsive, or only not able to register? I am asking since I also had a sensor working for some weeks, but now it stopped working and even pressing a pin-hole reset/registration, will not work anymore (even the red LED will not start flashing). Though likely I am having some other issue then…
Hi. I bought a Sonos Zigbee Smart plug (S26R2ZB) and added it as an eWeLink OnOff device. It is recognized as an Unknown Zigbee Device but seems to have basic functionality (can at least switch on and off)
This is what I get back from interviewing the device. I hope you can use it to add this device to the app:
"ids": {
"modelId": "S26R2ZB",
"manufacturerName": "SONOFF"
},
"endpoints": {
"endpointDescriptors": [
{
"endpointId": 13,
"applicationProfileId": 49246,
"applicationDeviceId": 57694,
"applicationDeviceVersion": 0,
"_reserved1": 2,
"inputClusters": [
4096
],
"outputClusters": [
4096
]
},
{
"endpointId": 1,
"applicationProfileId": 260,
"applicationDeviceId": 256,
"applicationDeviceVersion": 0,
"_reserved1": 1,
"inputClusters": [
0,
3,
4,
5,
6,
64599
],
"outputClusters": [
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",
"value": 3
},
{
"acl": [
"readable"
],
"id": 3,
"name": "hwVersion",
"value": 1
},
{
"acl": [
"readable"
],
"id": 4,
"name": "manufacturerName",
"value": "SONOFF"
},
{
"acl": [
"readable"
],
"id": 5,
"name": "modelId",
"value": "S26R2ZB"
},
{
"acl": [
"readable"
],
"id": 6,
"name": "dateCode",
"value": "20210511"
},
{
"acl": [
"readable"
],
"id": 7,
"name": "powerSource",
"value": "mains"
},
{
"acl": [
"readable",
"writable"
],
"id": 17,
"name": "physicalEnv",
"value": "Unspecified"
},
{
"acl": [
"readable"
],
"id": 16384,
"name": "swBuildId",
"value": "2.0.0"
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 2
}
],
"commandsGenerated": [],
"commandsReceived": [
"factoryReset"
]
},
"identify": {
"attributes": [
{
"acl": [
"readable",
"writable"
],
"id": 0
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": [],
"commandsReceived": []
},
"groups": {
"attributes": [
{
"acl": [
"readable"
],
"id": 0,
"name": "nameSupport",
"value": {
"type": "Buffer",
"data": [
0
]
}
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": [],
"commandsReceived": []
},
"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": [],
"commandsReceived": []
},
"onOff": {
"attributes": [
{
"acl": [
"readable",
"reportable"
],
"id": 0,
"name": "onOff",
"value": false,
"reportingConfiguration": {
"direction": "reported",
"attributeDataType": 16,
"minInterval": 0,
"maxInterval": 10,
"status": "SUCCESS"
}
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": [],
"commandsReceived": [
"setOff",
"setOn",
"toggle",
"offWithEffect"
]
}
},
"bindings": {
"ota": {
"attributes": [],
"commandsGenerated": [],
"commandsReceived": []
}
}
},
"13": {
"clusters": {
"touchlink": {}
},
"bindings": {
"touchlink": {}
}
},
"242": {
"clusters": {},
"bindings": {}
}
}
}
1 Like
Hello Janno,
Yes, the sensor became unresponsive from one day to the next.
I took the follow steps and was not successful until #5 :
- Exchange of battery (although 70%)
- 10+ attempts at pairing after reset (pin hole)
Multiple resets of Aqara & Xiaomi ZigBee app
New start of Homey Pro - 10+ attempts at pairing of a new and identical sensor.
At this point I had isolated it to a Homey issue and not a sensor issue.
Multiple resets of Aqara & Xiaomi ZigBee app.
New start of Homey Pro - Reached out to this great forum
- (finally) Reset of the Homey Pro ZigBee NETWORK. After the reset, I was able to pair the sensor on the first attempt
.
This finally did the trick, but I had to go back and reconnect almost all of the devices I had added.
Even worse, I had to go back am modify all of the flows for the „new“ devices. 
I presume that if one uses the Cloud for backup purposes, that this would not have been necessary.
Good luck,
Jeffrey
OK. Thanks. It seems that I just have a hw issue with my sensor.
Other than that, there are many other threads about the cases with Zigbee sensors, also some are related to wifi/zigbee network design, as they are using the same frequency band (so it could be that in some more dense living area some neighbour installes some new wifi AP (or changes the channel), and it can start interferring already.
Also, might be good idea to start from Athom’s own articles, e.g.
where it is also claimed, that there can be up to 15 directly connected devices, however, some people claim to have larger networks (but is some scenarios their exact network designs are not described).
Also, might be good idea to check about changing the Zigbee RF channel before making a network reset…
Some threads:
hope it give some thoughts for You.
Hi, I have the same problem as Ray_Godjord. Did you find a solution?
If I want my temperature/humidity sensor to report temperature every minute, what should the settings look like. It’s kind of random atm.
Hi @Ray_Godjord, under settings you should have a few different values to test out. Do remember that if you set the intervals to low the unit will drain it’s batteries.
The unit will use the values as “guidelines” for reporting, it’s not used by the device as a fixed time to report. Nothing I can do about it as this is how it works.
Hi @johan_bendz thank for reply. I’m sending an interview. It is SNZB-02. In eWeLink application works well.
"ids": {
"modelId": "66666",
"manufacturerName": "eWeLink"
},
"endpoints": {
"endpointDescriptors": [
{
"endpointId": 1,
"applicationProfileId": 260,
"applicationDeviceId": 770,
"applicationDeviceVersion": 0,
"_reserved1": 0,
"inputClusters": [
0,
3,
1026,
1029,
1
],
"outputClusters": [
3
]
}
],
"endpoints": {
"1": {
"clusters": {
"basic": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"identify": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"temperatureMeasurement": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"relativeHumidity": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"powerConfiguration": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
}
},
"bindings": {
"identify": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
}
}
}
}
}
