Deployment Verifier

[tthiery]

When you build a user interface or something related, you expect the connected sensors, actors and hubs to follow a pre-defined model (which you then control by your UI).

var model = new DeploymentModelBuilder()
                 .AddHub<TechnicMediumHub>(hubBuilder => hubBuilder
                     .AddDevice<TechnicLinearMotor>(hub => hub.A)
                     .AddDevice<TechnicXlargeLinearMotor>()
                 )
                .Build();

var errors = model.Verify(protocol);

// or reactive

var errorObservable = protocol.VerifyObservable(model);

With errors being something like ..

class DeploymentError
{
    int ErrorCode;
    byte HubId;
    byte? PortId;
    string Message;
}

[tthiery]

• Initial verification on request
• Update README.md
• Observable verification stream (reacting on connecting and disconnecting devices)
• Verify Hub/System Type
• Verify "Any" device (e.g. for selective port discovery)
• Verify "Any" hub (e.g. for hub does not matter as long as motor is connected)
• Documentation
• re-work of protocol knowledge to include hubId
• Multi-Hub Verification

[tthiery]

• Multi Hub Validation is a non-goal since no hardware available.