Kann mnn eigentlich die Bewässerungsventile auch über den IOT-Adapter mittels Alexa steuern? Wenn ja, wie?
NEWS
Latest posts made by MaZi
-
RE: Gardena smart garden Adapter
-
RE: Gardena smart garden Adapter
@thomas-braun
Nach Hardwaretausch von Raspberry 3 auf Raspberry 4 und Neuinstallation des Adapters funktioniert es jetzt! Danke! -
RE: Gardena smart garden Adapter
@thomas-braun
Habe ich gemacht! Leider ohne Erfolgsmartgarden.0 2022-07-01 21:11:41.900 error Error: request returned 403 Forbidden smartgarden.0 2022-07-01 21:11:41.569 info starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v16.15.1, js-controller: 4.0.23 smartgarden.0 2022-07-01 21:11:41.207 debug States connected to redis: 127.0.0.1:9000 smartgarden.0 2022-07-01 21:11:41.148 debug States create User PubSub Client smartgarden.0 2022-07-01 21:11:41.146 debug States create System PubSub Client smartgarden.0 2022-07-01 21:11:41.114 debug Redis States: Use Redis connection: 127.0.0.1:9000 smartgarden.0 2022-07-01 21:11:41.064 debug Objects connected to redis: 127.0.0.1:9001 smartgarden.0 2022-07-01 21:11:41.056 debug Objects client initialize lua scripts smartgarden.0 2022-07-01 21:11:40.963 debug Objects create User PubSub Client smartgarden.0 2022-07-01 21:11:40.962 debug Objects create System PubSub Client smartgarden.0 2022-07-01 21:11:40.959 debug Objects client ready ... initialize now smartgarden.0 2022-07-01 21:11:40.895 debug Redis Objects: Use Redis connection: 127.0.0.1:9001
-
Gardena smart garden Adapter
Ich bekomme leider die Fehlermeldung "Error: request returned 403 Forbidden" obwohl ich mich mit APP-Key und APP-Secret in der Instanz anmede.
Die beiden API´s: Authentication API und GARDENA smart system API habe ich auch ordnungsgemöß connected.
Mein Logfile habe ich angehangen:
Hat jemand eine Idee woran es scheitert?
v5.3.8
304Log-Größe: 32.0 KB
ZeitNachricht
smartgarden.0 2022-07-01 11:32:39.302 error Error: request returned 403 Forbidden smartgarden.0 2022-07-01 11:27:39.176 error Error: request returned 403 Forbidden smartgarden.0 2022-07-01 11:27:38.846 info starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v12.22.7, js-controller: 4.0.21 smartgarden.0 2022-07-01 11:27:38.192 debug States connected to redis: 127.0.0.1:9000 smartgarden.0 2022-07-01 11:27:38.037 debug States create User PubSub Client smartgarden.0 2022-07-01 11:27:38.034 debug States create System PubSub Client smartgarden.0 2022-07-01 11:27:37.976 debug Redis States: Use Redis connection: 127.0.0.1:9000 smartgarden.0 2022-07-01 11:27:37.880 debug Objects connected to redis: 127.0.0.1:9001 smartgarden.0 2022-07-01 11:27:37.868 debug Objects client initialize lua scripts smartgarden.0 2022-07-01 11:27:37.688 debug Objects create User PubSub Client smartgarden.0 2022-07-01 11:27:37.686 debug Objects create System PubSub Client smartgarden.0 2022-07-01 11:27:37.681 debug Objects client ready ... initialize now smartgarden.0 2022-07-01 11:27:37.578 debug Redis Objects: Use Redis connection: 127.0.0.1:9001 smartgarden.0 2022-07-01 11:27:30.960 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason smartgarden.0 2022-07-01 11:27:30.958 info terminating smartgarden.0 2022-07-01 11:27:30.955 info Got terminate signal TERMINATE_YOURSELF smartgarden.0 2022-07-01 11:27:21.428 error Error: request returned 403 Forbidden smartgarden.0 2022-07-01 11:27:21.099 info starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v12.22.7, js-controller: 4.0.21 smartgarden.0 2022-07-01 11:27:20.472 debug States connected to redis: 127.0.0.1:9000 smartgarden.0 2022-07-01 11:27:20.324 debug States create User PubSub Client smartgarden.0 2022-07-01 11:27:20.321 debug States create System PubSub Client smartgarden.0 2022-07-01 11:27:20.260 debug Redis States: Use Redis connection: 127.0.0.1:9000 smartgarden.0 2022-07-01 11:27:20.161 debug Objects connected to redis: 127.0.0.1:9001 smartgarden.0 2022-07-01 11:27:20.148 debug Objects client initialize lua scripts smartgarden.0 2022-07-01 11:27:19.964 debug Objects create User PubSub Client smartgarden.0 2022-07-01 11:27:19.962 debug Objects create System PubSub Client smartgarden.0 2022-07-01 11:27:19.958 debug Objects client ready ... initialize now smartgarden.0 2022-07-01 11:27:19.847 debug Redis Objects: Use Redis connection: 127.0.0.1:9001 smartgarden.0 2022-07-01 11:27:12.901 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason smartgarden.0 2022-07-01 11:27:12.898 info terminating smartgarden.0 2022-07-01 11:27:12.895 info Got terminate signal TERMINATE_YOURSELF smartgarden.0 2022-07-01 11:23:33.648 error Error: request returned 403 Forbidden smartgarden.0 2022-07-01 11:18:33.536 error Error: request returned 403 Forbidden smartgarden.0 2022-07-01 11:18:33.183 info starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v12.22.7, js-controller: 4.0.21 smartgarden.0 2022-07-01 11:17:37.685 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason smartgarden.0 2022-07-01 11:17:37.682 info terminating smartgarden.0 2022-07-01 11:17:37.676 info Got terminate signal TERMINATE_YOURSELF smartgarden.0 2022-07-01 11:16:10.923 error Error: request returned 403 Forbidden smartgarden.0 2022-07-01 11:11:10.828 error Error: request returned 403 Forbidden smartgarden.0 2022-07-01 11:11:10.469 info starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v12.22.7, js-controller: 4.0.21 smartgarden.0 2022-07-01 11:11:02.634 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason smartgarden.0 2022-07-01 11:11:02.632 info terminating smartgarden.0 2022-07-01 11:11:02.627 info Got terminate signal TERMINATE_YOURSELF smartgarden.0 2022-07-01 11:10:15.492 error Error: request returned 404 Not Found smartgarden.0 2022-07-01 11:10:14.864 info starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v12.22.7, js-controller: 4.0.21 smartgarden.0 2022-07-01 11:10:06.923 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason smartgarden.0 2022-07-01 11:10:06.920 info terminating smartgarden.0 2022-07-01 11:10:06.914 info Got terminate signal TERMINATE_YOURSELF smartgarden.0 2022-07-01 11:06:02.955 error Error: request returned 403 Forbidden smartgarden.0 2022-07-01 11:06:02.539 info starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v12.22.7, js-controller: 4.0.21 smartgarden.0 2022-07-01 11:05:54.521 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason smartgarden.0 2022-07-01 11:05:54.519 info terminating smartgarden.0 2022-07-01 11:05:54.515 info Got terminate signal TERMINATE_YOURSELF smartgarden.0 2022-07-01 11:04:04.246 error Error: request returned 403 Forbidden smartgarden.0 2022-07-01 11:04:03.884 info starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v12.22.7, js-controller: 4.0.21 smartgarden.0 2022-07-01 11:03:55.864 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason smartgarden.0 2022-07-01 11:03:55.860 info terminating smartgarden.0 2022-07-01 11:03:55.854 info Got terminate signal TERMINATE_YOURSELF smartgarden.0 2022-07-01 11:01:21.269 error Error: request returned 403 Forbidden smartgarden.0 2022-07-01 11:01:20.697 info starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v12.22.7, js-controller: 4.0.21 smartgarden.0 2022-07-01 11:01:14.694 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason smartgarden.0 2022-07-01 11:01:14.691 info terminating smartgarden.0 2022-07-01 11:01:14.684 info Got terminate signal TERMINATE_YOURSELF smartgarden.0 2022-07-01 10:59:50.273 error Error: request returned 403 Forbidden smartgarden.0 2022-07-01 10:59:49.962 info starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v12.22.7, js-controller: 4.0.21 smartgarden.0 2022-07-01 10:59:42.155 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason smartgarden.0 2022-07-01 10:59:42.153 info terminating smartgarden.0 2022-07-01 10:59:42.149 info Got terminate signal TERMINATE_YOURSELF smartgarden.0 2022-07-01 10:54:44.946 error Error: request returned 404 Not Found smartgarden.0 2022-07-01 10:54:44.338 info starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v12.22.7, js-controller: 4.0.21 smartgarden.0 2022-07-01 10:54:36.345 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason smartgarden.0 2022-07-01 10:54:36.343 info terminating smartgarden.0 2022-07-01 10:54:36.338 info Got terminate signal TERMINATE_YOURSELF smartgarden.0 2022-07-01 10:53:54.470 error Error: request returned 404 Not Found smartgarden.0 2022-07-01 10:53:53.845 info starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v12.22.7, js-controller: 4.0.21 smartgarden.0 2022-07-01 10:52:17.139 warn Terminated (UNCAUGHT_EXCEPTION): Without reason smartgarden.0 2022-07-01 10:52:17.136 info terminating smartgarden.0 2022-07-01 10:52:17.126 error undefined is not a valid uri or options object. smartgarden.0 2022-07-01 10:52:17.124 error Error: undefined is not a valid uri or options object. at request (/opt/iobroker/node_modules/request/index.js:44:11) at connect (/opt/iobroker/node_modules/iobroker.smartgarden/lib/api.js:2889:2) at connectToGardena (/opt/iobroker/node_modules/iobroker.smartgarden/lib/api.js:2760:2) at Object.exports.getConnection (/opt/iobroker/node_modules/iobroker.smartgarden/lib/api.js:2740:2) at /opt/iobroker/node_modules/iobroker.smartgarden/main.js:230:15 at /opt/iobroker/node_modules/iobroker.smartgarden/main.js:123:19 at updateAdapter020000 (/opt/iobroker/node_modules/iobroker.smartgarden/main.js:101:17) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.smartgarden/main.js:122:4) at processImmediate (internal/timers.js:463:21) smartgarden.0 2022-07-01 10:52:17.121 error uncaught exception: undefined is not a valid uri or options object. smartgarden.0 2022-07-01 10:52:17.117 error Error: no possible grant for connect smartgarden.0 2022-07-01 10:52:17.020 info starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v12.22.7, js-controller: 4.0.21 smartgarden.0 2022-07-01 10:51:41.495 warn Terminated (UNCAUGHT_EXCEPTION): Without reason smartgarden.0 2022-07-01 10:51:41.493 info terminating smartgarden.0 2022-07-01 10:51:41.482 error undefined is not a valid uri or options object. smartgarden.0 2022-07-01 10:51:41.481 error Error: undefined is not a valid uri or options object. at request (/opt/iobroker/node_modules/request/index.js:44:11) at connect (/opt/iobroker/node_modules/iobroker.smartgarden/lib/api.js:2889:2) at connectToGardena (/opt/iobroker/node_modules/iobroker.smartgarden/lib/api.js:2760:2) at Object.exports.getConnection (/opt/iobroker/node_modules/iobroker.smartgarden/lib/api.js:2740:2) at /opt/iobroker/node_modules/iobroker.smartgarden/main.js:230:15 at /opt/iobroker/node_modules/iobroker.smartgarden/main.js:123:19 at updateAdapter020000 (/opt/iobroker/node_modules/iobroker.smartgarden/main.js:101:17) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.smartgarden/main.js:122:4) at processImmediate (internal/timers.js:463:21) smartgarden.0 2022-07-01 10:51:41.477 error uncaught exception: undefined is not a valid uri or options object. smartgarden.0 2022-07-01 10:51:41.474 error Error: no possible grant for connect smartgarden.0 2022-07-01 10:51:41.359 info starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v12.22.7, js-controller: 4.0.21 smartgarden.0 2022-07-01 10:51:05.794 warn Terminated (UNCAUGHT_EXCEPTION): Without reason smartgarden.0 2022-07-01 10:51:05.792 info terminating smartgarden.0 2022-07-01 10:51:05.780 error undefined is not a valid uri or options object. smartgarden.0 2022-07-01 10:51:05.778 error Error: undefined is not a valid uri or options object. at request (/opt/iobroker/node_modules/request/index.js:44:11) at connect (/opt/iobroker/node_modules/iobroker.smartgarden/lib/api.js:2889:2) at connectToGardena (/opt/iobroker/node_modules/iobroker.smartgarden/lib/api.js:2760:2) at Object.exports.getConnection (/opt/iobroker/node_modules/iobroker.smartgarden/lib/api.js:2740:2) at /opt/iobroker/node_modules/iobroker.smartgarden/main.js:230:15 at /opt/iobroker/node_modules/iobroker.smartgarden/main.js:123:19 at /opt/iobroker/node_modules/iobroker.smartgarden/main.js:98:18 at /opt/iobroker/node_modules/iobroker.smartgarden/main.js:205:19 at /opt/iobroker/node_modules/iobroker.smartgarden/main.js:205:19 at /opt/iobroker/node_modules/iobroker.smartgarden/main.js:205:19 smartgarden.0 2022-07-01 10:51:05.775 error uncaught exception: undefined is not a valid uri or options object. smartgarden.0 2022-07-01 10:51:05.772 error Error: no possible grant for connect smartgarden.0 2022-07-01 10:51:03.644 info starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v12.22.7, js-controller: 4.0.21 smartgarden.0 2022-07-01 10:46:34.090 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason smartgarden.0 2022-07-01 10:46:34.087 info terminating smartgarden.0 2022-07-01 10:46:34.082 info Got terminate signal TERMINATE_YOURSELF
-
RE: ERLEDIGT: Steuerung Homematic-IP Dimmaktor (BDT) über IOT
Ich habe die Lösung gefunden:
hier kann man die Prozentzahl eingeben: HmIP-BDT 0008DA499293CD:4.LEVEL -
ERLEDIGT: Steuerung Homematic-IP Dimmaktor (BDT) über IOT
Hallo zusammen,
wie kann ich einen Homematic-IP Dimmaktor (BDT) über den IOT-Adapter einbinden, so dass ich ihn dann über ALexa ein- bzw. ausschalten kann?
Bei den normalen Homematic-IP Schalt- / Messaktoren (BSM) habe ich dies über den den Kanal 4 - STATE (HmIP-BSM 00085BE98B3BEF:4.STATE) hinbekommen.
Vielen Dank für Eure Unetrstützung.
Viele Grüße aus München
Martin
-
RE: 2 CCU auf einer Iobroker Installation
@Homoran
Da hast Du vollkommen recht! Ich habe es geändert!Jetzt funktioniert es. Vielen herzlichen Dank für Deine Hilfe!!!!!!!
Kann ich den Post irgendwie schließen?
-
RE: 2 CCU auf einer Iobroker Installation
@Homoran
Danke für Deine Antwort.
Screenshots folgen mit diesem Post.
Mit zwei Standorten meine ich zwei Netzwerke (jeweils mit Fritzbox) welche mittels VPN verbunden sind (LAN to LAN) (Netzwerkerweiterung mit Fritzbox).Im Netzwerk "1" steht der Raspbeery Pi auf dem der "iobroker" läuft (192.168.0.165:8081). Netzwerk "1" hat den IP-Adressenbereich 192.168.0.x. In diesem Netzwerksegment (also an diesem Satandort) befindet sich die CCU2 (192.168.0.160).
Im Netzwerk "2" (IP-Adressenereich: 192.168.10.x) steht kein Raspberry aber dafür die CCU3 (192.168.10.127) (es handelt sich um zwei Häuser).
Daher habe ich auf dem iobroker nun jeweils zwei Instanzen vom Rega-Adapter und zwei Instanzen vom RPC-Adapter installiert.
Jeweils die 0.Instanz gehört zur CCU2, welche sich im gleichen Netzwerksegment wie der iobroker befidnet. Die 1.Instanzen gehören zur CCU im anderen Netzwerksgement.
Die Konfiguartion der 1. Instanzen nun in den Screenshots:
hm-rega.1:
hm-rpc.1:
So sieht es bei den Objekten aus:
beim hm-rpc.0 sieht es korrekt aus, der Kanal "1" ist korrekt befüllt
beim hm-rpc.1 leider nicht, der Kanal "1" ist komisch:
Neustart des hm-rega.1 bringt leider auch nichts. Keine fehler im Log-Reiter. Loglevel debug kenne ich leider nicht. Wie macht man das?
Vielen Dank und viele Grüße
Martin
-
2 CCU auf einer Iobroker Installation
Hallo zusammen,
ich habe momentan zwei CCU (2 und 3) an zwei verschiedenen Standorten in einer iobroker-Installation laufen.
Standort A: (CCU2)
hm-rega.0
hm-rpc.0Standort B: (CCU3):
hm-rega.1
hm-rpc.1In den 0-Instanzen läuft nach wie vor alles prima.
In den 1-Instanzen fehlen mir im Bereich "Objekte" bei den RPC-Geräten die Ordner "1" wo zum beispiel bei Fensterkontakten der "State" angezeigt wird.Ich sehe somit nur die Ordner "0" wo lediglich folgender Inhalt angezeigt wird:
CONFIG_PENDING_ALARM state
Fensterkontakt-I14-Terrassentür:0.CONFIG_PENDING_ALARM
state indicator.alarm NO ALARM(0)
LOW_BAT_ALARM state
Fensterkontakt-I14-Terrassentür:0.LOW_BAT_ALARM
state indicator.alarm NO ALARM(0)
SABOTAGE_ALARM state
Fensterkontakt-I14-Terrassentür:0.SABOTAGE_ALARM
state indicator.alarm NO ALARM(0)
UNREACH_ALARM state
Fensterkontakt-I14-Terrassentür:0.UNREACH_ALARM
state indicator.alarm NO ALARM(0)
UPDATE_PENDING_ALARM state
Fensterkontakt-I14-Terrassentür:0.UPDATE_PENDING_ALARM
state indicator.alarm NO ALARM(0)Der für mich relevante Zustand aus Ornder "1":
STATE state
HmIP-SWDO-I 00109709A8EA1B:1.STATE
state value.window funcLock, funcSecurity CLOSED(0)
fehlt leider. Alle Instanzen sind grün und es werden auch keine Fehler-Logs ausgegeben.Wo liegt der "Hase im Peffer"?
Vielen dank für Eure Untrstützung.
Viele Grüße
Martin