Wrong dimmer value in gui
-
I installed a new dimmer a few days ago, a Sunrichter "knob smart dimmer" (SR-ZV2835RACS).
It included without problems into Z-way and shows up in AluUI and in the Console as usual.
However the dimmer value in AltUI/Console does not change when you adjust it manually on the dimmer. I have checked the variables and it seems as if AltUI displays LoadLevelTarget and when checking on the dimmer variables the LoadLevelTarget value is not updated in OpenLuup when the dim level is changed on the dimmer. In other words LoadLevelStatus and LoadLevelTarget differs and LoadLevelStatus shows the correct dim level set manually on the dimmer.
If you change the dim level in OpenLuup then both values are updated.
On/off state is however always updated.In Z-way the dim level is updated as it should, so it works there as it should from what I can see.
Running OpenLuup 20.12.19 and AltUI 2.53b.2552.
@akbooer any idea if this is something that can be fixed?
-
I submitted PRs for both the openLuup console and ALTUI on github.
@akbooer, I dug into how vera handles it and it is displaying the LoadLevelStatus on its slider as far as I can see from the D_Dimmablexxx.json. That's why there is an inconsistency between what we see inside the device and on the device dashboard on ALTUI since they are being run by different files. I think there was a misunderstanding of the LoadLevelTarget value is being used for. It does not represent the load value when the dimmer is getting turned on. It represents what the target value is at every instant. What value the dimmer gets to when it turns from off to on is stored by the device, not the controller and if it is to be stored in the controller, it is in a different variable. -
@catmanv2 Yepp! The full name on the instruction leaflet is "Push Compatible Z-wave Knob Smart Dimmer".
It is this kind of push-and-twist dimmer:
A quite common type of device in Sweden and in the other Nordic countries.
But a funny name, google translate at you service! I assume they don't sell it in the UK.
-
@rafale77 said in Wrong dimmer value in gui:
What value the dimmer gets to when it turns from off to on is stored by the device, not the controller and if it is to be stored in the controller, it is in a different variable.
I believe that's where we got the
LoadLevelLast
kludge. -
@catmanv2 Yepp! The full name on the instruction leaflet is "Push Compatible Z-wave Knob Smart Dimmer".
It is this kind of push-and-twist dimmer:
A quite common type of device in Sweden and in the other Nordic countries.
But a funny name, google translate at you service! I assume they don't sell it in the UK.
-
@rafale77 said in Wrong dimmer value in gui:
What value the dimmer gets to when it turns from off to on is stored by the device, not the controller and if it is to be stored in the controller, it is in a different variable.
I believe that's where we got the
LoadLevelLast
kludge.@toggledbits yep, I’m restoring it when a virtual dimmer is turned on and I suspect it’s what Vera is pushing anyway for some Zwave devices.
-
I submitted PRs for both the openLuup console and ALTUI on github.
@akbooer, I dug into how vera handles it and it is displaying the LoadLevelStatus on its slider as far as I can see from the D_Dimmablexxx.json. That's why there is an inconsistency between what we see inside the device and on the device dashboard on ALTUI since they are being run by different files. I think there was a misunderstanding of the LoadLevelTarget value is being used for. It does not represent the load value when the dimmer is getting turned on. It represents what the target value is at every instant. What value the dimmer gets to when it turns from off to on is stored by the device, not the controller and if it is to be stored in the controller, it is in a different variable. -
Well, for unknown devices, it defaults to combo_device type I believe anyway and uses the corresponding device files. What do you mean by ALTUI console? Do you mean openLuup console?