Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

CFenner
Copy link
Contributor

@CFenner CFenner commented Oct 6, 2025

Proposed change

This makes ZigBee device connection appear on the device page as for BLE and MAC.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New feature (thank you!)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Example configuration

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue or discussion:
  • Link to documentation pull request:

Checklist

  • The code change is tested and works locally.
  • There is no commented out code in this PR.
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

@CFenner
Copy link
Contributor Author

CFenner commented Oct 6, 2025

I'm not familiar with the frontend project, so do not know how to test this, even failed to test this manually. But maybe the change is small enough so we can merge it anyways.

protected _getAddresses() {
return this.device.connections.filter(
(conn) => conn[0] === "mac" || conn[0] === "bluetooth"
(conn) => conn[0] === "mac" || conn[0] === "bluetooth" || conn[0] === "zigbee"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While rendering, we check for the type and only handle bluetooth and mac for now, so nothing will be done with this.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, is zigbee even used as a connection type here?

Copy link
Contributor Author

@CFenner CFenner Oct 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we check for the type and only handle bluetooth and mac for now

No, it's handled in the else case, but I had to have another look as well:

: html`${type === "mac" ? "MAC" : titleCase(type)}:
                      ${value.toUpperCase()}`}

I wanted to use it in my intestration and was wondering why it did not show up. It is used for e.g. ZHA, WEMO and Decons devices, but for ZHA it is also rendered in the additional Zigbee Info part.

Copy link
Member

@bramkragten bramkragten Oct 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So for ZHA we are now showing it twice?

Copy link
Contributor Author

@CFenner CFenner Oct 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would look like this:

Bildschirmfoto 2025-10-08 um 11 10 52 Bildschirmfoto 2025-10-08 um 11 10 37

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we then remove it from the ZHA zigbee info?

Co-authored-by: Bram Kragten <mail@bramkragten.nl>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.