Auto-detection of Schema

[joepavitt]

We've proposed (in #3445) the idea of offering a Schema Builder, but as pointed out by customers we've discussed this with, this would be a significant undertaking to flesh out and define for full scale factory ecosystems, etc.

Alternatively, we could provide an "auto-detection" option, whereby, based on values we're seeing come into different topics, we could try to offer proposals for schemas, e.g. payloads that are email, number, string, array, or whichever definitions we decide upon.

Differentiation here is important for:

• FlowFuse Broker
• Bring Your Own Broker

We then have two levels of Schema:

• Topic Hierarchy
• Payload Structure

Will also pair with #4908 whereby any schema we "store" will be structured as to work with Async API

Tasks

Preview Give feedback

1. Design Work: Auto-detection of Schema #4963
   design
   
2. Options for auto-refreshing the hierarchy view #5036
   research

Topics

Preview Give feedback

1. Create Async API schema from our own broker's topic hierarchy #4919
   2 of 2
   area:api +1
   
2. Expose generated Async API schema docs via FlowFuse UI #5013
   area:api +2
   
3. Monitor third-party brokerd to generate topic hierarchy schemas

Payloads

Preview Give feedback

1. Add simple JSONSchema generator mqtt-schema-agent#3
2. Establish the structure/schema of an incoming messages on MQTT #5032
   area:api +2
   
3. "Smart" Payload Structure Suggestions #5125
   area:frontend +3
   

Available To

• Enterprise Tier Customers Only

[joepavitt]

@hardillb for the first part of this "Monitor the latest message received on each topic" - what are are (technical) options here, other than subscribe to /#?

[hardillb]

None

And it's # NOT /# these are very different things

[joepavitt]

Okay, so # subscription it will need to be

[joepavitt]

#5125 is the last outstanding item here, core work has been delivered/

[joepavitt]

Calling this work closed out as major items have been delivered