At times you may find that a device is not responding to controls you send it, or you see a message in the Devicebook app that says 'Device is disconnected' or 'Device is not responding to commands.'
For each unresponsive device:
1. Make sure the device is powered on
If it is a battery powered device, make sure that the battery in the device is healthy. Replace it with a new one, or charge it if needed.
If it is an AC/Mains-powered device, make sure it is still plugged in to power.
2. Make sure the device is in range of the Devicebook Hub
If the device is wireless and was moved after installation, it may have been moved out of range of the Devicebook Hub. In this case, move the device back to where it was initially installed.
If the Devicebook Hub was moved after installation of the device, some wireless devices may now be out of range of the Devicebook Hub. In this case, move the Hub back to where it was initially installed.
If the device is connected to the hub by an Ethernet cable, or some other cable, make sure that both ends of the cable are securely attached.
3. Power Cycle the device
- Power the device off by disconnecting it from its power supply or battery.
- Wait for five seconds.
- Reconnect the device to its power supply or battery.
- It may take up to five minutes for the device to become reconnected in Devicebook.
4. Wait for 10 minutes, and try again
Some devices may stop accepting commands if too many have been sent in a short period of time. For example, third-party-cloud-connected devices will rate-limit the number of requests sent per minute.
Wait for a period of time, at least ten minutes, and try to control the device again.
If none of the above steps solved the issue, try the steps detailed in this article: My Devicebook Hub is Offline or not functioning properly. How do I fix this?