Vielen Dank für die Markierung. Ich hab meine Profileinstellungen auch optimiert, so dass ich nun auch eine E-Mail bekomme...
Hab aber den Beitrag auf Facebook gesehen und würde gerne kommen, wenn noch Platz da ist.

Vielen Dank für die Markierung. Ich hab meine Profileinstellungen auch optimiert, so dass ich nun auch eine E-Mail bekomme...
Hab aber den Beitrag auf Facebook gesehen und würde gerne kommen, wenn noch Platz da ist.

Ja, ich hätte im Forum suchen können und ja, ich hätte mit Sicherheit auch irgendwann das hier gefunden:

https://github.com/ioBroker/ioBroker.zigbee/issues/1838

Aber ein kurzer Hinweis auf das Problem, oder wenigstens die Info, dass man selbst suchen muss weil es schon bekannt ist, wäre halt auch nett gewesen...

Auch gut wäre es gewesen, solche Wichtigen Informationen auch in den Releasenotes der Adapter zu schreiben. Dann bekommt jeder beim Updaten des Adapters mit das man was anpassen muss wenn man diese Schalter hat.
Dafür gibt es doch diese Funktion beim Updateprozess?
Ich denke sehr viele User haben diese Buttons und jeder muss sich für die Lösung auf die Suche machen... Das ist doch nicht sehr Enduserfreundlich.

RasputinBerry created this issue in ioBroker/ioBroker.zigbee

closed Zigbee 1.8.23 Problem mit Switch WXKG01LM #1838

@arteck sagte in ZigBee-Probleme beim Upgrade des Adapters:

die da währen ??

Wie gesagt, es wird nur msg_from_zigbee und link_quality upgedatet. Die Datenpunkte wie click und double_click bekommen kein Update.

Mit dem ZigBee Adapter 1.8.16 klappt das alles noch wunderbar, aber nach dem Upgrade auf 1.8.23 habe ich diese Probleme.

Ich hab meinen ZigBee Adapter nun auf die neuste Z-Stack-Firmware upgedatet und leider habe ich immer noch die gleichen Probleme.

Beim Klick auf einen Button ändert sich msg_from_zigbee und auch link_quality

msg_from_zigbee:

{"type":"attributeReport","data":{"onOff":1},"linkquality":98,"groupID":0,"cluster":"genOnOff","meta":{"zclTransactionSequenceNumber":20,"manufacturerCode":null,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

Das Log aus ioBroker:

zigbee.0 2023-09-04 10:29:25.325	warn	DeviceAvailability:Failed to ping 0x0017880104fcd5ca LCT012
zigbee.0 2023-09-04 10:29:25.141	warn	DeviceAvailability:Failed to ping 0x842e14fffe0fc33f TS0121
zigbee.0 2023-09-04 10:29:01.988	info	debug devices set to []
zigbee.0 2023-09-04 10:29:01.649	info	Zigbee started
zigbee.0 2023-09-04 10:29:01.648	info	0x00158d000277042b (addr 56970): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0 2023-09-04 10:29:01.647	info	0x00158d00027976ab (addr 21387): MFKZQ01LM - Xiaomi Mi/Aqara smart home cube (EndDevice)
zigbee.0 2023-09-04 10:29:01.629	info	0x00158d00045122b6 (addr 35579): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
zigbee.0 2023-09-04 10:29:01.628	info	0x842e14fffe0fc33f (addr 12915): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)
zigbee.0 2023-09-04 10:29:01.627	info	0x00158d0001e5109b (addr 14680): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
zigbee.0 2023-09-04 10:29:01.626	info	0x00158d0002743621 (addr 12185): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
zigbee.0 2023-09-04 10:29:01.621	info	0x0017880104fcd5ca (addr 6499): 9290012573A - Philips Hue white and color ambiance E26/E27/E14 (Router)
zigbee.0 2023-09-04 10:29:01.619	info	0x0017880106367933 (addr 48088): 324131092621 - Philips Hue dimmer switch (EndDevice)
zigbee.0 2023-09-04 10:29:01.599	info	0x00158d000224609c (addr 12725): RTCGQ01LM - Xiaomi MiJia human body movement sensor (EndDevice)
zigbee.0 2023-09-04 10:29:01.598	info	0x00158d0001bc51cc (addr 41693): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0 2023-09-04 10:29:01.592	info	0x00158d000278d4a8 (addr 866): MFKZQ01LM - Xiaomi Mi/Aqara smart home cube (EndDevice)
zigbee.0 2023-09-04 10:29:01.591	info	0x00158d00031b2cf5 (addr 48539): DJT11LM - Xiaomi Aqara vibration sensor (EndDevice)
zigbee.0 2023-09-04 10:29:01.590	info	0x00158d00023f502e (addr 60929): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
zigbee.0 2023-09-04 10:29:01.582	info	0x84182600000eecef (addr 11312): AB3257001NJ - OSRAM Smart+ plug (Router)
zigbee.0 2023-09-04 10:29:01.582	info	0x00158d000271a814 (addr 19595): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
zigbee.0 2023-09-04 10:29:01.582	info	0x00158d00025315ea (addr 17346): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
zigbee.0 2023-09-04 10:29:01.581	info	0x00158d00024e344e (addr 3266): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
zigbee.0 2023-09-04 10:29:01.581	info	0x00158d0002157e4d (addr 53299): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
zigbee.0 2023-09-04 10:29:01.580	info	0x00158d0002c3997b (addr 29406): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
zigbee.0 2023-09-04 10:29:01.572	info	0x00158d0002c4105b (addr 14157): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0 2023-09-04 10:29:01.572	info	0x00158d000249f83a (addr 46097): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
zigbee.0 2023-09-04 10:29:01.571	info	0x00158d0002772e48 (addr 17364): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
zigbee.0 2023-09-04 10:29:01.570	info	0x00158d0002277ce4 (addr 9926): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
zigbee.0 2023-09-04 10:29:01.570	info	0x84182600000eb797 (addr 16997): AB3257001NJ - OSRAM Smart+ plug (Router)
zigbee.0 2023-09-04 10:29:01.552	info	0x00158d0002562ee4 (addr 22907): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0 2023-09-04 10:29:01.552	info	0x7cb03eaa0a02d6ae (addr 49407): AB3257001NJ - OSRAM Smart+ plug (Router)
zigbee.0 2023-09-04 10:29:01.551	info	0x00158d000275ca03 (addr 866): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
zigbee.0 2023-09-04 10:29:01.550	info	0x00158d00016bf654 (addr 49341): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0 2023-09-04 10:29:01.550	info	0x00158d0002732cfe (addr 14966): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
zigbee.0 2023-09-04 10:29:01.549	info	0x00158d00016bf740 (addr 8159): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0 2023-09-04 10:29:01.548	info	0x00158d00016be014 (addr 14082): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0 2023-09-04 10:29:01.548	info	0x00158d0003599f42 (addr 25628): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0 2023-09-04 10:29:01.532	info	0x00158d00035557aa (addr 41157): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0 2023-09-04 10:29:01.200	info	Currently 33 devices are joined:
zigbee.0 2023-09-04 10:29:01.188	info	--> transmitPower : high
zigbee.0 2023-09-04 10:29:01.176	info	Unable to disable LED, unsupported function.
zigbee.0 2023-09-04 10:29:01.169	info	Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20230507}}
zigbee.0 2023-09-04 10:28:59.882	info	Installed Version: iobroker.zigbee@1.8.23
zigbee.0 2023-09-04 10:28:59.122	info	Starting Zigbee npm ...
zigbee.0 2023-09-04 10:28:59.121	info	delete old Backup files. keep only last 10
zigbee.0 2023-09-04 10:28:58.979	info	starting. Version 1.8.23 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.1, js-controller: 4.0.24

Mein ioBroker diag summary:

======================= SUMMARY =======================
		     v.2023-04-16


Operatingsystem: 	Debian GNU/Linux 12 (bookworm)
Kernel: 		5.15.108-1-pve
Installation: 		lxc
Timezone: 		Europe/Berlin (CEST, +0200)
User-ID: 		1000
X-Server: 		false
Boot Target: 		graphical.target

Pending OS-Updates: 	0
Pending iob updates: 	0

Nodejs-Installation: 	/usr/bin/nodejs 	v18.17.1
			/usr/bin/node 		v18.17.1
			/usr/bin/npm 		9.6.7
			/usr/bin/npx 		9.6.7

Recommended versions are nodejs 18.x.y and npm 9.x.y
Your nodejs installation is correct

MEMORY: 
               total        used        free      shared  buff/cache   available
Mem:            4.3G        3.3G        447M        118K        513M        960M
Swap:           4.3G        194M        4.1G
Total:          8.6G        3.5G        4.5G

Active iob-Instances: 	42
Active repo(s): stable

ioBroker Core: 		js-controller 		4.0.24
			admin 			6.8.0

ioBroker Status: 	iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Status admin and web instance:
+ system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.admin.1                  : admin                 : iobroker2                                -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.web.0                    : web                   : iobroker                                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin

Objects: 		15603
States: 		13736

Size of iob-Database:

19M	/opt/iobroker/iobroker-data/objects.jsonl
8.0M	/opt/iobroker/iobroker-data/states.jsonl



=================== END OF SUMMARY ====================

Was kann ich noch machen?

@thomas-braun sagte in ZigBee-Probleme beim Upgrade des Adapters:

Die Firmware des Sticks würde ich mal erneuern.

Ich hatte damals irgendwie im Kopf, dass man danach alle Devices neu anlernen muss, und darum hab ich das nie gemacht.
Stimmt das nicht?

@arteck sagte in ZigBee-Probleme beim Upgrade des Adapters:

0x0000000000000000

Habe ich gemacht. Es war diese Zeile hier:

{"id":39,"type":"EndDevice","ieeeAddr":"0x0000000000000000","nwkAddr":37984,"manufId":4151,"epList":[],"endpoints":{},"interviewCompleted":false,"meta":{},"lastSeen":1665473093519,"defaultSendRequestWhen":"immediate"}

Danach habe ich den ZigBee Adapter neugestartet.

Ich weiß nicht ob es vorher auch schon war, aber in den ZigBee-Objekten in ioBroker sehe ich Aktionen.
Wenn ich einen Switch lange drücke, wird das Feld long_press nicht auf true gesetzt, aber z.B. msg_from_zigbee auf:

{"type":"attributeReport","data":{"onOff":0},"linkquality":9,"groupID":0,"cluster":"genOnOff","meta":{"zclTransactionSequenceNumber":167,"manufacturerCode":null,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

Ich hab eine komplette neuinstallations meines ioBroker-Systems in einen Proxmox Container gemacht.
Dabei habe ich Debian 12 (Bookworm) installiert und node.js 18.x installiert.

Danach habe ich ein Backup von dem alten ioBroker System über die Console eingespielt und später das ZigBee Backup über Backupit.
Danach hat ZigBee funktioniert. Zum Schluss habe ich noch alle Adapter upgedatet und auch ZigBee von der Version 1.8.16 auf 1.8.23.
Seitdem funktioniert Zigbee nicht mehr.
Nach einem Adapterneustart sehe ich folgende Zigbee Ausgaben im Log:

zigbee.0
2023-09-01 15:31:06.465	warn	DeviceAvailability:Failed to ping 0x0017880104fcd5ca LCT012
zigbee.0
2023-09-01 15:31:06.333	warn	DeviceAvailability:Failed to ping 0x842e14fffe0fc33f TS0121
zigbee.0
2023-09-01 15:30:46.096	error	Device 0x0000000000000000 "undefined" not described in statesMapping.
zigbee.0
2023-09-01 15:30:44.200	info	debug devices set to []
zigbee.0
2023-09-01 15:30:43.860	warn	download icon undefined for undefined Device not available. Check your devices.
zigbee.0
2023-09-01 15:30:43.817	info	Zigbee started
zigbee.0
2023-09-01 15:30:43.815	info	0x0000000000000000 (addr 37984): Not supported (model undefined)(EndDevice)
zigbee.0
2023-09-01 15:30:43.815	info	0x00158d000277042b (addr 56970): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0
2023-09-01 15:30:43.815	info	0x00158d00027976ab (addr 21387): MFKZQ01LM - Xiaomi Mi/Aqara smart home cube (EndDevice)
zigbee.0
2023-09-01 15:30:43.800	info	0x00158d00045122b6 (addr 35579): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
zigbee.0
2023-09-01 15:30:43.799	info	0x842e14fffe0fc33f (addr 12915): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)
zigbee.0
2023-09-01 15:30:43.798	info	0x00158d0001e5109b (addr 14680): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
zigbee.0
2023-09-01 15:30:43.798	info	0x00158d0002743621 (addr 12185): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
zigbee.0
2023-09-01 15:30:43.796	info	0x0017880104fcd5ca (addr 6499): 9290012573A - Philips Hue white and color ambiance E26/E27/E14 (Router)
zigbee.0
2023-09-01 15:30:43.795	info	0x0017880106367933 (addr 48088): 324131092621 - Philips Hue dimmer switch (EndDevice)
zigbee.0
2023-09-01 15:30:43.794	info	0x00158d000224609c (addr 12725): RTCGQ01LM - Xiaomi MiJia human body movement sensor (EndDevice)
zigbee.0
2023-09-01 15:30:43.794	info	0x00158d0001bc51cc (addr 41693): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0
2023-09-01 15:30:43.793	info	0x00158d000278d4a8 (addr 866): MFKZQ01LM - Xiaomi Mi/Aqara smart home cube (EndDevice)
zigbee.0
2023-09-01 15:30:43.793	info	0x00158d00031b2cf5 (addr 48539): DJT11LM - Xiaomi Aqara vibration sensor (EndDevice)
zigbee.0
2023-09-01 15:30:43.792	info	0x00158d00023f502e (addr 60929): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
zigbee.0
2023-09-01 15:30:43.792	info	0x84182600000eecef (addr 11312): AB3257001NJ - OSRAM Smart+ plug (Router)
zigbee.0
2023-09-01 15:30:43.791	info	0x00158d000271a814 (addr 19595): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
zigbee.0
2023-09-01 15:30:43.791	info	0x00158d00025315ea (addr 17346): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
zigbee.0
2023-09-01 15:30:43.790	info	0x00158d00024e344e (addr 3266): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
zigbee.0
2023-09-01 15:30:43.790	info	0x00158d0002157e4d (addr 53299): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
zigbee.0
2023-09-01 15:30:43.789	info	0x00158d0002c3997b (addr 29406): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
zigbee.0
2023-09-01 15:30:43.789	info	0x00158d0002c4105b (addr 14157): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0
2023-09-01 15:30:43.788	info	0x00158d000249f83a (addr 46097): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
zigbee.0
2023-09-01 15:30:43.788	info	0x00158d0002772e48 (addr 17364): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
zigbee.0
2023-09-01 15:30:43.787	info	0x00158d0002277ce4 (addr 9926): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
zigbee.0
2023-09-01 15:30:43.787	info	0x84182600000eb797 (addr 16997): AB3257001NJ - OSRAM Smart+ plug (Router)
zigbee.0
2023-09-01 15:30:43.786	info	0x00158d0002562ee4 (addr 22907): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0
2023-09-01 15:30:43.786	info	0x7cb03eaa0a02d6ae (addr 49407): AB3257001NJ - OSRAM Smart+ plug (Router)
zigbee.0
2023-09-01 15:30:43.785	info	0x00158d000275ca03 (addr 866): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
zigbee.0
2023-09-01 15:30:43.784	info	0x00158d00016bf654 (addr 49341): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0
2023-09-01 15:30:43.784	info	0x00158d0002732cfe (addr 14966): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
zigbee.0
2023-09-01 15:30:43.783	info	0x00158d00016bf740 (addr 8159): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0
2023-09-01 15:30:43.782	info	0x00158d00016be014 (addr 14082): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0
2023-09-01 15:30:43.782	info	0x00158d0003599f42 (addr 25628): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0
2023-09-01 15:30:43.778	info	0x00158d00035557aa (addr 41157): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0
2023-09-01 15:30:43.668	info	Currently 34 devices are joined:
zigbee.0
2023-09-01 15:30:43.652	info	--> transmitPower : high
zigbee.0
2023-09-01 15:30:43.640	info	Unable to disable LED, unsupported function.
zigbee.0
2023-09-01 15:30:43.633	info	Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20191106}}
zigbee.0
2023-09-01 15:30:42.195	info	Installed Version: iobroker.zigbee@1.8.23
zigbee.0
2023-09-01 15:30:40.696	info	Starting Zigbee npm ...
zigbee.0
2023-09-01 15:30:40.693	info	delete old Backup files. keep only last 10
zigbee.0
2023-09-01 15:30:40.582	info	starting. Version 1.8.23 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.1, js-controller: 4.0.24

Im ZigBee Adapter sehe ich keine Fehler. Die Adapterwolke baut sich nach so 10-15 Sekunden auf... Alles so wie immer.

Auch habe ich noch einmal das Backitup Backup drüber gespielt und konnte noch mal verifizieren, dass es mit ZigBee 1.8.16 funktioniert und nach einem erneuten upgrade auf 1.8.23 wieder nicht.

======================= SUMMARY =======================
		     v.2023-04-16


/home/iobroker/.diag.sh: line 304: lsb_release: command not found
Operatingsystem: 
Kernel: 		5.15.108-1-pve
Installation: 		lxc
Timezone: 		Europe/Berlin (CEST, +0200)
User-ID: 		1000
X-Server: 		false
Boot Target: 		graphical.target

Pending OS-Updates: 	0
Pending iob updates: 	0

Nodejs-Installation: 	/usr/bin/nodejs 	v18.17.1
			/usr/bin/node 		v18.17.1
			/usr/bin/npm 		9.6.7
			/usr/bin/npx 		9.6.7

Recommended versions are nodejs 18.x.y and npm 9.x.y
Your nodejs installation is correct

MEMORY: 
               total        used        free      shared  buff/cache   available
Mem:            4.3G        3.1G        222M        110K        988M        1.2G
Swap:           4.3G         24K        4.3G
Total:          8.6G        3.1G        4.5G

Active iob-Instances: 	42
Active repo(s): stable

ioBroker Core: 		js-controller 		4.0.24
			admin 			6.8.0

ioBroker Status: 	iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Status admin and web instance:
+ system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.admin.1                  : admin                 : iobroker2                                -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.web.0                    : web                   : iobroker                                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin

Objects: 		15475
States: 		13616

Size of iob-Database:

24M	/opt/iobroker/iobroker-data/objects.jsonl
5.0M	/opt/iobroker/iobroker-data/states.jsonl



=================== END OF SUMMARY ====================

Leider habe ich nach der Neuinstallation noch den ein oder anderen kleinen Fehler:

In der Logdatei taucht ab und zu dies hier auf:

admin.0
2023-09-01 15:38:57.469	error	Not exists
admin.0
2023-09-01 15:38:31.288	error	Not exists
admin.0
2023-09-01 15:38:26.218	error	Not exists
admin.0
2023-09-01 15:37:49.434	error	Not exists

Und auch Vis scheint nicht zu funktionieren:

http://iobroker:8082/vis/index.html

File index.html not found: {}

Hoffe mir kann jemand helfen.

Ich hab jetzt eine Neuinstallation auf Debian Bookworm gemacht und bin gerade dabei ioBroker wieder komplett an's Laufen zu bekommen.
Hat sich also erledigt.

@djmarc75 Wenn es keine anderen Dinge mehr gibt die ich machen kann, dann muss ich den Container zurückspielen und eine Neuinstallation die Tage machen.

Aber vielleicht hat noch jemand eine Idee.

@crunchip

@djmarc75 sagte in Troubleshooting NodeJS update:

Warum nicht auf Bullseye ? Welche dubiose Anleitung hast Du verwendet ?

Ja, leider habe ich ein bisschen verschlafen das System aktuell zu halten und hole das natürlich nach.
Von Stretch --> Buster --> Bullseye

Das letzte Upgrade wollte ich erst machen wenn ioBroker wieder läuft.

Die angepinnte News mit meinem Problem habe ich natürlich nicht gesehen, aber trotzdem habe ich ja den Fixer mehrer Male gestartet und das hat leider nichts gebraucht.

Ich habe gerade versucht die aktuellste Version so herunterzuladen

curl -fsL https://iobroker.net/fix.sh | bash -

Aber das Ergebnis bei einem Adapterupgradeversuch ist immer noch:

tobias@iobroker:/opt/iobroker$ iob upgrade --debug

This upgrade of "yahka" will introduce the following changes:
==========================================================================
-> 1.0.3:
Corrected empty device list with rebuild

-> 1.0.1:
we ensured controller 5 compatibility
Formatting
==========================================================================

BE CAREFUL: THIS IS A MAJOR UPGRADE, WHICH WILL MOST LIKELY INTRODUCE BREAKING CHANGES!
Would you like to upgrade yahka from @0.17.0 to @1.0.3 now? [(y)es, (n)o]: n
No upgrade of "yahka" desired.

This upgrade of "ping" will introduce the following changes:
==========================================================================
-> 1.6.2:
Handling of state updates causing crashes with js-controller 5 has been corrected. (Issue #106)
Trailing spaces are now removed from ip address and name. Trailing spaces blocked correct operation. (Issue #98)
Added json config
Added different intervals for online and offline devices
implemented export/import of devices

-> 1.6.0:
Handling of state updates causing crashes with js-controller 5 has been corrected. (Issue #106)
Trailing spaces are now removed from ip address and name. Trailing spaces blocked correct operation. (Issue #98)
Added json config
==========================================================================

Would you like to upgrade ping from @1.5.3 to @1.6.2 now? [(y)es, (n)o]: y
Update ping from @1.5.3 to @1.6.2
NPM version: 9.6.7
Installing iobroker.ping@1.6.2... (System call)
npm WARN skipping integrity check for git dependency ssh://git@github.com/noopkat/browser-serialport.git 
npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
npm WARN deprecated topo@3.0.3: This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated babel@6.23.0: In 6.x, the babel package has been deprecated in favor of babel-cli. Check https://opencollective.com/babel to support the Babel maintainers
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated hoek@6.1.3: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
npm WARN deprecated circular-json@0.5.9: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated appdirectory@0.1.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
npm WARN deprecated jscs-preset-wikimedia@1.0.1: No longer maintained. We recomment migrating to ESLint with eslint-config-wikimedia.
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated nomnom@1.8.1: Package no longer supported. Contact support@npmjs.com for more info.
npm WARN deprecated uuid@2.0.3: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated joi@14.3.1: This module has moved and is now available at @hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated jscs@3.0.7: JSCS has merged with ESLint! See - https://medium.com/@markelog/jscs-end-of-the-line-bc9bf0b3fdb2
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN cleanup Failed to remove some directories [
npm WARN cleanup   [
npm WARN cleanup     '/opt/iobroker/node_modules/cpu-features',
npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/cpu-features'] {
npm WARN cleanup       errno: -39,
npm WARN cleanup       code: 'ENOTEMPTY',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: '/opt/iobroker/node_modules/cpu-features'
npm WARN cleanup     }
npm WARN cleanup   ],
npm WARN cleanup   [
npm WARN cleanup     '/opt/iobroker/node_modules/cpu-features',
npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/cpu-features'] {
npm WARN cleanup       errno: -39,
npm WARN cleanup       code: 'ENOTEMPTY',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: '/opt/iobroker/node_modules/cpu-features'
npm WARN cleanup     }
npm WARN cleanup   ]
npm WARN cleanup ]
npm ERR! code 1
npm ERR! path /opt/iobroker/node_modules/@serialport/bindings
npm ERR! command failed
npm ERR! command sh -c prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
npm ERR! make: Verzeichnis „/opt/iobroker/node_modules/@serialport/bindings/build“ wird betreten
npm ERR!   CXX(target) Release/obj.target/bindings/src/serialport.o
npm ERR! make: Verzeichnis „/opt/iobroker/node_modules/@serialport/bindings/build“ wird verlassen
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp@9.3.1
npm ERR! gyp info using node@18.17.1 | linux | x64
npm ERR! gyp info find Python using Python version 3.7.3 found at "/usr/bin/python3"
npm ERR! gyp info spawn /usr/bin/python3
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   '/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
npm ERR! gyp info spawn args   'binding.gyp',
npm ERR! gyp info spawn args   '-f',
npm ERR! gyp info spawn args   'make',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/@serialport/bindings/build/config.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/home/iobroker/.cache/node-gyp/18.17.1/include/node/common.gypi',
npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
npm ERR! gyp info spawn args   '-Dvisibility=default',
npm ERR! gyp info spawn args   '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.17.1',
npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',
npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.17.1/<(target_arch)/node.lib',
npm ERR! gyp info spawn args   '-Dmodule_root_dir=/opt/iobroker/node_modules/@serialport/bindings',
npm ERR! gyp info spawn args   '-Dnode_engine=v8',
npm ERR! gyp info spawn args   '--depth=.',
npm ERR! gyp info spawn args   '--no-parallel',
npm ERR! gyp info spawn args   '--generator-output',
npm ERR! gyp info spawn args   'build',
npm ERR! gyp info spawn args   '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! gyp info spawn make
npm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/serialport.cpp:78:69: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
npm ERR!    uv_queue_work(uv_default_loop(), req, EIO_Open, (uv_after_work_cb)EIO_AfterOpen);
npm ERR!                                                                      ^~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/serialport.cpp:135:71: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
npm ERR!    uv_queue_work(uv_default_loop(), req, EIO_Update, (uv_after_work_cb)EIO_AfterUpdate);
npm ERR!                                                                        ^~~~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Close(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/serialport.cpp:175:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
npm ERR!    uv_queue_work(uv_default_loop(), req, EIO_Close, (uv_after_work_cb)EIO_AfterClose);
npm ERR!                                                                       ^~~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Flush(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/serialport.cpp:215:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
npm ERR!    uv_queue_work(uv_default_loop(), req, EIO_Flush, (uv_after_work_cb)EIO_AfterFlush);
npm ERR!                                                                       ^~~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/serialport.cpp:270:68: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
npm ERR!    uv_queue_work(uv_default_loop(), req, EIO_Set, (uv_after_work_cb)EIO_AfterSet);
npm ERR!                                                                     ^~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Get(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/serialport.cpp:314:68: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
npm ERR!    uv_queue_work(uv_default_loop(), req, EIO_Get, (uv_after_work_cb)EIO_AfterGet);
npm ERR!                                                                     ^~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: In function ‘void EIO_AfterGet(uv_work_t*)’:
npm ERR! ../src/serialport.cpp:329:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’
npm ERR!      results->Set(Nan::New<v8::String>("cts").ToLocalChecked(), Nan::New<v8::Boolean>(data->cts));
npm ERR!                                                                                                 ^
npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:13,
npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,
npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:73,
npm ERR!                  from ../../../nan/nan.h:60,
npm ERR!                  from ../src/./serialport.h:6,
npm ERR!                  from ../src/serialport.cpp:1:
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’
npm ERR!    V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,
npm ERR!                                      ^~~
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note:   candidate expects 3 arguments, 2 provided
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’
npm ERR!    V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
npm ERR!                                      ^~~
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note:   candidate expects 3 arguments, 2 provided
npm ERR! ../src/serialport.cpp:330:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’
npm ERR!      results->Set(Nan::New<v8::String>("dsr").ToLocalChecked(), Nan::New<v8::Boolean>(data->dsr));
npm ERR!                                                                                                 ^
npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:13,
npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,
npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:73,
npm ERR!                  from ../../../nan/nan.h:60,
npm ERR!                  from ../src/./serialport.h:6,
npm ERR!                  from ../src/serialport.cpp:1:
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’
npm ERR!    V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,
npm ERR!                                      ^~~
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note:   candidate expects 3 arguments, 2 provided
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’
npm ERR!    V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
npm ERR!                                      ^~~
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note:   candidate expects 3 arguments, 2 provided
npm ERR! ../src/serialport.cpp:331:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’
npm ERR!      results->Set(Nan::New<v8::String>("dcd").ToLocalChecked(), Nan::New<v8::Boolean>(data->dcd));
npm ERR!                                                                                                 ^
npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:13,
npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,
npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:73,
npm ERR!                  from ../../../nan/nan.h:60,
npm ERR!                  from ../src/./serialport.h:6,
npm ERR!                  from ../src/serialport.cpp:1:
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’
npm ERR!    V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,
npm ERR!                                      ^~~
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note:   candidate expects 3 arguments, 2 provided
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’
npm ERR!    V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
npm ERR!                                      ^~~
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note:   candidate expects 3 arguments, 2 provided
npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE GetBaudRate(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/serialport.cpp:363:76: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
npm ERR!    uv_queue_work(uv_default_loop(), req, EIO_GetBaudRate, (uv_after_work_cb)EIO_AfterGetBaudRate);
npm ERR!                                                                             ^~~~~~~~~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: In function ‘void EIO_AfterGetBaudRate(uv_work_t*)’:
npm ERR! ../src/serialport.cpp:378:106: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::IntegerFactory<v8::Integer>::return_t)’
npm ERR!      results->Set(Nan::New<v8::String>("baudRate").ToLocalChecked(), Nan::New<v8::Integer>(data->baudRate));
npm ERR!                                                                                                           ^
npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:13,
npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,
npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:73,
npm ERR!                  from ../../../nan/nan.h:60,
npm ERR!                  from ../src/./serialport.h:6,
npm ERR!                  from ../src/serialport.cpp:1:
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’
npm ERR!    V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,
npm ERR!                                      ^~~
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note:   candidate expects 3 arguments, 2 provided
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’
npm ERR!    V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
npm ERR!                                      ^~~
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note:   candidate expects 3 arguments, 2 provided
npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Drain(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/serialport.cpp:409:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
npm ERR!    uv_queue_work(uv_default_loop(), req, EIO_Drain, (uv_after_work_cb)EIO_AfterDrain);
npm ERR!                                                                       ^~~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: At global scope:
npm ERR! ../src/serialport.cpp:430:28: warning: unnecessary parentheses in declaration of ‘ToParityEnum’ [-Wparentheses]
npm ERR!  SerialPortParity NAN_INLINE(ToParityEnum(const v8::Local<v8::String>& v8str)) {
npm ERR!                             ^
npm ERR! ../src/serialport.cpp:449:30: warning: unnecessary parentheses in declaration of ‘ToStopBitEnum’ [-Wparentheses]
npm ERR!  SerialPortStopBits NAN_INLINE(ToStopBitEnum(double stopBits)) {
npm ERR!                               ^
npm ERR! In file included from ../../../nan/nan.h:60,
npm ERR!                  from ../src/./serialport.h:6,
npm ERR!                  from ../src/serialport.cpp:1:
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:1014:43: warning: cast between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
npm ERR!        (node::addon_register_func) (regfunc),                          \
npm ERR!                                            ^
npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:1048:3: note: in expansion of macro ‘NODE_MODULE_X’
npm ERR!    NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
npm ERR!    ^~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp:483:1: note: in expansion of macro ‘NODE_MODULE’
npm ERR!  NODE_MODULE(serialport, init);
npm ERR!  ^~~~~~~~~~~
npm ERR! make: *** [bindings.target.mk:116: Release/obj.target/bindings/src/serialport.o] Fehler 1
npm ERR! gyp ERR! build error 
npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2
npm ERR! gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:203:23)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:514:28)
npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
npm ERR! gyp ERR! System Linux 5.15.108-1-pve
npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/@serialport/bindings
npm ERR! gyp ERR! node -v v18.17.1
npm ERR! gyp ERR! node-gyp -v v9.3.1
npm ERR! gyp ERR! not ok

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-08-31T13_46_32_906Z-debug-0.log
upload [4] ping.admin /opt/iobroker/node_modules/iobroker.ping/admin/img/info-big.png img/info-big.png image/png
upload [3] ping.admin /opt/iobroker/node_modules/iobroker.ping/admin/index.html index.html text/html
upload [2] ping.admin /opt/iobroker/node_modules/iobroker.ping/admin/index_m.html index_m.html text/html
upload [1] ping.admin /opt/iobroker/node_modules/iobroker.ping/admin/ping.png ping.png image/png
upload [0] ping.admin /opt/iobroker/node_modules/iobroker.ping/admin/words.js words.js application/javascript

Yahka habe ich erst einmal übersprungen, da ich denke dass der Ping Adapter die wenigsten Probleme machen sollte.

mikeal created this issue in request/request

open Request’s Past, Present and Future #3142

mikeal created this issue in request/request

open Request’s Past, Present and Future #3142

Qix- created this issue in visionmedia/debug

closed ReDos Vulnerability Regression Visibility Notice #797

mikeal created this issue in request/request

open Request’s Past, Present and Future #3142