Closed balloob closed 8 years ago
Can this property be set via the customization of functionality?
mån 15 feb. 2016 10:14 Paulus Schoutsen notifications@github.com skrev:
This weekend we added support for assumed states in #1247 https://github.com/balloob/home-assistant/pull/1247. This is made available to any entity via the assumed_state https://github.com/balloob/home-assistant/blob/dev/homeassistant/helpers/entity.py#L119-L122 property.
The frontend has been updated to support this for any entity that used to be toggled (blue color indicates the state we assume it is).
[image: screen shot 2016-02-15 at 1 01 34] https://cloud.githubusercontent.com/assets/1444314/13043978/63e90bbc-d380-11e5-8b22-7a9903a0a935.png
Assumed states are currently only implemented by the demo switch. It is not being used by platforms or components, yet.
These are the components that I can think of of the top of my head that support should be added to:
- Group should have assumed_state = True if any child state is assumed
- MQTT Light should have assumed_state = True if optimistic
- MQTT Switch should have assumed_state = True if optimistic
If you're going to add this to your platforms, please also add the ha_iot_class: "Assumed State" to your documentation on the website (example https://raw.githubusercontent.com/balloob/home-assistant.io/master/source/_components/light.limitlessled.markdown )
— Reply to this email directly or view it on GitHub https://github.com/balloob/home-assistant/issues/1263.
Yes, it's just an attribute like anything else
On Mon, Feb 15, 2016, 07:15 Stefan Jonasson notifications@github.com wrote:
Can this property be set via the customization of functionality?
mån 15 feb. 2016 10:14 Paulus Schoutsen notifications@github.com skrev:
This weekend we added support for assumed states in #1247 https://github.com/balloob/home-assistant/pull/1247. This is made available to any entity via the assumed_state < https://github.com/balloob/home-assistant/blob/dev/homeassistant/helpers/entity.py#L119-L122
property.
The frontend has been updated to support this for any entity that used to be toggled (blue color indicates the state we assume it is).
[image: screen shot 2016-02-15 at 1 01 34] < https://cloud.githubusercontent.com/assets/1444314/13043978/63e90bbc-d380-11e5-8b22-7a9903a0a935.png
Assumed states are currently only implemented by the demo switch. It is not being used by platforms or components, yet.
These are the components that I can think of of the top of my head that support should be added to:
- Group should have assumed_state = True if any child state is assumed
- MQTT Light should have assumed_state = True if optimistic
- MQTT Switch should have assumed_state = True if optimistic
If you're going to add this to your platforms, please also add the ha_iot_class: "Assumed State" to your documentation on the website (example < https://raw.githubusercontent.com/balloob/home-assistant.io/master/source/_components/light.limitlessled.markdown
)
— Reply to this email directly or view it on GitHub https://github.com/balloob/home-assistant/issues/1263.
— Reply to this email directly or view it on GitHub https://github.com/balloob/home-assistant/issues/1263#issuecomment-184249775 .
This weekend we added support for assumed states in #1247. This is made available to any entity via the
assumed_state
property.The frontend has been updated to support this for any entity that used to be toggled (blue color indicates the state we assume it is).
Assumed states are currently only implemented by the demo switch. It is not being used by platforms or components, yet.
These are the components that I can think of of the top of my head that support should be added to:
If you're going to add this to your platforms, please also add the
ha_iot_class: "Assumed State"
to your documentation on the website (example)