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

EP25 Compatibility #358

Open
1 task done
bowtiedave opened this issue Dec 7, 2024 · 0 comments
Open
1 task done

EP25 Compatibility #358

bowtiedave opened this issue Dec 7, 2024 · 0 comments
Labels

Comments

@bowtiedave
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

I have EP25 outlet. It appears that TP-Link now requires login to confirm discoverability of the devices. Had to use the
"TPLink Tapo" plugin to get my new devices to work. Currently no issues EP10 & HS103 using this plugin. Verified not an issue with mulitcast or any other issue on Unifi network. Appears to be an issue with how the homekit aspect of these devices work. Any thoughts?

What, if anything, has recently changed?

None - new ep25 outlets

Version

8.0.3

Node Version

v1.8.5

Homebridge Version

v4.64.0

Which OS/Platform?

Linux

Relevant log output

None - not recognized via plugin

Configuration

{
            "name": "TplinkSmarthome",
            "addCustomCharacteristics": true,
            "deviceTypes": [
                "plug",
                "bulb"
            ],
            "devicesUseDiscoveryPort": false,
            "_bridge": {
                "username": "0E:EB:F9:2E:A5:0B",
                "port": 46923
            },
            "platform": "TplinkSmarthome"
        },
@bowtiedave bowtiedave added the bug label Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant