Can't connect RFCOMM socket: Host is down











up vote
3
down vote

favorite












I have bluez 5.4.3 and I am attempting to communicate with a ble device through minicom. These two deceives (my computer and a bluno nano) are alreadt paired and this has been my method so far.



#bluetoothctl
# pair xx:xx:xx:xx:xx:xx
# exit


Everything is working well so far then...



#sudo rfcomm connect /dev/rfcomm0 xx:xx:xx:xx:xx:xx 1 &
[1] 3665
Can't connect RFCOMM socket: Host is down


Does anyone know how to resolve this issue? Any help would be very much appreciated.










share|improve this question














bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.



















    up vote
    3
    down vote

    favorite












    I have bluez 5.4.3 and I am attempting to communicate with a ble device through minicom. These two deceives (my computer and a bluno nano) are alreadt paired and this has been my method so far.



    #bluetoothctl
    # pair xx:xx:xx:xx:xx:xx
    # exit


    Everything is working well so far then...



    #sudo rfcomm connect /dev/rfcomm0 xx:xx:xx:xx:xx:xx 1 &
    [1] 3665
    Can't connect RFCOMM socket: Host is down


    Does anyone know how to resolve this issue? Any help would be very much appreciated.










    share|improve this question














    bumped to the homepage by Community 2 days ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

















      up vote
      3
      down vote

      favorite









      up vote
      3
      down vote

      favorite











      I have bluez 5.4.3 and I am attempting to communicate with a ble device through minicom. These two deceives (my computer and a bluno nano) are alreadt paired and this has been my method so far.



      #bluetoothctl
      # pair xx:xx:xx:xx:xx:xx
      # exit


      Everything is working well so far then...



      #sudo rfcomm connect /dev/rfcomm0 xx:xx:xx:xx:xx:xx 1 &
      [1] 3665
      Can't connect RFCOMM socket: Host is down


      Does anyone know how to resolve this issue? Any help would be very much appreciated.










      share|improve this question













      I have bluez 5.4.3 and I am attempting to communicate with a ble device through minicom. These two deceives (my computer and a bluno nano) are alreadt paired and this has been my method so far.



      #bluetoothctl
      # pair xx:xx:xx:xx:xx:xx
      # exit


      Everything is working well so far then...



      #sudo rfcomm connect /dev/rfcomm0 xx:xx:xx:xx:xx:xx 1 &
      [1] 3665
      Can't connect RFCOMM socket: Host is down


      Does anyone know how to resolve this issue? Any help would be very much appreciated.







      bluetooth bluez






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 9 '17 at 18:46









      Brandon Knape

      4626




      4626





      bumped to the homepage by Community 2 days ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 2 days ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          Seems that your local bluetooth hci device is down.



          Try hciconfig to get current device name and status, and you can use hciconfig hci0 up where hci0 is your device name.






          share|improve this answer





















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f343815%2fcant-connect-rfcomm-socket-host-is-down%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            Seems that your local bluetooth hci device is down.



            Try hciconfig to get current device name and status, and you can use hciconfig hci0 up where hci0 is your device name.






            share|improve this answer

























              up vote
              0
              down vote













              Seems that your local bluetooth hci device is down.



              Try hciconfig to get current device name and status, and you can use hciconfig hci0 up where hci0 is your device name.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                Seems that your local bluetooth hci device is down.



                Try hciconfig to get current device name and status, and you can use hciconfig hci0 up where hci0 is your device name.






                share|improve this answer












                Seems that your local bluetooth hci device is down.



                Try hciconfig to get current device name and status, and you can use hciconfig hci0 up where hci0 is your device name.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 11 '17 at 21:31









                ton

                1515




                1515






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f343815%2fcant-connect-rfcomm-socket-host-is-down%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Accessing regular linux commands in Huawei's Dopra Linux

                    Kernel panic - not syncing: Fatal Exception in Interrupt