NEWS
[gelöst]HMIP-PS Datenpunkte
-
Hallo, habe gestern eine Schaltsteckdose HMIP-PS angeschlossen. In Homematic funktioniert sie. Im Broker werden mir nur für diese Steckdose keine Datenpunkte angezeigt. Fehler werden im Log auch nicht angezeigt. Alle anderen Datenpunkte der integrierten Geräte sind da.! Muss ich die Steckdose wieder aus dem Broker auslöschen um sie neu einzubinden? Und wenn ja, wie mache ich das? Danke für Eure Hilfe!
-
@michaelxhoffmann
Bilder bitte direkt hier einbinden (über die Wolke)@michaelxhoffmann sagte in HMIP-PS Datenpunkte:
Muss ich die Steckdose wieder aus dem Broker auslöschen um sie neu einzubinden?
Wahrscheinlich nicht.
Bitte einmal in der entsprechenden HmIP INstanz des hm-rpc-Adapters auf geräte neu einlesen gehen und danach auch mal die hm-rega Instanz neu starten -
@Homoran Das hat leider nicht funktioniert.
2020-06-19 02:00:13.586 - warn: host.raspberrypi Objects 127.0.0.1:36352 Error from InMemDB: Error: ERROR readDir id=0_userdata.0: Not exists 2020-06-19 02:00:13.607 - warn: host.raspberrypi Objects 127.0.0.1:36352 Error from InMemDB: Error: ERROR readDir id=admin.0: Not exists 2020-06-19 02:00:13.608 - warn: host.raspberrypi Objects 127.0.0.1:36352 Error from InMemDB: Error: ERROR readDir id=admin.1: Not exists 2020-06-19 02:00:13.609 - warn: host.raspberrypi Objects 127.0.0.1:36352 Error from InMemDB: Error: ERROR readDir id=web.0: Not exists 2020-06-19 04:49:48.025 - error: iot.0 (8386) Error by device connection: "read ECONNRESET" 2020-06-19 10:13:09.926 - info: host.raspberrypi Update repository "default" under "http://download.iobroker.net/sources-dist.json" 2020-06-19 12:49:23.098 - info: host.raspberrypi instance system.adapter.hm-rpc.2 started with pid 11132 2020-06-19 12:49:23.109 - warn: hm-rpc.2 (8780) Got terminate signal. Checking desired PID: 0 vs own PID 8780 2020-06-19 12:49:23.132 - warn: hm-rpc.2 (8780) Got terminate signal. Checking desired PID: 11132 vs own PID 8780 2020-06-19 12:49:23.756 - error: host.raspberrypi instance system.adapter.hm-rpc.2 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-06-19 12:49:23.757 - info: host.raspberrypi Do not restart adapter system.adapter.hm-rpc.2 because desired by instance 2020-06-19 12:50:09.366 - info: host.raspberrypi instance system.adapter.hm-rpc.2 started with pid 11183 2020-06-19 12:50:09.370 - warn: hm-rpc.2 (11132) Got terminate signal. Checking desired PID: 0 vs own PID 11132 2020-06-19 12:50:09.397 - warn: hm-rpc.2 (11132) Got terminate signal. Checking desired PID: 11183 vs own PID 11132 2020-06-19 12:50:09.983 - error: host.raspberrypi instance system.adapter.hm-rpc.2 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-06-19 12:50:09.984 - info: host.raspberrypi Do not restart adapter system.adapter.hm-rpc.2 because desired by instance 2020-06-19 12:51:11.027 - info: host.raspberrypi instance system.adapter.hm-rpc.2 started with pid 11349 2020-06-19 12:51:11.032 - warn: hm-rpc.2 (11183) Got terminate signal. Checking desired PID: 0 vs own PID 11183 2020-06-19 12:51:11.041 - warn: hm-rpc.2 (11183) Got terminate signal. Checking desired PID: 11349 vs own PID 11183 2020-06-19 12:51:11.631 - error: host.raspberrypi instance system.adapter.hm-rpc.2 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-06-19 12:51:11.631 - info: host.raspberrypi Do not restart adapter system.adapter.hm-rpc.2 because desired by instance 2020-06-19 12:51:13.953 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 (force=false, process=true) 2020-06-19 12:51:13.957 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 send kill signal 2020-06-19 12:51:14.524 - info: host.raspberrypi instance system.adapter.hm-rega.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2020-06-19 12:51:17.016 - info: host.raspberrypi instance system.adapter.hm-rega.0 started with pid 11368 2020-06-19 12:51:55.342 - info: host.raspberrypi instance system.adapter.hm-rpc.2 started with pid 11385 2020-06-19 12:51:55.346 - warn: hm-rpc.2 (11349) Got terminate signal. Checking desired PID: 0 vs own PID 11349 2020-06-19 12:51:55.356 - warn: hm-rpc.2 (11349) Got terminate signal. Checking desired PID: 11385 vs own PID 11349 2020-06-19 12:51:55.943 - error: host.raspberrypi instance system.adapter.hm-rpc.2 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-06-19 12:51:55.944 - info: host.raspberrypi Do not restart adapter system.adapter.hm-rpc.2 because desired by instance 2020-06-19 12:52:01.128 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 (force=false, process=true) 2020-06-19 12:52:01.131 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 send kill signal 2020-06-19 12:52:01.695 - info: host.raspberrypi instance system.adapter.hm-rega.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2020-06-19 12:52:04.197 - info: host.raspberrypi instance system.adapter.hm-rega.0 started with pid 11401 2020-06-19 12:53:13.462 - info: host.raspberrypi instance system.adapter.hm-rpc.2 started with pid 11571 2020-06-19 12:53:13.467 - warn: hm-rpc.2 (11385) Got terminate signal. Checking desired PID: 0 vs own PID 11385 2020-06-19 12:53:13.481 - warn: hm-rpc.2 (11385) Got terminate signal. Checking desired PID: 11571 vs own PID 11385 2020-06-19 12:53:14.071 - error: host.raspberrypi instance system.adapter.hm-rpc.2 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-06-19 12:53:14.072 - info: host.raspberrypi Do not restart adapter system.adapter.hm-rpc.2 because desired by instance 2020-06-19 12:53:19.071 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.1 (force=false, process=true) 2020-06-19 12:53:20.073 - info: host.raspberrypi stopInstance timeout 1000 system.adapter.hm-rpc.1 killing pid 21369 2020-06-19 12:53:20.634 - info: host.raspberrypi instance system.adapter.hm-rpc.1 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2020-06-19 12:53:23.127 - info: host.raspberrypi instance system.adapter.hm-rpc.1 started with pid 11587 2020-06-19 12:53:27.061 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.0 (force=false, process=true) 2020-06-19 12:53:27.494 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.1 (force=false, process=true) 2020-06-19 12:53:28.068 - info: host.raspberrypi stopInstance timeout 1000 system.adapter.hm-rpc.0 killing pid 21343 2020-06-19 12:53:28.500 - info: host.raspberrypi stopInstance timeout 1000 system.adapter.hm-rpc.1 killing pid 11587 2020-06-19 12:53:28.623 - info: host.raspberrypi instance system.adapter.hm-rpc.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2020-06-19 12:53:29.057 - info: host.raspberrypi instance system.adapter.hm-rpc.1 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2020-06-19 12:53:30.544 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 (force=false, process=true) 2020-06-19 12:53:30.546 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 send kill signal 2020-06-19 12:53:31.075 - info: host.raspberrypi instance system.adapter.hm-rega.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2020-06-19 12:53:31.100 - info: host.raspberrypi instance system.adapter.hm-rpc.0 started with pid 11603 2020-06-19 12:53:31.527 - info: host.raspberrypi instance system.adapter.hm-rpc.1 started with pid 11610 2020-06-19 12:53:33.583 - info: host.raspberrypi instance system.adapter.hm-rega.0 started with pid 11629 2020-06-19 12:53:33.652 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.0 (force=false, process=true) 2020-06-19 12:53:34.662 - info: host.raspberrypi stopInstance timeout 1000 system.adapter.hm-rpc.0 killing pid 11603 2020-06-19 12:53:35.230 - info: host.raspberrypi instance system.adapter.hm-rpc.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2020-06-19 12:53:37.688 - info: host.raspberrypi instance system.adapter.hm-rpc.0 started with pid 11648 2020-06-19 12:53:37.822 - error: hm-rpc.1 (11610) xmlrpc -> setValue ["1","STATE",true] BOOL 2020-06-19 12:53:37.825 - error: hm-rpc.1 (11610) Error: XML-RPC fault: Failure 2020-06-19 12:53:47.435 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 (force=false, process=true) 2020-06-19 12:53:47.438 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 send kill signal 2020-06-19 12:53:47.977 - info: host.raspberrypi instance system.adapter.hm-rega.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2020-06-19 12:53:50.486 - info: host.raspberrypi instance system.adapter.hm-rega.0 started with pid 11663
Habe mal alle Instanzen neu eingelesen. Die betreffende Instanz ist die rpc2
Brachte aber keinen eRfolg -
@michaelxhoffmann sagte in HMIP-PS Datenpunkte:
@Homoran Das hat leider nicht funktioniert.
2020-06-19 02:00:13.586 - warn: host.raspberrypi Objects 127.0.0.1:36352 Error from InMemDB: Error: ERROR readDir id=0_userdata.0: Not exists 2020-06-19 02:00:13.607 - warn: host.raspberrypi Objects 127.0.0.1:36352 Error from InMemDB: Error: ERROR readDir id=admin.0: Not exists 2020-06-19 02:00:13.608 - warn: host.raspberrypi Objects 127.0.0.1:36352 Error from InMemDB: Error: ERROR readDir id=admin.1: Not exists 2020-06-19 02:00:13.609 - warn: host.raspberrypi Objects 127.0.0.1:36352 Error from InMemDB: Error: ERROR readDir id=web.0: Not exists 2020-06-19 04:49:48.025 - error: iot.0 (8386) Error by device connection: "read ECONNRESET" 2020-06-19 10:13:09.926 - info: host.raspberrypi Update repository "default" under "http://download.iobroker.net/sources-dist.json" 2020-06-19 12:49:23.098 - info: host.raspberrypi instance system.adapter.hm-rpc.2 started with pid 11132 2020-06-19 12:49:23.109 - warn: hm-rpc.2 (8780) Got terminate signal. Checking desired PID: 0 vs own PID 8780 2020-06-19 12:49:23.132 - warn: hm-rpc.2 (8780) Got terminate signal. Checking desired PID: 11132 vs own PID 8780 2020-06-19 12:49:23.756 - error: host.raspberrypi instance system.adapter.hm-rpc.2 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-06-19 12:49:23.757 - info: host.raspberrypi Do not restart adapter system.adapter.hm-rpc.2 because desired by instance 2020-06-19 12:50:09.366 - info: host.raspberrypi instance system.adapter.hm-rpc.2 started with pid 11183 2020-06-19 12:50:09.370 - warn: hm-rpc.2 (11132) Got terminate signal. Checking desired PID: 0 vs own PID 11132 2020-06-19 12:50:09.397 - warn: hm-rpc.2 (11132) Got terminate signal. Checking desired PID: 11183 vs own PID 11132 2020-06-19 12:50:09.983 - error: host.raspberrypi instance system.adapter.hm-rpc.2 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-06-19 12:50:09.984 - info: host.raspberrypi Do not restart adapter system.adapter.hm-rpc.2 because desired by instance 2020-06-19 12:51:11.027 - info: host.raspberrypi instance system.adapter.hm-rpc.2 started with pid 11349 2020-06-19 12:51:11.032 - warn: hm-rpc.2 (11183) Got terminate signal. Checking desired PID: 0 vs own PID 11183 2020-06-19 12:51:11.041 - warn: hm-rpc.2 (11183) Got terminate signal. Checking desired PID: 11349 vs own PID 11183 2020-06-19 12:51:11.631 - error: host.raspberrypi instance system.adapter.hm-rpc.2 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-06-19 12:51:11.631 - info: host.raspberrypi Do not restart adapter system.adapter.hm-rpc.2 because desired by instance 2020-06-19 12:51:13.953 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 (force=false, process=true) 2020-06-19 12:51:13.957 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 send kill signal 2020-06-19 12:51:14.524 - info: host.raspberrypi instance system.adapter.hm-rega.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2020-06-19 12:51:17.016 - info: host.raspberrypi instance system.adapter.hm-rega.0 started with pid 11368 2020-06-19 12:51:55.342 - info: host.raspberrypi instance system.adapter.hm-rpc.2 started with pid 11385 2020-06-19 12:51:55.346 - warn: hm-rpc.2 (11349) Got terminate signal. Checking desired PID: 0 vs own PID 11349 2020-06-19 12:51:55.356 - warn: hm-rpc.2 (11349) Got terminate signal. Checking desired PID: 11385 vs own PID 11349 2020-06-19 12:51:55.943 - error: host.raspberrypi instance system.adapter.hm-rpc.2 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-06-19 12:51:55.944 - info: host.raspberrypi Do not restart adapter system.adapter.hm-rpc.2 because desired by instance 2020-06-19 12:52:01.128 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 (force=false, process=true) 2020-06-19 12:52:01.131 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 send kill signal 2020-06-19 12:52:01.695 - info: host.raspberrypi instance system.adapter.hm-rega.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2020-06-19 12:52:04.197 - info: host.raspberrypi instance system.adapter.hm-rega.0 started with pid 11401 2020-06-19 12:53:13.462 - info: host.raspberrypi instance system.adapter.hm-rpc.2 started with pid 11571 2020-06-19 12:53:13.467 - warn: hm-rpc.2 (11385) Got terminate signal. Checking desired PID: 0 vs own PID 11385 2020-06-19 12:53:13.481 - warn: hm-rpc.2 (11385) Got terminate signal. Checking desired PID: 11571 vs own PID 11385 2020-06-19 12:53:14.071 - error: host.raspberrypi instance system.adapter.hm-rpc.2 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-06-19 12:53:14.072 - info: host.raspberrypi Do not restart adapter system.adapter.hm-rpc.2 because desired by instance 2020-06-19 12:53:19.071 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.1 (force=false, process=true) 2020-06-19 12:53:20.073 - info: host.raspberrypi stopInstance timeout 1000 system.adapter.hm-rpc.1 killing pid 21369 2020-06-19 12:53:20.634 - info: host.raspberrypi instance system.adapter.hm-rpc.1 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2020-06-19 12:53:23.127 - info: host.raspberrypi instance system.adapter.hm-rpc.1 started with pid 11587 2020-06-19 12:53:27.061 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.0 (force=false, process=true) 2020-06-19 12:53:27.494 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.1 (force=false, process=true) 2020-06-19 12:53:28.068 - info: host.raspberrypi stopInstance timeout 1000 system.adapter.hm-rpc.0 killing pid 21343 2020-06-19 12:53:28.500 - info: host.raspberrypi stopInstance timeout 1000 system.adapter.hm-rpc.1 killing pid 11587 2020-06-19 12:53:28.623 - info: host.raspberrypi instance system.adapter.hm-rpc.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2020-06-19 12:53:29.057 - info: host.raspberrypi instance system.adapter.hm-rpc.1 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2020-06-19 12:53:30.544 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 (force=false, process=true) 2020-06-19 12:53:30.546 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 send kill signal 2020-06-19 12:53:31.075 - info: host.raspberrypi instance system.adapter.hm-rega.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2020-06-19 12:53:31.100 - info: host.raspberrypi instance system.adapter.hm-rpc.0 started with pid 11603 2020-06-19 12:53:31.527 - info: host.raspberrypi instance system.adapter.hm-rpc.1 started with pid 11610 2020-06-19 12:53:33.583 - info: host.raspberrypi instance system.adapter.hm-rega.0 started with pid 11629 2020-06-19 12:53:33.652 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.0 (force=false, process=true) 2020-06-19 12:53:34.662 - info: host.raspberrypi stopInstance timeout 1000 system.adapter.hm-rpc.0 killing pid 11603 2020-06-19 12:53:35.230 - info: host.raspberrypi instance system.adapter.hm-rpc.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2020-06-19 12:53:37.688 - info: host.raspberrypi instance system.adapter.hm-rpc.0 started with pid 11648 2020-06-19 12:53:37.822 - error: hm-rpc.1 (11610) xmlrpc -> setValue ["1","STATE",true] BOOL 2020-06-19 12:53:37.825 - error: hm-rpc.1 (11610) Error: XML-RPC fault: Failure 2020-06-19 12:53:47.435 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 (force=false, process=true) 2020-06-19 12:53:47.438 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 send kill signal 2020-06-19 12:53:47.977 - info: host.raspberrypi instance system.adapter.hm-rega.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2020-06-19 12:53:50.486 - info: host.raspberrypi instance system.adapter.hm-rega.0 started with pid 11663
Habe mal alle Instanzen neu eingelesen. Die betreffende Instanz ist die rpc2
Brachte aber keinen eRfolgHabe heute mal das Ding aus den Objekten entfernt und neu eingelesen. Auch das brachte keinen Erfolg. Es muss doch eine Möglichkeit geben diese Schaltsteckdose zu integrieren.
Homematic RPC Adapter ist 1.14.2In meiner ccu2 lässt es sich einwandfrei konfigurieren. also Verknüpfung mit Schalter etc... im iobroker werden leider nur folgende Datenpunkte erfasst:
config_pending_alarm
error_overheat_alarm
unreach_alarm
update_pending_alarm
Diese entsprechen Kanal 0, ich brauche aber Kanal 3, der noch nicht einmal in Betracht gezogen wird vom IOBroker -
@michaelxhoffmann sagte in HMIP-PS Datenpunkte:
ich brauche aber Kanal 3,
was ist denn Kanal 3?
Wie sieht da die Konfig in der CCU aus?Hattest du irgendwo Screenshots der Konfig der HM-RPC und der Rega gezeigt?
Laufen andere HmIP Geräte korrekt? -
also nein die hatte ich noch nicht gepostet.
was mir in den Objekten auch auffällt ist, dass der Datenpunkt kein Pictogramm vorangestellt hat.
-
@michaelxhoffmann sagte in HMIP-PS Datenpunkte:
also nein die hatte ich noch nicht gepostet.
Der Haken bei erenut einlesen müsste von alleine weggehen, wenn alles klappt.
Da er noch da ist scheint etwas anderes nicht zu stimmen.Die Seite Weitere Einstellungen fehlt noch
Was hast du da als Callback-Adresse drin? -
GELÖST
@Homoran Die Callbackadresse in den zusätzlichen Einstellungen de hm-rpc Instanz für die IP Geräte war schuld! ICH DANKE DIR! Statt 192.168.178.45 stand da 192.168.78.45 drin. Nachdem ich es geändert habe ist der HMIP-PS Datenpunkt korrekt in den Objekten!
-
@michaelxhoffmann
Super!Da sieht man mal wieder wie wichtig Screenshots von Konfigurationen sind!
-
@Homoran Das ist wahr! Das Problem ist nur, dass ich das nicht wahrgenommen habe, dass da noch mehr Konfigurationsseiten sind.