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!
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!