I am trying to configure automatic closing of the shutters around sunset; while opening them manually. The issue seems to be that linknx doesn't want to send another close to a group it thinks it is already closed (question about on/on/on on type of group addresses).
I have grouped all my shutters, upstairs and downstairs in separate groups for convenience and this seems to the start of the problem. My configuration is as follows:
I have my individual address (2/0/5), my all shutters address (3/0/4) and my up or down level addresses (3/0/{5|6}). During the evening; I close the upstairs shutters and some time later, the down ones if we don't have a particular ligh on/off (don't want to get us locked out).
These are the rules:
In the morning; some of the shutters are opened on an individual basis; or they are opened by using the group addresses. (up/down/all levels).
I have noticed that, even though I thought to have compensated by letting the objects listen to the different group addresses of up/down/all levels; the linknx state is not adjusted accordingly; or as I would expect; the shutters that are not opened individually are not shown as openend on knxweb; and when I do not fix this; the opening and closing of the shutters seems to fail during the evening.
If the 'close up/down/all' commands are sent in the evening with linknx; the knxweb status is not adjusted either. I found a post that was claiming that multiple on/on commands are not supported if the status is 'on'. Probably there is a mismatch in my configuration that doesn't allow the internal states to be updated accordingly and resulting in ignoring to send the new (evening down) state.
Since I am about to start packaging linknx in Debian; I'd like to have this scenario solved as an example in the package since I expect that this is a scenario other people would use to.
I have grouped all my shutters, upstairs and downstairs in separate groups for convenience and this seems to the start of the problem. My configuration is as follows:
Code:
<object type="1.001" id="92" gad="2/0/5"><listener gad="3/0/4" /><listener gad="3/0/6" /> Living vitrine op/neer (motorsturingen) </object> <object type="1.001" id="93" gad="2/0/6"><listener gad="3/0/4" /><listener gad="3/0/6" /> Kitchen deur op/neer (motorsturingen) </object> <object type="1.001" id="94" gad="2/0/7"><listener gad="3/0/4" /><listener gad="3/0/5" /> Room NO op/neer (motorsturingen) </object> <object type="1.001" id="95" gad="2/0/8"><listener gad="3/0/4" /><listener gad="3/0/5" /> Room ZO op/neer (motorsturingen) </object>
These are the rules:
Code:
<rule id="shutters_up_down">
<condition type="timer" trigger="true">
<at type="sunset" offset="-30m" />
</condition>
<actionlist>
<!-- upstairs down -->
<action type="set-value" id="119" value="on" />
</actionlist>
</rule>
<!-- downstairs down only if kitchen light is not on -->
<rule id="shutters_down_down">
<condition type="and">
<condition type="timer" trigger="true">
<at type="sunset" />
</condition>
<condition type="object" id="4" value="off" />
</condition>
<actionlist>
<!-- downstairs down -->
<action type="set-value" id="118" value="on" />
</actionlist>
</rule>
I have noticed that, even though I thought to have compensated by letting the objects listen to the different group addresses of up/down/all levels; the linknx state is not adjusted accordingly; or as I would expect; the shutters that are not opened individually are not shown as openend on knxweb; and when I do not fix this; the opening and closing of the shutters seems to fail during the evening.
If the 'close up/down/all' commands are sent in the evening with linknx; the knxweb status is not adjusted either. I found a post that was claiming that multiple on/on commands are not supported if the status is 'on'. Probably there is a mismatch in my configuration that doesn't allow the internal states to be updated accordingly and resulting in ignoring to send the new (evening down) state.
Since I am about to start packaging linknx in Debian; I'd like to have this scenario solved as an example in the package since I expect that this is a scenario other people would use to.
Kommentar