-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support wireless m-bus for openHAB 4.0.3 #27
Comments
Hello Jens, I believe binding is available through nexus and it is being built on regular basis. I know you have faced some issues with handling of Techem devices, serial port access, however - would you consider this issue to be solved? |
Not sure what you mean... I didn't found a binding named nexus. I still have 4.0.0.pr-31-SNAPSHOT of wmbus binding installed |
Its there, the #31 was created as a temporary solution to test #29 made for master, but on top of OH 4.0.x APIs. The #29 is merged and included and master; and 4.0.x branch was already rebased several times. Could you please look at version: https://repository.connectorio.cloud/#browse/browse:co7io-public-snapshots:org%2Fconnectorio%2Faddons%2Forg.connectorio.addons.kar.wmbus%2F4.0.0-SNAPSHOT ? Latest version is |
I installed Version org.connectorio.addons.kar.wmbus-4.1.0-20240305.150633-5.kar
So in general from last try to today: Techem don't show decryption error anymore, but still didn't work. Warm Water Heating Kamstrup Techem unencrypted now with error (earlier expected keys, now this looks like solved but not recognized as correct device) Does this test help? |
Thank you Jens, this helps. Message you got comes from invalid configuration generated by discovery phase, your techem devices report themselves (at the protocol level) as |
I am closing this issue as all builds for OH 4.0.x-4.2.x are now being published by CI/CD pipeline. Binaries can be obtained from nexus at https://repository.connectorio.cloud. |
Happy to get feedback if someone else uses 4.0.3 and wmbus :-)
The text was updated successfully, but these errors were encountered: