Dear all!
How do you set the shift and slope of the heating curve with this binding? The only channel I found for those two is read-only.
Just to let you know, when installing and uninstalling this binding via market place or by dropping the kar file in the addons folder, the openhab cloud service is shutting down:
2024-10-02 19:41:43.722 [INFO ] [io.openhabcloud.internal.CloudClient] - Shutting down openHAB Cloud service connection
2024-10-02 19:41:43.723 [WARN ] [io.openhabcloud.internal.CloudClient] - Socket.IO disconnected: io client disconnect
2024-10-02 19:41:43.724 [INFO ] [io.openhabcloud.internal.CloudClient] - Disconnected from the openHAB Cloud service (UUID = db...9d, base URL = http://localhost:8080)
2024-10-02 19:41:44.083 [WARN ] [ax.web.service.spi.model.ServerModel] - ServletModel{id=ServletModel-71,name='cxf-servlet',urlPatterns=[/*],contexts=[{WB,OCM-1,default,/}]} can't be registered now in context / under "/*" mapping. Conflict with ServletModel{id=ServletModel-29,name='/',urlPatterns=[/*],contexts=[{WB,OCM-1,default,/}]}.
2024-10-02 19:41:44.084 [WARN ] [ax.web.service.spi.model.ServerModel] - Skipped registration of ServletModel{id=ServletModel-71,name='cxf-servlet',urlPatterns=[/*],contexts=[{WB,OCM-1,default,/}]} because of existing mappings. Servlet will be added as "awaiting registration".
I am on openhab 4.3.0.M1
Installation via kar file does not show up in MainUI and adding bridge thing is not possible, allthough bundle:list in openhab console shows that com.qubular.openhab-binding-vicare-bundle and com.qubular.vicare-osgi are active
Only installation via market place was successful.
How are the thing channels detected?
Since my last OH restart, I have 11 health issues (orphaned links), all caused by missing channels in vicare:heating.
F.e. Heating_Circuit_0_Heating_Operating_Mode_Active, Heating_Heating_Power_Consumption_Current_Day, Heating_DHW_Power_Consumption_Current_Day…
They were present before.
The thing is a heat pump VitoCal 200-S, modelId E3_Vitocal.
I am on OH 4.3.0.M1.
Any ideas?
They are determined by whatever the API returns back in its response. If the API stops returning features in the response, the corresponding channels will not be recreated on startup.
From time to time Viessmann do rearrange them. I have tried the binding on 4.3.0M1 and it does appear to work and I see all the features I expect for my own device.
Ah, okay, so maybe a restart or deleting and adding the viessmann heatpump thing again may help…
I will try.