First: Sorry for crossposting, i allready postet my problem in the Phsocon App Section wich was maybe wrong. If Maybe on Mod can delete it there. thanks.
Hi everyone,
I have an issue that should have been fixed in #5880.
There is a problem, when pairing a wall scene switch from JUNG type ZLLLS5004M.
When using the latest 2.28.1 the switch will be paired as “Remote” instead of “WS_4f_J_1”
The “Remote”-device has only one button, while the correct “WS_4f_J_1” has 8 buttons. So i can not map the different buttons to different actions, because there ist only on button showing up.
working, but very ugly workaround:
downgrade to 2.23.01
pair ZLLLS5004M
and upgrade to latest version again.
Maybe one can have a look on it. Thanks in advance.
Steps to reproduce the behavior
pair a ZLLLS5004M in latest deconz Version
Expected behavior
pair ZLLLS5004M like in 2.23.01 with the correct icon, the right descriptions and features
Environment
Host system: PC
Running method: Ubuntu, running in Docker Container
Firmware version: (26720700)
deCONZ version latest 2.28.1
Device: (ConBee II)
Do you use an USB extension cable: yes
Is there any other USB or serial devices connected to the host system? yes, many? IMHO not relevant in this case.
deCONZ Logs
please ask for specific logs
Additional context
Switches:
6 x Insta WS_4f_J_1
4 x dresden elektronik Scene Switch
7 x lumi.remote.b686opcn01 Switch
Lights:
3 x dresden elektronik FLS-CT
1 x Philips LWB010
2 x innr RB 248 T
2 x GLEDOPTO GL-C-008P
7 x GLEDOPTO GL-C-006P
Sensors:
1 x TRADFRI motion sensor
5 x lumi.sensor_magnet.aq2
3 x lumi.weather
1 x lumi.sen_ill.agl01
I tested it with deCONZ 2.28.1 and the switch was indeed paired in Phoscon app as a one button switch. Then it took a while, I played around with the switch, all button events came in as expected. After a while the switch was correctly shown with the correct model id and an icon with all buttons in Phoscon app.
So I think it just took some time until the switch was fully paired in deCONZ and deCONZ gathered all informations and send it to the app via RestAPI. When the app knows the model id of the switch it can show the switch correctly.
The only thing what I did was to read the basic cluster of the switch in the deCONZ GUI.
So I don’t know if this is related to these old bugs mentioned in this topic or if something broke again in one of the newer deCONZ Versions or if we just need to wait a little time and press some buttons on the switch to help to pair the switch completely to deCONZ.
I have already downgraded to 2.23.01. And I will now work and live with that. Maybe I try a more recent version later. At the moment I dont have the nerves for trying workaround “A” , reading something in “B” and waiting a “while”.
Sorry, it worked already flawless. What changed? Why does phoscon say “green” when it is not?
Can you imagine how much “whiles” I spent on my own before posting in this forum? This is always the last option for me.
Sorry, if that sounds a little rude.
Another point is that the use of deconz GUI is just a mystery to me. I could handle to use the OTA thing, but I would never click on any other button, because I dont want to mess up my system. Doubtles deconz-GUI is a powerful tool, but the GUI was made by programmers and not users. Its for me not intuitive enough in that kind, that I cant use it only once a year with confidence, when I have a problem in my system.
The 2.28 Version also gave me the "user experience" that I have to change my batteries in some of my original dresden elektronik wall scene switches twice a month. The battery was always drained to lower then 1,7 Volts. With 2.23.01 the problem seems to be gone.
I really dont know if that was real the cause.
My wife complaints are gone and therefore my problems for the moment.
It is not working fine, because sometimes pressed buttons have no effect and sometimes some lights dont turn out when they should. But it is good enough.