Discovered Devices Time Out Early

[Riveloper]

Analysis

Experiencing an issue with the Alexa plug-in, where requests result in timeouts. Oddly, when I run Discover Devices again, the previously requested action executes successfully.

This is very odd. Running actions direct from the Homebridge GUI has no issues with the same devices.

Expected Behavior

This is a new install and I have not had this problem with the same setup running at our other house with another copy of the plugin. Perhaps slower network timeout to fast.

Steps To Reproduce

I am not able to give you a way to reproduce since I only experience this at a single location using the plugin and not another. Unless you try and emulate an older network like we have at this home which has 100mb Ethernet.

Logs

I didn’t know how to copy and paste the log here from the terminal.

Configuration

Not applicable as it is nothing special.

Environment

• OS: Debian
• Software: Homebridge
• Node: latest
• npm: latest

Process Supervisor

hb-service

Additional Context

I mistakenly paid for the plugin already and if it doesn’t work at this location I may need to refund

[NorthernMan54]

Sounds like your homebridge may not be stable and restarting occasionally. When you do discover devices and it starts working again, behind the scenes it refreshes the cached configuration which may get outdated if homebridge is restarting occasionally.

for a log file, try a screen shot if needed.

PS if you’re seeing things in the log file, then network bandwidth is not an issue. Also the plugin has been around for a long time, from when 100 mb connections where the norm so it shouldn’t be an issue.

[Riveloper]

I should have clarified. This occurs all the time. For every command, regardless of if I restart Homebridge or not.

I appreciate the quick reply though. I'll keep looking into what else could be the problem. Like I said, I am happy using the plugin at the other home with no issues.

Another thing that this could be is the majority of the smart home devices are run on the Leviton OmniProII. But since they do work from the Homebridge gui and HomeKit I don't think that has anything to do with it.

[NorthernMan54]

Maybe a log entry of an error message might help

one from when the issue occurs, and a second one from after the same device worked once

the error message would included device details, and my first thought they are changing