So, basically. When you turn your lights on with the HA app (or any way but the lidl button), and then want to change the brightness with the lidl button, you first have to turn it on (again) using the lidl button with a single click. And then hold it for brightness sweep?
I’d agree it’s not perfect, but still usable I guess.
Hi all, Could you help a noob?
I bought the Lidl Smart Button and add this to HA. It is add to HA but i dont see the button clicked. Battery is shown. But the Action is null or sometimes n/a.
I have tried ZHA and Zigbee2mqtt,
Is there a setting/configuration im missing?
btw: this is my second button, i replaced the first one because i thought i was broken.
Thanks in advance.
I just ordered one. Will let you know when it arrives and I get it to work.
This got me confused as well. If you check in the log you will find that it sends the following:
Info <small>2022-12-01 19:52:13</small>`MQTT publish: topic 'zigbee2mqtt/button_kitchen', payload '{"action":"on","battery":100,"linkquality":191}'`
Info <small>2022-12-01 19:52:13</small>`MQTT publish: topic 'zigbee2mqtt/button_kitchen', payload '{"action":"","battery":100,"linkquality":191}'`
Info <small>2022-12-01 19:52:13</small>`MQTT publish: topic 'zigbee2mqtt/button_kitchen/action', payload 'on'`
So in Zigbee2mqtt you just see it flash and the action remains empty, but it’s really fast and actually sends the ‘on’ action and then quickly going back to a empty value.
As for people wanting to change the brightness, I assumed (pretty native in hindsight) that you could actually turn the button to control the brightness. Turns out, it has a hold-action which cycles through several ‘brightness_step_up’ and ‘brightness_step_down’ actions. Actually, 4 times up, then 4 times down, then 4 times up, etc. So, I made three automations: One to turn the light on/off, one turn the brightness down and one turn the brightness up. So holding the button now will update the light through several brightness states. If you like the brightness you got, let go of the button:
- id: 'on_off bathroom'
alias: Button bathroom (on/off)
description: ''
trigger:
- platform: state
entity_id:
- sensor.button_bathroom_action
to: 'on'
condition: []
action:
- service: light.toggle
data: {}
target:
entity_id: light.bathroom
mode: single
- id: 'brightness_up bathroom'
alias: Button bathroom (brightness up)
description: ''
trigger:
- platform: state
entity_id:
- sensor.button_bathroom_action
to: brightness_step_up
condition: []
action:
- service: light.turn_on
data:
brightness_step: 50
target:
entity_id: light.bathroom
mode: single
- id: 'brightness_down bathroom'
alias: Button bathroom (brightness down)
description: ''
trigger:
- platform: state
entity_id:
- sensor.button_bathroom_action
to: brightness_step_down
condition: []
action:
- service: light.turn_on
data:
brightness_step: -50
target:
entity_id: light.bathroom
mode: single
Hope this helps
Where do you check the action state? In Z2MQTT, or in the HA Logbook?
I received mine today and it worked out of the box:
Then, in the HA Logbook (so not in Z2MQTT), it shows the states correctly. When I click it once, the action becomes “on” and immediately after that " ".
Then I used automations to control my devices:
Tomorrow I will add an automation for the brightness. But I want to do it a little differently than Milenco’s example. When it receives a “brightness down” or “brightness up”, I want it to start sweeping the brightness up and down in steps of 1% and stop when it receives “brightness stop”.
But I have to figure out first how to play with time in the automations. In pseudo-code, I’d like it to be something like:
if(brightness_up OR brightness_down)
{
step = 1%
while(action != brightness_stop)
{
if(brightness == 100%)
{
step = -1%
}
if(brightness == 0%)
{
step = 1%
}
brightness = brightness + step
delay(0.1s)
}
}
That should give a smooth brightness sweep up and down until you release the button.
When I get that to work nicely I’ll add it here as an example.
Hi Milenco, Istria1704,
Thank you for the info. I thought it would stay on “on” or “off”. i will check the HA log. I this works, i will look at the brightnes.
I may come back at you for addvice.
That is what I expected initially as well. But it is more like a “pulse” of the command than a permanent state change. So you just use it as a trigger for an automation.
Good luck!
Showing the same problem, found the battery in my H.A.
Nothing on the buton action that comes along in automation.
I’m using the Conbee II / Deconz integration. Reading about a need (must) to have Zigbee2mqtt.
In H.A. logs i see of every 10’s attempt: fired event 1002 or fired event 1004
How to get this buton working in my H.A.? What needs to be created where… need some guidance
By “HA logs”, do you mean the HA Logbook? Or the logfile?
I have no experience with Deconz integration. It works for me with the Sonoff USB Zigbee stick and Zigbee2MQTT. After pairing it there, the button clicks show up on the HA Logbook (“Logbook” in the sidebar menu) page.
By default, Zigbee2MQTT gives it an “unfriendly” device name. Maybe Deconz does the same and that is why you can’t find it?
The “Logboek” page as it’s called in my gui. all i see is Knop1 (that’s the name i gave it in the Conbee II stick gui) fired event 1002 i’ve also seen event number 1004.
In de DeCONZ log’s i can see the signal event/the id’s etc. as:
19:27:55:145 [INFO] - Button 1002 - TS004F, unicast to: 0x0000, endpoint: 0x01, cluster: ONOFF (0x0006), action: B1 short, payload: 00, zclSeq: 83
19:27:55:184 Websocket 10.10.xxx.yyy:ppppp send message: {“attr”:{“id”:“19”,“lastannounced”:null,“lastseen”:“2022-12-06T18:27Z”,“manufacturername”:"_TZ3000_rco1yzb1",“modelid”:“TS004F”,“name”:“Knop1”,“swversion”:null,“type”:“ZHASwitch”,“uniqueid”:“2c:11:65:ff:fe:c7:39:48-01-0006”},“e”:“changed”,“id”:“19”,“r”:“sensors”,“t”:“event”,“uniqueid”:“2c:11:65:ff:fe:c7:39:48-01-0006”} (ret = -1091502072)
But when i want to automated something i’ve only the Knop1 als apparaat and it provices the trigger batterij level changed. so it looks like somewhen I need to write code to get this event moved into an action but not on the automation / blueprint but making a script from scratch.
And do these “fired event 1002” correspond with your button presses? So when you have the “Logboek” open and you press the button, do you see that event happen in real time?
This is how it looks on my side:
This is how I’m using the button. Im using the “on” state to toggle the lights and the “off” state to switch between full and dimmed light:
alias: Office Button Ambiance
description: ""
trigger:
- platform: device
domain: mqtt
device_id: xxx
type: action
subtype: "off"
discovery_id: xxx action_off
condition: []
action:
- if:
- condition: numeric_state
entity_id: light.office_spots
attribute: brightness
above: 99
then:
- service: light.turn_on
data:
brightness_pct: 10
target:
entity_id: light.office_spots
else:
- service: light.turn_on
data:
brightness_pct: 100
target:
entity_id: light.office_spots
mode: single
Perhaps nice to know the button seems to have a lock-mode.
When pressing the button 3 times, the button with signal a led when pressing, but actually won’t send anything to the zigbee controller.
Learned the hard way when the button stopped working.
So when the button seems to stop working; just press the button 3 times and check again.
Works like a charm, thanks!
This is an easy way to let a switch change between on/off after eacha single click on the LIDL smart button (SW2). Works fine with Sonoff Zigbee 3.0 USB & Zigbee Home Automation.
Peter
Knop1 fired event ‘Short press’ : is what i see in the log of H.A. 
so it receives something…and shows battery: 
But getting this log in something usefull (not having MQTT but Conbee II/Deconz integration is still a puzzle2me.
Took me some days, but it’s working.
Created the automation from the battery entry:
Then selected automation and added a rule 
Default 2 actions on pressing the button (short and long)
So out of the box H.A. and using Conbee II
Thanks for the support and patience on this.
Thanks4this. I experienced this too. Also when starting with a new button out-of-the-box. First thougth it was a DOA. but using this tip it started working 
Thanks. It also works this way in Node-Red.
Some extra information (also from the manual):
When you press the button 3 times it switches from a “remote switch and dimmer” to “scene linkgage function”.
I tried to repair it in this mode but then nothing works anymore. No entities are detected and switching back to “remote mode” does nothing. So repairing in “remote mode” was the solution to get it back.
So if someone is stuck with a device in this state it may help.
