NorthernMan54 / homebridge-alexa

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

alexa #566

Open cammansour opened 1 year ago

cammansour commented 1 year ago

alexa not sending command to lights and saying it is not responding when it works fine in the homekit app

NorthernMan54 commented 1 year ago

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.

cammansour commented 1 year ago

i already tried that it didn’t work, it discovers that but then doesn’t actually turn them on E287C843-929B-4C8F-9122-E9A4DB5524AB

NorthernMan54 commented 1 year ago

Can you ask Alexa to turn the light on, and capture the homebridge log with the failure. It should be logged

cammansour commented 1 year ago

![Uploading 79C755CE-7CB5-431F-A620-3AE6C56AF293.png…]()

cammansour commented 1 year ago

39AF154A-18D5-46CA-A836-58FFF1F6FD3E

NorthernMan54 commented 1 year ago

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

cammansour commented 1 year ago

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 https://github.com/NorthernMan54/homebridge-alexa/issues/566#issuecomment-1463966095, or unsubscribe https://github.com/notifications/unsubscribe-auth/A52S2MHR34QTBYK5Q47FFBTW3NB67ANCNFSM6AAAAAAVWR5EGE . You are receiving this because you authored the thread.Message ID: @.***>

-- Cameron

NorthernMan54 commented 1 year ago

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 https://github.com/NorthernMan54/homebridge-alexa/issues/566#issuecomment-1463966095, 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 https://github.com/NorthernMan54/homebridge-alexa/issues/566#issuecomment-1463985761, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEXEFGG67ICV3PMDGYIQPNTW3NDTHANCNFSM6AAAAAAVWR5EGE. You are receiving this because you commented.

cammansour commented 1 year ago

So sorry for not replying I was on a road trip. I did the deleting and rediscovering and it still didn’t work

NorthernMan54 commented 1 year ago

Same error message in the logs ? What is the name of the device with the issue

cammansour commented 1 year ago

The name is Cameron’s bedroom light that I am testing it with this time but all devices don’t work 104EF637-C515-48FD-9261-94A85D40458B

NorthernMan54 commented 1 year ago

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

cammansour commented 1 year ago

what does that mean?

Get Outlook for iOShttps://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 GitHubhttps://github.com/NorthernMan54/homebridge-alexa/issues/566#issuecomment-1470128135, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A52S2MEGCQKVTURP4QW467DW4HH7XANCNFSM6AAAAAAVWR5EGE. You are receiving this because you authored the thread.Message ID: @.***>

NorthernMan54 commented 1 year ago

image

Kilo132 commented 1 year ago

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.