When I add correct setup (IP, Port, multi) the adapter add the correct objects.
But after this no date comes from ekey LAN converter.
In Log i see following message:
"adapter listening 0.0.0.0:56000"
Fore sure, the IP address is not 0.0.0.0
I bought the system 1 year ago and tested it with same setup successfully.
2 Month ago I installed it and it doesn't work now.
I tested it with version 1.1.0 and 1.2.3.

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/ioBroker/ioBroker.ekey

• [E301] Tests on Travis-ci.org are broken. Please fix.
• [E605] No actual year found in copyright. Please add "Copyright (c) 2019 Bluefox [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2019 Bluefox [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.

I´m integrating Ekey-Multi-central via CV-Lan (192.168.2.250) to iobroker (192.168.2.223).
Ekey Adapter Version 1.0.0.

Ekey support told that for Multi-Central connection to CV-Lan data format MULTI is mandatory. Raw/Rare doesn´t work.

MULTI format uses strings with separator as data format. I used default configured separator _ .
Documentation says that user-name can be 10 characters max.

The problem:
If user-name is directly included between separators data points are correctly fed.
If there is a blank appended to user-name before separator data points are shifted and incomplete.

IMO adapter should be able to cope with a blank after user-name.
Appended pics show those diverging data point results.

I used Windows software packet-sender (192.168.2.118) to create UDP data strings and for display of CV Lan data strings.

Please help.

More details can be found at
ioBroker forum at https://forum.iobroker.net/viewtopic.php?p=206516#p206516

Hi

i am new at iobroker

i have a ekey net system running at server (its not a multi and not a home system)

it uses the ekey net CV Lan (not the home cv lan) where i could set rare

the adapter will not find it manual

and when i ad it by hand i get at every try

invalid version length! 828321840 != 3

wenn i use the scanner.

any ideas or help?

thanks

tom

Hallo wäre es eventuell möglich auch die Integration in Iobroker ohne dem EkeyUDPRS485 Adapter?

Habe nen Ekey Home mit einem RS485 Adapter am Rasperry 3 , nur leider kann ich leider nicht programmieren daher die Frage ? Wäre vielleicht eine Möglichkeit mehr Ekey User anzusprechen ohne dem etwas teuren EkeyConverter ? Ich würde es zb als Anwesenheits bzw Alarmanlagesteuernung verwenden.
sofern Interresse bestehen sollte hier die Infos
mfg
mikewolf

mit folgenden programm funktionierts einwandfrei auch ohne ekeyConverter direkt am ekey mit USB to RS485

eKey RS485.log.txt (8,5 KB, 2x aufgerufen) eKeyHack-1.0.0-SNAPSHOT-jar-with-dependencies.jar.zip (699,4 KB, 1 Hit)
https://github.com/tuxedo0801/ekeyde...eyDecoder.java

https://knx-user-forum.de/forum/%C3%B6ffentlicher-bereich/knx-eib-forum/diy-do-it-yourself/34358-ekey-fingerscanner-per-rs485-auslesen-protokollanalyse/page4

https://knx-user-forum.de/forum/%C3%B6ffentlicher-bereich/knx-eib-forum/5390-homeserver-ekey-anbindung-weiterentwicklung-%C3%BCber-das-forum-wer-hat-interesse

Hallo
habe festgestellt, das immer beim Linken Ringfinger (FingerNr2) die falsche Action Nr/Bezeichnung zurückgegeben wird.
beim rechten Mittelfinger kommt Action = 1
beim linken Ringfinger kommt Action = REJECT

Erstmal danke, den Adapter net fähig zu machen :-)

Version 1.2.3 aktualisiert die Objekte bei mir nur 1x nach Neuinstallation. Bei jeder Nutzung des Fingerscanners erscheint Im Log folgende Warnung:

Welche Informationen zum Fehler darf ich noch liefern?

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

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

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some 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 or info log there from these checks please adjust the adapter and fix the relevant cases.

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

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

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.

Think about update stable version to 1.2.3

Version: stable=1.1.0 (1202 days old) => latest=1.2.3 (15 days old)
Installs: stable=264 (91.35%), latest=23 (7.96%), total=289
Click to edit

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/ioBroker/ioBroker.ekey

• [E104] No common.titleLang found in io-package.json
• [E150] No common.connectionType found in io-package.json
• [E152] No common.dataSource found in io-package.json
• [E605] No actual year found in copyright. Please add "Copyright (c) 2018-2022 Bluefox [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2018-2022 Bluefox [email protected]" at the start of LICENSE

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

• [W505] setTimeout found in "main.js", but no clearTimeout detected

Thanks,
your automatic adapter checker.

Guten Tag,

Ich habe mit dem EKey Adapter ein Problem.
In meinem System sind zwei Fingerprintleser, eine Reg4 und der LAN Converter verbaut.
Ich nutze zwei Schlüssel, S1 auf beiden Fingerprints und S2 nur auf dem einen.
S1 triggert je nach Tür das Relais 1 oder Relais 2.
S2 triggert das Relais 3.
Beim Datenpunkt im ioBroker bekomme ich jedoch nur das Relais 2 oder Relais 3 angezeigt, egal bei welcher Türe ich rein gehe.
Vom Support EKey habe ich eine Schnittstellendefinition mit sämtlichen Datenpunkten bekommen.
Aus dieser kann ich jedoch den Datenpunkt des geschalteten Relais nicht entnehmen. Wird dieser Datenpunkt im Adapter selbst generiert?
Im ioBroker bekomme ich «nur» die Datenpunkte action, finger, relay, serial und user.
Gemäss Schnittstellenbeschreibung werden jedoch folgende Datenpunkte übergeben:
Pakettyp, User ID, User Name, User Status, Finger ID, Schlüssel ID, Seriennr FS, Name FS, Aktion, Input ID

Kann bezüglich dem Relais Problem etwas gemacht werden?

Vielen Dank im Voraus, Gruss Thomas

Dear Adapter developer,

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!

We have detected that your adapter supports the compact mode. Please use the latest js-controller 2.0 and verify that everything works.

Some more information what is important to check can be found at ioBroker/ioBroker.js-controller#512

On questions please answer to the linked issue. Please close this issue after your test and add the version number that you have tested please as a comment.

Thank you for your support.

Both Links in README.md

http://descargas.futurasmus-knxgroup.org/DOC/GB/E-Key/13004/Operating_instructions_ekey_converter_UDP_RS485_ID51.pdf
https://www.ekey.net/assets/media_center/EN/User_Guide_ekey_net_4.3_en_web_ID181.pdf

are dead.

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