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
Recent update
26.05.2019 11:38
59
members
~46
avg post reach
~10
daily reach
~4
posts per week
78%
ERR %
0.03
citation index
Recent posts
Deleted
With mentions
Forwards
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
flespi noc 7 Apr, 13:57
The most critical part of network split is finished now. Minor works should not affect the platform accessability, but we never know what can happend.
Still we hope everything is finished already, and would like to wish you to relax lazy Sunday's afternoon.

Our NOC bots will keep an eye on the platform connectivity and notify you in case of any problems immediately.

With regards,
Your flespi team
Read more
flespi noc 7 Apr, 13:10
downtime ended, period: 844 seconds
flespi noc 7 Apr, 12:56
downtime started, error: GET channel info failed
flespi noc 7 Apr, 10:55
downtime ended, period: 1043 seconds
flespi noc 7 Apr, 10:37
downtime started, error: GET channel info failed
flespi noc 7 Apr, 10:09
Dear flespi users!

Today we are starting the planned datacenter maintenance.
As we said before, there will be a significant change in our networking configuration,
so we are expecting that flespi platform will be unaccessible for some time.
The expected offline-time will be 5-10 minutes.

The network state changes and platform accessibility will be reported by our automated bot here.

Sorry for any inconveniences.
Read more
flespi noc 4 Apr, 16:30
Dear flespi users!

The last downtime was caused by network connectivity issue on our datacenter uplink provider.
Everything is okay now.
Sorry for any inconveniences.
flespi noc 4 Apr, 16:19
downtime ended, period: 51 seconds
flespi noc 4 Apr, 16:19
downtime started, error: GET channel info failed
flespi noc 4 Apr, 13:09
Dear flespi users!

At Sunday, April 7 about 07:00 UTC a planned datacenter maintenance will be performed.
There will be a significant change in our networking configuration, so we are expecting that flespi platform will be unaccessible for some time.
The expected offline-time will be 5-10 minutes.

We will post additional notification to this channel just before the operations.
Sorry for any inconveniences.
Read more
flespi noc 14 Mar, 11:24
Dear flespi users! Due to the our customers requests the update of Wialon IPS and Wialon Retranslator protocols is postponed to Monday 18, March, 12-00 GMT. The update will be done with no more notifications.
flespi noc 13 Mar, 11:07
Dear flespi users!
We are on the way of updating the Wialon Retranslator protocol. Several parameters with "custom." prefix will be renamed to standard flespi notation. For the next 24 hours, both parameters will be stored. On 14, March at 8-00 GMT these "custom." prefixed parameters will be removed. If you want us to delay the update - please, contact us within the specified period. The list of renaming parameters is the same as for previous NOC message (update for Wialon IPS).
Read more
flespi noc 12 Mar, 11:00
Dear flespi users!
We are on the way of updating the Wialon IPS protocol. Several parameters with "custom." prefix will be renamed to standard flespi notation. For the next 2 days, both parameters will be stored. On 14, March at 8-00 GMT "custom." prefixed parameters will be removed. If you want us to delay the update - please, contact us within the specified period. Following is the list of parameters to be renamed:
custom.battery => battery.level
custom.pwr_int => battery.voltage
custom.pwr_ext => external.powersource.voltage
custom.gsm => gsm.signal.level
custom.gsm_cell => gsm.cellid
custom.hdop => position.hdop
custom.mileage => vehicle.mileage
custom.ibutton => ibutton.code
custom.engine_temp => can.engine.temperature
custom.cool_temp => can.engine.coolant.temperature
custom.fuel_consumption => fuel.consumed
custom.fuel_level => fuel.level
custom.fuel_volume => can.fuel.volume
custom.engine_hours => engine.motorhours
custom.taho_speed => tacho.position.speed
custom.axis_weight => can.axle.weight
custom.engine_rpm => engine.rpm
custom.oil_pressure => engine.oil.presure
custom.ign => engine.iginition.status
custom.sf_ver => software.version
custom.accel_x => x.acceleration
custom.accel_y => y.acceleration
custom.accel_z => z.acceleration
custom.accel_res => absolute.acceleration
custom.mсс => gsm.mcc
custom.mnс => gsm.mnc
custom.lac => gsm.lac
custom.cell_id => gsm.cellid
custom.hw_cfg_protocol_version => protocol.version
custom.hw_cfg_in_roaming => gsm.network.roaming.status
custom.avl_driver => ibutton.code
custom.touch_key => touch.memory.id
Read more
flespi noc 11 Mar, 10:01
Dear flespi users!

We have done a major refactoring on the flespi implementation of Teltonika protocols. The main change concerns the parsing of AVL ID parameters. Since the same AVL ID may have different values for different device types, now parsing of AVL ID parameters depends on the device type in your flespi account. If there is no device with specified ident registered and flespi is unable to determine its type, parameters common to all device types will be presented in normalized form (as it is now), but if parameter interpretation is dependent upon device type we will store it in raw form as custom parameter: "custom.param.".

So, in order to pass all the normalization logic to the flespi we recommend you to register Teltonika devices with corresponding ident and device type. In order to prevent data storage on the flespi you may set zero messages_ttl for them.

The change mostly concerns secondary parameters like CAN-data, temperature and accelerometer sensors, fuel, mileage, 1-Wire devices etc. General parameters like timestamps, digital and analogue inputs state, position information should not be affected.

If you want us to delay the update and get more details - contact us urgently. The update is scheduled for 11:00 UTC today. Please, review your Teltonika channels usage after the update and let us know in case something goes wrong.
Read more