Fórum OpenRemote

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

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 1 post - 1 participant Read full topic

The fleet management custom project has been updated to 1.30.0 ! Make sure to read the release notes, as we move forward to the latest Keycloak release.

Good afternoon @Ankou , I’ve created a new fleet management release ! It includes the fix you mentioned. Make sure to read the release notes. Thanks for letting me know of the issue, let me know if it’s still there.

The new release 1.30.0 is out! Note that you need to update the identity service! Sorry to have missed notifying you about the last four releases

The new release 1.30.0 is out! Note that you need to update the identity service! Sorry to have missed notifying you about the last four releases 1 post - 1 participant Read full topic

Feel free to check your DMs!