-
Notifications
You must be signed in to change notification settings - Fork 3
Cannot find dongle aka q.dongle(id) ESP32 - CC1101 #8
Comments
The dongle ID is not needed because the client is able to do auto discovery. If you don't see any radio object, then it means that auto discovery somehow failed. The best way to find out what failed is to increase the debug level of the firmware at compile time, so that you'll see a more verbose serial output: you'll find a couple of issues where I mention how to do that, or you could grep for "debug" in the source code. Could you paste the entire serial output, before the MQTT stuff? Also, when it says "transport not connected" it may indicate that it's having issues connecting to the broker. Can you try an auto-less, local, plain broker instead of an internet connected one? We've never had issues, but it's better to investigate one thing at a time. |
ok I will try the debug mode. I thought because of
also seems like a DNS resoving issue so I used an IP, but I think that those are the initial retries after finding a WIFI:
So they can see each other because of the serial log scrolling down in the moment I run the PyCLI and stating |
I also had to add a stub for not beeing implemented in
|
Same with the CLI over Serial:
|
sry just found the DEBUG flag:
but no clue... |
I removed the MQTT part and now it seems to work:
|
Hello, nice project.
Should the dongle be available automatically? I can see how my MQTT shell is connecting successfully to the ESP32 but I cannot find my dongle.
What would be my DongleID? Also the radioA object is missing?
Thank you!
The text was updated successfully, but these errors were encountered: