Consumable's remaining time is not published via MQTT unless web interface is visited

[JanickGers85]

Describe the bug

Consumable's remaining time is not published via MQTT unless web interface is visited

To Reproduce

1. Open web interface
2. You see these warning
   
3. Now take a look to MQTT (or HA in my case, I use HA autodiscovery)
4. Entities are updated now
   

Vacuum Model

RoborockV1ValetudoRobot

Valetudo Version

2022.01.0

Expected behavior

Consumables stats regularly updated, as done for the map.

Additional context

Here the logs

2022-01-12T19:07:29.233Z
Info
Set Logfile to /tmp/valetudo.log
2022-01-12T19:07:29.244Z
Info
Autodetected RoborockV1ValetudoRobot
2022-01-12T19:07:29.330Z
Info
Starting Valetudo 2022.01.0
2022-01-12T19:07:29.333Z
Info
Commit ID: 4055f65e50cf2c789df4f1810781f03d74405de4
2022-01-12T19:07:29.334Z
Info
Configuration file: /mnt/data/valetudo_config.json
2022-01-12T19:07:29.336Z
Info
Logfile: /tmp/valetudo.log
2022-01-12T19:07:29.337Z
Info
Robot: Roborock V1 (RoborockV1ValetudoRobot)
2022-01-12T19:07:29.338Z
Info
JS Runtime Version: v16.10.0
2022-01-12T19:07:29.339Z
Info
Arch: arm
2022-01-12T19:07:29.341Z
Info
Max Heap Size: 38 MiB
2022-01-12T19:07:29.342Z
Info
Node Flags: --expose-gc --max-heap-size=38
2022-01-12T19:07:29.357Z
Info
Autogenerated System ID: VoluminousCoolWasp
2022-01-12T19:07:29.362Z
Info
DeviceId 260856367
2022-01-12T19:07:29.363Z
Info
IP 127.0.0.1
2022-01-12T19:07:29.363Z
Info
CloudSecret zZVBXPh5vEmbxv2g
2022-01-12T19:07:29.365Z
Info
LocalSecret IYTKxfQJHUd4Jui4
2022-01-12T19:07:29.371Z
Info
Current rootfs: system_a (mmcblk0p8)
2022-01-12T19:07:43.700Z
Info
Valetudo can be reached via: valetudo-voluminouscoolwasp.local
2022-01-12T19:07:43.742Z
Info
Current /proc/self/oom_score_adj: 666
2022-01-12T19:07:43.756Z
Info
Dummycloud is spoofing 127.0.0.1:8053 on 127.0.0.1:8053
2022-01-12T19:07:43.759Z
Info
Webserver running on port 80
2022-01-12T19:07:43.778Z
Info
SSDP/UPnP advertisement started
2022-01-12T19:07:43.790Z
Info
Map Upload Server running on port 8079
2022-01-12T19:07:43.819Z
Info
Bonjour service "Valetudo V1 Web" with type "http" started
2022-01-12T19:07:43.821Z
Info
Bonjour service "Valetudo V1" with type "valetudo" started
2022-01-12T19:07:47.003Z
Info
Successfully set the robot time via NTP to 2022-01-12T19:07:47.896Z
2022-01-12T19:07:47.045Z
Info
Connected successfully to MQTT broker
2022-01-12T19:07:47.799Z
Info
MQTT configured
2022-01-12T19:08:03.594Z
Info
Cloud connected
2022-01-13T03:07:47.004Z
Info
Successfully set the robot time via NTP to 2022-01-13T03:07:47.896Z
2022-01-13T08:24:47.007Z
Info
Cloud message timed out. Assuming that we're not connected anymore
2022-01-13T08:24:54.161Z
Warn
Token is okay, however we're unable to reach the vacuum { retries: 10, method: 'get_status', args: {} }
2022-01-13T08:25:04.499Z
Info
Cloud connected
2022-01-13T08:30:26.695Z
Info
Cloud message timed out. Assuming that we're not connected anymore
2022-01-13T08:30:26.699Z
Error
Failed auto refresh: MiioTimeoutError: request timed out:{"method":"get_status","params":{},"id":4532}
    at Timeout.timeout [as _onTimeout] (/snapshot/Valetudo/backend/lib/miio/MiioSocket.js:209:32)
    at listOnTimeout (node:internal/timers:557:17)
    at processTimers (node:internal/timers:500:7)
2022-01-13T08:30:45.155Z
Info
Cloud connected
2022-01-13T08:32:27.938Z
Info
Cloud message timed out. Assuming that we're not connected anymore
2022-01-13T08:32:45.878Z
Info
Cloud connected
2022-01-13T08:32:46.433Z
Info
Cloud message timed out. Assuming that we're not connected anymore
2022-01-13T08:32:46.699Z
Info
Cloud connected
2022-01-13T08:36:08.262Z
Info
Cloud message timed out. Assuming that we're not connected anymore
2022-01-13T08:36:25.426Z
Warn
Token is okay, however we're unable to reach the vacuum { retries: 10, method: 'get_status', args: {} }
2022-01-13T08:36:26.599Z
Info
Cloud connected
2022-01-13T08:36:28.591Z
Info
Cloud message timed out. Assuming that we're not connected anymore
2022-01-13T08:36:30.108Z
Info
Cloud connected

[Hypfer]

Huh. Seems to be roborock-specific as it did work on dreame.

I was able to reproduce it on my S5. Why though?