For me is the date of the next exchange interesting. I think, the calculation is only “last exchange date + defined exchange interval”. In my case every 3 month. After changing the filter I enter the date of the exchange via the webinterface of my Vallox and it shows me the date of the next exchange.
Being able to display the date of the next exchange is interesting for me because since I use your binding, I’ve never used the “official” control display again so I forgot to change my filters
I received a BUILD FAILURE at the end of the “mvn clean install” but I think, it was only because of my quick and dirty maven installation. However it created a .jar-file so I could test your changes and it is working brilliant. Thank you so much for your work!
As far as I can see, it is actually not possible to link the new channels via PaperUI (in my environment). It doesn’t bother me, because I only use item-files.
it seems, that the binding is not working anymore with OH 2.5.0 M3. The binding is installed but not listed in paperUI under installed bindings. The thing is still online but there are no items available. can you please check this and if you can reproduce this error maybe there is a way to fix it.
Hmm, both files (.items & .things) are equal to the files on my 2.4 system. I checked it with the todays snapshot version and there is the same problem. my things-file looks like this:
I am having exactly the same problem as Arne with 2.5.0 (stable release version) after upgrading from 2.4.0 today. Did you find any solution to your problem in 2.5? My Vallox is a 350MV.
The binding hasn’t been touched for quite a while (beside the move to the new build system).
Have to check myself when doing the upgrade over Christmas days.
Thanks for looking into this issue. I compiled some information regarding the addon that I could find. First of all I don’t receive any error message in openhab.log. If I set events to INFO the following messages are found in events.log:
2019-12-17 12:37:23.808 [hingStatusInfoChangedEvent] - 'valloxmv:valloxmv:lueftung' changed from UNINITIALIZED to INITIALIZING
2019-12-17 12:37:23.839 [hingStatusInfoChangedEvent] - 'valloxmv:valloxmv:lueftung' changed from INITIALIZING to UNKNOWN
2019-12-17 12:37:24.876 [hingStatusInfoChangedEvent] - 'valloxmv:valloxmv:lueftung' changed from UNKNOWN to ONLINE
In PaperUI it looks a bit odd because in “Configuration -> Binding” the binding is not listed at all. Under things it is listed without a description:
I have the same problem as Rene with update from 2.4.0 to 2.5.0 my Vallox.
The logs are the same as Rene.
I use Debian 9 with zulu-8.
Thanks if you can help.
FYI, got a message from Vallox support yesterday saying they’ll release v2.0 beginning of next year, to include major improvements on the MyVallox cloud service. That now we’re probably not interested in but I guess it can bring a number of new issues.
Following up, my contact at Vallox has let me know this: We have (finally) decided that the websocket protocol will be public, and the protocol documentation will be released at the beginning of 2020. The problem has been that the protocol is autoregenerated at compile time and therefore too unstable to be supported officially. But now we decided that the current single register commands etc. will be frozen so that they will not change in the future. There are many bindings/implementations for it already and we do not want to break them in every firmware update (and I have already tried to keep the protocol as it is). So, we will make a public protocol description which will be stable in the future updates.
I took a clean docker instance of 2.5 and installed the vallox mv binding, but I was not able to install any vallox mv thing as no line item for it is displayed. Strange.
@bjoernbrings Thank you Björn, that jar is working for my setup (350MV). Just copied it to the addons folder and openHAB is immediately reporting the correct values.
Vallox just informed me that they’ll release v2.0 of their firmware next week.
They say that if your system is registered with and connected to the myVallox cloud it’ll automatically update.
My developer contact said they’re not gonna change modbus variables from now on but I’m not 100% sure what ‘now’ is.
So the binding may or may not continue to work with units when you update to v2.0.
(and if you don’t want that to happen automatically, log out of myVallox cloud)