Dear flespi users!
Due to a critical security issue (CVE-2019-11477) discovered recently in Linux kernel we decided to perform urgent servers maintenance and upgrade them today with new kernel. We do not expect any impact on the platform services, but you may experience short reconnects to MQTT broker while we upgrade this or that server. The upgrade process will be finished this evening.
Just for your information. Have a good & peaceful day!
Due to a critical security issue (CVE-2019-11477) discovered recently in Linux kernel we decided to perform urgent servers maintenance and upgrade them today with new kernel. We do not expect any impact on the platform services, but you may experience short reconnects to MQTT broker while we upgrade this or that server. The upgrade process will be finished this evening.
Just for your information. Have a good & peaceful day!
Dear developers using flespi,
Although analytics API is marked as experimental already few projects using it for production services. That's why we are notifying here about is changes.
So the changes are:
Instead of REST method GET /gw/devices/{device-selector/intervals please use POST /gw/devices/{device-selector}/calculate.
For those realying on real-time intervals instead of analyzing MQTT user property 'active' to determine unfinished yet intervals please use 'active' counter.
New method and counter are already available, old method/counter will be removed from API end of this week.
Also we have added the possibility to calculate generalization intervals on top of intervals with POST /gw/calcs/{calc-selector}/devices/{device-selector}/calculate.
Whenever you have questions about flespi analytics, its use cases and possibilities please contact us via HelpBox.
Your flespi team
Although analytics API is marked as experimental already few projects using it for production services. That's why we are notifying here about is changes.
So the changes are:
Instead of REST method GET /gw/devices/{device-selector/intervals please use POST /gw/devices/{device-selector}/calculate.
For those realying on real-time intervals instead of analyzing MQTT user property 'active' to determine unfinished yet intervals please use 'active' counter.
New method and counter are already available, old method/counter will be removed from API end of this week.
Also we have added the possibility to calculate generalization intervals on top of intervals with POST /gw/calcs/{calc-selector}/devices/{device-selector}/calculate.
Whenever you have questions about flespi analytics, its use cases and possibilities please contact us via HelpBox.
Your flespi team
Flespi
Interval counters — calculate interval messages
Interval counters are used to calculate specific parameters for each interval
Dear flespi users!
This is the announcement for those who use bce, gosafe or suntech devices with flespi.
We made a refactoring of 1-Wire parameters parsing, and for these protocols the following changes in parameters names and types happened:
bce:
onewire.sensor.id[type=number] becomes onewire.sensor.serial[type=string]
gosafe:
temperature.sensor.serial becomes onewire.sensor.serial
sensor.temperature becomes onewire.sensor.temperature
suntech:
temperature.sensor.serial becomes onewire.sensor.serial
Both old and new parameters are registered now to allow you to apply corresponding changes in your applications.
Old parameters will be removed on Monday, 8th of July.
If you have any questions, please contact us in the chat embedded in flespi.io panel.
This is the announcement for those who use bce, gosafe or suntech devices with flespi.
We made a refactoring of 1-Wire parameters parsing, and for these protocols the following changes in parameters names and types happened:
bce:
onewire.sensor.id[type=number] becomes onewire.sensor.serial[type=string]
gosafe:
temperature.sensor.serial becomes onewire.sensor.serial
sensor.temperature becomes onewire.sensor.temperature
suntech:
temperature.sensor.serial becomes onewire.sensor.serial
Both old and new parameters are registered now to allow you to apply corresponding changes in your applications.
Old parameters will be removed on Monday, 8th of July.
If you have any questions, please contact us in the chat embedded in flespi.io panel.
Dear flespi users!
Tomorrow, July 4 after 12:00 UTC we are planning to install an update changing our registry level API.
This change affecting creating (POST) and editing (PUT) devices using the REST API.
In short, the device "ident" and "phone" JSON fields will be placed in the separate object named "configuration". The schema of that object will be defined by selected device type and may vary for different types.
For backward compatibility, we will accept "ident" and "phone" fields at the old place and automatically create a "configuration" object for such incoming REST API requests. Receiving (GET) device information will also include both "ident", "phone" and "configuration" fields with the same data.
This backward compatibility will be preserved for a few months and we will additionally update you on the exact date when we will turn it off.
There is a very small subset of devices (less than 0.01% of all created devices), containing a password in their "ident" fields after a colon char (":"). For those devices, there will be additional field "password" in the "configuration" object, and the substring of "ident" field after colon char will be moved into this new field. The "password" field will be available only in "configuration" field, no backward compatibility possible for it.
After installing the update we will notify you when new REST API will be available. Please review your flespi platform integration and update it to use the new "configuration" field in the REST API.
And soon we will post a detailed blog post explaining all recent changes in our REST API.
Tomorrow, July 4 after 12:00 UTC we are planning to install an update changing our registry level API.
This change affecting creating (POST) and editing (PUT) devices using the REST API.
In short, the device "ident" and "phone" JSON fields will be placed in the separate object named "configuration". The schema of that object will be defined by selected device type and may vary for different types.
For backward compatibility, we will accept "ident" and "phone" fields at the old place and automatically create a "configuration" object for such incoming REST API requests. Receiving (GET) device information will also include both "ident", "phone" and "configuration" fields with the same data.
This backward compatibility will be preserved for a few months and we will additionally update you on the exact date when we will turn it off.
There is a very small subset of devices (less than 0.01% of all created devices), containing a password in their "ident" fields after a colon char (":"). For those devices, there will be additional field "password" in the "configuration" object, and the substring of "ident" field after colon char will be moved into this new field. The "password" field will be available only in "configuration" field, no backward compatibility possible for it.
After installing the update we will notify you when new REST API will be available. Please review your flespi platform integration and update it to use the new "configuration" field in the REST API.
And soon we will post a detailed blog post explaining all recent changes in our REST API.
Dear flespi users!
We have successfully installed an update with the new "configuration" field in the devices REST API.
Please review your integrations and correct them for using this new field.
If you have any questions - please contact us.
We have successfully installed an update with the new "configuration" field in the devices REST API.
Please review your integrations and correct them for using this new field.
If you have any questions - please contact us.
Dear flespi users!
We have posted an article explaining the latest REST API changes and the backward compatibility removal dates:
https://flespi.com/blog/sync-up-with-changes-in-the-flespi-device-api
Please read it carefully and update your integrations.
If you have any questions - please contact us.
We have posted an article explaining the latest REST API changes and the backward compatibility removal dates:
https://flespi.com/blog/sync-up-with-changes-in-the-flespi-device-api
Please read it carefully and update your integrations.
If you have any questions - please contact us.
Flespi
Sync up with changes in the flespi device API
Novelties in working with flespi devices and when you should switch to the updated API.
Dear flespi users!
This is the announcement for those who use concox, coban and xexun devices with flespi.
We made a refactoring of engine ignition status parameters parsing, and for these protocols the following changes in parameters names happened:
concox:
acc.status becomes engine.ignition.status
coban and xexun:
acc.event becomes engine.ignition.status
Both old and new parameters are registered now to allow you to apply corresponding changes in your applications.
Old parameters will be removed on Thursday, 18th of July.
If you have any questions, please contact us in the chat embedded in flespi.io panel.
This is the announcement for those who use concox, coban and xexun devices with flespi.
We made a refactoring of engine ignition status parameters parsing, and for these protocols the following changes in parameters names happened:
concox:
acc.status becomes engine.ignition.status
coban and xexun:
acc.event becomes engine.ignition.status
Both old and new parameters are registered now to allow you to apply corresponding changes in your applications.
Old parameters will be removed on Thursday, 18th of July.
If you have any questions, please contact us in the chat embedded in flespi.io panel.
downtime started, error: failed to receive ACK from server for WialonIPS message
Dear flespi users,
We have conducted a regular platform update. The recent downtime was caused by a pure coincidence - two out of three NOC nodes detected the unavailability. Sorry for the inconvenience. Everything is stable.
We have conducted a regular platform update. The recent downtime was caused by a pure coincidence - two out of three NOC nodes detected the unavailability. Sorry for the inconvenience. Everything is stable.
Dear flespi users!
In the next minutes we will install an update which will add standard fields "sms_login" and "sms_password" to configuration object in devices, which type requires such authentication data to be presented in SMS messages.
After adding such fields we will automatically migrate passwords from the device's settings called "Device Password for SMS commands", "SMS Password", "SMS Authentication" and so on to appropriate device configuration fields, and finally remove specified settings from devices.
If you have any questions, please contact us in the chat embedded in the flespi.io panel.
In the next minutes we will install an update which will add standard fields "sms_login" and "sms_password" to configuration object in devices, which type requires such authentication data to be presented in SMS messages.
After adding such fields we will automatically migrate passwords from the device's settings called "Device Password for SMS commands", "SMS Password", "SMS Authentication" and so on to appropriate device configuration fields, and finally remove specified settings from devices.
If you have any questions, please contact us in the chat embedded in the flespi.io panel.
Dear flespi users!
Next Thursday, July 25 we will install update bringing a small change to our registry level REST API.
We believe the parameter "ttl" of the REST API for changing device settings ( PUT /devices/{dev-selector}/settings/{sett-selector} ) is not used by anyone, so we will delete it to make our API cleaner.
If you have any questions, please contact us in the chat embedded in the flespi.io panel.
Next Thursday, July 25 we will install update bringing a small change to our registry level REST API.
We believe the parameter "ttl" of the REST API for changing device settings ( PUT /devices/{dev-selector}/settings/{sett-selector} ) is not used by anyone, so we will delete it to make our API cleaner.
If you have any questions, please contact us in the chat embedded in the flespi.io panel.
Dear flespi users!
The update to our data parsing subsystem installed yesterday, July 22 at 8:30 UTC caused an issue with CalAmp devices data parsing. The messages received from your CalAmp devices were registered in flespi with zero coordinates ("position.latitude" and "position.longitude" parameters) for several hours.
The issue was caused by the rounding error of very small numbers used to calculate CalAmp devices position in our data parsing subsystem.
The patch installed on July 22 at 13:34 UTC fixed this issue.
We deeply apologize for the loss of positional data. We will make every effort to avoid this in the future.
If you have any questions, please contact us in the chat embedded in the flespi.io panel.
The update to our data parsing subsystem installed yesterday, July 22 at 8:30 UTC caused an issue with CalAmp devices data parsing. The messages received from your CalAmp devices were registered in flespi with zero coordinates ("position.latitude" and "position.longitude" parameters) for several hours.
The issue was caused by the rounding error of very small numbers used to calculate CalAmp devices position in our data parsing subsystem.
The patch installed on July 22 at 13:34 UTC fixed this issue.
We deeply apologize for the loss of positional data. We will make every effort to avoid this in the future.
If you have any questions, please contact us in the chat embedded in the flespi.io panel.
Dear flespi users!
Today, after 12 pm UTC we will install an update removing the "ident" and "phone" parameters from default REST API fields of the devices. Also, our platform will start adding an error message to the response if you keep using those deprecated fields in the PUT and POST requests. Those fields will be also deleted from the flespi/state/gw/devices/+/{ident,phone} MQTT retained topics.
The old streams subscriptions API will also be marked as deprecated and will emit an error message if you keep using it.
Nevertheless, all listed REST API will work until September 4, 2019.
Please refer to this article for more details: https://flespi.com/blog/sync-up-with-changes-in-the-flespi-device-api
If you have any questions, please contact us in the chat embedded in the flespi.io panel.
Today, after 12 pm UTC we will install an update removing the "ident" and "phone" parameters from default REST API fields of the devices. Also, our platform will start adding an error message to the response if you keep using those deprecated fields in the PUT and POST requests. Those fields will be also deleted from the flespi/state/gw/devices/+/{ident,phone} MQTT retained topics.
The old streams subscriptions API will also be marked as deprecated and will emit an error message if you keep using it.
Nevertheless, all listed REST API will work until September 4, 2019.
Please refer to this article for more details: https://flespi.com/blog/sync-up-with-changes-in-the-flespi-device-api
If you have any questions, please contact us in the chat embedded in the flespi.io panel.
Flespi
Sync up with changes in the flespi device API
Novelties in working with flespi devices and when you should switch to the updated API.
Dear flespi users!
Today we are going to patch telematics database. There are no changes for users and we do not expect problems or downtime.
Today we are going to patch telematics database. There are no changes for users and we do not expect problems or downtime.
Dear Flespi Users!
The patch has been applied. Downtime hit the telematics gateway but the rest of the systems worked normally.
The patch has been applied. Downtime hit the telematics gateway but the rest of the systems worked normally.