ERR_CONNECTION_REFUSED

Question

ERR_CONNECTION_REFUSED

Closed this issue 4 years ago · 14 comments

Hey :)

I need your help.
I have an old Roborock S5 and I updated my Valetudo to 10.1. That worked well. After that I wanted to do the firmware package install. I just took the original 2034.pkg one from vacuumz (not with valetudo or something in the name).

It installed successfully and now my valetudo site does not load. I do not have any s11valetudo file in /etc/init. The other ones are there:

Valetudo is there as well:

How can I startup that site again?

Thank you!

Answer 1 · 2021-01-11T13:53:39.000Z

You can take missing files from here and put it to corresponding locations. You'll need the aforementioned s11valetudo and valetudo-daemon.sh.

Answer 2 · 2021-01-11T14:01:35.000Z

Hi, thanks for the files. Sadly the error persists...

Answer 3 · 2021-01-11T14:01:38.000Z

You've installed only a "rooted" firmware file. Why not using the complete prebuild image with containing valetdo (if you don't want to build the firmware by yourself)?

Answer 4 · 2021-01-11T14:03:07.000Z

I had valetudo up and running. That's why I thought I could make an update from that... Well wrong thought I guess.

@rand256 and @pidator Is there any command where I can update the firmware again with the valetudo img from shell?
The shell with root privileges is working.

Answer 5 · 2021-01-11T14:10:32.000Z

Ah got it working again. The daemon needed to be under /usr/local/bin :)

Answer 6 · 2021-01-11T14:15:18.000Z

Actually you'll need to "install" (unpack) at least dns catcher and put contents of rc.local to /etc/rc.local to get local "cloud" connection working, otherwise you'll get no map and no chance to install other image using valetudo's Web UI.

Answer 7 · 2021-01-11T14:16:45.000Z

@rand256
ok where do I need to put the dns catcher?

Answer 8 · 2021-01-11T14:21:57.000Z

Simply unpack that tgz to root, there are already correct paths exist inside the archive.

And I forgot to mention these two lines to put into rc.local (after those of valetudo) for it to work.

Answer 9 · 2021-01-11T14:29:01.000Z

@rand256
After I did that it now states:

Answer 10 · 2021-01-11T14:30:08.000Z

Alternatively if you've installed miio python tools on your laptop/pc you could flash a whole new firmware file with the command
mirobo --ip <ROBOT-IP> --token <TOKEN> update-firmware <FILENAME>

Answer 11 · 2021-01-11T14:32:51.000Z

@pidator I guess original 2034 image won't allow local OTA updates.

@Schattenruf well, really probably the easiest way in this case could be to do a factory reset and start from scratch.

Answer 12 · 2021-01-11T14:39:46.000Z

@pidator I guess original 2034 image won't allow local OTA updates.

Since root access is still possible, I think it was installed vacuum_2034.pkg and following vacuum_2034.pkg.diff miio client should be replaced in this firmwarefile too:

Binary files /image.org/opt/rockrobo/miio/miio_client and /image/opt/rockrobo/miio/miio_client differ

so, mirobo update could be successfull ;)

Answer 13 · 2021-01-11T14:40:35.000Z

@pidator
Sadly it is not... "No respone from device"

Answer 14 · 2021-01-11T14:41:30.000Z

I gonna start from scratch then. Thank you all for your time!