One thin you need to keep in mind is that Gluu Server is mostly designed to interact with web applications. If your intention is to, for example, create a dedicated service handling authentication for your users and a central point of distributing your users' personal data, which then will be used by your devices (for example, their web UI will be sending users to your Gluu Server for authentication and will be using it as a source of their personal attributes) - you are on the right track. With UMA you could delegate the process of making auhtorization decision to Gluu as well.
But in the end, it's your device which must be capable to interact with Gluu Server using one of the supported protocols, and then enforce some access policies based on the data received from it. This will be your part of the responsibility to implement or configure. We can't be aware of what kind of devices they are, or what kind of embeded software they use.
There are a few packages which can be used to add OpenID Connect or UMA support for your app. Gluu offers one as well, called [oxd server](https://gluu.org/docs/oxd/220.127.116.11/) (it's a paid solution). It's hard to suggest something specific without knowing all the details.