The driver knx_windowcoverings is causing problems in my case.

In drivers/knx_windowcoverings/device.js lines 49-51 and 64-66 a stop/step-command is issued before the up/down command. With my windowcovers this leads to timing-problems and the coverings often do not react to the up/down command.

I did not issue a pull request as I am not sure what the initial reason for this implementation was. I see two possible solutions:

1. (preferred) just delete the stop/step commands in lines 49-51 and 64-66
2. insert some short delay between the stop/step and up/down

Hello,

I’m using homey since three years with my knx devices, since that time I’m missing a window/door sensor (open/close) I asked they people from homey several times - no Reaktion - no they wrote - ask the Comunity. Here I am - can someone help my. I want to se if there is a window open ore closed - I have contacts in every window - I have them in my Knx system but not in may homey - help !

kind regards Steffen

Right now the app uses its own simple datapoint parsing in: https://github.com/athombv/org.knx/blob/master/lib/DatapointTypeParser.js

However the knx lib actually have a very robust and detailed parsing library that is also extendable, I have used those methods for the receive telegram flow: https://github.com/athombv/org.knx/pull/21/files#diff-e07d531ac040ce3f40e0ce632ac2a059d7cd60f20e61f78268ac3be015b3b28fR58-R59

A first step would be to simply make DatapointTypeParser use that implementation instead of its own implementation, so we leverage any bug fixes in the upstream library.

What do you think?

Hi, i am new with Homey. Maybe advanced user, but not a developer. I only wanted kindly ask, if someone is working on integration of KNX Motion Sensors for Homey

I use Merten Argus

Kind Regards,
René

For each of the devices the full set of html files for pairing is included in the driver folders.

Additionally the zip-fs.js (and zip-fs.min.js) is included in every driver folder.

Both of these seems excessive, but I am unsure whether there is a technical limitation that is the cause of this. So before starting a project to clean it up, maybe we can either kill the cleanup idea or make a game plan?