feature/ch51186/usb-cloud-connection-status

[busticated]

Description

Adds particle usb cloud-status <deviceID> command to query the device via USB and return its cloud connection status: unknown, connecting, connected, disconnecting, disconnected (ch)

How to Test

run particle usb cloud-status --help and try out the command and options.

Related Issues / Discussions

particle-iot/particle-usb#24

Completeness

• User is totes amazing for contributing!
• Contributor has signed CLA
• Problem and solution clearly stated
• Tests have been provided
• Docs have been updated
• CI is passing

[busticated]

@sergeuz i don't think it's related to my changes as this isn't new behavior (though perhaps my updates make it worse) but i get IN control transfer failed: LIBUSB_TRANSFER_TIMED_OUT from time to time as well as IN control transfer failed: LIBUSB_TRANSFER_STALL - any ideas what might be going on?

[busticated]

i get IN control transfer failed: LIBUSB_TRANSFER_TIMED_OUT from time to time

i can reproduce this 100% of the time by connecting my device, letting my computer go to sleep, waking it, and running any usb command. unplugging and plugging back in gets things back to working.

[busticated]

@sergeuz can you think of a way to trigger "disconnecting" and / or "disconnected" states in these e2e tests? i haven't been able to observe a device reporting "disconnecting" for example.

[sergeuz]

can you think of a way to trigger "disconnecting" and / or "disconnected" states in these e2e tests? i haven't been able to observe a device reporting "disconnecting" for example.

It can be due to a transition from "disconnecting" to "disconnected" happening almost immediately, or do you mean you don't ever get "disconnected" as well?

[busticated]

@sergeuz

do you mean you don't ever get "disconnected" as well?

correct - i never see "disconnecting" or "disconnected" just "unknown", "connecting", and "connected"

[sergeuz]

i don't think it's related to my changes as this isn't new behavior (though perhaps my updates make it worse) but i get IN control transfer failed: LIBUSB_TRANSFER_TIMED_OUT from time to time as well as IN control transfer failed: LIBUSB_TRANSFER_STALL - any ideas what might be going on?

No idea, unfortunately. There seems to be some issue in the USB HAL implementation and, possibly, particle-usb as well. @technobly Is this something your team is currently looking into?

[sergeuz]

i never see "disconnecting" or "disconnected"

@busticated Even if the device is indeed disconnected?

[busticated]

@sergeuz

Even if the device is indeed disconnected?

yes? i tried putting the device into listening mode and then querying but in that case it returns unknown. polling after issuing a reset reports unknown -> connecting -> connected

[sergeuz]

i tried putting the device into listening mode and then querying but in that case it returns unknown. polling after issuing a reset reports unknown -> connecting -> connected

That's weird. I'm not sure why "unknown" is reported, it looks like a parsing error somewhere in fromProtobufEnum(). I'll take a look.

[busticated]

self-review