check online status first

[CloneDevil]

Is it possible to add a status check by pinging the server first?
At the moment the whole Homebridge gets nearly locked when the server is not online.

[mpbzh]

Good input.

Does homebridge lock up while waiting for a reply from Plex or is it just constantly retrying and thus blocking homebridge?

[CloneDevil]

I think the problem occurs when I open the Homebridge-App and it automatically checks the status after selecting the room with the Plex-Server in it. I will look in the log-files later when I am at home.

[mpbzh]

That would certainly help fixing the ussue.

[CloneDevil]

Now I can't trigger it anymore! Your code became self aware and fixed itself. 🤪

…

Am 05.02.2018 um 17:18 schrieb Michael Burri ***@***.***>: That would certainly help fixing the ussue. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[mpbzh]

Feel free to reopen the issue when my code decides to act up again 😉

[CloneDevil]

Oh. Wrong github-repository!! I am testing too many projects at once.
In the log it says:
Getting current state...

Then after a while:
Error getting state (status code 1): Error: connect ETIMEDOUT [my plex ip address]:32400

[mpbzh]

That still does not really answer my question:

Does homebridge lock up while waiting for a reply from Plex or is it just constantly retrying and thus blocking homebridge?

A slow request should not block the whole homebridge, because these requests are asynchronous which means homebridge should just go on working while it waits for the Plex server to reply.

Also it should not retry more quickly than it checks for the status anyways.

[CloneDevil]

Ok. I try to describe it as well as possible:
I stopped Homebridge as service and startet it per SSH with "sudo homebridge"
After waiting for a while to load I open the Homekit-App on my iPhone and select the room with the Plex-Status inside I see in the running SSH-window this message: "Getting current state..." No other Homebridge accessory can update for ca. half a minute.
So the answer is that Homebridge locks up.

[mpbzh]

This looks like a platform limitation: homebridge/homebridge#948

I'm not sure what to do about it. While I agree, that a non-reachable Plex should not block the whole homebridge, I'll have to think of an elegant solution for that problem.

Feel free to comment with any good ideas.

[aviationio]

Has anyone came up with a solition for this? My homebridge also completely locks up if my plex server is not running and in Home app I navigate to the room which contains this plex sensor. If plex server is running, everything is fast.