Skip to content

How to run meshcli application ? #137

@pjp009

Description

@pjp009

python-bluetooth-mesh/bluetooth_mesh/apps/meshcli.py application exist.
but I have no idea how to build and run the application.
Suppose if I'm run command meshcli -h then get the below instructions :

       Mesh CLI
        Usage:
            meshcli [options] [<command>...]
            meshcli -h | --help | --version

        Options:
            -l --login <login>             User login to platform service (email)
            -p --password <password>       User password to platform service (!unsecured!)
            -n --project <project>         Project name or id to be loaded from platform

            --partner <partner>            Partner identifier [default: silvair]
            --env <environment>            Environment: dev,preprod or prod [default: preprod]

            --auth0-client-id <client_id>  Auth0 client id
            --auth0-secret <secret>        Auth0 secret (!unsecured!)
            --auth0-domain <domain>        Auth0 domain name
            --serial-number <serial_num>   Gateway serial number

            -d --debug
            -h --help                      Show this help message and exit
            --version                      Show version and exit

But I didn't find any following MeshCommandLine commands on the console :

COMMANDS = [
        HelpCommand,
        LsCommand,
        AttentionCommand,
        SceneCommand,
        UptimeCommand,
        FaultCommand,
        VersionCommand,
        IvIndexCommand,
        ArapCommand,
        StatsCommand,
        AppVersionCommand,
        LightCommand,
        GenericOnCommand,
        GenericOffCommand,
        CompositionDataCommand,
        MorseCommand,
        NetworkTransmissionCommand,
        TtlCommand,
        RelayCommand,
        GatewayConfigurationCommand,
        GatewayPacketsCommand,
        AclCommand,
        PublicationCommand,
        SubscribeCommand,
        AddSubscriptionCommand,
        BindAppKeyCommand,
        UnsubscribeCommand,
        LightExtendedControllerCommand,
        LightRangeCommand,
        SensorCommand,
        TimeGetCommand,
        TimeCurrentSetCommand,
        TimeRoleGetCommand,
        TimeRoleSetCommand,
    ]

kindly provide me with the steps of the demo application. So, I can run basic applications to understand the dbus_next.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions