Connection Unstable Issue while Running Module 1.4 of Self-Driving Laboratories

[greenmossball]

Hi all,

I'm experiencing an error message when running the mqtt_led.py script described in the 1.4 module (Device communication). This is the error message I see:

Obtaining CA Certificate
Checking WiFi integrity.
Traceback (most recent call last):
File "", line 119, in
File "asyncio/core.py", line 1, in run
File "asyncio/core.py", line 1, in run_until_complete
File "asyncio/core.py", line 1, in run_until_complete
File "", line 102, in main
File "mqtt_as.py", line 654, in connect
File "mqtt_as.py", line 646, in wifi_connect
OSError: Connection Unstable

Any help will be greatly appreciated. I was able to run the "Run the demo" module so I'm not sure what I'm doing wrong.

[sgbaird]

I don't think I've seen a "connection unstable" error before. Could you try with one or two other WiFi networks? (E.g., phone hotspot).

Did you finish module 1 recently? Might be worth going back to check to make sure it still runs OK. May help with troubleshooting.

[greenmossball]

Hi Sterling, Yes, I tried it again just to see if something might have changed between then and now. It seems to run fine. I'll try running in another Wifi. The phone hotspot doesn't seem to work,btw. best, -a-

…

On Sat, Nov 16, 2024 at 7:43 PM Sterling G. Baird ***@***.***> wrote: I don't think I've seen a "connection unstable" error before. Could you try with one or two other WiFi networks? (E.g., phone hotspot). Did you finish module 1 recently? Might be worth going back to check to make sure it still runs OK. May help with troubleshooting. — Reply to this email directly, view it on GitHub <#133 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKHETI2NEZDR45NU32TFQLL2BAGFVAVCNFSM6AAAAABR5JJINKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMRYGE2DGOI> . You are receiving this because you authored the thread.Message ID: <AccelerationConsortium/ac-microcourses/repo-discussions/133/comments/11281439 @github.com>

[sgbaird]

Thanks!

The phone hotspot doesn't seem to work

Oof. I'll ask someone to see if they can reproduce it. Do you mind also opening an issue on the mqtt_as repo? They'd probably know about this error better than me.

I'll keep digging.

[sgbaird]

@RubainaFarin31 could you test out the mentioned code to see if you run into the same error or not?

[sgbaird]

@greenmossball any update with trying another WiFi?

[greenmossball]

Hi Sterling, I tried wifi from my phone but that did not work either. I just answered the questions of the tests as best as i could and moved on and completed the course. best, -a-

…

On Mon, Jan 6, 2025 at 2:53 AM Sterling G. Baird ***@***.***> wrote: @greenmossball <https://github.com/greenmossball> any update with trying another WiFi? — Reply to this email directly, view it on GitHub <#133 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKHETI6OY4TLQCCJEO45FRD2JJOEPAVCNFSM6AAAAABR5JJINKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZUG4ZTQOI> . You are receiving this because you were mentioned.Message ID: <AccelerationConsortium/ac-microcourses/repo-discussions/133/comments/11747389 @github.com>

[sgbaird]

Ah, OK. Sorry to hear that. One key difference is that self-driving-lab-demo package uses mqtt.simple, whereas module 1.4 uses mqtt_as (typically more robust and offers more features). I've been meaning to switch self-driving-lab-demo over to mqtt_as, but left it as-is since it's been working fine. I'll open an issue about the instability on mqtt_as repo.

[sgbaird]

One possible workaround might be to replace await client.connect() with await client.connect(quick=True)