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

Aeotec Range Extender Zi #6785

Closed
stijnmeijer opened this issue Mar 6, 2023 · 16 comments · Fixed by #6793
Closed

Aeotec Range Extender Zi #6785

stijnmeijer opened this issue Mar 6, 2023 · 16 comments · Fixed by #6793

Comments

@stijnmeijer
Copy link

stijnmeijer commented Mar 6, 2023

Device

  • Product name: Range Extender Zi
  • Manufacturer: AL001
  • Model identifier: WG001-Z01
  • Device type :
    • Other: Range extender

Screenshots

afbeelding

Basic

afbeelding

Identify

afbeelding
Note: after pressing Read and/or Exec, the value remains 0

OTAU

afbeelding
afbeelding

Other info

All other clusters do not seem to contain any attributes, or are duplicate to the above.

DDF

The pre-generated DDF in Phoscon GUI looks like this.
{ "schema": "devcap1.schema.json", "manufacturername": "AL001", "modelid": "WG001-Z01", "product": "WG001-Z01", "sleeper": false, "status": "Draft", "subdevices": [] }
I'm not sure if this is correct, as it seems too straightforward.

@Smanar
Copy link
Collaborator

Smanar commented Mar 6, 2023

I'm not sure if this is correct, as it seems too straightforward.

Lol, yes. And it will be the first DDF for range extender, try this one

{
  "schema": "devcap1.schema.json",
  "manufacturername": "AL001",
  "modelid": "WG001-Z01",
  "product": "Aeotec Range Extender Zi",
  "sleeper": false,
  "status": "Gold",
  "subdevices": [
    {
      "type": "$TYPE_RANGE_EXTENDER",
      "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/reachable"
        }
      ]
    }
  ]
}

IDK if your device have special feature that can be used in the DDF ?

@Idaho947
Copy link
Contributor

Idaho947 commented Mar 9, 2023

Works for me

@Smanar
Copy link
Collaborator

Smanar commented Mar 9, 2023

You have this device too ? Lol, you are devices tester or you are a "compulsive buyer" ^^ ?

@Idaho947
Copy link
Contributor

Idaho947 commented Mar 9, 2023

Yes I bought it. I am a device tester in real life.

@Smanar
Copy link
Collaborator

Smanar commented Mar 10, 2023

And this device haven't special feature ? (So much endpoints and clusters for nothing)

@Idaho947
Copy link
Contributor

I don't know. For me it's just an extender

@wvuyk
Copy link

wvuyk commented Mar 11, 2023

why to expose an extender to the api if there is no added value then extend signals.....?

@Idaho947
Copy link
Contributor

For exemple to check if it's always on the network.

@wvuyk
Copy link

wvuyk commented Mar 12, 2023

You will not see any updates in the API to tell the device is still alive? You need to check on the deCONZ map. That is the place to check is a device is still on the network.
Adding an extender to the api does not add any value, there are no controls and there are no updates. Instead apps using the api need to provision ways to ignore these devices.

@Idaho947
Copy link
Contributor

Ok but if your using a third party app for your domotic use and this third party use the api ?

@wvuyk
Copy link

wvuyk commented Mar 12, 2023

Yes, I am maintaining my own app here

@wvuyk
Copy link

wvuyk commented Mar 12, 2023

Sorry, my last answer was unclear. I am a writer of a thrid party app. That is also the reason for my earlier answer. Why would a third party app show a device that has no controls and no updates that are of interest for the user? For my app, I hide these devices for the user as the app can not show any assured confirmation it is alive?

@Smanar
Copy link
Collaborator

Smanar commented Mar 12, 2023

Using state/reachable don't work ?
Without the DDF, user on headless setup can't know if the inclusion have worked or not, as they have a look only on the API.

@Idaho947
Copy link
Contributor

Yes it works. But in my memories, my app use the api to import and use it.

@github-actions
Copy link

github-actions bot commented Apr 3, 2023

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.

@Schmandre
Copy link

Schmandre commented Jan 9, 2024

Hello,

I just tried to pair the device but can’t see anything in Web UI. Any information how to get that to work?

I can see the device through VNC, but not in Web UI. Unsure if anything works as should.
image

Using Phoscon in docker.

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.

5 participants