Closed gitMiguel closed 3 years ago
Hmm, looks like the Eclipse Marketplace link points to 2.5.4 version. What is the current bindings, that fails, exact version? You can find it when listing bindings in karaf console: bundle:list | grep -i vallox
Hello,
I have the problem with the version 2.5.5:
321 │ Active │ 80 │ 2.5.5.202004290131 │ openHAB Add-ons :: Bundles :: Vallox Binding
Here a more detailed trace log:
2020-07-01 10:08:38.209 [ome.event.ItemCommandEvent] - Item 'FanSpeed2' received command 5
2020-07-01 10:08:38.254 [nt.ItemStatePredictedEvent] - FanSpeed2 predicted to become 5
2020-07-01 10:08:38.328 [vent.ItemStateChangedEvent] - FanSpeed2 changed from 4 to 5
2020-07-01 10:08:38.678 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-25-11-29-1F-7F
2020-07-01 10:08:39.184 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-25-11-29-1F-7F
2020-07-01 10:08:39.687 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-25-11-29-1F-7F
2020-07-01 10:08:40.190 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-25-11-29-1F-7F
2020-07-01 10:08:40.695 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-25-11-29-1F-7F
2020-07-01 10:08:41.197 [DEBUG] [.internal.se.handler.ValloxSEHandler] - Reconnecting after error: Ack byte not received for telegram: 01-25-11-29-1F-7F
2020-07-01 10:08:41.202 [hingStatusInfoChangedEvent] - 'vallox:se-serial:downstairs' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Ack byte not received for telegram: 01-25-11-29-1F-7F
Thanks. And what happens if you repeat the fan speed command after that?
Nothing, I have to restart the binding
I have two systems and unfortunately I cannot see in the traces which messages come from which device .
@gitMiguel: some feedback from me after 2 weeks of using. In my case the new binding (2.5.5 Snapshot) works much better and I'm still happy. Thank you very much.
@flashy02 that's good to hear!
@Sprocket02 are you using ip or serial connection? Do you think this https://github.com/gitMiguel/openhab2-addons/issues/5 are somehow related?
I must correct myself. I have the problem with both versions. Now I have one system configured serially and the other via TCP. With the second system, however, this message always comes up when the adjustment is made. I'm pretty sure it worked before.
Ok. Let me see if I can build you a test version that show device name or number when logging.
Sorry for not responding for such a long time. My new job has taken all my spare time. What versions are you running now?
@gitMiguel: Are you still on developing the Vallox SE Binding? Now OH3 came out and the "old" binding doesn't work anymore. Is there any hope to get it work in the near future for OH3?
I am also very interested.
Hi @flashy02 and @Sprocket02,
I've migrated the code to 3.0. Code is uploaded to main branch along with downloadable and runnable jar file:
Hi, @Sprocket02 and @majherek
I made a fresh build of the binding. Find it here. Remember to change .zip to .jar.
Few things to mention.
Thanks for testing!