Roborock S5 Max - Entities Unavailable but seen in DEBUG mode

Hi everybody,

I set up my Roborock S5 Max successfully through ip + token and it works reliably except that 9 entities are always disabled:

I have enabled the DEBUG on the integration and interesting I see way more values that retrieved correctly like fanspeed, and DND status which show as Unavailable in Home Assistant.

Does anybody know what the problem could be?

Thanks,
Sam

2021-12-05 22:15:08 DEBUG (MainThread) [homeassistant.components.xiaomi_miio] 
Got new vacuum state: VacuumCoordinatorData(status=<VacuumStatus battery=100 clean_area=16.195 
clean_time=0:14:47 error=No error error_code=0 fanspeed=102 got_error=False 
in_segment_cleaning=False in_zone_cleaning=False is_on=False is_paused=False 
map=True state=Charging state_code=8>, dnd_status=<DNDStatus enabled=True end=08:00:00 
start=22:00:00>, last_clean_details=<CleaningDetails area=16.195 complete=True duration=0:14:47 
end=2021-12-05 10:39:03 error=No error error_code=0 start=2021-12-05 10:24:16>, 
consumable_status=<ConsumableStatus filter=4:28:03 filter_left=6 days, 1:31:57 main_brush=4:28:03 
main_brush_left=12 days, 7:31:57 sensor_dirty=4:15:25 sensor_dirty_left=1 day, 1:44:35 
side_brush=4:28:03 side_brush_left=8 days, 3:31:57>, clean_history_status=<CleaningSummary 
count=9 dust_collection_count=None ids=[1638696256, 1638695014, 1638691626, 1638636573, 
1638636443, 1638433405, 1638428135, 1638423515, 1638392743] total_area=234.68 
total_duration=4:15:25>, timers=[], fan_speeds={'Silent': 101, 'Standard': 102, 'Medium': 103, 'Turbo': 
104, 'Gentle': 105, 'Auto': 106}, fan_speeds_reverse={101: 'Silent', 102: 'Standard', 103: 'Medium', 104: 
'Turbo', 105: 'Gentle', 106: 'Auto'})

Hi @jambuu
,i have the same issue with my roborock S5.
Could you already solve it?

Hi @desantes,

yes, I raised as a bug here but it turns out it is not a bug, but a feature. Now, entities are being disabled by default (due to reasons) and we need to manually enable them :smiley:

I spent a long time looking at debug logs for it!

Cheers!

Hi @jambuu ,
thanks a lot for your feedback and the information about that new feature :wink:

regards

Sascha