Deebot 601 not working

[dev-xaur]

I tested the adapter on my Deebot 601. Connection works correctly, data (name, nick, serial, etc.) are transmitted, but the control (charge, clean, edge, spot stop) does not work. And in the log only info messages appear, but no errors.

[mrbungle64]

Thanks for your feedback :)
I'll try to enhance the error handling and to provide error messages to the log.

Do the states 'info.cleanstatus' and 'info.chargestatus' display correct information when you control the device app/manually?

[dev-xaur]

Do the states 'info.cleanstatus' and 'info.chargestatus' display correct information when you control the device app/manually?

both states are empty, only connection and name are set. Neither the app nor the remote control changes any of the states.

[mrbungle64]

Hi @dev-xaur,

I released a new version of the adapter. I hope your device works (better) by using the new version.

[dev-xaur]

tach auch,

unfortunately it still doesn't work, I have removed the old instance and reinstalled version 0.3.3. Starting the instance only works with at least one spot area, on startup a warning '(10954) Failure code 0002' is logged. If necessary I can provide additional logs

[mrbungle64]

tach auch,

unfortunately it still doesn't work, I have removed the old instance and reinstalled version 0.3.3. Starting the instance only works with at least one spot area, on startup a warning '(10954) Failure code 0002' is logged. If necessary I can provide additional logs

Hi @dev-xaur,

can you please install the latest version from github?
https://github.com/mrbungle64/ioBroker.ecovacs-deebot.git

I improved the logging a few minutes ago. The Deebot 601 should work.
If not please post additional logs. Thanks in advance :)

[dev-xaur]

tach auch,

I improved the logging a few minutes ago. The Deebot 601 should work.
If not please post additional logs. Thanks in advance :)

here with current version from git repository, no running instances except 'ecovacs', 'admin' & 'web'

or 'complete' including update
ecovacs-log.pdf

i have another 129 pages of logs since noon today, but i would not like to make them public ;)

[mrbungle64]

tach auch,

I improved the logging a few minutes ago. The Deebot 601 should work.
If not please post additional logs. Thanks in advance :)

here with current version from git repository, no running instances except 'ecovacs', 'admin' & 'web'

Thanks for providing logs.

'Couldn't reach the vac :[404] recipient-unavailable' usally means that the device is not available for the Ecovacs server.
If the message appears again please check if the device is reachable via mobile app.

Did you press all the buttons (clean, edge etc) between 18:47:15 and 18:47:22 or was this somehow triggered automatically?

[dev-xaur]

'Couldn't reach the vac :[404] recipient-unavailable' usally means that the device is not available for the Ecovacs server.
If the message appears again please check if the device is reachable via mobile app.

i will try ...

Did you press all the buttons (clean, edge etc) between 18:47:15 and 18:47:22 or was this somehow triggered automatically?

nothing automatically triggered, when I use the APP then these actions do not appear in the log of the iobroker

[mrbungle64]

Hi @dev-xaur,

the adapter (version 0.3.4) is now available via latest repo :)

Can you please check the value in 'info.communicationProtocol'?
If the value is 'XMPP' your device should work :)

[dev-xaur]

hi @mrbungle64,

i installed the version 0.3.4 from the latest repo and changed the value from 'info.communicationProtocol' to 'XMPP' and now the main operations work. Only 'control.pause' seems not to work and all 'consumable.*' are empty.

[mrbungle64]

hi @mrbungle64,

i installed the version 0.3.4 from the latest repo and changed the value from 'info.communicationProtocol' to 'XMPP' and now the main operations work. Only 'control.pause' seems not to work and all 'consumable.*' are empty.

Hi @dev-xaur

did you change the value of 'info.communicationProtocol' manually?

[dev-xaur]

did you change the value of 'info.communicationProtocol' manually?

yes, but after installing version 0.3.9 from git, it's now back to MQTT and still works ;)

[mrbungle64]

@dev-xaur
Are the infos in the 'info' channel working (e.g. 'battery', 'chargestatus', 'cleanstatus')?
Btw have you installed a water tank?

[dev-xaur]

@dev-xaur
Are the infos in the 'info' channel working (e.g. 'battery', 'chargestatus', 'cleanstatus')?

no information, no matter in which mode

Btw have you installed a water tank?

no water tank installed

[mrbungle64]

@dev-xaur

I just released version 0.3.10 on GitHub. It might be possible that the values are now displayed :)

[dev-xaur]

@dev-xaur

It might be possible that the values are now displayed :)

correct, now the values are displayed

[mrbungle64]

Deebot 601 now seems to work to almost full extent