# Roborock node causes instance to shut down

**URL:** <https://discourse.nodered.org/t/roborock-node-causes-instance-to-shut-down/56468>\
**Category:** General\
**Created:** [11 January 2022 13:55 UTC](https://discourse.nodered.org/t/roborock-node-causes-instance-to-shut-down/56468 "2022-01-11T13:55:10Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pinky](https://avatars.discourse-cdn.com/v4/letter/p/3d9bf3/32.png) [@Pinky](https://discourse.nodered.org/u/Pinky)\
**Post date:** [11 January 2022 13:55 UTC](https://discourse.nodered.org/t/roborock-node-causes-instance-to-shut-down/56468/1 "2022-01-11T13:55:10Z")

</div>

Hello everybody,

I have installed 'node-red-contrib-miio-roborock' in my Instance of node-red and connected my Vaccuum cleaner. I already noticed, that the software causes the whole instance to break when the cleaner does not respond. (Battery down i.e.)

Now I sent it away for maintenence and just realized that nothing in my house works anymore, because the node-red instance is completely broken. Is there anything I can do to deactivate the error causing part? Maybe from the console delete the node of the cleaner or something? The node-red backend also does not load!

Best regards,  
Pinky

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [11 January 2022 13:59 UTC](https://discourse.nodered.org/t/roborock-node-causes-instance-to-shut-down/56468/2 "2022-01-11T13:59:23Z")

</div>

Start node-red in safe mode. Once running, you can access the browser, remove any nodes you need to then deploy.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [11 January 2022 14:01 UTC](https://discourse.nodered.org/t/roborock-node-causes-instance-to-shut-down/56468/3 "2022-01-11T14:01:56Z")

</div>

Ps, there are a couple of issues on the repo. This one suggests a fix....

> <https://github.com/andreypopov/node-red-contrib-miio-roborock/issues/19#issuecomment-966964021>
>
> \*\* Describe issue \*\*
> If Vacuum is not available NodeRed hangs and restarting in… endless loop
> 
> \*\* Your flow here \*\*
> Happens with each Command or Event Flow.
> 
> \*\* Screens / Logs \*\*
> node-red.0 | 2020-09-23 08:52:53.337 | info | (2706) Starting node-red: --max-old-space-size=128 /opt/iobroker/node\_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js
> \-- | -- | -- | --
> node-red.0 | 2020-09-23 08:52:48.336 | info | (2706) node-red exited with 6
> node-red.0 | 2020-09-23 08:52:47.069 | warn | (22221) Terminated (UNCAUGHT\_EXCEPTION): Without reason
> node-red.0 | 2020-09-23 08:52:46.004 | error | (22221) Error: Could not connect to device, handshake timeout at Timeout.handshakeTimeout.setTimeout \[as \_onTimeout\] (/opt/iobroker/iobroker-data/node-red/node\_modules/miio/lib/network.js:427:17)
> node-red.0 | 2020-09-23 08:52:46.003 | error | (22221) unhandled promise rejection: Could not connect to device, handshake timeout
> node-red.0 | 2020-09-23 08:52:45.997 | error | Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
> node-red.0 | 2020-09-23 08:52:45.994 | warn | (2706) 23 Sep 08:52:45 - \[warn\] \[miio-roborock-server:Wilma\] Miio Roborock Error: Could not connect to device, handshake timeout
> node-red.0 | 2020-09-23 08:52:43.170 | warn | (2706) 23 Sep 08:52:43 - \[warn\] Projekte inaktiviert: editorTheme.projects.enabled=false
> node-red.0 | 2020-09-23 08:52:31.727 | info | (2706) Starting node-red: --max-old-space-size=128 /opt/iobroker/node\_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js
> 
> 
> 
> \*\* Hardware / Software \*\*
>   - raspberry 4  

---

<div class="post-metadata">

**Author:** ![Pinky](https://avatars.discourse-cdn.com/v4/letter/p/3d9bf3/32.png) [@Pinky](https://discourse.nodered.org/u/Pinky)\
**Post date:** [11 January 2022 14:04 UTC](https://discourse.nodered.org/t/roborock-node-causes-instance-to-shut-down/56468/4 "2022-01-11T14:04:41Z")

</div>

Awesome, that sounds good - one Problem is left:

I installed node-red within iobroker, so the usual paths for stopping the service do not work.  
Has anyone the correct "stop/safemode"-Path?

Best regards

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [11 January 2022 14:06 UTC](https://discourse.nodered.org/t/roborock-node-causes-instance-to-shut-down/56468/5 "2022-01-11T14:06:24Z")

</div>

Can you access the terminal of the container? You can uninstall the node using `npm remove node-red-contrib-xxxxx` then restart.

---

<div class="post-metadata">

**Author:** ![Pinky](https://avatars.discourse-cdn.com/v4/letter/p/3d9bf3/32.png) [@Pinky](https://discourse.nodered.org/u/Pinky)\
**Post date:** [11 January 2022 14:06 UTC](https://discourse.nodered.org/t/roborock-node-causes-instance-to-shut-down/56468/6 "2022-01-11T14:06:42Z")

</div>

I just found: Within iobroker activate checkbox: Security-Mode and relaunch the module.

Worked!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [12 March 2022 14:07 UTC](https://discourse.nodered.org/t/roborock-node-causes-instance-to-shut-down/56468/7 "2022-03-12T14:07:35Z")

</div>

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