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

[tado] Add channel for PresenceState and support setting HOME/AWAY. Fixes #8826 #8854

Closed
wants to merge 1 commit into from

Conversation

Pro
Copy link
Contributor

@Pro Pro commented Oct 24, 2020

[tado] Add channel for PresenceState and support setting HOME/AWAY

This PR adds the support for reading the Tado Home Presence State (HOME/AWAY) and adds support for changing the HOME/AWAY state through OpenHAB.
See also #8826

@Pro Pro force-pushed the tado_presence branch 2 times, most recently from c440ad4 to 22e4a95 Compare October 24, 2020 14:47
…ixes openhab#8826

Signed-off-by: Stefan Profanter <pro@users.noreply.github.com>
@TravisBuddy
Copy link

Hey @Pro,
Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

View build log

TravisBuddy Request Identifier: f89f2fa0-160d-11eb-94fa-edf6748ec8ed

@Pro
Copy link
Contributor Author

Pro commented Oct 24, 2020

I had to update the Api package, which is included in this bundle under src/main/api

org.openhab.binding.tado:api-client:jar:1.4.1

It seems this is not automatically build/included by the pom file.
I'm not a maven expert, therefore I'm not sure how to fix the build error.

Can someone please advise?
Thanks!

@wborn
Copy link
Member

wborn commented Oct 24, 2020

Thanks for your PR! As explained in #8512, all PRs should target OH3 and be made against the main branch. Can you recreate/update the PR for OH3?

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.

3 participants