Announcement

Collapse
No announcement yet.

BLRoombaWifi

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Blade
    replied
    No problem - glad you got it working

    Leave a comment:


  • MNB
    replied
    Bob, I've figured it out re Dorita980. In my procedure for the 980 I had the following command: in the “Command Prompt” screen Type “node .\bin\getpassword.js 192.168.1.XXX”, and enter, however this procedure with the i7 will only produce the password. Soo... for the i7 the following command must be use to produce both correct userid and password same output as 980;in the “Command Prompt” screen Type “get-roomba-password 192.168.1.XXX”, and enter.

    What I discovered is that my blid was slightly different it started out correctly but was short 8 additional characters at the end. I then deleted my prior Roomba in the Plug-In and its' associated devices and re-added a new Roomba as normal with the correct blid and password and Wala! now working i7 Roomba devices. As always a learning moment, thanxs Bob for all the support and time I hope this helps the next person trying to navigate all things npm, I will update my previous procedure to reflect the changes. Mike

    Leave a comment:


  • Blade
    replied
    I cannot think of anything right now
    I wonder why dorita does not return the user name

    Leave a comment:


  • MNB
    replied
    Originally posted by Blade View Post
    OK the return back from the MQTT connect is 2 which is this:

    CONN_REFUSED_IDENT_REJECTED

    Looks like it could possibly be the username or password or both
    Bob, any suggestions? Mike

    Leave a comment:


  • MNB
    replied
    I also noticed that when I look at my 980 Roomba the hostname is Roomba followed by the username (numbers after the dash) which is the same as what I used for the I7. Mike
    Attached Files

    Leave a comment:


  • MNB
    replied
    I noticed when I did my Dorita980 on the i7 Roomba I got an abbreviated return (see attached) which only contained the password (this was noted by another i7 user via post) so in order to get the username I went to my UniFi Clients which gave me the Hostname see attached
    Attached Files

    Leave a comment:


  • Blade
    replied
    OK the return back from the MQTT connect is 2 which is this:

    CONN_REFUSED_IDENT_REJECTED

    Looks like it could possibly be the username or password or both

    Leave a comment:


  • MNB
    replied
    Bob, per your request..
    Attached Files

    Leave a comment:


  • Blade
    replied
    It runs the trigger on connect or a connect failed attempt to the roomba

    Try out 2.0.32
    I added more debug logging

    Delete the debug log and capture the same log

    Leave a comment:


  • MNB
    replied
    Bob, question relating to the BLRoomba Connectivity Trigger is there a frequency when the trigger is issued or is it on a change basis? The reason I asked is that I created a Virtual Device that has two state Connected or Not connected which is toggled depending on Connectivity Trigger, I noticed that when I change it from On to Off it seems to stay Off even though it is really still connected. Mike

    Leave a comment:


  • MNB
    replied
    Ok Bob, firstly thanxs for taking the time to investigate. English please so the connection issue is re the Roomba PI or something else and more importantly is there a possible fix? Mike

    Leave a comment:


  • Blade
    replied
    Try out 2.0.32
    I added more debug logging

    Delete the debug log and capture the same log

    Leave a comment:


  • Blade
    replied
    The connection is being refused to the i7. The MQTT library is not reporting an exception but the the object is not connected

    Leave a comment:


  • MNB
    replied
    Rosie (Down Stairs) - Username/Blid:1DC00179C5B947F6934DEB11

    Leave a comment:


  • Blade
    replied
    Which one of your roombas is the i7?

    Leave a comment:

Working...
X