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
HAP Discovery failed, please review config (Docker, multiple homebridge instance) #81
Comments
Try moving the -I as the first parameter rather than the last.
The review config error is caused by having no devices passed to Alexa.
…Sent from my iPad
On Mar 23, 2018, at 8:36 PM, quacktacular ***@***.***> wrote:
I have multiple homebridge instances setup with the oznu's docker-homebridge image. Each runs on its own port with its own pin.
I only really want to use one with homebridge-alexa (for my webos tv)
Set that container to start up using insecure home (using HOMEBRIDGE_INSECURE=1 for env)
Used the PIN from above container in my homebridge-alexa config.
Also started homebridge-alexa instance in secure mode, and with debug enabled.
config on homebridge-webos instance
"bridge": {
"name": "TVbert Bridge",
"username": "CC:22:3D:E3:00:00",
"port": 51000,
"pin": "031-45-000"
},
config on homebridge-alexa instance
"platforms": [
{
"platform": "Alexa",
"name": "Alexa",
"username": "myusername",
"password": "mypassword",
"pin": "031-45-000"
}
]
Confirmed the homebridge-webos instance is starting up in insecure mode:
Starting homebridge in insecure mode...
-U /homebridge -P /homebridge/node_modules -I
This is all I get: [Alexa] ERROR: HAP Discovery failed, please review config
What am I missing?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Thanks! Because the instance is in a docker container I wasn't able to change the arg order in a persistent way (without editing the image), but by turning off the debug option entirely it started working. Woohoo. Follow up question--if I later on wanted to connect to a second homebridge instance with a different PIN, would that be possible? |
Sorry, all the pins must be identical.
Which Docker container are you running?
… On Mar 24, 2018, at 1:06 PM, quacktacular ***@***.***> wrote:
Thanks! Because the instance is in a docker container I wasn't able to change the arg order in a persistent way (without editing the image), but by turning off the debug option entirely it started working. Woohoo.
Follow up question--if I later on wanted to connect to a second homebridge instance with a different PIN, would that be possible?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have multiple homebridge instances setup with the oznu's docker-homebridge image. Each runs on its own port with its own pin.
I only really want to use one with homebridge-alexa (for my webos tv)
config on homebridge-webos instance
config on homebridge-alexa instance
Confirmed the homebridge-webos instance is starting up in insecure mode:
This is all I get:
[Alexa] ERROR: HAP Discovery failed, please review config
What am I missing?
The text was updated successfully, but these errors were encountered: