NEWS
Anfrage Tahoma/Somfy IO Adapter
-
@puls200 Connexoon ist die Schuldige. Dort gibt es weder den Enwicklermodus noch die lokale Api. Als ich den Pin im iobroker eingetragen habe, konnte ich mich auch nicht mehr verbinden. Selbst als ich ihn dann wieder rausgenommen habe.
Wie ich es letztlich lösen konnte, kann ich dir aber nicht sagen, da ich den broker in eier virtuellen Maschine hoste und somit einfach ein Backup aus der Nacht einspielen konnte.
ps: Gestern ging die Verbindung auch nicht mehr, musste die Box updaten, dann ging der login wieder. -
@murphys234d Bei Version 0.7.1 gibt es einen Bug, bei dem nach dem Löschen der PIN der Zugriff auf die Online-API nicht möglich ist. Das ist mit 0.7.2 (aktuell nur im Beta-Repo) behoben.
@excodibur Super! Herzlichen Dank für die schnelle Hilfe. Es scheint geklappt zu haben, (den PIN hatte ich mir ja schon bei meinen ersten Versuchen besorgt) jedenfalls hab ich im Log den Eintrag "Adapter will connect to Tahoma Box via local API." und anschliessend: "Using stored bearer token 62..." und eine EventRegisterID. Ich nehme mal an, dass das gute Anzeichen sind dass ich nun via die lokale API darauf zugreife.
Ein Problem scheine ich aber bei Somfy noch zu haben. Wenn ich mich auf Somfy.de einloggen will, kriege ich eine ellenlange Fehlermeldung bei welcher fast zuoberst der Eintrag "Message: JSON parsing failure at character 1:'Y' in You exceeded the rate limit" steht. Was bedeutet das genau? (Über tahomalink kann ich mich einloggen und der Adapter scheint auch ok zu sein)
-
@excodibur Super! Herzlichen Dank für die schnelle Hilfe. Es scheint geklappt zu haben, (den PIN hatte ich mir ja schon bei meinen ersten Versuchen besorgt) jedenfalls hab ich im Log den Eintrag "Adapter will connect to Tahoma Box via local API." und anschliessend: "Using stored bearer token 62..." und eine EventRegisterID. Ich nehme mal an, dass das gute Anzeichen sind dass ich nun via die lokale API darauf zugreife.
Ein Problem scheine ich aber bei Somfy noch zu haben. Wenn ich mich auf Somfy.de einloggen will, kriege ich eine ellenlange Fehlermeldung bei welcher fast zuoberst der Eintrag "Message: JSON parsing failure at character 1:'Y' in You exceeded the rate limit" steht. Was bedeutet das genau? (Über tahomalink kann ich mich einloggen und der Adapter scheint auch ok zu sein)
-
@lucky256 Ja, die gleiche Fehlermeldung kriege ich im Moment auch. Scheint mir aber ein Server-seitiges Problem (gibt es ja schonmal öfters bei Somfy :face_with_rolling_eyes: ) zu sein.
@excodibur Das ist ja "beruhigend" ... ;-)
Ich hab mir nun mal das Log etwas genauer angeschaut und dabei gesehen, dass es Warnmeldungen bei meinen Somfy Lichtschaltern gibt, bei welchen ich vermute, dass die vom Adapter aus kommen. In meinen Skripten nutze ich den State core:ManufacturerSettingsState.wired_input_type eigentlich nicht. Ist zwar nur ne info, ist aber ev. etwas, das sich leicht korrigieren lässt?2022-06-25 13:05:22.115 - info: host.ds-iobroker stopInstance system.adapter.tahoma.0 (force=false, process=true) 2022-06-25 13:05:22.161 - info: tahoma.0 (653102) Got terminate signal TERMINATE_YOURSELF 2022-06-25 13:05:22.161 - info: host.ds-iobroker stopInstance system.adapter.tahoma.0 send kill signal 2022-06-25 13:05:22.164 - info: tahoma.0 (653102) terminating 2022-06-25 13:05:22.165 - info: tahoma.0 (653102) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2022-06-25 13:05:22.783 - info: host.ds-iobroker instance system.adapter.tahoma.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2022-06-25 13:05:25.305 - info: host.ds-iobroker instance system.adapter.tahoma.0 started with pid 656416 2022-06-25 13:05:25.663 - info: host.ds-iobroker instance system.adapter.mobile-alerts.0 terminated with code 0 (NO_ERROR) 2022-06-25 13:05:28.350 - info: tahoma.0 (656416) starting. Version 0.7.2 in /opt/iobroker/node_modules/iobroker.tahoma, node: v14.19.0, js-controller: 4.0.23 2022-06-25 13:05:28.407 - info: tahoma.0 (656416) [START] Starting adapter tahoma v0.7.2.3 2022-06-25 13:05:28.410 - info: tahoma.0 (656416) Configured polling interval: 60000 2022-06-25 13:05:28.416 - info: tahoma.0 (656416) Adapter will connect to Tahoma Box via local API. 2022-06-25 13:05:28.421 - info: tahoma.0 (656416) Using stored bearer token 62b494e200422b6a4b38 2022-06-25 13:05:31.337 - info: tahoma.0 (656416) eventRegisterID = 04186a9f-8124-4bc3-b36e-a121903ad04f 2022-06-25 13:08:31.413 - info: tahoma.0 (656416) State value to set for "tahoma.0.devices.Gartenbeleuchtung.states.core:ManufacturerSettingsState.wired_input_type" has to be type "string" but received type "object" 2022-06-25 13:08:31.420 - info: tahoma.0 (656416) State value to set for "tahoma.0.devices.Gartenbeleuchtung.states.core:ManufacturerSettingsState.wired_input_type" has to be type "string" but received type "object" 2022-06-25 13:08:31.426 - info: tahoma.0 (656416) State value to set for "tahoma.0.devices.Frühbeet_HQI.states.core:ManufacturerSettingsState.wired_input_type" has to be type "string" but received type "object" 2022-06-25 13:08:31.432 - info: tahoma.0 (656416) State value to set for "tahoma.0.devices.Frühbeet_HQI.states.core:ManufacturerSettingsState.wired_input_type" has to be type "string" but received type "object" 2022-06-25 13:08:31.439 - info: tahoma.0 (656416) State value to set for "tahoma.0.devices.Sitzplatzbeleuchtung.states.core:ManufacturerSettingsState.wired_input_type" has to be type "string" but received type "object" 2022-06-25 13:08:31.444 - info: tahoma.0 (656416) State value to set for "tahoma.0.devices.Sitzplatzbeleuchtung.states.core:ManufacturerSettingsState.wired_input_type" has to be type "string" but received type "object"Hast du ev. eine Idee, wie ich das korrigieren kann? Danke schon mal
-
@excodibur Das ist ja "beruhigend" ... ;-)
Ich hab mir nun mal das Log etwas genauer angeschaut und dabei gesehen, dass es Warnmeldungen bei meinen Somfy Lichtschaltern gibt, bei welchen ich vermute, dass die vom Adapter aus kommen. In meinen Skripten nutze ich den State core:ManufacturerSettingsState.wired_input_type eigentlich nicht. Ist zwar nur ne info, ist aber ev. etwas, das sich leicht korrigieren lässt?2022-06-25 13:05:22.115 - info: host.ds-iobroker stopInstance system.adapter.tahoma.0 (force=false, process=true) 2022-06-25 13:05:22.161 - info: tahoma.0 (653102) Got terminate signal TERMINATE_YOURSELF 2022-06-25 13:05:22.161 - info: host.ds-iobroker stopInstance system.adapter.tahoma.0 send kill signal 2022-06-25 13:05:22.164 - info: tahoma.0 (653102) terminating 2022-06-25 13:05:22.165 - info: tahoma.0 (653102) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2022-06-25 13:05:22.783 - info: host.ds-iobroker instance system.adapter.tahoma.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2022-06-25 13:05:25.305 - info: host.ds-iobroker instance system.adapter.tahoma.0 started with pid 656416 2022-06-25 13:05:25.663 - info: host.ds-iobroker instance system.adapter.mobile-alerts.0 terminated with code 0 (NO_ERROR) 2022-06-25 13:05:28.350 - info: tahoma.0 (656416) starting. Version 0.7.2 in /opt/iobroker/node_modules/iobroker.tahoma, node: v14.19.0, js-controller: 4.0.23 2022-06-25 13:05:28.407 - info: tahoma.0 (656416) [START] Starting adapter tahoma v0.7.2.3 2022-06-25 13:05:28.410 - info: tahoma.0 (656416) Configured polling interval: 60000 2022-06-25 13:05:28.416 - info: tahoma.0 (656416) Adapter will connect to Tahoma Box via local API. 2022-06-25 13:05:28.421 - info: tahoma.0 (656416) Using stored bearer token 62b494e200422b6a4b38 2022-06-25 13:05:31.337 - info: tahoma.0 (656416) eventRegisterID = 04186a9f-8124-4bc3-b36e-a121903ad04f 2022-06-25 13:08:31.413 - info: tahoma.0 (656416) State value to set for "tahoma.0.devices.Gartenbeleuchtung.states.core:ManufacturerSettingsState.wired_input_type" has to be type "string" but received type "object" 2022-06-25 13:08:31.420 - info: tahoma.0 (656416) State value to set for "tahoma.0.devices.Gartenbeleuchtung.states.core:ManufacturerSettingsState.wired_input_type" has to be type "string" but received type "object" 2022-06-25 13:08:31.426 - info: tahoma.0 (656416) State value to set for "tahoma.0.devices.Frühbeet_HQI.states.core:ManufacturerSettingsState.wired_input_type" has to be type "string" but received type "object" 2022-06-25 13:08:31.432 - info: tahoma.0 (656416) State value to set for "tahoma.0.devices.Frühbeet_HQI.states.core:ManufacturerSettingsState.wired_input_type" has to be type "string" but received type "object" 2022-06-25 13:08:31.439 - info: tahoma.0 (656416) State value to set for "tahoma.0.devices.Sitzplatzbeleuchtung.states.core:ManufacturerSettingsState.wired_input_type" has to be type "string" but received type "object" 2022-06-25 13:08:31.444 - info: tahoma.0 (656416) State value to set for "tahoma.0.devices.Sitzplatzbeleuchtung.states.core:ManufacturerSettingsState.wired_input_type" has to be type "string" but received type "object"Hast du ev. eine Idee, wie ich das korrigieren kann? Danke schon mal
@excodibur und diese Warnung erhalte ich ebenfalls. Hat das ev einen Zusammenhang?
2022-06-25 13:14:31.561 - warn: tahoma.0 (656416) error during request: null, request path: history/executions/82a707c7-60b2-4059-b9d5-c1604f053590 with payload:{} 2022-06-25 13:14:31.570 - warn: tahoma.0 (656416) Response: {"statusCode":400,"body":"{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}","headers":{"content-type":"application/json","access-control-allow-origin":"*","access-control-allow-headers":"Authorization","content-length":"59","connection":"close","date":"Sat, 25 Jun 2022 11:14:31 GMT","server":"KizOs"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"gateway-1224-3740-5129.local:8443","port":"8443","hostname":"gateway-1224-3740-5129.local","hash":null,"search":null,"query":null,"pathname":"/enduser-mobile-web/1/enduserAPI/history/executions/82a707c7-60b2-4059-b9d5-c1604f053590","path":"/enduser-mobile-web/1/enduserAPI/history/executions/82a707c7-60b2-4059-b9d5-c1604f053590","href":"https://gateway-1224-3740-5129.local:8443/enduser-mobile-web/1/enduserAPI/history/executions/82a707c7-60b2-4059-b9d5-c1604f053590"},"method":"GET","headers":{"User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0","Authorization":"Bearer 62b494e200422b6a4b38","Content-type":"application/json"}}} 2022-06-25 13:14:31.576 - warn: tahoma.0 (656416) Body: "{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}" 2022-06-25 13:14:31.577 - warn: tahoma.0 (656416) Failed getting execution state for 82a707c7-60b2-4059-b9d5-c1604f053590 -
@murphys234d Bei Version 0.7.1 gibt es einen Bug, bei dem nach dem Löschen der PIN der Zugriff auf die Online-API nicht möglich ist. Das ist mit 0.7.2 (aktuell nur im Beta-Repo) behoben.
@excodibur ah, danke für die Info.
ps. ansonsten bin ich mit dem Adapter rundum glücklich :+1: . Wenn es Probleme gibt, liegt es eigentlich immer an Somfy. Auch deshalb bin ich schwer am überlegen, von connexoon auf Tahoma (switch) zu wechseln um dann die lokale api zu nutzen -
@excodibur ah, danke für die Info.
ps. ansonsten bin ich mit dem Adapter rundum glücklich :+1: . Wenn es Probleme gibt, liegt es eigentlich immer an Somfy. Auch deshalb bin ich schwer am überlegen, von connexoon auf Tahoma (switch) zu wechseln um dann die lokale api zu nutzenHi, hab mir jetzt auch mal die neuste Beta Version drauf gemacht, bekomme auch den Fehler und der Adapter wird irgendwann mal beendet und muss wieder manuell neu gestartet werden. Ich habe keine Lichtschalter, nur Motoren im Betrieb. Kann ich etwas loggen und damit @Excodibur weiterhelfen den Fehler zu finden? Somfy hat diese Woche ja ein neues Update für die Box raus gebracht und vermutlich wieder an der API etwas geändert. Gib bescheid, wenn ich etwas tun kann, bin aber leider kein programmierer und kenne mich damit nicht aus. Testen kann ich aber :-)
Vielen Dank nochmal, dass du den Adapter wieder belebt hast :+1:host.raspberrypi 2022-06-26 02:48:58.795 warn Do not restart adapter system.adapter.tahoma.0 because restart loop detected host.raspberrypi 2022-06-26 02:48:58.795 info Restart adapter system.adapter.tahoma.0 because enabled host.raspberrypi 2022-06-26 02:48:58.794 error instance system.adapter.tahoma.0 terminated with code 6 (UNCAUGHT_EXCEPTION) tahoma.0 2022-06-26 02:48:58.130 error The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-06-26 02:48:58.130 error Error: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5669:23) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5752:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.tahoma/lib/tahoma.js:1317:36) at processImmediate (internal/timers.js:463:21) tahoma.0 2022-06-26 02:48:58.129 error unhandled promise rejection: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-06-26 02:48:58.128 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(). tahoma.0 2022-06-26 02:48:58.125 warn Terminated (UNCAUGHT_EXCEPTION): Without reason tahoma.0 2022-06-26 02:48:58.124 info terminating tahoma.0 2022-06-26 02:48:58.118 error The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-06-26 02:48:58.117 error Error: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5669:23) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5752:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.tahoma/lib/tahoma.js:1317:36) at processImmediate (internal/timers.js:463:21) tahoma.0 2022-06-26 02:48:58.109 error unhandled promise rejection: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-06-26 02:48:58.107 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(). tahoma.0 2022-06-26 02:40:38.076 info eventRegisterID = 10b7c50d-2db3-45ef-xxxx-cd81473454b7 tahoma.0 2022-06-26 02:40:37.878 info State value to set for "tahoma.0.devices.4__Balkontüre.states.core:ManufacturerSettingsState.open_level" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:40:37.877 info State value to set for "tahoma.0.devices.4__Balkontüre.states.core:ManufacturerSettingsState.smart_protect" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:40:37.876 info State value to set for "tahoma.0.devices.4__Balkontüre.states.core:ManufacturerSettingsState.security_level" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:40:37.874 info State value to set for "tahoma.0.devices.3__Esszimmer.states.core:ManufacturerSettingsState.open_level" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:40:37.872 info State value to set for "tahoma.0.devices.3__Esszimmer.states.core:ManufacturerSettingsState.smart_protect" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:40:37.866 info State value to set for "tahoma.0.devices.3__Esszimmer.states.core:ManufacturerSettingsState.security_level" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:40:37.862 info State value to set for "tahoma.0.devices.5__Wohnzimmer.states.core:ManufacturerSettingsState.open_level" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:40:37.860 info State value to set for "tahoma.0.devices.5__Wohnzimmer.states.core:ManufacturerSettingsState.security_level" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:40:36.753 info Using stored bearer token 6263c4b71f21561axxxx tahoma.0 2022-06-26 02:40:36.750 info Adapter will connect to Tahoma Box via local API. tahoma.0 2022-06-26 02:40:36.747 info Configured polling interval: 500000 tahoma.0 2022-06-26 02:40:36.746 info [START] Starting adapter tahoma v0.7.2.3 tahoma.0 2022-06-26 02:40:36.708 info starting. Version 0.7.2 (non-npm: Excodibur/ioBroker.tahoma) in /opt/iobroker/node_modules/iobroker.tahoma, node: v12.22.12, js-controller: 4.0.23 host.raspberrypi 2022-06-26 02:40:34.552 info instance system.adapter.tahoma.0 started with pid 27510 host.raspberrypi 2022-06-26 02:40:04.372 info Restart adapter system.adapter.tahoma.0 because enabled host.raspberrypi 2022-06-26 02:40:04.371 error instance system.adapter.tahoma.0 terminated with code 6 (UNCAUGHT_EXCEPTION) tahoma.0 2022-06-26 02:40:03.769 error The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-06-26 02:40:03.769 error Error: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5669:23) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5752:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.tahoma/lib/tahoma.js:1317:36) at processImmediate (internal/timers.js:463:21) tahoma.0 2022-06-26 02:40:03.768 error unhandled promise rejection: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-06-26 02:40:03.768 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(). tahoma.0 2022-06-26 02:40:03.765 warn Terminated (UNCAUGHT_EXCEPTION): Without reason tahoma.0 2022-06-26 02:40:03.762 info terminating tahoma.0 2022-06-26 02:40:03.753 error The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-06-26 02:40:03.752 error Error: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5669:23) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5752:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.tahoma/lib/tahoma.js:1317:36) at processImmediate (internal/timers.js:463:21) tahoma.0 2022-06-26 02:40:03.744 error unhandled promise rejection: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-06-26 02:40:03.742 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(). tahoma.0 2022-06-26 02:31:43.853 info eventRegisterID = 73427a7f-921b-464e-8678-c2376e8f9d28 tahoma.0 2022-06-26 02:31:43.513 info State value to set for "tahoma.0.devices.4__Balkontüre.states.core:ManufacturerSettingsState.open_level" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:31:43.511 info State value to set for "tahoma.0.devices.4__Balkontüre.states.core:ManufacturerSettingsState.smart_protect" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:31:43.510 info State value to set for "tahoma.0.devices.4__Balkontüre.states.core:ManufacturerSettingsState.security_level" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:31:43.502 info State value to set for "tahoma.0.devices.3__Esszimmer.states.core:ManufacturerSettingsState.open_level" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:31:43.500 info State value to set for "tahoma.0.devices.3__Esszimmer.states.core:ManufacturerSettingsState.smart_protect" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:31:43.485 info State value to set for "tahoma.0.devices.3__Esszimmer.states.core:ManufacturerSettingsState.security_level" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:31:43.484 info State value to set for "tahoma.0.devices.5__Wohnzimmer.states.core:ManufacturerSettingsState.open_level" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:31:43.482 info State value to set for "tahoma.0.devices.5__Wohnzimmer.states.core:ManufacturerSettingsState.security_level" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:31:42.302 info Using stored bearer token 6263c4b71f21561a9245 tahoma.0 2022-06-26 02:31:42.298 info Adapter will connect to Tahoma Box via local API. tahoma.0 2022-06-26 02:31:42.295 info Configured polling interval: 500000 tahoma.0 2022-06-26 02:31:42.294 info [START] Starting adapter tahoma v0.7.2.3 tahoma.0 2022-06-26 02:31:42.255 info starting. Version 0.7.2 (non-npm: Excodibur/ioBroker.tahoma) in /opt/iobroker/node_modules/iobroker.tahoma, node: v12.22.12, js-controller: 4.0.23 host.raspberrypi 2022-06-26 02:31:40.098 info instance system.adapter.tahoma.0 started with pid 27068 host.raspberrypi 2022-06-26 02:31:09.938 info Restart adapter system.adapter.tahoma.0 because enabled host.raspberrypi 2022-06-26 02:31:09.936 error instance system.adapter.tahoma.0 terminated with code 6 (UNCAUGHT_EXCEPTION) tahoma.0 2022-06-26 02:31:09.257 warn Terminated (UNCAUGHT_EXCEPTION): Without reason tahoma.0 2022-06-26 02:31:09.255 info terminating tahoma.0 2022-06-26 02:31:09.247 error The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-06-26 02:31:09.247 error Error: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5669:23) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5752:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.tahoma/lib/tahoma.js:1317:36) at processImmediate (internal/timers.js:463:21) tahoma.0 2022-06-26 02:31:09.242 error unhandled promise rejection: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-06-26 02:31:09.239 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(). tahoma.0 2022-06-26 02:06:09.189 info eventRegisterID = 43f47f50-5e67-4a5a-b4e3-90e0a4a90e34 tahoma.0 2022-06-26 02:06:08.968 info State value to set for "tahoma.0.devices.4__Balkontüre.states.core:ManufacturerSettingsState.open_level" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:06:08.964 info State value to set for "tahoma.0.devices.4__Balkontüre.states.core:ManufacturerSettingsState.smart_protect" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:06:08.962 info State value to set for "tahoma.0.devices.4__Balkontüre.states.core:ManufacturerSettingsState.security_level" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:06:08.961 info State value to set for "tahoma.0.devices.3__Esszimmer.states.core:ManufacturerSettingsState.open_level" has to be type "number" but received type "string" tahoma.0 2022-06-26 02:06:08.936 info State value to set for "tahoma.0.devices.3__Esszimmer.states.core:ManufacturerSettingsState.smart_protect" has to be type "number" but received type "string" -
@murphys234d Bei Version 0.7.1 gibt es einen Bug, bei dem nach dem Löschen der PIN der Zugriff auf die Online-API nicht möglich ist. Das ist mit 0.7.2 (aktuell nur im Beta-Repo) behoben.
@excodibur sagte in Anfrage Tahoma/Somfy IO Adapter:
Das ist mit 0.7.2 (aktuell nur im Beta-Repo) behoben.
Kann man schon sagen, wann die Version aus dem Beta raus kommt?
-
@excodibur sagte in Anfrage Tahoma/Somfy IO Adapter:
Das ist mit 0.7.2 (aktuell nur im Beta-Repo) behoben.
Kann man schon sagen, wann die Version aus dem Beta raus kommt?
Du könntest dir auch die Beta installieren und testen. Expertenmodus - Installieren aus eigender URL - von Github
-
@Excodibur
Weiß nicht ob dir das hilft, hänge hier mal etwas ran.
tahoma.0 2022-06-27 02:49:08.680 error The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-06-27 02:49:08.680 error Error: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5669:23) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5752:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.tahoma/lib/tahoma.js:1317:36) at processImmediate (internal/timers.js:463:21) tahoma.0 2022-06-27 02:49:08.674 error unhandled promise rejection: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-06-27 02:49:08.673 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(). -
@willi-wunder Du kannst mir gerne nochmal DEBUG-Logs (inkl. Adapter Neustart schicken, dann kann ich mal schauen.
@Murphys234d Das Release ins Stable-Repo dauert noch etwas. Aktuell gibt es noch einige Probleme mit dem Adapter und der lokalen API (hauptsächlich "Unknown Object", was mit fehlenden API-Funktionen zusammenhängt), die erst behoben werden sollten, aber doch etwas aufwändiger sind.
-
@puls200 Connexoon ist die Schuldige. Dort gibt es weder den Enwicklermodus noch die lokale Api. Als ich den Pin im iobroker eingetragen habe, konnte ich mich auch nicht mehr verbinden. Selbst als ich ihn dann wieder rausgenommen habe.
Wie ich es letztlich lösen konnte, kann ich dir aber nicht sagen, da ich den broker in eier virtuellen Maschine hoste und somit einfach ein Backup aus der Nacht einspielen konnte.
ps: Gestern ging die Verbindung auch nicht mehr, musste die Box updaten, dann ging der login wieder.@murphys234d Hi... was heisst das jetzt? Müsste es theoretisch mit der Connexoon Box auch funktionieren?
Ich bin nun von der Connexoon-App zur Tahoma-App gewechselt. Soweit geht auch alles über die Tahoma App. Der Adapter hat eine Verbindung zur Connexoon Box aber weiterhin kann ich die Jalousien nicht ansprechen, egal, ob ich die PIN eingebe oder nicht.
Und noch was anderes: falls die Connexoon Box nun nicht mehr mit dem Adapter funktioniert: sind sowohl die Tahoma Box als auch das Connectivity Kit kompatibel mit dem Adapter (Unterschiede siehe HIER). Und dann gibt es ja noch die Tahoma Switch. Oder wurde die Tahoma Box mit der Switch ersetzt? Mir ist das Update etwas schleierhaft...
-
@murphys234d Hi... was heisst das jetzt? Müsste es theoretisch mit der Connexoon Box auch funktionieren?
Ich bin nun von der Connexoon-App zur Tahoma-App gewechselt. Soweit geht auch alles über die Tahoma App. Der Adapter hat eine Verbindung zur Connexoon Box aber weiterhin kann ich die Jalousien nicht ansprechen, egal, ob ich die PIN eingebe oder nicht.
Und noch was anderes: falls die Connexoon Box nun nicht mehr mit dem Adapter funktioniert: sind sowohl die Tahoma Box als auch das Connectivity Kit kompatibel mit dem Adapter (Unterschiede siehe HIER). Und dann gibt es ja noch die Tahoma Switch. Oder wurde die Tahoma Box mit der Switch ersetzt? Mir ist das Update etwas schleierhaft...
@puls200
Ich habe auch eine Connexoon und bin letzte Woche von der Connexoon App auf die Tahoma App gewechselt.
Aktuell habe ich die Adapterversion 0.7.2 im Einsatz und kann weiterhin meine Rollladen über die Connexoon Box und den Adapter steuern.
Lediglich eine lokale API bietet die Connexoon (noch) nicht, vielleicht kommt da ja noch was, die Hoffnung stirbt zuletzt. -
@puls200
Ich habe auch eine Connexoon und bin letzte Woche von der Connexoon App auf die Tahoma App gewechselt.
Aktuell habe ich die Adapterversion 0.7.2 im Einsatz und kann weiterhin meine Rollladen über die Connexoon Box und den Adapter steuern.
Lediglich eine lokale API bietet die Connexoon (noch) nicht, vielleicht kommt da ja noch was, die Hoffnung stirbt zuletzt.@blackeagle998 Wie komme ich denn an die Version 0.7.2? Bei mir ist die 0.7.1 installiert, aber ioBroker bietet mir keine aktuellere Version an.
-
@blackeagle998 Wie komme ich denn an die Version 0.7.2? Bei mir ist die 0.7.1 installiert, aber ioBroker bietet mir keine aktuellere Version an.
@puls200
Schau mal bitte in den ioBroker Einstellungen, Reiter "Repositories", ob da stable oder Beta (latest) angehakt ist?
-
@puls200
Schau mal bitte in den ioBroker Einstellungen, Reiter "Repositories", ob da stable oder Beta (latest) angehakt ist?
-
@willi-wunder Du kannst mir gerne nochmal DEBUG-Logs (inkl. Adapter Neustart schicken, dann kann ich mal schauen.
@Murphys234d Das Release ins Stable-Repo dauert noch etwas. Aktuell gibt es noch einige Probleme mit dem Adapter und der lokalen API (hauptsächlich "Unknown Object", was mit fehlenden API-Funktionen zusammenhängt), die erst behoben werden sollten, aber doch etwas aufwändiger sind.
-
@Excodibur
PN hat nicht geklappt, hab keine Adresse gefunden........Hab aber gerade wieder den Fehler im Log, vielleicht reicht das auch schon, ansonsten kann ich dir gerne die anderen Dateien noch schicken.tahoma.0 2022-07-02 01:09:48.188 info eventRegisterID = 221bef9d-1c57-4d26-8ba3-005b34dxxxxx tahoma.0 2022-07-02 01:09:46.343 info Using stored bearer token 6263c4b71f21561xxxxx tahoma.0 2022-07-02 01:09:46.340 info Adapter will connect to Tahoma Box via local API. tahoma.0 2022-07-02 01:09:46.337 info Configured polling interval: 500000 tahoma.0 2022-07-02 01:09:46.336 info [START] Starting adapter tahoma v0.7.2.3 tahoma.0 2022-07-02 01:09:46.300 info starting. Version 0.7.2 (non-npm: Excodibur/ioBroker.tahoma) in /opt/iobroker/node_modules/iobroker.tahoma, node: v12.22.12, js-controller: 4.0.23 host.raspberrypi 2022-07-02 01:09:44.086 info instance system.adapter.tahoma.0 started with pid 27807 host.raspberrypi 2022-07-02 01:09:13.866 info Restart adapter system.adapter.tahoma.0 because enabled host.raspberrypi 2022-07-02 01:09:13.864 error instance system.adapter.tahoma.0 terminated with code 6 (UNCAUGHT_EXCEPTION) tahoma.0 2022-07-02 01:09:13.254 error The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 01:09:13.254 error Error: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5669:23) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5752:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.tahoma/lib/tahoma.js:1317:36) at processImmediate (internal/timers.js:463:21) tahoma.0 2022-07-02 01:09:13.253 error unhandled promise rejection: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 01:09:13.252 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(). tahoma.0 2022-07-02 01:09:13.250 error The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 01:09:13.249 error Error: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5669:23) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5752:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.tahoma/lib/tahoma.js:1317:36) at processImmediate (internal/timers.js:463:21) tahoma.0 2022-07-02 01:09:13.248 error unhandled promise rejection: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 01:09:13.247 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(). tahoma.0 2022-07-02 01:09:13.242 warn Terminated (UNCAUGHT_EXCEPTION): Without reason tahoma.0 2022-07-02 01:09:13.240 info terminating tahoma.0 2022-07-02 01:09:13.236 error The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 01:09:13.236 error Error: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5669:23) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5752:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.tahoma/lib/tahoma.js:1317:36) at processImmediate (internal/timers.js:463:21) tahoma.0 2022-07-02 01:09:13.234 error unhandled promise rejection: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 01:09:13.233 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(). tahoma.0 2022-07-02 01:09:13.227 error The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 01:09:13.226 error Error: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5669:23) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5752:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.tahoma/lib/tahoma.js:1317:36) at processImmediate (internal/timers.js:463:21) tahoma.0 2022-07-02 01:09:13.220 error unhandled promise rejection: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 01:09:13.219 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(). tahoma.0 2022-07-02 01:00:53.155 info eventRegisterID = 90020fb6-eea8-4b6d-a51c-c8870f5xxxxxx tahoma.0 2022-07-02 01:00:51.366 info Using stored bearer token 6263c4b71f21561xxxxx tahoma.0 2022-07-02 01:00:51.363 info Adapter will connect to Tahoma Box via local API. tahoma.0 2022-07-02 01:00:51.360 info Configured polling interval: 500000 tahoma.0 2022-07-02 01:00:51.359 info [START] Starting adapter tahoma v0.7.2.3 tahoma.0 2022-07-02 01:00:51.323 info starting. Version 0.7.2 (non-npm: Excodibur/ioBroker.tahoma) in /opt/iobroker/node_modules/iobroker.tahoma, node: v12.22.12, js-controller: 4.0.23 host.raspberrypi 2022-07-02 01:00:49.003 info instance system.adapter.tahoma.0 started with pid 27411 host.raspberrypi 2022-07-02 01:00:18.879 info Restart adapter system.adapter.tahoma.0 because enabled host.raspberrypi 2022-07-02 01:00:18.878 error instance system.adapter.tahoma.0 terminated with code 6 (UNCAUGHT_EXCEPTION) tahoma.0 2022-07-02 01:00:18.224 warn Terminated (UNCAUGHT_EXCEPTION): Without reason tahoma.0 2022-07-02 01:00:18.223 info terminating tahoma.0 2022-07-02 01:00:18.221 error The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 01:00:18.221 error Error: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5669:23) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5752:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.tahoma/lib/tahoma.js:1317:36) at processImmediate (internal/timers.js:463:21) tahoma.0 2022-07-02 01:00:18.220 error unhandled promise rejection: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 01:00:18.220 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(). tahoma.0 2022-07-02 01:00:18.219 error The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 01:00:18.219 error Error: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5669:23) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5752:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.tahoma/lib/tahoma.js:1317:36) at processImmediate (internal/timers.js:463:21) tahoma.0 2022-07-02 01:00:18.218 error unhandled promise rejection: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 01:00:18.218 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(). tahoma.0 2022-07-02 01:00:18.216 error The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 01:00:18.215 error Error: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5669:23) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5752:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.tahoma/lib/tahoma.js:1317:36) at processImmediate (internal/timers.js:463:21) tahoma.0 2022-07-02 01:00:18.209 error unhandled promise rejection: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 01:00:18.209 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(). tahoma.0 2022-07-02 00:35:18.102 info eventRegisterID = 29eff3c1-fe48-4ff3-81ba-a7927f1xxxxx tahoma.0 2022-07-02 00:35:16.296 info Using stored bearer token 6263c4b71f21561xxxxx tahoma.0 2022-07-02 00:35:16.293 info Adapter will connect to Tahoma Box via local API. tahoma.0 2022-07-02 00:35:16.290 info Configured polling interval: 500000 tahoma.0 2022-07-02 00:35:16.289 info [START] Starting adapter tahoma v0.7.2.3 tahoma.0 2022-07-02 00:35:16.253 info starting. Version 0.7.2 (non-npm: Excodibur/ioBroker.tahoma) in /opt/iobroker/node_modules/iobroker.tahoma, node: v12.22.12, js-controller: 4.0.23 host.raspberrypi 2022-07-02 00:35:14.066 info instance system.adapter.tahoma.0 started with pid 26211 host.raspberrypi 2022-07-02 00:34:43.957 info Restart adapter system.adapter.tahoma.0 because enabled host.raspberrypi 2022-07-02 00:34:43.956 error instance system.adapter.tahoma.0 terminated with code 6 (UNCAUGHT_EXCEPTION) tahoma.0 2022-07-02 00:34:43.306 warn Terminated (UNCAUGHT_EXCEPTION): Without reason tahoma.0 2022-07-02 00:34:43.305 info terminating tahoma.0 2022-07-02 00:34:43.303 error The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 00:34:43.302 error Error: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5669:23) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5752:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.tahoma/lib/tahoma.js:1317:36) at processImmediate (internal/timers.js:463:21) tahoma.0 2022-07-02 00:34:43.302 error unhandled promise rejection: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 00:34:43.301 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(). tahoma.0 2022-07-02 00:34:43.301 error The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 00:34:43.300 error Error: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5669:23) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5752:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.tahoma/lib/tahoma.js:1317:36) at processImmediate (internal/timers.js:463:21) tahoma.0 2022-07-02 00:34:43.300 error unhandled promise rejection: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 00:34:43.299 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(). tahoma.0 2022-07-02 00:34:43.298 error The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 00:34:43.297 error Error: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5669:23) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5752:21) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.tahoma/lib/tahoma.js:1317:36) at processImmediate (internal/timers.js:463:21) tahoma.0 2022-07-02 00:34:43.294 error unhandled promise rejection: The state contains the forbidden properties security_level, soft_stop, discreet_mode_speed, nominal_mode_speed, soft_start, smart_protect, unroll_end_limit_state, roll_end_limit_state, open_level, setting_state, current_position! tahoma.0 2022-07-02 00:34:43.294 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().Gruß Willi
-
Wenn ich den bei meinem Rolladen den command.down auf True stelle, fährt der Rolladen runter. Er stellt sich dann aber nicht wieder auf false, wenn er runtergefahren ist.
Nun kann ich auch keinen anderen Rolladen mehr fahren, sondern muss die adapter instanz neu starten. Dann kann ich wieder einmal fahren.Wenn ich nach dem runterfahren den down wert wieder auf false stelle geht es wieder mit dem hochfahren. Dann muss ich up wieder auf false stellen. Das geht dann ein paar mal, dann gar nicht mehr und ich muss die instanz wieder neustarten.....
Gibt es eine Anleitung um die Rolläden als button in Jarvis hinzuzufügen?
note: Nutze tahoma switch, adapter auf 0.7.2
-
Wenn ich den bei meinem Rolladen den command.down auf True stelle, fährt der Rolladen runter. Er stellt sich dann aber nicht wieder auf false, wenn er runtergefahren ist.
Nun kann ich auch keinen anderen Rolladen mehr fahren, sondern muss die adapter instanz neu starten. Dann kann ich wieder einmal fahren.Wenn ich nach dem runterfahren den down wert wieder auf false stelle geht es wieder mit dem hochfahren. Dann muss ich up wieder auf false stellen. Das geht dann ein paar mal, dann gar nicht mehr und ich muss die instanz wieder neustarten.....
Gibt es eine Anleitung um die Rolläden als button in Jarvis hinzuzufügen?
note: Nutze tahoma switch, adapter auf 0.7.2
851
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge