Müller-Licht tint remote control 404049 #5841
Comments
|
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. |
|
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. |
|
I have been scratching my head for weeks now why this wouldnt work when other people in the home assistant forum were abled to add their remotes. Now i find out that the specific remote im using is not supported? Wow. |
|
is there any plan to add support for the remote control? |
|
A dev needs to pick this up. I'm happy to re open, but if nobody wants to do it it can take a while |
|
Hello can you try this DDF Then enable logs in deconz (help / debug view) and press buttons, you will have different error message, can you share them ? |
|
-----I did that, there are no errors in debug view, but now home assistant says the light entities are unavailable (still abled to control them via phoscon)----- Update: So now it properly took the ddf, shows up as switch 2 in phoscon and deconz, but there are no error messages whatsoever when i press buttons. |
|
Yes the light entry need to be not present, it s a battery remote so only sensor entry, can have some synchronisation issue. Ok if you don't have error message, (they ara about button or button map) It probably mean the device need binding. BTW how are you so fast on HA to install a DDF, you know docker or have a tuto ? DDF with binding enabled to a group, to use this switch with a zigbee group If you still have no error message, we will try with unicast binding, but it will be strange. BTW need to enable "info" "info_l2" and "DDF" as flag for debug (the checkbox). |
|
My Setting is a Home-Assistant based one, with deconz as Docker Addon. With Debug Mode INFO_2 and DDF, I get eg the following message: And it was the ONOFF Switch pressed. If I press some different switches, It is named appropriate. So the question is, how can I configure a Button Map for those messages? |
Those should be all available buttons on the remote control. The Remote Control has a center Button, to address 3(-4) Groups. Every group has its own Color Level, Temperatur level and basic buttons set. (
|
Ha ok, so you are using the editor to have same result.
It's the second part ^^. But the problem will be the same, you need to access docker file. The problem is with XX part, I m searching in the code, but I don't think it's present on legacy code. |
|
Thanks for the Link. It was helpful to find the default configs within the container. I was only looking into In the system button Map file, I found a good looking part: |
|
Take a look in But on your logs you don't have thoses request ? The json can work natively for ONOFF and LEVEL_CONTROL but not other, because of the value used from the payload. |
|
ah i just "sshed" into the docker and loaded the ddf manually :D |
|
This method can work for the DDF but not for the button_map file ^^. |
|
So, i just added the part into the button_map file. btw if i enable Info2 this is spammed alot: |
|
There is nothing to see with the button_map file.
but this line is not normal, this command need to work.
You are using my code ? |
|
Get the So do i have to place your provided json fragment into the $home file? and trigger some reload? Or do I need to rewrite the entire I did the following, but actually with no success: modified the button_maps file with the But no changes: (and now I can't restart the container) but that's a different error... |
|
I still get this:
|
|
interestingly, tho the switch shows up in phoscon, i cant actually add it to any groups |
|
Its showed in phoscon in cause of the added DDF. The appropriate key map is missing, that's why nothing happens, but visible. How can I trigger a reload of the button_maps.json. Is it possible for test purposes to cp in a modified version of the maps.json file? For me I had to restart everything, because the docker image couldn't be removed on reload of the docker container (it already exist,,,) For a progress on this do we need some more debug infos? e.g. long and short press sequences with the corresponding buttons?! In my first test the payload was not so clear on the color change stuff. The ONOFF has no long/shortpress function. It has only a ON (0x01) or OFF (0x00) state. |
For me it's the good method, you just need to add the code fragment to the complete file. Using the cat command is not working like #5917 (comment) Here a way to found the file #3670 (comment) You don't have vi nano or vim as usable command ? |
|
you can install it in the docker with |
|
There is no command pre-installed (native) in the docker ? |
|
what command pre installed? yes there is no editor pre installed in this container. It is not to good way to change files inside the docker container. The way to do those hot fix stuff is via Or do i not need to restart the service? otherwise Is the json file parsed on every event? Now with the changed file, I don't get any response inside the debug monitor. (and with the original file... so I don't know what's going wrong at this point with my setup...) |
This file is only parsed on deconz start. And I have my answer, I need to make a JS code to handle all button event. Not so hard but need some time, and need first to found a way to add/edit file definitively on dockers. |
|
actually no reload functionality. (maybe for test purposes a separate setup would be good... with only a small set of test devices... next item on my shopping list..) in the home assistant add-on (https://github.com/home-assistant/addons/tree/master/deconz), there is also no functionality to expose the $home config files to the host. https://community.home-assistant.io/t/deconz-support-management-of-ddf-files-through-ha-config/370331 Additionally for the COLOR_CONTRO -> MOVE_TO_COLOR command, there is no separate key code, the remote calculates the next value and sends it inside the payload, the following 19 values I have seen in a sequence of a lot up presses and a lot down presses: with the [0F4D0E260000; 645FAA960000] max, min values. following the order, with round about 20 up presses, down presses, up presses. |
|
docker cp is not as good... It brings the container in a not removable state... If I try to restart the add-on via web ui, I get the following error message: via terminal I get the following from docker: a force remove doesn't work. My fix in this situation is to restart the entire host. (or maybe moby/moby#22312 (comment)) |
|
Sorry, I realy can't help you for docker, I totaly hates this working mode and don't know how it work at all. For the move to color, you are right :( I have just read the doc, and first 2 bytes are X color, then Y color and transition time. But need to memorise the last action to compare. Seriously it s realy too much work without using c++ code. |
|
docker is not the scope of this issue ☺ where did you find a documentation of this remote? The order in my prev post was not the right order, only the (sorted) unique values. too much work, sounds not so good... |
|
Not remote documentation, but zigbee one ^^
|
|
Hi @Smanar, I am not sure if you noticed already, but another version of this remote which is very similar (maybe identical?) is already supported in deCONZ. Erik added support for it in #2849. The original issue is #1209. I know that this old version also has the color change stuff, and Erik hard coded the colors in de_web_plugin.cpp (see linked PR above). If it is possible, it would be nice to expose this new remote exactly the same (or similar) to the old one. That would make it easier for third party app developers (like me) to add support for it. So the same button events, etc. Maybe you can even reuse the existing code if it is the same. |
|
The problem is it's no more possible, ATM adding new device using c++ is forbidden, can add them only using DDF. But ATM I think we can use the "move to color tezmperature" if we can store the previous value somewhere (and compare it with the new one) but I don't see how to use the "move to color" only with values returned by the device. |
|
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. |
|
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. |
|
Is there a final solution, to bring this remote control to work? |
|
@Smanar ? |
|
This device can only work partially. |
|
Can someone provide the partially working ddf? I use some stuff from above and i can see the device but there are no working things in iobroker :-( |
|
The orignal one is here #5841 (comment) But what is your model id ? |
|
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. |
|
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. |
|
Is this device now supported or not? |
|
Nothing more since #5841 (comment) |
Device
This remote seems to be very similar to the one from #1209.
Screenshots
Cluster
Basic
Identify
Node Info
The text was updated successfully, but these errors were encountered: