Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sonoff ZBMINI-L #5763

Closed
SarcasticShrimp opened this issue Feb 6, 2022 · 24 comments · Fixed by #6095
Closed

Sonoff ZBMINI-L #5763

SarcasticShrimp opened this issue Feb 6, 2022 · 24 comments · Fixed by #6095

Comments

@SarcasticShrimp
Copy link

Device

  • Product name: SONOFF ZBMINI-L Zigbee 3.0 Smart Switch
  • Manufacturer: SONOOF
  • Model identifier: ZBMINI-L
  • Device type : Please remove all unrelated device types.
    • Light
    • Switch

Screenshots

Basic

image
image

Identify

image

Alarms

Device Temperature

Groups

image

Scenes

image

On/Off

image
image

Level Control

Color Control

Simple Metering

Diagnostics

Other clusters that are not mentioned above

image

image

@github-actions
Copy link
Contributor

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

@pyrech
Copy link

pyrech commented Feb 28, 2022

I guess this issue should be kept open until support is added even if we have to wait a bit until #5733 is done?

In the meantime I created https://forum.phoscon.de/t/sonoff-zbmini-l/1686 as requested in #5113

@Mimiix
Copy link
Collaborator

Mimiix commented Feb 28, 2022

Yes but you need to keep bumping this open once in a while.

@Mimiix Mimiix reopened this Feb 28, 2022
@github-actions github-actions bot removed the stale label Mar 1, 2022
@github-actions
Copy link
Contributor

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Mar 22, 2022
@github-actions
Copy link
Contributor

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.

@pyrech
Copy link

pyrech commented Mar 30, 2022

Doh, not the OP here but still need this feature request to be kept open 😅

@Mimiix
Copy link
Collaborator

Mimiix commented Mar 30, 2022

Sure!
@Smanar Can we make a DDF?

@Mimiix Mimiix reopened this Mar 30, 2022
@Smanar
Copy link
Collaborator

Smanar commented Mar 30, 2022

Ha I think yes, this device is probably not working because it's not router but it s a wired device ?
There is 2 unknow clusters but for me it can work without them.
Just drag and drop a "on off light", configure the "basic cluster indentification", let all by defaut.

If I m right you will be able to send request to the device, you will just miss the return state, for that need to configure the binding, but will be the next part.

@github-actions github-actions bot removed the stale label Mar 31, 2022
@github-actions
Copy link
Contributor

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Apr 21, 2022
@sir-Unknown
Copy link

Not the OP. Got the device working by adjusting the DDF. However would like to have the possibility to receive the toggle of the power on/off from the wire. I don't have the skills to add that.

@github-actions github-actions bot removed the stale label Apr 24, 2022
@Smanar
Copy link
Collaborator

Smanar commented Apr 24, 2022

However would like to have the possibility to receive the toggle of the power on/off from the wire. I don't have the skills to add that.

You mean the return when using the device manualy ? It's the binding part https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/DDF-cheat-sheet#bindings-panel
Else if you can copy/paste the DDF I can complete it.

@github-actions
Copy link
Contributor

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label May 16, 2022
@github-actions
Copy link
Contributor

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.

@moecre
Copy link

moecre commented May 25, 2022

Not the OP. Got the device working by adjusting the DDF. However would like to have the possibility to receive the toggle of the power on/off from the wire. I don't have the skills to add that.

I'm confused right now. Does this mean the device is compatible/partly compatible? These devices are the missing link for my smart home and I'd like to know if I can start buying them. Thanks.

@Smanar
Copy link
Collaborator

Smanar commented May 25, 2022

You have the device ?
Can try to make a DDF, I can help but I need at least a skeleton to start.

@felixnurse
Copy link

I have both devices (zbmini and zbmini-l) if that helps.
Let me know what I need to share from deconz and illlpaste here for you.thanks

@Smanar
Copy link
Collaborator

Smanar commented May 25, 2022

Depend of device but for exemple for the ZBMINI-L, you can start a DDF

  • fill the basic cluster indentification
  • drag and drop a "on off light"
  • save the file, look at the name and path on the editor (to be able to edit it later)
  • share the contain

Some part can be auto filled
The device can work direclty if you take "hot relaod" in the editor menu. You will just miss the binding, but you can try to set them too.

https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/DDF-cheat-sheet

@ads1230
Copy link

ads1230 commented May 29, 2022

DDF Works with simply the following. On/Off updates accordingly.

{
  "schema": "devcap1.schema.json",
  "manufacturername": "SONOFF",
  "modelid": "ZBMINI-L",
  "product": "ZBMINI-L",
  "sleeper": false,
  "status": "Gold",
  "path": "/devices/zbmini-l.json",
  "subdevices": [
    {
      "type": "$TYPE_ON_OFF_LIGHT",
      "restapi": "/lights",
      "uuid": [
        "$address.ext",
        "0x01"
      ],
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "state/on",
          "description": "True when device is on; false when off.",
          "refresh.interval": 5
        },
        {
          "name": "state/reachable"
        }
      ]
    }
  ]
}

@Smanar
Copy link
Collaborator

Smanar commented May 29, 2022

You miss the binding/reporting but not sure you need it ?

Without it the device don't make state report, not sure it usefull for this kind of device but it prevent having different state on the api and on the reality.

{
  "schema": "devcap1.schema.json",
  "manufacturername": "SONOFF",
  "modelid": "ZBMINI-L",
  "product": "ZBMINI-L",
  "sleeper": false,
  "status": "Gold",
  "subdevices": [
    {
      "type": "$TYPE_ON_OFF_LIGHT",
      "restapi": "/lights",
      "uuid": [
        "$address.ext",
        "0x01"
      ],
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "state/on",
          "description": "True when device is on; false when off.",
          "refresh.interval": 5
        },
        {
          "name": "state/reachable"
        }
      ]
    }
  ],
  "bindings": [
    {
      "bind": "unicast",
      "src.ep": 1,
      "cl": "0x0006",
      "report": [
        {
          "at": "0x0000",
          "dt": "0x10",
          "min": 5,
          "max": 1800
        }
      ]
    }
  ]
}

Have added the bind/report for the on/off cluster.

If it still working can make a PR to add it ?

1 similar comment
@Smanar
Copy link
Collaborator

Smanar commented May 29, 2022

You miss the binding/reporting but not sure you need it ?

Without it the device don't make state report, not sure it usefull for this kind of device but it prevent having different state on the api and on the reality.

{
  "schema": "devcap1.schema.json",
  "manufacturername": "SONOFF",
  "modelid": "ZBMINI-L",
  "product": "ZBMINI-L",
  "sleeper": false,
  "status": "Gold",
  "subdevices": [
    {
      "type": "$TYPE_ON_OFF_LIGHT",
      "restapi": "/lights",
      "uuid": [
        "$address.ext",
        "0x01"
      ],
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "state/on",
          "description": "True when device is on; false when off.",
          "refresh.interval": 5
        },
        {
          "name": "state/reachable"
        }
      ]
    }
  ],
  "bindings": [
    {
      "bind": "unicast",
      "src.ep": 1,
      "cl": "0x0006",
      "report": [
        {
          "at": "0x0000",
          "dt": "0x10",
          "min": 5,
          "max": 1800
        }
      ]
    }
  ]
}

Have added the bind/report for the on/off cluster.

If it still working can make a PR to add it ?

@ads1230
Copy link

ads1230 commented May 29, 2022

You miss the binding/reporting but not sure you need it ?

Without it the device don't make state report, not sure it usefull for this kind of device but it prevent having different state on the api and on the reality.

{
  "schema": "devcap1.schema.json",
  "manufacturername": "SONOFF",
  "modelid": "ZBMINI-L",
  "product": "ZBMINI-L",
  "sleeper": false,
  "status": "Gold",
  "subdevices": [
    {
      "type": "$TYPE_ON_OFF_LIGHT",
      "restapi": "/lights",
      "uuid": [
        "$address.ext",
        "0x01"
      ],
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "state/on",
          "description": "True when device is on; false when off.",
          "refresh.interval": 5
        },
        {
          "name": "state/reachable"
        }
      ]
    }
  ],
  "bindings": [
    {
      "bind": "unicast",
      "src.ep": 1,
      "cl": "0x0006",
      "report": [
        {
          "at": "0x0000",
          "dt": "0x10",
          "min": 5,
          "max": 1800
        }
      ]
    }
  ]
}

Have added the bind/report for the on/off cluster.

If it still working can make a PR to add it ?

Working with your edits. Set up 3 devices today all working fine even after reboot.

@Smanar
Copy link
Collaborator

Smanar commented May 30, 2022

Nice, do you want to make a PR or wana I make it ? (to add it officialy)

@ads1230
Copy link

ads1230 commented May 30, 2022

Nice, do you want to make a PR or wana I make it ? (to add it officialy)

Could you do it please. I'm not too savvy on these things.

@Smanar
Copy link
Collaborator

Smanar commented May 30, 2022

Done #6095
Thx Again

@Smanar Smanar linked a pull request May 30, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants