Deconz-rest-plugin: Paul Neuhaus Q-REMOTE

[cracyfloyd]

Can anyone help to integrate this Paul Neuhaus Q-REMOTE in the _Conbee II network. step by step.
Here a link for remote information:
""https://www.paul-neuhaus.de/shop/de/ersatzteil-fernbedienung-sender-100-462-31.html""
It is possible to make this remote visible in deconz? I cant get it.

best regards

[cracyfloyd]

no one can help? i see this remote in deconz but it it possible that i can see the remote in phoscon and define buttons or anything else?

[sheineme]

I have the cheap version of a Paul Neuhaus remote - the one that comes included when you buy a Q-lamp (Q-PANEL with adjustable color temp. in my case). I also can't see it in Phoscon. I use deConz headless and I have never checked how it looks like in the GUI.
However, I can use the remote: the buttons 1,2 and 3 refer to the groups with the IDs 1,2 and 3. You cannot specifiy the ID of a group when creating it in Phoscon, so I have modified the underlying sqlite database file to make the groups 1, 2 and 3 what I wanted them to be. Changes needed to be done in the groups table and in the table where the relationship groupID -> lightIDs is set up; if this is of interrest, I can look up in more detail what needs to be done (of course: make a backup the original sqlite database file before hacking around in it ;) )
With that I can control my groups 1, 2 and 3 (Kitchen, Dining-, Livingroom): swithing on/off, dimming and color temperature.
My guess is, this just works because the remote sends standard zigbee group commands over the network

[alessandroceleste]

I have the same problem with the Paul Neuhaus Q-Remote Controller. It would be great to be able to configure it via Phoscon App.

[cracyfloyd]

Please....Integrate this Remote...

[MrSolo570]

How can you actually pair it with deconz / phoscon?
Edit: ok I managed to do that. But within home assistant it does not show up as entity nor within phoscon. How or where could you possibly set which button controls which function? Thank you

[Mimiix]

It seems this issue is resolved or otherwise inactive. If it is not, please re-open!