石头机器人S5在更新1.01版本之后，部分实体消失了

[LUOZEYUE]

Device model / 设备型号

roborock.vacuum.s5

Component version / 插件版本

1.01

HA core version / HA版本

2024.11.3

Integrated mode / 集成方式

Automatic (自动模式)

The problem / 问题详情

部分实体消失了，比如那个点一下就启动机器人的石头。我删除重新添加也不行。现在只有如图几个实体。

Entity attributes / 实体属性

info: null
model: roborock.vacuum.s5
did: "74457781"
mac: 78:11:DC:81:E4:47
lan_ip: 192.168.31.176
app_link: mihome://device?uid=42198941&did=74457781
miot_type: urn:miot-spec-v2:device:vacuum:0000A006:roborock-s5:1
available: true
home_room: 我爱我家 客厅
icon: mdi:information
updater: local
updated_at: "2024-12-03 17:23:30.635021+08:00"
converters:
  - info
  - battery_level
  - vacuum.status
  - props:clean_area
  - props:clean_time
  - brush_life_level
customizes:
  sensor_attributes: props:clean_area,props:clean_time,brush_life_level
  sensor_properties: vacuum.status
  select_properties: water_level,mop_mode
battery_level: 100
vacuum.status: 3
battery.charging_state: 1
vacuum.mode: 104
device_class: update
friendly_name: 扫地机器人 信息

Home Assistant Logs / 系统日志

日志记录器: homeassistant.components.vacuum
来源: helpers/entity_platform.py:728
集成: 扫地机 (文档, 问题)
首次出现: 17:16:14 (1 次总计出现)
上次记录: 17:16:14

xiaomi_miot: Error on device update!
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 728, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1302, in async_device_update
await self.async_update()
File "/config/custom_components/xiaomi_miot/vacuum.py", line 291, in async_update
await self.device.dispatch(self.device.encode({'props': props}))
TypeError: object NoneType can't be used in 'await' expression

[fay000fay]

我也是。S5和T7SPLUS全部失效。

[ZhengGood]

我也是。S5失效了

[oimag]

+1

[fay000fay]

我也是。S5失效了

退回老版本即可。尝鲜有风险。

[alxstojanovic]

It's not just the roborock vac. Almost every device was changed and almost every device has had some info/status entity removed which to me is INSANE.

I cannot express how frustrating the recent 4 upgrades were, especially because of breaking changes!!!

First upgrade caused a complete and utter failure of my alarming system because the alarm entities for Hubs got broken in Miot Auto, so I had to switch to Gateway 3 Integration and redo BASICALLY EVERYTHING which took an entire weekend of recoding entities, redoing some logic because of course the other integration was providing them in a different way and so on.

Next upgrade and the Temp and Humidity sensors got messed up because guess what? MiotAuto decided to re-do its EXISTING entities...
But wait, there's more - the latest update messed up literally every device in my 300+ devices smart home, of which over 150 are Xiaomi whereby lots of device status entities subsequently became 'no longer provided by integration'. These were being used to not only display the status of my stuff around the home but also to determine the next courses of action my smart home would be taking regarding those devices and other devices which must react a certain way to the status changes of the aforementioned devices. I don't like saying it - but my smart home setup is complicated because it simply does a lot. Over 800 checks are done every second, over 500 being on Xiaomi devices...

I know that this is an open-source project and that the developer does it in their free time and all that speak, but we are not talking about a small integration used by a few hundred instances at best. We are talking about a very popular, major integration that serves as a backbone to many systems, so it is unacceptable that such breaking changes are being introduced with either zero or extremely poor documentation and warning provided and with absolutely no legacy support whatsoever for systems where moving to the new way of obtaining information is either not feasible due to their size or simply impossible due to the way the information was being processed.

I hope the developer reverts their changes in later versions or at least returns the status entities for legacy support for existing devices, because I personally won't be upgrading any further than 0.75. This project is becoming worse than Tuya with how owners are being treated to changes.

[fay000fay]

It's not just the roborock vac. Almost every device was changed and almost every device has had some info/status entity removed which to me is INSANE.

I cannot express how frustrating the recent 4 upgrades were, especially because of breaking changes!!!

First upgrade caused a complete and utter failure of my alarming system because the alarm entities for Hubs got broken in Miot Auto, so I had to switch to Gateway 3 Integration and redo BASICALLY EVERYTHING which took an entire weekend of recoding entities, redoing some logic because of course the other integration was providing them in a different way and so on.

Next upgrade and the Temp and Humidity sensors got messed up because guess what? MiotAuto decided to re-do its EXISTING entities... But wait, there's more - the latest update messed up literally every device in my 300+ devices smart home, of which over 150 are Xiaomi whereby lots of device status entities subsequently became 'no longer provided by integration'. These were being used to not only display the status of my stuff around the home but also to determine the next courses of action my smart home would be taking regarding those devices and other devices which must react a certain way to the status changes of the aforementioned devices. I don't like saying it - but my smart home setup is complicated because it simply does a lot. Over 800 checks are done every second, over 500 being on Xiaomi devices...

I know that this is an open-source project and that the developer does it in their free time and all that speak, but we are not talking about a small integration used by a few hundred instances at best. We are talking about a very popular, major integration that serves as a backbone to many systems, so it is unacceptable that such breaking changes are being introduced with either zero or extremely poor documentation and warning provided and with absolutely no legacy support whatsoever for systems where moving to the new way of obtaining information is either not feasible due to their size or simply impossible due to the way the information was being processed.

I hope the developer reverts their changes in later versions or at least returns the status entities for legacy support for existing devices, because I personally won't be upgrading any further than 0.75. This project is becoming worse than Tuya with how owners are being treated to changes.

Yes. I reverted to version 0.75 and everything worked fine again.

[AlexNikitos]

Yes. I reverted to version 0.75 and everything worked fine again.

How to go back to the previous version?

[fay000fay]

Yes. I reverted to version 0.75 and everything worked fine again.

How to go back to the previous version?

HACS--xiaomi miot auto --redownload, then select old version you want.