ux4iot
  • Introduction
  • Quickstart
  • Concepts
  • How Ux4iot works
  • REST API Reference
  • Configuration Options
  • Create your ux4iot Instance
  • EventHub / IoTHub
    • Configure your existing IoT Hub
    • Create IoT Hub and linked ux4iot
    • Using a separate Event Hub
  • ux4iot-react
    • Initialization
    • Hooks
    • Grant Request Function
    • Tutorial using create-react-app
  • Implementing your custom security backend
    • Introduction
    • Security Backend
    • Security Backend Example - Azure Function
    • ux4iot-admin-node
  • Resources
    • Pricing
    • Performance
    • Limitations
    • Known Bugs & Nice to know's
    • Changelog
  • Made with ❤️ at Device Insight
Powered by GitBook
On this page
  • How can the connection string and websocket URL be retrieved from az cli?
  • Failed to publish event hub message ... "$cbs" endpoint timed out

Was this helpful?

  1. Resources

Known Bugs & Nice to know's

How can the connection string and websocket URL be retrieved from az cli?

Here is an example for the websocket URL:

# ID of your Azure subscription
SUB="..."
# Name of the resource group containing the ux4iot instance
RG="..."
# Name of the ux4iot instance
NAME="ux4iot"

RESOURCE_ID="/subscriptions/$SUB/resourceGroups/$RG/providers/Microsoft.Solutions/applications/$NAME"

az resource show \
  --ids $RESOURCE_ID/customwebsocketUrls/url \
  --api-version 2018-09-01-preview \
  --query properties.value \
  --output tsv

Here is an example for the primary admin connection string

# ID of your Azure subscription
SUB="..."
# Name of the resource group containing the ux4iot instance
RG="..."
# Name of the ux4iot instance
NAME="ux4iot"

RESOURCE_ID="/subscriptions/$SUB/resourceGroups/$RG/providers/Microsoft.Solutions/applications/$NAME"

az resource show \
  --ids $RESOURCE_ID/customsharedAccessPolicies/Primary \
  --api-version 2018-09-01-preview \
  --query properties.connectionString \
  --output tsv

You can quite easily find the RESOURCE_ID of the ux4iot instance in the Azure portal if you navigate to the ux4iot instance and copy the highlighted section of the URL:

Failed to publish event hub message ... "$cbs" endpoint timed out

This is a bug that was communicated to the azure support, and that has still not been resolved yet. It occurred when subscribing directly to an IoTHub and caused message loss. We don't know where it comes from or what the issue is. When this happens to you, try to deploy an EventHub and redirect the messages from your IoTHub there. Then let your ux4iot use the connection string of the EventHub to subscribe to messages. You will need to restart your ux4iot service after a successful deployment. This is now possible in the managed application mainscreen on the top icon bar.

PreviousLimitationsNextChangelog

Last updated 1 year ago

Was this helpful?