search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.73k stars 29.99k forks source link

No device or entities after reinstall of the integration #107847

Closed ltaferner closed 5 months ago

ltaferner commented 8 months ago

The problem

Hi all!

The day before yesterday Viessmann had problems with their app. After a view hours everything worked fine again. Yesterday I mentioned that the values of my entities didn’t show up again, after a restart of my ha instance. So I tried several times to reload the integration, but nothing worked. So I decided to reinstall the integration and to reconfigure it. After that, the integration showed up again, but there were no device and either no entity.

What version of Home Assistant Core has the issue?

core-2024.1.2

What was the last working version of Home Assistant Core?

core-2024.1.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Viessmann 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?

No response

Additional information

No response

home-assistant[bot] commented 8 months ago

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)

CFenner commented 8 months ago

Is there anything useful in the logs?

fridgee1 commented 8 months ago

Same here. Home Assistant restart, Vicare integration loaded, but provides no entities. Here is my log: 2024-01-12 090738.574 DEBUG ViCare.txt

szymondrozdz commented 8 months ago

Same.

2024-01-12 10:58:50.515 INFO (SyncWorker_6) [homeassistant.components.vicare] Found device: E3_TCU41_x04 (online: True)
2024-01-12 10:58:50.516 INFO (SyncWorker_6) [homeassistant.components.vicare] Found device: E3_Vitodens_100_BHC_0421 (online: True)
2024-01-12 10:58:50.692 DEBUG (SyncWorker_8) [homeassistant.components.vicare.utils] Feature not supported solar_pump_active
2024-01-12 10:58:50.693 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported activate_onetimecharge
2024-01-12 10:58:50.694 DEBUG (SyncWorker_7) [homeassistant.components.vicare.utils] No circuits found
2024-01-12 10:58:50.696 DEBUG (SyncWorker_3) [homeassistant.components.vicare.utils] No circuits found
2024-01-12 10:58:50.697 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported outside_temperature
2024-01-12 10:58:50.698 DEBUG (SyncWorker_12) [homeassistant.components.vicare.utils] No circuits found
2024-01-12 10:58:50.701 DEBUG (SyncWorker_8) [homeassistant.components.vicare.utils] Feature not supported charging_active
2024-01-12 10:58:50.703 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported return_temperature
2024-01-12 10:58:50.704 DEBUG (SyncWorker_8) [homeassistant.components.vicare.utils] Feature not supported dhw_circulationpump_active
2024-01-12 10:58:50.705 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported boiler_temperature
2024-01-12 10:58:50.706 DEBUG (SyncWorker_8) [homeassistant.components.vicare.utils] Feature not supported dhw_pump_active
2024-01-12 10:58:50.706 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported boiler_supply_temperature
2024-01-12 10:58:50.706 DEBUG (SyncWorker_8) [homeassistant.components.vicare.utils] No circuits found
2024-01-12 10:58:50.707 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported primary_circuit_supply_temperature
2024-01-12 10:58:50.708 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported primary_circuit_return_temperature
2024-01-12 10:58:50.714 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported secondary_circuit_supply_temperature
2024-01-12 10:58:50.715 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported secondary_circuit_return_temperature
2024-01-12 10:58:50.715 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported hotwater_out_temperature
2024-01-12 10:58:50.716 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported hotwater_max_temperature
2024-01-12 10:58:50.717 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported hotwater_min_temperature
2024-01-12 10:58:50.717 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported hotwater_gas_consumption_today
2024-01-12 10:58:50.717 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported hotwater_gas_consumption_heating_this_week
2024-01-12 10:58:50.717 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported hotwater_gas_consumption_heating_this_month
2024-01-12 10:58:50.717 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported hotwater_gas_consumption_heating_this_year
2024-01-12 10:58:50.717 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported gas_consumption_heating_today
2024-01-12 10:58:50.717 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported gas_consumption_heating_this_week
2024-01-12 10:58:50.717 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported gas_consumption_heating_this_month
2024-01-12 10:58:50.718 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported gas_consumption_heating_this_year
2024-01-12 10:58:50.718 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported gas_summary_consumption_heating_currentday
2024-01-12 10:58:50.718 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported gas_summary_consumption_heating_currentmonth
2024-01-12 10:58:50.718 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported gas_summary_consumption_heating_currentyear
2024-01-12 10:58:50.718 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported gas_summary_consumption_heating_lastsevendays
2024-01-12 10:58:50.718 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported hotwater_gas_summary_consumption_heating_currentday
2024-01-12 10:58:50.718 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported hotwater_gas_summary_consumption_heating_currentmonth
2024-01-12 10:58:50.718 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported hotwater_gas_summary_consumption_heating_currentyear
2024-01-12 10:58:50.718 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported hotwater_gas_summary_consumption_heating_lastsevendays
2024-01-12 10:58:50.719 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported energy_summary_consumption_heating_currentday
2024-01-12 10:58:50.719 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported energy_summary_consumption_heating_currentmonth
2024-01-12 10:58:50.719 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported energy_summary_consumption_heating_currentyear
2024-01-12 10:58:50.719 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported energy_summary_consumption_heating_lastsevendays
2024-01-12 10:58:50.719 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported energy_dhw_summary_consumption_heating_currentday
2024-01-12 10:58:50.719 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported energy_dhw_summary_consumption_heating_currentmonth
2024-01-12 10:58:50.719 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported energy_dhw_summary_consumption_heating_currentyear
2024-01-12 10:58:50.719 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported energy_summary_dhw_consumption_heating_lastsevendays
2024-01-12 10:58:50.719 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported power_production_current: 'GazBoiler' object has no attribute 'getPowerProductionCurrent'
2024-01-12 10:58:50.719 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported power_production_today: 'GazBoiler' object has no attribute 'getPowerProductionToday'
2024-01-12 10:58:50.720 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported power_production_this_week: 'GazBoiler' object has no attribute 'getPowerProductionThisWeek'
2024-01-12 10:58:50.720 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported power_production_this_month: 'GazBoiler' object has no attribute 'getPowerProductionThisMonth'
2024-01-12 10:58:50.720 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported power_production_this_year: 'GazBoiler' object has no attribute 'getPowerProductionThisYear'
2024-01-12 10:58:50.720 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported solar storage temperature
2024-01-12 10:58:50.720 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported collector temperature
2024-01-12 10:58:50.720 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported solar power production today
2024-01-12 10:58:50.720 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported solar power production this week
2024-01-12 10:58:50.720 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported solar power production this month
2024-01-12 10:58:50.720 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported solar power production this year
2024-01-12 10:58:50.720 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported power consumption today
2024-01-12 10:58:50.721 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported power consumption this week
2024-01-12 10:58:50.721 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported power consumption this month
2024-01-12 10:58:50.721 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported power consumption this year
2024-01-12 10:58:50.721 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported buffer top temperature: 'GazBoiler' object has no attribute 'getBufferTopTemperature'
2024-01-12 10:58:50.721 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported buffer main temperature: 'GazBoiler' object has no attribute 'getBufferMainTemperature'
2024-01-12 10:58:50.721 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] Feature not supported volumetric_flow
2024-01-12 10:58:50.721 DEBUG (SyncWorker_5) [homeassistant.components.vicare.utils] No circuits found
agvdberg commented 8 months ago

Same here home-assistant_vicare_2024-01-12T10-21-54.261Z.log

In the Viessmann-community there are a few discussions about their API and downtime of the server. https://www.viessmann-community.com/t5/Konnektivitaet/GELOeST-Dein-Kommunikationsmodul-ist-nicht-verbunden-Aktuelle/td-p/408286 https://www.viessmann-community.com/t5/Feedback-API/Direktzugriff-auf-Daten-per-VITOCONNECT-100-OPTO1-ohne-Cloud/m-p/259146

fire4you commented 8 months ago

Same here. Since yesterday, no entities available ;-(

Keffu3636 commented 8 months ago

Same here... :(

CFenner commented 8 months ago

Please note that the Viessmann API is currently unstable. Unfortunately, the integration is not that resilient that errors on the API are not propagated to the HA ui.

pacsabi commented 8 months ago

Same here as well. I once reloaded a previous home assistant VM backup, the integration worked for a few hours, but now it's empty

ripero0 commented 8 months ago

Hi, the same thing happened to me yesterday, it arose after a power outage and restarting HA, the vicare integration did not work again, it tells me that there are no devices or entities. I have tried a thousand ways and it doesn't work. I hope viesmann fixes the error.

Mercury0802 commented 8 months ago

Hi, my integration lost some entities after a reboot (dont know what exactly changed / updated). I can't retrieve any values of the buffer temperature of the heating section, compressor state and runtimes. Due to the log, the entities / feature is not supported (...obviously anymore). All the other entities of my vitocal 200-g working quite well :)

ltaferner commented 8 months ago

Nothing new here either 🙄

neikk commented 8 months ago

Same here. Completely lost everything. Thought it is my fault at first, because I changed the underlying hardware. But after a lot of tried rescues, no change.

kuschel100 commented 8 months ago

Same here... :(

ggliniak commented 8 months ago

Also here, the same problem. Vicare App is working again, but not working communication via API in HA. I'm asking myself, if the payed version of API accounts are working again, I'm on a free API plan only...

I'm frustrated that doing research what is my problem I decided to delete the integration and so I lost all entities. Before that task they were only UNKNOWN and my visualization looked much more better than now with not existing entities. ;-)

So let's wait together for Viessmann, but honestly I don't think there will be a fix in the next two days, they will 100% not work at weekend on this error. :-/

ggliniak commented 8 months ago

Additional info: Creating a new API ID in the Viessmann Developer Portal does also not bringing back any entities, you can skip this task for you. (and also: "IT: have you tried to turn it off and on again?") ;-) (I thought maybe Viessmann lost due to the "server crash" any internal mapping between the API Client ID and the ViCare App interface or so, but obviously not)

epoullet commented 8 months ago

Same here :-(

thatguy-za commented 8 months ago

I've also had this issue for the last few days.

What's interesting is that the diagnostics information in HA seems to be correct. E.G it shows that the burner in boiler s currently active but that value isn't being reported to the entity in Home Assistant. image

ggliniak commented 8 months ago

Update from my side due to a hint of a user in the Viessmann Community to test the Viessmann API with Postman, see https://github.com/somm15/PyViCare/tree/63f9f7fea505fdf9a26c77c6cd0bff889abcdb05#api-usage-in-postman

Did this, must say at the moment: Over all the Viessmann API seems to work on the first view, I get valid data from may gas boiler via API, but timestamps of the entries are not always up2date. Some are from today morning but some other have fresh timestamps.

But maybe this can be the problem with the HA integration?

When creating a new Auth-Token in Postman with the "Scope" Field not set (empty), I get a Auth-Token generated. But when using it to poll my systems data I get:

    "viErrorId": "req-101cd74791**********",
    "statusCode": 403,
    "errorType": "NOT_ALLOWED",
    "message": "You are not allowed to Missing required scope"

When I create the Auth-Token with "Scope Field" set with "IoT User" (like in the howto in the link above) it works:

            "commands": {},
            "apiVersion": 1,
            "uri": "https://api.viessmann.com/iot/v1/features/installations/**********/gateways/*********/devices/0/features/heating.sensors.temperature.outside",
            "gatewayId": "7***************",
            "feature": "heating.sensors.temperature.outside",
            "timestamp": "2024-01-13T22:43:59.085Z",
            "isEnabled": true,
            "isReady": true,
            "deviceId": "0"

Has Viessmann changed anything after the server failure?! Maybe the "Missing required scope" answer from the API when scope ist not set is the reason why the integrations gets no entities... @CFenner is there any way to get the Auth-Token handling in your integration more verbose?

ggliniak commented 8 months ago

Actual data really are provided by API when requesting through Postman, this value changed in the last 3 requests with some minutes of distance:

           "properties": {
                "value": {
                    "type": "number",
                    "value": 28.4,
                    "unit": "celsius"
                },
                "status": {
                    "type": "string",
                    "value": "connected"
                }
            },
            "commands": {},
            "apiVersion": 1,
            "uri": "https://api.viessmann.com/iot/v1/features/installations/*********/gateways/************/devices/0/features/heating.boiler.sensors.temperature.commonSupply",
            "gatewayId": "7***********",
            "feature": "heating.boiler.sensors.temperature.commonSupply",
            "timestamp": "2024-01-13T23:07:28.558Z",
            "isEnabled": true,
            "isReady": true,
            "deviceId": "0"
CFenner commented 8 months ago

That's interesting, from other posts it seems that the diagnostic info in HA is also providing data. Very weird that the integration does not work for some users.

You could also try to copy the working token into the .storage/vicare_token.save file to check if that works. But I think if the diagnostic info are ok for you you're fine.

CFenner commented 8 months ago

What devices do you use? In the logs you should see something like this:

Setting up ViCare component
[homeassistant.components.vicare] Found device: E3_TCU10_x07 (online: True)
[homeassistant.components.vicare] Found device: E3_Vitocal (online: True)

As this vicare integration just shows one device (working on that) it could be that Viessmann now returns another device as default than the one that was previously used. Leading to showing a device that has no supported entities.

ggliniak commented 8 months ago

wooohauu

'utf-8' codec can't decode byte 0x80 in position 0: invalid start byte

That is what I found in my .storage/vicare_token.save

ggliniak commented 8 months ago

Yes, I do:

2024-01-14 00:19:36.711 DEBUG (MainThread) [homeassistant.components.vicare] Setting up ViCare component
2024-01-14 00:19:36.895 INFO (SyncWorker_10) [homeassistant.components.vicare] Found device: E3_TCU19_x05 (online: True)
2024-01-14 00:19:36.895 INFO (SyncWorker_10) [homeassistant.components.vicare] Found device: E3_Vitodens_200_0821 (online: True)
2024-01-14 00:19:37.043 DEBUG (SyncWorker_0) [homeassistant.components.vicare.utils] Feature not supported solar_pump_active
2024-01-14 00:19:37.043 DEBUG (SyncWorker_0) [homeassistant.components.vicare.utils] Feature not supported charging_active
2024-01-14 00:19:37.043 DEBUG (SyncWorker_13) [homeassistant.components.vicare.utils] Feature not supported activate_onetimecharge
2024-01-14 00:19:37.043 DEBUG (SyncWorker_21) [homeassistant.components.vicare.utils] No circuits found

... ...

What devices do you use? In the logs you should see something like this:

Setting up ViCare component
[homeassistant.components.vicare] Found device: E3_TCU10_x07 (online: True)
[homeassistant.components.vicare] Found device: E3_Vitocal (online: True)
CFenner commented 8 months ago

Do you know if both of the devices TCU and Vitocal have data points in their API response that should be display in entities in HA?

Maybe simply share the diagnostic info from HA.

ggliniak commented 8 months ago

Sorry, forget this. In my Terminal all is fine. Need to find out how to put the Postman generated Auth Token in the right coding into the file...

wooohauu

'utf-8' codec can't decode byte 0x80 in position 0: invalid start byte

That is what I found in my .storage/vicare_token.save

CFenner commented 8 months ago

Check the diagnostics first! Otherwise you can spare this.

ggliniak commented 8 months ago

This is my debug log from HA when configuring the integration. Nothing to find that is helpful at the moment :-(

2024-01-14 00:19:36.711 DEBUG (MainThread) [homeassistant.components.vicare] Setting up ViCare component
2024-01-14 00:19:36.895 INFO (SyncWorker_10) [homeassistant.components.vicare] Found device: E3_TCU19_x05 (online: True)
2024-01-14 00:19:36.895 INFO (SyncWorker_10) [homeassistant.components.vicare] Found device: E3_Vitodens_200_0821 (online: True)
2024-01-14 00:19:37.043 DEBUG (SyncWorker_0) [homeassistant.components.vicare.utils] Feature not supported solar_pump_active
2024-01-14 00:19:37.043 DEBUG (SyncWorker_0) [homeassistant.components.vicare.utils] Feature not supported charging_active
2024-01-14 00:19:37.043 DEBUG (SyncWorker_13) [homeassistant.components.vicare.utils] Feature not supported activate_onetimecharge
2024-01-14 00:19:37.043 DEBUG (SyncWorker_21) [homeassistant.components.vicare.utils] No circuits found
2024-01-14 00:19:37.043 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported outside_temperature
2024-01-14 00:19:37.043 DEBUG (SyncWorker_9) [homeassistant.components.vicare.utils] No circuits found
2024-01-14 00:19:37.044 DEBUG (SyncWorker_0) [homeassistant.components.vicare.utils] Feature not supported dhw_circulationpump_active
2024-01-14 00:19:37.044 DEBUG (SyncWorker_3) [homeassistant.components.vicare.utils] No circuits found
2024-01-14 00:19:37.044 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported return_temperature
2024-01-14 00:19:37.044 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported boiler_temperature: 'HeatingDevice' object has no attribute 'getBoilerTemperature'
2024-01-14 00:19:37.044 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported boiler_supply_temperature: 'HeatingDevice' object has no attribute 'getBoilerCommonSupplyTemperature'
2024-01-14 00:19:37.044 DEBUG (SyncWorker_0) [homeassistant.components.vicare.utils] Feature not supported dhw_pump_active
2024-01-14 00:19:37.044 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported primary_circuit_supply_temperature
2024-01-14 00:19:37.045 DEBUG (SyncWorker_0) [homeassistant.components.vicare.utils] No circuits found
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported primary_circuit_return_temperature
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported secondary_circuit_supply_temperature
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported secondary_circuit_return_temperature
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported hotwater_out_temperature
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported hotwater_max_temperature
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported hotwater_min_temperature
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported hotwater_gas_consumption_today: 'HeatingDevice' object has no attribute 'getGasConsumptionDomesticHotWaterToday'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported hotwater_gas_consumption_heating_this_week: 'HeatingDevice' object has no attribute 'getGasConsumptionDomesticHotWaterThisWeek'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported hotwater_gas_consumption_heating_this_month: 'HeatingDevice' object has no attribute 'getGasConsumptionDomesticHotWaterThisMonth'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported hotwater_gas_consumption_heating_this_year: 'HeatingDevice' object has no attribute 'getGasConsumptionDomesticHotWaterThisYear'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported gas_consumption_heating_today: 'HeatingDevice' object has no attribute 'getGasConsumptionHeatingToday'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported gas_consumption_heating_this_week: 'HeatingDevice' object has no attribute 'getGasConsumptionHeatingThisWeek'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported gas_consumption_heating_this_month: 'HeatingDevice' object has no attribute 'getGasConsumptionHeatingThisMonth'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported gas_consumption_heating_this_year: 'HeatingDevice' object has no attribute 'getGasConsumptionHeatingThisYear'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported gas_summary_consumption_heating_currentday: 'HeatingDevice' object has no attribute 'getGasSummaryConsumptionHeatingCurrentDay'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported gas_summary_consumption_heating_currentmonth: 'HeatingDevice' object has no attribute 'getGasSummaryConsumptionHeatingCurrentMonth'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported gas_summary_consumption_heating_currentyear: 'HeatingDevice' object has no attribute 'getGasSummaryConsumptionHeatingCurrentYear'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported gas_summary_consumption_heating_lastsevendays: 'HeatingDevice' object has no attribute 'getGasSummaryConsumptionHeatingLastSevenDays'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported hotwater_gas_summary_consumption_heating_currentday: 'HeatingDevice' object has no attribute 'getGasSummaryConsumptionDomesticHotWaterCurrentDay'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported hotwater_gas_summary_consumption_heating_currentmonth: 'HeatingDevice' object has no attribute 'getGasSummaryConsumptionDomesticHotWaterCurrentMonth'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported hotwater_gas_summary_consumption_heating_currentyear: 'HeatingDevice' object has no attribute 'getGasSummaryConsumptionDomesticHotWaterCurrentYear'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported hotwater_gas_summary_consumption_heating_lastsevendays: 'HeatingDevice' object has no attribute 'getGasSummaryConsumptionDomesticHotWaterLastSevenDays'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported energy_summary_consumption_heating_currentday: 'HeatingDevice' object has no attribute 'getPowerSummaryConsumptionHeatingCurrentDay'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported energy_summary_consumption_heating_currentmonth: 'HeatingDevice' object has no attribute 'getPowerSummaryConsumptionHeatingCurrentMonth'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported energy_summary_consumption_heating_currentyear: 'HeatingDevice' object has no attribute 'getPowerSummaryConsumptionHeatingCurrentYear'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported energy_summary_consumption_heating_lastsevendays: 'HeatingDevice' object has no attribute 'getPowerSummaryConsumptionHeatingLastSevenDays'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported energy_dhw_summary_consumption_heating_currentday: 'HeatingDevice' object has no attribute 'getPowerSummaryConsumptionDomesticHotWaterCurrentDay'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported energy_dhw_summary_consumption_heating_currentmonth: 'HeatingDevice' object has no attribute 'getPowerSummaryConsumptionDomesticHotWaterCurrentMonth'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported energy_dhw_summary_consumption_heating_currentyear: 'HeatingDevice' object has no attribute 'getPowerSummaryConsumptionDomesticHotWaterCurrentYear'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported energy_summary_dhw_consumption_heating_lastsevendays: 'HeatingDevice' object has no attribute 'getPowerSummaryConsumptionDomesticHotWaterLastSevenDays'
2024-01-14 00:19:37.045 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported power_production_current: 'HeatingDevice' object has no attribute 'getPowerProductionCurrent'
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported power_production_today: 'HeatingDevice' object has no attribute 'getPowerProductionToday'
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported power_production_this_week: 'HeatingDevice' object has no attribute 'getPowerProductionThisWeek'
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported power_production_this_month: 'HeatingDevice' object has no attribute 'getPowerProductionThisMonth'
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported power_production_this_year: 'HeatingDevice' object has no attribute 'getPowerProductionThisYear'
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported solar storage temperature
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported collector temperature
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported solar power production today
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported solar power production this week
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported solar power production this month
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported solar power production this year
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported power consumption today: 'HeatingDevice' object has no attribute 'getPowerConsumptionToday'
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported power consumption this week: 'HeatingDevice' object has no attribute 'getPowerConsumptionThisWeek'
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported power consumption this month: 'HeatingDevice' object has no attribute 'getPowerConsumptionThisMonth'
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported power consumption this year: 'HeatingDevice' object has no attribute 'getPowerConsumptionThisYear'
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported buffer top temperature: 'HeatingDevice' object has no attribute 'getBufferTopTemperature'
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported buffer main temperature: 'HeatingDevice' object has no attribute 'getBufferMainTemperature'
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] Feature not supported volumetric_flow: 'HeatingDevice' object has no attribute 'getVolumetricFlowReturn'
2024-01-14 00:19:37.046 DEBUG (SyncWorker_11) [homeassistant.components.vicare.utils] No circuits found
CFenner commented 8 months ago

Please select your vicare device and click on the ... do download the diagnostics information.

ggliniak commented 8 months ago

And this is the full diagnostics

config_entry-vicare-626306581539549395f1ab09c734c995.json.txt

ggliniak commented 8 months ago

Also here in the diagnostics I see valid data and fresh timestamps. I'm completely confused now because I do have no entities. Bildschirmfoto 2024-01-14 um 00 36 12

CFenner commented 8 months ago

Ok, great, as I suspected!

Bildschirmfoto 2024-01-14 um 00 34 32

The first device is empty which is the one that is used by HA. So please checkout my PR: https://github.com/home-assistant/core/pull/96044

This is not yet finalized, but essential working and can handle multiple devices.

You need to run a commend on your terminal in HA.

curl -o- -L https://gist.githubusercontent.com/bdraco/43f8043cb04b9838383fd71353e99b18/raw/core_integration_pr | bash /dev/stdin -d vicare -p 96044

This will create a copy of the code from the PR and add it to your custom_components, overwriting the default integration. Restart HA after that.

ggliniak commented 8 months ago

Thank you @CFenner, can confirm it is working again with your workaround! Back in business, Kids can shower tomorrow morning and HA can control the amount of warm water again 😬😂

Bildschirmfoto 2024-01-14 um 00 44 59

CFenner commented 8 months ago

Great, let's share the news!

I've another PR that would allow user to select the device they want to use: https://github.com/home-assistant/core/pull/107906 Maybe that is easier to release that we can get this out in a hotfix soon.

ggliniak commented 8 months ago

Great, let's share the news!

Yes sure, I will post it to the Viessmann User Community where also HA Users requested help :-) Thank you very much with your night time support 🤩

ltaferner commented 8 months ago

@CFenner - it‘s working again - you are the best 🥳

epoullet commented 8 months ago

Hi, maybe I missed something but when running the CURL command and restarting HA after that, It doesn't work on my HA and I sill see no entities or no device. When running the CURL command, I got this message in terminal : Screenshot 2024-01-14 at 09 50 37 any idea ?

neikk commented 8 months ago

Hi, maybe I missed something but when running the CURL command and restarting HA after that, It doesn't work on my HA and I sill see no entities or no device. When running the CURL command, I got this message in terminal : Screenshot 2024-01-14 at 09 50 37 any idea ?

You have to switch to directory: "/root/homeassistant".

Then curl command and then restart HA.

Good luck.

And thanks again @CFenner . Back in production with my vicare since 02:00 CET 😘

epoullet commented 8 months ago

ooops ! my mistake ! Many thanks to you and to @CFenner for his dedication !

pacsabi commented 8 months ago

Great work! I can’t thank you enough!

fridgee1 commented 8 months ago

How can I use this solution if I use home assistant in docker? Thanks in advance

CFenner commented 8 months ago

How can I use this solution if I use home assistant in docker? Thanks in advance

You need to somehow run the command above. Do you have the terminal add-on with the HA Docker or a SMB share? You can also do that from your host if you step into the /config folder with a terminal and run the command there.

Keffu3636 commented 8 months ago

Thanks to all, got it working again. Suggestion to Viessmann to rename their brand from vicare to vidontcare :)

fridgee1 commented 8 months ago

image

It works! Thank you, @CFenner

the screenshot is for everyone with the same problem and Home Assistant on a Synology NAS as a Docker container. Just create a new terminal in your Home Assistant container and paste* that curl command from above.

*if ctrl+v don't work, press ctrl+a first and then ctrl+v

handy21 commented 8 months ago

How can I use this solution if I use home assistant in docker? Thanks in advance

You need to somehow run the command above. Do you have the terminal add-on with the HA Docker or a SMB share? You can also do that from your host if you step into the /config folder with a terminal and run the command there.

These Fix works great also on a Raspy- Installation, Thank you very much!!!

ripero0 commented 8 months ago

Thank you very much for your work and help @CFenner, it works for me again. Greetings

coro1404 commented 8 months ago

works perfectly! how to get back on the official update path once it's release?

CFenner commented 8 months ago

works perfectly! how to get back on the official update path once it's release?

Just remove the vicare folder from /config/custom_components.

4stepup commented 8 months ago

How(Where) do I have to change the directory as mentiond by @ neikk?

You have to switch to directory: "/root/homeassistant". Then curl command and then restart HA. Good luck. And thanks again @CFenner . Back in production with my vicare since 02:00 CET 😘

Many thanks in advance.

neikk commented 8 months ago

How(Where) do I have to change the directory as mentiond by @ neikk?

You have to switch to directory: "/root/homeassistant". Then curl command and then restart HA. Good luck. And thanks again @CFenner . Back in production with my vicare since 02:00 CET 😘

Many thanks in advance.

Depends on your setup. HAOS (one way): get a CLI (e.g. advanced ssh & web terminal add-on). And then on the CLI "cd /root/homeassistant" And then copy paste the curl command (the whole command).

But as far as I know the community. If you are not sure, wait for the general update. Couldn't be a long wait time 😁