OpenRemote forum

I believe this has been resolved now as of release 1.30.0 , can you double check? GitHub Releases · openremote/openremote 100% open-source IoT Platform - Integrate your devices, add intelligence, build custom apps - openremote/openremote

This has been resolved as of release 1.30.0 GitHub Releases · openremote/openremote 100% open-source IoT Platform - Integrate your devices, add intelligence, build custom apps - openremote/openremote

Hi! First of all, welcome to the forum! You can look on the documentation website , which has plenty of information on how to auto provision a device through MQTT. docs.openremote.io Auto provisioning devices and users | OpenRemote Documentation OpenRemote offers functionality for automatic client and asset provisioning. If you build and distribute your own hardware devices, you can use this mechanism to have your devices automatically register and connect to OpenRemote.

Hi! There is indeed no support for x86-64-v2 because of the base ubi10 image we’re using. We’re looking into changing it for broader and better OS support, but it’s a lower priority for us. Do you have any recommendations? Feel free to open an issue and/or pull request if you’d like.

Hi all, I’m new to OpenRemote and plan to use for EMS related research. Just as a first start I want to customize the web UI, i.e. the map and colors, and add some assets. Regarding customizing the UI I get some mixed information from the documentation. I watched the video on whitelabeling openRemote, which seem to use a (manual) custom deployment, and it seems the documentaion ‘working on maps’ also assumes I have a custom deployment. On the other hand I see comments in the youtube video that customizing the UI can now also be done via the UI itself which indeed seem to work fine as well. I’m a bit puzzled now when and when not to use a custom deployment when I want to whitelabel my openremote instance. Can somebody shed a light on this? or point me to the right documentation? Thanks!

Hi all, I’m new to OpenRemote and plan to use for EMS related research. Just as a first start I want to customize the web UI, i.e. the map and colors, and add some assets. Regarding customizing the UI I get some mixed information from the documentation. I watched the video on whitelabeling openRemote, which seem to use a (manual) custom deployment, and it seems the documentaion ‘working on maps’ also assumes I have a custom deployment. On the other hand I see comments in the youtube video that customizing the UI can now also be done via the UI itself which indeed seem to work fine as well. I’m a bit puzzled now when and when not to use a custom deployment when I want to whitelabel my openremote instance. Can somebody shed a light on this? or point me to the right documentation? Thanks! 1 post - 1 participant Read full topic

I am deploying Central + Edge on a small home server (Debian 13, Intel Pentium Silver N6005). That CPU has SSE4.2 but no AVX2, so it is x86-64-v2 only. docker compose build of a manager image based on openremote/manager:1.29.0 fails with: Fatal glibc error: CPU does not support x86-64-v3 Hub layers show 1.29.0 (and 1.28.0-core) on ubi10-minimal / ubi10/openjdk-21-runtime. UBI 10’s glibc refuses to start Java on this machine. Mosquitto and Zigbee2MQTT are fine. Would you consider publishing manager (and Keycloak, if it is also UBI 10) for x86-64-v2, for example ubi9/openjdk-21-runtime? If the supported answer is “rebase the published image onto UBI 9 yourself”, that is useful to have in the docs as well. I can rebuild from source; I would rather stay on the official tags if a v2 image exists or is planned.

I am deploying Central + Edge on a small home server (Debian 13, Intel Pentium Silver N6005). That CPU has SSE4.2 but no AVX2, so it is x86-64-v2 only. docker compose build of a manager image based on openremote/manager:1.29.0 fails with: Fatal glibc error: CPU does not support x86-64-v3 Hub layers show 1.29.0 (and 1.28.0-core) on ubi10-minimal / ubi10/openjdk-21-runtime. UBI 10’s glibc refuses to start Java on this machine. Mosquitto and Zigbee2MQTT are fine. Would you consider publishing manager (and Keycloak, if it is also UBI 10) for x86-64-v2, for example ubi9/openjdk-21-runtime? If the supported answer is “rebase the published image onto UBI 9 yourself”, that is useful to have in the docs as well. I can rebuild from source; I would rather stay on the official tags if a v2 image exists or is planned. 1 post - 1 participant Read full topic

Hi all, I am exploring OpenRemote and looking for a solution that I can auto provision devices from AWS IoT Core MQTT. I am using Thingsboard for IoT management and I can achieve this by using Thingsboard IoT gateway or the AWS Integration in ThingsBoard PE. I setup the MQTT Agent but it seem not work the same way as Thingsboard IoT gateway. I am consider to move to OpenRemote so I am wondering if I can do the same setup in OpenRemote. In my setup, I use AWS IoT Core as the device ingress, and the PKI will be done in AWS IoT Core. The device then will be auto provisioned by mapping a field in payload to device name. Thank you all and appriaciate if oneany one can give me some idea to resolve this with OpenRemote