devicehive/devicehive-android

DeviceHive Android example

DeviceHive Android Example

DeviceHive Android Example demostrates the usage of DeviceHive Java Library inside Android Application. DeviceHive Java Library could be easily implemented into any Android Project. It supports Android Applications for tablets and phones, Android Wear and Android Things.

This Android Application is showing how easily you can register a new Device or get the existing and start sending any data to the server. For an example we are sending current Location.

//Creating DeviceHive Instance
  DeviceHive deviceHive = DeviceHive.getInstance().init(String serverUrl,
                    new TokenAuth(String refreshToken));
//Registering new Device or getting the existing
  DHResponse<Device> dhResponse = deviceHive.getDevice(String deviceId);
        if (dhResponse.isSuccessful()) {
            Device device = dhResponse.getData();        
        }
//Sending of the notifications
device.sendNotification(String notificationName, List<Parameter> params);

DeviceHive license

DeviceHive is developed by DataArt Apps and distributed under Open Source Apache 2.0. This basically means you can do whatever you want with the software as long as the copyright notice is included. This also means you don't have to contribute the end product or modified sources back to Open Source, but if you feel like sharing, you are highly encouraged to do so!

© Copyright 2017 DataArt Apps © All Rights Reserved

devicehive-android's Issues

GetDeviceEquipmentStateCommand - bug when getting deviceId

When trying to get deviceId from with

GetDeviceEquipmentStateCommand.getDeviceId(resultBundle), an error is returned that states that expected result was String, but it got Parcelable instead.

The simple fix is to make a change in the following line:

GetDeviceEquipmentStateCommand: 96

from getParcelable(...) to get String().

Unhandled status code 204 and unhandled exception - bug ?

I think I found a bug when device is trying to register.
When device registers returns status code 204, from documentation for RESTful protocol 1.3.1 -
"204 No Content: Requested operation completed successfully and there is no resource in the response body (typically for DELETE operations)."
So according to this i think that code 204 is successful status code and need to be in isSuccessStatusCode(int statusCode) in network/NetworkCommand.java. So on line 171

FROM:
protected boolean isSuccessStatusCode(int statusCode) {
return statusCode == 200 || statusCode == 201;
}

TO:
protected boolean isSuccessStatusCode(int statusCode) {
return statusCode == 200 || statusCode == 201 || statusCode == 204;
}

When the code is 204 and it has no resources in the body, an exception is raised, because responce.getEntity() returns null and toString cannot parse it. So on line 209 I suggest

FROM:
String responceString = EntityUtils.toString(responce.getEntity());

TO:
try {
responceString = EntityUtils.toString(responce.getEntity());
} catch (IllegalArgumentException iae) {
responceString = "";
}

Please look at this bug, and if it is real bug please fix it.