-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HmIP-BBL datapoint LEVEL_2 cannot be set #154
Comments
Hello, I think the reason behind it is that the actor only does something when you set LEVEL_2 and LEVEL (or LEVEL_2 and STOP) right after each other. When you run a Homematic script you also need to set both, setting only LEVEL_2 doesn't work. See https://www.flurweg.net/hmip-fbl/ Since I couldn't figure out how to set two values right after each other with the ccu-value node (tried it with delay node etc. but it didn't work), I ended up using a function and ccu-script node. The function node produces a Homematic script like this:
It works for one actor but if I want to set multiple actors at the same time (e.g. when controlling the blinds according to the sun position) it unfortunately doesn't work reliably. Seems like the scripts fire too fast and some delay is needed, but I haven't found a good solution yet. How does COMBINED_PARAMETER work, can you provide an example of how the payload needs to look like? Thanks. |
Hi, I have a few HmIP-BBL (for blinds with slats). There are two datapoints, LEVEL which sets the height of the blinds, and LEVEL_2 which sets the position of the slats. Unfortunately, the latter cannot be set.
While reading the slat position datapoint LEVEL_2 using the
get value
node works without problems, setting a new value does not result in any actions. Interestingly, the datapoint COMBINED_PARAMETER which lets you set LEVEL and LEVEL_2 simoultaneously, works without problems and can be used to set the slat position.It appears to me that the set LEVEL_2 command is somehow not forwarded to the CCU.
Node-RED version: 1.3.5
node-red-contrib-ccu version: 3.4.2
The text was updated successfully, but these errors were encountered: