Sensor not responding in Apple Home
The sensor installation is easy. The sensor connects to the Wi-Fi network, but after a few moments it disconnects from it and is no longer visible in my home network monitoring app. In the Apple Home app, the device status is - "not responding". This is most likely due to the fact that the sensor is not connected to Wi-Fi. Of course, when I get close to the sensor, a Bluetooth connection is established and then I can see the real status of the device. Is this normal operation of the sensor? Isn't the sensor supposed to be permanently connected to the Wi-Fi network? Does this mean that the sensor will only connect to the Wi-Fi network when CO2 is detected?
Comments
3 comments
Hi,
The Smart Carbon Monoxide Alarm connects once a month to the WLAN (if it has been configured) to check if the connection is still valid and to send logs to our servers.
The WLAN will only be used by the Carbon Monoxide Alarm to send you a notification if something happens.
In order to save energy (as the WLAN is power consuming), the device communicates with your smartphone using Bluetooth so the information shown in your app will update when you get in Bluetooth range with your device (as long as the Bluetooth is ON and the app is running).
NOTE: Even if your app says "last checked X hours/days ago", that means your app collected information from the CO Alarm X hours/days ago.
The CO Alarm monitors the CO level all the time.
If the CO level reaches at least 50ppm, the device will automatically connect via WLAN to notify you about the situation, and you will be able to check the level detected by looking for your CO detector at the bottom of the main screen of your app. Press on it then use the gear icon.
Thanks for the info. That explains a lot. I suspected that the wi-fi was being turned off to save power. I think this information should be in the user manual or in the FAQ, because a lot of people ask about it on various forums on the internet. Best regards.
I have exactly the same problem! Although it sounds logical, it is annoying that Homekit continuously indicates a "fault" because the sensor is not responding. Is there a solution to solve this problem?
Please sign in to leave a comment.