This repository aims to promote the development of a multi-vendor management platform for CPEs and IoTs. Any device that follows the TR-369 protocol can be managed. The main objective is to facilitate and unify device management, which generates countless benefits for the end user and service providers, suppressing the demands that today's technologies require: device interconnection, data collection, speed, availability and more.
+ +If you'd like to know how to donate above Github Sponsors values, start a partnership or somehow to contribute to the project, email leandro@oktopustr369.com, every contribution is welcome, and the resources will help the project to move on. Also, if your company uses this project and you'd like your logo to appear up here, contact us. + +-------------------------------------------------------------------------------------------------------------------------------------------------------- + +
+ Our solution has an open-source software license, meaning you can modify/study the code and use it for free. You can perform all the configurations, allocate servers, and set it up on your network with the classic "do it yourself" approach, or save time and money: contact us for a quote and get commercial support. +
+Contact leandro@oktopustr369.com via email and get a quote.
++user@user-laptop:~$ cd oktopus/deploy/compose +user@user-laptop:~/oktopus/deploy/compose$ docker compose up ++
user@user-laptop:~$ cd oktopus/backend/services/mqtt/ && go run cmd/main.go -redis "127.0.0.1:6379"+
+user@user-laptop:~$ cd oktopus/backend/services/controller/ && go run cmd/oktopus/main.go -u root -P root -mongo "mongodb://127.0.0.1:27017"+
+user@user-laptop:~$ cd oktopus/backend/services/socketio && npm i && npm start+
+user@user-laptop:~$ cd oktopus/backend/services/ws && go run cmd/main.go+
+user@user-laptop:~$ cd oktopus/frontend && npm i && npm run dev+
+ P.S: This guide in here is too simple, and at the same time hard, because you have to compile obuspa C code yourself, for an easier, more complete and real-world simulation of devices you might use Oktopus TR-369 Agent Simulator. +
+Follow the instructions to build obuspa at their repo QUICK_START_GUIDE.md and remember to define 'INCLUDE_PROGRAMMATIC_FACTORY_RESET' at 'vendor_defs.h' inside src/vendor folder, also advice you to build it with make tool.
+You can customize 'oktopus-mqtt-obuspa.txt' accordingly to your needs, there you can change broker address, client password, and etc. '-i' option defines the interface your usp packets will go through, in this case it's localhost, also keep in mind that after you run obuspa if you made a change to 'oktopus-mqtt-obuspa.txt' and want it to take effect you must delete '/usr/local/var/obuspa/usp.db' file before running the agent again (docs provide you other methods to do it too).'-r' option defines the config file you want the agent to use.
+Run MQTT agent:
+user@user-laptop:~/oktopus$ obuspa -p -v 4 -r agent/oktopus-mqtt-obuspa.txt -i lo+
Run Websockets agent:
+user@user-laptop:~/oktopus$ obuspa -p -v 4 -r agent/oktopus-websockets-obuspa.txt -i lo+
Obuspa has a lot of info and docs at their repo, which shows you many options to set your environment and customize agent to your embedded project. This basic agent has the purpose to test oktopus connection and shows an idea of how it's like with true devices, although with those, you're able to explore much more parameters and execute lots of configurations. Obuspa has default parameters and mocked info:
++ The project goals are organized with milestones that have a due date, just like a sprint. Those issues grouped in milestones are done and have their status updated in a kanban board. +
+Are you going to use our project in your company? would like to talk about TR-369 and IoT management, we're online on Slack.
+ +---------------------------------------------------------------------------------------------------------------------------------------------------------user@user-laptop:~$ cd oktopus/deploy/compose -user@user-laptop:~/oktopus/deploy/compose$ docker compose up --
user@user-laptop:~$ cd oktopus/backend/services/mqtt/ && go run cmd/main.go -redis "127.0.0.1:6379"-
-user@user-laptop:~$ cd oktopus/backend/services/controller/ && go run cmd/oktopus/main.go -u root -P root -mongo "mongodb://127.0.0.1:27017"-
-user@user-laptop:~$ cd oktopus/backend/services/socketio && npm i && npm start-
-user@user-laptop:~$ cd oktopus/backend/services/ws && go run cmd/main.go-
-user@user-laptop:~$ cd oktopus/frontend && npm i && npm run dev-
- P.S: This guide in here is too simple, and at the same time hard, because you have to compile obuspa C code yourself, for an easier, more complete and real-world simulation of devices you might use Oktopus TR-369 Agent Simulator. -
-Follow the instructions to build obuspa at their repo QUICK_START_GUIDE.md and remember to define 'INCLUDE_PROGRAMMATIC_FACTORY_RESET' at 'vendor_defs.h' inside src/vendor folder, also advice you to build it with make tool.
-You can customize 'oktopus-mqtt-obuspa.txt' accordingly to your needs, there you can change broker address, client password, and etc. '-i' option defines the interface your usp packets will go through, in this case it's localhost, also keep in mind that after you run obuspa if you made a change to 'oktopus-mqtt-obuspa.txt' and want it to take effect you must delete '/usr/local/var/obuspa/usp.db' file before running the agent again (docs provide you other methods to do it too).'-r' option defines the config file you want the agent to use.
-Run MQTT agent:
-user@user-laptop:~/oktopus$ obuspa -p -v 4 -r agent/oktopus-mqtt-obuspa.txt -i lo-
Run Websockets agent:
-user@user-laptop:~/oktopus$ obuspa -p -v 4 -r agent/oktopus-websockets-obuspa.txt -i lo-
Obuspa has a lot of info and docs at their repo, which shows you many options to set your environment and customize agent to your embedded project. This basic agent has the purpose to test oktopus connection and shows an idea of how it's like with true devices, although with those, you're able to explore much more parameters and execute lots of configurations. Obuspa has default parameters and mocked info:
-If you'd like to know how to donate above Github Sponsors values, start a partnership or somehow to contribute to the project, email leandro@oktopustr369.com, every contribution is welcome, and the resources will help the project to move on. Also, if your company uses this project and you'd like your logo to appear up here, contact us. - --------------------------------------------------------------------------------------------------------------------------------------------------------- - -
- Our solution has an open-source software license, meaning you can modify/study the code and use it for free. You can perform all the configurations, allocate servers, and set it up on your network with the classic "do it yourself" approach, or save time and money: contact us for a quote and get commercial support. -
-Contact leandro@oktopustr369.com via email and get a quote.
-- The project goals are organized with milestones that have a due date, just like a sprint. Those issues grouped in milestones are done and have their status updated in a kanban board. -
-Are you going to use our project in your company? would like to talk about TR-369 and IoT management, we're online on Slack.
-If you are interested in internal information about the team and our intentions, visit our Wiki. [DEPRECATED]
- --------------------------------------------------------------------------------------------------------------------------------------------------------- -Bibliographic sources: MU-461.pdf, TR-369.html, USP Training Session SlidesTR-369.html