joeyhage / homebridge-alexa-smarthome

Connect Alexa devices to HomeKit
MIT License
81 stars 20 forks source link

Fan accessory (Vornado Transom) recognised by plugin but not in Home app. #113

Closed BenWard closed 7 months ago

BenWard commented 7 months ago

Describe Your Problem:

Hi Joey! Very excited for the new fan support. Thanks for all your work on this.

Getting my new Vornado Transom fan set up, I'm running into an odd issue: The fan accessory is recognized and is available in the Homebridge Accessories list, and can be turned on/off through the Homebridge web UI. However, the device is not appearing in the Apple Home app, or any other HomeKit frontends (Eve, Home+).

I've turned on plugin debugging, and the following output from the plugin comes out on start-up. Not sure if there's any subtle issue with the config data that would be preventing it being picked up outside of Homebridge?

Let me know if there are further debugging steps I can take to extract more info. Thanks!

Logs:

[2/15/2024, 11:31:42 AM] [HomebridgeAlexaSmartHome] Extractor Fan ::: Attempting to add accessory(s) for device: {
  "id": "<UUID>",
  "displayName": "Extractor Fan",
  "description": "Vornado Transom",
  "supportedProperties": [
    "turnOff@<UUID>_4",
    "turnOff",
    "turnOn",
    "setModeValue@<UUID>_2",
    "setModeValue@<UUID>_1",
    "setRangeValue@<UUID>_3",
    "turnOn@<UUID>_4"
  ],
  "supportedTriggers": [],
  "supportedOperations": [
    "turnOff@<UUID>_4",
    "turnOff",
    "turnOn",
    "setModeValue@<UUID>_2",
    "setModeValue@<UUID>_1",
    "setRangeValue@<UUID>_3",
    "turnOn@<UUID>_4"
  ],
  "availability": "AVAILABLE",
  "icon": {
    "@iconType": "SmartHomeApplianceType",
    "value": "FAN"
  },
  "providerData": {
    "enabled": true,
    "relationships": [],
    "categoryType": "APPLIANCE",
    "deviceType": "FAN",
    "dmsDeviceIdentifiers": [
      {
        "deviceSerialNumber": "<SERIAL>",
        "deviceType": "A1AZ0VKGUB06NH"
      }
    ]
  }
}
[2/15/2024, 11:31:42 AM] [HomebridgeAlexaSmartHome] Extractor Fan ::: Current state: [
  {
    "namespace": "Alexa.ToggleController",
    "name": "toggleState",
    "value": "OFF",
    "instance": "4"
  },
  {
    "namespace": "Alexa.ModeController",
    "name": "mode",
    "value": "0",
    "instance": "2"
  },
  {
    "namespace": "Alexa.ModeController",
    "name": "mode",
    "value": "0",
    "instance": "1"
  },
  {
    "namespace": "Alexa.EndpointHealth",
    "name": "connectivity",
    "value": {
      "value": "OK"
    }
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 67,
    "instance": "5"
  },
  {
    "namespace": "Alexa.PowerController",
    "name": "powerState",
    "value": "OFF"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 0,
    "instance": "3"
  }
]

Plugin Config:

{
    "devices": [
        "Extractor"
    ],
    "auth": {
        "refreshInterval": 4,
        "proxy": {
            "clientHost": "<hostname>.local",
            "port": 8868
        }
    },
    "amazonDomain": "amazon.com",
    "language": "en-US",
    "performance": {
        "cacheTTL": 60,
        "backgroundRefresh": true
    },
    "debug": true,
    "platform": "HomebridgeAlexaSmartHome"
}

Environment:

BenWard commented 7 months ago

Updating and closing as I think this was not a bug with the plugin. Instead I removed and re-added my Homebridge bridge in Apple Home and the missing device was discovered; it now works as expected. Thanks!