-
Describe the issue you are experiencingHMIP-FROLL does not propagate LEVEL when using UP or DOWN buttons in the UI after pushing stop before totally up or down. Instead when pushing the button down LEVEL will become value 0 and when pufhing the button up LEVEL will become 1 after stop button pressed while shutter was still moving. When using the text input to eg. 30% LEVEL will become value 0.3 correctly. The UI is always showing the correct shutter value but not the internal LEVEL value propagated to eg nodered. Describe the behavior you expectedLEVEL should propagate current level. Steps to reproduce the issue
In NodeRed I have created a simple flow catching the LEVEL value. What is the version this bug report is based on?3.69.7.20230506 Which base platform are you running?rpi3 (RaspberryPi3) Which HomeMatic/homematicIP radio module are you using?RPI-RF-MOD Anything in the logs that might be useful for us?I cannot exactly find out anymore when this bug started to appear. I used Version 3.65.11.20221005 before and it already had the problem. Now I am at 3.69.7.20230506 Additional information |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
I guess I found the problem: The way LEVEL on Channel 4 is used has changed. Prior to some version of rasperrymatic (see above) on channel 4 LEVEL was propagating the value on the final state of the shutter. When you stopped the movement while eg. closing the shutter, LEVEL would become the value of the blinds's stopped position. This new way was braking my automations but I guess this way it makes more sense. In expert mode one can see that channel 3 shows the actual position in percent. On channel 4 LEVEL represents the value one entered in the textbox and not the actual position. Long story short: I might have missed this breaking change in the release notes. Furthermore it was probably a long existing bug no one really was aware of ore cared before. |
Beta Was this translation helpful? Give feedback.
-
I really would love to get a short comment on this change if I missed it or if it was silently introduced. |
Beta Was this translation helpful? Give feedback.
-
Thanks for having solved the issue yourself. I guess that this will be better suited in the discussion fora part of this repo, thus I will move it accordingly for later reference. |
Beta Was this translation helpful? Give feedback.
I guess I found the problem:
The way LEVEL on Channel 4 is used has changed. Prior to some version of rasperrymatic (see above) on channel 4 LEVEL was propagating the value on the final state of the shutter. When you stopped the movement while eg. closing the shutter, LEVEL would become the value of the blinds's stopped position.
This changed, Now, when eg. closing the blinds and stopping them in motion LEVEL on channel 4 will be set to 0 which is not the actual position but more the command you gave to close them. Hence, I guess when setting a percent position and not stopping the movement the value of LEVEL on channel 4 is showing the actual position.
This new way was braking my automat…