Jemand eine Idee?

modbus.0	2019-12-18 13:36:05.927	warn	(2323) On error: {"errno":"ETIMEDOUT","code":"ETIMEDOUT","syscall":"connect","address":"192.168.2.210","port":502}
modbus.0	2019-12-18 13:36:05.926	error	(2323) Client in error state.
modbus.0	2019-12-18 13:36:05.923	error	(2323) Socket Error
modbus.0	2019-12-18 13:32:51.366	warn	(2323) On error: {"errno":"ETIMEDOUT","code":"ETIMEDOUT","syscall":"connect","address":"192.168.2.210","port":502}
modbus.0	2019-12-18 13:32:51.365	error	(2323) Client in error state.
modbus.0	2019-12-18 13:32:51.363	error	(2323) Socket Error
modbus.0	2019-12-18 13:32:49.176	info	(2323) List of port: [{"comName":"/dev/ttyAMA0"}]```

Hier:
https://www.iobroker.net/docu/index-15.htm?page_id=8323&lang=de

@Daniel-S

mhhh. Der Befehl:

curl -sL https://raw.githubusercontent.com/ioBroker/ioBroker/stable-installer/fix_installation.sh | bash

hat schonmal bis auf den Modbus alles repariert....

Moin,

nach dem NPM Update funktionieren BLE, Modbus und auch web.0 SSL bei mir nicht mehr. Anbei der Log. Jemand eine Idee woran das liegen könnte?
Was könnte ich versuchen bevor ich das ganze wieder neu aufsetze?

Grüße aus Hamburg

host.raspberrypi	2019-12-18 12:12:31.605	error	instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
web.0	2019-12-18 12:12:31.062	info	(3035) https server listening on port 1024
web.0	2019-12-18 12:12:31.059	warn	(3035) Terminated (JS_CONTROLLER_STOPPED): Without reason
web.0	2019-12-18 12:12:31.056	error	(3035) port 443 already in use
web.0	2019-12-18 12:11:32.170	info	(3035) Secure socket.io server listening on port 443
web.0	2019-12-18 12:11:31.596	info	(3035) starting. Version 2.4.10 in /opt/iobroker/node_modules/iobroker.web, node: v10.17.0
host.raspberrypi	2019-12-18 12:11:29.411	info	instance system.adapter.web.0 started with pid 3035
modbus.0	2019-12-18 12:10:59.777	warn	(2750) On error: {"errno":"ETIMEDOUT","code":"ETIMEDOUT","syscall":"connect","address":"192.168.2.210","port":502}
modbus.0	2019-12-18 12:10:59.776	error	(2750) Client in error state.
modbus.0	2019-12-18 12:10:59.775	error	(2750) Socket Error
host.raspberrypi	2019-12-18 12:10:59.383	info	Restart adapter system.adapter.web.0 because enabled
host.raspberrypi	2019-12-18 12:10:59.380	error	instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
web.0	2019-12-18 12:10:58.834	info	(2991) https server listening on port 1024
web.0	2019-12-18 12:10:58.831	warn	(2991) Terminated (JS_CONTROLLER_STOPPED): Without reason
web.0	2019-12-18 12:10:58.828	error	(2991) port 443 already in use
web.0	2019-12-18 12:09:59.954	info	(2991) Secure socket.io server listening on port 443
web.0	2019-12-18 12:09:59.415	info	(2991) starting. Version 2.4.10 in /opt/iobroker/node_modules/iobroker.web, node: v10.17.0
host.raspberrypi	2019-12-18 12:09:57.141	info	instance system.adapter.web.0 started with pid 2991
host.raspberrypi	2019-12-18 12:09:27.110	info	Restart adapter system.adapter.web.0 because enabled
host.raspberrypi	2019-12-18 12:09:27.107	error	instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
web.0	2019-12-18 12:09:26.568	info	(2939) https server listening on port 1024
web.0	2019-12-18 12:09:26.566	warn	(2939) Terminated (JS_CONTROLLER_STOPPED): Without reason
web.0	2019-12-18 12:09:26.562	error	(2939) port 443 already in use
web.0	2019-12-18 12:08:27.702	info	(2939) Secure socket.io server listening on port 443
web.0	2019-12-18 12:08:27.115	info	(2939) starting. Version 2.4.10 in /opt/iobroker/node_modules/iobroker.web, node: v10.17.0
host.raspberrypi	2019-12-18 12:08:24.912	info	instance system.adapter.web.0 started with pid 2939
host.raspberrypi	2019-12-18 12:07:54.883	info	Restart adapter system.adapter.web.0 because enabled
host.raspberrypi	2019-12-18 12:07:54.880	error	instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
web.0	2019-12-18 12:07:54.317	info	(2900) https server listening on port 1024
web.0	2019-12-18 12:07:54.316	warn	(2900) Terminated (JS_CONTROLLER_STOPPED): Without reason
web.0	2019-12-18 12:07:54.314	error	(2900) port 443 already in use
modbus.0	2019-12-18 12:07:45.219	warn	(2750) On error: {"errno":"ETIMEDOUT","code":"ETIMEDOUT","syscall":"connect","address":"192.168.2.210","port":502}
modbus.0	2019-12-18 12:07:45.217	error	(2750) Client in error state.
modbus.0	2019-12-18 12:07:45.216	error	(2750) Socket Error
web.0	2019-12-18 12:06:55.422	info	(2900) Secure socket.io server listening on port 443
web.0	2019-12-18 12:06:54.874	info	(2900) starting. Version 2.4.10 in /opt/iobroker/node_modules/iobroker.web, node: v10.17.0
host.raspberrypi	2019-12-18 12:06:52.557	info	instance system.adapter.web.0 started with pid 2900
host.raspberrypi	2019-12-18 12:06:22.527	info	Restart adapter system.adapter.web.0 because enabled
host.raspberrypi	2019-12-18 12:06:22.524	error	instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
web.0	2019-12-18 12:06:21.982	info	(2872) https server listening on port 1024
web.0	2019-12-18 12:06:21.980	warn	(2872) Terminated (JS_CONTROLLER_STOPPED): Without reason
web.0	2019-12-18 12:06:21.976	error	(2872) port 443 already in use
web.0	2019-12-18 12:05:23.111	info	(2872) Secure socket.io server listening on port 443
web.0	2019-12-18 12:05:22.538	info	(2872) starting. Version 2.4.10 in /opt/iobroker/node_modules/iobroker.web, node: v10.17.0
host.raspberrypi	2019-12-18 12:05:20.564	info	instance system.adapter.web.0 started with pid 2872
host.raspberrypi	2019-12-18 12:04:50.536	info	Restart adapter system.adapter.web.0 because enabled
host.raspberrypi	2019-12-18 12:04:50.533	error	instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
web.0	2019-12-18 12:04:49.990	info	(2809) https server listening on port 1024
web.0	2019-12-18 12:04:49.987	warn	(2809) Terminated (JS_CONTROLLER_STOPPED): Without reason
web.0	2019-12-18 12:04:49.983	error	(2809) port 443 already in use
modbus.0	2019-12-18 12:04:30.663	warn	(2750) On error: {"errno":"ETIMEDOUT","code":"ETIMEDOUT","syscall":"connect","address":"192.168.2.210","port":502}
modbus.0	2019-12-18 12:04:30.661	error	(2750) Client in error state.
modbus.0	2019-12-18 12:04:30.658	error	(2750) Socket Error
web.0	2019-12-18 12:03:51.045	info	(2809) Secure socket.io server listening on port 443
web.0	2019-12-18 12:03:50.449	info	(2809) starting. Version 2.4.10 in /opt/iobroker/node_modules/iobroker.web, node: v10.17.0
host.raspberrypi	2019-12-18 12:03:47.634	info	instance system.adapter.web.0 started with pid 2809
host.raspberrypi	2019-12-18 12:03:17.609	info	Restart adapter system.adapter.web.0 because enabled
host.raspberrypi	2019-12-18 12:03:17.608	error	instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
web.0	2019-12-18 12:03:17.084	info	(2757) https server listening on port 1024
web.0	2019-12-18 12:03:17.082	warn	(2757) Terminated (JS_CONTROLLER_STOPPED): Without reason
web.0	2019-12-18 12:03:17.080	error	(2757) port 443 already in use
host.raspberrypi	2019-12-18 12:02:51.439	info	iobroker exit 0

• list item

|Systemdata| Bitte Ausfüllen|

@Röstkartoffel
Moin,
Danke der Nachfrage.

Ich habe den Raspi neu aufgesetzt und dem IoBroker neu installiert.
Modbus läuft seitdem ohne Probleme.

Gruß

@Stabilostick
da kommt sowas:

Ping geht

aber ich kriege den Port nicht:

Okay, danke für die Info!

Das hatte ich befürchtet, da ich die Schnittstelle dort schon aktiviert habe. Scheint also für mein Problem nicht die Lösung zu sein. Mist...

Gruß

Moin,
ich versuche seit Tagen den Modbus zum laufen zu kriegen und bin mit meinem Latein ziemlich am Ende. Wenn jemand also eine hilfreich Idee hat, immer her damit. Ich bin für jede Hilfestellung echt dankbar.

Meine SMA PV Anlage hat einen Sunnyboy 4.0 Inverter welcher im Keller steht. Dort sind jetzt auch der Zyxel1200-5 Switch an dem auch der Raspberry hängt. Auf diesem läuft der IoBroker usw. Mittlerweile geht ein Netzwerkkabel vom Keller bis ins Dachgeschoß wo der Speedport W724V hängt. Dieser verteilt das Wlan womit alle anderen Teilnehmer verbunden sind. Der SMA SHM 2.0 hängt noch am ursprünglichen DLAN und der bläst seine Daten noch an den Speedport im Dach. Ursprünglich sollten der Inverter auch seine Daten über das DLan schicken aber ich habe irgendwo gelesen das damit der Modbus nicht funktioniert und daher den Switch in den Keller eingebaut.

Eigentlich funktioniert alles hervorragend, bis auf den Modbus. Was kann ich noch tun? Was habe ich vergessen? Welche Informationen fehlen noch für ein Fehlerbild?

Vielen Dank!

2019-10-20 00:00:48.399 - error: modbus.0 Socket Error
2019-10-20 00:00:48.399 - error: modbus.0 Client in error state.
2019-10-20 00:00:48.400 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:01:52.569 - error: modbus.0 Socket Error
2019-10-20 00:01:52.569 - error: modbus.0 Client in error state.
2019-10-20 00:01:52.570 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:02:56.719 - error: modbus.0 Socket Error
2019-10-20 00:02:56.719 - error: modbus.0 Client in error state.
2019-10-20 00:02:56.719 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:04:00.879 - error: modbus.0 Socket Error
2019-10-20 00:04:00.880 - error: modbus.0 Client in error state.
2019-10-20 00:04:00.881 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:05:05.039 - error: modbus.0 Socket Error
2019-10-20 00:05:05.040 - error: modbus.0 Client in error state.
2019-10-20 00:05:05.041 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:05:40.870 - info: info.0 Popup news was read...
2019-10-20 00:06:09.199 - error: modbus.0 Socket Error
2019-10-20 00:06:09.200 - error: modbus.0 Client in error state.
2019-10-20 00:06:09.200 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:07:13.359 - error: modbus.0 Socket Error
2019-10-20 00:07:13.360 - error: modbus.0 Client in error state.
2019-10-20 00:07:13.360 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:08:17.519 - error: modbus.0 Socket Error
2019-10-20 00:08:17.520 - error: modbus.0 Client in error state.
2019-10-20 00:08:17.520 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:09:21.679 - error: modbus.0 Socket Error
2019-10-20 00:09:21.680 - error: modbus.0 Client in error state.
2019-10-20 00:09:21.681 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:10:00.667 - info: host.raspberrypi object change system.adapter.modbus.0
2019-10-20 00:10:00.668 - info: host.raspberrypi stopInstance system.adapter.modbus.0
2019-10-20 00:10:00.668 - info: host.raspberrypi stopInstance system.adapter.modbus.0 killing pid 31428
2019-10-20 00:10:00.705 - info: host.raspberrypi instance system.adapter.modbus.0 terminated with code 156 ()
2019-10-20 00:10:31.427 - info: host.raspberrypi object change system.adapter.modbus.0
2019-10-20 00:10:31.439 - info: host.raspberrypi instance system.adapter.modbus.0 started with pid 17079
2019-10-20 00:10:32.611 - info: modbus.0 starting. Version 2.0.9 in /opt/iobroker/node_modules/iobroker.modbus, node: v10.16.3
2019-10-20 00:10:36.162 - error: modbus.0 Socket Error
2019-10-20 00:10:36.165 - error: modbus.0 Client in error state.
2019-10-20 00:10:36.166 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:11:40.320 - error: modbus.0 Socket Error
2019-10-20 00:11:40.321 - error: modbus.0 Client in error state.
2019-10-20 00:11:40.322 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:12:44.479 - error: modbus.0 Socket Error
2019-10-20 00:12:44.480 - error: modbus.0 Client in error state.
2019-10-20 00:12:44.480 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:13:48.639 - error: modbus.0 Socket Error
2019-10-20 00:13:48.640 - error: modbus.0 Client in error state.
2019-10-20 00:13:48.641 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:14:52.799 - error: modbus.0 Socket Error
2019-10-20 00:14:52.800 - error: modbus.0 Client in error state.
2019-10-20 00:14:52.801 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:15:56.960 - error: modbus.0 Socket Error
2019-10-20 00:15:56.960 - error: modbus.0 Client in error state.
2019-10-20 00:15:56.961 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:17:01.119 - error: modbus.0 Socket Error
2019-10-20 00:17:01.120 - error: modbus.0 Client in error state.
2019-10-20 00:17:01.121 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:18:05.279 - error: modbus.0 Socket Error
2019-10-20 00:18:05.279 - error: modbus.0 Client in error state.
2019-10-20 00:18:05.279 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:19:09.439 - error: modbus.0 Socket Error
2019-10-20 00:19:09.440 - error: modbus.0 Client in error state.
2019-10-20 00:19:09.440 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:19:41.146 - error: cloud.0 Ping timeout
2019-10-20 00:19:41.148 - info: cloud.0 Connection changed: Ping timeout
2019-10-20 00:19:41.148 - info: cloud.0 Connection lost
2019-10-20 00:20:13.599 - error: modbus.0 Socket Error
2019-10-20 00:20:13.600 - error: modbus.0 Client in error state.
2019-10-20 00:20:13.600 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:20:41.172 - info: cloud.0 Trying to connect as system.user.admin
2019-10-20 00:20:41.266 - info: cloud.0 Connection changed: connect
2019-10-20 00:21:17.759 - error: modbus.0 Socket Error
2019-10-20 00:21:17.760 - error: modbus.0 Client in error state.
2019-10-20 00:21:17.761 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:22:16.766 - info: admin.0 successful connection to socket.io from ::ffff:192.168.2.115
2019-10-20 00:22:21.919 - error: modbus.0 Socket Error
2019-10-20 00:22:21.920 - error: modbus.0 Client in error state.
2019-10-20 00:22:21.920 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:23:09.102 - info: host.raspberrypi object change system.adapter.modbus.0
2019-10-20 00:23:09.102 - info: host.raspberrypi stopInstance system.adapter.modbus.0
2019-10-20 00:23:09.103 - info: host.raspberrypi stopInstance system.adapter.modbus.0 killing pid 17079
2019-10-20 00:23:09.164 - info: host.raspberrypi instance system.adapter.modbus.0 terminated with code 156 ()
2019-10-20 00:23:11.294 - info: host.raspberrypi object change system.adapter.modbus.0
2019-10-20 00:23:11.313 - info: host.raspberrypi instance system.adapter.modbus.0 started with pid 546
2019-10-20 00:23:12.470 - info: modbus.0 starting. Version 2.0.9 in /opt/iobroker/node_modules/iobroker.modbus, node: v10.16.3
2019-10-20 00:23:15.015 - info: host.raspberrypi object change system.adapter.modbus.0
2019-10-20 00:23:15.015 - info: host.raspberrypi stopInstance system.adapter.modbus.0
2019-10-20 00:23:15.016 - info: host.raspberrypi stopInstance system.adapter.modbus.0 killing pid 546
2019-10-20 00:23:15.078 - info: host.raspberrypi instance system.adapter.modbus.0 terminated with code 156 ()
2019-10-20 00:23:17.536 - info: host.raspberrypi instance system.adapter.modbus.0 started with pid 748
2019-10-20 00:23:18.646 - info: modbus.0 starting. Version 2.0.9 in /opt/iobroker/node_modules/iobroker.modbus, node: v10.16.3
2019-10-20 00:23:22.162 - error: modbus.0 Socket Error
2019-10-20 00:23:22.165 - error: modbus.0 Client in error state.
2019-10-20 00:23:22.166 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:23:25.081 - info: admin.0 successful connection to socket.io from ::ffff:192.168.2.115
2019-10-20 00:23:26.015 - info: admin.0 successful connection to socket.io from ::ffff:192.168.2.115
2019-10-20 00:24:26.320 - error: modbus.0 Socket Error
2019-10-20 00:24:26.321 - error: modbus.0 Client in error state.
2019-10-20 00:24:26.322 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:25:30.479 - error: modbus.0 Socket Error
2019-10-20 00:25:30.480 - error: modbus.0 Client in error state.
2019-10-20 00:25:30.480 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:26:34.639 - error: modbus.0 Socket Error
2019-10-20 00:26:34.640 - error: modbus.0 Client in error state.
2019-10-20 00:26:34.641 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:27:38.799 - error: modbus.0 Socket Error
2019-10-20 00:27:38.800 - error: modbus.0 Client in error state.
2019-10-20 00:27:38.800 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:28:42.959 - error: modbus.0 Socket Error
2019-10-20 00:28:42.960 - error: modbus.0 Client in error state.
2019-10-20 00:28:42.960 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:29:47.119 - error: modbus.0 Socket Error
2019-10-20 00:29:47.120 - error: modbus.0 Client in error state.
2019-10-20 00:29:47.121 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:30:51.279 - error: modbus.0 Socket Error
2019-10-20 00:30:51.279 - error: modbus.0 Client in error state.
2019-10-20 00:30:51.279 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:31:55.439 - error: modbus.0 Socket Error
2019-10-20 00:31:55.440 - error: modbus.0 Client in error state.
2019-10-20 00:31:55.440 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:32:59.599 - error: modbus.0 Socket Error
2019-10-20 00:32:59.600 - error: modbus.0 Client in error state.
2019-10-20 00:32:59.601 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:34:03.759 - error: modbus.0 Socket Error
2019-10-20 00:34:03.760 - error: modbus.0 Client in error state.
2019-10-20 00:34:03.761 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:35:07.919 - error: modbus.0 Socket Error
2019-10-20 00:35:07.920 - error: modbus.0 Client in error state.
2019-10-20 00:35:07.920 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:35:40.858 - info: info.0 Popup news was read...
2019-10-20 00:36:12.079 - error: modbus.0 Socket Error
2019-10-20 00:36:12.079 - error: modbus.0 Client in error state.
2019-10-20 00:36:12.079 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:37:16.239 - error: modbus.0 Socket Error
2019-10-20 00:37:16.240 - error: modbus.0 Client in error state.
2019-10-20 00:37:16.240 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:38:20.399 - error: modbus.0 Socket Error
2019-10-20 00:38:20.400 - error: modbus.0 Client in error state.
2019-10-20 00:38:20.400 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:39:24.559 - error: modbus.0 Socket Error
2019-10-20 00:39:24.560 - error: modbus.0 Client in error state.
2019-10-20 00:39:24.561 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:40:28.719 - error: modbus.0 Socket Error
2019-10-20 00:40:28.720 - error: modbus.0 Client in error state.
2019-10-20 00:40:28.720 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:41:32.879 - error: modbus.0 Socket Error
2019-10-20 00:41:32.880 - error: modbus.0 Client in error state.
2019-10-20 00:41:32.880 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:42:37.039 - error: modbus.0 Socket Error
2019-10-20 00:42:37.040 - error: modbus.0 Client in error state.
2019-10-20 00:42:37.041 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:43:41.199 - error: modbus.0 Socket Error
2019-10-20 00:43:41.200 - error: modbus.0 Client in error state.
2019-10-20 00:43:41.200 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:44:45.359 - error: modbus.0 Socket Error
2019-10-20 00:44:45.359 - error: modbus.0 Client in error state.
2019-10-20 00:44:45.359 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:45:49.519 - error: modbus.0 Socket Error
2019-10-20 00:45:49.520 - error: modbus.0 Client in error state.
2019-10-20 00:45:49.520 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:46:53.679 - error: modbus.0 Socket Error
2019-10-20 00:46:53.680 - error: modbus.0 Client in error state.
2019-10-20 00:46:53.680 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:47:57.839 - error: modbus.0 Socket Error
2019-10-20 00:47:57.840 - error: modbus.0 Client in error state.
2019-10-20 00:47:57.840 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:49:01.999 - error: modbus.0 Socket Error
2019-10-20 00:49:02.000 - error: modbus.0 Client in error state.
2019-10-20 00:49:02.001 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:50:06.159 - error: modbus.0 Socket Error
2019-10-20 00:50:06.160 - error: modbus.0 Client in error state.
2019-10-20 00:50:06.161 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:51:10.319 - error: modbus.0 Socket Error
2019-10-20 00:51:10.319 - error: modbus.0 Client in error state.
2019-10-20 00:51:10.319 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:52:14.479 - error: modbus.0 Socket Error
2019-10-20 00:52:14.480 - error: modbus.0 Client in error state.
2019-10-20 00:52:14.480 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:53:18.639 - error: modbus.0 Socket Error
2019-10-20 00:53:18.639 - error: modbus.0 Client in error state.
2019-10-20 00:53:18.639 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:54:22.799 - error: modbus.0 Socket Error
2019-10-20 00:54:22.800 - error: modbus.0 Client in error state.
2019-10-20 00:54:22.801 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:55:26.959 - error: modbus.0 Socket Error
2019-10-20 00:55:26.960 - error: modbus.0 Client in error state.
2019-10-20 00:55:26.960 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:56:31.119 - error: modbus.0 Socket Error
2019-10-20 00:56:31.120 - error: modbus.0 Client in error state.
2019-10-20 00:56:31.121 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:57:35.279 - error: modbus.0 Socket Error
2019-10-20 00:57:35.280 - error: modbus.0 Client in error state.
2019-10-20 00:57:35.281 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:58:39.439 - error: modbus.0 Socket Error
2019-10-20 00:58:39.440 - error: modbus.0 Client in error state.
2019-10-20 00:58:39.440 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 00:59:43.599 - error: modbus.0 Socket Error
2019-10-20 00:59:43.600 - error: modbus.0 Client in error state.
2019-10-20 00:59:43.601 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 01:00:47.759 - error: modbus.0 Socket Error
2019-10-20 01:00:47.760 - error: modbus.0 Client in error state.
2019-10-20 01:00:47.760 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 01:01:51.919 - error: modbus.0 Socket Error
2019-10-20 01:01:51.919 - error: modbus.0 Client in error state.
2019-10-20 01:01:51.921 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 01:02:56.079 - error: modbus.0 Socket Error
2019-10-20 01:02:56.080 - error: modbus.0 Client in error state.
2019-10-20 01:02:56.080 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 01:04:00.239 - error: modbus.0 Socket Error
2019-10-20 01:04:00.239 - error: modbus.0 Client in error state.
2019-10-20 01:04:00.239 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 01:05:04.400 - error: modbus.0 Socket Error
2019-10-20 01:05:04.401 - error: modbus.0 Client in error state.
2019-10-20 01:05:04.402 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 01:05:40.862 - info: info.0 Popup news was read...
2019-10-20 01:06:08.559 - error: modbus.0 Socket Error
2019-10-20 01:06:08.559 - error: modbus.0 Client in error state.
2019-10-20 01:06:08.560 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 01:07:12.719 - error: modbus.0 Socket Error
2019-10-20 01:07:12.719 - error: modbus.0 Client in error state.
2019-10-20 01:07:12.720 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}
2019-10-20 01:08:16.879 - error: modbus.0 Socket Error
2019-10-20 01:08:16.879 - error: modbus.0 Client in error state.
2019-10-20 01:08:16.881 - warn: modbus.0 On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.2.122","port":502}

Systemdata	Bitte Ausfüllen
Hardwaresystem:	NUC/Pi3/etc.
Arbeitsspeicher:	1GB
Festplattenart:	SD-Karte/SSD/HDD
Betriebssystem:	Ubuntu/Windows/Mac
Node-Version:	v10.16.3
Nodejs-Version:	8.16.2
NPM-Version:	6.9.0
Installationsart:	Skript/Manuell
Image genutzt:	Ja/Nein
Ort/Name der Imagedatei:	Link

Moin,
habe anscheinend das gleiche Problem. Wie habt ihr das genau gelöst?

Gruß
Daniel