SOT
    • Introduction
    • Concepts
      • Operating principle
      • Machine interfaces
      • Supported protocols
    • Getting started
    • How-to
      • Send data
    • Operations manual
      • Overview
      • System architecture and interfaces
        • Technical context and deployment view
        • Machine interface
        • PPMP
        • OPP
        • Rexroth Tightening
        • Dynamic multi-tenancy
        • AMQP
        • Kafka
        • MQTT
        • Unknown Device handling
        • Watchdog handling
      • System requirements
        • connectivity/connectivity-service:1
        • connectivity/connectivity-webui-service:1
      • Migration from previous versions
        • Tenant ID migration guide
        • Migration to 2.0.0+
        • Migration to 2.1.0+
      • Setup and configuration
        • Logging
        • Helm configuration
        • Messaging (inbound)
      • Start and shutdown
      • Regular operations
      • Failure handling
        • Unknown device handling
      • Logging and monitoring
      • Known limitations
        • Rexroth Tightening
        • Unknown Device handling
        • Amqp
        • Kafka
    • Troubleshooting
    • API documentation
    • Glossary
Information Router
  • Smart Operations Toolkit
    • Deviation Processor
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Process Quality
    • AI Services
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
  • Enterprise & Shopfloor Integration
    • Information Router
    • Master Data Management

SOT Learning Portal

  • Information Router
  • Operations manual
  • Known limitations
  • Unknown Device handling

Unknown Device handling

This functionality is currently only supported in single instance deployments.
If the device created event doesn’t reach Information Router (because of messaging infrasturcture or network issues), the only way to resume forwarding for internally blocked devices is to restart Information Router.

Contents

© Robert Bosch Manufacturing Solutions GmbH 2023-2026, all rights reserved

Changelog Corporate information Legal notice Data protection notice Third party licenses