v1.2.x - Please Report "Not Responding" issues here
See original GitHub issueIf you are running v1.2.0, v1.2.1 or v1.2.2; please downgrade to v1.1.6 or update to the latest beta.
If you are having issues with the latest beta please post below with the following information.
- Homebridge logs with
DEBUG=ciao:*
set (see below). Logs without this being set are not helpful. - Operating System (Windows / macOS / Ubuntu / Alpine / Debian) - if using Docker post what OS your Docker image is running.
If you don’t have this info, please restrain from commenting so it’s easier for us to track what’s going on.
How to set DEBUG=ciao:*
:
If you are using Homebridge with hb-service
choose “Homebridge Settings” from the upper-right-corner drop down menu and enter ciao:*
into the DEBUG
input, then restart Homebridge:
If you are running Homebridge at the command line you can do so like this:
DEBUG='ciao:*' homebridge
Systemd users can add DEBUG=ciao:*
line to the bottom of their /etc/default/homebridge
file.
Other users need to set DEBUG=ciao:*
as an environment variable.
How change Homebridge version:
You can change the Homebridge version from the Homebridge UI (v4.29.0 or later):
Issue Analytics
- State:
- Created 3 years ago
- Comments:232 (44 by maintainers)
Top GitHub Comments
To give some insights. We are currently preparing some other changes to improve stability of the HomeKit server. When we opened this issue to track issues with the migration from the
bonjour-hap
library (used in version<= 1.1.6
) to the newly writtenciao
library (used with version>=1.2.0
), we discovered that many people are experiencing the same symptoms (accessories with ‘No response’) though caused by totally different problems (It may also didn’t help that we released 1.2.x at the same time as iOS 14 lol). With the .1, .2 and .3 released we could already squash some problems, which most people experienced here. To help us discover the problems faster and also to help the users having a much more reliable homebridge experience we are reworking some of the fundamental connection and plugin management.The thing is, this takes time. No one here is getting paid for working on homebridge or it’s subsequent libraries. It’s done in our free time and we are doing our best.
We have the impression that most people are running fine with 1.2.x, though as we haven’t any analytical data we can’t exactly calculate how many people are actually running 1.2.x. And as there are also enough people having problems and as we currently haven’t the capacity and time to process all issues posted here, we decided to revert the latest version of homebridge back to 1.1.6.
So what to do now:
sudo npm install -g homebridge
sudo npm install -g homebridge@1.2.3
) or you simply revert back to 1.1.6 as shown above.If someone wants to follow along the current development progress and process you can visit https://github.com/homebridge/HAP-NodeJS/projects/4 (the different columns are explained here). If you want to try the latest (publicly available) state of this planned release you can install the beta by running
sudo npm install -g homebridge@beta
.Thank you so much for this post - I always wanted to use your official Homebridge app but struggled to get it configured correctly with UnRaid - using your guides the installation went flawless for me! Backed up my siwatinc homebridge config and restored it into the proper homebridge docker easily.