flespi noc

@flespi_noc Like 0
Is this your channel? Confirm ownership for additional features

flespi platform NOC
Channel's geo & Language
not specified, English


Channel's geo
not specified
Channel language
English
Category
Technologies
Added to index
13.04.2019 16:13
advertising
Adepts. Blockchain and cryptocurrency
Wanna know all the crypto trends, news and events? np!
Telegram Analytics
Subscribe to stay informed about TGStat news.
TGAlertsBot
Monitoring of keywords in channels and chats
61
members
~72
avg post reach
~14
daily reach
~16
posts per month
118%
ERR %
0.03
citation index
Recent posts
Deleted
With mentions
Forwards
flespi noc 7 Aug, 10:52
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.
Read more
flespi noc 23 Jul, 11:30
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.
Read more
flespi noc 18 Jul, 15:13
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.
Read more
flespi noc 17 Jul, 13:28
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.
Read more
flespi noc 12 Jul, 17:15
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.
flespi noc 12 Jul, 16:55
downtime ended, period: 7 seconds
flespi noc 12 Jul, 16:55
downtime started, error: failed to receive ACK from server for WialonIPS message
flespi noc 11 Jul, 14:18
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.
Read more
flespi noc 10 Jul, 12:06
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.
flespi noc 4 Jul, 16:25
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.
flespi noc 3 Jul, 14:59
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.
Read more
flespi noc 1 Jul, 18:13
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.
Read more
flespi noc 25 Jun, 11:15
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
Read more
flespi noc 24 Jun, 13:23
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!
Read more
flespi noc 21 May, 11:01
downtime ended, period: 112 seconds
flespi noc 21 May, 10:59
downtime started, error: GET channel info failed
flespi noc 21 May, 09:24
Dear flespi users!

As a part of our regular infrastructure maintenance we plan to upgrade to latest kernel and reboot our edge routers today.
We do not expect any troubles upon this procedure, except MQTT/HTTP connections resets within few seconds may occur.
Short service interruptions can be observed two times - first time when we migrate gateway function to secondary router and second time when we will migrate it back to primary router.

Sorry for any inconveniences.
Read more
flespi noc 24 Apr, 11:56
Dear flespi users!

Our MQTT Broker is currently having temporary connection resets for some sessions. You may experience reconnects.
We will fix this situation in a minute.

Sorry for any inconveniences.
flespi noc 19 Apr, 09:55
Dear flespi users!

We have important notification for those who are using tokens with ACL to consume data from flespi telematics hub via MQTT Broker.

According to flespi ACL specification all access to flespi items should be controlled directly via special ACL rules. But initially there was a feature that made possible to specify in token ACE rule MQTT topic 'flespi/#' with subscribe action and receive flespi related messages.

We decided to cleanup the architecture of the platform and yesterday we have installed the update that closed that bug/feature.

So what you need to check is to ensure that if you are using ACL tokens that access to flespi related item is not via MQTT topic ACE entries, but via flespi ACE entries. Or if this sounds too complex please just check that via your MQTT sessions(if any) you still correctly receive data you expect. That is.

Sorry for late notification, yesterday we were too busy by tuning the platform for initial phase (6K devices, 5K subaccounts) of large (150K devices and 100K subaccounts) project on the platform. And if hosting 200K of the devices is totally OK for us we were not really ready to host thousands of subaccounts. But we managed with that, as usual. You can monitor live the status of the platform here: https://flespi.com/status

Have a great Friday and sunny weekend!
Read more
flespi noc 9 Apr, 10:47
Dear flespi users!

As a final stage of network split process that occured this Sunday our uplink provider will perform routing announcement update, making configuration permanent. The update will occur at 08:00 UTC, e.g. scheduled in next 15 minutes.
We do not expect any network interruptions due to this update and notify you just in case. Our bots are keeping eye on the connectivity 24/7, even on holidays and Christmas night.

Have a good day!
Read more