Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Paulmann Zigbee Switch 501.34 #6102

Closed
carstenph1 opened this issue Jun 2, 2022 · 54 comments
Closed

Paulmann Zigbee Switch 501.34 #6102

carstenph1 opened this issue Jun 2, 2022 · 54 comments

Comments

@carstenph1
Copy link

carstenph1 commented Jun 2, 2022

Device

  • Product name: Zigbee Wandschalter On/Off/Dimm
  • Manufacturer: Paulman LichtGmbH
  • Model identifier: 501.34
  • Device type : Switch

Screenshots

Basic

grafik

Power Configuration

grafik

Identify

grafik

Diagnostics

grafik

ZLL Commissioning

grafik

Node Info

grafik

@Mimiix
Copy link
Collaborator

Mimiix commented Jun 3, 2022

Missing screenshots.

@carstenph1
Copy link
Author

I added the complete available information on cluster information.

@carstenph1
Copy link
Author

@Mimiix are you missing any further details?

@Mimiix
Copy link
Collaborator

Mimiix commented Jun 14, 2022

Woops, sorry! Missed your comment. Looks good :)

@github-actions
Copy link
Contributor

github-actions bot commented Jul 6, 2022

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Jul 6, 2022
@LilYea
Copy link

LilYea commented Jul 7, 2022

Is there progress yet?

@github-actions github-actions bot removed the stale label Jul 8, 2022
@github-actions
Copy link
Contributor

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Jul 30, 2022
@carstenph1
Copy link
Author

it would be awesome to see this feature in one of the next releases :-)

@github-actions github-actions bot removed the stale label Aug 2, 2022
@github-actions
Copy link
Contributor

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Aug 24, 2022
@carstenph1
Copy link
Author

pushing it again!

@github-actions github-actions bot removed the stale label Aug 29, 2022
@Artur-Fedjukevits
Copy link

I have the same switch. I would also be very grateful to see this device as supported.

@github-actions
Copy link
Contributor

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Sep 23, 2022
@carstenph1
Copy link
Author

@Mimiix is it still planned to include this switch compatibility in one of the next releases?

@Mimiix
Copy link
Collaborator

Mimiix commented Sep 26, 2022

A dev needs to pick it up. Perhaps @Smanar or @SwoopX wants to help out. Otherwise, we are kinda stuck...

@github-actions github-actions bot removed the stale label Sep 27, 2022
@Smanar
Copy link
Collaborator

Smanar commented Sep 27, 2022

Product name: Zigbee Wandschalter On/Off/Dimm

So this device don't have color ?

@carstenph1
Copy link
Author

no. its a switch to turn on/off/dim the light bulbs. there is nothing available to control the color.

@Smanar
Copy link
Collaborator

Smanar commented Sep 27, 2022

So can try with this DDF

{
  "schema": "devcap1.schema.json",
  "manufacturername": "Paulman LichtGmbH",
  "modelid": "501.34",
  "product": "Paulmann Zigbee Switch",
  "sleeper": true,
  "status": "Gold",
  "subdevices": [
    {
      "type": "$TYPE_SWITCH",
      "restapi": "/sensors",
      "uuid": [
        "$address.ext",
        "0x01",
        "0x0006"
      ],
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "config/on"
        },
        {
          "name": "config/reachable"
        },
        {
          "name": "state/buttonevent"
        },
        {
          "name": "config/battery"
        },
        {
          "name": "state/lastupdated"
        }
      ]
    }
  ],
  "bindings": [
    {
      "bind": "unicast",
      "src.ep": 1,
      "cl": "0x0001",
      "report": [
        {
          "at": "0x0021",
          "dt": "0x20",
          "min": 60,
          "max": 3600,
          "change": "0x00000001"
        }
      ]
    },
    {
      "bind": "unicast",
      "src.ep": 1,
      "dst.ep": 1,
      "cl": "0x0006"
    },
    {
      "bind": "unicast",
      "src.ep": 1,
      "dst.ep": 1,
      "cl": "0x0008"
    }
  ]
}

With it the device will be reconized but not working.
Just enable deconz log with "info_l2" in the application / help / debug view
Press all buttons and pls share the result, you will error like

	Line 4570:         DBG_Printf(DBG_INFO_L2, "[INFO] - No button map for: %s%s, endpoint: 0x%02X, cluster: %s, command: %s, payload: %s, zclSeq: %u\n",
	Line 5607:         DBG_Printf(DBG_INFO_L2, "[INFO] - No button handler for: %s%s, endpoint: 0x%02X, cluster: %s, command: %s, payload: %s, zclSeq: %u\n",

We will use them to edit another json file.

@carstenph1
Copy link
Author

thanks Smanar.
I hope I made the import correct. I had to remove a comma in the json, otherwise it did not load.
I imported the json in the DDF Editor of Deconz and ran the debug view with info_l2. but I cant see any output of "no button ...". just "APS-DATA.indication from child 0x32E3" every time I clicked the switch buttons.

here you can find the full debug log
https://pastebin.com/Z9ayZkyy

@Smanar
Copy link
Collaborator

Smanar commented Oct 2, 2022

Ha yes, have removed the comma too.

But it s strange there is still nothing. The node have changed from 0xXXXX to a better name ? To check if the device is now in the API.
You have made a "hot reload" (in the editor menu) after having modified the DDF ?

Else can enable log "aps" to see what is this aps request.

@baaaron
Copy link

baaaron commented Oct 27, 2022

Bought the same switch, just now I realized it isn‘t supported yet :(
Let me know if anything’s still needed to get it supported

@Smanar
Copy link
Collaborator

Smanar commented Oct 28, 2022

Sure can use the same DDF and the button map from the previous post.
Press button and tell me the result.

And BTW if you can confirm me how many endpoint have this device ?

@carstenph1
Copy link
Author

Hello Smanar,
the switch can control two separate endpoints/devices. each side on/off (short press) or dimm brighter/darker (long press). with your current configuration the button map.json I have 6 buttons visible in phoscon html gui.

is this the information you required?

grafik

@Smanar
Copy link
Collaborator

Smanar commented Nov 3, 2022

I have 6 buttons visible in phoscon html gui.

This is "phoscon magic" I haven't impact on it ^^

But I think I miss at least 2 buttons return, as only the on/off use the 2 endpoint

        "PaulmannMap": {
            "vendor": "Paulmann LichtGmbH",
            "doc": "On off remote",
            "modelids": ["501.34"],
            "map": [
                [1, "0x01", "ONOFF", "ON", "0", "S_BUTTON_1", "S_BUTTON_ACTION_SHORT_RELEASED", " B1"],
                [1, "0x01", "ONOFF", "OFF", "0", "S_BUTTON_2", "S_BUTTON_ACTION_SHORT_RELEASED", "B2"],
                [1, "0x02", "ONOFF", "ON", "0", "S_BUTTON_3", "S_BUTTON_ACTION_SHORT_RELEASED", "B3"],
                [1, "0x02", "ONOFF", "OFF", "0", "S_BUTTON_4", "S_BUTTON_ACTION_SHORT_RELEASED", "B4"],
                [1, "0x01", "LEVEL_CONTROL", "MOVE_WITH_ON_OFF", "0", "S_BUTTON_5", "S_BUTTON_ACTION_SHORT_RELEASED", "B5"],
                [1, "0x01", "LEVEL_CONTROL", "STOP_WITH_ON_OFF", "0", "S_BUTTON_6", "S_BUTTON_ACTION_SHORT_RELEASED", "B6"]
            ]
        }

You can see button return in Phoscon/help/API Information/events, and I think you will miss 2 of them.

Probably

                [1, "0x02", "LEVEL_CONTROL", "MOVE_WITH_ON_OFF", "0", "S_BUTTON_7", "S_BUTTON_ACTION_SHORT_RELEASED", "B7"],
                [1, "0x02", "LEVEL_CONTROL", "STOP_WITH_ON_OFF", "0", "S_BUTTON_8", "S_BUTTON_ACTION_SHORT_RELEASED", "B8"]

@github-actions
Copy link
Contributor

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Nov 25, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Dec 9, 2022

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.

@github-actions github-actions bot closed this as completed Dec 9, 2022
@Millhouse273
Copy link

Hi,
I call this button my own and are very thankful for your great work here. After some problems I got it working and can link the buttons to my lights. There is only one thing missing and I didn't figured out fixing it by working me through the button_maps.json. I tried to adopt the dim function, but haven't enough skills to transfer it to the paulmann button.

Now the missing function: I'd like to dimm down with the off-button. dim up is possible with the posted map and the on buttons. Thanks for any response

@Millhouse273
Copy link

Is it possible to get a real dim button? Like the Ikea on/off button with long press controlling the level constantly? Like mentioned before I have no idea off programming all the stuff...

@Smanar
Copy link
Collaborator

Smanar commented Dec 23, 2022

Hello, first you are asking with phoscon or third app ?
From that you are saying you are using direct link with remote and light ? So no automation that use the state/buttonevent ?

You can make a long press on a button and check logs if the device support this action, with info_l2

	Line 4570:         DBG_Printf(DBG_INFO_L2, "[INFO] - No button map for: %s%s, endpoint: 0x%02X, cluster: %s, command: %s, payload: %s, zclSeq: %u\n",
	Line 5607:         DBG_Printf(DBG_INFO_L2, "[INFO] - No button handler for: %s%s, endpoint: 0x%02X, cluster: %s, command: %s, payload: %s, zclSeq: %u\n",

@Millhouse273
Copy link

Hi, thx for your answer.

I'm using the web interface of phoscon. The light is grouped in phoscon an the switch is grouped within this group. I can set an action like on or off to the buttons.
Their is no automation in any other app or phoscon.

I check, if the switch supports long press. In the description is mentioned on/off/dimm...

Thanks a lot for your help so far

@Smanar
Copy link
Collaborator

Smanar commented Jan 3, 2023

Ok so you are not using automation but direct zigbee connexion.

Nothing to programme, the device support it or not ^^. Ha have the good cluster and support group feature

Just try this DDF to enable the group feature on the DDF

{
  "schema": "devcap1.schema.json",
  "manufacturername": "Paulman LichtGmbH",
  "modelid": "501.34",
  "product": "Paulmann Zigbee Switch",
  "sleeper": true,
  "status": "Gold",
  "subdevices": [
    {
      "type": "$TYPE_SWITCH",
      "restapi": "/sensors",
      "uuid": [
        "$address.ext",
        "0x01",
        "0x0006"
      ],
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "config/on"
        },
        {
          "name": "config/reachable"
        },
        {
          "name": "state/buttonevent"
        },
        {
          "name": "config/battery"
        },
        {
            "name": "config/group",
            "default": "auto"
        },
        {
          "name": "state/lastupdated"
        }
      ]
    }
  ],
  "bindings": [
    {
      "bind": "unicast",
      "src.ep": 1,
      "cl": "0x0001",
      "report": [
        {
          "at": "0x0021",
          "dt": "0x20",
          "min": 60,
          "max": 3600,
          "change": "0x00000001"
        }
      ]
    },
    {
        "bind": "groupcast",
        "src.ep": 1,
        "cl": "0x0006",
        "config.group": 0
    },
    {
        "bind": "groupcast",
        "src.ep": 1,
        "cl": "0x0008",
        "config.group": 0
    }
  ]
}

IDK if phoscon will support it natively but the old webapp (in phoscon /help ) will support it.

@Millhouse273
Copy link

Hi,

this is the log from l2.

{"id":"106","lastannounced":"2022-12-31T14:13:04Z","lastseen":"2023-01-04T19:07Z","manufacturername":"Paulmann LichtGmbH","modelid":"501.34","name":"Switch 106","swversion":"2.7.6_r25","type":"ZHASwitch","uniqueid":"b4:e3:f9:ff:fe:14:0d:a5-01-0006"},"e":"changed","id":"106","r":"sensors","t":"event","uniqueid":"b4:e3:f9:ff:fe:14:0d:a5-01-0006"} (ret = 2125021208)
20:07:36:681 Websocket 192.168.: send message: {"e":"changed","id":"106","r":"sensors","state":{"buttonevent":7002,"lastupdated":"2023-01-04T19:07:36.676"},"t":"event","uniqueid":"b4:e3:f9:ff:fe:14:0d:a5-01-0006"} (ret = 2125021208)
20:07:36:682 Websocket 192.168.: send message: {"e":"changed","id":"106","r":"sensors","state":{"buttonevent":7002,"lastupdated":"2023-01-04T19:07:36.676"},"t":"event","uniqueid":"b4:e3:f9:ff:fe:14:0d:a5-01-0006"} (ret = 2125021208)
20:07:36:686 Websocket 192.168.: send message: {"e":"changed","id":"16","r":"lights","state":{"alert":null,"bri":254,"on":true,"reachable":true},"t":"event","uniqueid":"00:17:88:01:08:a4:01:8d-0b"} (ret = 150)


{"id":"106","lastannounced":"2022-12-31T14:13:04Z","lastseen":"2023-01-04T19:09Z","manufacturername":"Paulmann LichtGmbH","modelid":"501.34","name":"Switch 106","swversion":"2.7.6_r25","type":"ZHASwitch","uniqueid":"b4:e3:f9:ff:fe:14:0d:a5-01-0006"},"e":"changed","id":"106","r":"sensors","t":"event","uniqueid":"b4:e3:f9:ff:fe:14:0d:a5-01-0006"} (ret = 2125021208)
20:09:22:369 Websocket 192.168.: send message: {"attr":{"id":"106","lastannounced":"2022-12-31T14:13:04Z","lastseen":"2023-01-04T19:09Z","manufacturername":"Paulmann LichtGmbH","modelid":"501.34","name":"Switch 106","swversion":"2.7.6_r25","type":"ZHASwitch","uniqueid":"b4:e3:f9:ff:fe:14:0d:a5-01-0006"},"e":"changed","id":"106","r":"sensors","t":"event","uniqueid":"b4:e3:f9:ff:fe:14:0d:a5-01-0006"} (ret = 2125021208)

Long press on the off Button did no log. Don't know why...

@Smanar
Copy link
Collaborator

Smanar commented Jan 5, 2023

{"buttonevent":7002

??? The button map go only to button 6 maximum

        "PaulmannMap": {
            "vendor": "Paulmann LichtGmbH",
            "doc": "On off remote",
            "modelids": ["501.34"],
            "map": [
                [1, "0x01", "ONOFF", "ON", "0", "S_BUTTON_1", "S_BUTTON_ACTION_SHORT_RELEASED", " B1"],
                [1, "0x01", "ONOFF", "OFF", "0", "S_BUTTON_2", "S_BUTTON_ACTION_SHORT_RELEASED", "B2"],
                [1, "0x02", "ONOFF", "ON", "0", "S_BUTTON_3", "S_BUTTON_ACTION_SHORT_RELEASED", "B3"],
                [1, "0x02", "ONOFF", "OFF", "0", "S_BUTTON_4", "S_BUTTON_ACTION_SHORT_RELEASED", "B4"],
                [1, "0x01", "LEVEL_CONTROL", "MOVE_WITH_ON_OFF", "0", "S_BUTTON_5", "S_BUTTON_ACTION_SHORT_RELEASED", "B5"],
                [1, "0x01", "LEVEL_CONTROL", "STOP_WITH_ON_OFF", "0", "S_BUTTON_6", "S_BUTTON_ACTION_SHORT_RELEASED", "B6"]
            ]

Long press on the off Button did no log. Don't know why...

Generaly this button don't have long press, its on or off, no utility to use a long press.

But on your side you want to use direct link, so you will not need buttonevent return, just need to check if the device create a "switch group" to be able to put light on it.

And you need to have in log for all button reconized (for with "info" only this time, sorry)

DBG_Printf(DBG_INFO, "[INFO] - Button %u - %s%s, endpoint: 0x%02X, cluster: %s, action: %s, payload: %s, zclSeq: %u\n",

You will have the "action" on this log it the last field in the buttonmap.

@NurNano
Copy link

NurNano commented Jul 3, 2023

Hey,
thank you all for your work. I looked over it with my new Switch and found out, some Keybindings were missing.
I did some try/error and optimized the button_maps.

Here for you to test:

        "PaulmannMap": {
            "vendor": "Paulmann LichtGmbH",
            "doc": "On off remote",
            "modelids": ["501.34"],
            "buttons": [
                {"S_BUTTON_1": "ON Left"},
                {"S_BUTTON_2": "OFF Left"},
                {"S_BUTTON_3": "ON Right"},
                {"S_BUTTON_4": "OFF Right"}
            ],
            "map": [
                [1, "0x01", "ONOFF", "ON", "0", "S_BUTTON_1", "S_BUTTON_ACTION_SHORT_RELEASED", "ON Left"],
                [1, "0x01", "ONOFF", "OFF", "0", "S_BUTTON_2", "S_BUTTON_ACTION_SHORT_RELEASED", "OFF Left"],
                [1, "0x02", "ONOFF", "ON", "0", "S_BUTTON_3", "S_BUTTON_ACTION_SHORT_RELEASED", "ON Right"],
                [1, "0x02", "ONOFF", "OFF", "0", "S_BUTTON_4", "S_BUTTON_ACTION_SHORT_RELEASED", "OFF Right"],
                [1, "0x01", "LEVEL_CONTROL", "MOVE_WITH_ON_OFF", "0", "S_BUTTON_1", "S_BUTTON_ACTION_SHORT_RELEASED", "Dim Up Left"],
                [1, "0x01", "LEVEL_CONTROL", "STOP_WITH_ON_OFF", "0", "S_BUTTON_1", "S_BUTTON_ACTION_SHORT_RELEASED", "Stop Dim"],
                [1, "0x01", "LEVEL_CONTROL", "MOVE_WITH_ON_OFF", "1", "S_BUTTON_2", "S_BUTTON_ACTION_SHORT_RELEASED", "Dim Down Left"],
                [1, "0x01", "LEVEL_CONTROL", "STOP_WITH_ON_OFF", "1", "S_BUTTON_2", "S_BUTTON_ACTION_SHORT_RELEASED", "Stop Dim"],
                [1, "0x02", "LEVEL_CONTROL", "MOVE_WITH_ON_OFF", "0", "S_BUTTON_3", "S_BUTTON_ACTION_SHORT_RELEASED", "Dim Up Right"],
                [1, "0x02", "LEVEL_CONTROL", "STOP_WITH_ON_OFF", "0", "S_BUTTON_3", "S_BUTTON_ACTION_SHORT_RELEASED", "Stop Dim"],
                [1, "0x02", "LEVEL_CONTROL", "MOVE_WITH_ON_OFF", "1", "S_BUTTON_4", "S_BUTTON_ACTION_SHORT_RELEASED", "Dim Down Right"],
                [1, "0x02", "LEVEL_CONTROL", "STOP_WITH_ON_OFF", "1", "S_BUTTON_4", "S_BUTTON_ACTION_SHORT_RELEASED", "Stop Dim"]
            ]
        }

With this I got all Keys recognized.

EDIT:

After some testing i got stuck in my openhab and it seems to be needed to add some more Buttons to access all of the Keys in Openhab due to only get the Pressed Button ID delivered.
So I just edited my Binding to:

        "PaulmannMap": {
            "vendor": "Paulmann LichtGmbH",
            "doc": "On off remote",
            "modelids": ["501.34"],
            "buttons": [
                {"S_BUTTON_1": "ON Left"},
                {"S_BUTTON_2": "OFF Left"},
                {"S_BUTTON_3": "ON Right"},
                {"S_BUTTON_4": "OFF Right"},
                {"S_BUTTON_5": "ON Left long"},
                {"S_BUTTON_6": "OFF Left long"},
                {"S_BUTTON_7": "ON Right long"},
                {"S_BUTTON_8": "OFF Right long"}
            ],
            "map": [
                [1, "0x01", "ONOFF", "ON", "0", "S_BUTTON_1", "S_BUTTON_ACTION_SHORT_RELEASED", "ON Left"],
                [1, "0x01", "ONOFF", "OFF", "0", "S_BUTTON_2", "S_BUTTON_ACTION_SHORT_RELEASED", "OFF Left"],
                [1, "0x02", "ONOFF", "ON", "0", "S_BUTTON_3", "S_BUTTON_ACTION_SHORT_RELEASED", "ON Right"],
                [1, "0x02", "ONOFF", "OFF", "0", "S_BUTTON_4", "S_BUTTON_ACTION_SHORT_RELEASED", "OFF Right"],
                [1, "0x01", "LEVEL_CONTROL", "MOVE_WITH_ON_OFF", "0", "S_BUTTON_5", "S_BUTTON_ACTION_SHORT_RELEASED", "Dim Up Left"],
                [1, "0x01", "LEVEL_CONTROL", "STOP_WITH_ON_OFF", "0", "S_BUTTON_5", "S_BUTTON_ACTION_SHORT_RELEASED", "Stop Dim"],
                [1, "0x01", "LEVEL_CONTROL", "MOVE_WITH_ON_OFF", "1", "S_BUTTON_6", "S_BUTTON_ACTION_SHORT_RELEASED", "Dim Down Left"],
                [1, "0x01", "LEVEL_CONTROL", "STOP_WITH_ON_OFF", "1", "S_BUTTON_6", "S_BUTTON_ACTION_SHORT_RELEASED", "Stop Dim"],
                [1, "0x02", "LEVEL_CONTROL", "MOVE_WITH_ON_OFF", "0", "S_BUTTON_7", "S_BUTTON_ACTION_SHORT_RELEASED", "Dim Up Right"],
                [1, "0x02", "LEVEL_CONTROL", "STOP_WITH_ON_OFF", "0", "S_BUTTON_7", "S_BUTTON_ACTION_SHORT_RELEASED", "Stop Dim"],
                [1, "0x02", "LEVEL_CONTROL", "MOVE_WITH_ON_OFF", "1", "S_BUTTON_8", "S_BUTTON_ACTION_SHORT_RELEASED", "Dim Down Right"],
                [1, "0x02", "LEVEL_CONTROL", "STOP_WITH_ON_OFF", "1", "S_BUTTON_8", "S_BUTTON_ACTION_SHORT_RELEASED", "Stop Dim"]
            ]
        }

@Smanar
Copy link
Collaborator

Smanar commented Jul 3, 2023

After some testing i got stuck in my openhab and it seems to be needed to add some more Buttons to access all of the Keys in Openhab due to only get the Pressed Button ID delivered.

Ha nice to know, I never use the field "buttons" on my side.

So you have finished the device inclusion ? do you want to make the PR to add it ?

@NurNano
Copy link

NurNano commented Jul 4, 2023

I really don't know how this things work. Just made the ddf working and liked to share the results with the community. If anyone is able to make the PR so i really would like it.

@Smanar
Copy link
Collaborator

Smanar commented Jul 4, 2023

@NurNano I have made it here #7087

If you can confirm all is fine ? Mainly the DDF, (long time we have started this device)

@NurNano
Copy link

NurNano commented Jul 5, 2023

I use this DDF:

{
  "schema": "devcap1.schema.json",
  "manufacturername": "Paulman LichtGmbH",
  "modelid": "501.34",
  "product": "Paulmann Zigbee Switch",
  "sleeper": true,
  "status": "Gold",
  "subdevices": [
    {
      "type": "$TYPE_SWITCH",
      "restapi": "/sensors",
      "uuid": [
        "$address.ext",
        "0x01",
        "0x0006"
      ],
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "config/on"
        },
        {
          "name": "config/reachable"
        },
        {
          "name": "state/buttonevent"
        },
        {
          "name": "config/battery"
        },
        {
          "name": "state/lastupdated"
        }
      ]
    }
  ],
  "bindings": [
    {
      "bind": "unicast",
      "src.ep": 1,
      "cl": "0x0001",
      "report": [
        {
          "at": "0x0021",
          "dt": "0x20",
          "min": 60,
          "max": 3600,
          "change": "0x00000001"
        }
      ]
    },
    {
      "bind": "unicast",
      "src.ep": 1,
      "dst.ep": 1,
      "cl": "0x0006"
    },
    {
      "bind": "unicast",
      "src.ep": 1,
      "dst.ep": 1,
      "cl": "0x0008"
    }
  ]
}

Works well for me.
Together with the Keybindings from my Post:

EDIT:

After some testing i got stuck in my openhab and it seems to be needed to add some more Buttons to access all of the Keys in Openhab due to only get the Pressed Button ID delivered. So I just edited my Binding to:

        "PaulmannMap": {
            "vendor": "Paulmann LichtGmbH",
            "doc": "On off remote",
            "modelids": ["501.34"],
            "buttons": [
                {"S_BUTTON_1": "ON Left"},
                {"S_BUTTON_2": "OFF Left"},
                {"S_BUTTON_3": "ON Right"},
                {"S_BUTTON_4": "OFF Right"},
                {"S_BUTTON_5": "ON Left long"},
                {"S_BUTTON_6": "OFF Left long"},
                {"S_BUTTON_7": "ON Right long"},
                {"S_BUTTON_8": "OFF Right long"}
            ],
            "map": [
                [1, "0x01", "ONOFF", "ON", "0", "S_BUTTON_1", "S_BUTTON_ACTION_SHORT_RELEASED", "ON Left"],
                [1, "0x01", "ONOFF", "OFF", "0", "S_BUTTON_2", "S_BUTTON_ACTION_SHORT_RELEASED", "OFF Left"],
                [1, "0x02", "ONOFF", "ON", "0", "S_BUTTON_3", "S_BUTTON_ACTION_SHORT_RELEASED", "ON Right"],
                [1, "0x02", "ONOFF", "OFF", "0", "S_BUTTON_4", "S_BUTTON_ACTION_SHORT_RELEASED", "OFF Right"],
                [1, "0x01", "LEVEL_CONTROL", "MOVE_WITH_ON_OFF", "0", "S_BUTTON_5", "S_BUTTON_ACTION_SHORT_RELEASED", "Dim Up Left"],
                [1, "0x01", "LEVEL_CONTROL", "STOP_WITH_ON_OFF", "0", "S_BUTTON_5", "S_BUTTON_ACTION_SHORT_RELEASED", "Stop Dim"],
                [1, "0x01", "LEVEL_CONTROL", "MOVE_WITH_ON_OFF", "1", "S_BUTTON_6", "S_BUTTON_ACTION_SHORT_RELEASED", "Dim Down Left"],
                [1, "0x01", "LEVEL_CONTROL", "STOP_WITH_ON_OFF", "1", "S_BUTTON_6", "S_BUTTON_ACTION_SHORT_RELEASED", "Stop Dim"],
                [1, "0x02", "LEVEL_CONTROL", "MOVE_WITH_ON_OFF", "0", "S_BUTTON_7", "S_BUTTON_ACTION_SHORT_RELEASED", "Dim Up Right"],
                [1, "0x02", "LEVEL_CONTROL", "STOP_WITH_ON_OFF", "0", "S_BUTTON_7", "S_BUTTON_ACTION_SHORT_RELEASED", "Stop Dim"],
                [1, "0x02", "LEVEL_CONTROL", "MOVE_WITH_ON_OFF", "1", "S_BUTTON_8", "S_BUTTON_ACTION_SHORT_RELEASED", "Dim Down Right"],
                [1, "0x02", "LEVEL_CONTROL", "STOP_WITH_ON_OFF", "1", "S_BUTTON_8", "S_BUTTON_ACTION_SHORT_RELEASED", "Stop Dim"]
            ]
        }

I'm using it since 2 Days now and the Keys work perfectly with my OpenHAB. I'm controlling the Lights and Rollershutter with it. Just got a second Paulmann Switch yesterday and added it to deconz a few Minutes ago. Everything works fine from adding the switch up to the recognition of pressed buttons.

@Smanar
Copy link
Collaborator

Smanar commented Jul 5, 2023

Nice, thx, i's same DDF (except you still have the typo in the manufacture name, you still missing the "n").

I remove the draft state on the PR

@NurNano
Copy link

NurNano commented Jul 6, 2023

Wait a sec....I was going to change the typo and opened the DDF, finding out my DDF looks different.

Here is my DDF.
Seems like I changed something while testing with my Windows PC and switching to Linux headless.

{
  "schema": "devcap1.schema.json",
  "manufacturername": "Paulmann LichtGmbH",
  "modelid": "501.34",
  "product": "501.34",
  "sleeper": false,
  "status": "Gold",
  "subdevices": [
    {
      "type": "$TYPE_SWITCH",
      "restapi": "/sensors",
      "uuid": [
        "$address.ext",
        "0x01",
        "0x0006"
      ],
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "config/battery"
        },
        {
          "name": "config/on"
        },
        {
          "name": "config/reachable"
        },
        {
          "name": "state/buttonevent"
        },
        {
          "name": "state/lastupdated"
        }
      ]
    }
  ],
  "bindings": [
    {
      "bind": "unicast",
      "src.ep": 1,
      "cl": "0x0001",
      "report": [
        {
          "at": "0x0021",
          "dt": "0x20",
          "min": 60,
          "max": 3600,
          "change": "0x00000001"
        }
      ]
    },
    {
      "bind": "unicast",
      "src.ep": 1,
      "dst.ep": 1,
      "cl": "0x0006"
    },
    {
      "bind": "unicast",
      "src.ep": 1,
      "dst.ep": 1,
      "cl": "0x0008"
    }
  ]
}

@Smanar
Copy link
Collaborator

Smanar commented Jul 6, 2023

So there is no big change, don't worry.
The only one is the "slepper" state, you have changed it to "false", but I m sure at 99% all battery remote are sleeper.

@AndreasHauber
Copy link

Hello,
I bought some new 501.34 as the old one was working perfectly. The new ones have a different firmware version and are not shown after pairing. Here are my readings:

Basic
image
Power Configuration
image
Node Info
image

@NurNano
Copy link

NurNano commented Sep 30, 2024

Seems like they just added a space in the manufacturer filed between the Licht and GmbH.
Can you try to copy the 501_34_battery_switch.json to 501_34_battery_switch_new.json and add the space in the "manufacturername" field?
Then reload the Deconz and try to add it again. It should now be there like the old switches.
If it works the button_maps.json has to be edited too.

@AndreasHauber
Copy link

Thanks, that worked for me.

@NurNano
Copy link

NurNano commented Sep 30, 2024

@Smanar can u do an other commit and add a second json and change the button_maps.json by just copy and pasting and adding the space?
That would help all future users of the new Buttons :)

@Smanar
Copy link
Collaborator

Smanar commented Sep 30, 2024

Sure #7952
I haven't modified the buttonmap file as deconz use only the ModelID for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants