I have seen same behavior with my DH (Ikea Symfonisk Controller). Sometimes it goes up to 60% but around 45% is quite normal… the spec says that message has battery level as percent so DH just reports what the device says
Should be fixed, I will commit changes to Git
It worked with the fix.
The dimming reporting is quirky. I have to release the dial after turning it before it registers a new dim level. I guess this is just how the hardware works.
Thanks, @Luis_Pinto!
It will be like that if you turn it fast, if you turn it slowly it will register in between. This is how Ikea design it
Hi - thank you for your work on this.
I am able to pair successfully, and can see success messages in the log when I press, double press, and triple press the button. But, when I try to turn the knob, I see errors in the log and the level doesn’t change:
I’m using a v1 hub - any thoughts/suggestions?
Getting the same error. Did you ever figure it out?
I’ve been trying for days to do what you wrote, i.e. add your code to the Samsung developer site but without success.
I registered, asked to register the company, and I did it. And still when I try to add new virgins prompts me to register the company
With all due respect to you and the people from your profession, but almost all solutions for smart home (and specifically instructions) are made for the engineers of automatics and electronics and developers…
It’s like you’re consciously doing that we “ordinary mortals” should stay away.
What is difficult to be precise in instructions…
thank you
Maybe try this:
Hi guys- although I am just an ordinary, garden-variety end user, and I have no idea what I’m talking about, I was able to discern in this thread (despite overwhelming jargon, lingo, poor grammar and spelling, etc) that you guys seem to be having problems with the coding required to achieve precise control of the rotating volume knob on the SYMPHONISK sound controller.
I stumbled upon this video which unfortunately is in German. I don’t speak German but I was able to see that the narrator goes in to meticulous step-by-step detail regarding the changes required in “deCONZ” (whatever that is). I have included a couple of representative pictures. The video is also linked and the relevant section begins a few seconds after 6:30.
I have a feeling that this might be exactly what you need to take this device handler to the “next level” and hopefully permit the sound controller to perform as desired! Perhaps you have already resolved these problems, but given the persistent issues that I am observing, I suspect not. Thank you so much for your hard work and diligence with all this. As one of you said: it is certainly “not trivial”!!
