Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    Improvements to Bluetooth / BLE documentation

    Scheduled Pinned Locked Moved MicroPython
    4 Posts 2 Posters 1.4k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T Offline
      TravisT
      last edited by

      My question is mainly for the device acting as a peripheral.

      Not that there is no information for this subject, but it would be nice to get much more clarity on how the this specific implementation is expected to be used. It makes it much harder to setup and diagnose early issues with such sparse examples.

      This is the best reference I have found so far.
      https://docs.pycom.io/pycom_esp32/library/network.Bluetooth.html

      The documentation page for Bluetooth is out of date and incomplete.
      https://docs.pycom.io/pycom_esp32/pycom_esp32/tutorial/includes/bluetooth.html

      Honestly I will pay for prompt support, I just want to get this product working so I can evaluated and test it for my application. I know learning and testing is part of the game, but I would like to minimize me trying to figure out how best to your the product you designed.

      You are planning to sell OEM modules without proper documentation scares me. I know I am personally accepting risk for a new product with young company, but it would really ease my mind to see more updates to the documentation when new features are part of the firmware.

      1 Reply Last reply Reply Quote 2
      • D Offline
        daniel
        last edited by

        @TravisT you are right, the documentation is still a bit behind in some areas, specially when it comes to the tutorials. Good news is that we have a new member in our team that will start working on this next Monday.

        Regarding dedicated support, please send us an email to: support at pycom.io with the details of your project and we'll back to you with feedback asap.

        Cheers,
        Daniel

        1 Reply Last reply Reply Quote 0
        • T Offline
          TravisT
          last edited by

          @daniel
          Hello,
          Thanks for the reply. I am happy to hear that you will be having somebody help with this. The product seems amazing so far (WiPy 2) but it does add to the struggle when API and documentation are not complete.

          I emailed support about 5 days ago.

          Thanks

          1 Reply Last reply Reply Quote 0
          • D Offline
            daniel
            last edited by

            @TravisT thanks for the quick reply. I found your email, somehow we missed it 5 days ago, apologies for that... We'll get back to you very soon.

            1 Reply Last reply Reply Quote 0

            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

            With your input, this post could be even better 💗

            Register Login
            • 1 / 1
            • First post
              Last post

            Pycom on Twitter

            Pycom