Skip to content
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

Devices are unreachable after a while #603

Open
martinhomolka opened this issue Mar 3, 2024 · 5 comments
Open

Devices are unreachable after a while #603

martinhomolka opened this issue Mar 3, 2024 · 5 comments
Labels

Comments

@martinhomolka
Copy link

Current Situation

Hello,
I have 3 Hue hubs at home (a lot of lights), and so I want to connect the two Hue Hubs with Alexa through Homebridge. All works fine, when I restart the homebridge, but it the devices become unreachable after some time. I can see in the homebridge log that the Alexa emits the message and it is delivered to the Homebridge, but it does nothing.

Logs

2024-03-03T20:52:47.318Z alexaLocal Emitting Alexa.PowerController
[3/3/2024, 9:52:47 PM] [Alexa] PowerController TurnOn CC:22:3D:E3:CE:31 { characteristics: [ { aid: 177, iid: 10, status: -70410 } ] } null

Configuration

{
    "bridge": {
        "name": "Homebridge - Alexa",
        "username": "",
        "port": 51827,
        "pin": ""
    },
    "platforms": [
        {
            "name": "Config",
            "port": 8092,
            "auth": "form",
            "theme": "auto",
            "restart": "systemctl restart homebridge2.service",
            "tempUnits": "c",
            "lang": "auto",
            "sudo": true,
            "log": {
                "method": "systemd",
                "service": "homebridge2"
            },
            "platform": "config"
        },
        {
            "name": "Hue",
            "anyOn": true,
            "effects": true,
            "groups": false,
            "hosts": [
                "192.168.88.83",
                "192.168.88.87"
            ],
            "lights": true,
            "nativeHomeKitLights": false,
            "nativeHomeKitSensors": false,
            "resource": true,
            "sensors": true,
            "users": {
                "": "",
                "": ""
            },
            "wallSwitch": true,
            "platform": "Hue"
        },
        {
            "name": "Alexa",
            "username": "",
            "password": "",
            "pin": "",
            "routines": true,
            "platform": "Alexa",
            "debug": true
        }
    ],
    "accessories": []
}

Environment

  • OS: Ubuntu Focal Fossa (20.04.6 LTS)
  • Software: homebridge
  • Node:
  • npm:

Process Supervisor

systemd

Additional Context

No response

@NorthernMan54
Copy link
Owner

NorthernMan54 commented Mar 4, 2024 via email

@martinhomolka
Copy link
Author

When I tried it for the first time, it did resolve the issue itself, but after some time it stopped working again so I tried it again and this time it did not solve the issue, the devices remained unresponsive.

@martinhomolka
Copy link
Author

martinhomolka commented Mar 4, 2024

Found this in the log, not sure if it helps:

2024-03-04T14:23:53.239Z alexaActions alexaDiscovery
[3/4/2024, 3:23:53 PM] [Alexa] ERROR: Parsing failed, removing duplicate endpointID => Garden Tree Spot 8
2024-03-04T14:23:53.257Z alexaActions alexaDiscovery - returned 69 devices
2024-03-04T14:23:53.259Z alexa:Messages INFO: DeviceList empty feature not enabled or config error in deviceListHandling

@NorthernMan54
Copy link
Owner

Error -70410 is defined here - https://github.com/homebridge/HAP-NodeJS/blob/6dbba2f9956d059ddc7976d44e060c030ac9ad06/src/lib/HAPServer.ts#L94

Looks like the plugin is sending an incorrect value, give me a few days to look into this.

@NorthernMan54
Copy link
Owner

NorthernMan54 commented Mar 8, 2024

I spent the morning looking into this in detail, and could not recreate the issue. I had updated my setup to the latest version of the Homebridge-hue plugin, and tried turning on and off a light. This worked without issue.

I also looked at the logs associated with your account and did not notice anything.

Can you enable more debug options, restart homebridge, wait for the issue to occur, then download and share the homebridge log. As the file is large and may contain personal setup details, please reach out via the homebridge discord server, and upload via a direct message to me. This log should contain the details around what is occurring between the various components. Tks

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants