[APP][Pro] SONOFF Zigbee

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": {}
      }
    }
  }

Hello Janno,

Yes, the sensor became unresponsive from one day to the next.

I took the follow steps and was not successful until #5 :

  1. Exchange of battery (although 70%)
  2. 10+ attempts at pairing after reset (pin hole)
    Multiple resets of Aqara & Xiaomi ZigBee app
    New start of Homey Pro
  3. 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
  4. Reached out to this great forum :wink:
  5. (finally) Reset of the Homey Pro ZigBee NETWORK. After the reset, I was able to pair the sensor on the first attempt :+1:.

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. :joy:
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 @Matej_Frtus, no solution in place. Can you please interview your device and post the data?

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"
          }
        }
      }
    }
  }

Hello Johan

Thanks for your work. Did you get an update from Athom about having your app approved for Homey Bridge. I am looking forward to using it as I first went for the Homey Bridge to install some sensors in my apartment

Hi @johan_bendz,
Happily using your app. I do see some strange behaviour (dont think its intended)

I have connected a Sonoff ZBMINI.
When the zigbee network is instable the device responds with a timeout (good behaviour)
But when I make the device powerless… It keeps behaving like its operating normally (no time outs, no exclamation mark for being disconnected.)
@Aotw reported the same behaviour in his post

Is this intended behaviour?
(I would expect the exclamation)

If you need additional info, let me know

Hej Johan, any updates on your Bridge support?

Hi @johan_bendz,

Is your app also supporting the Sonoff SBMINI-L? I couldn’t find it so far in the specs.

Thanks in advance,

Ralf

Hi @FKey, thanks for reporting this. I am releasing a test version of the app, please try it and report back if your issue has been solved.

1 Like

Still got temp/humidity sensor getting recognized as a motion sensor.

Did the test, behaviour did unfortunately not change.

  • Installed test version 0.0.21 of the sonoff app
  • waited for a few hours
    *. Tried switching the sonoff, works nicely
  • left the light switched on
  • removed the power line (brown)
  • waited for some time
  • switched off the light in the homey app, icon goes to off
  • switched on the light again, icon goes to on
    No time-outs no errors, just behaves like normal (with zbmini still disconnected…)
  • opened the developer app & performed an interview. This times out
    But even after the interview the app button behaves as if the zbmini is connected

Hi Johan,

Can you please add a (Reverse Contact Alarm Logic) function for the " SONOFF SNZB-04 ZigBee Wireless Door/Window Sensor" as we have at “Aqara Zigbee Door and Windows Sensor” please?


Thanks,

Hi,

I would like to buy the Sonoff Zigbee Motion/Occupancy sensor: SNZB-03

Is this working now?