Eclipse Hono

Multi-tenant device connectivity layer with MQTT, HTTP, AMQP and CoAP protocol adapters.

Provider
default
Category
Messaging
Properties · 5 set by this component
propertytypevaluesrequiredkind defaultthis component
commandAndControl · component propertyboolean—notrueinherited
deviceCountinteger—no—inherited
deviceProvisioningboolean—no—▸ true
deviceTwinboolean—no—▸ false
managedboolean—nofalse▸ false
messagesPerDayLimitinteger—no—inherited
multiTenant · component propertyboolean—notrueinherited
perDeviceIdentityboolean—notrue▸ true
protocolenummqtt | amqp | http | multi | lorawanno—▸ multi
Rules that apply · 0

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

No rule reads this kind yet. That is a gap, not a guarantee.
Use it in a design
nodes:
  - { id: "hono", component: "hono" }
Other IoT hub products · 21
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Eclipse Hono: multi-tenant device connectivity layer. The "Component View" describes MQTT, HTTP,
# AMQP and CoAP protocol adapters in front of a device registry that holds per-device credentials,
# an HTTP device management API for provisioning, and a Command Router for command and control.
# Hono routes telemetry to messaging infrastructure; it stores no device twin of its own.
schemaVersion: "1"
type: "component"
id: "hono"
kind: "iot-hub"
provider: "default"
docs: "https://eclipse.dev/hono/docs/architecture/component-view/"
defaults:
  protocol: "multi"
  perDeviceIdentity: true
  deviceProvisioning: true
  deviceTwin: false
  managed: false
properties:
  commandAndControl:
    type: "boolean"
    default: true
  multiTenant:
    type: "boolean"
    default: true

The same page as markdown, for an agent: /catalogue/components/hono.md