[question] Qubino Mini Dimmer delay/performance help #2226
Comments
|
@AlCalzone Could you tell me how to send that command? I think he could do that using sendCommand mqtt api |
|
Variant a) TL;DR this should do the trick: node.setValue(
{
commandClass: 0x26,
property: "targetValue",
},
99, // (= 0x63) or any other target value
{ transitionDuration: "default" }
);@robertsLando It would be a good idea to expose these options via the UI in general - I think HomeAssistant already does. Variant b) |
|
Thanks for your help, much appreciated, I'll go and try and post back here if I was successful. |
I already expose some options, I think transition duration should be there |
|
When trying to use the options trough the ui I get a message from the driver (that I can't get to go away). I was trying below from HomeAssistant, but I'm getting: "Failed to call service Experiment" which doesn't show anything in zwave-js debug so it's probably something else. I have to attend something quickly but I'll try variant B later today as it's probably easier for me, I'm just running z-wavejs2mqtt as is in a docker container. |
|
@LarsMudde zwavejs2mqtt logs please |
I set the log level to Silly, did a clean start of zwavejs and reproduced the error, but I don't see it in the logs. I'm not entirely sure if these are the logs you are looking for? This occurs when I send 10-38-0-duration Transition duration with 0 seconds. My gut says it might have something to do with them being separate commands. I think it should maybe be one command with both transition duration and target value? |
|
The screenshot of the Control Panel is missing the part that shows what targetValue was specified. Based on the error message, the wrong value was input (it requires a value 0-99 or 255). Regarding HA, it already has support for transitions using the light integration turn_on service, with the I don't think you can set options in the Device Action as shown in the screenshot. You'd have to use the |
That's a different error than what you showed previously. You can't set the |
|
@kpine my bad, I treated them as essentially the same error, but you are right. they are different, I get that one when posting the transition duration. The problem is, that there is no way for me to set the duration to 1 second or (preferred) 0. The manufacturer claims that it's possible (if I read the email in the OP correctly). This means that when dimming to a new value it uses the time set in 10-112-0-66 (which is 6 seconds). This is the time that should be used for dimming when pressing the button. But not for dimming from HA/Zwavejs, because it only reports the value after it's done and I don't like having the 6s delay before my app updates. |
|
For HA I posted the documentation and description of how to set transition. Did you try it? Is it not working? |
|
@kpine on it, I'm not as fast yet |
|
If you want to set transition in the control panel, you just need to fill in the proper values.
|
That's exactly what I was looking for, and it works :) now I just have to figure out how to get it to always use 0s in home assistant using the lights yaml but that should work out, at least now I actually saw it work and know the dimmer can actually do it with no transition. Some online review I read (in Dutch) claimed it can't. Thanks a ton! |
|
Truly appreciate the help a lot guys, I'll make a small donation to the project as a thank you for all the help. |
|
The only way to get a default value is using light profiles. That may or may not work depending on your needs. |
|
I'll go and try to get it to work (I have to run an errand now) I'll do a follow up tomorrow if I got to work it out on HA too. |
|
Hi, I've been trying to get it to work from HomeAssistant using the suggestion of @kpine, after some more effort I got this to work from the lovelaceui using an automation and a numeric helper (input number) Regards, Lars |
|
So after some more tinkering around, for anyone else running into this: You can also leave everything default and create a light_profiles.csv for Home Assistant in the same folder as your configuration.yaml with the following content:
This should also set the transition to 0s. |
|
Dear all, I have experienced the same issues and see that it was indeed possible to make it faster in Zwavejs2mqtt control panel. thank you very much |
|
Hi @rezzalex , I have no experience with Domoticz whatsoever. It should all work fine as long as you can get Domoticz to pass the transition(duration) to zwavejs2mqtt. Regards, Lars |
In MQTT Explorer, I have tried this without any success :
|
|
Not supported with mqtt set, you should use another api like setValue or sendcommand, I could add the support in next version |
|
Oh wait... we're going in circles: #2226 (comment) |
|
If it is possible to include it in the next version, it could be great, it would avoid a temporary implementation of the "setValue" or "sendcommand" API by the Domoticz MQTT auto discovery plugin |
|
@rezzalex Could you open an issue for the MQTT feature. BTW like I already said you have lot of other ways to do that |
Hi everyone,
Recently I've bought a Fibaro Dimmer 2 and a Qubino Mini Dimmer to see which one would work best for me.
After a test setup and playing around with both I came to the conclusion that I like that the Qubino dimmer is smaller and that dims using a mosfet (to a lower level than the Fibaro) with a bypass. There is however one big drawback:
The dimmer has a configuration parameter that allows you to set the time that you need to hold down the button to dim between 0 and 100 percent when holding the actual physical switch connected to the dimmer. I found about 5 seconds to be comfortable for me. However, here is my problem: If I dim using the app, the lamp also takes 5 seconds to transition between the old and new value. The dimmer only sends back the new value after it's done dimming. Which means if I turn on the lamp in the app, it turns the toggle back to off, and then only turns it back on after the 5 seconds mentioned earlier. This is a long time for me, to be turning on a lamp trough my phone and to me it's a drawback. So I decided to reach out to their customer support and they replied with the following message:
I've been trying to send the command described in the e-mail to see if this would work as intended, but so far I haven't been able to get this to work. I've tried posting a message using MQTT and also sending one on the websocket that the GUI uses for communication (haven't succeeded). I'm hoping someone can give me a pointer in the right direction.
Thanks for any and all help!
Regards,
Lars
The text was updated successfully, but these errors were encountered: