New Software Upgrade. Update from 3.2.0 to 3.2.1

How to configure Meshlium or use the Manager System
libelium-dev
Posts: 27967
Joined: Mon Sep 28, 2009 1:06 pm

New Software Upgrade. Update from 3.2.0 to 3.2.1

Post by libelium-dev » Mon Jun 29, 2015 2:07 pm

Dear Developer,

We are happy to inform that we have implemented new software versions for our main products.

They are available for free download following the instructions on the links below.

Meshlium Manager System v3.2.1:

- Added IoTSens cloud connector
- Scanner vendor list updated
- Added optional MAC randomization in scanner

To update your Meshlium, please follow the steps explained in the chapter "Upgrading old versions of Meshlium" of the Meshlium Technical Guide.

Cheers,

--The Libelium R&D Team


- NOTE: Password of the local MySQL Database can not be changed. An external Data Base may be used to store the frames with a new password.

- NOTE: TX power of AP is fixed to "auto" due to a bug detected in the drivers. We will enable a way to set the power in future releases.

inv_dinesh
Posts: 9
Joined: Tue Sep 01, 2015 12:10 pm

Re: New Software Upgrade. Update from 3.2.0 to 3.2.1

Post by inv_dinesh » Tue Sep 01, 2015 12:19 pm

We had procured multiple Meshlium sensors for our development activity from Libelium over the past couple of months. Of recent we upgraded one of these sensors from version Meshlium 3.1.9 to Meshlium 3.2.1; following this we are observing the following issues with this particular sensor:
1. A number of Bluetooth devices are not getting scanned by the sensor; these devices do get scanned by other Meshliums whose software has not been upgraded yet (the software version on these Meshliums is 3.1.9). Also these devices are kept close to the sensor whose software was upgraded and relatively farther from the other ones (having older software).
2. After the upgrade, I am unable to get the scanned data written to a local file, although writing to local data-base is working but writing to the local file is no longer effective. (When I click on "show data" nothing comes up, except any older data already stored in that file) In doing so I have ensured that the associated check-boxes are selected.
3. Is there a way to downgrade to an older version, e.g. 3.1.9?

libelium-dev
Posts: 27967
Joined: Mon Sep 28, 2009 1:06 pm

Re: New Software Upgrade. Update from 3.2.0 to 3.2.1

Post by libelium-dev » Wed Sep 02, 2015 3:08 pm

Hi inv_dinesh,

We realized an issue in the Bluetooth update process in the 3.2.1 version.
1. The decreasing of Bluetooth devices detected in this version is due to the vendor table update. To solve it, you can try to update the database, connecting to your Meshlium by SSH, accessing to mysql

Code: Select all

mysql -u root -p
, it requests the password and then you can paste

Code: Select all

ALTER TABLE `macaddress`.`OUIData` CHANGE COLUMN `oui` `oui` VARCHAR(60) NOT NULL ;
ALTER TABLE `MeshliumDB`.`bluetoothData` CHANGE COLUMN `Vendor` `Vendor` VARCHAR(60) CHARACTER SET 'utf8' COLLATE 'utf8_unicode_ci' NOT NULL ;
. Anyway, in the next version of the Manager System will be solved.

2. We will thoroughly review the local file issue in order to find out a solution for the next update. Anyway, the file section will disappear.

3. Meshlium downgrade it is not possible at the moment.

We are sorry for the inconveniences caused and we thank you for your feedback.

Best regards,

inv_dinesh
Posts: 9
Joined: Tue Sep 01, 2015 12:10 pm

Re: New Software Upgrade. Update from 3.2.0 to 3.2.1

Post by inv_dinesh » Thu Sep 03, 2015 8:51 am

Hello,

Thanks for your response.

After executing the steps suggested for BluetoothData Table, the Bluetooth scan is working fine. Most of the Bluetooth devices are now getting scanned and are listed in the DB.

We are Still facing a couple more issues, your quick help on these will be appreciated:
1. No results are seen in the wifiScan table as of now. Though the same wifi device is scanned by another nearby meshlium(running on rel 3.1.9). Do we need to make a similar change to wifiScan Table? Can you please provide the exact SQL command that should be run.

2. When trying to access the MeshliumDB using the phyMyAdmin after upgrade , Following error is thrown :

Fatal error: strtotime() [<a href='function.strtotime'>function.strtotime</a>]: Timezone database is corrupt - this should *never* happen! in /usr/share/phpmyadmin/libraries/db_info.inc.php on line 88

Thought the Db is accessible via SSH to Meshlilum or from Other SQL browser Applications.

3. Also, would it be advisable to not upgrade the other Meshlium sensors to the new release(3.2.1)?

Regards,

inv_dinesh
Posts: 9
Joined: Tue Sep 01, 2015 12:10 pm

Re: New Software Upgrade. Update from 3.2.0 to 3.2.1

Post by inv_dinesh » Thu Sep 03, 2015 1:48 pm

Hi,

I am unsure if the following is specific to the use of Meshlium 3.2.1 as it could be a generic observation (irrespective of the software version):
1. While the Bluetooth concern got almost addressed as we are able to observe greater scanned devices as well as data on both local file and local database, however, the local file which showed the data is actually not the one selected for data-writing; i.e. the write logo is against a different file which does not show any scanned data, while the scanned data shows up for a different file in the list (created earlier, but disabled presently for data writing).
2. We are observing for quite some time that a number of WiFi devices do not get scanned on a consistent basis; i.e. a number of devices kept stationary at different locations are getting scanned intermittently by the Meshlium sensor. As an example, a smartphone kept at Line-of-Sight 10m range from a Meshlium for 1 hour showed up ~20 times (for different minutes) in the scan-results. Ideally I would have expected it appear at least 60 times in the scan results.
(We have presently set the WiFi scanning time as 60 sec in the Manager System.)

It is extremely critical for us to have consistent scanning of the WiFi devices (unless these go out of range with respect to the Meshlium sensor) for our intended application/use-case.

Thanks for suggesting a prompt resolution to the above.

Regards

libelium-dev
Posts: 27967
Joined: Mon Sep 28, 2009 1:06 pm

Re: New Software Upgrade. Update from 3.2.0 to 3.2.1

Post by libelium-dev » Thu Sep 03, 2015 1:57 pm

Hi inv_dinesh,

We have updated one Meshlium from version 3.1.9 to 3.2.1 and the only bug found is related with Bluetooth process and solved in our previous post (except save into file). So the following issues you post don't have any relation to update to 3.2.1 version.

1. This WiFi problem is different from the Bluetooth happened. As we can see in the image sent you to our mates, we have detected you can't see any data (in Bluetooth happened you can't see new data). So it could be a corruption of your MySQL table, try to follow these steps to solve it.
- Stop the wifiScan service (it is located at the top right of the ManagerSystem WifiScan screen)
- Access to the database by SSH

Code: Select all

mysql -u root -p
it requests the database password

Code: Select all

use MeshliumDB;
repair table wifiScan;
- Start the wifiScan service.

2. In our update process this problem does not happen. Anyway, it seems to be related with your timezone. We don't know if you have made some change related to it but you can try to change the timezone in your php.ini file (/etc/php5/apache2/php.ini) and set your timezone following the php documentation (http://www.php.net/manual/en/timezones.php)

For example:

Code: Select all

...
;;;;;;;;;;;;;;;;;;;
; Module Settings ;
;;;;;;;;;;;;;;;;;;;

[Date]
; Defines the default timezone used by the date functions
date.timezone = "Europe/Madrid"
...
and restart the web server.

3. We always recommend to be up to date because in every update we solve some minor bugs and make important improvements and new relevant features. On this occasion one improvement has produced a bug an it will be solved for the next version and meanwhile it is launched, we post the solution here in order to everybody who affect it, can work with their Meshlium properly.

Regarding your question about the "Anonymize MAC": if you mark this field, the Meshlium will store the MAC address ciphered with an MD5 hash changed each day. You can see in our tech guide pages 112 and 120 http://www.libelium.com/downloads/docum ... _guide.pdf

Let us know your situation after doing all we commented.

Best regards,

inv_dinesh
Posts: 9
Joined: Tue Sep 01, 2015 12:10 pm

Re: New Software Upgrade. Update from 3.2.0 to 3.2.1

Post by inv_dinesh » Wed Sep 09, 2015 5:56 am

Hello,

Concerning the Meshlium with updated software (ver. 3.2.1) based on the suggested resolution we were able to regain WiFi scanning and could observe the scanned results in the local data-base.
However, there are still following concerns of varying criticality:
1. [Extremely critical; most important and concerning] Irrespective of the software version (i.e. whether it is ver. 3.1.9 or ver. 3.2.1) we are observing a number of mobile phones getting skipped/not-scanned in the WiFi-Scan consistently. For instance, we have tested with 6 smartphones (Blackberry mobile, a couple of Samsung mobiles, a Micromax mobile, Microsoft-Lumia mobile and a Sony mobile) by positioning these at fixed locations within ~10m from two Meshliums (one with software ver. 3.2.1 and other with ver. 3.1.9), for at least 2 hours. In the 120 min duration, these devices got scanned very few times (some of these got scanned just once) with random duration between successive scans, e.g. 10 / 20 / 45 min. At times, some devices got scanned multiple times within a single minute; but then the same device did not show up in the scans for the next 30 min and then showed up for another couple of minutes and again disappeared for next 10 min. To summarize, the occurence of the devices in the scans was very random and often very rare.
Please note that we have conducted this experiment by having the WiFi scanning interval set to 60 sec and then again the scanning interval set to 90 sec (for both Meshlium devices; one with older and other with newer software version), but the observations were similar in both scenarios.
We really need to overcome this issue as it directly impacts our decision to use these sensors. Presently we are uncertain to what extent we can rely on the working of the Meshliums for WiFi scanning. With respect to Bluetooth scanning, we are pretty much convinced as we do observe fairly consistent scans of all devices with their Bluetooths enabled and in visible mode. However, since WiFi is a more prevalent interface and majority devices are expected to have their WiFi enabled, it is extremely critical for us to have consistent scanning of all these devices.
In trying to understand the reason for this inconsistency in case of WiFi devices (especially Smartphones), it would be helpful if you can share some insight with respect to any inherent restrictions in the scanning operation and corresponding results; e.g.:
a. Is there any dependency on the max. number of devices that can be scanned?
b. Any limitations with respect to the make and model of the devices that can be scanned? In general, are there any particularly known smartphone make and models that are observed to not getting scanned by Meshlium?
c. Any other limiting aspect, e.g. the device must be connected to some WiFi-AP in order for it to be scanned consistently?
d. If the above stated concern is already known, are you working on providing a resolution for the same?

Requesting you to treat the above on high priority as it completely impacts our customer deliverables and puts a number of projects at stake.

2. [Important] Working with the Meshlium with software ver. 3.2.1, we are observing that while the scanned output gets duly written to the local database, while attempting to also have these written to a "local file":
- In case of WiFi-Scan, the same is NOT getting written to the chosen/selected file but some other pre-existing local-file (even though the latter is not selected to be written; and the pencil-sign shows up against the previous file only).
- In case of Bluetooth-Scan, nothing gets written to the selected local file; only the scanned results get written to the local database
I did observe in the new software release notes that you intend to do away with the local file in future, but as of now I do also need to access this file for analysis and wondering how the above concerns can be resolved.

Thanks.

libelium-dev
Posts: 27967
Joined: Mon Sep 28, 2009 1:06 pm

Re: New Software Upgrade. Update from 3.2.0 to 3.2.1

Post by libelium-dev » Wed Sep 09, 2015 9:47 am

Hi inv_dinesh,

1. Is it possible you give us permission to access to one Meshlium by SSH in order to see the process in live and detect any possible issue? It is not common the duplicity and the lack of a device during a lot of time. If you agree, send us the credentials by email (tech [at] libelium [dot] com)

2. As we can said in previous post, we are working on find the solution but bear in mind this feature will be not supported in future versions because it generates files with a big amount of data. If you want to export scanner information, we recommend you to use phpMyAdmin export tool.

Best regards,

inv_dinesh
Posts: 9
Joined: Tue Sep 01, 2015 12:10 pm

Re: New Software Upgrade. Update from 3.2.0 to 3.2.1

Post by inv_dinesh » Wed Sep 09, 2015 1:33 pm

Hello,

Thanks for your response.
We can certainly share the access to any of the Meshliums through desktop sharing mode (as direct access through SSH may not be feasible as it is a secure office network).

In this respect we can use software like Skype / Lync / Team-Viewer / AMMYY Admin. Please state your availability; assuming that the support is located in Spain and realizing the 3.5 hrs time difference between India and Spain, it would be helpful if this can be scheduled between 9AM and 3PM Spanish time.

Awaiting your response. Please do share the contact details as sync-up over phone might be required to share connection details.

Thanks.

inv_dinesh
Posts: 9
Joined: Tue Sep 01, 2015 12:10 pm

Re: New Software Upgrade. Update from 3.2.0 to 3.2.1

Post by inv_dinesh » Thu Sep 17, 2015 4:15 pm

I am trying to update the software on a Meshlium from 3.2.0 to 3.2.1 but unable to do so. In this respect, since the Meshlium is installed quite high above the ground it is not feasible to connect it directly to the Internet, I chose the option to download the upgrade (from the link: http://www.libelium.com/downloads/manag ... 321.libupd) to a laptop and use the option of upload update from a “Local file” (by connecting to the Meshlium through WiFi). Specifying the file using the select option, firstly it is observed that the file path is something other than what I have specified (it comes as “C:\fakepath\320-321.libupd” whereas the file is in some other folder) and then clicking on “Upload”, the system shows progress up to some random percentage and after that, each time results in an error screen ("Error-connection ..."). I have tried this process multiple times, but each time the result is the same (the upload progress changes every time, not always increasing, but eventually the error page comes up). Finally after trying for 20-30 times I eventually saw the upload going to 100% but after that the same web-page reloads and the system does not provide any install button.
I also tried choosing the URL option but that does not seem to work at all as nothing happens.
So currently I do not know how to upgrade this Meshlium!

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests