We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
以cuco.plug.cp2这个插座为例,注意到HA一启动,switch.cuco_cp2_switch这个parent entity就已经很快获得包括sub-entity需要引用的属性的全部value,但是几个sub-entity包括Power,Current, Voltage, Power_Cost_Today, Power_Cost_Month还要等待将近20~30秒以后才会更新。
我试过在customization中bind sensor, 也并不能加快sub-entity开机创建的过程。甚至如果sub-entity和parent-entity的interval_seconds不一样的话,它们的value更新都是不同步的,是否说明sub-entity是另外的cloud pull获得value的吗?
能够考虑sub entity的值从parent entity的property当中获得呢?这样是否会更快吗?除非sub-entity的value没有包含在parent的property当中。
The text was updated successfully, but these errors were encountered:
目前子实体的状态就是从父实体中拿到的,更新状态是由父实体完成的,所以interval_seconds只能用于父实体。但是子实体是在父实体注册到Hass以后才创建的,所以导致HA启动后子实体需多等待一会才变为可用。
interval_seconds
Sorry, something went wrong.
🚀 improve for sub entities (#313)
1ea0773
No branches or pull requests
以cuco.plug.cp2这个插座为例,注意到HA一启动,switch.cuco_cp2_switch这个parent entity就已经很快获得包括sub-entity需要引用的属性的全部value,但是几个sub-entity包括Power,Current, Voltage, Power_Cost_Today, Power_Cost_Month还要等待将近20~30秒以后才会更新。
我试过在customization中bind sensor, 也并不能加快sub-entity开机创建的过程。甚至如果sub-entity和parent-entity的interval_seconds不一样的话,它们的value更新都是不同步的,是否说明sub-entity是另外的cloud pull获得value的吗?
能够考虑sub entity的值从parent entity的property当中获得呢?这样是否会更快吗?除非sub-entity的value没有包含在parent的property当中。
The text was updated successfully, but these errors were encountered: