Why do my Philips Hue bulbs turn on by themselves after a power outage, even when I set them to “PowerOn Behavior: Last State”?

Smart home owners often discover a strange problem:

Z-Wave security sensors (door, window, or motion sensors) work perfectly as Alexa triggers at first, but as soon as the system puts them into “supervised mode”, Alexa custom routines suddenly stop reacting.

This behavior is not a random bug. It is usually the result of how:

• Z-Wave security devices behave in supervised/secure mode
• Your hub exposes those devices to Alexa
• Amazon’s security and privacy rules limit what can be done with “security-classified” devices

This article explains, in practical terms, why this happens and what you can do about it without weakening the security of your system.

1. How Alexa Custom Routines Use Z-Wave Sensors

Alexa routines are event-driven automations. A typical configuration is:

• Trigger: “When this happens → Contact sensor opens”
• Action: “Turn on hallway lights” or “Announce: ‘Front door opened’”

For this to work, several things must happen behind the scenes:

1. Your Z-Wave sensor sends a state change (open/close, motion/no motion) to the hub or alarm panel.
2. The hub’s Alexa Skill (cloud integration) converts that event into a standard Alexa device capability, such as:
• contactSensor (open/closed)
• motionSensor (detected/cleared)
3. Amazon’s Alexa Smart Home API receives that event and uses it to trigger the routine.

As long as the sensor is treated by the hub as a normal contact or motion sensor, Alexa sees clean, simple state transitions and routines work reliably.

2. What “Supervised Mode” Means for Z-Wave Security Sensors

The term “supervised mode” can refer to slightly different mechanisms depending on the brand of hub or alarm panel, but they all share the same goals:

• Ensure the sensor is constantly monitored (not just when it changes state)
• Guarantee reliable delivery of alarm-related messages
• Detect tamper, low battery, or communication loss

Under the hood, this typically involves:

• Use of Z-Wave Supervision Command Class (reliable, acknowledged commands)
• Use of secure inclusion (e.g., S2 Access Control) so all traffic is encrypted
• Periodic check-in / heartbeat communication between sensor and hub
• Treating the device as part of a formal security subsystem (armed/disarmed, monitored)

Once supervised mode is enabled, your hub may reclassify the device internally:
It’s no longer just a generic sensor; it is now a security sensor subject to stricter handling.

That reclassification is exactly where Alexa behavior usually changes.

3. Why Alexa Routines Stop Triggering in Supervised Mode

When Z-Wave security sensors enter supervised mode, several side effects can break or block Alexa routines.

3.1 The Hub Exposes Sensors as “Security System” Devices, Not Plain Sensors

Many hubs and alarm panels treat supervised Z-Wave sensors as part of a security system entity instead of exposing every sensor as a standard contact/motion device to Alexa.

Typical changes include:

• Alexa sees a single “Security System” or “Alarm Panel” device (Arm/Disarm)
• Individual door/window sensors are:
• Hidden from Alexa, or
• Exposed only in a restricted way (alarm vs. normal contact state)

Because Alexa does not receive straightforward open / closed or motion events:

• Existing routines like “When front door opens → turn on light” no longer see a trigger.
• Alexa may show the sensor but not list it under “When this happens” → Smart Home as a valid trigger.

In other words, once those sensors are pulled into the supervised security subsystem, they may lose their “normal sensor” role in Alexa.

3.2 Security Events Are Not Mapped to Alexa’s Routine Triggers

In supervised mode, a sensor can send more than just open/closed:

• Intrusion alarm
• Tamper alert
• Supervision failure
• Battery or health reports

Your hub’s Alexa integration must decide which of these Z-Wave notifications map to Alexa’s supported capabilities. Many integrations:

• Map alarm-style or supervision events to internal security logic only
• Do not translate them into the contactSensor or motionSensor events that Alexa expects for routines

As a result:

• The Z-Wave sensor is working and alarming correctly,
• The hub is receiving those alarms,
• But Alexa never sees a supported trigger event, so your custom routines appear “dead”.

3.3 Amazon’s Security and Privacy Rules Limit Certain Automations

For safety and legal reasons, Amazon places extra restrictions on devices that are:

• Classified as security sensors
• Connected to professional monitoring or formal security systems

These restrictions can include:

• Blocking certain routine triggers from security feeds
• Blocking sensitive actions (e.g., unlock doors, disarm systems) from being fired automatically by those triggers
• Limiting how often or how granularly security-related data is passed to Alexa

If your Z-Wave sensors become part of a supervised, possibly monitored security system, the Alexa skill may intentionally reduce or reshape what is exposed so it complies with Amazon’s policies. That can silently break automations that were created when the same devices were treated as “plain smart home sensors”.

3.4 Driver / Device-Type Changes Inside the Hub

In many Z-Wave hubs (SmartThings, Hubitat, Home Assistant with Z-Wave JS, etc.), entering supervised or secure mode can cause:

• A change in driver / device handler
• A change in which Z-Wave command classes are used for reporting
• A change in device category (e.g., “Access Control Sensor” → “Security Sensor”)

If the new driver:

• Uses Notification reports instead of Basic/Binary Sensor reports, or
• Labels the device as a security-only capability,

the Alexa Skill may no longer recognize it as a valid trigger source. Again, the sensor is fine, the mapping layer is what changed.

4. How to Confirm Supervised Mode Is Breaking Your Alexa Routines

To avoid guessing, you can verify the behavior with a few checks.

4.1 Check the Device Type in the Alexa App

1. Open the Alexa app.
2. Go to Devices → All Devices.
3. Tap the sensor that used to trigger routines.

Look for:

• How Alexa labels the device:
• “Contact Sensor” or “Motion Sensor” (good sign), or
• Some generic or security-related label with limited options.
• Whether it appears under Routines → When this happens → Smart Home as a trigger source.

If the sensor no longer shows up (or shows up but doesn’t allow “open/close” as a trigger), it is now exposed differently to Alexa.

4.2 Use Hub Logs or Device Details

On your Z-Wave hub:

• Open the live logs or event history for that sensor.
• Trigger the sensor (open door, move in front of PIR).
• Confirm that:
• The hub sees the event correctly (open/close, motion), and
• The Alexa Skill is still linked and online.

If the hub logs show events but Alexa does not react, the problem is between the hub and Alexa (capability mapping or security classification), not in the Z-Wave radio layer itself.

5. How to Fix or Work Around the Problem

You typically have three broad options, depending on how much you are willing to change your setup.

5.1 Expose the Sensors to Alexa as Generic Devices (When Safe)

Many hubs allow you to decide whether:

• A Z-Wave sensor participates in the security subsystem, and
• That same sensor is also exposed to smart home integrations as a generic contact or motion sensor.

Possible approaches (exact steps vary by platform):

• Disable “security-only” mode for specific sensors that you want to use strictly for automations (e.g., interior door used only for lighting).
• Change the device’s driver / type back to a generic:
• “Contact Sensor”
• “Door/Window Sensor”
• “Motion Sensor”
• In the hub’s Alexa (or cloud) integration settings, select those devices explicitly as exposed to Alexa as standard sensors.

Important:

• Do this only for sensors where it is acceptable that they are treated like general-purpose devices.
• For perimeter entry sensors fully tied to an alarm panel or professional monitoring, your options may be limited by the vendor’s security policy.

5.2 Run the Main Logic on the Hub and Use Virtual Sensors for Alexa

If your hub is flexible (Hubitat, Home Assistant, advanced alarm panels), you can decouple supervised security from Alexa-friendly triggers:

1. Keep your Z-Wave sensors in supervised/secure mode for maximum reliability and security.
2. Create a virtual contact or motion sensor in the hub.
3. Expose only the virtual sensor to Alexa.
4. On the hub, set up an automation:
• When real supervised sensor changes (e.g., front door opens),
• Toggle the virtual sensor to “open” (or “motion detected”).

Now:

• Alexa routines listen to the virtual sensor, which behaves like a normal device.
• Your real Z-Wave security sensor stays fully supervised, encrypted, and part of the alarm logic.
• The hub acts as the “translator” between supervised alarms and Alexa’s simple smart home triggers.

This is often the cleanest and safest method.

5.3 Separate “Security” Sensors From “Convenience” Sensors

If you are designing or expanding your system, consider splitting roles:

• Security-only sensors:
• Perimeter contacts, glass-breaks, life-safety detectors
• Fully supervised, might not be exposed to Alexa at all
• Automation / convenience sensors:
• Hallway motion for lights
• Interior doors for announcements
• Exposed to Alexa as plain smart home sensors

By not overloading security sensors with automation tasks, you avoid running into supervised-mode limitations and policy constraints.

5.4 General Troubleshooting Steps

In addition to the structural changes above, verify basics:

• Update firmware on:
• Z-Wave hub or alarm panel
• Z-Wave devices (if supported)
• Re-link the Alexa Skill for your hub to refresh capability mappings.
• Remove and re-add the affected sensor to the hub (carefully, so you don’t break the whole security configuration).
• Check vendor documentation or support articles for known issues regarding:
• “Supervised mode”
• Alexa integration
• S2 secure inclusion and device categories

6. Are There Risks in Disabling or Bypassing Supervised Mode?

Yes, there can be trade-offs.

Supervised mode and secure inclusion exist to:

• Ensure reliable alarm reporting
• Detect dead or missing sensors
• Protect against spoofing and tampering

If you:

• Remove a sensor from the supervised security subsystem
• Or force it to use a more generic driver just for the sake of Alexa routines

you may:

• Lose monitoring of check-ins or supervision faults
• Make that sensor ineligible for professional monitoring
• Slightly weaken the overall attack surface of your security system

For that reason, the virtual sensor pattern (Section 5.2) is often recommended:
You keep the real sensor supervised and secure but present a clean, non-sensitive abstraction to Alexa for convenience automations.

 

7. Summary

Alexa custom routines usually stop working when Z-Wave security sensors enter supervised mode because:

• The hub starts treating them as part of a formal security subsystem, not as generic smart home devices.
• Security-related events are no longer mapped to the simple contact/motion capabilities that Alexa routines expect.
• Amazon’s security and privacy policies limit how those supervised sensors can be used as routine triggers.
• Driver/type changes in the hub alter what Alexa sees.

To restore stable behavior without compromising security:

• Prefer keeping security sensors supervised and use virtual devices as Alexa triggers, or
• Expose only non-critical sensors to Alexa as generic devices, and
• Always respect the safety implications of weakening supervision for any sensor involved in intrusion or life-safety protection.