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.
That behaviour can actually become a bit of a nuisance as for example my vitotrol 300e room thermostat loses connectivity every once in a while (for your entertainment: the idiots at Viessmann had the glorious idea of connecting it via proprietary zigbee without wired option. Our heatpump sits in the cellar behind armed concrete walls), which means that the channels are lost after reboot.
Actually, in my case, not only are the channels lost but after clean-cache and reboot, the entire binding is lost and needs to be reinstalled.
I think Iāve ssen someone else running into that issue but I could not find any fix to that. Does anybody have an idea why it is removed after reboot?
Why are you clearing the cache? The channels will be rediscovered when the service starts responding with them again. The discovery process runs at startup and every hour, if you need to re-run it it should be sufficient to pause and unpause the bridge. The channel IDs do not change as they are derived from the feature names and if they reappear will reconnect to their original items. My boiler also loses connectivity every so often and I never have to do this.
The z-wave binding required clearing the cache. Also after upgrades to a newer OH version it is usually a good idea to clear the cache.
I also have this problem every āsomeā restarts of OH, no idea why.
Here, the channels did not reappear after some hours (even not after days), but a restart of OH brought them back.
Hi, have you solved this issue?
I am asking because I now moved from openhab 3 to 4. Before I had my heat pump authorised, but right now I am unable to do so.
Additionaly all the time I click on Authorise vicare binding I get the following in the openhab log
2024-10-20 14:50:06.764 [WARN ] [ernal.tokenstore.PersistedTokenStore] - Unable to store access token
java.io.IOException: Permission denied
Iām unable to reproduce this issue. I believe it must be something specific to your openhab installation.
A request for newbies: When you start you state that you authories the system under
http:///vicare/setup
Can you please update this to use http://your openhab:8080/vicare/setup ?
Without the port it does not work and it is not that selfevident what to do.
Thanks - it prevents extra work!
Hello everybody,
first of all, thanks for the great work for developing the OpenHAB addon. We are running a Vitodens 200W. In our case we are using heating circuit number 2. That heating circuit is present in the app so it should be also in the API, however the OpenHAB plugin does not show it. Would there be the possibility to release a plugin version which also includes heating circuits 2?
Thanks
Also Hello,
I am running a Hybrid Vitocaldens (gas boiler and heat pump) It would help quite a bit if the energy costs could also be read and even better written.
Atm, the system decides based on these number whether the boiler or the heat pump is cheaper to be used - if it is cold then the boiler kicks in - even if you have a pv with surplus which would change the cost perspective.
I am not sure whether these costs are transparent because the Vicare app do not show them - that is something you have to put into the boiler control itself.
The binding works well now.
However, it generates a lot of the following error messages in the logs:
2024-11-18 17:56:56.877 [ERROR] [al.ChannelCommandDescriptionProvider] - Dynamic command description matches original command description. DynamicCommandDescriptionProvider implementations must never return the original command description. class com.qubular.openhab.binding.vicare.internal.DeviceDynamicCommandDescriptionProvider has to be fixed.
It doesnāt seem to do any harm, just spams the logfile (and seems to keep the server very busy).
So is any body else seeing those messages?
Is this something that needs to be fixed in the binding (in which case I am happy to create a ticket), or is that related to my installation/configuration?
I also did see lots and lots of these log entries, but since several month the binding is broken. So i had to switch to the other Viessmann binding (which has no log issues).
The Viessmann API is changed at some data points (Name change). Is there any plan to update the openHAB binding accordingly ? Uli
Most of the things which have changed name, are supported with the generic data point support so the names may not be rendered correctly but the values will still be there. I donāt have json files for most of the properties especially the fuel cell, heat pump and ventilation because nobody has sent me any, so cannot say whether they will work correctly as I do not know exactly how they are represented.
The bufferCylinder stuff, I think one person sent me a json (in the old format), I think with the new format they will still appear but without pretty-printed names.
reducedEnergySaving program name change, I think should work already as some devices seemed to already report this
heating.co2.saving - absolutely no idea what this is, but itās a paid feature I think nobody has.
I donāt have a specific plan to update them because itās a bit like whack-a-mole - without concrete test case where I can say yes it works or no it doesnāt, it is somewhat of a stab in the dark.
Thanks for this explanation and for the fast feedback. As Iām new here, can someone support me with the question: How can I use generic data points. Is there an example or tutorial available ?
I can provide a json for a heatpump (vitocal 252a) and Iām happy to text stuff.
Unfortunately I never managed an Openhab development environment, otherwise I would try to dig to contribute.