Addition of the Silvercrest (Lidl) smart button over zigbee2mqtt

[Mrcuddles]

Blueprint Checklist

• [x] You viewed the README and conformed to the naming conventions
• [x] You ordered the actions as stated in the README action order
• [x] All filenames are lowercase and uses '-' for spaces and not '_' while using {service-name}-{switch-name-or-type}.yaml format
• [x] Images are png
• [x] Image backgrounds are transparent and is cropped to the device boundries
• [x] Images has a maximum width of 800px and maximum height of 500px
• [x] There are no missing buttons or actions
• [x] Your integration/service is running on the latest version
• [x] You have tested your blueprints and made sure each button and action works

[Sian-Lee-SA]

You will need to fix the titiles to the naming convention. Also could you explain the difference between the two hold actions?

[Sian-Lee-SA]

Also the button height doesn't need to be in there for shape circle... Infact no position/shape is needed for single buttons

[Mrcuddles]

This button is slightly confusing. When it's pressed once (payload on) and you then hold the button it will send the following:

info 2023-01-11 20:57:54MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'on' info 2023-01-11 20:57:59MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_up' info 2023-01-11 20:58:00MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_up' info 2023-01-11 20:58:01MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_up' info 2023-01-11 20:58:02MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_down' info 2023-01-11 20:58:03MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_down' info 2023-01-11 20:58:04MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_down' info 2023-01-11 20:58:05MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_down' info 2023-01-11 20:58:05MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_up' info 2023-01-11 20:58:06MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_up' info 2023-01-11 20:58:07MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_up' info 2023-01-11 20:58:08MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_up' info 2023-01-11 20:58:09MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_down' info 2023-01-11 20:58:10MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_down' info 2023-01-11 20:58:11MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_down' info 2023-01-11 20:58:12MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_down' info 2023-01-11 20:58:13MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_up' info 2023-01-11 20:58:14MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_step_up' info 2023-01-11 20:58:14MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_stop'

It will loop 3x up, 4x down, 4x up, 4x down, 4x up, etc until you release the button which sends a brightness_stop.

When the button is double pressed (payload off) it will do the following: info 2023-01-11 21:01:02MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'off' info 2023-01-11 21:01:09MQTT publish: topic 'zigbee2mqtt/Badkamer knop/action', payload 'brightness_stop'

No brightness_step_up nor brightness_step_down, just brightness_stop after releasing.

This behavior isn't documented anywhere, but useful. Do you have any advice in detailing this behavior to the end user?

[Sian-Lee-SA]

Yh i did a bit of research after seeing this pull request and the FW for the device is a bit weird. Just want to make the parts in backets ( ) shorter really and hold release should be hold (released)... The problem with switches and blueprints for them is that some devices are just not following a norm (Ikea does this too sometimes). I see it that if a person already owns that device, then they should be aware that you need to do 4x up and 4x down etc. so is there a more generic way to say just up or down etc.?

[Mrcuddles]

What do you think of this?

[Sian-Lee-SA]

That's better, Just one more thing, the latest update I have invalidated blueprints with the shape param because it's not needed and people leave it in with extra params that don't relate to their shape. So just remove the shape: circle then I can merge.

On second look, you need to remove all params relating to a shape as I have also invalidated single button switches to have no shape params as it's simply not needed and redundant.

[Mrcuddles]

Here you go :)

[Sian-Lee-SA]

Thank You!