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.

Sign up for GitHub

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

Jump to bottom

Update PyViCareGazBoiler.py #25

Merged
merged 1 commit into from
Mar 9, 2020
Merged

Update PyViCareGazBoiler.py #25

merged 1 commit into from
Mar 9, 2020

Conversation

stefanwi87
Copy link
Contributor

ViCare delivers information about the burner starts and burner hours (time how long the burner was used, e.g. 6200h). Added these two statistic values of burner.

@stefanwi87
Update PyViCareGazBoiler.py
eea2e0d 
ViCare delivers information about the burner starts and burner hours (time how long the burner was used, e.g. 6200h). Added these two statistic values of burner.
@ddokupil
Copy link

Awesome, do we have maybe some more "low hanging fruits" do add easily?

@stefanwi87 stefanwi87 mentioned this pull request Feb 28, 2020
Closed
20 tasks
@somm15 somm15 merged commit 5a030b5 into openviess:master Mar 9, 2020
@oischinger
Copy link
Contributor

@somm15 Could you please release a new version on pypi?
There is already an HA Core PR to make use of those properties: home-assistant/core#32304

Thanks alot!

@vandenberghev
Copy link

vandenberghev commented Mar 13, 2020 •
edited
Loading

I wouldn't bother; I just got a big "fuck you" e-mail from Viessmann saying they'll be closing off API access for all third-party applications.

an evaluation has shown that you have used the web interface to Viessmann IoT Services very frequently in recent days.

On the one hand, we are delighted to know you are taking a closer look at our products and solutions. Especially since you have (apparently) found a solution for your specific use case without a description or our support from our side.
On the other hand, it challenges us to check and channel the method and frequency of requests to our IoT Services in order to keep those stable and available for all our users.

That’s why we have now taken the decision to limit access to our API. From the coming week on, a threshold will become active that prevents from unauthorized use of the API. This will affect all third-party solutions, which can thereby no longer be used.

We are aware that the demand for APIs to our technologies for integration into other solutions and third-party systems is increasing. To provide you with an opportunity for this, we will launch a portal in the next two months for all developers to get access to our API. With the Viessmann Developer Portal, we intend to open ourselves up, release a documentation of the interface and co-develop new solutions together with you. In addition, we are planning to provide you with useful information around our heating systems you need for your development and to offer you a first-level support concerning our APIs.

As one of the users who is already working with our API, we would like to invite you to an early access to the Developer Portal. If you are interested, please fill out this short form. The access to the pre-version of the Portal will be sent to you within the next weeks.

We hope you understand the decision that we have to take. If you are interested to support us, on further development on the API and to explore new possibilities, we are very happy to welcome you to our Developer Portal soon!

In the meantime in case you have any questions, feel free to contact us under [email protected].

Thank you for your understanding.

All the best!

Your Viessmann Developer Portal Team

I wouldn't hold out hope for the 'developer portal' as it's probably just a way to monetize the API.

@ddokupil
Copy link

It'd be even ok as long as it's well documented and fair priced. The question is if it's going to happen any soon or they will disable access without enabling developer api.
Remember we can still use https://github.com/openv, but obviously it is way less convenient.

Could we also opt for access to pre-version?

@oischinger
Copy link
Contributor

https://www.viessmann-community.com/t5/Experten-fragen/Q-amp-A-Viessmann-API/qaq-p/127660

@somm15
Copy link
Collaborator

somm15 commented Mar 16, 2020

I did upgrade the pip package .... but rate limiting is now in place.
So it doesn't work anymore.
F**** Viessmann

CFenner referenced this pull request in CFenner/PyViCare Dec 26, 2023
@somm15
Merge pull request #25 from stefanwi87/patch-1
9289b46 
Update PyViCareGazBoiler.py
CFenner added a commit that referenced this pull request Sep 6, 2024
@CFenner
feat: expose Hysteresis data points (#392)
d601f3e 
* feat: expose hysteresis value data points (#19)

* update test data

* add hysteresis getter

* add setDomesticHotWaterHysteresis

* move to heat pump

* add test case

* update

* feat: expose Hysteresis data points (#25)

* update test data

* add hysteresis getter

* add setDomesticHotWaterHysteresis

* move to heat pump

* add test case

* update

* add switchOn switchOff temp setter

* add test cases

* add types

* fix type in setter

* add tes cases

* remove duplicate test case

* add missing type
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@stefanwi87 @ddokupil @oischinger @vandenberghev @somm15