You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
I have a virtual device that has four states, each with an assigned attribute/value pair in HS. (Motion, no motion, away, other)
However, within the integration, it is represented strictly as on/off both as a toggle device and on the timeline. The attributes of the entity show both the value (1) and the attribute title (e.g. Away).
The text was updated successfully, but these errors were encountered:
This would be hard to handle from both the HS API and HA side, mostly because this does not correspond to an entity type in HA, other than maybe Sensor. This is a single ref in HA? If it’s represented as a switch in HA it’s because you have given on and off values to two attributes in HS.
I am not extensively familiar with either but I understand what you're saying.
In HS it is a single ref with which I used multiple control values (e.g. onAlternate) but both on and off are present. For my control, I do not use on/off, so they could be removed or changed. If these are changed to NotSpecified, would this change the entity in HA?
Regarding entity types, with those in mind, is there a type that might expose the multiple states for control? I am relatively new to HA and do not expect you to troubleshoot my instance, simply trying to find a meet in the middle solution that allows this to work for both. Thanks!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a virtual device that has four states, each with an assigned attribute/value pair in HS. (Motion, no motion, away, other)
However, within the integration, it is represented strictly as on/off both as a toggle device and on the timeline. The attributes of the entity show both the value (1) and the attribute title (e.g. Away).
The text was updated successfully, but these errors were encountered: