Philips Hue Wall Module + Home Assistant: light turns off when the module goes to sleep — workaround?

Configuration Zigbee
1

I’m running into a persistent issue with a Philips Hue Wall Module paired to Home Assistant. The module is battery-powered, and after a period of inactivity it drops into its sleep mode, which also cuts the light. I’ve tried several things to fix this (different pairing methods, adjusting reporting/polling settings, checking binding to the light group) but haven’t been able to get it working reliably.

For comparison, I have a Sonoff ZBMINI installed elsewhere and that one behaves much better in the same setup, no sleep-related dropouts.

I still have this Hue Wall Module lying around unused, and I’d rather not write it off if there’s a known fix or workaround. Has anyone gotten a battery-powered Hue Wall Module to behave consistently with Home Assistant, or found a setting that prevents this sleep-then-lights-out behavior? Which integration are you using (ZHA, deCONZ, Zigbee2MQTT), and did that make a difference?

Any pointers welcome before I give up on it for good.

2

  1. How do you have the device paired to HA?

  2. Are you running the Phillips Hue intergration, ZHA, Z2M or a combo or them?

Your previous posts referenced using both Z2M and the Hue Bridge intergration.

3

Do the activity logs say what turned off the lights? It could very well be an badly configured automation tht does not take into account the situation when entities go unavailable.

4

Great point!

@patrickwit93 I have 10+ battery powered Hue devices intergrated into HA via Z2M with no Automation trigger issues. The state of those devices are the Automation triggers to boot!

unavailable won’t come into play if the automation trigger is defined specifically by state

triggers:
  - entity_id: binary_sensor.xxxx_occupancy
    from: 'off'
    id: motion_on
    to: 'on'
    trigger: state
  - entity_id: binary_sensor.xxxx_occupancy
    from: 'on'
    id: motion_off
    to: 'off'
    trigger: state
5

To bring everyone up to speed on the full picture: I’m running the Philips Hue Wall Switch Module through Zigbee2MQTT, not the Hue Bridge integration, that got cleaned up early on after I realized having both active at once was probably muddying the troubleshooting. The button-to-action mapping comes from the RDM004 blueprint linked earlier in this thread, so the automation logic itself isn’t something I built from scratch.

The problem I keep running into is that the light reliably goes out about five minutes after the last button press, no matter what state I leave it in. My first assumption was that the module was simply dropping into its battery sleep mode and taking the light down with it, since that’s the behavior I’d seen and couldn’t get past even after trying different pairing approaches and reporting settings. But watching the switch entity more closely, I noticed that right around that same five-minute mark, its action attribute quietly resets itself to N/A, and the light drops at almost exactly that moment.

That timing lines up too well to be a coincidence, so my current theory is that this isn’t a sleep or hardware issue at all, it’s an automation reacting to that N/A reset as if it were a genuine button press. If the trigger in the blueprint or in my own setup is listening for any change on that entity rather than a specific value, the reset would fire it every time, five minutes after the fact, completely independent of the actual sleep behavior of the module.

What I still don’t know is whether that N/A reset is something the Hue module itself sends, or just Z2M clearing a stateless attribute after a timeout with nothing actually happening on the device side. If it’s the latter, the fix is probably in tightening up the automation trigger rather than anything to do with the module’s battery or sleep behavior. If anyone else running this same combination, RDM004, Z2M, and this blueprint, has run into the same five-minute pattern, I’d be glad to hear whether that reset is expected and harmless or worth chasing further.

6

I’ll get one and test it, what’s the model number you currently have?

Looks discontinued where I am at… I think the age of your device is your primary issue.

The newer Hue Bridges no longer supports it. Shelly is probably your best alternative!

7

I’ve read this thread 4 times & don’t see any links to the blueprint you’re using. Is it this one?

8

Sorry, and yes Thats the blueprint

9

IMG6266
IMG62661179×2556 228 KB

Right know if i want to make de switch smart I use de sonoff zbminir2 which works fine.

But the hue ones are from the past when I only had a bridge in my old house

10

Go press the button on the switch, wait 5 minutes for your bulb to go off, then download the automation trace & post it here

11

{
“trace”: {
“last_step”: “action/0”,
“run_id”: “bc27e532da62d5256f2d51aa29f363e3”,
“state”: “stopped”,
“script_execution”: “finished”,
“timestamp”: {
“start”: “2026-08-15T10:22:54.825354+00:00”,
“finish”: “2026-08-15T10:22:54.873722+00:00”
},
“domain”: “automation”,
“item_id”: “1780402807244”,
“trigger”: “mqtt topic zigbee2mqtt/Hue wall switch eettafel/action”,
“trace”: {
“trigger/0”: [
{
“path”: “trigger/0”,
“timestamp”: “2026-08-15T10:22:54.825487+00:00”,
“changed_variables”: {
“this”: {
“entity_id”: “automation.lamp_eettafel_uit”,
“state”: “on”,
“attributes”: {
“id”: “1780402807244”,
“last_triggered”: “2026-08-14T20:30:25.027779+00:00”,
“mode”: “single”,
“current”: 0,
“friendly_name”: “Lamp eettafel uit”
},
“last_changed”: “2026-08-15T01:59:58.859616+00:00”,
“last_reported”: “2026-08-15T01:59:58.859616+00:00”,
“last_updated”: “2026-08-15T01:59:58.859616+00:00”,
“context”: {
“id”: “01M01JBE4BJTTMJT393HBVDW6X”,
“parent_id”: null,
“user_id”: null
}
},
“trigger”: {
“id”: “0”,
“idx”: “0”,
“alias”: null,
“platform”: “mqtt”,
“topic”: “zigbee2mqtt/Hue wall switch eettafel/action”,
“payload”: “left_hold_release”,
“qos”: 0,
“description”: “mqtt topic zigbee2mqtt/Hue wall switch eettafel/action”
}
}
}
],
“action/0”: [
{
“path”: “action/0”,
“timestamp”: “2026-08-15T10:22:54.826412+00:00”,
“changed_variables”: {
“context”: {
“id”: “01M02F4AV92HDQJJDCZW387DZG”,
“parent_id”: null,
“user_id”: null
}
},
“result”: {
“params”: {
“domain”: “light”,
“service”: “turn_off”,
“service_data”: {
“transition”: 2,
“entity_id”: [
“light.eettafal_lamp”
]
},
“target”: {
“entity_id”: [
“light.eettafal_lamp”
]
}
},
“running_script”: false
}
}
]
},
“config”: {
“id”: “1780402807244”,
“alias”: “Lamp eettafel uit”,
“description”: “”,
“triggers”: [
{
“domain”: “mqtt”,
“device_id”: “b65eb4972d4d9eb029118dc2494d2b0c”,
“type”: “action”,
“subtype”: “left_hold_release”,
“trigger”: “device”
}
],
“conditions”: ,
“actions”: [
{
“action”: “light.turn_off”,
“metadata”: {},
“data”: {
“transition”: 2
},
“target”: {
“entity_id”: “light.eettafal_lamp”
}
}
],
“mode”: “single”
},
“blueprint_inputs”: null,
“context”: {
“id”: “01M02F4AV92HDQJJDCZW387DZG”,
“parent_id”: null,
“user_id”: null
}
},
“logbookEntries”: [
{
“name”: “Lamp eettafel uit”,
“message”: “triggered by mqtt topic zigbee2mqtt/Hue wall switch eettafel/action”,
“source”: “mqtt topic zigbee2mqtt/Hue wall switch eettafel/action”,
“entity_id”: “automation.lamp_eettafel_uit”,
“context_id”: “01M02F4AV92HDQJJDCZW387DZG”,
“domain”: “automation”,
“when”: 1786789374.8257961
},
{
“state”: “off”,
“entity_id”: “light.lamp_eettafel_2”,
“when”: 1786789374.9435143,
“context_event_type”: “automation_triggered”,
“context_domain”: “automation”,
“context_name”: “Lamp eettafel uit”,
“context_message”: “triggered by mqtt topic zigbee2mqtt/Hue wall switch eettafel/action”,
“context_source”: “mqtt topic zigbee2mqtt/Hue wall switch eettafel/action”,
“context_entity_id”: “automation.lamp_eettafel_uit”
},
{
“state”: “off”,
“entity_id”: “light.0x001788010b7fdace”,
“when”: 1786789375.082693,
“context_event_type”: “automation_triggered”,
“context_domain”: “automation”,
“context_name”: “Lamp eettafel uit”,
“context_message”: “triggered by mqtt topic zigbee2mqtt/Hue wall switch eettafel/action”,
“context_source”: “mqtt topic zigbee2mqtt/Hue wall switch eettafel/action”,
“context_entity_id”: “automation.lamp_eettafel_uit”
},
{
“state”: “on”,
“entity_id”: “light.lamp_eettafel_2”,
“when”: 1786789375.102062,
“context_event_type”: “automation_triggered”,
“context_domain”: “automation”,
“context_name”: “Lamp eettafel uit”,
“context_message”: “triggered by mqtt topic zigbee2mqtt/Hue wall switch eettafel/action”,
“context_source”: “mqtt topic zigbee2mqtt/Hue wall switch eettafel/action”,
“context_entity_id”: “automation.lamp_eettafel_uit”
},
{
“state”: “off”,
“entity_id”: “light.lamp_eettafel_1”,
“when”: 1786789375.1118352,
“context_event_type”: “automation_triggered”,
“context_domain”: “automation”,
“context_name”: “Lamp eettafel uit”,
“context_message”: “triggered by mqtt topic zigbee2mqtt/Hue wall switch eettafel/action”,
“context_source”: “mqtt topic zigbee2mqtt/Hue wall switch eettafel/action”,
“context_entity_id”: “automation.lamp_eettafel_uit”
},
{
“state”: “on”,
“entity_id”: “light.0x001788010b7fdace”,
“when”: 1786789375.4369428,
“context_event_type”: “automation_triggered”,
“context_domain”: “automation”,
“context_name”: “Lamp eettafel uit”,
“context_message”: “triggered by mqtt topic zigbee2mqtt/Hue wall switch eettafel/action”,
“context_source”: “mqtt topic zigbee2mqtt/Hue wall switch eettafel/action”,
“context_entity_id”: “automation.lamp_eettafel_uit”
}
]
}

12

Looks like left_hold_release event is being fired. What is the blueprint set to do when left_hold_release is triggered? Is it set to turn off the light?

13

I just saw that i i dont used it anymore Maybe because it didnt works. No my automation to turn lights of is

IMG6279
IMG62791179×2556 223 KB