[gelöst] smartmeter instaz gelb

? Offline

leider geht er immer noch nicht, habe mit den Einstellungen versucht, was ich gelesen hatte. Leider immer noch gelb. was liest du aus dem Log?

r.0 (1923) SERIALPORT OPEN
2021-03-08 13:30:21.691 - debug: smartmeter.0 (1923) SET MESSAGE TIMEOUT TIMER: 120000
2021-03-08 13:30:21.711 - debug: smartmeter.0 (1923) connected set to false
2021-03-08 13:31:00.002 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:31:42.530 - info: host.raspberrypi1 stopInstance system.adapter.smartmeter.0 (force=false, process=true)
2021-03-08 13:31:42.541 - info: host.raspberrypi1 stopInstance system.adapter.smartmeter.0 send kill signal
2021-03-08 13:31:42.542 - info: smartmeter.0 (1923) Got terminate signal TERMINATE_YOURSELF
2021-03-08 13:31:42.554 - debug: smartmeter.0 (1923) SERIALPORT CLOSE
2021-03-08 13:31:42.557 - info: smartmeter.0 (1923) terminating
2021-03-08 13:31:42.560 - debug: smartmeter.0 (1923) Plugin sentry destroyed
2021-03-08 13:31:42.562 - info: smartmeter.0 (1923) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2021-03-08 13:31:43.135 - info: host.raspberrypi1 instance system.adapter.smartmeter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-03-08 13:31:45.675 - info: host.raspberrypi1 instance system.adapter.smartmeter.0 started with pid 1939
2021-03-08 13:31:47.218 - debug: smartmeter.1 (1701) system.adapter.admin.0: logging false
2021-03-08 13:31:48.166 - debug: smartmeter.0 (1939) Redis Objects: Use Redis connection: 127.0.0.1:9001
2021-03-08 13:31:48.221 - debug: smartmeter.0 (1939) Objects client ready ... initialize now
2021-03-08 13:31:48.225 - debug: smartmeter.0 (1939) Objects create System PubSub Client
2021-03-08 13:31:48.227 - debug: smartmeter.0 (1939) Objects create User PubSub Client
2021-03-08 13:31:48.230 - debug: smartmeter.0 (1939) Objects client initialize lua scripts
2021-03-08 13:31:48.251 - debug: smartmeter.0 (1939) Objects connected to redis: 127.0.0.1:9001
2021-03-08 13:31:48.269 - debug: smartmeter.0 (1939) objectDB connected
2021-03-08 13:31:48.274 - debug: smartmeter.0 (1939) Redis States: Use Redis connection: 127.0.0.1:9000
2021-03-08 13:31:48.287 - debug: smartmeter.0 (1939) States create System PubSub Client
2021-03-08 13:31:48.290 - debug: smartmeter.0 (1939) States create User PubSub Client
2021-03-08 13:31:48.303 - debug: smartmeter.0 (1939) States connected to redis: 127.0.0.1:9000
2021-03-08 13:31:48.305 - debug: smartmeter.0 (1939) statesDB connected
2021-03-08 13:31:48.607 - debug: smartmeter.0 (1939) Plugin sentry Initialize Plugin (enabled=true)
2021-03-08 13:31:48.990 - info: smartmeter.0 (1939) starting. Version 3.2.0 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v12.21.0, js-controller: 3.2.16
2021-03-08 13:31:49.041 - debug: smartmeter.0 (1939) SmartmeterObis options: {"debug":2,"protocol":"D0Protocol","transport":"SerialResponseTransport","requestInterval":"3","anotherQueryDelay":"1000","transportSerialPort":"/dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0047-if00-port0","transportSerialBaudrate":null,"transportSerialMessageTimeout":null,"protocolD0WakeupCharacters":0,"obisFallbackMedium":0}
2021-03-08 13:31:49.047 - debug: smartmeter.0 (1939) CREATE SERIALPORT: 9600 8 1 none
2021-03-08 13:31:49.060 - debug: smartmeter.0 (1939) SERIALPORT OPEN
2021-03-08 13:31:49.093 - debug: smartmeter.0 (1939) SET MESSAGE TIMEOUT TIMER: 120000
2021-03-08 13:31:49.112 - debug: smartmeter.0 (1939) connected set to false
2021-03-08 13:32:00.003 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:32:01.435 - debug: smartmeter.0 (1939) Message received = {"command":"listUart","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":32,"ack":false,"time":1615206721431},"_id":45775062}
2021-03-08 13:32:01.728 - info: smartmeter.0 (1939) List of port: [{"path":"/dev/ttyAMA0"},{"path":"/dev/ttyS0"},{"manufacturer":"Silicon Labs","serialNumber":"0047","pnpId":"usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0047-if00-port0","vendorId":"10c4","productId":"ea60","path":"/dev/ttyUSB0"},{"manufacturer":"Silicon Labs","serialNumber":"0027","pnpId":"usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0027-if00-port0","vendorId":"10c4","productId":"ea60","path":"/dev/ttyUSB1"}]
2021-03-08 13:32:01.731 - debug: smartmeter.0 (1939) sendTo "listUart" to system.adapter.admin.0 from system.adapter.smartmeter.0
2021-03-08 13:32:12.739 - debug: smartmeter.1 (1701) system.adapter.admin.0: logging true
2021-03-08 13:32:12.742 - debug: smartmeter.0 (1939) system.adapter.admin.0: logging true
2021-03-08 13:33:00.003 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:33:49.095 - debug: smartmeter.0 (1939) MESSAGE TIMEOUT TRIGGERED
2021-03-08 13:33:49.097 - debug: smartmeter.0 (1939) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:33:49.101 - warn: smartmeter.0 (1939) No or too long answer from Serial Device after last request.
2021-03-08 13:33:49.102 - debug: smartmeter.0 (1939) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:33:49.103 - debug: smartmeter.0 (1939) Transport Reset!! Restart = true
2021-03-08 13:33:49.114 - debug: smartmeter.0 (1939) SERIALPORT CLOSE
2021-03-08 13:33:49.117 - debug: smartmeter.0 (1939) SCHEDULE NEXT RUN IN 3s
2021-03-08 13:33:52.120 - debug: smartmeter.0 (1939) CREATE SERIALPORT: 9600 8 1 none
2021-03-08 13:33:52.128 - debug: smartmeter.0 (1939) SERIALPORT OPEN
2021-03-08 13:33:52.133 - debug: smartmeter.0 (1939) SET MESSAGE TIMEOUT TIMER: 120000
2021-03-08 13:34:00.003 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:34:40.491 - debug: smartmeter.1 (1701) CREATE SERIALPORT: 300 7 1 even
2021-03-08 13:34:40.498 - debug: smartmeter.1 (1701) SERIALPORT OPEN
2021-03-08 13:34:40.502 - debug: smartmeter.1 (1701) SERIALPORT RESET BAUDRATE TO 300
2021-03-08 13:34:40.505 - debug: smartmeter.1 (1701) INITIAL MESSAGES TO SEND: 2
2021-03-08 13:34:40.507 - debug: smartmeter.1 (1701) CURRENT PROCESS STEP 0 IN GETNEXTMESSAGE
2021-03-08 13:34:40.509 - debug: smartmeter.1 (1701) TO SEND 2:
2021-03-08 13:34:40.510 - debug: smartmeter.1 (1701) CURRENT PROCESS STEP 1 IN GETNEXTMESSAGE
2021-03-08 13:34:40.511 - debug: smartmeter.1 (1701) TO SEND 1: /?!
2021-03-08 13:34:40.676 - debug: smartmeter.1 (1701) DONE SEND 1
2021-03-08 13:34:40.928 - debug: smartmeter.1 (1701) DONE SEND 0
2021-03-08 13:34:40.929 - debug: smartmeter.1 (1701) SET MESSAGE TIMEOUT TIMER2: 120000
2021-03-08 13:35:00.003 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:35:52.135 - debug: smartmeter.0 (1939) MESSAGE TIMEOUT TRIGGERED
2021-03-08 13:35:52.137 - debug: smartmeter.0 (1939) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:35:52.139 - warn: smartmeter.0 (1939) No or too long answer from Serial Device after last request.
2021-03-08 13:35:52.140 - debug: smartmeter.0 (1939) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:35:52.141 - debug: smartmeter.0 (1939) Transport Reset!! Restart = true
2021-03-08 13:35:52.151 - debug: smartmeter.0 (1939) SERIALPORT CLOSE
2021-03-08 13:35:52.154 - debug: smartmeter.0 (1939) SCHEDULE NEXT RUN IN 3s
2021-03-08 13:35:55.155 - debug: smartmeter.0 (1939) CREATE SERIALPORT: 9600 8 1 none
2021-03-08 13:35:55.164 - debug: smartmeter.0 (1939) SERIALPORT OPEN
2021-03-08 13:35:55.168 - debug: smartmeter.0 (1939) SET MESSAGE TIMEOUT TIMER: 120000
2021-03-08 13:36:00.003 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:36:37.322 - debug: smartmeter.0 (1939) Message received = {"command":"listUart","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":34,"ack":false,"time":1615206997319},"_id":45775064}
2021-03-08 13:36:37.603 - info: smartmeter.0 (1939) List of port: [{"path":"/dev/ttyAMA0"},{"path":"/dev/ttyS0"},{"manufacturer":"Silicon Labs","serialNumber":"0047","pnpId":"usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0047-if00-port0","vendorId":"10c4","productId":"ea60","path":"/dev/ttyUSB0"},{"manufacturer":"Silicon Labs","serialNumber":"0027","pnpId":"usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0027-if00-port0","vendorId":"10c4","productId":"ea60","path":"/dev/ttyUSB1"}]
2021-03-08 13:36:37.605 - debug: smartmeter.0 (1939) sendTo "listUart" to system.adapter.admin.0 from system.adapter.smartmeter.0
2021-03-08 13:36:40.931 - debug: smartmeter.1 (1701) MESSAGE TIMEOUT TRIGGERED
2021-03-08 13:36:40.933 - debug: smartmeter.1 (1701) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:36:40.934 - warn: smartmeter.1 (1701) No or too long answer from Serial Device after last request.
2021-03-08 13:36:40.935 - debug: smartmeter.1 (1701) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:36:40.936 - debug: smartmeter.1 (1701) Transport Reset!! Restart = true
2021-03-08 13:36:40.937 - debug: smartmeter.1 (1701) STOP
2021-03-08 13:36:40.938 - debug: smartmeter.1 (1701) CLEAR MESSAGE TIMEOUT TIMER
2021-03-08 13:36:40.946 - debug: smartmeter.1 (1701) SERIALPORT CLOSE
2021-03-08 13:36:40.947 - debug: smartmeter.1 (1701) SERIALPORT REMOVE LISTENERS
2021-03-08 13:36:40.949 - debug: smartmeter.1 (1701) CURRENT SIGNON MESSAGE COUNTER 1 OF 1
2021-03-08 13:36:40.951 - debug: smartmeter.1 (1701) DELETE rest of data (0) because new Message start with a new Request Message
2021-03-08 13:36:40.952 - debug: smartmeter.1 (1701) SCHEDULE NEXT RUN IN 300000s
2021-03-08 13:36:42.324 - debug: smartmeter.1 (1701) system.adapter.admin.0: logging false
2021-03-08 13:36:42.325 - debug: smartmeter.0 (1939) system.adapter.admin.0: logging false
2021-03-08 13:37:00.003 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:37:10.882 - info: host.raspberrypi1 stopInstance system.adapter.smartmeter.0 (force=false, process=true)
2021-03-08 13:37:10.891 - info: smartmeter.0 (1939) Got terminate signal TERMINATE_YOURSELF
2021-03-08 13:37:10.891 - info: host.raspberrypi1 stopInstance system.adapter.smartmeter.0 send kill signal
2021-03-08 13:37:10.898 - debug: smartmeter.0 (1939) SERIALPORT CLOSE
2021-03-08 13:37:10.900 - info: smartmeter.0 (1939) terminating
2021-03-08 13:37:10.902 - debug: smartmeter.0 (1939) Plugin sentry destroyed
2021-03-08 13:37:10.903 - info: smartmeter.0 (1939) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2021-03-08 13:37:11.035 - debug: smartmeter.1 (1701) system.adapter.admin.0: logging true
2021-03-08 13:37:11.038 - debug: smartmeter.0 (1939) system.adapter.admin.0: logging true
2021-03-08 13:37:11.535 - info: host.raspberrypi1 instance system.adapter.smartmeter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-03-08 13:37:13.971 - info: host.raspberrypi1 instance system.adapter.smartmeter.0 started with pid 1986
2021-03-08 13:37:16.478 - debug: smartmeter.0 (1986) Redis Objects: Use Redis connection: 127.0.0.1:9001
2021-03-08 13:37:16.534 - debug: smartmeter.0 (1986) Objects client ready ... initialize now
2021-03-08 13:37:16.538 - debug: smartmeter.0 (1986) Objects create System PubSub Client
2021-03-08 13:37:16.541 - debug: smartmeter.0 (1986) Objects create User PubSub Client
2021-03-08 13:37:16.543 - debug: smartmeter.0 (1986) Objects client initialize lua scripts
2021-03-08 13:37:16.564 - debug: smartmeter.0 (1986) Objects connected to redis: 127.0.0.1:9001
2021-03-08 13:37:16.582 - debug: smartmeter.0 (1986) objectDB connected
2021-03-08 13:37:16.587 - debug: smartmeter.0 (1986) Redis States: Use Redis connection: 127.0.0.1:9000
2021-03-08 13:37:16.600 - debug: smartmeter.0 (1986) States create System PubSub Client
2021-03-08 13:37:16.603 - debug: smartmeter.0 (1986) States create User PubSub Client
2021-03-08 13:37:16.616 - debug: smartmeter.0 (1986) States connected to redis: 127.0.0.1:9000
2021-03-08 13:37:16.618 - debug: smartmeter.0 (1986) statesDB connected
2021-03-08 13:37:16.860 - debug: smartmeter.0 (1986) Plugin sentry Initialize Plugin (enabled=true)
2021-03-08 13:37:17.269 - info: smartmeter.0 (1986) starting. Version 3.2.0 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v12.21.0, js-controller: 3.2.16
2021-03-08 13:37:17.320 - debug: smartmeter.0 (1986) SmartmeterObis options: {"debug":2,"protocol":"SmlProtocol","transport":"SerialResponseTransport","requestInterval":"3","anotherQueryDelay":"1000","transportSerialPort":"/dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0047-if00-port0","transportSerialBaudrate":null,"transportSerialMessageTimeout":null,"protocolSmlIgnoreInvalidCRC":false,"obisFallbackMedium":0}
2021-03-08 13:37:17.325 - debug: smartmeter.0 (1986) CREATE SERIALPORT: 9600 8 1 none
2021-03-08 13:37:17.339 - debug: smartmeter.0 (1986) SERIALPORT OPEN
2021-03-08 13:37:17.371 - debug: smartmeter.0 (1986) SET MESSAGE TIMEOUT TIMER: 120000
2021-03-08 13:37:17.404 - debug: smartmeter.0 (1986) connected set to false
2021-03-08 13:38:00.003 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:39:00.002 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:39:17.373 - debug: smartmeter.0 (1986) MESSAGE TIMEOUT TRIGGERED
2021-03-08 13:39:17.375 - debug: smartmeter.0 (1986) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:39:17.378 - warn: smartmeter.0 (1986) No or too long answer from Serial Device after last request.
2021-03-08 13:39:17.379 - debug: smartmeter.0 (1986) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:39:17.380 - debug: smartmeter.0 (1986) Transport Reset!! Restart = true
2021-03-08 13:39:17.388 - debug: smartmeter.0 (1986) SERIALPORT CLOSE
2021-03-08 13:39:17.391 - debug: smartmeter.0 (1986) SCHEDULE NEXT RUN IN 3s
2021-03-08 13:39:20.393 - debug: smartmeter.0 (1986) CREATE SERIALPORT: 9600 8 1 none
2021-03-08 13:39:20.402 - debug: smartmeter.0 (1986) SERIALPORT OPEN
2021-03-08 13:39:20.407 - debug: smartmeter.0 (1986) SET MESSAGE TIMEOUT TIMER: 120000
2021-03-08 13:40:00.002 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:41:00.001 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:41:00.003 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:41:20.410 - debug: smartmeter.0 (1986) MESSAGE TIMEOUT TRIGGERED
2021-03-08 13:41:20.411 - debug: smartmeter.0 (1986) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:41:20.412 - warn: smartmeter.0 (1986) No or too long answer from Serial Device after last request.
2021-03-08 13:41:20.413 - debug: smartmeter.0 (1986) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:41:20.413 - debug: smartmeter.0 (1986) Transport Reset!! Restart = true
2021-03-08 13:41:20.418 - debug: smartmeter.0 (1986) SERIALPORT CLOSE
2021-03-08 13:41:20.420 - debug: smartmeter.0 (1986) SCHEDULE NEXT RUN IN 3s
2021-03-08 13:41:23.422 - debug: smartmeter.0 (1986) CREATE SERIALPORT: 9600 8 1 none
2021-03-08 13:41:23.431 - debug: smartmeter.0 (1986) SERIALPORT OPEN
2021-03-08 13:41:23.435 - debug: smartmeter.0 (1986) SET MESSAGE TIMEOUT TIMER: 120000
2021-03-08 13:41:40.955 - debug: smartmeter.1 (1701) CREATE SERIALPORT: 300 7 1 even
2021-03-08 13:41:40.963 - debug: smartmeter.1 (1701) SERIALPORT OPEN
2021-03-08 13:41:40.967 - debug: smartmeter.1 (1701) SERIALPORT RESET BAUDRATE TO 300
2021-03-08 13:41:40.971 - debug: smartmeter.1 (1701) INITIAL MESSAGES TO SEND: 2
2021-03-08 13:41:40.975 - debug: smartmeter.1 (1701) CURRENT PROCESS STEP 0 IN GETNEXTMESSAGE
2021-03-08 13:41:40.976 - debug: smartmeter.1 (1701) TO SEND 2:
2021-03-08 13:41:40.977 - debug: smartmeter.1 (1701) CURRENT PROCESS STEP 1 IN GETNEXTMESSAGE
2021-03-08 13:41:40.978 - debug: smartmeter.1 (1701) TO SEND 1: /?!
2021-03-08 13:41:41.137 - debug: smartmeter.1 (1701) DONE SEND 1
2021-03-08 13:41:41.389 - debug: smartmeter.1 (1701) DONE SEND 0
2021-03-08 13:41:41.390 - debug: smartmeter.1 (1701) SET MESSAGE TIMEOUT TIMER2: 120000
2021-03-08 13:42:00.002 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:43:00.003 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:43:23.438 - debug: smartmeter.0 (1986) MESSAGE TIMEOUT TRIGGERED
2021-03-08 13:43:23.440 - debug: smartmeter.0 (1986) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:43:23.441 - warn: smartmeter.0 (1986) No or too long answer from Serial Device after last request.
2021-03-08 13:43:23.442 - debug: smartmeter.0 (1986) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:43:23.443 - debug: smartmeter.0 (1986) Transport Reset!! Restart = true
2021-03-08 13:43:23.448 - debug: smartmeter.0 (1986) SERIALPORT CLOSE
2021-03-08 13:43:23.450 - debug: smartmeter.0 (1986) SCHEDULE NEXT RUN IN 3s
2021-03-08 13:43:26.452 - debug: smartmeter.0 (1986) CREATE SERIALPORT: 9600 8 1 none
2021-03-08 13:43:26.461 - debug: smartmeter.0 (1986) SERIALPORT OPEN
2021-03-08 13:43:26.466 - debug: smartmeter.0 (1986) SET MESSAGE TIMEOUT TIMER: 120000
2021-03-08 13:43:41.391 - debug: smartmeter.1 (1701) MESSAGE TIMEOUT TRIGGERED
2021-03-08 13:43:41.393 - debug: smartmeter.1 (1701) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:43:41.394 - warn: smartmeter.1 (1701) No or too long answer from Serial Device after last request.
2021-03-08 13:43:41.396 - debug: smartmeter.1 (1701) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:43:41.397 - debug: smartmeter.1 (1701) Transport Reset!! Restart = true
2021-03-08 13:43:41.398 - debug: smartmeter.1 (1701) STOP
2021-03-08 13:43:41.399 - debug: smartmeter.1 (1701) CLEAR MESSAGE TIMEOUT TIMER
2021-03-08 13:43:41.405 - debug: smartmeter.1 (1701) SERIALPORT CLOSE
2021-03-08 13:43:41.407 - debug: smartmeter.1 (1701) SERIALPORT REMOVE LISTENERS
2021-03-08 13:43:41.409 - debug: smartmeter.1 (1701) CURRENT SIGNON MESSAGE COUNTER 1 OF 1
2021-03-08 13:43:41.411 - debug: smartmeter.1 (1701) DELETE rest of data (0) because new Message start with a new Request Message
2021-03-08 13:43:41.413 - debug: smartmeter.1 (1701) SCHEDULE NEXT RUN IN 300000s
2021-03-08 13:44:00.004 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:45:00.003 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:45:26.469 - debug: smartmeter.0 (1986) MESSAGE TIMEOUT TRIGGERED
2021-03-08 13:45:26.471 - debug: smartmeter.0 (1986) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:45:26.472 - warn: smartmeter.0 (1986) No or too long answer from Serial Device after last request.
2021-03-08 13:45:26.474 - debug: smartmeter.0 (1986) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:45:26.475 - debug: smartmeter.0 (1986) Transport Reset!! Restart = true
2021-03-08 13:45:26.487 - debug: smartmeter.0 (1986) SERIALPORT CLOSE
2021-03-08 13:45:26.489 - debug: smartmeter.0 (1986) SCHEDULE NEXT RUN IN 3s
2021-03-08 13:45:29.491 - debug: smartmeter.0 (1986) CREATE SERIALPORT: 9600 8 1 none
2021-03-08 13:45:29.498 - debug: smartmeter.0 (1986) SERIALPORT OPEN
2021-03-08 13:45:29.502 - debug: smartmeter.0 (1986) SET MESSAGE TIMEOUT TIMER: 120000
2021-03-08 13:46:00.003 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:47:00.002 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:47:29.505 - debug: smartmeter.0 (1986) MESSAGE TIMEOUT TRIGGERED
2021-03-08 13:47:29.507 - debug: smartmeter.0 (1986) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:47:29.508 - warn: smartmeter.0 (1986) No or too long answer from Serial Device after last request.
2021-03-08 13:47:29.509 - debug: smartmeter.0 (1986) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:47:29.510 - debug: smartmeter.0 (1986) Transport Reset!! Restart = true
2021-03-08 13:47:29.520 - debug: smartmeter.0 (1986) SERIALPORT CLOSE
2021-03-08 13:47:29.522 - debug: smartmeter.0 (1986) SCHEDULE NEXT RUN IN 3s
2021-03-08 13:47:32.523 - debug: smartmeter.0 (1986) CREATE SERIALPORT: 9600 8 1 none
2021-03-08 13:47:32.530 - debug: smartmeter.0 (1986) SERIALPORT OPEN
2021-03-08 13:47:32.533 - debug: smartmeter.0 (1986) SET MESSAGE TIMEOUT TIMER: 120000
2021-03-08 13:48:00.003 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:48:41.416 - debug: smartmeter.1 (1701) CREATE SERIALPORT: 300 7 1 even
2021-03-08 13:48:41.424 - debug: smartmeter.1 (1701) SERIALPORT OPEN
2021-03-08 13:48:41.428 - debug: smartmeter.1 (1701) SERIALPORT RESET BAUDRATE TO 300
2021-03-08 13:48:41.431 - debug: smartmeter.1 (1701) INITIAL MESSAGES TO SEND: 2
2021-03-08 13:48:41.436 - debug: smartmeter.1 (1701) CURRENT PROCESS STEP 0 IN GETNEXTMESSAGE
2021-03-08 13:48:41.438 - debug: smartmeter.1 (1701) TO SEND 2:
2021-03-08 13:48:41.439 - debug: smartmeter.1 (1701) CURRENT PROCESS STEP 1 IN GETNEXTMESSAGE
2021-03-08 13:48:41.441 - debug: smartmeter.1 (1701) TO SEND 1: /?!
2021-03-08 13:48:41.605 - debug: smartmeter.1 (1701) DONE SEND 1
2021-03-08 13:48:41.857 - debug: smartmeter.1 (1701) DONE SEND 0
2021-03-08 13:48:41.858 - debug: smartmeter.1 (1701) SET MESSAGE TIMEOUT TIMER2: 120000
2021-03-08 13:49:00.002 - warn: javascript.0 (1449) State "javascript.0.variables.dayTime" has no existing object, this might lead to an error in future versions
2021-03-08 13:49:32.536 - debug: smartmeter.0 (1986) MESSAGE TIMEOUT TRIGGERED
2021-03-08 13:49:32.538 - debug: smartmeter.0 (1986) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:49:32.539 - warn: smartmeter.0 (1986) No or too long answer from Serial Device after last request.
2021-03-08 13:49:32.540 - debug: smartmeter.0 (1986) Error: No or too long answer from Serial Device after last request.
2021-03-08 13:49:32.541 - debug: smartmeter.0 (1986) Transport Reset!! Restart = true
2021-03-08 13:49:32.546 - debug: smartmeter.0 (1986) SERIALPORT CLOSE
2021-03-08 13:49:32.547 - debug: smartmeter.0 (1986) SCHEDULE NEXT RUN IN 3s

wendy2702

@marcel-drzal Poste mal ein Screenshot der Einstellungen und drehe zum testen den Lesekopf mal um 180 Grad.

Hast du aktuell nur einen oder beide Lesekoepfe angeschlossen?

? Offline

@wendy2702 ich habe den Lesekopf zu testzwecken noch nicht am Zähler, da ich erst am aufbau bin. ich wollte ihn mit einer Taschenlampe antriggern?

? Offline

@wendy2702 beide und auch mal mit einem Versucht selbe resultat

wendy2702

@marcel-drzal sagte in smartmeter instaz gelb:

ich habe den Lesekopf zu testzwecken noch nicht am Zähler, da ich erst am aufbau bin. ich wollte ihn mit einer Taschenlampe antriggern?

Sorry aber ist jetzt ein Scherz, oder?

Was erwartest du vom Lesekopf und dem Adapter wenn du ihn mit einer Taschenlampe anleuchtest?

Kannst du mit 9600Baud und dem entsprechenden Protokoll die Taschenlampe bedienen?

Der Adapter wird erst GRÜN wenn er valide Daten empfängt.

Also bevor der Lesekopf nicht auf dem Zähler sitzt müssen wir hier nichts weiter prüfen und Zeit verschwenden.

? Offline

@wendy2702 Danke dir es Funktioniert nun nach einbau.

noch einer Frage
Ich habe 2 Raspi mit Multihost.
Kann nun im iobroker mit einer IP beide bedienen.

Die influxDB auf dem Master Loggt nur daten vom Master (Nr 2). (zBsp,; KNX welcher auf dem Master ist)
Die Stromdaten befinden sich aber auf dem Slave.
Muss 2 Influx Dadenbanke erstellen oder geht das auch anders? Brauche sie für Grafana, dort sehe ich auch nur die influx Daten von KNX und keine Stromdaten.

hoffe ihr könnt mir Helfen.

Homoran

@marcel-drzal sagte in smartmeter instaz gelb:

Die influxDB auf dem Master Loggt nur daten vom Master (Nr 2). (zBsp,; KNX welcher auf dem Master ist)
Die Stromdaten befinden sich aber auf dem Slave.

zeig mal die Objekte vom zweiten Zähler

wendy2702

@marcel-drzal sagte in smartmeter instaz gelb:

Muss 2 Influx Dadenbanke erstellen oder geht das auch anders? Brauche sie für Grafana, dort sehe ich auch nur die influx Daten von KNX und keine Stromdaten.

Die Daten vom Smartmeter sollten bei richtiger Master - Slave Konfiguration auch auf dem Master unter den Objekten sichtbar sein. Zumindest ist es bei mir so. Bedeutet du solltest unter den Objekten alle Datenpunkte sehen was wir gerne, wie @Homoran geschrieben hat, mit einem Screenshot sehen würden.

? Offline

@homoran
Rasperry1 Slave
Rasperry2 Master siehe oben ds Bild

? Offline

ich sehe Alle

und in Grafana kommen nur Daten von KNX an welcher unter dem Master auch läuft
vom Slave kommt nicht an über InfluxDB

wendy2702

@marcel-drzal Hast du denn das Schreiben in Influx für die Datenpunkte aktiviert ?

Homoran

@marcel-drzal sagte in smartmeter instaz gelb:

Rasperry2 Master siehe oben ds Bild

da sehe ich leider nicht die Datenpunkte

? Offline

@homoran

Homoran

@marcel-drzal so!

und jetzt noch die Einstellungen im Schraubenschlüssel

? Offline

@homoran

ich glaub das Problem liegt im Multihost rasperry1 Slave und rasperry2 Master.
Grafana läuft ja unter 192.168.178.44/24
wie stell ich das im Slave (Rasperry1) ein? was denk du

Werte werden gelockt im Schraubenschlüssel

nur nicht auf Grafana weiter gegeben

Homoran

@marcel-drzal sagte in smartmeter instaz gelb:

ich glaub das Problem liegt im Multihost rasperry1 Slave und rasperry2 Master.

nein!

denn...

@marcel-drzal sagte in smartmeter instaz gelb:

Werte werden gelockt

@marcel-drzal sagte in smartmeter instaz gelb:

nur nicht auf Grafana weiter gegeben

dann ist das ein Grafana Problem

? Offline

@homoran Probleme mit Grafana
ich habe einene Multihost Rasperry1 Slave und Master Rasperry2

es werden nur die daden aus dem Master in Grafana angezeigt

Daten kommen über IOBroker InfluxDB

Einstellungen im Iobroker

Log vom SmartMeater

Homoran

@marcel-drzal sagte in smartmeter instaz gelb:

ich habe einene Multihost Rasperry1 Slave und Master Rasperry2

was willst du mir damit sagen/zeigen?

Die Daten kommen ja korrekt im Master an und werden auch in der influx gespeichert.
Also keine ioBroker-Baustelle

wendy2702

Starte mal Grafana neu

? Offline

@wendy2702 habe ich gemacht geht immer noch nicht
habe nun auch in iobroker eine Fehlermeldung

$ ./iobroker install easee
NPM version: 6.14.11
npm install iobroker.easee@0.1.2 --loglevel error --prefix "/opt/iobroker" (System call)
npm ERR! code ETARGET
npm ERR! notarget No matching version found for iobroker.easee@0.1.2.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2021-03-27T14_17_28_601Z-debug.log
ERROR: host.raspberrypi2 Cannot install iobroker.easee@0.1.2: 1
ERROR: process exited with code 25```
2021-03-27 15:14:07.981 - warn: admin.0 (1385) Object knx.0.Beleuchtung.Außen.----------A2_Gunnar_Seite---------- is invalid: obj.common.read has an invalid type! Expected "boolean", received "string"
2021-03-27 15:14:07.982 - warn: admin.0 (1385) This object will not be created in future versions. Please report this to the developer.
2021-03-27 15:14:08.067 - warn: admin.0 (1385) Object knx.0.Beleuchtung.Außen.----------A1_Haustür---------- is invalid: obj.common.read has an invalid type! Expected "boolean", received "string"
2021-03-27 15:14:08.068 - warn: admin.0 (1385) This object will not be created in future versions. Please report this to the developer.
2021-03-27 15:14:18.979 - warn: admin.0 (1385) Object info.0.sysinfo.disks.blockDevices.dev2.group is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json
2021-03-27 15:14:18.980 - warn: admin.0 (1385) This object will not be created in future versions. Please report this to the developer.
2021-03-27 15:14:19.733 - warn: admin.0 (1385) Object info.0.sysinfo.disks.blockDevices.dev1.group is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json
2021-03-27 15:14:19.734 - warn: admin.0 (1385) This object will not be created in future versions. Please report this to the developer.
2021-03-27 15:14:20.395 - warn: admin.0 (1385) Object info.0.sysinfo.disks.blockDevices.dev0.group is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json
2021-03-27 15:14:20.397 - warn: admin.0 (1385) This object will not be created in future versions. Please report this to the developer.
2021-03-27 15:15:00.093 - info: host.raspberrypi2 instance system.adapter.dwd.0 started with pid 2945
2021-03-27 15:15:03.009 - info: dwd.0 (2945) starting. Version 2.7.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v12.21.0, js-controller: 3.2.16
2021-03-27 15:15:12.536 - error: dwd.0 (2945) Empty or invalid JSON: Cannot parse JSON file: SyntaxError: Unexpected end of JSON input
2021-03-27 15:15:12.539 - info: dwd.0 (2945) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2021-03-27 15:15:13.117 - info: host.raspberrypi2 instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-03-27 15:17:10.160 - info: host.raspberrypi2 Updating repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
2021-03-27 15:17:15.166 - info: host.raspberrypi2 iobroker install easee
2021-03-27 15:17:18.947 - info: host.raspberrypi2 iobroker NPM version: 6.14.11
2021-03-27 15:17:18.951 - info: host.raspberrypi2 iobroker npm install iobroker.easee@0.1.2 --loglevel error --prefix "/opt/iobroker" (System call)
2021-03-27 15:17:28.551 - info: host.raspberrypi2 iobroker npm ERR! code ETARGET
2021-03-27 15:17:28.588 - info: host.raspberrypi2 iobroker npm ERR! notarget No matching version found for iobroker.easee@0.1.2.
2021-03-27 15:17:28.590 - info: host.raspberrypi2 iobroker npm ERR! notarget In most cases you or one of your dependencies are requesting
2021-03-27 15:17:28.595 - info: host.raspberrypi2 iobroker npm ERR! notarget a package version that doesn't exist.
2021-03-27 15:17:28.619 - info: host.raspberrypi2 iobroker
2021-03-27 15:17:28.623 - info: host.raspberrypi2 iobroker npm ERR! A complete log of this run can be found in:
2021-03-27 15:17:28.626 - info: host.raspberrypi2 iobroker npm ERR! /home/iobroker/.npm/_logs/2021-03-27T14_17_28_601Z-debug.log
2021-03-27 15:17:28.651 - error: host.raspberrypi2 iobroker host.raspberrypi2 Cannot install iobroker.easee@0.1.2: 1
2021-03-27 15:17:29.702 - info: host.raspberrypi2 iobroker exit 25
2021-03-27 15:20:00.082 - info: host.raspberrypi2 instance system.adapter.dwd.0 started with pid 3014
2021-03-27 15:20:02.952 - info: dwd.0 (3014) starting. Version 2.7.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v12.21.0, js-controller: 3.2.16
2021-03-27 15:20:15.752 - info: dwd.0 (3014) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2021-03-27 15:20:16.319 - info: host.raspberrypi2 instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-03-27 15:21:10.390 - info: host.raspberrypi2 iobroker install easee
2021-03-27 15:21:14.195 - info: host.raspberrypi2 iobroker NPM version: 6.14.11
2021-03-27 15:21:14.198 - info: host.raspberrypi2 iobroker npm install iobroker.easee@0.1.2 --loglevel error --prefix "/opt/iobroker" (System call)
2021-03-27 15:21:22.331 - info: host.raspberrypi2 iobroker npm ERR! code ETARGET
2021-03-27 15:21:22.372 - info: host.raspberrypi2 iobroker npm ERR! notarget No matching version found for iobroker.easee@0.1.2.npm ERR! notarget In most cases you or one of your dependencies are requestingnpm ERR! notarget a package version that doesn't exist.
2021-03-27 15:21:22.397 - info: host.raspberrypi2 iobroker npm ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2021-03-27T14_21_22_381Z-debug.log
2021-03-27 15:21:22.424 - error: host.raspberrypi2 iobroker host.raspberrypi2 Cannot install iobroker.easee@0.1.2: 1
2021-03-27 15:21:23.478 - info: host.raspberrypi2 iobroker exit 25
2021-03-27 15:25:00.096 - info: host.raspberrypi2 instance system.adapter.dwd.0 started with pid 3061

MOD EDIT:CODE TAGS KORRIGIERT

Community Forum

NEWS

[gelöst] smartmeter instaz gelb

Support us

411

32.9k

83.0k

1.3m