NEWS
HM-RPC Adapter keine Werte nach Serverneustart
-
Hallo zusammen,
ich habe das Problem, wenn ich meinen IO-Broker Server komplett neu starte, dass der HM-RPC Adapter keine Werte von der CCU bekommt.
Erst wenn ich den Adapter dann noch einmal manuell neu starte (im LOG um 15:44:27), bekommt er wieder Daten.
Adapterversion: 1.15.12hm-rpc.0 2022-06-29 15:44:32.345 info Connected hm-rpc.0 2022-06-29 15:44:32.320 info xmlrpc -> 93 devices hm-rpc.0 2022-06-29 15:44:32.301 info xmlrpc <- listDevices ["IOBroker-Server:hm-rpc.0:025be6186ff90b9a5f1be3027ff93e0e"] hm-rpc.0 2022-06-29 15:44:32.287 info xmlrpc <- system.listMethods ["IOBroker-Server:hm-rpc.0:025be6186ff90b9a5f1be3027ff93e0e"] hm-rpc.0 2022-06-29 15:44:32.274 info xmlrpc client is trying to connect to 192.168.1.100:2001/ with ["http://192.168.1.25:2001","IOBroker-Server:hm-rpc.0:025be6186ff90b9a5f1be3027ff93e0e"] hm-rpc.0 2022-06-29 15:44:32.273 info xmlrpc server is trying to listen on 0.0.0.0:2001 hm-rpc.0 2022-06-29 15:44:32.183 info starting. Version 1.15.12 in I:/ioBroker/node_modules/iobroker.hm-rpc, node: v16.15.1, js-controller: 4.0.23 hm-rpc.0 2022-06-29 15:44:27.949 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason hm-rpc.0 2022-06-29 15:44:27.948 info terminating hm-rpc.0 2022-06-29 15:44:27.948 info Disconnected hm-rpc.0 2022-06-29 15:44:27.943 info xmlrpc -> 192.168.1.100:2001/ init ["http://192.168.1.25:2001",""] hm-rpc.0 2022-06-29 15:44:27.942 info Got terminate signal TERMINATE_YOURSELF hm-rpc.0 2022-06-29 15:35:35.578 info Connected hm-rpc.0 2022-06-29 15:35:35.536 info xmlrpc -> 93 devices hm-rpc.0 2022-06-29 15:35:35.515 info xmlrpc <- listDevices ["IOBroker-Server:hm-rpc.0:a34cc66205223607b79ae1f8af6e7f85"] hm-rpc.0 2022-06-29 15:35:35.512 info xmlrpc <- system.listMethods ["IOBroker-Server:hm-rpc.0:a34cc66205223607b79ae1f8af6e7f85"] hm-rpc.0 2022-06-29 15:35:35.500 info xmlrpc client is trying to connect to 192.168.1.100:2001/ with ["http://192.168.1.25:2001","IOBroker-Server:hm-rpc.0:a34cc66205223607b79ae1f8af6e7f85"] hm-rpc.0 2022-06-29 15:35:35.500 info xmlrpc server is trying to listen on 0.0.0.0:2001 hm-rpc.0 2022-06-29 15:35:35.183 info starting. Version 1.15.12 in I:/ioBroker/node_modules/iobroker.hm-rpc, node: v16.15.1, js-controller: 4.0.23 hm-rpc.0 2022-06-29 15:35:32.505 warn Terminated (ADAPTER_ALREADY_RUNNING): Without reason hm-rpc.0 2022-06-29 15:35:32.504 error hm-rpc.0 already running
@surfer09 was verbirgt sich hinter den IPs ...25 und ...100?
wo genau läuft dein ioBroker drauf? -
Das Log danach mit dem erzwungenen Neustart bring so nicht viel , Interessanter ist davor ob es Fehler dazu gibt !?
Wenn nicht , Adapter in der Logstufe DEBUG setzten und den Server neu starten was dann kommt / warum er nach deiner Ansicht die Daten nicht abholt ..
@glasfaser
Direkt nach dem Serverneustart:2022-06-29 16:14:34.743 - debug: hm-rpc.0 (8864) Redis Objects: Use Redis connection: 127.0.0.1:9001 2022-06-29 16:14:34.758 - debug: hm-rpc.0 (8864) Objects client ready ... initialize now 2022-06-29 16:14:34.759 - debug: hm-rpc.0 (8864) Objects create System PubSub Client 2022-06-29 16:14:34.759 - debug: hm-rpc.0 (8864) Objects create User PubSub Client 2022-06-29 16:14:34.774 - debug: hm-rpc.0 (8864) Objects client initialize lua scripts 2022-06-29 16:14:34.781 - debug: hm-rpc.0 (8864) Objects connected to redis: 127.0.0.1:9001 2022-06-29 16:14:34.794 - debug: hm-rpc.0 (8864) Redis States: Use Redis connection: 127.0.0.1:9000 2022-06-29 16:14:34.798 - debug: hm-rpc.0 (8864) States create System PubSub Client 2022-06-29 16:14:34.799 - debug: hm-rpc.0 (8864) States create User PubSub Client 2022-06-29 16:14:34.807 - debug: hm-rpc.0 (8864) States connected to redis: 127.0.0.1:9000 2022-06-29 16:14:34.808 - error: hm-rpc.0 (8864) hm-rpc.0 already running 2022-06-29 16:14:34.809 - debug: hm-rpc.0 (8864) Plugin sentry destroyed 2022-06-29 16:14:34.809 - warn: hm-rpc.0 (8864) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2022-06-29 16:14:36.884 - debug: hm-rpc.0 (9036) Redis Objects: Use Redis connection: 127.0.0.1:9001 2022-06-29 16:14:36.899 - debug: hm-rpc.0 (9036) Objects client ready ... initialize now 2022-06-29 16:14:36.899 - debug: hm-rpc.0 (9036) Objects create System PubSub Client 2022-06-29 16:14:36.900 - debug: hm-rpc.0 (9036) Objects create User PubSub Client 2022-06-29 16:14:36.914 - debug: hm-rpc.0 (9036) Objects client initialize lua scripts 2022-06-29 16:14:36.917 - debug: hm-rpc.0 (9036) Objects connected to redis: 127.0.0.1:9001 2022-06-29 16:14:36.925 - debug: hm-rpc.0 (9036) Redis States: Use Redis connection: 127.0.0.1:9000 2022-06-29 16:14:36.930 - debug: hm-rpc.0 (9036) States create System PubSub Client 2022-06-29 16:14:36.930 - debug: hm-rpc.0 (9036) States create User PubSub Client 2022-06-29 16:14:36.937 - debug: hm-rpc.0 (9036) States connected to redis: 127.0.0.1:9000 2022-06-29 16:14:36.959 - debug: hm-rpc.0 (9036) Plugin sentry Initialize Plugin (enabled=true) 2022-06-29 16:14:37.054 - info: hm-rpc.0 (9036) starting. Version 1.15.12 in I:/ioBroker/node_modules/iobroker.hm-rpc, node: v16.15.1, js-controller: 4.0.23 2022-06-29 16:14:37.080 - debug: hm-rpc.0 (9036) Schedule restart: 30 5 * * * 2022-06-29 16:14:37.218 - info: hm-rpc.0 (9036) xmlrpc server is trying to listen on 0.0.0.0:2001 2022-06-29 16:14:37.218 - info: hm-rpc.0 (9036) xmlrpc client is trying to connect to 192.168.1.100:2001/ with ["http://192.168.1.25:2001","IOBroker-Server:hm-rpc.0:cb10e00673d97b9f3b28ccb982a1f291"] 2022-06-29 16:14:37.219 - debug: hm-rpc.0 (9036) Connect... 2022-06-29 16:14:37.219 - debug: hm-rpc.0 (9036) xmlrpc -> 192.168.1.100:2001/ init ["http://192.168.1.25:2001","IOBroker-Server:hm-rpc.0:cb10e00673d97b9f3b28ccb982a1f291"] 2022-06-29 16:14:37.222 - debug: hm-rpc.0 (9036) start connecting interval 2022-06-29 16:14:37.231 - info: hm-rpc.0 (9036) xmlrpc <- system.listMethods ["IOBroker-Server:hm-rpc.0:cb10e00673d97b9f3b28ccb982a1f291"] 2022-06-29 16:14:37.235 - info: hm-rpc.0 (9036) xmlrpc <- listDevices ["IOBroker-Server:hm-rpc.0:cb10e00673d97b9f3b28ccb982a1f291"] 2022-06-29 16:14:37.236 - debug: hm-rpc.0 (9036) No suitable Lua script, fallback to keys!: function(doc) { if (doc._id.match(/^hm-rpc\.[0-9]+\.\*?[A-Za-z0-9_-]+(\.[0-9]+)?$/)) { emit(doc._id, {ADDRESS:(doc.native?doc.native.ADDRESS:''),VERSION:(doc.native?doc.native.VERSION:'')}); } } 2022-06-29 16:14:37.256 - info: hm-rpc.0 (9036) xmlrpc -> 93 devices 2022-06-29 16:14:37.279 - info: hm-rpc.0 (9036) Connected 2022-06-29 16:14:37.279 - debug: hm-rpc.0 (9036) clear connecting interval 2022-06-29 16:14:37.279 - debug: hm-rpc.0 (9036) start ping interval 2022-06-29 16:14:37.279 - debug: hm-rpc.0 (9036) xml multicall : IOBroker-Server:hm-rpc.0:cb10e00673d97b9f3b28ccb982a1f291,LEQ1003243:0,STICKY_UNREACH,true 2022-06-29 16:14:37.280 - debug: hm-rpc.0 (9036) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:cb10e00673d97b9f3b28ccb982a1f291","LEQ1003243:0","STICKY_UNREACH",true] 2022-06-29 16:14:37.280 - debug: hm-rpc.0 (9036) hm-rpc.0.LEQ1003243.0.STICKY_UNREACH ==> UNIT: "" (min: undefined, max: undefined) From "true" => "true" 2022-06-29 16:14:37.280 - debug: hm-rpc.0 (9036) xml multicall : IOBroker-Server:hm-rpc.0:cb10e00673d97b9f3b28ccb982a1f291,OEQ0015243:0,STICKY_UNREACH,true 2022-06-29 16:14:37.280 - debug: hm-rpc.0 (9036) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:cb10e00673d97b9f3b28ccb982a1f291","OEQ0015243:0","STICKY_UNREACH",true] 2022-06-29 16:14:37.280 - debug: hm-rpc.0 (9036) hm-rpc.0.OEQ0015243.0.STICKY_UNREACH ==> UNIT: "" (min: undefined, max: undefined) From "true" => "true"Auf die Klingeltaster gedrückt (Tasterschnittstelle) "no matching device??"
hm-rpc.0 2022-06-29 16:20:02.817 debug xmlrpc <- event: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f.LEQ0796944.1.INSTALL_TEST:true discarded, no matching device hm-rpc.0 2022-06-29 16:20:02.817 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f","LEQ0796944:1","INSTALL_TEST",true] hm-rpc.0 2022-06-29 16:20:02.817 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f,LEQ0796944:1,INSTALL_TEST,true hm-rpc.0 2022-06-29 16:20:02.814 debug xmlrpc <- event: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f.LEQ0796944.1.PRESS:true discarded, no matching device hm-rpc.0 2022-06-29 16:20:02.814 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f","LEQ0796944:1","PRESS",true] hm-rpc.0 2022-06-29 16:20:02.814 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f,LEQ0796944:1,PRESS,true hm-rpc.0 2022-06-29 16:20:01.066 debug xmlrpc <- event: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f.LEQ0796944.3.INSTALL_TEST:true discarded, no matching device hm-rpc.0 2022-06-29 16:20:01.066 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f","LEQ0796944:3","INSTALL_TEST",true] hm-rpc.0 2022-06-29 16:20:01.066 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f,LEQ0796944:3,INSTALL_TEST,true hm-rpc.0 2022-06-29 16:20:01.064 debug xmlrpc <- event: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f.LEQ0796944.3.PRESS:true discarded, no matching device hm-rpc.0 2022-06-29 16:20:01.064 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f","LEQ0796944:3","PRESS",true] hm-rpc.0 2022-06-29 16:20:01.064 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f,LEQ0796944:3,PRESS,true hm-rpc.0 2022-06-29 16:19:59.315 debug xmlrpc <- event: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f.LEQ0796944.1.INSTALL_TEST:true discarded, no matching device hm-rpc.0 2022-06-29 16:19:59.315 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f","LEQ0796944:1","INSTALL_TEST",true] hm-rpc.0 2022-06-29 16:19:59.315 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f,LEQ0796944:1,INSTALL_TEST,true hm-rpc.0 2022-06-29 16:19:59.313 debug xmlrpc <- event: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f.LEQ0796944.1.PRESS:true discarded, no matching device hm-rpc.0 2022-06-29 16:19:59.313 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f","LEQ0796944:1","PRESS",true] hm-rpc.0 2022-06-29 16:19:59.313 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f,LEQ0796944:1,PRESS,true hm-rpc.0 2022-06-29 16:19:57.816 debug xmlrpc <- event: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f.LEQ0796944.3.INSTALL_TEST:true discarded, no matching device hm-rpc.0 2022-06-29 16:19:57.816 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f","LEQ0796944:3","INSTALL_TEST",true] hm-rpc.0 2022-06-29 16:19:57.816 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f,LEQ0796944:3,INSTALL_TEST,true hm-rpc.0 2022-06-29 16:19:57.815 debug xmlrpc <- event: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f.LEQ0796944.3.PRESS:true discarded, no matching device hm-rpc.0 2022-06-29 16:19:57.815 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f","LEQ0796944:3","PRESS",true] hm-rpc.0 2022-06-29 16:19:57.815 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f,LEQ0796944:3,PRESS,trueAuf Klingeltastergedrückt, nach manuellem Adapterneustart (Klingel funktioniert):
hm-rpc.0 2022-06-29 16:23:46.343 debug hm-rpc.0.LEQ0796944.3.PRESS ==> UNIT: "" (min: undefined, max: undefined) From "true" => "true" hm-rpc.0 2022-06-29 16:23:46.342 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:defd888ef20521f7492a1f78f4819353","LEQ0796944:3","PRESS",true] hm-rpc.0 2022-06-29 16:23:46.342 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:defd888ef20521f7492a1f78f4819353,LEQ0796944:3,PRESS,true hm-rpc.0 2022-06-29 16:23:42.317 debug hm-rpc.0.LEQ0796944.3.PRESS ==> UNIT: "" (min: undefined, max: undefined) From "true" => "true" hm-rpc.0 2022-06-29 16:23:42.317 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:defd888ef20521f7492a1f78f4819353","LEQ0796944:3","PRESS",true] hm-rpc.0 2022-06-29 16:23:42.317 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:defd888ef20521f7492a1f78f4819353,LEQ0796944:3,PRESS,true hm-rpc.0 2022-06-29 16:23:40.571 debug hm-rpc.0.LEQ0796944.1.PRESS ==> UNIT: "" (min: undefined, max: undefined) From "true" => "true" hm-rpc.0 2022-06-29 16:23:40.571 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:defd888ef20521f7492a1f78f4819353","LEQ0796944:1","PRESS",true] hm-rpc.0 2022-06-29 16:23:40.571 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:defd888ef20521f7492a1f78f4819353,LEQ0796944:1,PRESS,true -
@surfer09 was verbirgt sich hinter den IPs ...25 und ...100?
wo genau läuft dein ioBroker drauf? -
@homoran IOBroker Server: 192.168.1.25, CCU: 192.168.1.100. Die CCU hat die Firmware 3.63.9.
-
@surfer09 sagte: IOBroker Server: 192.168.1.25
Dann wähle diese IP-Adresse mal als "Adapter Adresse" aus.
-
Hab das Problem auch... Aber glaub schon lange. Hab mir angewöhnt hmrega und rpc immer noch mal durchzu starten nach 5min
-
Hallo zusammen,
ich habe das Problem, wenn ich meinen IO-Broker Server komplett neu starte, dass der HM-RPC Adapter keine Werte von der CCU bekommt.
Erst wenn ich den Adapter dann noch einmal manuell neu starte (im LOG um 15:44:27), bekommt er wieder Daten.
Adapterversion: 1.15.12hm-rpc.0 2022-06-29 15:44:32.345 info Connected hm-rpc.0 2022-06-29 15:44:32.320 info xmlrpc -> 93 devices hm-rpc.0 2022-06-29 15:44:32.301 info xmlrpc <- listDevices ["IOBroker-Server:hm-rpc.0:025be6186ff90b9a5f1be3027ff93e0e"] hm-rpc.0 2022-06-29 15:44:32.287 info xmlrpc <- system.listMethods ["IOBroker-Server:hm-rpc.0:025be6186ff90b9a5f1be3027ff93e0e"] hm-rpc.0 2022-06-29 15:44:32.274 info xmlrpc client is trying to connect to 192.168.1.100:2001/ with ["http://192.168.1.25:2001","IOBroker-Server:hm-rpc.0:025be6186ff90b9a5f1be3027ff93e0e"] hm-rpc.0 2022-06-29 15:44:32.273 info xmlrpc server is trying to listen on 0.0.0.0:2001 hm-rpc.0 2022-06-29 15:44:32.183 info starting. Version 1.15.12 in I:/ioBroker/node_modules/iobroker.hm-rpc, node: v16.15.1, js-controller: 4.0.23 hm-rpc.0 2022-06-29 15:44:27.949 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason hm-rpc.0 2022-06-29 15:44:27.948 info terminating hm-rpc.0 2022-06-29 15:44:27.948 info Disconnected hm-rpc.0 2022-06-29 15:44:27.943 info xmlrpc -> 192.168.1.100:2001/ init ["http://192.168.1.25:2001",""] hm-rpc.0 2022-06-29 15:44:27.942 info Got terminate signal TERMINATE_YOURSELF hm-rpc.0 2022-06-29 15:35:35.578 info Connected hm-rpc.0 2022-06-29 15:35:35.536 info xmlrpc -> 93 devices hm-rpc.0 2022-06-29 15:35:35.515 info xmlrpc <- listDevices ["IOBroker-Server:hm-rpc.0:a34cc66205223607b79ae1f8af6e7f85"] hm-rpc.0 2022-06-29 15:35:35.512 info xmlrpc <- system.listMethods ["IOBroker-Server:hm-rpc.0:a34cc66205223607b79ae1f8af6e7f85"] hm-rpc.0 2022-06-29 15:35:35.500 info xmlrpc client is trying to connect to 192.168.1.100:2001/ with ["http://192.168.1.25:2001","IOBroker-Server:hm-rpc.0:a34cc66205223607b79ae1f8af6e7f85"] hm-rpc.0 2022-06-29 15:35:35.500 info xmlrpc server is trying to listen on 0.0.0.0:2001 hm-rpc.0 2022-06-29 15:35:35.183 info starting. Version 1.15.12 in I:/ioBroker/node_modules/iobroker.hm-rpc, node: v16.15.1, js-controller: 4.0.23 hm-rpc.0 2022-06-29 15:35:32.505 warn Terminated (ADAPTER_ALREADY_RUNNING): Without reason hm-rpc.0 2022-06-29 15:35:32.504 error hm-rpc.0 already running@surfer09 sagte in HM-RPC Adapter keine Werte nach Serverneustart:
keine Werte von der CCU
Diese mal neu gestartet !?
Welche CCU , aktuelle Firmware usw.
-
Hab das Problem auch... Aber glaub schon lange. Hab mir angewöhnt hmrega und rpc immer noch mal durchzu starten nach 5min
@warp735 sagte in HM-RPC Adapter keine Werte nach Serverneustart:
Hab das Problem auch... Aber glaub schon lange. Hab mir angewöhnt hmrega und rpc immer noch mal durchzu starten nach 5min
Ich hab das Problem auch schon lange. Habe mir aber zuerst nichts dabei gedacht. Da ich meinen Server jetzt aber auch neu installiert habe und der Fehler immer noch besteht, habe ich mir gedacht ich melde es mal.
-
@surfer09 sagte in HM-RPC Adapter keine Werte nach Serverneustart:
keine Werte von der CCU
Diese mal neu gestartet !?
Welche CCU , aktuelle Firmware usw.
@glasfaser sagte in HM-RPC Adapter keine Werte nach Serverneustart:
@surfer09 sagte in HM-RPC Adapter keine Werte nach Serverneustart:
keine Werte von der CCU
Diese mal neu gestartet !?
Welche CCU , aktuelle Firmware usw.
@glasfaser CCU3 Firmware 3.63.9
Nach Serverneustart kommen keine Werte, erst nach manuellem Adapterneustart.
IO-Broker Master/Slave auf Windows 11 64bit, NPM 10.9.4, Node 22.21.1 js-controller 7.0.7
-
@glasfaser sagte in HM-RPC Adapter keine Werte nach Serverneustart:
@surfer09 sagte in HM-RPC Adapter keine Werte nach Serverneustart:
keine Werte von der CCU
Diese mal neu gestartet !?
Welche CCU , aktuelle Firmware usw.
@glasfaser CCU3 Firmware 3.63.9
Nach Serverneustart kommen keine Werte, erst nach manuellem Adapterneustart.
@surfer09 sagte in HM-RPC Adapter keine Werte nach Serverneustart:
Nach Serverneustart kommen keine Werte, erst nach manuellem Adapterneustart.
Ja , das habe ich schon verstanden !
Die CCU ....
@glasfaser sagte in HM-RPC Adapter keine Werte nach Serverneustart:
Diese mal neu gestartet !?Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..
-
@surfer09 sagte in HM-RPC Adapter keine Werte nach Serverneustart:
Nach Serverneustart kommen keine Werte, erst nach manuellem Adapterneustart.
Ja , das habe ich schon verstanden !
Die CCU ....
@glasfaser sagte in HM-RPC Adapter keine Werte nach Serverneustart:
Diese mal neu gestartet !?,@glasfaser Die CCU habe ich nicht neu gestartet, zumindest nicht heute. Seitdem ich das Problem aber habe, habe ich sie schon mal neu gestartet.
-
@glasfaser
Direkt nach dem Serverneustart:2022-06-29 16:14:34.743 - debug: hm-rpc.0 (8864) Redis Objects: Use Redis connection: 127.0.0.1:9001 2022-06-29 16:14:34.758 - debug: hm-rpc.0 (8864) Objects client ready ... initialize now 2022-06-29 16:14:34.759 - debug: hm-rpc.0 (8864) Objects create System PubSub Client 2022-06-29 16:14:34.759 - debug: hm-rpc.0 (8864) Objects create User PubSub Client 2022-06-29 16:14:34.774 - debug: hm-rpc.0 (8864) Objects client initialize lua scripts 2022-06-29 16:14:34.781 - debug: hm-rpc.0 (8864) Objects connected to redis: 127.0.0.1:9001 2022-06-29 16:14:34.794 - debug: hm-rpc.0 (8864) Redis States: Use Redis connection: 127.0.0.1:9000 2022-06-29 16:14:34.798 - debug: hm-rpc.0 (8864) States create System PubSub Client 2022-06-29 16:14:34.799 - debug: hm-rpc.0 (8864) States create User PubSub Client 2022-06-29 16:14:34.807 - debug: hm-rpc.0 (8864) States connected to redis: 127.0.0.1:9000 2022-06-29 16:14:34.808 - error: hm-rpc.0 (8864) hm-rpc.0 already running 2022-06-29 16:14:34.809 - debug: hm-rpc.0 (8864) Plugin sentry destroyed 2022-06-29 16:14:34.809 - warn: hm-rpc.0 (8864) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2022-06-29 16:14:36.884 - debug: hm-rpc.0 (9036) Redis Objects: Use Redis connection: 127.0.0.1:9001 2022-06-29 16:14:36.899 - debug: hm-rpc.0 (9036) Objects client ready ... initialize now 2022-06-29 16:14:36.899 - debug: hm-rpc.0 (9036) Objects create System PubSub Client 2022-06-29 16:14:36.900 - debug: hm-rpc.0 (9036) Objects create User PubSub Client 2022-06-29 16:14:36.914 - debug: hm-rpc.0 (9036) Objects client initialize lua scripts 2022-06-29 16:14:36.917 - debug: hm-rpc.0 (9036) Objects connected to redis: 127.0.0.1:9001 2022-06-29 16:14:36.925 - debug: hm-rpc.0 (9036) Redis States: Use Redis connection: 127.0.0.1:9000 2022-06-29 16:14:36.930 - debug: hm-rpc.0 (9036) States create System PubSub Client 2022-06-29 16:14:36.930 - debug: hm-rpc.0 (9036) States create User PubSub Client 2022-06-29 16:14:36.937 - debug: hm-rpc.0 (9036) States connected to redis: 127.0.0.1:9000 2022-06-29 16:14:36.959 - debug: hm-rpc.0 (9036) Plugin sentry Initialize Plugin (enabled=true) 2022-06-29 16:14:37.054 - info: hm-rpc.0 (9036) starting. Version 1.15.12 in I:/ioBroker/node_modules/iobroker.hm-rpc, node: v16.15.1, js-controller: 4.0.23 2022-06-29 16:14:37.080 - debug: hm-rpc.0 (9036) Schedule restart: 30 5 * * * 2022-06-29 16:14:37.218 - info: hm-rpc.0 (9036) xmlrpc server is trying to listen on 0.0.0.0:2001 2022-06-29 16:14:37.218 - info: hm-rpc.0 (9036) xmlrpc client is trying to connect to 192.168.1.100:2001/ with ["http://192.168.1.25:2001","IOBroker-Server:hm-rpc.0:cb10e00673d97b9f3b28ccb982a1f291"] 2022-06-29 16:14:37.219 - debug: hm-rpc.0 (9036) Connect... 2022-06-29 16:14:37.219 - debug: hm-rpc.0 (9036) xmlrpc -> 192.168.1.100:2001/ init ["http://192.168.1.25:2001","IOBroker-Server:hm-rpc.0:cb10e00673d97b9f3b28ccb982a1f291"] 2022-06-29 16:14:37.222 - debug: hm-rpc.0 (9036) start connecting interval 2022-06-29 16:14:37.231 - info: hm-rpc.0 (9036) xmlrpc <- system.listMethods ["IOBroker-Server:hm-rpc.0:cb10e00673d97b9f3b28ccb982a1f291"] 2022-06-29 16:14:37.235 - info: hm-rpc.0 (9036) xmlrpc <- listDevices ["IOBroker-Server:hm-rpc.0:cb10e00673d97b9f3b28ccb982a1f291"] 2022-06-29 16:14:37.236 - debug: hm-rpc.0 (9036) No suitable Lua script, fallback to keys!: function(doc) { if (doc._id.match(/^hm-rpc\.[0-9]+\.\*?[A-Za-z0-9_-]+(\.[0-9]+)?$/)) { emit(doc._id, {ADDRESS:(doc.native?doc.native.ADDRESS:''),VERSION:(doc.native?doc.native.VERSION:'')}); } } 2022-06-29 16:14:37.256 - info: hm-rpc.0 (9036) xmlrpc -> 93 devices 2022-06-29 16:14:37.279 - info: hm-rpc.0 (9036) Connected 2022-06-29 16:14:37.279 - debug: hm-rpc.0 (9036) clear connecting interval 2022-06-29 16:14:37.279 - debug: hm-rpc.0 (9036) start ping interval 2022-06-29 16:14:37.279 - debug: hm-rpc.0 (9036) xml multicall : IOBroker-Server:hm-rpc.0:cb10e00673d97b9f3b28ccb982a1f291,LEQ1003243:0,STICKY_UNREACH,true 2022-06-29 16:14:37.280 - debug: hm-rpc.0 (9036) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:cb10e00673d97b9f3b28ccb982a1f291","LEQ1003243:0","STICKY_UNREACH",true] 2022-06-29 16:14:37.280 - debug: hm-rpc.0 (9036) hm-rpc.0.LEQ1003243.0.STICKY_UNREACH ==> UNIT: "" (min: undefined, max: undefined) From "true" => "true" 2022-06-29 16:14:37.280 - debug: hm-rpc.0 (9036) xml multicall : IOBroker-Server:hm-rpc.0:cb10e00673d97b9f3b28ccb982a1f291,OEQ0015243:0,STICKY_UNREACH,true 2022-06-29 16:14:37.280 - debug: hm-rpc.0 (9036) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:cb10e00673d97b9f3b28ccb982a1f291","OEQ0015243:0","STICKY_UNREACH",true] 2022-06-29 16:14:37.280 - debug: hm-rpc.0 (9036) hm-rpc.0.OEQ0015243.0.STICKY_UNREACH ==> UNIT: "" (min: undefined, max: undefined) From "true" => "true"Auf die Klingeltaster gedrückt (Tasterschnittstelle) "no matching device??"
hm-rpc.0 2022-06-29 16:20:02.817 debug xmlrpc <- event: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f.LEQ0796944.1.INSTALL_TEST:true discarded, no matching device hm-rpc.0 2022-06-29 16:20:02.817 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f","LEQ0796944:1","INSTALL_TEST",true] hm-rpc.0 2022-06-29 16:20:02.817 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f,LEQ0796944:1,INSTALL_TEST,true hm-rpc.0 2022-06-29 16:20:02.814 debug xmlrpc <- event: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f.LEQ0796944.1.PRESS:true discarded, no matching device hm-rpc.0 2022-06-29 16:20:02.814 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f","LEQ0796944:1","PRESS",true] hm-rpc.0 2022-06-29 16:20:02.814 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f,LEQ0796944:1,PRESS,true hm-rpc.0 2022-06-29 16:20:01.066 debug xmlrpc <- event: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f.LEQ0796944.3.INSTALL_TEST:true discarded, no matching device hm-rpc.0 2022-06-29 16:20:01.066 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f","LEQ0796944:3","INSTALL_TEST",true] hm-rpc.0 2022-06-29 16:20:01.066 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f,LEQ0796944:3,INSTALL_TEST,true hm-rpc.0 2022-06-29 16:20:01.064 debug xmlrpc <- event: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f.LEQ0796944.3.PRESS:true discarded, no matching device hm-rpc.0 2022-06-29 16:20:01.064 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f","LEQ0796944:3","PRESS",true] hm-rpc.0 2022-06-29 16:20:01.064 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f,LEQ0796944:3,PRESS,true hm-rpc.0 2022-06-29 16:19:59.315 debug xmlrpc <- event: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f.LEQ0796944.1.INSTALL_TEST:true discarded, no matching device hm-rpc.0 2022-06-29 16:19:59.315 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f","LEQ0796944:1","INSTALL_TEST",true] hm-rpc.0 2022-06-29 16:19:59.315 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f,LEQ0796944:1,INSTALL_TEST,true hm-rpc.0 2022-06-29 16:19:59.313 debug xmlrpc <- event: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f.LEQ0796944.1.PRESS:true discarded, no matching device hm-rpc.0 2022-06-29 16:19:59.313 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f","LEQ0796944:1","PRESS",true] hm-rpc.0 2022-06-29 16:19:59.313 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f,LEQ0796944:1,PRESS,true hm-rpc.0 2022-06-29 16:19:57.816 debug xmlrpc <- event: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f.LEQ0796944.3.INSTALL_TEST:true discarded, no matching device hm-rpc.0 2022-06-29 16:19:57.816 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f","LEQ0796944:3","INSTALL_TEST",true] hm-rpc.0 2022-06-29 16:19:57.816 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f,LEQ0796944:3,INSTALL_TEST,true hm-rpc.0 2022-06-29 16:19:57.815 debug xmlrpc <- event: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f.LEQ0796944.3.PRESS:true discarded, no matching device hm-rpc.0 2022-06-29 16:19:57.815 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f","LEQ0796944:3","PRESS",true] hm-rpc.0 2022-06-29 16:19:57.815 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:7a7b719583ee87966fd906b30e4f1f8f,LEQ0796944:3,PRESS,trueAuf Klingeltastergedrückt, nach manuellem Adapterneustart (Klingel funktioniert):
hm-rpc.0 2022-06-29 16:23:46.343 debug hm-rpc.0.LEQ0796944.3.PRESS ==> UNIT: "" (min: undefined, max: undefined) From "true" => "true" hm-rpc.0 2022-06-29 16:23:46.342 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:defd888ef20521f7492a1f78f4819353","LEQ0796944:3","PRESS",true] hm-rpc.0 2022-06-29 16:23:46.342 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:defd888ef20521f7492a1f78f4819353,LEQ0796944:3,PRESS,true hm-rpc.0 2022-06-29 16:23:42.317 debug hm-rpc.0.LEQ0796944.3.PRESS ==> UNIT: "" (min: undefined, max: undefined) From "true" => "true" hm-rpc.0 2022-06-29 16:23:42.317 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:defd888ef20521f7492a1f78f4819353","LEQ0796944:3","PRESS",true] hm-rpc.0 2022-06-29 16:23:42.317 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:defd888ef20521f7492a1f78f4819353,LEQ0796944:3,PRESS,true hm-rpc.0 2022-06-29 16:23:40.571 debug hm-rpc.0.LEQ0796944.1.PRESS ==> UNIT: "" (min: undefined, max: undefined) From "true" => "true" hm-rpc.0 2022-06-29 16:23:40.571 debug xmlrpc <- event ["IOBroker-Server:hm-rpc.0:defd888ef20521f7492a1f78f4819353","LEQ0796944:1","PRESS",true] hm-rpc.0 2022-06-29 16:23:40.571 debug xml multicall <event>: IOBroker-Server:hm-rpc.0:defd888ef20521f7492a1f78f4819353,LEQ0796944:1,PRESS,true@surfer09 sagte in HM-RPC Adapter keine Werte nach Serverneustart:
debug: hm-rpc.0 (9036) Schedule restart: 30 5 * * *
Ok ... du startest es auch nach einer Zeit Neu !?
Teste mal ,
Instanz ausschalten .... Server neu starten ... alles hochfahren lassen und dann erst später die Instanz einschalten , was ist dann !?Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..
-
@surfer09 sagte in HM-RPC Adapter keine Werte nach Serverneustart:
debug: hm-rpc.0 (9036) Schedule restart: 30 5 * * *
Ok ... du startest es auch nach einer Zeit Neu !?
Teste mal ,
Instanz ausschalten .... Server neu starten ... alles hochfahren lassen und dann erst später die Instanz einschalten , was ist dann !?@glasfaser Ja genau. Ich lasse den Adapter morgens einmal neu starten - einfach prophylaktisch.
Dein Tipp Adapter stoppen, Server neustarten, kurz abwarten, Adapter starten - funktioniert! Die Klingel funktioniert sofort.IO-Broker Master/Slave auf Windows 11 64bit, NPM 10.9.4, Node 22.21.1 js-controller 7.0.7
-
@glasfaser Ja genau. Ich lasse den Adapter morgens einmal neu starten - einfach prophylaktisch.
Dein Tipp Adapter stoppen, Server neustarten, kurz abwarten, Adapter starten - funktioniert! Die Klingel funktioniert sofort.Jetzt wäre die Große Frage , was blockt die Verbindung ohne eine Fehlermeldung im Log !?
Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..
-
Jetzt wäre die Große Frage , was blockt die Verbindung ohne eine Fehlermeldung im Log !?
@glasfaser Netzwerk noch nicht bereit??
kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@glasfaser Netzwerk noch nicht bereit??
Das kann nur @surfer09 beantworten , bzw. hast du andere Adapter die auf das Netzwerk zugreifen !?
Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..
-
Hast du noch mehr auf deinem Server ... PI-Hole oder so ......!?
Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..
-
@glasfaser Also auf dem Server läuft der ioBroker, Logitech Media Server, Deconz, Avast Virenscanner, Cobian Backup. Der Server ist eine virtuelle Maschine auf einem ESXi.
Diese Adapter habe ich installiert:
-
Hallo zusammen,
ich habe das Problem, wenn ich meinen IO-Broker Server komplett neu starte, dass der HM-RPC Adapter keine Werte von der CCU bekommt.
Erst wenn ich den Adapter dann noch einmal manuell neu starte (im LOG um 15:44:27), bekommt er wieder Daten.
Adapterversion: 1.15.12hm-rpc.0 2022-06-29 15:44:32.345 info Connected hm-rpc.0 2022-06-29 15:44:32.320 info xmlrpc -> 93 devices hm-rpc.0 2022-06-29 15:44:32.301 info xmlrpc <- listDevices ["IOBroker-Server:hm-rpc.0:025be6186ff90b9a5f1be3027ff93e0e"] hm-rpc.0 2022-06-29 15:44:32.287 info xmlrpc <- system.listMethods ["IOBroker-Server:hm-rpc.0:025be6186ff90b9a5f1be3027ff93e0e"] hm-rpc.0 2022-06-29 15:44:32.274 info xmlrpc client is trying to connect to 192.168.1.100:2001/ with ["http://192.168.1.25:2001","IOBroker-Server:hm-rpc.0:025be6186ff90b9a5f1be3027ff93e0e"] hm-rpc.0 2022-06-29 15:44:32.273 info xmlrpc server is trying to listen on 0.0.0.0:2001 hm-rpc.0 2022-06-29 15:44:32.183 info starting. Version 1.15.12 in I:/ioBroker/node_modules/iobroker.hm-rpc, node: v16.15.1, js-controller: 4.0.23 hm-rpc.0 2022-06-29 15:44:27.949 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason hm-rpc.0 2022-06-29 15:44:27.948 info terminating hm-rpc.0 2022-06-29 15:44:27.948 info Disconnected hm-rpc.0 2022-06-29 15:44:27.943 info xmlrpc -> 192.168.1.100:2001/ init ["http://192.168.1.25:2001",""] hm-rpc.0 2022-06-29 15:44:27.942 info Got terminate signal TERMINATE_YOURSELF hm-rpc.0 2022-06-29 15:35:35.578 info Connected hm-rpc.0 2022-06-29 15:35:35.536 info xmlrpc -> 93 devices hm-rpc.0 2022-06-29 15:35:35.515 info xmlrpc <- listDevices ["IOBroker-Server:hm-rpc.0:a34cc66205223607b79ae1f8af6e7f85"] hm-rpc.0 2022-06-29 15:35:35.512 info xmlrpc <- system.listMethods ["IOBroker-Server:hm-rpc.0:a34cc66205223607b79ae1f8af6e7f85"] hm-rpc.0 2022-06-29 15:35:35.500 info xmlrpc client is trying to connect to 192.168.1.100:2001/ with ["http://192.168.1.25:2001","IOBroker-Server:hm-rpc.0:a34cc66205223607b79ae1f8af6e7f85"] hm-rpc.0 2022-06-29 15:35:35.500 info xmlrpc server is trying to listen on 0.0.0.0:2001 hm-rpc.0 2022-06-29 15:35:35.183 info starting. Version 1.15.12 in I:/ioBroker/node_modules/iobroker.hm-rpc, node: v16.15.1, js-controller: 4.0.23 hm-rpc.0 2022-06-29 15:35:32.505 warn Terminated (ADAPTER_ALREADY_RUNNING): Without reason hm-rpc.0 2022-06-29 15:35:32.504 error hm-rpc.0 already running@surfer09 sagte in HM-RPC Adapter keine Werte nach Serverneustart:
wenn ich meinen IO-Broker Server komplett neu starte
@surfer09 sagte in HM-RPC Adapter keine Werte nach Serverneustart:
eine virtuelle Maschine auf einem ESXi.
Und warum startest du den kompletten Server neu , oder meinst du die VM wird neu gestartet !?
Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..
843
Online32.4k
Users81.5k
Topics1.3m
Posts