Neue Homematic IP Geräte, CCU2 inkl. ioBroker

ple

Mal eine Frage zu HM IP.

Ich habe eine 2te Instanz gemacht für die HM-IP Geräte und habe nur die IP Adresse eingegeben.

Ist das normal, dass sich das Log füllt mit der Instanz und such neue Geräte oder so?

! ````
m-rpc.1 2017-08-30 06:04:55.040 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 06:04:54.838 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 06:04:54.550 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 06:04:54.464 info xmlrpc <- listDevices ["hm-rpc.1"]
host.orangepiplus2e 2017-08-30 06:03:05.286 info instance system.adapter.dwd.0 terminated with code 0 (OK)
dwd.0 2017-08-30 06:03:04.279 info starting. Version 2.2.1 in /opt/iobroker/node_modules/iobroker.dwd, node: v6.11.2
host.orangepiplus2e 2017-08-30 06:03:00.213 info instance system.adapter.dwd.0 started with pid 27346
hm-rpc.1 2017-08-30 05:56:54.979 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 05:56:54.949 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 05:56:54.635 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 05:56:54.430 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 05:53:24.788 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 05:53:24.765 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 05:53:24.436 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 05:53:24.255 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 05:49:54.635 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 05:49:54.611 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 05:49:54.333 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 05:49:54.209 info xmlrpc <- listDevices ["hm-rpc.1"]
telegram.0 2017-08-30 05:47:26.042 info getMe (reconnect): {"id":354375413,"is_bot":true,"first_name":"Haus","username":"Heimat_bot"}
hm-rpc.1 2017-08-30 05:46:24.596 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 05:46:24.571 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 05:46:24.270 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 05:46:24.234 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 05:42:54.458 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 05:42:54.431 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 05:42:54.146 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 05:42:54.122 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 05:39:24.444 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 05:39:24.421 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 05:39:24.114 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 05:39:24.066 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 05:35:54.568 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 05:35:54.526 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 05:35:54.224 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 05:35:54.151 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 05:32:24.314 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 05:32:24.291 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 05:32:24.012 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 05:32:23.927 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 05:28:54.258 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 05:28:54.212 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 05:28:53.921 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 05:28:53.869 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 05:25:24.100 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 05:25:24.075 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 05:25:23.941 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 05:25:23.907 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 05:20:24.237 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 05:20:24.189 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 05:20:23.860 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 05:20:23.785 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 05:16:54.010 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 05:16:53.989 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 05:16:53.701 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 05:16:53.661 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 05:13:23.830 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 05:13:23.805 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 05:13:23.687 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 05:13:23.620 info xmlrpc <- listDevices ["hm-rpc.1"]
host.orangepiplus2e 2017-08-30 05:12:14.093 info instance system.adapter.weatherunderground.0 terminated with code 0 (OK)
weatherunderground.0 2017-08-30 05:12:11.122 debug all forecast values set
weatherunderground.0 2017-08-30 05:12:10.292 debug all current conditions values set
weatherunderground.0 2017-08-30 05:12:04.668 debug calling forecast: http://api.wunderground.com/api/d16bdda8e41f40ae/forecast/hourly/lang:DL/q/52.220,7.391.json
weatherunderground.0 2017-08-30 05:12:04.636 debug calling current: http://api.wunderground.com/api/d16bdda8e41f40ae/conditions/lang:DL/q/52.220,7.391.json
weatherunderground.0 2017-08-30 05:12:04.484 debug init forecast objects
weatherunderground.0 2017-08-30 05:12:04.472 debug init conditions objects
weatherunderground.0 2017-08-30 05:12:04.462 debug on ready 222 : DL true true true true
weatherunderground.0 2017-08-30 05:12:04.448 info starting. Version 1.0.8 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v6.11.2
weatherunderground.0 2017-08-30 05:12:04.321 debug statesDB connected
weatherunderground.0 2017-08-30 05:12:04.204 debug objectDB connected
host.orangepiplus2e 2017-08-30 05:12:00.216 info instance system.adapter.weatherunderground.0 started with pid 25708
hm-rpc.1 2017-08-30 05:09:53.974 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 05:09:53.951 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 05:09:53.675 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 05:09:53.639 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 05:06:23.904 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 05:06:23.872 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 05:06:23.575 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 05:06:23.510 info xmlrpc <- listDevices ["hm-rpc.1"]
host.orangepiplus2e 2017-08-30 05:03:05.635 info instance system.adapter.dwd.0 terminated with code 0 (OK)
dwd.0 2017-08-30 05:03:04.606 info starting. Version 2.2.1 in /opt/iobroker/node_modules/iobroker.dwd, node: v6.11.2
host.orangepiplus2e 2017-08-30 05:03:00.176 info instance system.adapter.dwd.0 started with pid 25407
hm-rpc.1 2017-08-30 05:02:53.824 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 05:02:53.802 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 05:02:53.501 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 05:02:53.444 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 04:59:23.904 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 04:59:23.862 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 04:59:23.547 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 04:59:23.481 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 04:55:53.779 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 04:55:53.737 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 04:55:53.429 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 04:55:53.367 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 04:49:23.694 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 04:49:23.672 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 04:49:23.380 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 04:49:23.300 info xmlrpc <- listDevices ["hm-rpc.1"]
telegram.0 2017-08-30 04:47:25.989 info getMe (reconnect): {"id":354375413,"is_bot":true,"first_name":"Haus","username":"Heimat_bot"}
hm-rpc.1 2017-08-30 04:45:53.447 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 04:45:53.415 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 04:45:53.117 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 04:45:53.055 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 04:42:23.365 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 04:42:23.341 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 04:42:23.054 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 04:42:22.992 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 04:38:53.419 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 04:38:53.392 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 04:38:53.108 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 04:38:53.044 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 04:35:23.340 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 04:35:23.294 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 04:35:22.971 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 04:35:22.891 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 04:31:53.277 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 04:31:53.228 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 04:31:52.901 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 04:31:52.826 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 04:28:23.216 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 04:28:23.192 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 04:28:22.864 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 04:28:22.794 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 04:24:53.077 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 04:24:53.043 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 04:24:52.764 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 04:24:52.685 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 04:21:23.396 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 04:21:23.371 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 04:21:23.103 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 04:21:22.584 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 04:17:52.984 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 04:17:52.932 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 04:17:52.652 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 04:17:52.577 info xmlrpc <- listDevices ["hm-rpc.1"]
hm-rpc.1 2017-08-30 04:14:23.652 info new HmIP devices/channels after filter: 0
hm-rpc.1 2017-08-30 04:14:22.858 info xmlrpc <- newDevices 3
hm-rpc.1 2017-08-30 04:14:22.522 info xmlrpc -> 0 devices
hm-rpc.1 2017-08-30 04:14:22.472 info xmlrpc <- listDevices ["hm-rpc.1"]
host.orangepiplus2e 2017-08-30 04:12:14.246 info instance system.adapter.weatherunderground.0 terminated with code 0 (OK)
weatherunderground.0 2017-08-30 04:12:11.303 debug all forecast values set
weatherunderground.0 2017-08-30 04:12:10.651 debug all current conditions values set
weatherunderground.0 2017-08-30 04:12:05.058 debug calling forecast: http://api.wunderground.com/api/d16bdda8e41f40ae/forecast/hourly/lang:DL/q/52.220,7.391.json
weatherunderground.0 2017-08-30 04:12:05.026 debug calling current: http://api.wunderground.com/api/d16bdda8e41f40ae/conditions/lang:DL/q/52.220,7.391.json
weatherunderground.0 2017-08-30 04:12:04.913 debug init forecast objects
weatherunderground.0 2017-08-30 04:12:04.903 debug init conditions objects
weatherunderground.0 2017-08-30 04:12:04.890 debug on ready 222 : DL true true true true
weatherunderground.0 2017-08-30 04:12:04.877 info starting. Version 1.0.8 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v6.11.2
weatherunderground.0 2017-08-30 04:12:04.678 debug statesDB connected
weatherunderground.0 2017-08-30 04:12:04.556 debug objectDB connected

Homoran

~~@ple:~~

Ich habe eine 2te Instanz gemacht für die HM-IP Geräte und habe nur die IP Adresse eingegeben. `
Aber doch hoffentlich auch ip als Daemon ausgewählt, oder?

Bitte Screenshot von der Konfiguration.

Gruß

Rainer

ple

hier die Einstellungen.

Mich wundert es nur, dass die Instanz das Log vollballert.

Der Präsenzmelder funktioniert wie er soll, soweit alles ok
1241_bildschirmfoto_2017-08-30_um_14.08.43.png

Nabla

Bei mir wird das log auch vollgeschrieben. (kommt alle paar Minuten)

Vor allem habe ich nur die Zentrale und einen Türkontakt :lol:

hm-rpc.0 2017-09-01 20:09:49.216 info new HmIP devices/channels after filter: 0

hm-rpc.0 2017-09-01 20:09:49.206 info xmlrpc <- newDevices 3

hm-rpc.0 2017-09-01 20:09:48.952 info xmlrpc -> 0 devices

hm-rpc.0 2017-09-01 20:09:48.934 info xmlrpc <- listDevices ["hm-rpc.0"]

Daemon:Homematic IP

Ist es eigentlich korrekt, dass vom optischen Türkontakt nur State übertragen wird?

Wie sehe ich denn wann die Batterien leer sind? Sehe selbst in der CCU2 nichts.

Oder schickt mir die CCU ne E-Mail wenn es soweit ist?

Homoran

~~@Nabla:~~

Ist es eigentlich korrekt, dass vom optischen Türkontakt nur State übertragen wird? `
Nö:

Gruß

Rainer

Nabla

alles klar. Ich erkenne meinen Fehler und behaupte jetzt genau das Gegenteil

(Ich dachte 0 ist die Zentrale und 1 ist der Sensor. :? :? :? )

Homoran

~~@Nabla:~~

Ich dachte 0 ist die Zentrale und 1 ist der Sensor. `
…und selbst da ist ein LowBat

Gruß

Rainer

Nabla

~~@ple:~~

Mich wundert es nur, dass die Instanz das Log vollballert. `

Kann man hier nicht irgendwie die drei Zeilen zu einer Zeile zusammenfassen um das Log ein wenig übersichtlicher zu haben?

Zipkart

~~@andyb:~~

Ich hab mir vor 3 Tagen den von Mi home bestellt, mal schauen was der kann.

https://m.gearbest.com/smart-light-bulb/pp_257678.html `

Hallo!

Hast du den Sensor schon in Betrieb genommen? Wie wird er denn angebunden?

Kann Ich PI3,lightify,hue, TRÅDFRI,wemo benutzen oder brauche ich schon wieder ein neueres Gateway?

Gruß Stefan

IOBROKER MULTIHOST / MAX!/Homematic/Mysensors/Lightify/Wemo/Tasmota …

Fatmax

~~@Zipkart:~~

~~@andyb:~~

Ich hab mir vor 3 Tagen den von Mi home bestellt, mal schauen was der kann.

https://m.gearbest.com/smart-light-bulb/pp_257678.html `

Hallo!

Hast du den Sensor schon in Betrieb genommen? Wie wird er denn angebunden?

Kann Ich PI3,lightify,hue, TRÅDFRI,wemo benutzen oder brauche ich schon wieder ein neueres Gateway?

Gruß Stefan

IOBROKER MULTIHOST / MAX!/Homematic/Mysensors/Lightify/Wemo/Tasmota … `

Das würde mich auch interessieren, ob es eine Möglichkeit gibt den Sensor in Iobroker einzubinden.

Gruß,

Fatmax

Community Forum

NEWS

Neue Homematic IP Geräte, CCU2 inkl. ioBroker

Support us

545

32.5k

81.7k

1.3m