I ported the code to OH3 and created a org.openhab.binding.resol-3.0.0-SNAPSHOT.jar based on the ported code. See also my comment in the PR.
Thanks for these efforts @wborn, but the jar as is doesnāt work for the interesting datapoints, we get only the channels for String and DateTime types in that version. I left some technical question in the PR and will hopefully be able to create a new jar āsoonā.
So here is a org.openhab.binding.resol.jar of the resol binding that works for me on OH3.
Feedback is warmly welcome.
At first thanks for this binding, it helped and is still helping me a lot!
A few days ago I upgraded to OH3 and it works in general like a charm, same as on 2.5.
The only thing I am struggling is that I get too much entries in log.
I tried to set log level to ERROR only but this does not work, I am still getting INFO entries every few seconds:
2020-12-25 21:30:36.893 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'DeltasolTemp1' changed from 2.1 Ā°C to 2.2 Ā°C
2020-12-25 21:30:36.896 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'DeltasolTemp2' changed from 13.5 Ā°C to 13.600000000000001 Ā°C
2020-12-25 21:30:41.929 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'DeltasolTemp1' changed from 2.2 Ā°C to 2.1 Ā°C
2020-12-25 21:30:43.887 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'DeltasolTemp2' changed from 13.600000000000001 Ā°C to 13.5 Ā°C
2020-12-25 21:30:45.890 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'DeltasolTemp1' changed from 2.1 Ā°C to 2.2 Ā°C
2020-12-25 21:30:47.937 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'DeltasolTemp1' changed from 2.2 Ā°C to 2.1 Ā°C
2020-12-25 21:30:47.940 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'DeltasolTemp2' changed from 13.5 Ā°C to 13.600000000000001 Ā°C
2020-12-25 21:30:50.940 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'DeltasolTemp2' changed from 13.600000000000001 Ā°C to 13.5 Ā°C
2020-12-25 21:30:52.890 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'DeltasolTemp2' changed from 13.5 Ā°C to 13.600000000000001 Ā°C
2020-12-25 21:30:52.893 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'DeltasolTemp3' changed from 51.900000000000006 Ā°C to 51.800000000000004 Ā°C
2020-12-25 21:30:54.885 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'DeltasolTemp1' changed from 2.1 Ā°C to 2.2 Ā°C
2020-12-25 21:30:54.889 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'DeltasolTemp2' changed from 13.600000000000001 Ā°C to 13.5 Ā°C
2020-12-25 21:30:54.892 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'DeltasolTemp3' changed from 51.800000000000004 Ā°C to 51.900000000000
Is there a way to stop or even reduce this?
Thanks for the feedback. Currently the finding just forwards every update from the resol controller to OH and yes, the values are jittering due to noise. I have heard that on other bindings this is somehow filtered, but I am not convinced, that it should be the job of the binding to do this noise filtering, as it is a common issue and it seems strange to implement such a thing in each binding.
So in a sense I would say that the best would be to put that filtering into the heart of OH as a property of the item to trigger update actions only if the change since the last update was sufficiently big, or maybe implement a Profile for this behavior. - With that no action would be taken due to many of these item state changesā¦
Another reason why I donāt want this to be done in the binding directly is that I donāt see a general solution fitting all supported datatypes. Should it also be applied on volume flows and sun irradiation, on humidity and pressure values and what would be the threshold to trigger a new update but still remove the jitter?
Thanks for your reply.
If the data going 1:1 into OH this is fine, but what I meant is the loglevel.
Even if I set level to Error I have these Info entries.
Iād say this is not related to the resol binding. I would try to adjust log4j2.xml to log the ItemStateChangedEvents to a different level or move it to a different file whatever fits your needs.
Maybe that is a little outdated (at least for me the files change a little), but you could read here:
Okay, will try that.
Thanks for the link!
Just to let you know, the binding made it into the official openhab source tree, the ticket to add the support is close and openhab now officially supports resol solar controllers (ok, starting from the next Milestone build for 3.1 M4).
Thanks for all the feedback I received here and all your patience to get this one done. Stay tuned, and please report bugs from now on directly in the issue tracker of the openhab-addons repository.
I would like to add custom logic with Resol Controllers ? is there any specific model that i can use to add the logic ?
basically, when one of the thermostat is out of defined range 6C<S1<95C then energize R3.
Hi, this is not really possible from openhab. Only some of the controllers like the DelataSol MX support the extension modules EM. - these can be emulated by the resolbinding and then be used as a workaround to implement custom logic in OH. - on the other side I think the logic you describe can be achieved already with this controller aloneā¦
At first thank you for this great binding!
I have optimized my solar system what would not be possible without it.
But I am still looking for a possibility to get rid of the overload during the hottest season we have year by year in summer.
I remeber @danielwippermann mentioned in a thread which I did not find that it is not possible or recommended to adjust parameter by the binding.
What I would need is a possibility to start the pump manually by a rule, so not really an adjustment of parameter.
The Resol control allows to cool the boiler but this is not comfortable as it relies on the histeresis only.
So my question is if it is possible to provide a channel of the pump item to start and stop it by a rule?