IRobot binding compatible with Roomba i7?

1

We just acquired an Irobot Roomba i7+ vacuum cleaner. I tried to get the OH3 Irobot binding to work, but without any success thus far. The vacuum cleaner automatically appears in my inbox, but then I am unable to retrieve the password using the procedure described in the binding documentation. As soon as I accept the thing found in my inbox, that Irobot thing reports a “Communication error: Connection refused”. It does not appear to enter the “CONFIGURATION PENDING” state described in the documentation.

Any hints on this issue?

Many thanks in advance.

2

I have now done a bit of progress on this. I was able to download the relevant “password” using Dorita980. When I first entered that password into the relevant OH thing, OH apparently managed to connect to the Roomba. However, a moment later the connection was lost. The Roomba apparently acquired a new network name that includes the said password; perhaps this caused my router to assign a new DHCP address to the Roomba. And I am now getting error messages in the OH log whenever I try to activate the Roomba thing:

2021-03-24 17:28:26.905 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '192.168.2.3' with clientid f043af6f-0b5b-45f7-b8a5-42d29d95fff3
2021-03-24 17:28:26.905 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '192.168.2.245' with clientid D48C90B1519F431991212E954F9E5E11
2021-03-24 17:28:27.125 [INFO ] [mekit.internal.HomekitChangeListener] - Created 0 HomeKit items.
2021-03-24 17:28:27.847 [INFO ] [ab.ui.habpanel.internal.HABPanelTile] - Started HABPanel at /habpanel
2021-03-24 17:28:28.050 [WARN ] [robot.internal.handler.RoombaHandler] - MQTT connection failed: Timeout
2021-03-24 17:28:28.331 [ERROR] [io.openhabcloud.internal.CloudClient] - Error connecting to the openHAB Cloud instance
2021-03-24 17:28:29.253 [INFO ] [nal.communication.CommunicationState] - Login - Login to IP150 - OK
2021-03-24 17:28:32.909 [INFO ] [e.automation.internal.RuleEngineImpl] - Rule engine started.
2021-03-24 17:28:33.064 [INFO ] [.reconnect.PeriodicReconnectStrategy] - Try to restore connection to '192.168.2.245'. Next attempt in 5000ms
2021-03-24 17:28:33.064 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '192.168.2.245' with clientid D48C90B1519F431991212E954F9E5E11
2021-03-24 17:28:38.080 [INFO ] [.reconnect.PeriodicReconnectStrategy] - Try to restore connection to '192.168.2.245'. Next attempt in 5000ms
2021-03-24 17:28:38.080 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '192.168.2.245' with clientid D48C90B1519F431991212E954F9E5E11

The first (and succesful) attempt at connecting with an MQTT broker is my own stuff, but the second one, at address 192.168.2.245 (the address of my Roomba) is, I suppose, initiated by Irobot binding. Is there an MQTT broker in the Roomba, and if so why does the connection fail?

Many thanks in advance.

3

I now think I have probably confused the Roomba “blid” and the Roomba password. When I use dorita 980 to get the password, I get the following response:

Robot Data:
{ ver: '3',
  hostname: 'iRobot-D48C90B1519F431991212E954F9E5E11',
  robotname: 'Robot7',
  robotid: 'D48C90B1519F431991212E954F9E5E11',
  ip: '192.168.2.245',
  mac: '50:14:79:88:D1:8D',
  sw: 'lewis+3.10.8+lewis-release-rt320+13',
  sku: 'i755020',
  nc: 1,
  proto: 'mqtt',
  cap:
   { binFullDetect: 1,
     dockComm: 1,
     wDevLoc: 2,
     bleDevLoc: 1,
     edge: 0,
     maps: 3,
     pmaps: 4,
     tLine: 2,
     area: 1,
     eco: 1,
     multiPass: 2,
     pose: 1,
     team: 1,
     pp: 0,
     '5ghz': 1,
     prov: 3,
     sched: 1,
     svcConf: 1,
     ota: 2,
     log: 2,
     tileScan: 1 },
  blid: 'D48C90B1519F431991212E954F9E5E11' }
events.js:183
      throw er; // Unhandled 'error' event
      ^

Error: connect ECONNREFUSED 192.168.2.245:8883
    at Object._errnoException (util.js:1022:11)
    at _exceptionWithHostPort (util.js:1044:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1198:14)

Thus, it looks as if the problem is in getting the correct password.

4

Hi @isabellep ,

would this and/or this help? Please, read all the stuff. There were multiple fixes last time.

Greetings,

Alexander

5

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.