NorthernMan54 / homebridge-alexa

Expose your homebridge controlled devices to Amazon Alexa.
https://www.homebridge.ca
452 stars 69 forks source link

Filter Causes HAP issue #281

Closed meluvalli closed 4 years ago

meluvalli commented 4 years ago

Get the following error if I use filter:

[Alexa] ERROR: HAP Discovery failed, please review config

Trying to run two instances so need it to filter ONLY the one instance.

"filter": "192.168.1.50:42701"

My bridge is running on that local IP and that port.

    "mdns": {
        "interface": "192.168.1.50"
    },
    "bridge": {
        "name": "Homebridge for Homeseer",
        "username": "XX:XX:XX:XX:XX:XX",
        "port": 42701,
        "pin": "123-45-678",
    },

Works fine if I don't have the filter line in Alexa platform.

NorthernMan54 commented 4 years ago

A couple of things trigger this message, and one of them is not discovering any Alexa compatible devices. I’m thinking this is the case.

On Dec 20, 2019, at 4:08 AM, meluvalli notifications@github.com wrote:

Get the following error if I use filter:

[Alexa] ERROR: HAP Discovery failed, please review config Trying to run two instances so need it to filter ONLY the one instance.

"filter": "192.168.1.50:42701" My bridge is running on that local IP and that port.

"mdns": {
    "interface": "192.168.1.50"
},
"bridge": {
    "name": "Homebridge for Homeseer",
    "username": "XX:XX:XX:XX:XX:XX",
    "port": 42701,
    "pin": "123-45-678",
},

Works fine if I don't have the filter line in Alexa platform.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NorthernMan54/homebridge-alexa/issues/281?email_source=notifications&email_token=AEXEFGFNOYZTGVRO7WXYOH3QZSDQLA5CNFSM4J52XZW2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IB5DDRQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEXEFGHPDBXLNLSXE2JQMLTQZSDQLANCNFSM4J52XZWQ.

NorthernMan54 commented 4 years ago

I believe this is resolved?

meluvalli commented 4 years ago

Yes. I no longer have this issue. Thanks!