WIEGAND TCP/IP Adapter (Alias UHPPOTE)

kBrausew

@randyandy
Steht doch da: Keine Geräte im lokalen Netzwerk gefunden.
Hast du Docker oder eine andere Virtualisierung

Stell mal Interface auf 192.168.178.49. Das sollte doch die Netzwerk-Schnittstelle deines ioBroker's sein

Samson71

@randyandy sagte in WIEGAND TCP/IP Adapter (Alias UHPPOTE):

192.168.178.29 ist der PHPPote Server

Was meinst Du mit "Server"? Ist das die 4-Door-Controller-Karte oder "nur" der PC/Rechner mit dem Du die Karte/den Controller mit Deiner Eigenbau-Lösung ausliest?

Ändere mal die Netzwerkschnittstelle in Deinen Einstellungen von "Listen on all IPs" auf eth0 Deines ioBroker.

kBrausew

@samson71 ... und "schreib" die IP hier her

kBrausew · 11.03.2022

Ich habe mal noch die Schreib- und Übersetzungsfehler entfernt...
... und eine kleine Unzulänglichkeit in der Eventauswertung (siehe: PR1720 )

RandyAndy

@Samson71

Server ist die 4-Door Controller Karte. Ich verwende keinen Docker.
192.168.178.49 habe ich schon mal eingestellt, ändert aber nichts.
Ich checke es aber gerne noch einmal

Andreas

RandyAndy

@samson71

Hilft gar nichts. Ich habe mal den Port auf 60001 eingestellt, macht aber auch keinen Unterschied.

hier meine Settings:
2022-03-19 21_04_18-instances - raspberrypi.png

kBrausew

@randyandy
Installier die v0.4.6
Bleib auf eth0
Lösch den Controller
Restart des Adapters
Geh zur Ip Setting
Führe die Device-Suche aus ohne weiter Parameter
Jetzt die komplette Log von Adapter...

BTW: Hast du das nativ Web auf dem Controller aktiviert und mal die Config angeschaut welche Serial hier steht

RandyAndy

@kbrausew

Here we go.
LOG.txt

Und hier noch ein Screenshot the UHPPote controllers.

Die ID habe ich gelöscht. Aber die "xxxxxxxxx" in der LOG-Datei und im Config des UHPPote-Controller sind identisch.
Er scheint da schon etwas zu finden.
Nur so als Vermutung. Ich verwende kein Redis. Irgendwas scheint der Adapter aber zu erwarten.
2022-03-20 19_28_23-Web Controller.png

kBrausew

@randyandy hat sich die listbox nicht befüllt nach dem Search oder kam wieder "...keine Device gefunden..."

kBrausew

@randyandy sagte in WIEGAND TCP/IP Adapter (Alias UHPPOTE):

Er scheint da schon etwas zu finden.

Reset the device clock: xxxxxxxxx
wiegand-tcpip.0.controllers.xxxxxxxxx ok
Connect to controller: xxxxxxxxx
  {"deviceId":"xxxxxxxxx","address":"192.168.178.29","forceBroadcast":false}]
  {"config":{"name":"ctx","bind":"0.0.0.0","broadcast":"0.0.0.0:60000","listen":"0.0.0.0:60001","timeout":2500,"controllers":{},"debug":false}}
Create controller xxxxxxxxx for Model 4-Door Objects
starting. Version 0.4.6 (non-npm: kBrausew/ioBroker.wiegand-tcpip#v0.4.6) in /opt/iobroker/node_modules/iobroker.wiegand-tcpip, node: v14.19.0, js-controller: 4.0.21

Da ist alles OK!!!

Bitte konfiguriere...
Netzwerkschnittstelle: 192.168.178.49
Controller: Serial wie gehabt... Modell noch Eintragen; Rest LEER (für Broadcast)

Jetzt sollte alles funktionieren!
Zu sehen gibt's im Log als letzte Meldung

Reset the device clock: xxxxxxxxx

... das wars, fertig.

Jetzt noch ne Karte an den Reader und die Datenpunkte "lastSwipe" anschauen ...
Auswerten für wirkliches Tür-Öffnen würde ich generell nur über "unlocked"
Und öffnen über "remoteOpen"

BTW: redis ist irgendwas zwischen system.adapter... und dem Adapter an-sich... ich mache da Garnichts damit.

kBrausew

REDIS hier mal lesen

RandyAndy

@kbrausew

es kam wieder kein Device gefunden.
Im LOG sehe ich auch dass es eine Verbindung gibt. Hier ein Ausschnitt aus dem LOG

wiegand-tcpip.0
	2022-03-20 22:29:08.396	debug	received 192.168.178.48:60000 17 90 00 00 71 7f 38 19 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-20 22:29:08.204	debug	sent 192.168.178.255:60000 17 90 00 00 71 7f 38 19 c0 a8 b2 ff 61 ea 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-20 22:29:08.200	debug	received 192.168.178.48:60000 17 8e 00 00 71 7f 38 19 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-20 22:29:08.138	debug	sent 192.168.178.255:60000 17 8e 00 00 71 7f 38 19 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-20 22:29:08.136	info	Connect to controller: xxxxxxxxx
wiegand-tcpip.0
	2022-03-20 22:29:08.130	debug	received 192.168.178.48:60000 17 20 00 00 71 7f 38 19 73 1f 00 00 01 01 01 01 04 69 5a aa 20 22 03 20 22 14 37 01 01 01 01 01 00 00 00 00 00 22 29 07 00 00 00 00 00 00 00 00 00 00 00 22 03 20 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-20 22:29:08.128	debug	sent 192.168.178.255:60000 17 20 00 00 71 7f 38 19 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-20 22:29:06.307	info	Create controller xxxxxxxxx for Model 4-Door Objects
wiegand-tcpip.0
	2022-03-20 22:29:06.253	info	starting. Version 0.4.6 (non-npm: kBrausew/ioBroker.wiegand-tcpip#v0.4.6) in /opt/iobroker/node_modules/iobroker.wiegand-tcpip, node: v14.19.0, js-controller: 4.0.21

Scheint immer an der Adresse 192.168.178.48 und 192.168.178.255 hängen zu bleiben. 192.168.178.255 wird meines Wissen nach keinem physikalischen Gerät zugewiesen. 192.168.178.48 ist mein go-e charger, der ist aber momentan gar nicht angeschlossen.

Andreas

kBrausew

@randyandy
Alles in Ordnung
ioBroker sendet Broadcast (192.168.178.255) und der Kontroller (192.168.178.48) antwortet.

Schau mal im Web-GUI nach, schätze du hast hier "48" anstatt "23" stehen! ... in der Fritte sollte das auch erkennbar sein?!?

Adapter funktioniert somit.

Jetzt noch Card-Swipe...

Das er kein Device findet im IP-Setup-Tool schau ich mir nochmal im Code an (der Antest gerade eben brachte aber auch kein Ergebnis bei mir) Spiel aber keine Rolle da man die IP sowieso über die originalen Tools einstellen sollte. Glaube deaktivier dieses Set-IP-Tool wieder wenn's eh nicht läuft.

kBrausew

@kbrausew sagte in WIEGAND TCP/IP Adapter (Alias UHPPOTE):

... "48" anstatt "23" stehen! ...

Vergiss es, da passt was im Broadcast-Setup nicht. Das muss ich mir genau anschauen, je nach Netzwerk-Interface und Betriebssystem macht er was anderes => ???

Solange muss die IP für Controller und ioBroker eigegeben werden

BTW: Dein PHP-Server konsumiert ja auch die Events (Card-Swipe und der Gleichen)
So wie ich das bis jetzt mal angeschaut habe PHP Server carbonsphere, werden nicht beide gleichzeitig auf den Controller zugreifen können. Du musst dich für einen von beiden entscheiden, leider... aber test mal lieber selber wer die Events erhält (einer / beide / keiner ??)
siehe auch (im ioBroker Log)

Extendend HeartBeat negative (try re-connect device): xxxxxxxx

RandyAndy

@kbrausew

Habe nun mal die IP Adresse des Controllers eingetragen. Da scheint ja etwas zu geschehen.
Bezüglich des gleichzeitigen Zugriffs sollte das eigentlich nicht so sein. Die php-Skripte die ich verwende werden immer angestoßen z.B. durch einen cron-job oder durch den iobroker z.B. kann ich die Zugangs-Tags und Codes per php-Skript sperren und wieder freischalten (Ist echt hilfreich in Corona-Zeiten :grinning:).
Was bedeutet aber Incorrect controller-setup for non/broadcast: xxxxxxxxx.
Ich habe mal alle Meldungen ab dem Neustart des Controller anbei zusammengestellt.

wiegand-tcpip.0
	2022-03-21 08:09:35.160	debug	received 192.168.178.29:60000 17 82 00 00 71 7f 38 19 04 03 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 08:09:35.155	debug	sent 192.168.178.29:60000 17 82 00 00 71 7f 38 19 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 08:09:35.153	debug	received 192.168.178.29:60000 17 82 00 00 71 7f 38 19 03 03 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 08:09:35.150	debug	sent 192.168.178.29:60000 17 82 00 00 71 7f 38 19 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 08:09:35.147	debug	received 192.168.178.29:60000 17 82 00 00 71 7f 38 19 02 03 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 08:09:35.145	debug	sent 192.168.178.29:60000 17 82 00 00 71 7f 38 19 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 08:09:35.141	debug	received 192.168.178.29:60000 17 82 00 00 71 7f 38 19 01 03 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 08:09:35.138	debug	sent 192.168.178.29:60000 17 82 00 00 71 7f 38 19 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 08:09:35.135	debug	received 192.168.178.29:60000 17 30 00 00 71 7f 38 19 20 22 03 21 08 09 35 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 08:09:35.133	debug	sent 192.168.178.29:60000 17 30 00 00 71 7f 38 19 20 22 03 21 08 09 35 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 08:09:35.130	info	Reset the device clock: 423133041
wiegand-tcpip.0
	2022-03-21 08:09:35.128	debug	received 192.168.178.29:60000 17 90 00 00 71 7f 38 19 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 08:09:35.068	debug	sent 192.168.178.29:60000 17 90 00 00 71 7f 38 19 c0 a8 b2 31 61 ea 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 08:09:35.064	debug	received 192.168.178.29:60000 17 8e 00 00 71 7f 38 19 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 08:09:35.003	debug	sent 192.168.178.29:60000 17 8e 00 00 71 7f 38 19 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 08:09:35.001	info	Connect to controller: xxxxxxxxx
wiegand-tcpip.0
	2022-03-21 08:09:34.996	debug	received 192.168.178.29:60000 17 20 00 00 71 7f 38 19 73 1f 00 00 01 01 01 01 04 69 5a aa 20 22 03 20 22 14 37 01 01 01 01 01 00 00 00 00 00 08 09 34 00 00 00 00 00 00 00 00 00 00 00 22 03 21 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 08:09:34.994	debug	sent 192.168.178.29:60000 17 20 00 00 71 7f 38 19 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 08:09:34.977	warn	Incorrect controller-setup for non/broadcast: xxxxxxxxx
wiegand-tcpip.0
	2022-03-21 08:09:34.851	info	Create controller xxxxxxxxxx for Model 4-Door Objects
wiegand-tcpip.0
	2022-03-21 08:09:34.810	info	starting. Version 0.4.6 (non-npm: kBrausew/ioBroker.wiegand-tcpip#v0.4.6) in /opt/iobroker/node_modules/iobroker.wiegand-tcpip, node: v14.19.0, js-controller: 4.0.21

kBrausew

@randyandy sagte in WIEGAND TCP/IP Adapter (Alias UHPPOTE):

@kbrausew
... Incorrect controller-setup for ...

Entweder alle drei ( Ctrl-IP + ioB-IP + Port) Felder füllen oder keins davon.

... php-Skripte ...

Ok, dann sollte es gehen... würde einfach mal zwei drei Tage die Log beobachten auf:

Extendend HeartBeat negative (try re-connect device): xxxxxxxx

Das wäre der Indiz auf einen "Lauchangriff" durch die PHP-Scripte ;)
Das wird aber nur ein paar mal am Tag ( jeder 10ten Heartbeat) geprüft. => "Extendend" eben ;-)

...
BTW: Test Swipe und remoteOpen nicht vergessen

RandyAndy

@kbrausew sagte in WIEGAND TCP/IP Adapter (Alias UHPPOTE):

Test Swipe und remoteOpen nicht vergessen

remote Open muss ich noch machen, dazu muss ich aber am Objekt sein.
Swipe wird bestimmt 30 mal am Tag gemacht. In diesem Feld taucht aber nie etwas auf, ist immer auf 0. Während das php Skript eben regelmäßig etwas anzeigt.
Wie ich schon beschrieben habe, gibt das php Skript ein LOG aus und das Werte ich mit dem PARSER Adapter aus. ICh rufe das Skipt alle 5 Minuten auf und ziehe die letzten 3 zugänge ab.

Andreas

kBrausew

remote Open muss ich noch machen, dazu muss ich aber am Objekt sein.

Swipe wird bestimmt 30 mal am Tag gemacht...

stimmen die?

kannst du das LowLevel hier mitschneiden?

RandyAndy

@kbrausew

Here we go
Die Ports sind oben wie unten identisch auf 60001 eingestellt.

wiegand-tcpip.0
	2022-03-21 14:52:39.679	debug	Request remote open: xxxxxxxxx Door-1: {"deviceId":xxxxxxxxx,"opened":true}
wiegand-tcpip.0
	2022-03-21 14:52:39.678	debug	received 192.168.178.29:60000 17 40 00 00 71 7f 38 19 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:52:39.677	debug	sent 192.168.178.29:60000 17 40 00 00 71 7f 38 19 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:52:32.335	debug	Request remote open: xxxxxxxxx Door-1: {"deviceId":xxxxxxxxx,"opened":true}
wiegand-tcpip.0
	2022-03-21 14:52:32.334	debug	received 192.168.178.29:60000 17 40 00 00 71 7f 38 19 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:52:32.333	debug	sent 192.168.178.29:60000 17 40 00 00 71 7f 38 19 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.823	debug	received 192.168.178.29:60000 17 82 00 00 71 7f 38 19 04 03 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.818	debug	sent 192.168.178.29:60000 17 82 00 00 71 7f 38 19 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.815	debug	received 192.168.178.29:60000 17 82 00 00 71 7f 38 19 03 03 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.812	debug	sent 192.168.178.29:60000 17 82 00 00 71 7f 38 19 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.808	debug	received 192.168.178.29:60000 17 82 00 00 71 7f 38 19 02 03 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.806	debug	sent 192.168.178.29:60000 17 82 00 00 71 7f 38 19 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.800	debug	received 192.168.178.29:60000 17 82 00 00 71 7f 38 19 01 03 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.798	debug	sent 192.168.178.29:60000 17 82 00 00 71 7f 38 19 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.793	debug	received 192.168.178.29:60000 17 30 00 00 71 7f 38 19 20 22 03 21 14 50 37 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.791	debug	sent 192.168.178.29:60000 17 30 00 00 71 7f 38 19 20 22 03 21 14 50 37 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.786	info	Reset the device clock: xxxxxxxxx
wiegand-tcpip.0
	2022-03-21 14:50:37.785	debug	received 192.168.178.29:60000 17 90 00 00 71 7f 38 19 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.595	debug	sent 192.168.178.29:60000 17 90 00 00 71 7f 38 19 c0 a8 b2 31 71 17 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.591	debug	received 192.168.178.29:60000 17 8e 00 00 71 7f 38 19 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.401	debug	sent 192.168.178.29:60000 17 8e 00 00 71 7f 38 19 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.397	info	Connect to controller: xxxxxxxxx
wiegand-tcpip.0
	2022-03-21 14:50:37.392	debug	received 192.168.178.29:60000 17 20 00 00 71 7f 38 19 74 1f 00 00 01 01 01 01 04 78 70 aa 20 22 03 21 12 49 15 01 01 01 01 01 00 00 00 00 00 14 50 36 00 00 00 00 00 00 00 00 00 00 00 22 03 21 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.390	debug	sent 192.168.178.29:60000 17 20 00 00 71 7f 38 19 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wiegand-tcpip.0
	2022-03-21 14:50:37.278	info	Create controller xxxxxxxxx for Model 4-Door Objects
wiegand-tcpip.0
	2022-03-21 14:50:37.235	info	starting. Version 0.4.6 (non-npm: kBrausew/ioBroker.wiegand-tcpip#v0.4.6) in /opt/iobroker/node_modules/iobroker.wiegand-tcpip, node: v14.19.0, js-controller: 4.0.21
wiegand-tcpip.0
	2022-03-21 14:50:36.879	debug	States connected to redis: 127.0.0.1:9000
wiegand-tcpip.0
	2022-03-21 14:50:36.813	debug	States create User PubSub Client
wiegand-tcpip.0
	2022-03-21 14:50:36.812	debug	States create System PubSub Client
wiegand-tcpip.0
	2022-03-21 14:50:36.744	debug	Redis States: Use Redis connection: 127.0.0.1:9000
wiegand-tcpip.0
	2022-03-21 14:50:36.662	debug	Objects connected to redis: 127.0.0.1:9001
wiegand-tcpip.0
	2022-03-21 14:50:36.655	debug	Objects client initialize lua scripts
wiegand-tcpip.0
	2022-03-21 14:50:36.510	debug	Objects create User PubSub Client
wiegand-tcpip.0
	2022-03-21 14:50:36.508	debug	Objects create System PubSub Client
wiegand-tcpip.0
	2022-03-21 14:50:36.506	debug	Objects client ready ... initialize now

kBrausew

@randyandy sagte in WIEGAND TCP/IP Adapter (Alias UHPPOTE):

sent 192.168.178.29:60000 17 90 00 00 71 7f 38 19 c0 a8 b2 31 71 17 00

Muss dich leider enttäuschen; der untere hat eine '0' Zuwenig und steht auf 6001 anstatt auf 60001

Aktuelle Test Version	0.4.6
Veröffentlichungsdatum	11.03.2022
Installation via URL	https://github.com/kBrausew/ioBroker.wiegand-tcpip/tarball/v0.4.6
NodeJS	min. v14.18.3
Gitlab	https://github.com/kBrausew/ioBroker.wiegand-tcpip/blob/master/README.md

Hardware	Link
Wiegand to TCP/IP	(https://ingenier.wordpress.com/zutrittskontrolle/ german)
Door Access Controller Shenzhen Weigeng Industrial	(http://wiegand.com.cn)
UHPPOTE -UT0311-L01 (up to L04)	(https://github.com/uhppoted)
VBESTLIFE, Dioche, Tangxi, ...	(Big marketplace 😉 )
i-keys IK-Point SC300xNT SC90xNT?	(https://www.i-keys.de)
Secukey C1 - C4	(http://secukey.com.cn/)
S4A ACB	(http://www.s4a.com.cn/)

Operation	Objekt	Zugriff
Tür öffnen (Relais "auslösen):	wiegand-tcpip.$(instance).controllers.$(deviceId).$(doorId).remoteOpen	set TRUE
Xxx Event:	wiegand-tcpip.$(instance).controllers.$(deviceId).$(doorId).unlocked	subscribe TRUE
Info:	wiegand-tcpip.$(instance).controllers.$(deviceId).$(doorId).xYzzz	??

Community Forum

NEWS

WIEGAND TCP/IP Adapter (Alias UHPPOTE)

Support us

540

32.5k

81.8k

1.3m