Skip to content

Why a sleep is needed after MQTTLibrary.Connect #33

Description

@alepinio

Hi!

I've found that messages published right after execution of MQTTLibrary.Subscribe get lost. So I've had to come up with this workaround

    MQTTLibrary.Connect      ${host}

    # FIXME
    Sleep    1s

    MQTTLibrary.Subscribe    ${topic}

This way, messages published right after MQTTLibrary.Subscribe can be retrieved with MQTT.Listen, but of course a sleep sucks.

Am I missing something about the library?


PS: maybe client connect isn't blocking enough? The client id is empty in the log messages print by MQTTLibrary.Connect:

mqtt

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions