dreame-vacuum: "Device cannot be reached" after updating to 2025.3.0
Describe the bug
After updating HA to 2025.3.0b0 beta release I can not longer reach my Dreame device. I’m running the latest beta release of the Dreame Vacuum HACS integration (v2.0.0b16).
To Reproduce
Update to 2025.3.0b0 release.
Expected behavior Reaching the device.
Screenshots
Additional Information (please complete the following information)
- Model Name [e.g. dreame.vacuum.p2028]: D10s
- Firmware Version [e.g. 1156]: 4.1.8_1415
- Home Assistant Version: 2025.3.0b0
- Configuration Type [With or without map support]: With map support
- Errors or warnings shown in the HA logs (if applicable):
Felet härrör från en anpassad integration.
Loggare: custom_components.dreame_vacuum
Källa: custom_components/dreame_vacuum/coordinator.py:443
integration: Dreame Vacuum (dokumentation, ärenden)
Inträffade först: 11:16:21 (127 tillfällen)
Senast loggade: 14:02:50
Integration start failed: Traceback (most recent call last): File "/config/custom_components/dreame_vacuum/coordinator.py", line 437, in _async_update_data await self.hass.async_add_executor_job(self._device.update) File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 59, in run result = self.fn(*self.args, **self.kwargs) File "/config/custom_components/dreame_vacuum/dreame/device.py", line 2815, in update raise DeviceUpdateFailedException("Device cannot be reached") from None custom_components.dreame_vacuum.dreame.exceptions.DeviceUpdateFailedException: Device cannot be reached
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 24
- Comments: 70 (12 by maintainers)
Commits related to this issue
- Quick fix for https://github.com/Tasshack/dreame-vacuum/issues/866 — committed to toxic0berliner/dreame-vacuum by kinke 2 years ago
In the meantime, this can be used as a dirty workarround.
In protocol.py
add
from paho.mqtt import client as mqtt_clientunderfrom paho.mqtt.client import Clientand add
mqtt_client.CallbackAPIVersion.VERSION1,underself._client = Client(I have already made the changes related to paho 2.0 on my local. I am going to release a new version next week.
Fixed.
https://github.com/Tasshack/dreame-vacuum/releases/tag/v2.0.0b17
Any chance for a new v2.0.0 beta build with the fix?
Hi. The process that I followed, based on advice in one of the other threads was to re-download v2.0.0b17 via HACS and then restart Home Assistant. This worked for me, might be worth a try.
Confirm, it works! Thank you 😃
@Cheerpipe many thanks - this worked perfectly! Really appreciate you figuring out the issue.
Its already out, v2.0.0b17. 😉
Telnet is work on eu.iot.dreame.tech port 13267, but i can’t login on this page https://smarthome.dreame.tech/
For me it’s randomly on/off over the last few months. Mostly not working, sometimes working - which gives me the feeling that it is actually a server-side problem with Dreame, because it keeps changing even when there are no updates to this component.
I can approve that 2.0.0b17 fixed the issue for me (L10s Pro Ultra Heat)
Bonjour, Quand j’installe la version V2.0.0b17 cela fait rebooter mon HA en continu suis je le seul dans ce cas?
Big thanks. It is so easy, if you know where to find it. Works with 2025.2.5, let’s see what it will do with 2025.3.1. Or if it requires the changes in protocol.py mentioned earlier in this thread. But again, big thanks for the super fast response.
Normally, HA should prompt the update in the update-section.
If it does not, try the following: Go to HACs, find the Integration, click it. In the upper right corner click the 3 dots. There should be something like “download again” (sorry, my interface is german, so it says “erneut herunterladen”.) In the pop-up, you can read, which version you are about to download, change this with the field below if necessary (should be set to newest version automatically anyway). Click download.
Don’t worry, “download again” does not delete anything, it just updates the config of the integration, so your settings should stay. However I always recommend making a backup before running any update.
Feel free to ask for more details, if you can’t find it. I’ll add screenshots if necessary.
Thank you very much for the fast solution!! ❤️❤️