Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

HS100 not automatically detected

See original GitHub issue

Expected Behavior

After installing the TPLink smarthome plugin and using the given config, the HS100 should show up in the Home app.

Current Behavior

HomeBridge launches fine, but the HS100 is not detected.

Steps to Reproduce (for bugs)

Install HomeBridge and the TPLink plugin.
Use the config.json file that is supplied with TPLink plugin.
Launch HomeBridge.

Versions

Node: 8.9.4
Homebridge: 0.4.38
OS: Windows 8.1 (64 bit)

Configuration


{
    "bridge": {
        "name": "Homebridge",
        "username": "CC:22:3D:E3:CE:30",
        "port": 51826,
        "pin": "031-45-154"
    },

    "description": "This is an example configuration file.",

    "platforms": [{
        "platform": "TplinkSmarthome",
        "name": "TplinkSmarthome"
    }],

    "accessories": []
}

Homebridge Log / Command Output


[2018-4-9 18:34:19] Loaded plugin: homebridge-tplink-smarthome
[2018-4-9 18:34:19] Registering platform 'homebridge-tplink-smarthome.TplinkSmar
thome'
[2018-4-9 18:34:19] ---
[2018-4-9 18:34:19] Loaded config.json with 0 accessories and 1 platforms.
[2018-4-9 18:34:19] ---
[2018-4-9 18:34:19] Loading 1 platforms...
[2018-4-9 18:34:19] [TplinkSmarthome] Initializing TplinkSmarthome platform...
[2018-4-9 18:34:19] [TplinkSmarthome] homebridge-tplink-smarthome v3.11.0, node
v8.9.4, homebridge v0.4.38
[2018-4-9 18:34:19] [TplinkSmarthome] config.json: {"platform":"TplinkSmarthome"
,"name":"TplinkSmarthome"}
[2018-4-9 18:34:19] [TplinkSmarthome] config: {"platform":"TplinkSmarthome","nam
e":"TplinkSmarthome","addCustomCharacteristics":true,"deviceTypes":[],"switchMod
els":["HS200"],"discoveryOptions":{"discoveryInterval":10000,"deviceTypes":[],"d
eviceOptions":{"timeout":5000},"macAddresses":[]}}
[2018-4-9 18:34:19] Loading 0 accessories...

[2018-4-9 18:34:20] [TplinkSmarthome] didFinishLaunching
[2018-4-9 18:34:20] [TplinkSmarthome.API] client.startDiscovery({"discoveryInter
val":10000,"deviceTypes":[],"deviceOptions":{"timeout":5000},"macAddresses":[]})

[2018-4-9 18:34:20] Homebridge is running on port 51826.
[2018-4-9 18:34:20] [TplinkSmarthome.API] client.socket: UDP IPv4 listening on 0
.0.0.0:55412
[2018-4-9 18:34:20] [TplinkSmarthome.API] client.sendDiscovery(255.255.255.255,
undefined, 3)
[2018-4-9 18:34:30] [TplinkSmarthome.API] client.sendDiscovery(255.255.255.255,
undefined, 3)

Issue Analytics

State:
Created 5 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

2reactions

plasticrakecommented, Aug 17, 2018

@Eloquite @angelothegr8 This plugin sends a UDP broadcast packet on the local subnet and listens for responses to come back from the devices. Some home routers will mess with this broadcast packets and cause it to not work. Some people have reported just restarting their router fixes it, changing certain router settings, or getting a new router. If you can’t get the auto discovery to work you can always manually enter the IP addresses in the configuration and make sure the devices have a static IP using DHCP reservations.

0reactions

plasticrakecommented, Jan 11, 2019

Closing due to inactivity. Note that you may try to tweak the broadcast address configuration setting to match your subnet.