Thingsee Support

Limitations with Thingsee One HW and SW

We’ve previously discussed some features of the Thingsee One device that may cause some drawbacks for the end user. Rather than have you look for the information from different blog posts and helpdesk articles, we thought it would be helpful to comprise them into a single source. What follows is a list of Thingsee One HW and SW features that may require special attention from the user.

 

Some features are affected by the hardware design and construction of the device. What this means is that the HW and the SW relating to that specific feature work as such, but the construction of the complete devices as well as the other components contained therein affect the functionality of the features in question.

  • Light sensor: due to the dimmed window on top of the sensor, as well as the sensor’s characteristics and placement inside the device, the sensor is good for measuring changes in light levels, but not for getting absolute values of environment brightness.
  • Temperature sensor: the placement as well as the temperature of other device components affect the sensor's temperature readings, which basically causes the sensor to reflect the internal temperature of the device instead of ambient temperature.
  • Humidity sensor: the sensor’s placement causes the readings to be affected by the device HW, much like in the temperature sensor case. This, in turn, means it works best when programmed to measure slower long-term chances in relative humidity rather than absolute values or quick changes.

 

There are also features where both the device's SW and its HW design cause some issues, even though the components themselves work perfectly fine.

  • iNemo 9-axis inertial sensor (source for the gyroscope, accelerometer and magnetometer sensor data): the problem here is that the current fusion algorithm does not work correctly. However, the sensor itself works perfectly fine, and the gyroscope and other 9-axis features can be utilised by creating a custom algorithm using the Thingsee SDK. For basic orientation data you can also use the accelerometer, which can be utilised straight from the Creator tool. 

 

There are also some HW and SW issues where the root cause is not yet fully known or understood. This affects the WiFi, GPS and SMS notification features.

  • WiFi: The WiFi module (Texas Instruments CC3000) has been found to have issues at least when connecting to servers in the same local area network with the device. The problems are hardware based and cannot be fixed with a software update. The WiFi module has not been deactivated, and in some use cases it is fully functional.  
  • GPS: sometimes the GPS is not accurate enough to give a pinpoint location. This needs further testing in order to assess the root cause of the problem, be it in the SW or HW. 
  • SMS notifications: there are reports of messages that haven’t been sent even though it has been defined in the purpose in question. The specific root cause is still unclear: it can be caused by the operator’s limitation for the amount of text messages per a given time period, or it can be a SW limitation that cannot be fixed by the end user. We’re looking into this.

 

There is also the issue of Bluetooth connectivity. The Bluetooth chip itself is intact, but the software does not include working BT profiles. The end users can still make use of the chip by creating a custom firmware build using the Thingsee SDK.

 

We hope that this article is helpful. If you still have questions about the product or its use, please don’t hesitate to contact us at feedback@thingsee.com

Have more questions? Submit a request

Comments