Why is the script not installing the latest valetudo?

[w1an]

Why is the script installing valetudo 0.5.3? Current version is 0.6.1, sha256 42b27288405db7f6335029c3ffedf8f12971aaf3b8d71ce5c3f28f095926fc76.

Is there a reason for sticking with 0.5.3?

Thanks

[rumpeltux]

This was a confirmed working version. 0.6.1 is partially broken for viomi. It’s fixed at head, so I’ll update this once a new release is available.

[mikoladz]

Valetudo 0.5.3 is not working at all with viomi.vacuum.v8, it crashes right away. I have replaced it with 0.6.1 and it's working, although looks like it has limited support for the device.

[Kaan88]

@rumpeltux Uninstall insructions you are pointing to doesn't have any info about s51valetudo script in rc.d folder. As far as I know your script is using the old method, not the miio_client.

I have an unrelated question, after deleting does miio_client file reappear after rebooting?

[rumpeltux]

Yes, deletion just removes the overlay and thereby restores the original firmware version.

For older uninstall instructions, refer to the respective version, e.g. https://github.com/Hypfer/Valetudo/blob/0.5.3/docs/_pages/installation/viomi.md

[forast3r]

Just a quick note on the rooting script, as far as been explained, it installs an older version of valetudo, note that this old version has some missing line(s). For example in /etc/init.d/valetudo (source: Valetudo/deployment/viomi/etc/init.d/valetudo)

        procd_open_instance
missing ->>>    procd_set_param env VALETUDO_CONFIG_PATH=/mnt/UDISK/valetudo_config.json
    procd_set_param oom_adj $OOM_ADJ

otherwise, the config file won't survive a reboot

[rumpeltux]

Fixed with #24