Add possibility to put Bubendorff shutter with jalousieable slats in jalousie mode
Opened this issue · 5 comments
Original implementation of the ability to control Bubendorff shutters is described in issue 166.
At the moment the adapter only features a range for state "target position" from -1 to 100 for Bubendorff shutters.
The "target position" also has value "step" set to 100.
After trying my luck with the Netatmo app and the JSON file created on adapter start I found out,
that there is a possibility to put a Bubendorff shutter with jalousieable slats in jalousie mode:
To make this happen I have to set the value "target position" to -2.
If set to -1 the shutter just closes normally just like a normal shutter without jalousieable slats.
To set "target position" to -2 Min range needs to be set to -2 and "step" needs to be removed completely.
I tested this successfully with two shutters.
Describe the solution you'd like
I would like a solution which gives me the possibility to set "target position" accordingly
or have a button or something that serves this purpose. Since this possibility cannot be set from
Apple HomeKit this feature would make the adapter unique since its the only way to include the
shutters with all functionality into a smarthome system.
Is there some kind of workaround to achieve this function in the meantime until the adapter is updated? When I alter the target position object it automatically gets reset at some point.
Thx!
@Apollon77 Is there some kind of workaround to achieve this function in the meantime until the adapter is updated?
When I alter the target position object it automatically gets reset at some point.
Most likely it gets reset when you restart the adapter ... I have no workaround so far but in fact it should also work still after that, you one have warn logs in your logfile, right?
tested it, you are correct. Gets changed back to default on adapter restart. Netatmo adapter log level is on "info" but I have no entries in my protocol file regarding this change.
@Apollon77 @Claus1985 I can confirm that it works using value -2 without any problem.
Problem is it constantly gets reset to default value even without adapter restart