Alpha Test js-controller 5.0

Feuersturm

@apollon77 Schreibst du hier, wenn es eine neue Version vom js-controller gibt die getestet werden soll?

e-i-k-e

Beeindruckend wie schnell das update auf den js-controller 5.0 durchgeführt worden ist.

Ich habe auch das bekannte Problem mit dem log und der milight-smart-light Adapter funktioniert nicht wirklich.
https://github.com/Steiger04/ioBroker.milight-smart-light/issues/58

Ansonsten läuft alles. :+1:

apollon77

@feuersturm Na klar,

e-i-k-e

Nach einem erneuten Neustart von ioBroker, will mein Yeelight Adapter plötzlich auch nicht mehr.

host.ioBroker-Rock
2023-04-02 21:33:58.543	warn	Do not restart adapter system.adapter.yeelight-2.0 because restart loop detected
host.ioBroker-Rock
2023-04-02 21:33:58.543	info	Restart adapter system.adapter.yeelight-2.0 because enabled
host.ioBroker-Rock
2023-04-02 21:33:58.543	error	instance system.adapter.yeelight-2.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.ioBroker-Rock
2023-04-02 21:33:58.542	error	Caught by controller[0]: at TCP.<anonymous> (node:net:322:12)
host.ioBroker-Rock
2023-04-02 21:33:58.542	error	Caught by controller[0]: at Socket.emit (node:domain:489:12)
host.ioBroker-Rock
2023-04-02 21:33:58.542	error	Caught by controller[0]: at Socket.emit (node:events:525:35)
host.ioBroker-Rock
2023-04-02 21:33:58.541	error	Caught by controller[0]: at Object.onceWrapper (node:events:628:26)
host.ioBroker-Rock
2023-04-02 21:33:58.541	error	Caught by controller[0]: at Socket.onClose (node:net:911:10)
host.ioBroker-Rock
2023-04-02 21:33:58.541	error	Caught by controller[0]: at new NodeError (node:internal/errors:399:5)
host.ioBroker-Rock
2023-04-02 21:33:58.540	error	Caught by controller[0]: Error: Socket closed before the connection was established
host.ioBroker-Rock
2023-04-02 21:33:58.539	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

yeelight-2.0
2023-04-02 21:33:58.409	info	terminating

yeelight-2.0
2023-04-02 21:33:57.906	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

yeelight-2.0
2023-04-02 21:33:57.904	info	terminating

yeelight-2.0
2023-04-02 21:33:57.903	info	cleaned everything up...

yeelight-2.0
2023-04-02 21:33:57.875	error	Exception-Code: ERR_SOCKET_CLOSED_BEFORE_CONNECTION: Socket closed before the connection was established

yeelight-2.0
2023-04-02 21:33:57.874	error	Error: Socket closed before the connection was established at new NodeError (node:internal/errors:399:5) at Socket.onClose (node:net:911:10) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:525:35) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:322:12)

yeelight-2.0
2023-04-02 21:33:57.873	error	unhandled promise rejection: Socket closed before the connection was established

yeelight-2.0
2023-04-02 21:33:57.871	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

yeelight-2.0
2023-04-02 21:33:54.669	info	starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.yeelight-2, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230330-e0b409fe
host.ioBroker-Rock
2023-04-02 21:33:50.899	info	instance system.adapter.yeelight-2.0 started with pid 23551

alexa2.0
2023-04-02 21:33:50.136	info	Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
host.ioBroker-Rock
2023-04-02 21:33:20.706	info	Restart adapter system.adapter.yeelight-2.0 because enabled
host.ioBroker-Rock
2023-04-02 21:33:20.705	error	instance system.adapter.yeelight-2.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.ioBroker-Rock
2023-04-02 21:33:20.705	error	Caught by controller[1]: at TCP.<anonymous> (node:net:322:12)
host.ioBroker-Rock
2023-04-02 21:33:20.704	error	Caught by controller[1]: at Socket.emit (node:domain:489:12)
host.ioBroker-Rock
2023-04-02 21:33:20.704	error	Caught by controller[1]: at Socket.emit (node:events:525:35)
host.ioBroker-Rock
2023-04-02 21:33:20.701	error	Caught by controller[1]: at Object.onceWrapper (node:events:628:26)
host.ioBroker-Rock
2023-04-02 21:33:20.701	error	Caught by controller[1]: at Socket.onClose (node:net:911:10)
host.ioBroker-Rock
2023-04-02 21:33:20.701	error	Caught by controller[1]: at new NodeError (node:internal/errors:399:5)
host.ioBroker-Rock
2023-04-02 21:33:20.700	error	Caught by controller[1]: Error: Socket closed before the connection was established
host.ioBroker-Rock
2023-04-02 21:33:20.699	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

yeelight-2.0
2023-04-02 21:33:20.586	info	terminating

yeelight-2.0
2023-04-02 21:33:20.084	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

yeelight-2.0
2023-04-02 21:33:20.082	info	terminating

yeelight-2.0
2023-04-02 21:33:20.081	info	cleaned everything up...

yeelight-2.0
2023-04-02 21:33:20.051	error	Exception-Code: ERR_SOCKET_CLOSED_BEFORE_CONNECTION: Socket closed before the connection was established

yeelight-2.0
2023-04-02 21:33:20.049	error	Error: Socket closed before the connection was established at new NodeError (node:internal/errors:399:5) at Socket.onClose (node:net:911:10) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:525:35) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:322:12)

yeelight-2.0
2023-04-02 21:33:20.048	error	unhandled promise rejection: Socket closed before the connection was established

yeelight-2.0
2023-04-02 21:33:20.047	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

yeelight-2.0
2023-04-02 21:33:16.855	info	starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.yeelight-2, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230330-e0b409fe
host.ioBroker-Rock
2023-04-02 21:33:13.855	info	instance system.adapter.yeelight-2.0 started with pid 23534

apollon77

Alpha (@next) updated to 5.0.1-alpha.0-20230403-fd495c2e

Fixes missing logging object when logTransporter is used (e.g. Admin)
Fixes other issue with logTransporter (e.g. Admin) - events should now stream again in Admin
Fixed Compact group initialization
Fixes Binary/Text detection in writeFile
Fixes sendToHost (all) command

Laut aktuellem stand sind damit alle gemeldete und auf den controller zurückzuführeden Themen behoben. Das Windows Kodi/git-npm-Fehler Thema muss man noch genauer untersuchen denke ich.

Gaspode

@apollon77
Die Missing Logging object Warnung tritt hier nicht mehr auf
Admin Log wird automatisch aktualisiert (wobei das bei mir ja auch mit der Vorgängerversion ging)

Sonst ist mir erst mal nix aufgefallen, ~~nur ein alter bekannter unter Windows ist wieder da (das liegt aber am aktualisierten JavaScript Adapter): Der Font für die Symbole im Suchfenster ist kaputt:~~

~~Fehlermeldung im Log~~

javascript.0	2023-04-03 12:43:30.883	error	Cannot patch font: Error: Parameter "data" needs to be a Buffer but type "object" has been passed

Edit: OK, vergiss es, hat Bluefox bereits (wieder) in GIT gefixt.

e-i-k-e

Danke für das Update.
Das Problem mit Yeelight besteht weiterhin.

host.ioBroker-Rock
2023-04-03 21:29:21.231	info	Restart adapter system.adapter.yeelight-2.0 because enabled
host.ioBroker-Rock
2023-04-03 21:29:21.230	error	instance system.adapter.yeelight-2.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.ioBroker-Rock
2023-04-03 21:29:21.229	error	Caught by controller[1]: at TCP.<anonymous> (node:net:322:12)
host.ioBroker-Rock
2023-04-03 21:29:21.228	error	Caught by controller[1]: at Socket.emit (node:domain:489:12)
host.ioBroker-Rock
2023-04-03 21:29:21.227	error	Caught by controller[1]: at Socket.emit (node:events:525:35)
host.ioBroker-Rock
2023-04-03 21:29:21.227	error	Caught by controller[1]: at Object.onceWrapper (node:events:628:26)
host.ioBroker-Rock
2023-04-03 21:29:21.226	error	Caught by controller[1]: at Socket.onClose (node:net:911:10)
host.ioBroker-Rock
2023-04-03 21:29:21.225	error	Caught by controller[1]: at new NodeError (node:internal/errors:399:5)
host.ioBroker-Rock
2023-04-03 21:29:21.225	error	Caught by controller[1]: Error: Socket closed before the connection was established
host.ioBroker-Rock
2023-04-03 21:29:21.224	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

yeelight-2.0
2023-04-03 21:29:20.592	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

yeelight-2.0
2023-04-03 21:29:20.590	info	terminating

yeelight-2.0
2023-04-03 21:29:20.589	info	cleaned everything up...

yeelight-2.0
2023-04-03 21:29:20.562	error	Exception-Code: ERR_SOCKET_CLOSED_BEFORE_CONNECTION: Socket closed before the connection was established

yeelight-2.0
2023-04-03 21:29:20.561	error	Error: Socket closed before the connection was established at new NodeError (node:internal/errors:399:5) at Socket.onClose (node:net:911:10) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:525:35) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:322:12)

yeelight-2.0
2023-04-03 21:29:20.560	error	unhandled promise rejection: Socket closed before the connection was established

yeelight-2.0
2023-04-03 21:29:20.558	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
host.ioBroker-Rock
2023-04-03 21:29:20.372	info	instance system.adapter.alexa2.0 started with pid 33531
host.ioBroker-Rock
2023-04-03 21:29:18.170	info	instance system.adapter.alexa2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
host.ioBroker-Rock
2023-04-03 21:29:17.910	info	instance system.adapter.device-watcher.0 started with pid 33520

yeelight-2.0
2023-04-03 21:29:17.308	info	starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.yeelight-2, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230403-fd495c2e

Feuersturm

@apollon77 sagte in Alpha Test js-controller 5.0:

Alpha (@next) updated to 5.0.1-alpha.0-20230403-fd495c2e

Master Slave System wurde erfolgreich aktualisiert.
Admin Log aktualisiert sich jetzt auch wieder automatisch

Bisher keine weiteren Auffälligkeiten bei mir :-)
Dankeschön :sunflower:

apollon77

@e-i-k-e mach mal loglevel Debug. Vllt sieht man da mehr.

e-i-k-e

@apollon77

Gerne.

host.ioBroker-Rock
2023-04-03 23:27:06.136	info	Restart adapter system.adapter.yeelight-2.0 because enabled
host.ioBroker-Rock
2023-04-03 23:27:06.135	error	instance system.adapter.yeelight-2.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.ioBroker-Rock
2023-04-03 23:27:06.135	error	Caught by controller[1]: at TCP.<anonymous> (node:net:322:12)
host.ioBroker-Rock
2023-04-03 23:27:06.135	error	Caught by controller[1]: at Socket.emit (node:domain:489:12)
host.ioBroker-Rock
2023-04-03 23:27:06.134	error	Caught by controller[1]: at Socket.emit (node:events:525:35)
host.ioBroker-Rock
2023-04-03 23:27:06.134	error	Caught by controller[1]: at Object.onceWrapper (node:events:628:26)
host.ioBroker-Rock
2023-04-03 23:27:06.134	error	Caught by controller[1]: at Socket.onClose (node:net:911:10)
host.ioBroker-Rock
2023-04-03 23:27:06.134	error	Caught by controller[1]: at new NodeError (node:internal/errors:399:5)
host.ioBroker-Rock
2023-04-03 23:27:06.133	error	Caught by controller[1]: Error: Socket closed before the connection was established
host.ioBroker-Rock
2023-04-03 23:27:06.133	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

yeelight-2.0
2023-04-03 23:27:05.485	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

yeelight-2.0
2023-04-03 23:27:05.484	debug	Plugin sentry destroyed

yeelight-2.0
2023-04-03 23:27:05.483	info	terminating

yeelight-2.0
2023-04-03 23:27:05.482	info	cleaned everything up...

yeelight-2.0
2023-04-03 23:27:05.446	error	Exception-Code: ERR_SOCKET_CLOSED_BEFORE_CONNECTION: Socket closed before the connection was established

yeelight-2.0
2023-04-03 23:27:05.445	error	Error: Socket closed before the connection was established at new NodeError (node:internal/errors:399:5) at Socket.onClose (node:net:911:10) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:525:35) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:322:12)

yeelight-2.0
2023-04-03 23:27:05.445	error	unhandled promise rejection: Socket closed before the connection was established

yeelight-2.0
2023-04-03 23:27:05.444	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

yeelight-2.0
2023-04-03 23:27:05.436	debug	ERROR YEELIGHT CONNECTION: 0x000000000000000: Connection 192.168.3.140:55443: Error: connect EHOSTUNREACH 192.168.3.140:55443

yeelight-2.0
2023-04-03 23:27:02.673	debug	DEVICE FOUND IN AND CONFIG: {"name":"Stehlampe_Schlafzimmer_klein","ip":"192.168.3.141","port":"55443","smart_name":"","type":"color","id":"0x0000000005ed0835"}

yeelight-2.0
2023-04-03 23:27:02.670	debug	INITINAL ID FOUND FOR: color-0x0000000005ed0835

yeelight-2.0
2023-04-03 23:27:02.669	debug	RESPONSE MESSAGE: from: 0x0000000005ed0835, id: 1, result:[off,23,16711680,2,3000,,,0,100,0,,,,,,,,]}

yeelight-2.0
2023-04-03 23:27:02.642	debug	YEELIGHT FOUND: 192.168.3.141:55443 id: 0x0000000005ed0835 model: color

yeelight-2.0
2023-04-03 23:27:02.349	debug	YEELIGHT FOUND: 192.168.3.140:55443 id: 0x000000000000000 model: color

yeelight-2.0
2023-04-03 23:27:02.333	debug	SMARTNAME:

yeelight-2.0
2023-04-03 23:27:02.331	debug	OLD CONF. FROM OBJ: {"name":"Stehlampe_Schlafzimmer_groß","ip":"192.168.3.140","port":"55443","smart_name":"","type":"color","id":"0x000000000000000","supports":["get_prop","set_default","set_power","toggle","set_bright","start_cf","stop_cf","set_scene","cron_add","cron_get","cron_del","set_ct_abx","set_rgb","set_hsv","set_adjust","adjust_bright","adjust_ct","adjust_color","set_music","set_name"]}

yeelight-2.0
2023-04-03 23:27:02.323	debug	OBJ_ELEMENT: yeelight-2.0.Stehlampe_Schlafzimmer_groß

yeelight-2.0
2023-04-03 23:27:02.322	debug	SMARTNAME:

yeelight-2.0
2023-04-03 23:27:02.320	debug	OLD CONF. FROM OBJ: {"name":"Stehlampe_Schlafzimmer_klein","ip":"192.168.3.141","port":"55443","smart_name":"","type":"color","id":"0x0000000005ed0835"}

yeelight-2.0
2023-04-03 23:27:02.308	debug	OBJ_ELEMENT: yeelight-2.0.Stehlampe_Schlafzimmer_klein

yeelight-2.0
2023-04-03 23:27:02.307	debug	DEVICES IN OBJECTS FOUND: 2

yeelight-2.0
2023-04-03 23:27:02.306	debug	DEVICES IN OBJECTS: {"yeelight-2.0.Stehlampe_Schlafzimmer_klein":{"type":"device","common":{"name":"color","icon":"/icons/color.png"},"native":{"sid":"Stehlampe_Schlafzimmer_klein","type":"color"},"from":"system.adapter.yeelight-2.0","user":"system.user.admin","ts":1680464629168,"_id":"yeelight-2.0.Stehlampe_Schlafzimmer_klein","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}},"yeelight-2.0.Stehlampe_Schlafzimmer_groß":{"type":"device","common":{"name":"color","icon":"/icons/color.png"},"native":{"sid":"Stehlampe_Schlafzimmer_groß","type":"color"},"from":"system.adapter.yeelight-2.0","user":"system.user.admin","ts":1680464629164,"_id":"yeelight-2.0.Stehlampe_Schlafzimmer_groß","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}}

yeelight-2.0
2023-04-03 23:27:02.272	debug	DEVICES IN CONFIG: [{"name":"Stehlampe_Schlafzimmer_groß","ip":"192.168.3.140","port":"55443","smart_name":"","type":"color","id":"0x000000000000000","supports":["get_prop","set_default","set_power","toggle","set_bright","start_cf","stop_cf","set_scene","cron_add","cron_get","cron_del","set_ct_abx","set_rgb","set_hsv","set_adjust","adjust_bright","adjust_ct","adjust_color","set_music","set_name"]},{"name":"Stehlampe_Schlafzimmer_klein","ip":"192.168.3.141","port":"55443","smart_name":"","type":"color","id":"0x0000000005ed0835"}]

yeelight-2.0
2023-04-03 23:27:02.218	info	starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.yeelight-2, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230403-fd495c2e

yeelight-2.0
2023-04-03 23:27:01.853	debug	Plugin sentry Initialize Plugin (enabled=true)

mqtt.0
2023-04-03 23:27:01.267	info	Client [] connected with secret 1680557221267_3140

mqtt.0
2023-04-03 23:27:01.022	info	Client [] connection closed: disconnected
host.ioBroker-Rock
2023-04-03 23:26:59.134	info	instance system.adapter.yeelight-2.0 started with pid 34722

influxdb.0
2023-04-03 23:26:36.571	info	Store 501 buffered influxDB history points
host.ioBroker-Rock
2023-04-03 23:26:29.001	info	Restart adapter system.adapter.yeelight-2.0 because enabled
host.ioBroker-Rock
2023-04-03 23:26:29.000	error	instance system.adapter.yeelight-2.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.ioBroker-Rock
2023-04-03 23:26:29.000	error	Caught by controller[0]: at TCP.<anonymous> (node:net:322:12)
host.ioBroker-Rock
2023-04-03 23:26:29.000	error	Caught by controller[0]: at Socket.emit (node:domain:489:12)
host.ioBroker-Rock
2023-04-03 23:26:28.999	error	Caught by controller[0]: at Socket.emit (node:events:525:35)
host.ioBroker-Rock
2023-04-03 23:26:28.999	error	Caught by controller[0]: at Object.onceWrapper (node:events:628:26)
host.ioBroker-Rock
2023-04-03 23:26:28.999	error	Caught by controller[0]: at Socket.onClose (node:net:911:10)
host.ioBroker-Rock
2023-04-03 23:26:28.999	error	Caught by controller[0]: at new NodeError (node:internal/errors:399:5)
host.ioBroker-Rock
2023-04-03 23:26:28.998	error	Caught by controller[0]: Error: Socket closed before the connection was established
host.ioBroker-Rock
2023-04-03 23:26:28.997	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

yeelight-2.0
2023-04-03 23:26:28.347	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

yeelight-2.0
2023-04-03 23:26:28.346	debug	Plugin sentry destroyed

yeelight-2.0
2023-04-03 23:26:28.345	info	terminating

yeelight-2.0
2023-04-03 23:26:28.344	info	cleaned everything up...

yeelight-2.0
2023-04-03 23:26:28.323	error	Exception-Code: ERR_SOCKET_CLOSED_BEFORE_CONNECTION: Socket closed before the connection was established

yeelight-2.0
2023-04-03 23:26:28.323	error	Error: Socket closed before the connection was established at new NodeError (node:internal/errors:399:5) at Socket.onClose (node:net:911:10) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:525:35) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:322:12)

yeelight-2.0
2023-04-03 23:26:28.322	error	unhandled promise rejection: Socket closed before the connection was established

yeelight-2.0
2023-04-03 23:26:28.322	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

yeelight-2.0
2023-04-03 23:26:28.315	debug	ERROR YEELIGHT CONNECTION: 0x000000000000000: Connection 192.168.3.140:55443: Error: connect EHOSTUNREACH 192.168.3.140:55443

yeelight-2.0
2023-04-03 23:26:26.545	debug	DEVICE FOUND IN AND CONFIG: {"name":"Stehlampe_Schlafzimmer_klein","ip":"192.168.3.141","port":"55443","smart_name":"","type":"color","id":"0x0000000005ed0835"}

yeelight-2.0
2023-04-03 23:26:26.542	debug	INITINAL ID FOUND FOR: color-0x0000000005ed0835

yeelight-2.0
2023-04-03 23:26:26.542	debug	RESPONSE MESSAGE: from: 0x0000000005ed0835, id: 1, result:[off,23,16711680,2,3000,,,0,100,0,,,,,,,,]}

yeelight-2.0
2023-04-03 23:26:25.547	debug	YEELIGHT FOUND: 192.168.3.141:55443 id: 0x0000000005ed0835 model: color

yeelight-2.0
2023-04-03 23:26:25.254	debug	YEELIGHT FOUND: 192.168.3.140:55443 id: 0x000000000000000 model: color

yeelight-2.0
2023-04-03 23:26:25.238	debug	SMARTNAME:

yeelight-2.0
2023-04-03 23:26:25.236	debug	OLD CONF. FROM OBJ: {"name":"Stehlampe_Schlafzimmer_groß","ip":"192.168.3.140","port":"55443","smart_name":"","type":"color","id":"0x000000000000000","supports":["get_prop","set_default","set_power","toggle","set_bright","start_cf","stop_cf","set_scene","cron_add","cron_get","cron_del","set_ct_abx","set_rgb","set_hsv","set_adjust","adjust_bright","adjust_ct","adjust_color","set_music","set_name"]}

yeelight-2.0
2023-04-03 23:26:25.229	debug	OBJ_ELEMENT: yeelight-2.0.Stehlampe_Schlafzimmer_groß

yeelight-2.0
2023-04-03 23:26:25.228	debug	SMARTNAME:

yeelight-2.0
2023-04-03 23:26:25.226	debug	OLD CONF. FROM OBJ: {"name":"Stehlampe_Schlafzimmer_klein","ip":"192.168.3.141","port":"55443","smart_name":"","type":"color","id":"0x0000000005ed0835"}

yeelight-2.0
2023-04-03 23:26:25.213	debug	OBJ_ELEMENT: yeelight-2.0.Stehlampe_Schlafzimmer_klein

yeelight-2.0
2023-04-03 23:26:25.212	debug	DEVICES IN OBJECTS FOUND: 2

yeelight-2.0
2023-04-03 23:26:25.211	debug	DEVICES IN OBJECTS: {"yeelight-2.0.Stehlampe_Schlafzimmer_klein":{"type":"device","common":{"name":"color","icon":"/icons/color.png"},"native":{"sid":"Stehlampe_Schlafzimmer_klein","type":"color"},"from":"system.adapter.yeelight-2.0","user":"system.user.admin","ts":1680464629168,"_id":"yeelight-2.0.Stehlampe_Schlafzimmer_klein","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}},"yeelight-2.0.Stehlampe_Schlafzimmer_groß":{"type":"device","common":{"name":"color","icon":"/icons/color.png"},"native":{"sid":"Stehlampe_Schlafzimmer_groß","type":"color"},"from":"system.adapter.yeelight-2.0","user":"system.user.admin","ts":1680464629164,"_id":"yeelight-2.0.Stehlampe_Schlafzimmer_groß","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}}

yeelight-2.0
2023-04-03 23:26:25.181	debug	DEVICES IN CONFIG: [{"name":"Stehlampe_Schlafzimmer_groß","ip":"192.168.3.140","port":"55443","smart_name":"","type":"color","id":"0x000000000000000","supports":["get_prop","set_default","set_power","toggle","set_bright","start_cf","stop_cf","set_scene","cron_add","cron_get","cron_del","set_ct_abx","set_rgb","set_hsv","set_adjust","adjust_bright","adjust_ct","adjust_color","set_music","set_name"]},{"name":"Stehlampe_Schlafzimmer_klein","ip":"192.168.3.141","port":"55443","smart_name":"","type":"color","id":"0x0000000005ed0835"}]

yeelight-2.0
2023-04-03 23:26:25.142	info	starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.yeelight-2, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230403-fd495c2e

yeelight-2.0
2023-04-03 23:26:24.734	debug	Plugin sentry Initialize Plugin (enabled=true)

yeelight-2.0
2023-04-03 23:26:24.629	debug	States connected to redis: 192.168.3.104:6379

yeelight-2.0
2023-04-03 23:26:24.617	debug	States create User PubSub Client

yeelight-2.0
2023-04-03 23:26:24.615	debug	States create System PubSub Client

yeelight-2.0
2023-04-03 23:26:24.608	debug	Redis States: Use Redis connection: 192.168.3.104:6379

yeelight-2.0
2023-04-03 23:26:24.587	debug	Objects connected to redis: 192.168.3.104:6379

yeelight-2.0
2023-04-03 23:26:24.579	debug	Objects client initialize lua scripts

yeelight-2.0
2023-04-03 23:26:23.863	debug	Objects create User PubSub Client

yeelight-2.0
2023-04-03 23:26:23.861	debug	Objects create System PubSub Client

yeelight-2.0
2023-04-03 23:26:23.856	debug	Objects client ready ... initialize now

yeelight-2.0
2023-04-03 23:26:23.793	debug	Redis Objects: Use Redis connection: 192.168.3.104:6379
host.ioBroker-Rock
2023-04-03 23:26:21.996	info	instance system.adapter.yeelight-2.0 started with pid 34705
host.ioBroker-Rock
2023-04-03 23:26:21.680	info	"system.adapter.yeelight-2.0" enabled
host.ioBroker-Rock
2023-04-03 23:26:10.184	info	"system.adapter.yeelight-2.0" disabled

apollon77

@e-i-k-e sagte in Alpha Test js-controller 5.0:

2023-04-03 23:27:05.436 debug ERROR YEELIGHT CONNECTION: 0x000000000000000: Connection 192.168.3.140:55443: Error: connect EHOSTUNREACH 192.168.3.140:55443

Also mal abgesehen vom crash tippe ich das eher das dein issue ist ... EHOSTUNREACH heisst das das gerät im Netzwerk nicht da ist ... Ich denke er adapter code schliesst darauf hin das socket was aber nie offen war wegen dem Fehler. Bitte adapter issue anlegen das man das dort fixt ... und schau warum das Geröt nicht online ist

apollon77

Alpha Update

5.0.1-alpha.0-20230406-4552d569

Fixes compact mode
Hide warning about "www folder not found" for widgets adapters

Wenn alles so stabil bleibt würde wir überlegen Mitte nächste Woche in den Beta Test im Latest Repo zu gehen ...

Gaspode

@apollon77
Keine Auffälligkeiten. Den Compact Mode nutze ich normalerweise nicht. Hab ihn jetzt mal testweise nach langer Suche :) eingeschaltet (Windows) und merke keinen Unterschied zu vorher. Ist wahrscheinlich gut so, aber kann ich irgendwie kontrollieren, dass er auch wirklich aktiv ist? Hinter jeder Instanz wird jedenfalls noch unterschiedliche RAM Nutzung angezeigt.

@apollon77 said in Alpha Test js-controller 5.0:

Hide warning about "www folder not found" for widgets adapters

Dazu kann ich nix sagen, kenne die Warning nicht.

Thomas Braun

@apollon77

So auf den ersten Blick läuft das rund hier. Das Log ist ruhig, ich verwende allerdings auch den CompactMode nicht.

apollon77

@gaspode Compat einschalten macht erstmal nichts. Du musst jetzt Instanzen sagen das sie in compact laufen sollen und eine gruppe angeben (0 ist "Mit controller", 1....n ist eigene Gruppen, je gruppe gibts einen prozess). das geht via admin bei den instanzen. ggf expertenmodus. Dann sollte ram nutzung weg sein bei den instanzen.

Gaspode

@apollon77 said in Alpha Test js-controller 5.0:

@gaspode Compat einschalten macht erstmal nichts. Du musst jetzt Instanzen sagen das sie in compact laufen sollen und eine gruppe angeben (0 ist "Mit controller", 1....n ist eigene Gruppen, je gruppe gibts einen prozess). das geht via admin bei den instanzen. ggf expertenmodus. Dann sollte ram nutzung weg sein bei den instanzen.

Ah, OK. Danke. Wieder was gelernt. Hab jetzt alle Instanzen in die Controller Gruppe gepackt. Sehe keine Auffälligkeiten.

? Offline

@apollon77

Habe hier 71 Adapter laufen, nur der fitbit-fitness zickt rum:

2023-04-06 10:52:54.815  - info: host.iobrokerS2 instance system.adapter.fitbit-fitness.0 started with pid 13160
2023-04-06 10:52:54.815  - info: host.iobrokerS2 instance system.adapter.fitbit-fitness.0 started with pid 13160
2023-04-06 10:52:55.535  - debug: fitbit-fitness.0 (13160) Redis Objects: Use Redis connection: 10.1.1.1:6379
2023-04-06 10:52:55.555  - debug: fitbit-fitness.0 (13160) Objects client ready ... initialize now
2023-04-06 10:52:55.556  - debug: fitbit-fitness.0 (13160) Objects create System PubSub Client
2023-04-06 10:52:55.557  - debug: fitbit-fitness.0 (13160) Objects create User PubSub Client
2023-04-06 10:52:56.062  - debug: fitbit-fitness.0 (13160) Objects client initialize lua scripts
2023-04-06 10:52:56.066  - debug: fitbit-fitness.0 (13160) Objects connected to redis: 10.1.1.1:6379
2023-04-06 10:52:56.089  - debug: fitbit-fitness.0 (13160) Redis States: Use Redis connection: 10.1.1.1:6379
2023-04-06 10:52:56.096  - debug: fitbit-fitness.0 (13160) States create System PubSub Client
2023-04-06 10:52:56.097  - debug: fitbit-fitness.0 (13160) States create User PubSub Client
2023-04-06 10:52:56.103  - debug: fitbit-fitness.0 (13160) States connected to redis: 10.1.1.1:6379
2023-04-06 10:52:55.535  - debug: fitbit-fitness.0 (13160) Redis Objects: Use Redis connection: 10.1.1.1:6379
2023-04-06 10:52:55.555  - debug: fitbit-fitness.0 (13160) Objects client ready ... initialize now
2023-04-06 10:52:55.556  - debug: fitbit-fitness.0 (13160) Objects create System PubSub Client
2023-04-06 10:52:55.557  - debug: fitbit-fitness.0 (13160) Objects create User PubSub Client
2023-04-06 10:52:56.062  - debug: fitbit-fitness.0 (13160) Objects client initialize lua scripts
2023-04-06 10:52:56.066  - debug: fitbit-fitness.0 (13160) Objects connected to redis: 10.1.1.1:6379
2023-04-06 10:52:56.089  - debug: fitbit-fitness.0 (13160) Redis States: Use Redis connection: 10.1.1.1:6379
2023-04-06 10:52:56.096  - debug: fitbit-fitness.0 (13160) States create System PubSub Client
2023-04-06 10:52:56.097  - debug: fitbit-fitness.0 (13160) States create User PubSub Client
2023-04-06 10:52:56.103  - debug: fitbit-fitness.0 (13160) States connected to redis: 10.1.1.1:6379
2023-04-06 10:52:58.489  - info: fitbit-fitness.0 (13160) starting. Version 0.4.10 (non-npm: Chris-656/ioBroker.fitbit-fitness) in /opt/iobroker/node_modules/iobroker.fitbit-fitness, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230406-4552d569
2023-04-06 10:52:58.550  - debug: fitbit-fitness.0 (13160) Getting refresh Token: c817bd62dd39ec8ed529fc0d16396a1xxxxxxxx
2023-04-06 10:52:58.803  - info: fitbit-fitness.0 (13160) User logged in B...l id:xxxx8
2023-04-06 10:52:58.808  - debug: fitbit-fitness.0 (13160) Tokens checked
2023-04-06 10:52:59.041  - info: fitbit-fitness.0 (13160) Activity Records: Steps:0 Floors:undefined Calories:1884
2023-04-06 10:52:59.047  - error: fitbit-fitness.0 (13160) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-04-06 10:52:59.047  - error: fitbit-fitness.0 (13160) unhandled promise rejection: undefined is not a valid state value
2023-04-06 10:52:59.049  - error: fitbit-fitness.0 (13160) Error: undefined is not a valid state value
   at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17)
   at FitBit._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5332:49)
   at FitBit.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5293:21)
   at FitBit.setActivityStates (/opt/iobroker/node_modules/iobroker.fitbit-fitness/main.js:321:9)
   at FitBit.getActivityRecords (/opt/iobroker/node_modules/iobroker.fitbit-fitness/main.js:305:15)
   at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
   at async FitBit.getFitbitRecords (/opt/iobroker/node_modules/iobroker.fitbit-fitness/main.js:87:5)
2023-04-06 10:52:59.049  - error: fitbit-fitness.0 (13160) undefined is not a valid state value
2023-04-06 10:52:59.057  - info: fitbit-fitness.0 (13160) terminating
2023-04-06 10:52:59.058  - warn: fitbit-fitness.0 (13160) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-04-06 10:52:59.277  - info: fitbit-fitness.0 (13160) Body records: Weight:10.5 Fat:11.342750549316406 BMI:20.1
2023-04-06 10:52:59.559  - info: fitbit-fitness.0 (13160) terminating
2023-04-06 10:52:59.612  - error: host.iobrokerS2 instance system.adapter.fitbit-fitness.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

hab n Issue beim Adapter angelegt:
Issue

Daten zum System(iob diag):

======== Start marking the full check here =========

Skript v.2023-04-02

*** BASE SYSTEM ***
Architecture : x86_64
Docker : false
Virtualization : kvm
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye

PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Systemuptime and Load:
11:09:32 up 38 min, 1 user, load average: 1.21, 1.27, 1.24
CPU threads: 8

*** Time and Time Zones ***
Local time: Thu 2023-04-06 11:09:33 CEST
Universal time: Thu 2023-04-06 09:09:33 UTC
RTC time: Thu 2023-04-06 09:09:33
Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
NTP service: n/a
RTC in local TZ: no

*** User and Groups ***
ilovegym
/home/ilovegym
ilovegym tty cdrom floppy audio dip video plugdev netdev iobroker

*** X-Server-Setup ***
X-Server: false
Desktop:
Terminal: tty
Boot Target: graphical.target

*** MEMORY ***
total used free shared buff/cache available
Mem: 16G 5.5G 9.6G 0.0K 886M 10G
Swap: 974M 0B 974M
Total: 16G 5.5G 10G

    16007 M total memory
     5518 M used memory
      384 M active memory
     5558 M inactive memory
     9602 M free memory
       98 M buffer memory
      788 M swap cache
      974 M total swap
        0 M used swap
      974 M free swap

*** FILESYSTEM ***
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 7.8G 0 7.8G 0% /dev
tmpfs tmpfs 1.6G 492K 1.6G 1% /run
/dev/sda1 ext4 8.9G 5.6G 2.8G 67% /
tmpfs tmpfs 7.9G 0 7.9G 0% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
//10.10.2.10/photo cifs 11T 7.4T 3.1T 71% /mnt/photo
//10.10.2.10/daten cifs 11T 7.4T 3.1T 71% /mnt/daten
tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Thu Apr 6 10:30:48 2023] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[Thu Apr 6 10:30:53 2023] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro

Show mounted filesystems (real ones only):
TARGET SOURCE FSTYPE OPTIONS
/ /dev/sda1 ext4 rw,relatime,errors=remount-ro
|-/mnt/photo //10.10.2.10/photo cifs rw,relatime,vers=3.1.1,cache=strict,username=ilovegym,uid=0,noforceuid,gid=0,noforcegid,addr=10.10.2.10,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1
`-/mnt/daten //10.10.2.10/daten cifs rw,relatime,vers=3.1.1,cache=strict,username=iobroker,uid=0,noforceuid,gid=0,noforcegid,addr=10.10.2.10,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1

Files in neuralgic directories:

/var:
760M /var/
349M /var/log
273M /var/log/journal/fa9fb9e36d4942faa246786f755447be
273M /var/log/journal
259M /var/cache

/opt/iobroker/backups:
4.0K /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
151M /opt/iobroker/iobroker-data/
28M /opt/iobroker/iobroker-data/files
13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js
13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static
13M /opt/iobroker/iobroker-data/files/admin.admin/custom

The five largest files in iobroker-data are:
93M /opt/iobroker/iobroker-data/objects.jsonl
29M /opt/iobroker/iobroker-data/states.jsonl
6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map
2.8M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js
1.6M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_material_Accordion_index_js-node_modules_mui_material_AccordionDetai-57e02d.0886b730.chunk.js.map

*** NodeJS-Installation ***

/usr/bin/nodejs v18.15.0
/usr/bin/node v18.15.0
/usr/bin/npm 9.5.0
/usr/bin/npx 9.5.0

nodejs:
Installed: 18.15.0-deb-1nodesource1
Candidate: 18.15.0-deb-1nodesource1
Version table:
*** 18.15.0-deb-1nodesource1 500
500 https://deb.nodesource.com/node_18.x bullseye/main amd64 Packages
100 /var/lib/dpkg/status
12.22.12~dfsg-1~deb11u3 500
500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
12.22.5~dfsg-2~11u1 500
500 http://deb.debian.org/debian bullseye/main amd64 Packages

Temp directories causing npm8 problem: 0
No problems detected

*** ioBroker-Installation ***

ioBroker Status
iobroker is running on this host.

At least one iobroker host is running.

Objects type: redis
States type: redis

Core adapters versions
js-controller: 5.0.1-alpha.0-20230406-4552d569
admin: 6.4.3
javascript: 7.0.3

Adapters from github: 21

Adapter State

system.adapter.admin.0 : admin : iobrokerS2 - enabled, port: 8081, bind: 0.0.0.0, run as: admin
system.adapter.alarm.0 : alarm : iobrokerS2 - enabled
system.adapter.alexa-shoppinglist.0 : alexa-shoppinglist : iobrokerS2 - enabled
system.adapter.alexa-timer-vis.0 : alexa-timer-vis : iobrokerS2 - enabled
system.adapter.alexa2.0 : alexa2 : iobrokerS2 - enabled
system.adapter.backitup.0 : backitup : iobrokerS2 - enabled
system.adapter.bluelink.0 : bluelink : iobrokerS2 - enabled
system.adapter.cloud.0 : cloud : iobrokerS2 - enabled
system.adapter.countdown.0 : countdown : iobrokerS2 - enabled
system.adapter.device-watcher.0 : device-watcher : iobrokerS2 - enabled
system.adapter.devices.0 : devices : iobrokerS2 - disabled
system.adapter.deyeidc.0 : deyeidc : iobrokerS2 - enabled, port: 8899
system.adapter.deyeidc.1 : deyeidc : iobrokerS2 - enabled, port: 8899
system.adapter.discovery.0 : discovery : iobrokerS2 - enabled
system.adapter.drops-weather.0 : drops-weather : iobrokerS2 - enabled
system.adapter.dwd.0 : dwd : iobrokerS2 - enabled
system.adapter.email.0 : email : iobrokerS2 - enabled
system.adapter.energiefluss.0 : energiefluss : iobrokerS2 - enabled
system.adapter.energiefluss.1 : energiefluss : iobrokerS2 - enabled
system.adapter.feiertage.0 : feiertage : iobrokerS2 - enabled
system.adapter.fitbit-fitness.0 : fitbit-fitness : iobrokerS2 - disabled
system.adapter.flot.0 : flot : iobrokerS2 - disabled
system.adapter.fritzdect.0 : fritzdect : iobrokerS2 - enabled
system.adapter.fully-mqtt.0 : fully-mqtt : iobrokerS2 - enabled
system.adapter.go-e.0 : go-e : iobrokerS2 - enabled
system.adapter.govee-app.0 : govee-app : iobrokerS2 - enabled
system.adapter.heizoel.0 : heizoel : iobrokerS2 - enabled
system.adapter.ical.0 : ical : iobrokerS2 - enabled
system.adapter.iceroad.0 : iceroad : iobrokerS2 - enabled
system.adapter.influxdb.0 : influxdb : iobrokerS2 - enabled, port: 8086
system.adapter.influxdb.1 : influxdb : iobrokerS2 - enabled, port: 8086
system.adapter.influxdb.2 : influxdb : iobrokerS2 - enabled, port: 8086
system.adapter.iot.0 : iot : iobrokerS2 - enabled
system.adapter.javascript.0 : javascript : iobrokerS2 - enabled
system.adapter.lgtv.0 : lgtv : iobrokerS2 - enabled
system.adapter.lgtv.1 : lgtv : iobrokerS2 - enabled
system.adapter.lightcontrol.0 : lightcontrol : iobrokerS2 - enabled
system.adapter.lightcontrol.1 : lightcontrol : iobrokerS2 - enabled
system.adapter.linux-control.0 : linux-control : iobrokerS2 - enabled
system.adapter.lovelace.0 : lovelace : iobrokerS2 - enabled, port: 8091, bind: 0.0.0.0, run as: admin
system.adapter.meteoalarm.0 : meteoalarm : iobrokerS2 - enabled
system.adapter.mihome-vacuum.0 : mihome-vacuum : iobrokerS2 - enabled, port: 54321
system.adapter.mihome-vacuum.1 : mihome-vacuum : iobrokerS2 - enabled, port: 54321
system.adapter.mihome-vacuum.2 : mihome-vacuum : iobrokerS2 - enabled, port: 54321
system.adapter.mihome-vacuum.3 : mihome-vacuum : iobrokerS2 - enabled, port: 54321
system.adapter.minuaru.0 : minuaru : iobrokerS2 - enabled
system.adapter.minuvis.0 : minuvis : iobrokerS2 - disabled
system.adapter.mqtt.0 : mqtt : iobrokerS2 - enabled, port: 1886, bind: 0.0.0.0
system.adapter.mqtt.1 : mqtt : iobrokerS2 - enabled, port: 1884, bind: 0.0.0.0
system.adapter.nut.0 : nut : iobrokerS2 - enabled
system.adapter.octoprint.0 : octoprint : iobrokerS2 - enabled
system.adapter.odl.0 : odl : iobrokerS2 - enabled
system.adapter.oilfox.0 : oilfox : iobrokerS2 - enabled
system.adapter.openligadb.0 : openligadb : iobrokerS2 - enabled
system.adapter.openweathermap.0 : openweathermap : iobrokerS2 - enabled
system.adapter.operating-hours.0 : operating-hours : iobrokerS2 - enabled
system.adapter.ping.0 : ping : iobrokerS2 - enabled
system.adapter.pioneer_sc_vsx.0 : pioneer_sc_vsx : iobrokerS2 - enabled, port: 8102
system.adapter.pollenflug.0 : pollenflug : iobrokerS2 - enabled
system.adapter.puppeteer.0 : puppeteer : iobrokerS2 - enabled
system.adapter.rest-api.0 : rest-api : iobrokerS2 - enabled, port: 8880, bind: 0.0.0.0, run as: restapi
system.adapter.simple-api.0 : simple-api : iobrokerS2 - enabled, port: 8087, bind: 0.0.0.0, run as: admin
system.adapter.snmp.0 : snmp : iobrokerS2 - enabled
system.adapter.solarmanpv.0 : solarmanpv : iobrokerS2 - enabled
system.adapter.sonoff.0 : sonoff : iobrokerS2 - enabled, port: 1883, bind: 0.0.0.0
system.adapter.synochat.0 : synochat : iobrokerS2 - enabled
system.adapter.synology.0 : synology : iobrokerS2 - enabled, port: 5001
system.adapter.synology.1 : synology : iobrokerS2 - enabled, port: 5000
system.adapter.text2command.0 : text2command : iobrokerS2 - enabled
system.adapter.tr-064.0 : tr-064 : iobrokerS2 - enabled
system.adapter.tr-064.1 : tr-064 : iobrokerS2 - enabled
system.adapter.trashschedule.0 : trashschedule : iobrokerS2 - enabled
system.adapter.tuya.0 : tuya : iobrokerS2 - enabled
system.adapter.unifi.0 : unifi : iobrokerS2 - enabled
system.adapter.viessmannapi.0 : viessmannapi : iobrokerS2 - enabled
system.adapter.vis.0 : vis : iobrokerS2 - enabled
system.adapter.weatherunderground.0 : weatherunderground : iobrokerS2 - enabled
system.adapter.web.0 : web : iobrokerS2 - enabled, port: 81, bind: 0.0.0.0, run as: admin
system.adapter.wifilight.0 : wifilight : iobrokerS2 - enabled
system.adapter.windows-control.0 : windows-control : iobrokerS2 - enabled
system.adapter.wireguard.0 : wireguard : iobrokerS2 - enabled
system.adapter.wled.0 : wled : iobrokerS2 - enabled
system.adapter.worx.0 : worx : iobrokerS2 - enabled
system.adapter.yahka.0 : yahka : iobrokerS2 - enabled
system.adapter.yeelight-2.0 : yeelight-2 : iobrokerS2 - enabled
system.adapter.zigbee.0 : zigbee : iobrokerS2 - enabled, port: tcp://10.1.1.98:20108
instance is alive

Enabled adapters with bindings

system.adapter.admin.0 : admin : iobrokerS2 - enabled, port: 8081, bind: 0.0.0.0, run as: admin
system.adapter.deyeidc.0 : deyeidc : iobrokerS2 - enabled, port: 8899
system.adapter.deyeidc.1 : deyeidc : iobrokerS2 - enabled, port: 8899
system.adapter.influxdb.0 : influxdb : iobrokerS2 - enabled, port: 8086
system.adapter.influxdb.1 : influxdb : iobrokerS2 - enabled, port: 8086
system.adapter.influxdb.2 : influxdb : iobrokerS2 - enabled, port: 8086
system.adapter.lovelace.0 : lovelace : iobrokerS2 - enabled, port: 8091, bind: 0.0.0.0, run as: admin
system.adapter.mihome-vacuum.0 : mihome-vacuum : iobrokerS2 - enabled, port: 54321
system.adapter.mihome-vacuum.1 : mihome-vacuum : iobrokerS2 - enabled, port: 54321
system.adapter.mihome-vacuum.2 : mihome-vacuum : iobrokerS2 - enabled, port: 54321
system.adapter.mihome-vacuum.3 : mihome-vacuum : iobrokerS2 - enabled, port: 54321
system.adapter.mqtt.0 : mqtt : iobrokerS2 - enabled, port: 1886, bind: 0.0.0.0
system.adapter.mqtt.1 : mqtt : iobrokerS2 - enabled, port: 1884, bind: 0.0.0.0
system.adapter.pioneer_sc_vsx.0 : pioneer_sc_vsx : iobrokerS2 - enabled, port: 8102
system.adapter.rest-api.0 : rest-api : iobrokerS2 - enabled, port: 8880, bind: 0.0.0.0, run as: restapi
system.adapter.simple-api.0 : simple-api : iobrokerS2 - enabled, port: 8087, bind: 0.0.0.0, run as: admin
system.adapter.sonoff.0 : sonoff : iobrokerS2 - enabled, port: 1883, bind: 0.0.0.0
system.adapter.synology.0 : synology : iobrokerS2 - enabled, port: 5001
system.adapter.synology.1 : synology : iobrokerS2 - enabled, port: 5000
system.adapter.web.0 : web : iobrokerS2 - enabled, port: 81, bind: 0.0.0.0, run as: admin
system.adapter.zigbee.0 : zigbee : iobrokerS2 - enabled, port: tcp://10.1.1.98:20108

ioBroker-Repositories
stable : http://download.iobroker.net/sources-dist.json
beta : http://download.iobroker.net/sources-dist-latest.json

Active repo(s): beta

Installed ioBroker-Instances
Used repository: beta
Adapter "admin" : 6.4.3 , installed 6.4.3
Adapter "alarm" : 3.3.10 , installed 3.3.10
Adapter "alexa-shoppinglist": 0.1.5, installed 0.1.5
Adapter "alexa-timer-vis": 0.1.14 , installed 0.1.14
Adapter "alexa2" : 3.23.2 , installed 3.23.2
Adapter "backitup" : 2.6.16 , installed 2.6.16
Adapter "bluelink" : 2.2.6 , installed 2.2.8
Adapter "cloud" : 4.4.0 , installed 4.4.0
Adapter "countdown" : 1.3.0 , installed 1.3.0
Adapter "device-watcher": 2.8.0 , installed 2.8.0
Adapter "devices" : 1.1.2 , installed 1.1.2
Adapter "discovery" : 3.1.0 , installed 3.1.0
Adapter "dwd" : 2.8.3 , installed 2.8.3
Adapter "email" : 1.1.4 , installed 1.1.4
Adapter "feiertage" : 1.1.0 , installed 1.1.0
Adapter "fitbit-fitness": 0.4.10 , installed 0.4.10
Adapter "flot" : 1.12.0 , installed 1.12.0
Adapter "fritzdect" : 2.3.1 , installed 2.3.1
Adapter "go-e" : 1.0.27 , installed 1.0.26 [Updatable]
Adapter "heizoel" : 1.0.3 , installed 1.0.3
Adapter "ical" : 1.13.2 , installed 1.13.2
Adapter "iceroad" : 1.2.0 , installed 1.2.0
Adapter "influxdb" : 3.2.0 , installed 3.2.0
Adapter "iot" : 1.14.5 , installed 1.14.5
Adapter "javascript" : 7.0.3 , installed 7.0.3
Controller "js-controller": 4.0.24 , installed 5.0.1
Adapter "lgtv" : 1.1.10 , installed 1.1.10
Adapter "lightcontrol" : 0.2.1 , installed 0.2.1
Adapter "linux-control": 1.1.5 , installed 1.1.5
Adapter "lovelace" : 3.0.1 , installed 3.0.1
Adapter "meteoalarm" : 2.3.5 , installed 2.3.5
Adapter "mihome-vacuum": 3.9.5 , installed 3.9.5
Adapter "minuvis" : 2.3.3 , installed 2.3.3
Adapter "mqtt" : 4.1.1 , installed 4.1.1
Adapter "nut" : 1.6.0 , installed 1.6.0
Adapter "octoprint" : 4.1.0 , installed 4.1.0
Adapter "odl" : 2.0.5 , installed 2.0.5
Adapter "oilfox" : 4.1.2 , installed 4.1.2
Adapter "openligadb" : 1.2.4 , installed 1.2.4
Adapter "openweathermap": 0.3.8 , installed 0.3.8
Adapter "operating-hours": 1.0.0 , installed 1.0.0
Adapter "ping" : 1.5.3 , installed 1.5.3
Adapter "pollenflug" : 1.0.6 , installed 1.0.6
Adapter "puppeteer" : 0.2.7 , installed 0.2.7
Adapter "rest-api" : 1.0.5 , installed 1.0.5
Adapter "simple-api" : 2.7.2 , installed 2.7.2
Adapter "snmp" : 2.4.6 , installed 2.4.6
Adapter "socketio" : 6.3.5 , installed 6.3.5
Adapter "solarmanpv" : 0.3.2 , installed 0.3.2
Adapter "sonoff" : 2.5.3 , installed 2.5.3
Adapter "synochat" : 1.2.1 , installed 1.2.1
Adapter "synology" : 2.1.13 , installed 2.1.13
Adapter "text2command" : 3.0.2 , installed 3.0.2
Adapter "tr-064" : 4.2.18 , installed 4.2.18
Adapter "trashschedule": 2.2.0 , installed 2.2.0
Adapter "tuya" : 3.14.2 , installed 3.14.2
Adapter "unifi" : 0.6.4 , installed 0.6.4
Adapter "viessmannapi" : 2.0.9 , installed 2.0.9
Adapter "vis" : 1.4.16 , installed 1.4.16
Adapter "weatherunderground": 3.4.2, installed 3.4.2
Adapter "web" : 5.5.3 , installed 5.5.3
Adapter "wifilight" : 1.1.4 , installed 1.1.4
Adapter "windows-control": 0.1.5 , installed 0.1.5
Adapter "wireguard" : 1.4.1 , installed 1.4.1
Adapter "wled" : 0.6.7 , installed 0.6.7
Adapter "worx" : 2.0.3 , installed 2.0.3
Adapter "ws" : 2.3.6 , installed 2.3.6
Adapter "yahka" : 1.0.3 , installed 1.0.3
Adapter "yeelight-2" : 1.2.1 , installed 1.2.1
Adapter "zigbee" : 1.8.10 , installed 1.8.11

Objects and States
Please stand by - This may take a while
Objects: 101001
States: 83854

*** OS-Repositories and Updates ***
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 https://deb.nodesource.com/node_18.x bullseye InRelease
Hit:5 https://packagecloud.io/ookla/speedtest-cli/debian bullseye InRelease
Reading package lists...
Pending Updates: 0

*** Listening Ports ***
Active Internet connections Proto Recv-Q Send-Q Local Address tcp 0 0 0.0.0.0:111 tcp 0 0 127.0.0.1:44467 tcp 0 0 0.0.0.0:22 tcp 0 0 127.0.0.1:6010 tcp 0 0 0.0.0.0:1883 tcp 0 0 0.0.0.0:1884 tcp 0 0 0.0.0.0:1886 tcp6 0 0 :::44783 tcp6 0 0 :::111 tcp6 0 0 :::8880 tcp6 0 0 :::81 tcp6 0 0 :::8081 tcp6 0 0 :::22 tcp6 0 0 :::8087 tcp6 0 0 ::1:6010 tcp6 0 0 :::8091 tcp6 0 0 :::1888 udp 0 0 0.0.0.0:68 udp 0 0 0.0.0.0:111 udp 0 0 10.1.1.2:123 udp 0 0 127.0.0.1:123 udp 0 0 0.0.0.0:123 udp 0 0 0.0.0.0:41823 udp 0 0 0.0.0.0:34368 udp 0 0 0.0.0.0:53421 udp 0 0 0.0.0.0:54322 udp 0 0 0.0.0.0:54323 udp 0 0 0.0.0.0:54324 udp 0 0 0.0.0.0:5353 udp 0 0 10.1.1.2:5353 udp 0 0 0.0.0.0:5353 udp 0 0 0.0.0.0:6666 udp 0 0 0.0.0.0:6667 udp6 0 0 :::111 udp6 0 0 fe80::11:32ff:fe28::123 udp6 0 0 ::1:123 udp6 0 0 :::123 udp6 0 0 :::5353 udp6 0 0 :::38898 (only servers)
Foreign Address State User Inode PID/Program name
0.0.0.0:* LISTEN 0 15385 1/init
0.0.0.0:* LISTEN 1001 43357 9753/chrome
0.0.0.0:* LISTEN 0 14536 523/sshd: /usr/sbin
0.0.0.0:* LISTEN 1000 10636 597/sshd: ilovegym@
0.0.0.0:* LISTEN 1001 32668 7176/io.sonoff.0
0.0.0.0:* LISTEN 1001 31568 7623/io.mqtt.1
0.0.0.0:* LISTEN 1001 33588 7529/io.mqtt.0
:::* LISTEN 1001 42537 8491/io.yahka.0
:::* LISTEN 0 17436 1/init
:::* LISTEN 1001 40249 8662/io.rest-api.0
:::* LISTEN 1001 37769 9131/io.web.0
:::* LISTEN 1001 36296 6749/io.admin.0
:::* LISTEN 0 14538 523/sshd: /usr/sbin
:::* LISTEN 1001 46575 10220/io.simple-api
:::* LISTEN 1000 10635 597/sshd: ilovegym@
:::* LISTEN 1001 37748 8954/io.lovelace.0
:::* LISTEN 1001 51609 12074/io.fully-mqtt
0.0.0.0:* 0 15469 387/dhclient
0.0.0.0:* 0 17433 1/init
0.0.0.0:* 0 9840 509/ntpd
0.0.0.0:* 0 9838 509/ntpd
0.0.0.0:* 0 9834 509/ntpd
0.0.0.0:* 110 10608 489/avahi-daemon: r
0.0.0.0:* 1001 42324 8208/io.snmp.0
0.0.0.0:* 1001 34730 7059/io.mihome-vacu
0.0.0.0:* 1001 46892 10637/io.mihome-vac
0.0.0.0:* 1001 32598 7020/io.mihome-vacu
0.0.0.0:* 1001 51230 10678/io.mihome-vac
0.0.0.0:* 1001 46434 10133/io.wled.0
0.0.0.0:* 1001 38275 7909/io.tr-064.0
0.0.0.0:* 110 10606 489/avahi-daemon: r
0.0.0.0:* 1001 37294 7833/io.tuya.0
0.0.0.0:* 1001 37295 7833/io.tuya.0
:::* 0 17439 1/init
:::* 106 9986 509/ntpd
:::* 0 9842 509/ntpd
:::* 0 9831 509/ntpd
:::* 110 10607 489/avahi-daemon: r
:::* 110 10609 489/avahi-daemon: r

*** Log File - Last 25 Lines ***

2023-04-06 11:10:08.921 - info: web.0 (9131) ==> Connected system.user.admin from ::ffff:10.1.1.60
2023-04-06 11:10:10.219 - warn: sonoff.0 (7176) Client "Stecker7" not connected
2023-04-06 11:10:11.100 - info: meteoalarm.0 (20420) starting. Version 2.3.5 (non-npm: jack-blackson/ioBroker.meteoalarm) in /opt/iobroker/node_modules/iobroker.meteoalarm, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230406-4552d569
2023-04-06 11:10:12.555 - info: meteoalarm.0 (20420) 15.1: Updated Weather Alarms for Kreis Darmstadt-Dieburg und Stadt Darmstadt -> 0 alarm(s) found
2023-04-06 11:10:12.556 - warn: meteoalarm.0 (20420) Terminated (ADAPTER_REQUESTED_TERMINATION): All data processed. Adapter stopped until next scheduled process.
2023-04-06 11:10:13.080 - info: host.iobrokerS2 instance system.adapter.meteoalarm.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-04-06 11:10:15.813 - info: javascript.0 (6930) script.js.common.Nuki.mqtt2log: NUKI Hub KI: MQTT connected
2023-04-06 11:10:16.138 - info: solarmanpv.0 (20379) Terminated (ADAPTER_REQUESTED_TERMINATION): Everything done. Going to terminate till next schedule
2023-04-06 11:10:16.653 - info: host.iobrokerS2 instance system.adapter.solarmanpv.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-04-06 11:10:17.236 - info: javascript.0 (6930) script.js.common.Nuki.mqtt2log: NUKI Hub KA: MQTT connected
2023-04-06 11:10:20.096 - info: javascript.0 (6930) script.js.common.Nuki.mqtt2log: NUKI Hub KI: Nuki start pairing
2023-04-06 11:10:20.098 - info: javascript.0 (6930) script.js.common.Nuki.mqtt2log: NUKI Hub KI: Nuki paired
2023-04-06 11:10:20.810 - info: javascript.0 (6930) script.js.common.Nuki.mqtt2log: NUKI Hub KA: Nuki start pairing
2023-04-06 11:10:20.811 - info: javascript.0 (6930) script.js.common.Nuki.mqtt2log: NUKI Hub KA: Nuki paired
2023-04-06 11:10:23.579 - info: javascript.0 (6930) script.js.common.Nuki.mqtt2log: NUKI Hub KI: Querying lock state: locked
2023-04-06 11:10:23.679 - info: javascript.0 (6930) script.js.common.Nuki.mqtt2log: NUKI Hub KI: Querying lock battery state: success
2023-04-06 11:10:23.897 - info: javascript.0 (6930) script.js.common.Nuki.mqtt2log: NUKI Hub KI: Reading config. Result: success
2023-04-06 11:10:23.897 - info: javascript.0 (6930) script.js.common.Nuki.mqtt2log: NUKI Hub KI: Reading advanced config. Result: success
2023-04-06 11:10:24.088 - info: javascript.0 (6930) script.js.common.Nuki.mqtt2log: NUKI Hub KA: Querying lock state: locked
2023-04-06 11:10:24.200 - info: javascript.0 (6930) script.js.common.Nuki.mqtt2log: NUKI Hub KA: Querying lock battery state: success
2023-04-06 11:10:24.494 - info: javascript.0 (6930) script.js.common.Nuki.mqtt2log: NUKI Hub KA: Reading config. Result: success
2023-04-06 11:10:24.597 - info: javascript.0 (6930) script.js.common.Nuki.mqtt2log: NUKI Hub KA: Reading advanced config. Result: success
2023-04-06 11:10:25.923 - info: web.0 (9131) <== Disconnect system.user.admin from ::ffff:10.1.1.60
2023-04-06 11:10:29.145 - info: web.0 (9131) ==> Connected system.user.admin from ::ffff:10.1.1.60
2023-04-06 11:10:29.146 - info: web.0 (9131) ==> Connected system.user.admin from ::ffff:10.1.1.60


============ Mark until here for C&P =============

apollon77 · Skript v.2023-04-02

@ilovegym sagte in Alpha Test js-controller 5.0:

hab n Issue beim Adapter angelegt:

Jupp das ist genau richtig ... das sollte aber schon mit controller 4 gemeckert haben :-)

? Offline

@apollon77

hmm mit Controller 4 hat er evtl gemeckert aber nicht den Adapter gestoppt.. hier stoppt er ihn und im Host-Tab wird eine 1 angezeigt und die Meldung, dass der fitbit-Adapter mehrmals mit Fehler gestartet wurde..

vorher lief er ohne mir aufzufallen.. und sonst ist am System nichts anders.. hab die VM geklont und nur den js-controller geupdatet...

apollon77

@ilovegym Ok, dann haben wir vllt doch eine "lange zeit deprecation" jetzt härter ... Danke!

Community Forum

NEWS

Alpha Test js-controller 5.0

Alpha (@next) updated to 5.0.1-alpha.0-20230403-fd495c2e

Alpha (@next) updated to 5.0.1-alpha.0-20230403-fd495c2e

Alpha (@next) updated to 5.0.1-alpha.0-20230403-fd495c2e

Alpha Update

5.0.1-alpha.0-20230406-4552d569

Alpha Update

5.0.1-alpha.0-20230406-4552d569

Alpha Update

5.0.1-alpha.0-20230406-4552d569

Support us

587

32.4k

81.5k

1.3m