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

vicare integration is not working anymore #121429

Open
huebnerthomas opened this issue Jul 7, 2024 · 8 comments
Open

vicare integration is not working anymore #121429

huebnerthomas opened this issue Jul 7, 2024 · 8 comments

Comments

@huebnerthomas
Copy link

The problem

The vicare integration entities were not available anymore. After a new installation of the integration the integration throw errors.

What version of Home Assistant Core has the issue?

2024.7.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

vicare

Link to integration documentation on our website

https://www.home-assistant.io/integrations/vicare/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Errors in the LOG's

ogger: ViCare
Quelle: components/vicare/button.py:44
Erstmals aufgetreten: 12:45:13 (4 Vorkommnisse)
Zuletzt protokolliert: 12:48:54

Missing 'data' property when fetching data.


Logger: homeassistant.components.button
Quelle: helpers/entity_platform.py:364
Integration: Taste ([Dokumentation](https://www.home-assistant.io/integrations/button), [Probleme](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+button%22))
Erstmals aufgetreten: 12:45:13 (4 Vorkommnisse)
Zuletzt protokolliert: 12:48:54

Error while setting up vicare platform for button
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 364, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/usr/src/homeassistant/homeassistant/components/vicare/button.py", line 76, in async_setup_entry
    await hass.async_add_executor_job(
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/vicare/button.py", line 63, in _build_entities
    if is_supported(description.key, description, device.api)
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/vicare/utils.py", line 37, in is_supported
    entity_description.value_getter(vicare_device)
  File "/usr/src/homeassistant/homeassistant/components/vicare/button.py", line 44, in <lambda>
    value_getter=lambda api: api.getOneTimeCharge(),
                             ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/PyViCare/PyViCareUtils.py", line 55, in feature_flag_wrapper
    return wrapper(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/PyViCare/PyViCareUtils.py", line 48, in wrapper
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/PyViCare/PyViCareHeatingDevice.py", line 275, in getOneTimeCharge
    return self.service.getProperty("heating.dhw.oneTimeCharge")["properties"]["active"]["value"]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/PyViCare/PyViCareCachedService.py", line 24, in getProperty
    data = self.__get_or_update_cache()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/PyViCare/PyViCareCachedService.py", line 45, in __get_or_update_cache
    raise PyViCareInvalidDataError(data)
PyViCare.PyViCareUtils.PyViCareInvalidDataError: {'viErrorId': '|00-de68ed18ebee4ca59f33edd448ac8e1a-bc980c246514448c-01.588c25fb_', 'statusCode': 400, 'errorType': 'DEVICE_COMMUNICATION_ERROR', 'message': '', 'extendedPayload': {'httpStatusCode': 'NotFound', 'code': '404', 'reason': 'GATEWAY_OFFLINE'}}

Additional information

No response

@home-assistant

This comment was marked as outdated.

@home-assistant
Copy link

home-assistant bot commented Jul 7, 2024

Hey there @CFenner, mind taking a look at this issue as it has been labeled with an integration (vicare) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of vicare can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign vicare Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


vicare documentation
vicare source
(message by IssueLinks)

@huebnerthomas
Copy link
Author

I suppose i've found the rootcause. I have a hybrid solution with a Vitocal 250-AH and a Vitodens 100-W.
I switched of the Vitodens 100-W. If I switch on the Vitodens 100-W again - Everything is working.
Is there a solution that I can switch off the Vitodens 100-W and the integration is still running ?

@CFenner
Copy link
Contributor

CFenner commented Jul 7, 2024

Interesting…!
Can you post the diagnostic info from both states?

@CFenner
Copy link
Contributor

CFenner commented Jul 7, 2024

I guess each platform iterates over all devices without caring about any error, this all devices that are in line after an error occurs are not initialized.

I have two devices myself and should be able to reproduce this.

@huebnerthomas
Copy link
Author

Hi please find attached the Diagnostic information of the two devices.

config_entry-vicare1.json
config_entry-vicare2.json

I have now deicsonnected the communication module in the VICare-App of the Vitodens 100-W. Let's see if the AH-250 is now still delivering data.

@CFenner
Copy link
Contributor

CFenner commented Jul 8, 2024

The files are actually the same, could be that the device was turned on, but the state was not (yet) reflected in the API response.

Can you please have a look at the beginning of the vicare logs. Is any of the devices marked as offline?

2024-07-08 05:48:26.877 DEBUG (SyncWorker_4) [custom_components.vicare] Found device: VScotHO1_40 (online: False)
2024-07-08 05:48:26.877 DEBUG (SyncWorker_4) [custom_components.vicare] Found device: VScotHO1_72 (online: True)

@huebnerthomas
Copy link
Author

Hi Christopher,

I have disonnected the communication module in the ViCare-App of the Vitodens 100-W and turned the Vitodens off.
The AH-250 is still deliverung now data. This is fine for me. Thx a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants