search

NorthernMan54 / homebridge-alexa

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

Window blind showing as “unresponsive” #591

Closed mariomaz87 closed 6 months ago

mariomaz87 commented 6 months ago

Analysis

A window blind configured in Deconz and usable in Homebridge and HomeKit shows as unresponsive in Alexa

Expected Behavior

To be able to open, close and set %

Steps To Reproduce

I have added the device in my “include” list in the plugin configuration. It is discovered in Alexa but it’s always “unresponsive”

Logs

Can’t see anything relevant in HB log

Configuration

{
            "name": "Alexa",
            "username": "xxx",
            "password": "xxx",
            "pin": "xxx",
            "routines": false,
            "blind": false,
            "door": false,
            "debug": false,
            "refresh": 900,
            "keepalive": 10,
            "CloudTransport": "mqtts",
            "deviceListHandling": "allow",
            "deviceList": [
                "Dummytvspentaalexa",
                "Dummytv",
                "DummyluceAmbrogio",
                "DummyEmergenza",
                "DummyPioggiaLenticchia",
                "DummyLuciSera",
                "Finestra Bagno Vasca",
                "Luce Cameretta",
                "Luce Corridoio",
                "Luce Studio"
            ],
            "platform": "Alexa"

Environment

Docker in Rasp4 on Raspberry OS

Process Supervisor

hb-service

Additional Context

Other homebridge devices are working ok in Alexa

NorthernMan54 commented 6 months ago

With debug in the plugin enabled does anything show up in the log? Can you share you login, want to look at the logs for your account.

On Dec 9, 2023, at 3:58 AM, mariomaz87 @.***> wrote:

Analysis

A window blind configured in Deconz and usable in Homebridge and HomeKit shows as unresponsive in Alexa

Expected Behavior

To be able to open, close and set %

Steps To Reproduce

I have added the device in my “include” list in the plugin configuration. It is discovered in Alexa but it’s always “unresponsive”

Logs

Can’t see anything relevant in HB log Configuration

{ "name": "Alexa", "username": "xxx", "password": "xxx", "pin": "xxx", "routines": false, "blind": false, "door": false, "debug": false, "refresh": 900, "keepalive": 10, "CloudTransport": "mqtts", "deviceListHandling": "allow", "deviceList": [ "Dummytvspentaalexa", "Dummytv", "DummyluceAmbrogio", "DummyEmergenza", "DummyPioggiaLenticchia", "DummyLuciSera", "Finestra Bagno Vasca", "Luce Cameretta", "Luce Corridoio", "Luce Studio" ], "platform": "Alexa" Environment

Docker in Rasp4 on Raspberry OS

Process Supervisor

hb-service

Additional Context

Other homebridge devices are working ok in Alexa

— Reply to this email directly, view it on GitHub https://github.com/NorthernMan54/homebridge-alexa/issues/591, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEXEFGEI7Q5HZDQCO6QWVFDYIQR4FAVCNFSM6AAAAABANUZRRWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAZTGNZTG42DMNI. You are receiving this because you are subscribed to this thread.

mariomaz87 commented 6 months ago

With debug in the plugin enabled does anything show up in the log? Can you share you login, want to look at the logs for your account. … On Dec 9, 2023, at 3:58 AM, mariomaz87 @.***> wrote: Analysis A window blind configured in Deconz and usable in Homebridge and HomeKit shows as unresponsive in Alexa Expected Behavior To be able to open, close and set % Steps To Reproduce I have added the device in my “include” list in the plugin configuration. It is discovered in Alexa but it’s always “unresponsive” Logs Can’t see anything relevant in HB log Configuration { "name": "Alexa", "username": "xxx", "password": "xxx", "pin": "xxx", "routines": false, "blind": false, "door": false, "debug": false, "refresh": 900, "keepalive": 10, "CloudTransport": "mqtts", "deviceListHandling": "allow", "deviceList": [ "Dummytvspentaalexa", "Dummytv", "DummyluceAmbrogio", "DummyEmergenza", "DummyPioggiaLenticchia", "DummyLuciSera", "Finestra Bagno Vasca", "Luce Cameretta", "Luce Corridoio", "Luce Studio" ], "platform": "Alexa" Environment Docker in Rasp4 on Raspberry OS Process Supervisor hb-service Additional Context Other homebridge devices are working ok in Alexa — Reply to this email directly, view it on GitHub <#591>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEXEFGEI7Q5HZDQCO6QWVFDYIQR4FAVCNFSM6AAAAABANUZRRWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAZTGNZTG42DMNI. You are receiving this because you are subscribed to this thread.

Thanks. My account is mariomario87. I removed the blind from Alexa and rediscovered the device from Alexa app with the log enabled from the plugin. I attach the log and I think there is something relevant:

interface: 'Alexa.ContactSensor,Alexa.PowerController,Alexa.PowerLevelController', deviceID: '0E:5A:D1:A3:87:F4', spacer: ',', elements: [ { interface: 'Alexa.ContactSensor', aid: 14, iid: 9 }, { interface: 'Alexa.PowerController', aid: 14, iid: 11 }, { interface: 'Alexa.PowerLevelController', aid: 14, iid: 11 } ] } 2023-12-10T14:04:52.988Z hapNodeJSClient Homebridge Status failed 192.168.1.95:39295 Status: 422 ?id=14.9,14.11,14.11 { status: -70410 } 2023-12-10T14:04:52.990Z alexaActions alexaMessage: Response { "event": { "header": { "namespace": "Alexa", "name": "ErrorResponse", "messageId": "5bd2abc6-9f73-453a-b62f-748cd2120b53", "correlationToken": "AAAAAAAAAQBdaQ3pDdfTHgoihJ2efvMBAAIAAAAAAAB4DNBjumL4gUB+y0n5LjyHpzgE7kJQXTWSFb5Izoc97KIw8zTT6RoLNC2U1R6O2y2GqzGuQl/Z/RHvxZNNPZ7Ds3GRvszwxs0XY+2/BFZK0j9vRg0f0Ay5m3+SXt0iYuyInxQCSwjOly5EFE39p/FJCX5mW4IDxYMqwPQXYICugPvhGEgP/cTCUBIsowlfSuQrppa65HzIPygHgfD6pN5mOJ7zKNJPgDWIC5+0i88ZhVr1jB4baGXm2r0UFgyDhESU8KscMN/n5vr8RuD+8gqiSwFzPQD+e0Emvrm9z5kyoIyWVSlBzw50OYwVy6orTeJ3oSbUWJqbhiTAxN+OxJAg7wveW/+NfOgde1Pe7BHqZCvsm29J3m8gSKl5pVL5XvIxIT9xFUarZ7pgh/r09vVSG0fxArRjGwPchpZksLhuBuuPPPAFQ2USdn12UNU+kyvI/eoWVI8NXGTsjvN+X4rcykTPuKZmfBN+02TNTQ2PeyU9VMt1MT4L0gShfhMCzn2VBISLLQGQzosQG3+SLG15wjgCC45ohJTMxT0MxLRRw1QblzuraE8BogiKcCmJA7dPbire5YEgn74n7+rrxBbrkh1Bqv4VBtfUQdSCr6wRkZzS/fDEErzA7PunylmUe1t5zMgMwznrfDAXviV+tjDyEkSSt97Os8svsVxOB2lNIg==", "payloadVersion": "3" }, "endpoint": { "endpointId": "MEU6NUE6RDE6QTM6ODc6RjQtaG9tZWJyaWRnZS1MZWdyYW5kLUZpbmVzdHJhIEJhZ25vIFZhc2NhLTAwMDAwMDhDLTAwMDAtMTAwMC04MDAwLTAwMjZCQjc2NTI5MQ==" }, "payload": { "type": "ENDPOINT_UNREACHABLE", "message": "Homebridge Status failed" } } }

homebridge.log.txt

NorthernMan54 commented 6 months ago

I'm just working thru a fix for the "ENDPOINT_UNREACHABLE" message, and should have something tomorrow.

But you should be able to ask Alexa turn on Finestra Bagno Vasca and the blinds should open or Alexa set Finestra Bagno Vasca to 50 and the blinds should open half way ( if they support that )

mariomaz87 commented 6 months ago

I'm just working thru a fix for the "ENDPOINT_UNREACHABLE" message, and should have something tomorrow.

But you should be able to ask Alexa turn on Finestra Bagno Vasca and the blinds should open or Alexa set Finestra Bagno Vasca to 50 and the blinds should open half way ( if they support that )

It works with voice control! I assumed it won’t work due to the unreachable problem. Thanks in advance for the fix!

mariomaz87 commented 6 months ago

Thanks. The device is now showing as reachable in the latest version. Comparing to my other windows blinds (integrated in Alexa with another skill) I don’t have the % selector showing in the iOS app but I can control it using voice control.

NorthernMan54 commented 6 months ago

The plugin has 2 methods for operating, one is for areas where blinds are not properly support, and one for when blinds are properly supported. Have you tried changing the blinds option to true in the config?

You will need to delete the existing blind from the Alexa app, then make the change, restart homebridge, then ask Alexa to discover devices again.

mariomaz87 commented 6 months ago

The plugin has 2 methods for operating, one is for areas where blinds are not properly support, and one for when blinds are properly supported. Have you tried changing the blinds option to true in the config?

You will need to delete the existing blind from the Alexa app, then make the change, restart homebridge, then ask Alexa to discover devices again.

Thanks, that solved also this issue. I think we can close the issue?

NorthernMan54 commented 6 months ago

Glad to here