The upcoming version 2.0.0 of js-controller will support a new mode for low memory devices. For this, a few minor adjustments to the adapter must be made. Please follow these instructions: https://forum.iobroker.net/viewtopic.php?f=24&t=20387#p213466

New Firmware out 0.2.0.0.71.0 as released here: https://updates2.velux.com/
ioBroker Forum reports that this is not working with this adapter: https://forum.iobroker.net/viewtopic.php?f=24&t=15919&p=182768#p182768

Please add support for this Firmware.

ALL USERS: PLEASE DO NOT UPGRADE TO NEW FW VERSION!

Achtung: Dies ist eine andere Fehlermeldung als die Fehlermeldung ISSUE #69: “KLF 200: Current Position – Wert im Trigger falsch“

1. Ich öffne das Fenster mit der VELUX-Bedienung auf 29 Prozent.
   ++++++++++++++++ Screenshot: VELUX Bedienung auf 29.jpg++++++++++++++++++
   

2. Wenn das den Öffnungszustand 29% erreicht ist in den Objekten die currentPosition wie erwartet 29
   ++++++++++++++++ Screenshot: Objektwert currentPosition ist 29.jpg ++++++++++++++++++
   

3. Wenn der Wert 29% erreicht ist, triggert der Trigger STATUSÄNDERUNG
   Der Trigger ist in Blockly geschrieben:
   +++++++++ Screenshot: Blockly Script.jpg+++++++++
   

Wenn im Trigger der Status den Wert 5 hat (d.h. DONE) lese ich nun im Trigger die CurrentPosition ein.
Fehler: Es wird 0 eingelesen und nicht 29 (Teil 1 betrachten !)
+++++++++ Screenshot: Logbuch für 29 und 82 +++++++++

4. Jetzt startet der zweite Teil

5. Ich öffne das Fenster mit der VELUX-Bedienung nun auf 82 Prozent.
   ++++++++++++++++ Screenshot: VELUX Bedienung auf 82.jpg++++++++++++++++++
   

6. Wenn das den Öffnungszustand 82% erreicht ist in den Objekten die currentPosition wie erwartet 82
   ++++++++++++++++ Screenshot: Objektwert currentPosition ist 82.jpg ++++++++++++++++++

7. Wenn der Wert 82% erreicht ist, triggert der Trigger STATUSÄNDERUNG
   Wenn im Trigger der Status den Wert 5 hat (d.h. DONE) lese ich nun im Trigger die CurrentPosition ein.
   ++++++++ Screenshot: Logbuch für 29 und 82 +++++++++
   

Fehler: Es wird 29 eingelesen und nicht 82. 29 ist der Wert von vorher !!! (Teil 2 betrachten !)

Describe the bug
When changing "targtPosition" of any product via e.g. API ("http://:8087/set/klf200.0.products.3.targetPosition?value=100&prettyPrint") everything works as intended. When trying the same via the adapter "mqtt-client" the value of the object is changed in the iobroker GUI ("tagetPosition" is updated to the new value) but the command is not executed, i.e. the position of the roller/shader will not start to change.

To Reproduce
Steps to reproduce the behavior:

1. Setup MQTT broker if not available yet (e.g. via adapter "mqtt" localhost)
2. Add adapter mqtt-client if necessary
3. Change settings of object "targetPosition" to both publish and subscribe to an appropriate MQTT topic, e.g. "klf200/0/products/0/targetPosition"
4. Publish a random value on topic "klf200/0/products/0/targetPosition"
5. The value is updated but no movement executed

Expected behavior
One would expect the shader/roller to start moving with any change in "targetPosition" no matter the source of change.

Screenshots & Logfiles
Screenshot 1: Everything normal, currentPosition = targetPosition as intended

Screenshot 2: After updating targetPosition to a random value via MQTT publish, the currentPosition will not change, as there is no movement happening

Versions:

• Adapter version: 1.0.1
• JS-Controller version: 3.2.16
• Node version: 12.22.1
• Operating system: Raspberry Pi OS Lite 5.10

Dear Adapter develop,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

Describe the bug
In the current documentation it is stated that for connecting/configuring the klf200 adapter to connect to the KLF200 system the web logon password should be used (see https://github.com/MiSchroe/ioBroker.klf200/blame/master/docs/de/ReadMe.md#L71-L73). It, however, took me quite a while to identify that rather than using the "Web logon" (standard 'velux123' or a self defined webui password) the WIFI Password stated on the back of the KLF200 box is the one that has to be used.

While I don't know if this might be only the case for the latest firmware (I am using 0.2.0.0.71.0) and in previous versions also the web logon password worked, it is nevertheless the case for my klf200 gateway that I have to use the hard encoded WiFi Password printed on the back side of the KLF200 gateway rather than the web logon password.

Hi,

thank you very much for adding support for the new Firmware/API.

Till now I did use fhem (and fhem connector in ioBroker) to control my KLF device. I switched now to your adapter. I control a velux roof window with it that is also equipped with a rain sensor. fhem did show me a value for "limitationMax" in the states. With no rain this was set to 100 and with rain it was reduced to something like 5. In this way I could detect rain.
Is it possible to receive this value in the adapter, too?

Not sure if that makes sense at all.

Garfonso

The test should read all states dynamically and check if there are handlers associated with that state.
Otherwise we would create states without any meaning.

The REST API of the interface allows us to start the training mode of the scenarios. Maybe it's possible to start the training mode repeatedly with a fixed scenario to check the current value of the product.

Hi,

the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.

You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.

Please update your systems to js-controller 2.0 and check your adapter.

Please close this issue once you have checked your adapter or received successfull reports from users.

Thank you very much for your support. Please contact us in the other Threads or Forum on any question.

The silent mode of a scene should be changeable. This would make it possible to run a product (e.g. open a window) in silent mode during the night and in normal mode during the day.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

States can show wrong lengths due to wrong calculation. Instead of array length the array should be reduced to count the non-null and non-undefined members, only

Think about update stable version to 1.0.0

Version: stable=0.9.5 (695 days old) => latest=1.0.0 (15 days old)
Installs: stable=103 (72.54%), latest=39 (27.46%), total=142
Click to edit

Describe the bug
The adapter crashes 10 seconds after e.g. open a window from 0% to 40% (window will still move to the desired position).

To Reproduce
Steps to reproduce the behavior:

1. Set targetPosition of any state to e.g. 40%
2. Watch the log
3. unhandled promise rejection: Timeout, Error at new module.exports.TimeoutError (/opt/iobroker/node_modules/promise-timeout/index.js:44:16) at Object.module.exports.timeout (/opt/iobroker/node_modules/promise-timeout/index.js

Expected behavior
The adapter shouldn't crash.

Versions:

• Adapter version: v1.0.0-beta
• JS-Controller version: 3.1.4
• Node version: 12.18.1
• Operating system: Linux

Additional context
The error doesn't happen on node v10 with js-controller 2.x

The user should specify a duration in minutes which describes how often the adapter looks for configuration changes at the interface.

FP1-4 should be settable to support additional functionality, e.g. set Dual Roller Shutters.

The README.MD has to be rewritten to reflect the new and updated states. The whole setup procedure with the scenes is not necessary anymore and should be deleted.

I need help with translating the documentation. The following translations are finished:

• Dutch
• French
• German
• Italian
• Polish
• Portuguese
• Russian
• Spanish

Please translate at GitLocalize and submit a Pull Request at GitLocalize when finished.

It would be nice to see the remaining time decrease and the currentPosition state change over time.

Describe the bug
The adapter crashed two nights in a row and did not restart properly.
When opening the windows in the morrning with yahta, windows do not react but show busy.

To Reproduce
Steps to reproduce the behavior:

1. Run adapter
2. No further user interaction - adapter just crashes.

Expected behavior
Adapter should not crash.

Screenshots & Logfiles

>>> See events at 3 AM. I restarted KLF200 and yahta adapter in the morning.

2021-06-13 03:00:00.022 - info: klf200.0 (578) Automatic reboot due to schedule in configuration

2021-06-13 03:00:00.052 - info: klf200.0 (578) Rebooting the adapter, connection will be lost.
2021-06-13 03:00:00.245 - info: klf200.0 (578) Waiting 2 seconds after reboot for restart.
2021-06-13 03:00:02.246 - info: klf200.0 (578) Adapter will be restartet.
2021-06-13 03:00:02.247 - warn: klf200.0 (578) Restart initiated
2021-06-13 03:00:02.247 - info: klf200.0 (578) Remove socket listener...
2021-06-13 03:00:02.247 - info: klf200.0 (578) Shutting down event handlers...
2021-06-13 03:00:02.255 - info: klf200.0 (578) Disconnecting from the KLF-200...
2021-06-13 03:00:02.267 - info: klf200.0 (578) Cleaned everything up...
2021-06-13 03:00:02.268 - info: klf200.0 (578) terminating
2021-06-13 03:00:02.269 - info: klf200.0 (578) Terminated (NO_ERROR): Without reason
2021-06-13 03:00:03.007 - info: host.buanet-iobroker1 instance system.adapter.klf200.0 terminated with code 0 (NO_ERROR)
2021-06-13 03:00:03.014 - info: host.buanet-iobroker1 Restart adapter system.adapter.klf200.0 because enabled
2021-06-13 03:00:33.124 - info: host.buanet-iobroker1 instance system.adapter.klf200.0 started with pid 19479
2021-06-13 03:00:37.598 - info: klf200.0 (19479) starting. Version 1.0.1 in /opt/iobroker/node_modules/iobroker.klf200, node: v12.22.1, js-controller: 3.2.16
2021-06-13 03:00:37.685 - info: klf200.0 (19479) Host: 192.168.178.6
2021-06-13 03:00:40.698 - info: klf200.0 (19479) Terminated (ADAPTER_REQUESTED_TERMINATION): Login to KLF-200 device at 192.168.178.6 failed.
2021-06-13 03:00:41.206 - info: klf200.0 (19479) Remove socket listener...
2021-06-13 03:00:41.230 - error: host.buanet-iobroker1 instance system.adapter.klf200.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
2021-06-13 03:00:41.231 - info: host.buanet-iobroker1 Do not restart adapter system.adapter.klf200.0 because desired by instance
2021-06-13 07:01:51.126 - info: admin.0 (123) Request actual repository...
2021-06-13 07:01:52.444 - info: host.buanet-iobroker1 Updating repository "default" under "http://download.iobroker.net/sources-dist.json"
2021-06-13 07:01:53.449 - info: admin.0 (123) Repository received successfully.
2021-06-13 08:29:31.574 - info: host.buanet-iobroker1 Updating repository "default" under "http://download.iobroker.net/sources-dist.json"
2021-06-13 08:30:07.068 - info: host.buanet-iobroker1 instance system.adapter.klf200.0 started with pid 5845
2021-06-13 08:30:08.926 - info: klf200.0 (5845) starting. Version 1.0.1 in /opt/iobroker/node_modules/iobroker.klf200, node: v12.22.1, js-controller: 3.2.16
2021-06-13 08:30:08.955 - info: klf200.0 (5845) Host: 192.168.178.6
2021-06-13 08:30:13.627 - info: klf200.0 (5845) Connected to interface.
2021-06-13 08:30:13.627 - info: klf200.0 (5845) Reading device information...
2021-06-13 08:30:13.628 - info: klf200.0 (5845) Enabling the house status monitor...
2021-06-13 08:30:13.853 - info: klf200.0 (5845) Setting UTC clock to the current time.
2021-06-13 08:30:14.064 - info: klf200.0 (5845) Setting time zone to :GMT+1:GMT+2:0060:(1994)040102-0:110102-0
2021-06-13 08:30:17.364 - info: klf200.0 (5845) Reading scenes...
2021-06-13 08:30:17.575 - info: klf200.0 (5845) 0 scenes found.
2021-06-13 08:30:17.576 - info: klf200.0 (5845) Reading groups...
2021-06-13 08:30:19.141 - info: klf200.0 (5845) 0 groups found.
2021-06-13 08:30:19.141 - info: klf200.0 (5845) Reading products...
2021-06-13 08:30:41.264 - info: klf200.0 (5845) 21 products found.
2021-06-13 08:30:41.718 - info: klf200.0 (5845) Setup objects for product X Links WB.
2021-06-13 08:30:41.763 - info: klf200.0 (5845) Setup objects for product X Rechts WB.
2021-06-13 08:30:41.803 - info: klf200.0 (5845) Setup objects for product X Links RL WB.
2021-06-13 08:30:41.846 - info: klf200.0 (5845) Setup objects for product X Rechts RL WB.
2021-06-13 08:30:41.887 - info: klf200.0 (5845) Setup objects for product X Oben RL WB.
2021-06-13 08:30:41.931 - info: klf200.0 (5845) Setup objects for product DF-RL Schlafzimmer Rechts.
2021-06-13 08:30:41.971 - info: klf200.0 (5845) Setup objects for product DF-RL Kinderbad.
2021-06-13 08:30:42.009 - info: klf200.0 (5845) Setup objects for product DF Schlafzimmer Links.
2021-06-13 08:30:42.047 - info: klf200.0 (5845) Setup objects for product DF Kind 2 Links.
2021-06-13 08:30:42.082 - info: klf200.0 (5845) Setup objects for product DF-RL Ankleide.
2021-06-13 08:30:42.128 - info: klf200.0 (5845) Setup objects for product DF-RL Kind 2 Rechts.
2021-06-13 08:30:42.162 - info: klf200.0 (5845) Setup objects for product DF Kind 2 Rechts.
2021-06-13 08:30:42.196 - info: klf200.0 (5845) Setup objects for product DF-RL Schlafzimmer Links.
2021-06-13 08:30:42.235 - info: klf200.0 (5845) Setup objects for product DF Kinderbad.
2021-06-13 08:30:42.267 - info: klf200.0 (5845) Setup objects for product DF-RL Kind 2 Links.
2021-06-13 08:30:42.309 - info: klf200.0 (5845) Setup objects for product DF Ankleide.
2021-06-13 08:30:42.344 - info: klf200.0 (5845) Setup objects for product DF-RL Galerie Rechts.
2021-06-13 08:30:42.376 - info: klf200.0 (5845) Setup objects for product DF Schlafzimmer Rechts.
2021-06-13 08:30:42.413 - info: klf200.0 (5845) Setup objects for product DF-RL Galerie Links.
2021-06-13 08:30:42.445 - info: klf200.0 (5845) Setup objects for product DF Galerie Rechts.
2021-06-13 08:30:42.481 - info: klf200.0 (5845) Setup objects for product DF Galerie Links.
2021-06-13 08:30:42.514 - info: klf200.0 (5845) Setting up notification handlers for removal...
2021-06-13 08:30:42.514 - info: klf200.0 (5845) Setting up notification handlers for discovering new objects...
2021-06-13 08:30:42.514 - info: klf200.0 (5845) Setting up notification handler for gateway state...
2021-06-13 08:30:42.515 - info: klf200.0 (5845) Adapter is ready for use.
2021-06-13 08:30:42.515 - info: klf200.0 (5845) Starting background state refresher...
2021-06-13 08:30:42.515 - info: klf200.0 (5845) Automatic reboot enabled in configuration. Planning reboot job.
2021-06-13 08:30:47.716 - info: host.buanet-iobroker1 stopInstance system.adapter.yahka.0 (force=false, process=true)
2021-06-13 08:30:47.719 - info: yahka.0 (561) Got terminate signal TERMINATE_YOURSELF
2021-06-13 08:30:47.727 - info: yahka.0 (561) cleaning up ...
2021-06-13 08:30:47.727 - info: yahka.0 (561) cleaned up ...
2021-06-13 08:30:47.727 - info: yahka.0 (561) terminating
2021-06-13 08:30:47.728 - info: yahka.0 (561) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2021-06-13 08:30:47.759 - info: host.buanet-iobroker1 stopInstance system.adapter.yahka.0 send kill signal
2021-06-13 08:30:48.275 - info: host.buanet-iobroker1 instance system.adapter.yahka.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-06-13 08:30:50.801 - info: host.buanet-iobroker1 instance system.adapter.yahka.0 started with pid 5900
2021-06-13 08:30:52.320 - info: yahka.0 (5900) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.yahka, node: v12.22.1, js-controller: 3.2.16
2021-06-13 08:30:52.334 - info: yahka.0 (5900) adapter ready, checking config
2021-06-13 08:30:52.341 - info: yahka.0 (5900) adding DF Galerie Links with UUID: 2c848831-601b-4ac4-ac7f-717e805a4c88
2021-06-13 08:30:52.347 - info: yahka.0 (5900) adding DF Galerie Rechts with UUID: 938e09cd-3f0a-405d-a16a-1a08c9e8f128
2021-06-13 08:30:52.350 - info: yahka.0 (5900) adding DF-RL Galerie Links with UUID: 39562e93-afa3-49f2-a175-8125706b27c0
2021-06-13 08:30:52.352 - error: yahka.0 (5900) [DF-RL Links] unable to establish link between DF Links and DF-RL Links - one of the services was not found or is disabled
2021-06-13 08:30:52.352 - info: yahka.0 (5900) adding DF-RL Galerie Rechts with UUID: 911f4a6c-bae9-40e7-87b5-da8ff97b1fa1
2021-06-13 08:30:52.354 - error: yahka.0 (5900) [DF-RL Rechts] unable to establish link between DF Links and DF-RL Rechts - one of the services was not found or is disabled
2021-06-13 08:30:52.354 - info: yahka.0 (5900) adding DF Kind 2 Links with UUID: f71a3794-8e10-4c31-83f8-94050540530d
2021-06-13 08:30:52.356 - info: yahka.0 (5900) adding DF Kind 2 Rechts with UUID: e15a4888-197c-4e66-8e2e-09daa9c87cdb
2021-06-13 08:30:52.358 - info: yahka.0 (5900) adding DF-RL Kind 2 Links with UUID: 180a8cf3-4495-4b9b-9f11-f1a4a602ac40
2021-06-13 08:30:52.360 - error: yahka.0 (5900) [DF-RL Links] unable to establish link between DF Links and DF-RL Links - one of the services was not found or is disabled
2021-06-13 08:30:52.360 - info: yahka.0 (5900) adding DF-RL Kind 2 Rechts with UUID: 32dcfe09-99ed-4bb6-ae4c-c03e20ac10bd
2021-06-13 08:30:52.362 - error: yahka.0 (5900) [DF-RL Links] unable to establish link between DF Links and DF-RL Links - one of the services was not found or is disabled
2021-06-13 08:30:52.362 - info: yahka.0 (5900) adding DF Schlafzimmer Links with UUID: d0d88cd8-e58f-4610-831b-f117c1498e20
2021-06-13 08:30:52.364 - info: yahka.0 (5900) adding DF Schlafzimmer Rechts with UUID: 91fc7e0c-d374-44bf-93ae-757e1f096fcc
2021-06-13 08:30:52.366 - error: yahka.0 (5900) [DF Rechts] unable to establish link between DF Links and DF Rechts - one of the services was not found or is disabled
2021-06-13 08:30:52.366 - info: yahka.0 (5900) adding DF-RL Schlafzimmer Links with UUID: 6553ebe6-b016-48df-9d8a-bc76887804d1
2021-06-13 08:30:52.367 - error: yahka.0 (5900) [DF-RL Links] unable to establish link between DF Links and DF-RL Links - one of the services was not found or is disabled
2021-06-13 08:30:52.368 - info: yahka.0 (5900) adding DF-RL Schlafzimmer Rechts with UUID: dd977351-a125-4bb5-973a-7f0f9ca37b93
2021-06-13 08:30:52.369 - error: yahka.0 (5900) [DF-RL Rechts] unable to establish link between DF Links and DF-RL Rechts - one of the services was not found or is disabled
2021-06-13 08:30:52.369 - info: yahka.0 (5900) adding DF Ankleide with UUID: dcf008b8-23ca-4f3b-a411-f72fc4854d03
2021-06-13 08:30:52.371 - error: yahka.0 (5900) [DF Ankleide] unable to establish link between DF Links and DF Ankleide - one of the services was not found or is disabled
2021-06-13 08:30:52.372 - info: yahka.0 (5900) adding DF-RL Ankleide with UUID: f5def9e1-05c7-45c4-8e23-f5d54201364b
2021-06-13 08:30:52.373 - error: yahka.0 (5900) [DF-RL Ankleide] unable to establish link between DF Links and DF-RL Ankleide - one of the services was not found or is disabled
2021-06-13 08:30:52.374 - info: yahka.0 (5900) adding DF Kinderbad with UUID: 29bff174-111f-436c-ab74-81a40b3214e5
2021-06-13 08:30:52.375 - error: yahka.0 (5900) [DF Kinderbad] unable to establish link between DF Links and DF Kinderbad - one of the services was not found or is disabled
2021-06-13 08:30:52.375 - info: yahka.0 (5900) adding DF-RL Kinderbad with UUID: f924791c-3759-4a56-9a73-9e14827b586d
2021-06-13 08:30:52.377 - error: yahka.0 (5900) [DF-RL Kinderbad] unable to establish link between DF Links and DF-RL Kinderbad - one of the services was not found or is disabled
2021-06-13 08:30:52.377 - info: yahka.0 (5900) publishing bridge Yahka-0 on 0.0.0.0

Versions:

• Adapter version: 1.0.1
• JS-Controller version: 3.2.16
• Node version: v12.22.1
• Operating system: Synology DSM720+: DSM 6.2.4-25556

Additional context
Add any other context about the problem here.

Update LOG 14.06.2021 - This night adapter did not crash but produces error messages. Is there a automatic reboot at 3:00 AM in the morning in the KLF200 adapter?

2021-06-14 03:00:00.021 - info: klf200.0 (5845) Automatic reboot due to schedule in configuration

2021-06-14 03:00:00.130 - info: klf200.0 (5845) Rebooting the adapter, connection will be lost.
2021-06-14 03:00:00.440 - info: klf200.0 (5845) Waiting 2 seconds after reboot for restart.
2021-06-14 03:00:02.443 - info: klf200.0 (5845) Adapter will be restartet.
2021-06-14 03:00:02.443 - warn: klf200.0 (5845) Restart initiated
2021-06-14 03:00:02.444 - info: klf200.0 (5845) Remove socket listener...
2021-06-14 03:00:02.444 - info: klf200.0 (5845) Shutting down event handlers...
2021-06-14 03:00:02.452 - info: klf200.0 (5845) Disconnecting from the KLF-200...
2021-06-14 03:00:02.462 - info: klf200.0 (5845) Cleaned everything up...
2021-06-14 03:00:02.464 - info: klf200.0 (5845) terminating
2021-06-14 03:00:02.464 - info: klf200.0 (5845) Terminated (NO_ERROR): Without reason
2021-06-14 03:00:03.214 - info: host.buanet-iobroker1 instance system.adapter.klf200.0 terminated with code 0 (NO_ERROR)
2021-06-14 03:00:03.222 - info: host.buanet-iobroker1 Restart adapter system.adapter.klf200.0 because enabled
2021-06-14 03:00:33.369 - info: host.buanet-iobroker1 instance system.adapter.klf200.0 started with pid 31559
2021-06-14 03:00:37.495 - info: klf200.0 (31559) starting. Version 1.0.1 in /opt/iobroker/node_modules/iobroker.klf200, node: v12.22.1, js-controller: 3.2.16
2021-06-14 03:00:37.556 - info: klf200.0 (31559) Host: 192.168.178.6
2021-06-14 03:00:52.278 - info: klf200.0 (31559) Connected to interface.
2021-06-14 03:00:52.279 - info: klf200.0 (31559) Reading device information...
2021-06-14 03:00:52.279 - info: klf200.0 (31559) Enabling the house status monitor...
2021-06-14 03:00:54.011 - info: klf200.0 (31559) Setting UTC clock to the current time.
2021-06-14 03:00:54.221 - info: klf200.0 (31559) Setting time zone to :GMT+1:GMT+2:0060:(1994)040102-0:110102-0
2021-06-14 03:00:56.977 - info: klf200.0 (31559) Reading scenes...
2021-06-14 03:00:57.187 - info: klf200.0 (31559) 0 scenes found.
2021-06-14 03:00:57.187 - info: klf200.0 (31559) Reading groups...
2021-06-14 03:00:57.409 - info: klf200.0 (31559) 0 groups found.
2021-06-14 03:00:57.410 - info: klf200.0 (31559) Reading products...
2021-06-14 03:01:16.551 - info: klf200.0 (31559) 21 products found.
2021-06-14 03:01:17.003 - info: klf200.0 (31559) Setup objects for product X Links WB.
2021-06-14 03:01:17.051 - info: klf200.0 (31559) Setup objects for product X Rechts WB.
2021-06-14 03:01:17.094 - info: klf200.0 (31559) Setup objects for product X Links RL WB.
2021-06-14 03:01:17.133 - info: klf200.0 (31559) Setup objects for product X Rechts RL WB.
2021-06-14 03:01:17.175 - info: klf200.0 (31559) Setup objects for product X Oben RL WB.
2021-06-14 03:01:17.223 - info: klf200.0 (31559) Setup objects for product DF-RL Schlafzimmer Rechts.
2021-06-14 03:01:17.271 - info: klf200.0 (31559) Setup objects for product DF-RL Kinderbad.
2021-06-14 03:01:17.308 - info: klf200.0 (31559) Setup objects for product DF Schlafzimmer Links.
2021-06-14 03:01:17.347 - info: klf200.0 (31559) Setup objects for product DF Kind 2 Links.
2021-06-14 03:01:17.385 - info: klf200.0 (31559) Setup objects for product DF-RL Ankleide.
2021-06-14 03:01:17.427 - info: klf200.0 (31559) Setup objects for product DF-RL Kind 2 Rechts.
2021-06-14 03:01:17.462 - info: klf200.0 (31559) Setup objects for product DF Kind 2 Rechts.
2021-06-14 03:01:17.497 - info: klf200.0 (31559) Setup objects for product DF-RL Schlafzimmer Links.
2021-06-14 03:01:17.533 - info: klf200.0 (31559) Setup objects for product DF Kinderbad.
2021-06-14 03:01:17.568 - info: klf200.0 (31559) Setup objects for product DF-RL Kind 2 Links.
2021-06-14 03:01:17.607 - info: klf200.0 (31559) Setup objects for product DF Ankleide.
2021-06-14 03:01:17.641 - info: klf200.0 (31559) Setup objects for product DF-RL Galerie Rechts.
2021-06-14 03:01:17.680 - info: klf200.0 (31559) Setup objects for product DF Schlafzimmer Rechts.
2021-06-14 03:01:17.709 - info: klf200.0 (31559) Setup objects for product DF-RL Galerie Links.
2021-06-14 03:01:17.745 - info: klf200.0 (31559) Setup objects for product DF Galerie Rechts.
2021-06-14 03:01:17.781 - info: klf200.0 (31559) Setup objects for product DF Galerie Links.
2021-06-14 03:01:17.820 - info: klf200.0 (31559) Setting up notification handlers for removal...
2021-06-14 03:01:17.820 - info: klf200.0 (31559) Setting up notification handlers for discovering new objects...
2021-06-14 03:01:17.820 - info: klf200.0 (31559) Setting up notification handler for gateway state...
2021-06-14 03:01:17.820 - info: klf200.0 (31559) Adapter is ready for use.
2021-06-14 03:01:17.821 - info: klf200.0 (31559) Starting background state refresher...
2021-06-14 03:01:17.821 - info: klf200.0 (31559) Automatic reboot enabled in configuration. Planning reboot job.
2021-06-14 05:39:24.238 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 05:44:34.240 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 05:49:44.242 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 05:54:02.528 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 05:54:16.762 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 05:54:56.107 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:00:03.518 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:05:13.521 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:09:16.795 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:09:46.764 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:10:33.206 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:10:46.774 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:15:49.965 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:20:59.968 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:24:46.779 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:25:16.737 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:25:46.781 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:26:16.764 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:31:21.027 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:36:31.029 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:40:16.760 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:40:46.746 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:41:16.775 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:41:46.769 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:46:51.044 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:49:33.996 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:49:46.766 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:49:57.426 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 06:54:59.543 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:00:09.546 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:04:46.805 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:05:16.776 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:05:27.512 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:10:30.689 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:15:40.693 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:20:16.778 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:20:46.765 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:20:57.457 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:26:00.658 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:30:32.990 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:30:46.767 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:30:57.478 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:35:58.569 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:41:08.570 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:45:46.812 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:46:16.776 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:46:27.453 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:51:29.547 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.
2021-06-14 07:53:23.995 - error: klf200.0 (31559) Timemout occured during getting the current gateway status.

Hey Michael,
is it possible that you implement a datapoint like the "stop" action for "open" and "close"?
So that when you send true to the datapoint "open" the blind will get the 100% and open?

Thank you and best regards! :)
DcFamas

Round to integer value. We don't need fractions of percent. If someone does, use the targetPositionRaw.

Describe the bug
I have created a small blockly script which reacts to a system variable and sets all shutters to 0 or 100 (targetposition).
All seems to run well but when the script is triggered, the adapter crashes. All states are changed and the shutters actually move into position, but the adapter is restarted and throws a lot of errors.

To Reproduce
Steps to reproduce the behavior:

1. Import Blockly script
2. Start script
3. Trigger script
4. See error

Expected behavior
Script should not terminate.

Screenshots & Logfiles
blockly_export.txt
iobroker.log

Versions:

• Adapter version: 1.0.0

• JS-Controller version: 3.1.6

• Node version: 10.16.3

• Operating system: Ubuntu 16.04.6 LTS

Fehler 1:
Aus mir nicht bekannten Gründen hat der KLF200-Adapter in der Nacht einen Restart gemacht.
+++++++++++++++++ Screenshot: Restart Adapter +++++++++++++++++++++++

Fehler 2:
Während dieses Restart-Prozesses wird der Trigger mit geänderten Status fehlerhafterweise gefeuert.
Hier das entsprechende Script:
+++++++++++++++++ Screenshot: Blockly Script +++++++++++++++++++++++

Der Wert des Satus im Trigger ist fehlerhafterweise 255
+++++++++++++++++ Screenshot: Log Teil 1.mit Kommentar jpg +++++++++++++++++++++++

Danach wird scheinbar der richtige Wert (5 = DONE) in den Status geschrieben (Wer das macht weiß ich nicht) und wieder der Trigger gefeuert.
Im Trigger lese ich die currentPosition aus und diese ist falsch.
Es wird NULL ausgelesen !
+++++++++++++++++ Screenshot: Log Teil 2.mit Kommentar jpg +++++++++++++++++++++++

Is your feature request related to a problem? Please describe.
Hello

I don't have the KLF-200 yet thus I'm asking the question sorry.

In the documentation it states ' 2. Your window will start to move to 40% opening level. (If it's not blocked, e.g. by the rain sensor.)'

Does the window provide feedback of position or is it just told to go to that position. So I would be able to add logic if the window failed to moved due to rain?

Describe the solution you'd like
As above

Describe alternatives you've considered
As above

Additional context
Thanks in advance. Great work on this connector! :)

New scenes should be recognized without a restart of the adapter.

What I noticed is when I have one scene for one shutter the adapter is working. I don't need the scenes because of your object

klf200.0.products.0.targetPosition

So I deleted the scene in the klf200 and restarted the adapter. The adapter keeps yellow and I can't use the "targetPosition" object anymore. When I recreate a new program/scene in the klf (for example shutter.open) I can use the object again and the adapter gets green. It seems like you need at least one scene to get the adapter working?

`

`

Originally posted by @DcFamas in #15 (comment)

The password for the login to the KLF-200 should be stored encrypted.

Describe the bug
Too many event subscriptions for stateChange.

To Reproduce
Steps to reproduce the behavior:

1. Have a good amount of products and scenes
2. Start the adapter
3. Warning is displayed on the console

Expected behavior
The adapter should subscribe to the events on state base with a wildcard for products, groups and scenes.

Additional context
The current implementation creates a subscription for each writable state of each product, group, etc.
Instead a single subscription for each writable state for each type (products, groups, etc.) should be created based on wildcards. That subscription should pass the event to the relevant event handler.
We'll have to implement some kind of central registry for the subscription objects.

• Please remove restartAdapters "vis" unless a widget is included
• remove directories widget, www
• remove docs directory or better add docs
• update lib/utils and testing files to latest versions from adapter template

Afterthis and after adding Admin3 support please make forum thread to get more testers and request for repository addition :-)

Thank you

See https://forum.iobroker.net/viewtopic.php?f=24&t=10268 for additional information.

Ich habe einen Trigger für die Current Poition.
+++++++++ Screenshot: Objekt_Current Position.jpg+++++++++

Der Trigger ist in Blockly geschrieben:
+++++++++ Screenshot: Trigger Current Position.jpg+++++++++

Das Verhalten ist OK, wenn ich ein Fenster aufmache und warte bis es offen ist. Wie man im Screenshot erkennt, sendet der KLF200, wenn das Fenster vollständig geöffnet ist im Trigger der richtigen Wert Current Position = 100
+++++++++ Screenshot Fenster Aufmachen -- mit Kommentar.jpg+++++++++

Hier der Fehlerfall:
Das Fenster wird wie im obigen Fall geöffnet, aber während des Öffnungsvorgangs wird es wieder geschlossen. Es ist hier im Trigger für die Current Position kein richtiger Wert!
(Verdacht: Es schaut so aus als wäre es ein Nullpointer)
+++++++++ Screenshot Zumachen während Aufmachen läuft -- mit Kommenar.jpg+++++++++

Describe the bug
The Adapter stops working every 2-3 days.
Restart of adapter doesn't help. The KLF200 Gateway has to be powered off and on.
Cron pattern in the adapter is set. Also a reload of the adapter every day is set via cron job

To Reproduce
Steps to reproduce the behavior:
Happens ever 2-3 days after restart of KLF200

Expected behavior
The adapter should stay online in a working state

Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.

Versions:

• Adapter version: 1.0.1
• JS-Controller version: 3.2.16
• Node version: v12.21.0
• Operating system: linux

Additional context
KLF200 is on firmware 0.2.0.0.71.0

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/MiSchroe/ioBroker.klf200

• [E140] width and height of logo are not equal
• [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.klf200"
• [E802] No topics found in the repository. Please go to "https://github.com/MiSchroe/ioBroker.klf200" and press "Manage topics"
• [E605] No actual year found in copyright. Please add "Copyright (c) 2020 Michael Schroeder [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2020 Michael Schroeder [email protected]" at the start of LICENSE

I have also found warnings that may be fixed if possible.

• [W113] Adapter should support compact mode

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

The communication to the KLF-200 is secured by TLS. Currently, the device uses a self signed certificate, but this one could change.

The solution should provide a way to upload valid certificate details and the fingerprint.

Describe the bug
The adapter crashes after installation.
The log shows TypeError: _b.off is not a function

To Reproduce
After installed to iobroker and configured IP and Password.

Expected behavior
It should not crash.

Screenshots & Logfiles

Versions:

• Adapter version: 1.0.1
• JS-Controller version: 2.1.1
• Node version: v 8.15.0
• Operating system: Docker on Synology

Additional context

Remove devices from the list of scenes, groups or products, if they don't exist anymore.

• Check at startup of the adapter
  • Products
  • Groups
  • Scenes
• Check on notifications
  • Products
  • Groups
  • Scenes