ERR_CONNECTION_REFUSED

[Schattenruf]

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!

[rand256]

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

[Schattenruf]

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

[pidator]

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)?

[Schattenruf]

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.

[Schattenruf]

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

[rand256]

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.

[Schattenruf]

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

[rand256]

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.

[Schattenruf]

@rand256 After I did that it now states:

[pidator]

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>

[rand256]

@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.

[pidator]

@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 ;)

[Schattenruf]

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

[Schattenruf]

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