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
I have the following issue: I have created a generic sensor that triggers when a TV episode is being played and also some sensors for specific TV series. When I now start one of those specific TV series, both sensors are triggered, the specific one AND the generic one.
Is there a way, or can you add an optional flag or something, that ensures that when a more specific sensor is triggered the more generic sensor is not triggered too? The problem with the way it is now is that it will make my philips hue lights change twice quickly after each other.
(I know that part of this issue can also be attributed to HomeKit as there you can’t define a hierarchy an sensors either, but having it fixed in this homebridge plugin is probably easier than getting Apple to introduce a fix).
BTW Thanks for this fantastic plugin.
The text was updated successfully, but these errors were encountered:
I have the following issue: I have created a generic sensor that triggers when a TV episode is being played and also some sensors for specific TV series. When I now start one of those specific TV series, both sensors are triggered, the specific one AND the generic one.
Is there a way, or can you add an optional flag or something, that ensures that when a more specific sensor is triggered the more generic sensor is not triggered too? The problem with the way it is now is that it will make my philips hue lights change twice quickly after each other.
(I know that part of this issue can also be attributed to HomeKit as there you can’t define a hierarchy an sensors either, but having it fixed in this homebridge plugin is probably easier than getting Apple to introduce a fix).
BTW Thanks for this fantastic plugin.
The text was updated successfully, but these errors were encountered: