Add a websocket listener for the new Unfi Door Access Api

[ReziioAdmin]

Hi
I am hoping that you may be able to add a new node (or perhaps just add a Bearer authorization option to the existing node) to take advantage of the Unfi door access Api. (https://core-config-gfoz.uid.alpha.ui.com/configs/unifi-access/api_reference.pdf).

This Api requires a specific Api key to be passed and I have not been able to find anyway to do this using the standard Node-red websocket

[crxporter]

Woah! Unifi actually published an API document?!

Yeah with that it shouldn't be much trouble to set up. @marcus-j-davies - any thoughts on how to add a special API key for locks? Looks like it needs to send an extra header with 'Authorization: Bearer <apiKeyHere>'

[crxporter]

is there a way to disconnect the websocket from Unfi without just deleting the node ?

As it's built, no. And deleting it probably doesn't do a true "close web socket" with Unifi but just makes the client look like it's gone offline.

The JavaScript ws package of course has this functionality to close connections... but our example today is more a proof of concept than something to deploy long term. You'd likely want a more robust setup (meaning basing a new node off this concept) for high importance situations, this is just a start.

[crxporter]

Odd that the Unifi node crashed. If I was you, I would probably use the official API from Unifi for this (and whenever an "official" option exists)

[ReziioAdmin]

Yup. I see that. And, what I have experienced with NodeRed (and running the awesome Marcus zwave-js nodes) is that the slightest error of what versions of what xxx.js nodes are running can cause untold issues.
But, this is a great start and my thanks to you both for the work done. I am going to deploy the listener node to a low risk operational site and will give you feedback on how that goes

[marcus-j-davies]

One question - is there a way to disconnect the websocket from Unfi without just deleting the node ?

The subflow actually does cleanly close when deleting the node from the flow.

@crxporter
You can probably refactor the subflow, to add an input.
and react to it on the "On Message" block, but it won't be able to be restored after this, until your bring in a new instance of the node (I don't think anyway)

{
    topic: 'control',
    payload: 'disconnect'
}

[crxporter]

won't be able to be restored after this

Restoring would just require another instance of the connection bits from On Start if a message gets sent like

{
    "topic": "control",
    "payload": "reconnect"
}