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

[innogysmarthome] Remove binding (replaced by livisismarthome) #14674

Closed
Novanic opened this issue Mar 25, 2023 · 0 comments · Fixed by #14675
Closed

[innogysmarthome] Remove binding (replaced by livisismarthome) #14674

Novanic opened this issue Mar 25, 2023 · 0 comments · Fixed by #14675
Labels
bug An unexpected problem or unintended behavior of an add-on

Comments

@Novanic
Copy link
Contributor

Novanic commented Mar 25, 2023

The innogysmarthome binding should get removed, because there is a new binding "livisismarthome" since OpenHAB 3.3.0.

The innogysmarthome binding will stop working soon (at least in early 2024) because the cloud API will get shutdown. The new livisismarthome binding isn't affected by this issue, because it uses a new local API (which is also faster and more reliable).

See #12440 for more information.

@Novanic Novanic added the bug An unexpected problem or unintended behavior of an add-on label Mar 25, 2023
Novanic added a commit to Novanic/openhab-docs that referenced this issue Mar 25, 2023
The innogysmarthome binding will get removed, see issue openhab/openhab-addons#14674

Signed-off-by: Sven Strohschein <sven.strohschein@gmail.com>
Signed-off-by: Sven Strohschein <novanic@gmx.de>
Confectrician pushed a commit to openhab/openhab-docs that referenced this issue Apr 2, 2023
The innogysmarthome binding will get removed, see issue openhab/openhab-addons#14674

Signed-off-by: Sven Strohschein <sven.strohschein@gmail.com>
Signed-off-by: Sven Strohschein <novanic@gmx.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An unexpected problem or unintended behavior of an add-on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant