ZigBee CC2530+CC2592 Long Range Router/Repeater

[dxxxm]

Model 90085 manufactured by cod.m ZigBee Long Range Router/Repeater

Device

• Product name: ZigBee CC2530+CC2592 Long Range Router/Repeater
• Manufacturer: ptvo.info
• Model identifier: ptvo.switch
• Device type :
  • Light

Screenshots

Basic

Node Info panel

Diagnostics

[Mimiix]

I think that other than giving it a name it already works :)

[dxxxm]

Exactly what I thought, supported since Rudolph v2.9.0 Unfortunately didn't manage to make it known (searching for light). Doesn't show up. Neither in pwabeta nor on the RestAPI.

[Mimiix]

No thats because it's not supported yet :) Devices need to be whitelisted in order to be exposed in the API.

For a Repeater that probably only adds the ability to change the name.

[Smanar]

For a Repeater that probably only adds the ability to change the name.

Yep, I think too.

So do you want to add it in whitelist with other repeater ? it s just a 2 lines modification to do.

[dxxxm]

Yes , please or can I do it myself ?

[Smanar]

Hu, after taking a look, it will be more random than I thought. This device is not reconised a zigbee extender and use standard value (Xiaomi manufacture for exemple)

So we can have problem to reconize it

Will be easier in 1/2 week when we will start to use the ddf files.

[github-actions[bot]]

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.

[dxxxm]

bump

[github-actions[bot]]

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[bot]]

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.

[Mimiix]

@Smanar >?

[Smanar]

Ha yes sorry ^^, sorry too much issue to follow. I think will be easy using DDF.

Do you have a recent deconz version that use DDF ?

[dxxxm]

Installed v2.13.1-beta Peeked into the DDF of a CC2530. Not sure if it can be used as a template for my purpose. I suppose the "OnOff light" is closest ? Guess composing of a new DDF happens in status 'draft' ? Once finalized gets elevated to one the more prestigious ones ? What qualifies a DDF for one of the states Bronze, Silver, Gold ?

[Smanar]

The “Panels → Control → Normal mode” needs to be enabled. The Status of the DDF needs to be set to Bronze, Silver or Gold. The Default: Draft is acting as disabled

Peeked into the DDF of a CC2530. Not sure if it can be used as a template for my purpose. I suppose the "OnOff light" is closest

I think its better to start from scratch, if you are lucky deconz with auto fill some field when you select "edit DDF", else you can darg and drop model ID and Manufacture name for exemple. And yes you are right, it s missing the Range expender, try to add this file in /usr/share/deCONZ/devices/generic/subdevices

File "Range_extender.json"

{
    "schema": "subdevice1.schema.json",
    "type": "$TYPE_RANGE_EXTENDER",
    "name": "Range extender",
    "restapi": "/lights",
    "order": 11,
    "uuid": ["$address.ext", "0x01"],
    "items": [
        "state/reachable"
    ]
}

You will have it in deconz after a restart.

[dxxxm]

Cool. It worked. Thanks. Appreciate assistance.

{
    "etag": "4ba0816b44a92f24e1e1deb079357b06",
    "hascolor": false,
    "lastannounced": null,
    "lastseen": "2021-10-30T17:37Z",
    "manufacturername": "ptvo.info",
    "modelid": "ptvo.switch",
    "name": "Range extender 5",
    "state":
    {
        "reachable": true
    },
    "swversion": "2020-06-12",
    "type": "Range extender",
    "uniqueid": "00:xxxxxxxxxxxxxxxxxxxxxx"
}

[Smanar]

BTW, it s already working ?

Was easy finally ^^, will add the json for Range extender.

[dxxxm]

Yes, it does work. Completing the DDF structure turned out to be easy. Attributes were pre-filled, as you expected. First tried drag and drop, couldn't see any change, eventually figured out its a feature not bug because values were prefilled already.

Thanks again.