NEWS
Homematic IP (Beschleunigungssensor): Kein Datenpunkt
-
Hallo
Habe heute mein erstes Homematic IP Gerät (Beschleunigungssensor) eingebunden und deshalb in iobroker eine neue Adapterinstanz angelegt.
Im Log findet sich Folgendes.
Im Log steht ich soll das hier bitte dem Entwickler schicken
hm-rpc.2 2019-01-07 01:05:33.480 warn Send this info to developer: {"type":"meta","meta":{"adapter":"hm-rpc","type":"paramsetDescription"},"common":{},"native":{"MOTION":{"MIN":false,"OPERATIONS":5,"MAX":true,"FLAGS":1,"ID":"MOTION","TYP hm-rpc.2 2019-01-07 01:05:33.480 warn Send this info to developer: _id: "hm-rpc.meta.VALUES.HmIP-SAM.ACCELERATION_TRANSCEIVER.1" hm-rpc.2 2019-01-07 01:05:33.429 info xmlrpc -> getParamsetDescription ["000F18A98C92BD:1","VALUES"] hm-rpc.2 2019-01-07 01:05:33.381 warn Send this info to developer: {"type":"meta","meta":{"adapter":"hm-rpc","type":"paramsetDescription"},"common":{},"native":{"CONFIG_PENDING":{"MIN":false,"OPERATIONS":5,"MAX":true,"FLAGS":9,"ID":"CONF hm-rpc.2 2019-01-07 01:05:33.380 warn Send this info to developer: _id: "hm-rpc.meta.VALUES.HmIP-SAM.MAINTENANCE.1" hm-rpc.2 2019-01-07 01:05:33.080 info xmlrpc -> getParamsetDescription ["000F18A98C92BD:0","VALUES"] hm-rpc.2 2019-01-07 01:05:32.895 info xmlrpc <- newDevices 6 hm-rpc.2 2019-01-07 01:05:32.683 info xmlrpc -> 0 devices hm-rpc.2 2019-01-07 01:05:32.676 info xmlrpc <- listDevices ["hm-rpc.2"] hm-rpc.2 2019-01-07 01:05:32.446 info Connected hm-rpc.2 2019-01-07 01:05:32.362 info xmlrpc client is trying to connect to 192.168.111.160:2010/ with ["http://192.168.111.176:2010","hm-rpc.2"] hm-rpc.2 2019-01-07 01:05:32.362 info xmlrpc server is trying to listen on 192.168.111.176:2010 hm-rpc.2 2019-01-07 01:05:32.203 info starting. Version 1.8.3 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v8.14.0 hm-rpc.2 2019-01-07 01:05:32.060 info States connected to redis: 127.0.0.1:6379
Ausserdem werden die Ämderungen nicht an iobroker gemeldet, bzw. ich sehe sie nicht:
Man sieht nirgend die Meldung wie sie in der CCU steht ("Bewegung erkannt/senkrecht"). Es gibt nur den Datenpunkt Motion.Version von hm-rpc ist 1.8.3, Node ist v8.14.0, Nodejs ist v8.14.0
Gruss Ralf
-
Bitte mal die send this Info to developer Zeilen aus dem Log auf der Platte oder per log herunterladen kopieren, da sonst angeschnitten.
-
Ich nutze diesen Sensor auch, der Datenpunkt Motion ist der, der die Bewegung meldet (true/false); waagerecht/senkrecht wird nur in der CCU angezeigt.
-
Hallo
Anbei ein Auszg aus dem Logfile
2019-01-07 01:05:32.060 - [32minfo[39m: hm-rpc.2 States connected to redis: 127.0.0.1:6379 2019-01-07 01:05:32.203 - [32minfo[39m: hm-rpc.2 starting. Version 1.8.3 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v8.14.0 2019-01-07 01:05:32.362 - [32minfo[39m: hm-rpc.2 xmlrpc server is trying to listen on 192.168.111.176:2010 2019-01-07 01:05:32.362 - [32minfo[39m: hm-rpc.2 xmlrpc client is trying to connect to 192.168.111.160:2010/ with ["http://192.168.111.176:2010","hm-rpc.2"] 2019-01-07 01:05:32.446 - [32minfo[39m: hm-rpc.2 Connected 2019-01-07 01:05:32.676 - [32minfo[39m: hm-rpc.2 xmlrpc <- listDevices ["hm-rpc.2"] 2019-01-07 01:05:32.683 - [32minfo[39m: hm-rpc.2 xmlrpc -> 0 devices 2019-01-07 01:05:32.895 - [32minfo[39m: hm-rpc.2 xmlrpc <- newDevices 6 2019-01-07 01:05:33.080 - [32minfo[39m: hm-rpc.2 xmlrpc -> getParamsetDescription ["000F18A98C92BD:0","VALUES"] 2019-01-07 01:05:33.380 - [33mwarn[39m: hm-rpc.2 Send this info to developer: _id: "hm-rpc.meta.VALUES.HmIP-SAM.MAINTENANCE.1" 2019-01-07 01:05:33.381 - [33mwarn[39m: hm-rpc.2 Send this info to developer: {"type":"meta","meta":{"adapter":"hm-rpc","type":"paramsetDescription"},"common":{},"native":{"CONFIG_PENDING":{"MIN":false,"OPERATIONS":5,"MAX":true,"FLAGS":9,"ID":"CONFIG_PENDING","TYPE":"BOOL","DEFAULT":false},"DUTY_CYCLE":{"MIN":false,"OPERATIONS":5,"MAX":true,"FLAGS":1,"ID":"DUTY_CYCLE","TYPE":"BOOL","DEFAULT":false},"LOW_BAT":{"MIN":false,"OPERATIONS":5,"MAX":true,"FLAGS":9,"ID":"LOW_BAT","TYPE":"BOOL","DEFAULT":false},"UNREACH":{"MIN":false,"OPERATIONS":5,"MAX":true,"FLAGS":25,"ID":"UNREACH","TYPE":"BOOL","DEFAULT":false},"RSSI_DEVICE":{"MIN":-128,"OPERATIONS":5,"MAX":127,"FLAGS":1,"ID":"RSSI_DEVICE","TYPE":"INTEGER","DEFAULT":0},"SENSOR_ERROR":{"MIN":false,"OPERATIONS":5,"MAX":true,"FLAGS":9,"ID":"SENSOR_ERROR","TYPE":"BOOL","DEFAULT":false},"OPERATING_VOLTAGE":{"MIN":0,"OPERATIONS":5,"MAX":25.2,"FLAGS":1,"ID":"OPERATING_VOLTAGE","TYPE":"FLOAT","DEFAULT":0},"RSSI_PEER":{"MIN":-128,"OPERATIONS":5,"MAX":127,"FLAGS":1,"ID":"RSSI_PEER","TYPE":"INTEGER","DEFAULT":0},"ERROR_CODE":{"MIN":0,"OPERATIONS":5,"MAX":255,"FLAGS":9,"ID":"ERROR_CODE","TYPE":"INTEGER","DEFAULT":0},"UPDATE_PENDING":{"MIN":false,"OPERATIONS":5,"MAX":true,"FLAGS":9,"ID":"UPDATE_PENDING","TYPE":"BOOL","DEFAULT":false}}} 2019-01-07 01:05:33.429 - [32minfo[39m: hm-rpc.2 xmlrpc -> getParamsetDescription ["000F18A98C92BD:1","VALUES"] 2019-01-07 01:05:33.480 - [33mwarn[39m: hm-rpc.2 Send this info to developer: _id: "hm-rpc.meta.VALUES.HmIP-SAM.ACCELERATION_TRANSCEIVER.1" 2019-01-07 01:05:33.480 - [33mwarn[39m: hm-rpc.2 Send this info to developer: {"type":"meta","meta":{"adapter":"hm-rpc","type":"paramsetDescription"},"common":{},"native":{"MOTION":{"MIN":false,"OPERATIONS":5,"MAX":true,"FLAGS":1,"ID":"MOTION","TYPE":"BOOL","DEFAULT":false}}} 2019-01-07 01:05:33.534 - [32minfo[39m: host.ioBroker-Tinker object change system.adapter.hm-rpc.2 2019-01-07 01:05:33.535 - [32minfo[39m: host.ioBroker-Tinker stopInstance system.adapter.hm-rpc.2 2019-01-07 01:05:34.535 - [32minfo[39m: host.ioBroker-Tinker stopInstance timeout "1000 system.adapter.hm-rpc.2 killing pid 10497 2019-01-07 01:05:34.537 - [32minfo[39m: hm-rpc.2 xmlrpc -> 192.168.111.160:2010/ init ["http://192.168.111.176:2010",""] 2019-01-07 01:05:34.596 - [32minfo[39m: hm-rpc.2 Disconnected 2019-01-07 01:05:34.600 - [32minfo[39m: hm-rpc.2 xmlrpc -> 192.168.111.160:2010/ init ["http://192.168.111.176:2010",""] 2019-01-07 01:05:34.614 - [32minfo[39m: host.ioBroker-Tinker instance system.adapter.hm-rpc.2 terminated with code 0 (OK) 2019-01-07 01:05:37.053 - [32minfo[39m: host.ioBroker-Tinker instance system.adapter.hm-rpc.2 started with pid 10507 2019-01-07 01:05:37.737 - [32minfo[39m: hm-rpc.2 States connected to redis: 127.0.0.1:6379 2019-01-07 01:05:37.877 - [32minfo[39m: hm-rpc.2 starting. Version 1.8.3 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v8.14.0 2019-01-07 01:05:38.025 - [32minfo[39m: hm-rpc.2 xmlrpc server is trying to listen on 192.168.111.176:2010 2019-01-07 01:05:38.025 - [32minfo[39m: hm-rpc.2 xmlrpc client is trying to connect to 192.168.111.160:2010/ with ["http://192.168.111.176:2010","hm-rpc.2"] 2019-01-07 01:05:38.126 - [32minfo[39m: hm-rpc.2 Connected 2019-01-07 01:05:38.419 - [32minfo[39m: hm-rpc.2 xmlrpc <- listDevices ["hm-rpc.2"] 2019-01-07 01:05:38.426 - [32minfo[39m: hm-rpc.2 xmlrpc -> 0 devices 2019-01-07 01:05:38.691 - [32minfo[39m: hm-rpc.2 xmlrpc <- newDevices 6 2019-01-07 01:05:38.698 - [32minfo[39m: hm-rpc.2 new HmIP devices/channels after filter: 0 2019-01-07 01:06:01.232 - [32minfo[39m: tvspielfilm.0 force terminating adapter after 1 minute 2019-01-07 01:06:01.751 - [32minfo[39m: host.ioBroker-Tinker instance system.adapter.tvspielfilm.0 terminated with code 0 (OK) 2019-01-07 01:06:47.973 - [32minfo[39m: javascript.0 script.js.common.Statusansagen: TempUnter. im Hauswirtschaftsraum:16.6 2019-01-07 01:08:38.132 - [33mwarn[39m: hm-rpc.2 [KEEPALIVE] Connection timed out 2019-01-07 01:09:01.659 - [32minfo[39m: javascript.0 script.js.common.Statusansagen: TempUnter. im Hauswirtschaftsraum:16.7 2019-01-07 01:09:08.624 - [32minfo[39m: hm-rpc.2 xmlrpc <- listDevices ["hm-rpc.2"]
Die Date selbst ist zu gross.
Gruss Ralf
-
Ich nutze diesen Sensor auch, der Datenpunkt Motion ist der, der die Bewegung meldet (true/false); waagerecht/senkrecht wird nur in der CCU angezeigt. `
Ach, echt? Sonst gibt's da nichts?
Dann muss ich nochmal schauen. Ich hab mit dem Ding rumgewackelt; in der CCU hat sich was getan, beim IOBroker nicht. Ich prüf das aber nochmal.
Gruss Ralf
-
-
Danke
Jetzt gehts bei mir auch.
Der Trick war ,dass man im Rega Adapter auch HM-IP eintragen muss!
Gruss Ralf
-
Moin,
kann man den nun fürs Garagentor nehmen oder nicht ?
( ich habe keine CCU, nur den hmip Adapter )Gibt es da nur den Zustand true/false oder auch senkrecht waagrecht ?
Ich habs noch nicht ganz verstanden.Danke, Gruß