I have used several of those ACC-250-LD dimmer plugs in the past in combination with the KlikAanKlikUit app for Homey. I don’t recall running into the issue you mention. But that was two years ago and don’t know if anything changed in the meantime app- or Homey firmware-wise that would cause that issue.
Maybe other Homey users have more recent experience with controlling that plug.
Otherwise you can always reach out to Athom.
Good to know… I wonder though if you tested for dim level when you did use them. Or any KAKU dimmer. Dimming the ACC 250 LD is not the problem, testing for its set dim level is… 
That’s a fair point. If I recall correctly I only used the control/slider, that displayed the dimming level. Not sure whether I used the dim level tag value as part of a flow.
Note that the KlikAanKlikUit dimmer doesn’t send its dimming state to Homey when you use other control methods (f.e. the remote control), since it’s only 1-way communication (Homey is the transmitter, the dimmer is the receiver). Probably getable is set to false in the dim capability options in the app, which means that you can’t read it from a Flow or the UI.
That’s clear Sven… in the case I encountered the dim value is issued by a Homey flow and the dimmer responds to it. So it is weird that the dim level stays at ‘1’ regardless of what you’ve sent to it.
For me on Homey KAKU app v7.6.0 works perfectly OK with a ACC-250 .
DIMLEVELS are between 0 and 1 so setting it to 25% returns 0.25 and calculating with that in a logic card to + 0.02 and setting that as a new Dimlevel set it to 0.27.
No issues here on Homey Pro running the latest firmware ( v 13.4.1-rc.1 shouldn’t be differentfrom the latest beta)
You have to use values between 0,01 and 0,99.
Thanks for moving the posts to here… although looking at the title of the other post… it seemed fully relevant to post that question there.
Thanks Dijker for that… I did have an inkling it might work like that (the value would something like 0.25 for 25%) but when clicking on the tag and looking at the dim value in the list shown it always says 1. But the flow apparently does pick up 0.25 which I did not see. So now it is working! Although the mind boggles why the right value isn’t shown in the list I get to see when clicking on the tag. And a bogglet why it doesn’t simply record 25 in the tag of course.
But that is now a moot point… onward! Thanks!!!
Value ‘1’ works too, when set at 100%!
Correct,
the title… but the different questions below and only 1 old reply without activity for 6 years ;-(
Now you have attention of al least ~74 active users in this “Official” cq Central [APP] Topic.
Anyway, not less Welcome to ask your question.
/OT
Tested also Homey -to - Homey,
only ON/OFF is synced, the Receiving Homey does not receive a Dim Value from the sending Homey. (Was under the impression that even that has worked in the last 10 years some time but not sure.)
The preview of the tag values are not always the actual values. I don’t know exactly when Homey shows actual values or just an example.
Thanks to this experience AND solution… I now know that that value list is… well… if they are just examples (but what would be the use of that…)… not to be trusted! I am assuming this goes for all the values shown there? Boy, that is not good. Anyway, very pleased with the outcome.
I’ve updated my request to Athom with my original finding (and that I was shown the incorrect value in that list) to say that it’s weird the value stays at 1 whatever I do… so perhaps something comes out of that as well. Great. Onwards, as I said… to new findings!
