Closed ThomasBergholdWieser closed 6 months ago
had the same Problem, also a reload did not help at the first time. Did the reload again at 09:05 AM and now it works again, maybe a problem with the vaillant api itself
edit: same problem again, just worked for about 5 mins
Hi, same error here, this line is telling you it's an API problem. Error 500 is always a server error.
2024-03-05 08:36:14.894 ERROR (MainThread) [custom_components.mypyllant.coordinator] Error fetching myVAILLANT data: 500, message='Internal Server Error', url=URL('https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/emf/v2/899af599-23e9-46b6-9988-3cc3e37cb006/currentSystem')
Hello; Yesterday I had an update on Android to version 2.14.0. This is surely the cause. On my samsung T715 tablet, I have an error message and unable to connect while on my oppo Find x5 it seems to work
Hello, i have same issue. I had similar issue in app on my phone (iOS) all informations and settings were unavailable but i have done update of "myVAILLANT" app and application is OK now. But in HASS same issue - "no longer provided by the integration".
Seems like vaillant server issues or change of API with the newest App version.
I can add that today, starting with approx 0:30 am, the server connection seems to be very unstable (seen from HA, I haven't checked the app). There are many server errors (500), and for longer periods the corresponding sensors are unavailable. But it does recover time-to-time, so the server is sometimes still reachable. So (for now) it doesn't seem to be a breaking API change (then it would be consistently unreachable), but just server accessibility problems. It was exactly one week ago when there were also server accessibility problems. Maybe Vaillant is doing some maintenance on Tuesdays?
This integration is still off, but my Android myVAILLANT works correctly
works now since about 2 hours, integration reload was required
yes, thanks
Its coming up and down again (down again right now) so i think the API is to blame here. I am probably just a bit confused how integrations work when something like this happens. What i mean is why it suddenly reports all entities as "not provided", as they are in fact provided, but just not available right now since the API is down. This is confusing to me (as a user) since this seems a bit misleading. Might be a general home assistant "problem", since the same thing happens with eg. rainbird if it fails to connect to HA for a short time.
However i think this should be closed since its probably not an issue with the integration. But i'll let the repo owner decide what to do here.
Looks like this is still a Problem. I can´t get it back to Work. Since 2-3 Days i have no Data. Reload etc... Nothing works.
@signalkraft
Any news on this? Do you need more Data from us?
Thanks!
@Brudertac i had some problem this week, but since yesterday everything works fine in my scenario...
@Brudertac are things working again for you?
No, but i opened a new Case here: https://github.com/signalkraft/mypyllant-component/issues/142
Thanks.
Before submitting a new issue
Problem description
All entities of the integration are marked as no longer provided by it, therefore making it unusable. The official app itself still works, so the system seems to be online and working fine. It seems to be related to the integration.
Logs