NEWS
Anfrage Tahoma/Somfy IO Adapter
-
Yes!
Jetzt geht wieder Alles dank v0.7.2...
Vielen Dank an alle!
-
-
@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
-
@memme Ja, das ist einer der komplizierteren Bugs mit der lokalen API. Hängt mit https://github.com/Excodibur/ioBroker.tahoma/issues/149 zusammen, nur leider bin ich noch nicht dazu gekommen.
-
Wie macht ihr es denn, wenn ihr einen Repeater braucht? Der IO Somfy Repeater kostet ja mehr als die Switch. Kann man die Connexoon in die Switch einlernen und dann auch mit dem Adapter steuern? Denn die Connexoon als single wird ja nicht vom adapter unterstützt.
Und gibt es eine Jarvis Anleitung?
-
Hallo,
ich habe auch noch mal einen neuen Versuch mit der neueren Version vorgenommen, aber irgendwie komme ich nicht weiter, wie schaltet man eigentlich um, auf lokal und umgekehrt?
Hier der Log, mir sagt das alles nicht viel:
-2989-5271.local, request path: setup/gateways with payload:{} tahoma.0 2022-07-08 09:22:50.248 debug GET request on https://gateway-xxxxx-xxxxx-xxxxx.local:8443/enduser-mobile-web/1/enduserAPI/setup/gateways with payload:{} tahoma.0 2022-07-08 09:22:50.247 debug Update gateway status for id undefined tahoma.0 2022-07-08 09:22:20.245 warn error during request: Error: getaddrinfo EAI_AGAIN gateway-xxxxx-xxxxx-xxxxx.local, request path: setup/gateways with payload:{} tahoma.0 2022-07-08 09:22:10.227 debug GET request on https://gateway-xxxxx-xxxxx-xxxxx.local:8443/enduser-mobile-web/1/enduserAPI/setup/gateways with payload:{} tahoma.0 2022-07-08 09:22:10.226 debug Update gateway status for id undefined tahoma.0 2022-07-08 09:21:40.224 warn error during request: Error: getaddrinfo EAI_AGAIN gateway-xxxxx-xxxxx-xxxxx.local, request path: setup/gateways with payload:{} tahoma.0 2022-07-08 09:21:30.304 warn {"error":{"errno":-3001,"code":"EAI_AGAIN","syscall":"getaddrinfo","hostname":"gateway-xxxxx-xxxxx-xxxxx.local"}} tahoma.0 2022-07-08 09:21:30.304 warn setup failed! tahoma.0 2022-07-08 09:21:30.303 warn error during request: Error: getaddrinfo EAI_AGAIN gateway-xxxxx-xxxxx-xxxxx.local, request path: setup with payload:{} tahoma.0 2022-07-08 09:21:30.204 debug GET request on https://gateway-xxxxx-xxxx-xxxx.local:8443/enduser-mobile-web/1/enduserAPI/setup/gateways with payload:{} tahoma.0 2022-07-08 09:21:30.203 debug Update gateway status for id undefined
-
@mike2712 Wenn du ab Version 0.7.2 die Gateway PIN aus der Konfiguration nimmst, verbindet sich der Adapter statt mit der lokalen API wieder mit Tahomalink (online).
Dein Fehler getaddrinfo EAI_AGAIN deutet darauf hin, das bei dir die lokale Namensauflösung nicht funktioniert, d.h. der Adapter findet zu dem Namen kein Gerät im lokalen Netz. Eine Lösung wäre in deinem Router zu schauen, welche IP zu der Domain (gateway-xxxxx-xxxxx-xxxxx.local) gehört und die auf dem System wo dein Adapter läuft direkt mit der IP in die lokale
hosts
Datei einzutragen und dann den Adapter neu zu starten. -
@excodibur
danke für den Tipp.Adapter:
Fritz Box:
An welcher Stelle muss ich jetzt die 172.16.20.61 eintragen, das verstehe ich nicht? -
Wenn ich das richtig sehe, dann ist bei dir Tahoma im selben Netz wie "alles" andere auch?
Hast du schon mal mDNS aktiviert?
Funktioniert es damit? -
ja mDNS das habe ich aktiviert.
Es ist aber nicht alles im selben Netz. Der iOBroker ist 172.16.20.30,. Alles im selben Netz ist unmöglich, dafür sind es zu viele Geräte, das ist in bestimmten Gruppen aufgeteilt, es ist alles im 172.16.xx.xx.
Das es nicht gefunden wird klingt etwas plausibel, aber ich weiß nicht an welcher Stelle ich den "IP in die lokale hosts Datei " eintragen muss. -
@mike2712 mDNS funktioniert bei mir zu Hause im von einer Fritzbox verwalteten Netz z.B. nicht, deswegen habe ich das immer aus.
Die IP-Adresse musst du bei dem von mir vorgeschlagenen Workaround in die hosts-Datei deines Betriebssystems (inkl. Hostname) eintragen. Läuft ioBroker auf Linux, normalerweise unter /etc/hosts, bei Windows meistens C:\Windows\System32\drivers\etc\hosts. Dort dann einen Eintrag in folgendem Format hinzufügen:
172.16.20.61 gateway-xxxxx-xxxxx-xxxxx.local gateway-xxxxx-xxxxx-xxxxx
xxxx ist natürlich deine individuelle Gateway-ID
-
danke, bei mir läuft es im Docker Container, vielleicht noch jemand hier der sich damit etwas auskennt?
Habe einiges probiert, aber hab es nicht hinbekommen.TCP 172.16.22.35:9999 Error: connect EHOSTUNREACH 172.16.22.35:9999 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16) { errno: -113, code: 'EHOSTUNREACH', syscall: 'connect', address: '172.16.22.35', port: 9999 } 172.16.20.61 gateway-2006-2989-5271.loacal gateway-xxxx-xxxx-xxxx TCP 172.16.22.35:9999 Error: connect EHOSTUNREACH 172.16.22.35:9999 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16) { errno: -113, code: 'EHOSTUNREACH', syscall: 'connect', address: '172.16.22.35', port: 9999 }
# list /bin/sh: 1: list: not found # dir backups homematic_2022_01_11-01_30_12_2.59.7_backupiobroker.tar.sbk INSTALLER_INFO.txt iob iobroker iobroker.bak iobroker-data log node_modules package.json package-lock.json @Recently-Snapshot @Recycle reinstall.js # cd iob /bin/sh: 3: cd: can't cd to iob # cd iobroker /bin/sh: 4: cd: can't cd to iobroker # iobroker iobroker [command] Commands: iobroker setup Setup ioBroker iobroker start [all|<adapter>.<instance>] Starts the js-controller or a specified adapter instance iobroker stop [<adapter>.<instance>] stops the js-controller or a specified adapter instance iobroker restart [<adapter>.<instance>] Restarts js-controller or a specified adapter instance [aliases: r] iobroker debug <adapter>[.<instance>] Starts a Node.js debugging session for the adapter instance iobroker info Shows the host info iobroker logs [<adapter>] Monitor log iobroker add <adapter> [desiredNumber] Add instance of adapter [aliases: a] iobroker install <adapter> Installs a specified adapter [aliases: i] iobroker rebuild [<module>] Rebuild all native modules or path iobroker url <url> [<name>] Install adapter from specified url, e.g. GitHub iobroker del <adapter> Remove adapter and all instances from this host [aliases: delete] iobroker del <adapter>.<instance> Remove adapter instance [aliases: delete] iobroker update [<repositoryUrl>] Update repository and list adapters iobroker upgrade Upgrade management iobroker upload [all|<adapter>] Upload management [aliases: u] iobroker object Object management [aliases: o] iobroker state State management [aliases: s] iobroker message <adapter>[.instance] <command> [<message>] Send message to adapter instance/s iobroker list <type> [<filter>] List all entries, like objects iobroker chmod <mode> <file> Change file rights iobroker chown <user> <group> <file> Change file ownership iobroker touch <file> Touch file iobroker rm <file> Remove file iobroker file File management iobroker user User commands iobroker group group management iobroker host <hostname> Set host to given hostname iobroker set <adapter>.<instance> Change settings of adapter config iobroker license <license.file or license.text> Update license by given file iobroker cert Certificate management iobroker clean <yes> Clears all objects and states iobroker backup Create backup iobroker restore <backup name or path> Restore a specified backup iobroker validate <backup name or path> Validate a specified backup iobroker status [all|<adapter>.<instance>] Status of ioBroker or adapter instance [aliases: isrun] iobroker repo [<name>] Show repo information iobroker uuid Show uuid of the installation [aliases: id] iobroker unsetup Reset license, installation secret and language iobroker fix Execute the installation fixer script, this updates your ioBroker installation iobroker multihost Multihost management iobroker compact compact group management iobroker plugin Plugin management iobroker version [<adapter>] Show version of js-controller or specified adapter [aliases: v] Options: --help Show help [boolean] # 172.16.20.61 gateway-xxxx-xxxx-xxxx.loacal gateway-xxxx-xxxx-xxxx /bin/sh: 6: 172.16.20.61: not found
-
@mike2712 Das hinter deinem Gateway-Namen ".loacal" statt ".local" steht, ist seltsam.
Bei Docker gäbe es zwei Möglichkeiten:
- Du verwendest beim Deployment
--add-host
(https://docs.docker.com/engine/reference/commandline/run/#add-entries-to-container-hosts-file---add-host) und fügst das IP-Hostname-Mapping hinzu. Bei docker-compose wäre das Derextra_hosts
Abschnitt. - Du zwingst deinen Container via
--network=host
(https://docs.docker.com/network/host/) das Netzwerk des Host-Systems direkt mit zu nutzen, dann wird sicher auch die hosts-Datei deines Betriebssystems bei der Namensauflösung verwendet. Damit hebst du aber auch einen Teil der Docker Container-Isolierung auf, was nicht so optimal ist. Daher würde ich immer eher zu Option 1 raten.
- Du verwendest beim Deployment
-
@mike2712
Wäre es nicht erstmal Sinnvoll, die Tahoma Box in das selbe Netz zu hängen und zu schauen, ob es dort ohne Probleme funktioniert?Erst dann würde ich vielleicht weiter machen oder ggf. sogar in dem Netz hängen lassen.
-
@Excodibur Vielen Dank für Deine Hilfe, nachdem ich alles nochmals durchgelesen habe ist mit das mit mDNS aufgefallen, das hatte ich aktiviert, nach dem deaktivieren ging es.
@wusa das ist eine gute Idee, dabei habe ich festgestellt das sie schon im selben Netz hängen, das hatte ich früher schon mal versuchsweise getestet.
Dann habe ich mich mit dem Tipp von Excodibur weiter versucht durchzukämpfen, leider habe ich das mit dem zufügen der Adresse nicht hinbekommen, danach habe ich alles nochmals gelesen.Seltsam war das der Adapter komplett grün ist, aber dennoch die Fehler ausgeben hatte.
Eine kleine Frage, mit welchem Datenpunkt steuert Ihr die Position? Es funktionieren komischerweise alle 3 gelb markierten.
Ich kann alles steuern, aber die Rückmeldungen, wenn ich aus der Handy App steuere, kommen die neuen Positionen offensichtlich nicht in ioBorker an.
-
Mit der Aktualisierung liegt wohl am Abrufintervall, das hatte mir damals die Somfy Hotline gesagt, weil das Konto immer gesperrt war, was war der default Eintrag noch? Leider vergessen.
-
Guten Tag in die Runde. Ich kann leider auf die Frage, ob man eine Connexoon io mit dem Adapter verbinden kann keine Antwort finden. Der Adapter möchte Zugangsdaten für das ältere Web-System TaHoma Link haben, die ich nicht habe, weil ich leider nur eine Connexoon io Box besitze. Gibt es hierfür auch eine Lösung?
Ich danke für eine Rückmeldung und hoffe auf eine Lösung. -
@tobfe : also bei meinem Adapter muss ich nur die Zugangsdaten eingeben, um meine Connexoon zu verbinden.
-
@puls200 Danke. Ich hatte einen Zahledreher
Allerdings bin ich nun zwar verbunden, aber in den Objekten finde ich meine angelegten Produkte nicht (Jaloussie, Lamellendach,...) Woran liegt das?