Skip to content
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

All set commands do not work with Viessmann KW protocol #10

Closed
armintan opened this issue Feb 4, 2018 · 8 comments
Closed

All set commands do not work with Viessmann KW protocol #10

armintan opened this issue Feb 4, 2018 · 8 comments

Comments

@armintan
Copy link

armintan commented Feb 4, 2018

All set commands do not send the value to be set in ViessmannKW.java

@Hotte37
Copy link

Hotte37 commented Feb 25, 2018

I have the same issues. I found this commit that claims to solve the write problem but it is not merged into the main branch.
I am waiting for the new release with this fix since a few month.

@steand
Do you see a chance for building a new relase in the near future?

@mikeww1
Copy link

mikeww1 commented Feb 28, 2018

I can confirm that the commit of @Sbried does actually fix the problem. I am using the version with his modifications and there is no USB timeout and I can write in KW mode to my heater.
If you know how to compile the stuff you could use the fork of Sbried to get the changes. Of course it would be great if @steand could update his version.

@Hotte37
Copy link

Hotte37 commented Mar 13, 2018

I tried to build the source with luna and oxigen. I allways have trouble with the maven dependencies. Eclipse was not able to find the external packages even if they are downloaded in a local folder and i can even see the reference to it in the project tree of eclipse:(
I am new with Java and i read a lot of documentation the last two days ... but obviously not enough.
Now i decided to give up.

Was anybody able to build the current version (with the merged pull request #2) and can provide it to @steand to save it as the Release 1.0.1?

@Hotte37
Copy link

Hotte37 commented Mar 13, 2018

I tried to build the jar without maven and this worked.

@lewie
Copy link
Contributor

lewie commented Mar 14, 2018

I hope this helps:

compiled jars: https://github.com/lewie/optolink/tree/master_Sbried_jars
changes: #13

@Hotte37
Copy link

Hotte37 commented Mar 14, 2018

Yes it helped. I commended out the "runtime" scope and now it compiles with maven without any problems.
I now read the documentation of maven dependency scope and now it is clear to me.
But without your help, i never would have found this solution.

@steand
Copy link
Owner

steand commented Mar 18, 2018

I have merged: #13

@sVnsation
Copy link

I tested the compiled jars of @lewie. The changes of @Sbried breaks the 'set function' for protocol 300.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants