rest980 VS Strapi

My Roomba is on a VLAN without internet access and is controlled via rest980[1] running in a container. It has a basic but functional web interface. Valentudo is probably nicer but I opted to trade that for the broad iRobot install base and spare part/consumable availability.

1. https://github.com/koalazak/rest980

Im still new to api’s and have been trying to connect to my roomba using one. I have firmware Version 22.29.3 and have been trying to connect to the roombas rest api using the rest980 on github. When I call the api, I get the software version of the wrapper in json form as a response, so the server is up. But when I try send a command to the roomba, I get an Endpoint not found error.

Basically, title. Would it be possible to do this using other software? like rest980?

On all internet connected robots (600, 800, 900, e5, i7/i7+, and S9 / S9+) you can use the Dorita980 or Rest980 SDKs to pull the robot's state, which includes all of the battery information (voltage, cycles, status, authenticity, etc.)

Strapi provides a centralized data managing platform. This makes it easier to organize, update, and maintain the FAQ data. It also automatically generates a RESTful API for accessing the content stored in its database.

https://prisma.io is popular as I understand it. I've been trying out https://strapi.io the last week and am thoroughly impressed.

They both do much more than build queries. One big thing both do is automate database migration calculations. Strapi goes further and gives you a CMS and admin UI on top, as well as doing a lot more of the complex query building from a json object. Both still require a fundamental understanding of the data model and SQL

As of April 2024, Strapi's GitHub repository has garnered 59.7k stars and 7.5k forks, showcasing its widespread adoption. The project has also secured a substantial $45+ million in funding, cementing its position as a prominent player in the headless CMS space.

const pages = await client.GET("/pages", { params: { query: { filters: { // @ts-ignore - openapi generated from strapi results in Record // https://github.com/strapi/strapi/issues/19644 path: { $eq: path, }, }, // @ts-ignore populate: { blocks: { populate: "*" }, }, }, }, });

On a side note. Where do all these endpoints come from? Strapi is open source. We can read the source code. All these endpoint come from the Users and permissions plugin. So, if we go to Strapi on github and browse around the files a bit eventually you will find the auth.js file that contains all of the routes. You can also find the Strapi controllers in there if you're interested.

Strapi

Strapi: The Code Anarchist

Strapi - Open source Node.js Headless CMS 🚀