- Edited
Our AI assistant, a.k.a. codi, also deserves its own changelog thread.
Especially after the publication of flespi roadmap 2024, where we highlighted a focus on the application of AI tech in our telematics services.
Here, we accumulate changes in codi's architecture and post updates to its capabilities as soon as they are integrated.
The list with actual codi capabilities:
- It can support you answering any flespi-related question loaded with the knowledge published in our comprehensive Knowledge Base and 7 year old Blog.
- It can generate code for your flespi-related API calls in any language, consult on flespi REST API, its structure and parameters to use.
- It can generate you PVM code to transform message parameters and parse binary and textual payloads upon your request. You may supply example in your code of choice and it will try to provide you with corresponding PVM code.
- It can generate flespi expressions for you upon request.
- It can consult you on the integrated protocols, devices and explain the meaning and protocol-specific source for any message parameter within some protocol.
- It can show you how to control device remotely, which API calls to use and how to correctly construct command API call for your specific device.
- It can help you to troubleshoot and diagnose what is wrong and propose changes in the configuration of devices, channels, streams, calculators, plugins and webhooks that you created.
- It can navigate you through parameters reported by the particular device (telemetry).
- It can assist you with your account usage and limitations or suggest how to save money on your flespi bill.
- It can consult you on the device configuration, remote management, peripheral usage for hardware produced by Teltonika, Ruptela, Xirgo, Galileosky, Suntech, Calamp, Howen, few most popular device models by Queclink, Jimi Iot(Concox), Topflytech and some other brands. That knowledge is based on the information from official device manuals.