ok i am ready
how can i get a log for you ?
@Mherwege I am waiting for a new SD to arrive as I want to reinstall my test system. I will try to generate some logs this weekend when I am back home.
Did anyone already upgrade their controller to the new version and validate that the binding still works?I have a v1 controller and I am considering buying a 2nd hand v1 controller just as a backup to be sure I can continue to use OpenHab if mine would break.
@extric99 @Serrrano
I have created a new version of the binding with an attempt to make percentageType with rollershutters work. It is based on some assumptions and expected behaviour from my side, so no guarantees it does work. I would like to ask you to try this out with debug logging enabled and let me know how it behaves. Please try up, down, stop and percentage. You can then send me the debug logs to improve on this.
This binding version will only run with a recent 2.3 snapshot release as it relies on some changes in core functionality that were not available in 2.2.
I will create a pull request to update the distribution binding as soon as it is stable.
You can find the binding here.
@Mherwege I sent the logs in a direct message. Let me know if this was done correctly or I need to retest
@Serrrano The latest beta version of the binding that Mark prepared is now working and allows to enter percentages. It would be great if you could also test it and tell me if you have the same issue I have regarding the inversed values. Openhab reports the blinds as open while they are closed and vice versa. The binding today has no option to inverse so it would be good to understand if is something that should be configurable or the change should be hardcoded in the binding. The issue present itself with the icon on the sitemap. Some info you can find here.
@Serrrano @extric99 I have added an invert flag to the rollershutter thing and inverted the standard behavior. I have also (I hope) improved the behavior of events and commands to rollershutters when the rollershutters are already moving. All of this requires extensive testing, as I cannot do it myself (no rollershutters in my setup).
I have added trace level logging for rollershutters, so if something does not work as expected, turn on trace logging for Niko Home Control and provide me the log with comments on what exactly you have tried.
The current development binding jar can be found here: https://www.dropbox.com/sh/zdic1sw7r0o1tzh/AADVr2x_XTm81DO1YhWvXajva?dl=0
For people wanting to test, best to skip this version as there a bug in it preventing the rollershutter to execute a command.
I can confirm that the open/closed state is now fixed and openhab is reflecting the state of the rollershutter perfectly.
@extric99 @Mherwege
i have installed it but i need to test it little be more .
it seems that all is working i made a command and in paper UI is everything changed alsi in homekit but when i look in NIKO home control blinds are in same position without change.
i am not home right now i will go back afternoon and i send you info whats happened
@serrrano @extric99 I just loaded a new version. Please test with that one. I did correct some errors with the previous version, but the nature of the changes is such that it is very sensitive to the sequence of messages between Niko and openHAB. So I it may still not work. Anyway, a trace log should give me more info again.
as i tested it today. the command is working on homekit and paper UI but nothing happened on NIKO site.
only when i manualy push the button niko after that did the comand i added it via homekit
i am going to load your new version and will test it
Yes.
I can break it when entering multiple times a value when the roller shutter is executing a command
Start position 0
I enter 100
Roller shutter starts
I Enter 60
I enter 70
I enter…
The binding stops reacting for the roller shutter
@Serrrano can you please also test this.
@Mherwege I will send the trace logs in the PM
