-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
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
Elgato Eve shows Inactive appliances as though they are in an error state #6
Comments
Testing how the various HomeKit apps show different status characteristics...
Additionally, Eve shows the Neither the Apple Home app nor Hesperus show any of these characteristics. |
The mapping from
This should work better with the Elgato Eve app. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When an appliance is idle, the Elgato Eve app presents it as though it is in an error state. On the summary screens it shows a red warning triangle with an exclamation mark, and on the detailed screens it shows the status icon in red with the message:
This is annoying. It appears to do this based on the
Status Active
characteristic being set tofalse
(even ifActive
isINACTIVE
and theStatus Fault
characteristic isNO_FAULT
).The HomeKit Accessory Protocol Specification describes
Status Active
as:This plugin currently maps
BSH.Common.Status.OperationState
to HomeKit Characteristics as follows:Active
Status Active
Status Error
Inactive
INACTIVE
false
NO_FAULT
Ready
INACTIVE
false
NO_FAULT
DelayedStart
ACTIVE
false
NO_FAULT
Run
ACTIVE
true
NO_FAULT
Pause
ACTIVE
false
NO_FAULT
ActionRequired
ACTIVE
false
NO_FAULT
Finished
INACTIVE
false
NO_FAULT
Error
ACTIVE
false
GENERAL_FAULT
Aborting
ACTIVE
false
NO_FAULT
A different mapping may work better.
If this is changed, then it is probably also worth considering using the
Active
characteristic to control program pause/resume (or stop) for appliances with those capabilities. This plugin currently configures theActive
characteristic as read-only, but this can be changed to read-write where appropriate.This was originally raised by @DJay-X in issue #1.
The text was updated successfully, but these errors were encountered: