deemote_diagnostic
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
deemote_diagnostic [2014/10/05 15:48] 88.187.38.162 [Diagnostic] |
deemote_diagnostic [2016/10/04 12:01] (current) |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ====== Diagnostic ====== | ====== Diagnostic ====== | ||
| \\ | \\ | ||
| - | \\ If you encounter scan/connectivity issues with Deemote, you can run a diagnostic. It will help you figure out the origin of the problem : | + | \\ If you encounter scan/connectivity issues, you can run a diagnostic. It will help you figure out the origin of the problem : |
| - | * Click on the upper right icon from the Deemote screen (or press the menu button of your device, depends of the device model) | + | * Click on the upper right icon from the Application screen (or press the menu button of your device, depends of the device model) |
| * Select the Diagnostic option | * Select the Diagnostic option | ||
| * Click on the Diagnostic button | * Click on the Diagnostic button | ||
| Line 11: | Line 11: | ||
| **GCM:** | **GCM:** | ||
| * **Ok**: All good | * **Ok**: All good | ||
| - | * **NotRegistered**: Deemote is trying hard to register to the GCM service but it seems like Google doesn't want to. Make sure you have a Google account configured on your phone. You can also try to reboot your phone | + | * **NotRegistered**: The application is trying hard to register to the GCM service but it seems like Google doesn't want to. Make sure you have a Google account configured on your phone. You can also try to reboot your phone |
| * **HttpError**: The GCM service returned an HTTP error, this should never happen | * **HttpError**: The GCM service returned an HTTP error, this should never happen | ||
| * **NoSSL**: The device doesn't support SSL connections. Get rid of it, it's not secure! | * **NoSSL**: The device doesn't support SSL connections. Get rid of it, it's not secure! | ||
| * **UnknownError**: Something bad happened when sending a request to GCM | * **UnknownError**: Something bad happened when sending a request to GCM | ||
| * **NoConnection**: Can't contact the GCM service, there is no Internet connection available | * **NoConnection**: Can't contact the GCM service, there is no Internet connection available | ||
| - | * **UnknownHostError**: Seems like you have a DNS issue as Deemote is unable to resolve the GCM servers address | + | * **UnknownHostError**: Seems like you have a DNS issue as the application is unable to resolve the GCM servers address |
| * **TimeoutError**: The GCM service took too much time to reply, may be a very slow Internet access or an issue with GCM | * **TimeoutError**: The GCM service took too much time to reply, may be a very slow Internet access or an issue with GCM | ||
| * **UnknownGcmErrorStatus**: The GCM service returned some kind of unexpected error | * **UnknownGcmErrorStatus**: The GCM service returned some kind of unexpected error | ||
| Line 22: | Line 22: | ||
| * Your device has no Google account configured, you should configure one | * Your device has no Google account configured, you should configure one | ||
| * Your device has connectivity issues with Google Cloud Messaging service, try to switch from WiFi to 3G/4G or vice versa | * Your device has connectivity issues with Google Cloud Messaging service, try to switch from WiFi to 3G/4G or vice versa | ||
| - | * Your device doesn't want Deemote to work, punish it | + | * Your device doesn't want the application to work, punish it |
| **Server:** | **Server:** | ||
| * **Online**: All good | * **Online**: All good | ||
| Line 31: | Line 31: | ||
| * **HttpError**: The server returned an error message | * **HttpError**: The server returned an error message | ||
| * **UnknownError**: Something bad happened when sending the request to the server | * **UnknownError**: Something bad happened when sending the request to the server | ||
| - | * **UnknownHostError**: Seems like there is a DNS issue, Deemote is unable to resolve the Nodria server address | + | * **UnknownHostError**: Seems like there is a DNS issue, the application is unable to resolve the Nodria server address |
| * **TimeoutError**: The server took too much time to reply, may be due to a very slow Internet connection or the server just doesn't want to reply because it's too busy | * **TimeoutError**: The server took too much time to reply, may be due to a very slow Internet connection or the server just doesn't want to reply because it's too busy | ||
| **Authentication:** | **Authentication:** | ||
| Line 42: | Line 42: | ||
| * Your computer has no Internet access | * Your computer has no Internet access | ||
| * You closed Chrome | * You closed Chrome | ||
| - | If you don't know what to do, just send me an e-mail. You can do it from Deemote. The Help option is just under the Diagnostic option | + | If you don't know what to do, just send me an e-mail. You can do it from the Application. The Help option is just under the Diagnostic option |
deemote_diagnostic.txt · Last modified: 2016/10/04 12:01 (external edit)
Page Tools
