-
Notifications
You must be signed in to change notification settings - Fork 68
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
alexa #566
Comments
Likely the internal reference between Amazon Alexa and Homebridge / your light is out of sync. Please ask Alexa to discovery devices again. If this does not resolve the issue, please share a log from homebridge when recreating the issue. |
Can you ask Alexa to turn the light on, and capture the homebridge log with the failure. It should be logged |
Take a look in the Alexa app, you may see two copies of your devices. You can select a device, and if it indicates not responding, it is the older device, and can be deleted. The other device should show as responding |
both don’t work like both of them say server unresponsive
On Fri, Mar 10, 2023 at 7:27 AM Northern Man ***@***.***> wrote:
HB Instance not found is triggered when Alexa tries to control a device
within homebridge, and the particular homebridge instance with the device
is not longer found. This is typically caused when your homebridge
environment is changed, and Amazon Alexa has an old device and the new
device. Or it could be cause by an instance of homebridge not being stable,
and not available when Alexa attempts to contact it.
Take a look in the Alexa app, you may see two copies of your devices. You
can select a device, and if it indicates not responding, it is the older
device, and can be deleted. The other device should show as responding
—
Reply to this email directly, view it on GitHub
<#566 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A52S2MHR34QTBYK5Q47FFBTW3NB67ANCNFSM6AAAAAAVWR5EGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Cameron
|
For the ones that indicate unresponsive, pls delete them from the Alexa app ( if these are truly valid devices, asking Alexa to discover devices will recreate them )
… On Mar 10, 2023, at 10:41 AM, cammansour ***@***.***> wrote:
both don’t work like both of them say server unresponsive
On Fri, Mar 10, 2023 at 7:27 AM Northern Man ***@***.***>
wrote:
> HB Instance not found is triggered when Alexa tries to control a device
> within homebridge, and the particular homebridge instance with the device
> is not longer found. This is typically caused when your homebridge
> environment is changed, and Amazon Alexa has an old device and the new
> device. Or it could be cause by an instance of homebridge not being stable,
> and not available when Alexa attempts to contact it.
>
> Take a look in the Alexa app, you may see two copies of your devices. You
> can select a device, and if it indicates not responding, it is the older
> device, and can be deleted. The other device should show as responding
>
> —
> Reply to this email directly, view it on GitHub
> <#566 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A52S2MHR34QTBYK5Q47FFBTW3NB67ANCNFSM6AAAAAAVWR5EGE>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
--
Cameron
—
Reply to this email directly, view it on GitHub <#566 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEXEFGG67ICV3PMDGYIQPNTW3NDTHANCNFSM6AAAAAAVWR5EGE>.
You are receiving this because you commented.
|
So sorry for not replying I was on a road trip. I did the deleting and rediscovering and it still didn’t work |
Same error message in the logs ? What is the name of the device with the issue |
Am seeing this in the error log |
what does that mean?
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Northern Man ***@***.***>
Sent: Wednesday, March 15, 2023 7:38:51 AM
To: NorthernMan54/homebridge-alexa ***@***.***>
Cc: cammansour ***@***.***>; Author ***@***.***>
Subject: Re: [NorthernMan54/homebridge-alexa] alexa (Issue #566)
Am seeing this in the error log Homebridge auth failed, invalid PIN is the pin in your homebridge-alexa config the same as your homebridge pin
—
Reply to this email directly, view it on GitHub<#566 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A52S2MEGCQKVTURP4QW467DW4HH7XANCNFSM6AAAAAAVWR5EGE>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Does homebridge keep a history or record of activity with the Alexa app? I know the Alexa app keeps a record of activity, but I am curious if Homebridge does. |
alexa not sending command to lights and saying it is not responding when it works fine in the homekit app
The text was updated successfully, but these errors were encountered: