js-controller 5.0.x jetzt in der BETA

crunchip

@foxriver76 debian VM in Proxmox
aktuell js-controller: 5.0.1-alpha.0-20230406-4552d569

foxriver76

@crunchip Hmm.. ok dann sollte es eigentlich gehen. Müsste @Bluefox etwas zu sagen, wie der Admin Check genau ausschaut.

haselchen

@foxriver76

@crunchip , ich und erstmal @heinhan hatten das „VIS“ Problem.
Kommt da ein Fix zu ?!

Chaot

@apollon77
Der LGTV Adapter fällt aus wie erwartet (ist aber bei mir eher unwichtig)
Dazu kommt noch eine Fehlermeldung:

host.ioBroker
2023-06-12 22:06:50.881	error	cannot call visUtils: Not exists

Die Fehlermeldung blieb jetzt erstmal weg nachdem ich den VIS Adapter nochmal hochgeladen habe.
Ansonsten scheint alles zu laufen.

Edit:
Scheinbar kommt doch noch was:

host.ioBroker
2023-06-12 22:20:00.903	error	instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.ioBroker
2023-06-12 22:20:00.903	error	Caught by controller[1]: at processImmediate (node:internal/timers:478:21)
host.ioBroker
2023-06-12 22:20:00.902	error	Caught by controller[1]: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:9313:46)
host.ioBroker
2023-06-12 22:20:00.902	error	Caught by controller[1]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15)
host.ioBroker
2023-06-12 22:20:00.902	error	Caught by controller[1]: Error: The pattern "Montag<br>12.06.2023" is not a valid ID pattern
host.ioBroker
2023-06-12 22:20:00.902	error	Caught by controller[0]: at processImmediate (node:internal/timers:478:21)
host.ioBroker
2023-06-12 22:20:00.902	error	Caught by controller[0]: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:9313:46)
host.ioBroker
2023-06-12 22:20:00.901	error	Caught by controller[0]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15)
host.ioBroker
2023-06-12 22:20:00.899	error	Caught by controller[0]: Error: The pattern "Montag<br>12.06.2023" is not a valid ID pattern

web.0
2023-06-12 22:20:00.678	error	The pattern "Montag<br>12.06.2023" is not a valid ID pattern

web.0
2023-06-12 22:20:00.678	error	Error: The pattern "Montag<br>12.06.2023" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:9313:46) at processImmediate (node:internal/timers:478:21)

web.0
2023-06-12 22:20:00.677	error	uncaught exception: The pattern "Montag<br>12.06.2023" is not a valid ID pattern

web.0
2023-06-12 22:20:00.638	error	The pattern "Montag<br>12.06.2023" is not a valid ID pattern

web.0
2023-06-12 22:20:00.637	error	Error: The pattern "Montag<br>12.06.2023" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:9313:46) at processImmediate (node:internal/timers:478:21)

web.0
2023-06-12 22:20:00.631	error	uncaught exception: The pattern "Montag<br>12.06.2023" is not a valid ID pattern

Chaot

Der VIS Editor hat auf zwei von 5 Projekten mit einem Absturz reagiert. Nach einem Neustart der ganzen VM scheint es jetzt allerdings zu laufen.
Ich habe zwei Fehlermeldungen, die aber scheinbar bei mir aus dem System kommen und nichts mit dem Controler zu tun haben.
Wie bekomme ich die weg?

host.ioBroker
2023-06-12 22:30:52.020	error	iobroker npm-install: host.ioBroker Unknown packetName fontui. Please install packages from outside the repository using npm!
host.ioBroker
2023-06-12 22:30:43.727	error	iobroker npm-install: host.ioBroker Unknown packetName openuv. Please install packages from outside the repository using npm!

Da scheint irgendwas falsch installiert zu sein.

Thomas Braun

@chaot sagte in js-controller 5.0.x jetzt in der BETA:

Wie bekomme ich die weg?

Das sind wohl verwaiste Adapter. Wenn die nicht benötigt werden würde ich die vor die Tür setzen.

Chaot

@thomas-braun Dachte ich auch. Danke dir.
Haben gerade den Tritt bekommen.

e-i-k-e

@haselchen sagte in js-controller 5.0.x jetzt in der BETA:

@foxriver76

@crunchip , ich und erstmal @heinhan hatten das „VIS“ Problem.
Kommt da ein Fix zu ?!

Ich habe den Fehler bei mir auch beobachten können. Bin allerdings noch auf der letzten Alpha von js.Controller.

Merlin123

Wenn ich in einem Blockly einen anderen DP auswählen will öffnet sich der Objektbaum, die Anzeige springt zum aktuellen DP und dann dreht sich nur noch der Wartekreis. Keine Chance, den DP wieder zu ändern.

Versuche ich einen Reload der Seite ( http://192.168.0.251:8081/#tab-javascript ) kommt erstmal ein "Webseite nicht erreichbar".
Muss dann so ne halbe bis ganze Minute warten, dann läd er die Seite wieder. Versuche ich den DP nochmal zu ändern gleiches Spiel.
Alle Adapter auf den neusten Beta Stand.

EDIT: Nach Downgrade auf 4.0.24 geht das wieder.

heinhan

@heinhan Leider ist der Fehler heute wieder auf getaucht.

error: host.Iobroker cannot call visUtils: Not exi

Marty56

Installation von js-controller 5.0.x ist möglich.
Allerdings kann ich diverse Adapter nicht mehr upgraden.
Ich bekomme die Fehlermeldung:

js-controller (>=2.0.0): 5.0.2
node (>=14.0.0):

Meine Node Versionen sind größer als 14.00

 node -v
v18.16.0
npm -v
9.5.1

Update: nach iob fix funktionierte es wieder

Folgende Ausfälle bei mir.

Yakha (V1.03)

host.iobroker
2023-06-13 08:11:39.286	error	instance system.adapter.yahka.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[26]: [Yahka-0 011F@Wasseralarm@Wasseralarm@Status Low Battery] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[25]: [Yahka-0 011F@Heizung im Kinderzimmer@KZ Heizung@Status Low Battery] characteristic value expected valid finite number and received "NaN" (number)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[24]: [Yahka-0 011F@Heizung im Kinderzimmer@KZ Heizung@Status Low Battery] characteristic value expected valid finite number and received "NaN" (number)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[23]: [Yahka-0 011F@Leuchtstreifen@Leuchtstreifen@Color Temperature] characteristic was supplied illegal value: number 0 exceeded minimum of 140
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[22]: [Yahka-0 011F@Leuchtstreifen@Leuchtstreifen@Color Temperature] characteristic was supplied illegal value: number 0 exceeded minimum of 140
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[21]: [Yahka-0 011F@nördliches Fenster K1@nördliches Fenster K1@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[20]: [Yahka-0 011F@südliche, rechte Fenster K3@südliche,rechteFenster K3@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[19]: [Yahka-0 011F@südliche, linke Fenster K3@südliche,linke Fenster K3@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[18]: [Yahka-0 011F@südliche, rechte Fenster im OG@südliche, rechte Fenster im OG@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[17]: [Yahka-0 011F@südliche, linke Fenster im OG@südliche, linke Fenster im OG@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[16]: [Yahka-0 011F@nördliches Fenster im Bad@nördliches Fenster im Bad@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[15]: [Yahka-0 011F@südliches Fenster OF@südliches Fenster OF@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[14]: [Yahka-0 011F@südliches Fenster KZ@südliches Fenster KZ@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[13]: [Yahka-0 011F@westliches Fenster KZ@westliches Fenster KZ@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[12]: [Yahka-0 011F@westliches Fenster SZ@westliches Fenster SZ@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[11]: [Yahka-0 011F@nördliches Fenster SZ@nördliches Fenster SZ@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[10]: [Yahka-0 011F@Haustür@Haustür@Status Low Battery] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[9]: [Yahka-0 011F@Haustür@Haustür@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[8]: [Yahka-0 011F@westliche Tür@westliche Tür@Status Low Battery] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[7]: [Yahka-0 011F@westliche Tür@westliche Tür@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[6]: [Yahka-0 011F@Terrasse rechts@Terrassentür rechts@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[5]: [Yahka-0 011F@Terrasse links@Terrassentür links@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[4]: [Yahka-0 011F@Neue Post@Neue Post@On] characteristic value expected boolean and received undefined
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[4]: [Yahka-0 011F@Garage@Garage@Obstruction Detected] characteristic value expected boolean and received undefined
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[3]: [Yahka-0 011F@Lampe im Schlafzimmer@Nachttischlampe@Hue] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[2]: [Yahka-0 011F@Lampe im Schlafzimmer@Nachttischlampe@Saturation] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.284	error	Caught by controller[1]: [Yahka-0 011F@Luftqual@Luftqualität@PM2.5 Density] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.284	error	Caught by controller[0]: [Yahka-0 011F@Justin@Justin@On] characteristic value expected boolean and received undefined

yahka.0
2023-06-13 08:11:38.555	error	Error The pattern "ObstructionDetectedObstructionDetectedObstructionDetectedObstructionDetected0_userdata.0.Garage.ObstructionDetected" is not a valid ID pattern

yahka.0
2023-06-13 08:11:38.555	error	ReplyError: Error The pattern "ObstructionDetectedObstructionDetectedObstructionDetectedObstructionDetected0_userdata.0.Garage.ObstructionDetected" is not a valid ID pattern at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)

yahka.0
2023-06-13 08:11:38.544	error	unhandled promise rejection: Error The pattern "ObstructionDetectedObstructionDetectedObstructionDetectedObstructionDetected0_userdata.0.Garage.ObstructionDetected" is not a valid ID pattern

yahka.0
2023-06-13 08:11:38.536	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
2023-06-13 08:11:05.745	error	instance system.adapter.yahka.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.iobroker
2023-06-13 08:11:05.745	error	Caught by controller[26]: [Yahka-0 011F@Wasseralarm@Wasseralarm@Status Low Battery] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:05.744	error	Caught by controller[25]: [Yahka-0 011F@Heizung im Kinderzimmer@KZ Heizung@Status Low Battery] characteristic value expected valid finite number and received "NaN" (number)
host.iobroker
2023-06-13 08:11:05.744	error	Caught by controller[24]: [Yahka-0 011F@Heizung im Kinderzimmer@KZ Heizung@Status Low Battery] characteristic value expected valid finite number and received "NaN" (number)
host.iobroker
2023-06-13 08:11:05.744	error	Caught by controller[23]: [Yahka-0 011F@Leuchtstreifen@Leuchtstreifen@Color Temperature] characteristic was supplied illegal value: number 0 exceeded minimum of 140
host.iobroker
2023-06-13 08:11:05.744	error	Caught by controller[22]: [Yahka-0 011F@Leuchtstreifen@Leuchtstreifen@Color Temperature] characteristic was supplied illegal value: number 0 exceeded minimum of 140
host.iobroker
2023-06-13 08:11:05.744	error	Caught by controller[21]: [Yahka-0 011F@nördliches Fenster K1@nördliches Fenster K1@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:05.744	error	Caught by controller[20]: [Yahka-0 011F@südliche, rechte Fenster K3@südliche,rechteFenster K3@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:05.744	error	Caught by controller[19]: [Yahka-0 011F@südliche, linke Fenster K3@südliche,linke Fenster K3@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:05.744	error	Caught by controller[18]: [Yahka-0 011F@südliche, rechte Fenster im OG@südliche, rechte Fenster im OG@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)

VIS (V 1.4.16 ) Anzeige Web UI

File index.html not found: {}

Log File:

vis.0
2023-06-13 08:30:13.571	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

vis.0
2023-06-13 08:30:13.063	error	Not exists

vis.0
2023-06-13 08:30:13.062	error	Error: Not exists at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:856:19) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:893:59) at process.processImmediate (node:internal/timers:478:21)

vis.0
2023-06-13 08:30:13.061	error	unhandled promise rejection: Not exists

vis.0
2023-06-13 08:30:13.059	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().

mcm1957

@apollon77
FHEM sollte auch auf die Liste der bekannten Adapterinkompatibilitäten:
https://github.com/iobroker-community-adapters/ioBroker.fhem/issues/213
sieht nach Problem analog zu stiebel-isg aus

asmitconsulting created this issue in iobroker-community-adapters/ioBroker.fhem

closed [JS-Controller5] Error after Update JS-Controller - Parameter "options" needs to be a real object... #213

apollon77

@chaot Also hier bitte web issue um die Fehler besser abzufangen und ansonsten such welches Widget mit solchen Daten hantiert weil das macht was komisches und versufht scheinbar DInge abzufragen die keine State IDs sind!! Also da ist eher in deiner Vis oder einem Widget was broken!

apollon77

@merlin123 Bitte Admin issue mit der relevanten Browser Konsole Fehlermeldung ... da müsste es eine geben

apollon77

@marty56 Bitte issue in yahka anlegen und "iob upload vis" machen. Danach ok? Auch issue in vis bitte dennich mit der Fehlermeldung

ilovegym

@chaot sagte in js-controller 5.0.x jetzt in der BETA:

@apollon77
Der LGTV Adapter fällt aus wie erwartet (ist aber bei mir eher unwichtig)
Dazu kommt noch eine Fehlermeldung:

Es gibt mittlerweile einen Fork von @basti4557 vom LG Adapter, Version 1.1.11, die funktioniert auch mit js-controller 5.x einwandfrei.
https://github.com/basti4557/ioBroker.lgtvs

apollon77

@ilovegym Ist das jetzt was anderes als

lgtv from https://github.com/foxriver76/ioBroker.lgtv nutzen bis Entwickler angepasst hat ?!

ilovegym

@apollon77

eine Weiterentwicklung von @foxriver76 da LG Änderungen gemacht hat..

haselchen

@apollon77
@foxriver76

2023-06-12 22:36:40.964 - warn: hue.0 (452) Unknown update for type "button": {"button":{"button_report":{"event":"short_release","updated":"2023-06-12T20:36:39.955Z"},"last_event":"short_release"},"id":"a3ffd014-1ce6-465f-b2ca-610336764b10","id_v1":"/sensors/72","owner":{"rid":"5e33ed7a-aef2-40ab-a1e2-11d1fdeb9e46","rtype":"device"},"type":"button"}
2023-06-12 22:36:40.964 - warn: hue.0 (452) Unknown update for type "button": {"button":{"button_report":{"event":"initial_press","updated":"2023-06-12T20:36:40.709Z"},"last_event":"initial_press"},"id":"b427bb8c-c890-42ab-beac-364383ef9378","id_v1":"/sensors/98","owner":{"rid":"ebc2d5e7-a972-4fd7-9290-45b2fa7c5562","rtype":"device"},"type":"button"}
2023-06-12 22:36:40.964 - warn: hue.0 (452) Unknown update for type "button": {"button":{"button_report":{"event":"short_release","updated":"2023-06-12T20:36:40.839Z"},"last_event":"short_release"},"id":"b427bb8c-c890-42ab-beac-364383ef9378","id_v1":"/sensors/98","owner":{"rid":"ebc2d5e7-a972-4fd7-9290-45b2fa7c5562","rtype":"device"},"type":"button"}
2023-06-12 22:36:54.785 - warn: hue.0 (452) Unknown update for type "button": {"button":{"button_report":{"event":"initial_press","updated":"2023-06-12T20:36:54.587Z"},"last_event":"initial_press"},"id":"b427bb8c-c890-42ab-beac-364383ef9378","id_v1":"/sensors/98","owner":{"rid":"ebc2d5e7-a972-4fd7-9290-45b2fa7c5562","rtype":"device"},"type":"button"}
2023-06-12 22:36:54.785 - warn: hue.0 (452) Unknown update for type "button": {"button":{"button_report":{"event":"short_release","updated":"2023-06-12T20:36:54.723Z"},"last_event":"short_release"},"id":"b427bb8c-c890-42ab-beac-364383ef9378","id_v1":"/sensors/98","owner":{"rid":"ebc2d5e7-a972-4fd7-9290-45b2fa7c5562","rtype":"device"},"type":"button"}

2023-06-12 11:52:17.705 - warn: ws.0 (845) Information for Developer: Using the direct "Let's encrypt" module import is deprecated and will be removed in the next js-controller version, use @iobroker/webserver instead

2023-06-12 22:23:08.219 - warn: shelly.0 (536) [http controlFunction] Unable to perform request - device 192.168.2.66 (shelly1 / shelly1- / SHSW-1##1) is offline
2023-06-12 22:23:12.210 - warn: shelly.0 (536) [http controlFunction] Unable to perform request - device 192.168.2.66 (shelly1 / shelly1- / SHSW-1##1) is offline
2023-06-12 22:23:15.311 - warn: shelly.0 (536) [http controlFunction] Unable to perform request - device 192.168.2.66 (shelly1 / shelly1- / SHSW-1##1) is offline
2023-06-12 22:23:17.289 - warn: shelly.0 (536) [http controlFunction] Unable to perform request - device 192.168.2.66 (shelly1 / shelly1- / SHSW-1##1) is offline
2023-06-12 22:23:18.341 - warn: shelly.0 (536) [http controlFunction] Unable to perform request - device 192.168.2.66 (shelly1 / shelly1- / SHSW-1##1) is offline
2023-06-12 22:23:45.705 - warn: shelly.0 (536) [http controlFunction] Unable to perform request - device 192.168.2.66 (shelly1 / shelly1- / SHSW-1##1) is offline

HUE Adapter 3.9.0
Shelly Adapter 6.4.1
WS Adapter 2.3.6

Weil das Log durchgehend mit den Warnmeldungen vollgespamt wurde, bin ich zurück auf 4.0.24
Ich weiß, es sind nur Warnmeldungen, aber ich möchte schon sehen, was da im System los ist.
Das sind leider nur Auszüge, die ich noch retten konnte, ich meine der Sonoff Adapter war auch dabei mit Warnmeldungen.

Edit: Die/der Shelly war nicht offline. War ganz normal zu erreichen.

foxriver76

@haselchen Hue Warnmeldungen kommen von hue 3.9.0 unabhängig von Controller

NEWS

js-controller 5.0.x jetzt in der BETA

closed [JS-Controller5] Error after Update JS-Controller - Parameter "options" needs to be a real object... #213

Support us

1.6k
Online

30.5k
Users

76.8k
Topics

1.2m
Posts

NEWS

js-controller 5.0.x jetzt in der BETA

closed [JS-Controller5] Error after Update JS-Controller - Parameter "options" needs to be a real object... #213

Support us

1.6kOnline

30.5kUsers

76.8kTopics

1.2mPosts

1.6k
Online

30.5k
Users

76.8k
Topics

1.2m
Posts