Table of contents
    [MISSING: System.API.no-headers]

    Version as of 23:20, 23 Jun 2021

    to this version.

    Return to Version archive.

    View current version

    If your seneye device has not sent a message to our servers for long enough to make us think there is a problem. We attempted to remotely contacted your seneye and reboot it, but contact could not be made.

     It is likely one of these scenarios:

     1. You have a power cut or your seneye has become disconnected.

    2. Your data connection from the seneye to the cloud is down.

    3. Your seneye has stopped responding.

    4. If you are using a PC it has gone to sleep or stopped responding.

     

    It is most likely to be easy to fix and if you can get some to check we would advise it.