Problem in homekit "accessory not responding"
See original GitHub issueWhat issue do you have? Please be as thorough and explicit as possible.
Problem in homekit “accessory not responding” In ewelink apps the switch is available and working
Details of your setup.
-
Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS? 3
-
Which version of Homebridge/HOOBS do you have?
HOOBS 3.3.12
- Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
Linux Ubuntu 20.04.2 LTS Node Version 14.17.2
-
Which version of this plugin (homebridge-ewelink) do you have? Has the issue started since upgrading from a previous version? 8.0.2
-
Which eWeLink devices do you have that are causing issues? Please include product models if applicable.
Please paste any relevant logs below.
hoobs -d |grep "eWeLink"
[16.08.2021, 19:34:13] Registering platform 'homebridge-ewelink.eWeLink'
[eWeLink] Initializing eWeLink platform...
[eWeLink] Initialising plugin v8.0.2 | Node v14.15.1 | HB v1.3.4 | HOOBS v3...
[eWeLink] Config entry [debugReqRes] is unused and can be removed.
[eWeLink] Config entry [sensorTimeLength] is unused and can be removed.
[eWeLink] Config entry [sensorTimeDifference] is unused and can be removed.
[eWeLink] Config entry [valveTimeLength] is unused and can be removed.
[eWeLink] Config entry [hideTHSwitch] is unused and can be removed.
[eWeLink] Config entry [hideZBLDPress] is unused and can be removed.
[eWeLink] Config entry [disableHTTPRefresh] is unused and can be removed.
[eWeLink] Config entry [inUsePowerThreshold] is unused and can be removed.
[eWeLink] Config entry [lowBattThreshold] is unused and can be removed.
[eWeLink] Config entry [resetRFBridge] is unused and can be removed.
[eWeLink] Plugin initialised. Setting up accessories....
[eWeLink] Sending HTTP login() request.
[eWeLink] Web socket host received [eu-pconnect6.coolkit.cc].
[eWeLink] Sending WS login request.
[eWeLink] LAN discovery starting.
[eWeLink] WS login successful.
[eWeLink] LAN discovery complete.
[eWeLink] LAN monitoring started.
[eWeLink] [Кухня] initialising with options {"logging":"debug","showAs":"default"}.
[eWeLink] [Кухня] initialised and found locally with IP [192.168.3.12].
[eWeLink] [Спальня с балконом] initialising with options {"brightnessStep":1,"logging":"debug"}.
[eWeLink] [Спальня с балконом] initialised and LAN mode unavailable as not discovered/supported.
[eWeLink] ✓ Setup complete. This plugin has been made with ♥ by bwp91 from the UK!
[eWeLink] [Кухня] receiving update {"switch":"on","online":true,"updateSource":"LAN"}.
[eWeLink] [Кухня] current state [on].
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
HomeKit Not Responding (No Response Error) - [ FIXED! ]
First, ensure that the devices are connected to your home network and that you can control them from their manufacturer's app. This indicates...
Read more >Suddenly all my devices stopped responding on Homekit, All ...
When this happens to me it's often after the hub has locked or lost connection or been powered off from a dead battery....
Read more >HomeKit accessories not responding - Apple Community
HomeKit accessories not responding · For HomePod, open the Home app on your iOS device, tap User uploaded file · On your Apple...
Read more >HomeKit No Response is the worst part of Smart Home tech
As with most technical problems, a simple reboot of the device fixes it 99% of the time. Apple could fix this to enable...
Read more >Apple HomeKit not working - Ubiquiti Community
I was able to re-pair all the Homekit devices in the house without any issue. I just got home from work, and I...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @motogon
One of the things I added to v8 of the plugin was showing an accessory as ‘No Response’ if it is reported offline by eWeLink. It will also show as no response while the plugin is restarting. The status will be removed when the accessory comes back online but sometimes you need to restart the Home app for the status to be updated there.
You can see in the logs when eWeLink reports an accessory as online/offline with messages like
You can also disable this with ‘Disable No Response’ option in ‘Optional Settings’:
An accessory will also be shown as ‘No Response’ if it is controlled through the Home app but the command fails. In this case the ‘No Response’ will be removed after a couple of seconds, but a home app restart may be required to remove the status there.
If none of these situations apply, then let me know so I can look into this further.
The eWeLink app also tries to use LAN mode so even if the device is blocked/disconnected from the internet, if the ewelink app is running on a device connected to the same network then it will be able to control the device.
In auto mode, the plugin will always attempt to control via LAN first. If this fails then it will revert to WAN.
I’m glad you found the issue – I was starting to really wonder what the issue was!