Skip to content
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

Cover update - up/down from bus; stop and movement direction #322

Merged
merged 16 commits into from Aug 13, 2020

Conversation

farmio
Copy link
Member

@farmio farmio commented Aug 3, 2020

this is derived from #259 so

  • in xknx 0% is open and 100% is closed now
  • adds is_opening and is_closing
  • react to up/down from bus and start travel calculator
  • add group_address_stop for actuators that have it (or don't support step)

resolves #314
fixes #257 (I hope)
fixes #105 (without implementing the DPT1 state address - just listening for the normal group_address so initial status may be off)
closes #25

Change Cover and TravelCalculator to
0% = open
100% = closed
1 bit telegrams have been inverted if `invert_position` was true.
These are specified in knx as 0="up/open" and 1="down/close".
I think invert_position shall only be applied to %
as this was only used for unittests
it doesn't matter if 0 or 1 is sent to stop for ABB and MDT actuators. Just fixing the tests here.
@coveralls
Copy link

coveralls commented Aug 3, 2020

Coverage Status

Coverage increased (+0.07%) to 91.858% when pulling fafec74 on farmio:next-cover into 58aca20 on XKNX:next.

@farmio
Copy link
Member Author

farmio commented Aug 8, 2020

Up/down from bus seems to have issues with the auto_stop_if_necessary function. When I set a down telegram on a tunnel a similar telegram is received as answer (not yet really sure why). This overwrites the travel_to_position value with 100% and auto stopping fails.

Workarounds:

  • don't Support absolute positioning without position group address or
  • don't process updown when is_traveling() == True this could lead to wrong positions when travel direction is changed at travel. Maybe ignore updown for the same direction as current movement.

Edit: now I know why the telegram boomerangs. See #323

@farmio farmio merged commit d4f45e0 into XKNX:next Aug 13, 2020
javicalle added a commit to javicalle/custom_components that referenced this pull request Oct 4, 2020
In v0.12.0 XKNX library have changed the internal OPEN/CLOSED numeric values. From this version 0% is OPEN and 100% is closed.
XKNX/xknx#322

`rts_rflink` must adapt the position values sent and received from the library
javicalle added a commit to javicalle/custom_components that referenced this pull request Oct 4, 2020
In v0.12.0 XKNX library have changed the internal OPEN/CLOSED numeric values. From this version 0% is OPEN and 100% is closed.
XKNX/xknx#322

`rts_rflink` must adapt the position values sent and received from the library
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants