-
Notifications
You must be signed in to change notification settings - Fork 10.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create node for BlueIris api #2555
Create node for BlueIris api #2555
Conversation
Implement status and camlist operations
Disable lint for response types
Hello, does anyone have any feedback about this PR? Thanks. |
Hey @hugo-ma-alves, Thanks for the contribution, We have now created a Community Node Repository which is our preferred method for new node submissions. Once a node has been published to the Community Node Repository users will be able to install the node from their n8n interface and will be able to use your node quicker, You will also be able to update the node as needed without needing to wait for the review process. In the future we may reach out to you about including your node in our main release, But for now I am going to close this PR. You can find more information in the links below, If you have any questions about this or need any help let us know. Building Community Nodes: https://docs.n8n.io/integrations/community-nodes/build-community-nodes/ |
This PR contains the base integration with the BlueIris API. The API details can be consulted on the software manual here, page 223.
BlueIris is a video management software for cctv cameras. The provided api is useful for monitoring purposes. Currently on my n8n workflow I have to create several nodes to fetch the necessary data. This node tries to solve that problem by encapsulating the login process and the operation invocation in a single node.
I felt the need to do this encapsulation because the login process on this API is a bit cumbersome, it requires an initial request to create a session, then we have to calculate a hash of that sessionid plus the username:password, send that hash to the api again and only then we can start to invoke the api operations.
Although this PR is still a work in progress I don't plan to implement all of the operations provided by the API. I prefer to start with the implementation of just 2 operations, and later i can implement the remaining if they are needed.
I'm waiting for your feedback
thanks