Neues YouTube-Video: Visualisierung im Devices-Adapter

[Palm_Maniac]

@sigi234 Genau das gleiche wie bei mir mit der 3.17.2, deshalb mußte ich wieder zurück.

[Diginix]

@apollon77 Und mir ist die 3.17.1 eben nach einer Sprachausgabe mittels announcement auf allen Echos mit diesen Meldungen abgestürzt:

2022-07-12 16:55:01.488 - warn: alexa2.0 (649312) Exception: TypeError: value.replace(...).replaceAll is not a function
2022-07-12 16:55:01.493 - error: alexa2.0 (649312) uncaught exception: value.replace(...).replaceAll is not a function
2022-07-12 16:55:01.494 - error: alexa2.0 (649312) TypeError: value.replace(...).replaceAll is not a function
    at /opt/iobroker/node_modules/iobroker.alexa2/main.js:2220:98
    at Array.forEach (<anonymous>)
    at /opt/iobroker/node_modules/iobroker.alexa2/main.js:2216:67
    at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.alexa2/main.js:2211:65)
    at processImmediate (internal/timers.js:466:21)
2022-07-12 16:55:01.494 - error: alexa2.0 (649312) value.replace(...).replaceAll is not a function
2022-07-12 16:55:01.512 - info: alexa2.0 (649312) terminating
2022-07-12 16:55:01.513 - warn: alexa2.0 (649312) Terminated (UNCAUGHT_EXCEPTION): Without reason
2022-07-12 16:55:02.080 - error: host.iobroker Caught by controller[0]: TypeError: value.replace(...).replaceAll is not a function
2022-07-12 16:55:02.083 - error: host.iobroker Caught by controller[0]:     at /opt/iobroker/node_modules/iobroker.alexa2/main.js:2220:98
2022-07-12 16:55:02.083 - error: host.iobroker Caught by controller[0]:     at Array.forEach (<anonymous>)
2022-07-12 16:55:02.083 - error: host.iobroker Caught by controller[0]:     at /opt/iobroker/node_modules/iobroker.alexa2/main.js:2216:67
2022-07-12 16:55:02.083 - error: host.iobroker Caught by controller[0]:     at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.alexa2/main.js:2211:65)
2022-07-12 16:55:02.083 - error: host.iobroker Caught by controller[0]:     at processImmediate (internal/timers.js:466:21)
2022-07-12 16:55:02.084 - error: host.iobroker instance system.adapter.alexa2.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2022-07-12 16:55:33.964 - info: alexa2.0 (652182) starting. Version 3.17.1 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.20.0, js-controller: 4.0.23
2022-07-12 16:55:34.205 - info: alexa2.0 (652182) Update History Interval is too low, set to 112s
2022-07-12 16:55:34.206 - info: alexa2.0 (652182) Update Device State Interval is too low, set to 112s
2022-07-12 16:55:39.181 - info: alexa2.0 (652182) Alexa-Push-Connection (macDms = true) established. Disable Polling
2022-07-12 16:56:37.755 - info: alexa2.0 (652182) Subscribing to states...

announcement funktioniert auch nicht mehr, weder mit "volume;text" noch mit nur "text". Dabei stürzt die Instanz immer ab. Die 3.17.2 ist aber auch unbrauchbar durch die loopenden Logmeldungen zu falschen Datentypen. ;-)

Also erstmal zurück zur 3.17.0.

[Palm_Maniac]

@apollon77 sagte in Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta):

Dann mach das doch mal :-) Der Entwickler freut sich

Stimmt, da hast du recht, das hätte ich gleich machen sollen. :)

[Palm_Maniac]

@apollon77 sagte in Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta):

@palm_maniac sagte in Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta):

Außerdem habe ich wohl den Auslöser für das Eigenleben des Lichts gefunden. Mir ist aufgefallen, dass das Treppenlicht 2mal unter Smart-Devices auftauchte mit allen Datenpunkten für RGB Beleuchtung. Das hätte so aber nicht sein dürfen, denn ich hatte dieses Licht garnicht per IOT-Adapter an Alexa übergeben. Also habe ich mir nochmal die Konfig in WLED angeschaut und gesehen, dass dort die Alexa-Unterstützung aktiviert war. Problem erkannt, Problem gebannt.

Warum es plötzlich was tut wenn nichts gesteuert wird ist dennoch strange

Ja, zumal diese Datenpunkte in keinem Skript Verwendung finden.

[apollon77]

@diginix Den hab ich auf Sentry gesehen. Fix kommt heute abend

[apollon77]

@sigi234 Hab schon ne vermutung. Fix heute abend

[Thomas Braun]

@apollon77

Das muss aber im Diff von

alexa2.git#0fd8690ca77e16285030ebbcdbce49b4c56f99a8 ist wieder leise im Log.

zum Release 3.17.2 zu finden sein.
Die quasselt mich nämlich auch im Log zu:

2022-07-12 18:15:30.770  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.4acc0e22-bfb9-4e3e-bdfe-bea4f3912910.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.771  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.d7d81c77-a50c-41cb-9c3a-0450992ae160.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.773  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.f3c8b652-2523-4cd9-b7da-2b125e973bb6.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.773  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.4e18554e-e6fe-4771-8f4e-12fc640761db.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.774  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.d359aeb1-03f5-4cde-9071-179a5924f7fa.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.775  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.0f9cec35-b064-4598-923d-963b29af18b8.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.776  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.7cd146f6-aac1-4b01-98e6-3167447f9e70.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.777  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.ca41d22b-884b-4be1-aa28-ced702d9f694.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.778  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.98257657-55fe-4a59-96ee-bcbb24ee9bc8.colorRgb" has to be type "string" but received type "object"
2022-07-12 18:15:30.814  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.98257657-55fe-4a59-96ee-bcbb24ee9bc8.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.815  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.3c24ecd2-b792-4d5f-9c25-75d7cf57a574.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.816  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.fb3ea3ff-cbdf-423a-9186-11da242e2947.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.816  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.dff78664-0a39-4ee4-aa2b-a9a8e0d7ba31.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.817  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.8bc3f37a-58a8-4d46-82e8-4d84dd10121c.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.817  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.39be3920-5d21-4742-9453-25790bcc07f5.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.818  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.e134e20d-ae41-4394-b4c7-1504ae3e4831.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.818  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.10d02cfd-be52-46a6-84ed-fcaae8db99b7.colorRgb" has to be type "string" but received type "object"
2022-07-12 18:15:30.819  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.10d02cfd-be52-46a6-84ed-fcaae8db99b7.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.820  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.5144a434-eee6-42db-a91b-3b5df7b712e5.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.820  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.3a8fa5bf-7037-4806-aecf-fea3af6070a4.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.821  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.c77e7be4-86da-4595-8223-5ceb6b50254b.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.821  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.4967049f-b2b6-42a5-a0fc-825172dad02a.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.822  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.e7ea8a09-6582-480b-a6a6-935cbbe3275e.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.823  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.81de86f1-23b0-49f6-b5d0-402c197dcba0.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.823  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.6c714265-c3e0-450a-b7e0-5acf25326e57.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.824  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.48f3f6f6-a74c-4daa-97a3-32766f03e5b1.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.824  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.141b1d14-9591-4d28-bd03-698cd0cfd970.batteryLevel" has to be type "number" but received type "object"
2022-07-12 18:15:30.825  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.141b1d14-9591-4d28-bd03-698cd0cfd970.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.825  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.60099b70-c2d2-46b7-b14d-77acc53e04f9.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.827  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.a3ab3c77-6751-458f-a7d5-0871e996c700.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.828  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.5d479e97-6965-4780-98d1-5438ccbc2371.colorRgb" has to be type "string" but received type "object"
2022-07-12 18:15:30.829  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.5d479e97-6965-4780-98d1-5438ccbc2371.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.829  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.30d44a62-ba23-4a51-a417-d4215f8e6336.connectivity-reason" has to be type "string" but received type "object"

[Megawaldi]

@apollon77
Hier das selbe Problem mit dem zugespamtem Log.

[Thomas Braun]

@megawaldi Setz das LogLevel auf 'Warning / Hinweis'.

[Megawaldi]

@thomas-braun
schon erledigt. Aber trotzdem Danke für den Tip. 😉

[Thomas Braun]

@megawaldi Danke für den #metoo-Beitrag. :-D

[Megawaldi]

@thomas-braun
Wollte nur nicht da jemand denkt es liegt an dir Thomas...

[apollon77]

@Diginix @sigi234 Version 3.17.3 mit Fix ist auf dem Weg

[sigi234]

@apollon77 sagte in Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta):

@sigi234 Hab schon ne vermutung. Fix heute abend

Log wieder Ok, Danke für den Fix.

[apollon77]

@sigi234 danke für die Bestätigung. Die Werte sind auch korrekt?! Vor allem bei den States die vorher angemeckert wurden?

[apollon77]

3.17.4 ist auf dem Weg mit einem weiteren Bugfix:

Es war nicht möglich die Query Intervalle für Smart-Home Devices, generellen State und Configuration auf 0 zu setzen aka zu deaktivieren.

[Diginix]

@apollon77 Aus der iob Facebook Gruppe:

[apollon77]

Naja ich sags mal so ... es gab einen Bug ... Alle schnellstens auf die 3.17.4 updaten!!!

Admin-Notify ist geschaltet um alle user daraf hinzuweisen. Im Forum ist auch ab gleich eine Headline

[Diginix]

@apollon77 Der Facebook User ist aber auf 3.14.0.

[apollon77]

@diginix Ok, da hats wohl mein changelog zerbröselt ... ab 3.14 ist "böse". Fixe kommunikatoon