Unsupported Condition Entity Integrations

Unsupported Condition Entity Integrations

Some integrations create switch or binary_sensor entities that appear compatible with Lock Code Manager but have state semantics that don't map to access control.

For supported entity types and useful integrations, see Using Condition Entities.

scheduler-component

Integration: nielsfaber/scheduler-component

Why its entities don't work as LCM condition entities:

scheduler-component creates switch.schedule_<token> entities whose state tracks the timer's runtime, not whether access should be allowed right now. LCM condition entities need a state that means "access is allowed" when on and "access is denied" when off.

Scheduler State	What It Means	Why It Fails as a Condition
on	Timer is armed, waiting for its next trigger time	Means "scheduled", not "active window"
triggered	An action just fired (entity resets after ~1 min)	Momentary state, not a window
off	Schedule is disabled entirely	Wrong axis — schedule on/off, not window open/closed
unknown	Schedule failed to initialize	Error state

A scheduler entity reporting on at 3pm tells you "this schedule is waiting to fire at some future time", not "access is currently permitted" — so attaching it as an LCM condition entity produces incorrect behavior.

Using scheduler-component with LCM anyway:

scheduler-component can be used alongside LCM by skipping LCM's condition entity system entirely and instead having scheduler-component drive the slot's Enabled switch directly. Each timeslot in scheduler-component specifies free-form actions (a list of HA service calls), so you can configure a schedule whose action calls switch.turn_on on the slot's Enabled switch at the window start and switch.turn_off at the window stop. Any gating logic — day-of-week, presence, device state — lives inside scheduler-component's own weekdays / conditions config. From LCM's perspective the slot simply gets enabled and disabled like any other switch toggle; LCM never sees the scheduler entity at all.

What to use instead (if you want LCM condition entities):

For native LCM condition entity support, see Using Condition Entities. The built-in Schedule helper is the recommended primitive — its on / off states correctly model "in window" / "out of window".

Adding New Integrations to This List

If you find another integration that creates entities incompatible with LCM's access control model, please open an issue with:

1. Integration name and link
2. Entity domain (switch, binary_sensor, etc.)
3. State values and their meanings
4. Why these states don't map to "access allowed" / "access denied"