@homoran wüsste ich das hätte ich hier nicht gefragt.

@felidsche Sorry. Ich habe keine Weishaupt WP.

@homoran ein KNX visualisierungsserver mit IP Schnittstelle

@glasfaser schon die erste Korrektur hat es gebracht. Ich dachte der Shellyplug rebootet noch, da war er schon im Iobroker zu sehen. Das war handfeste Hilfe - und echt schnell. Ich Danke Dir sehr. Jetzt muss ich herausbekommen, was ich am Besten mit diesem Plug machen kann. Und wie ich die Daten, die er liefert ansehen und darstellen kann. Gibt es eine Lese-Empfehlung welchen Adapter im IObroker ich mir genauer ansehen sollte? :-) servus Robby

@stefan-falt Anscheinend nicht .... Danke für die Info.

@tmischek sagte in Homematic CCU3 Adapter: das ganze läuft auf einer synologi, das ist doch wieder nur die halbe Wahrheit. da läuft doch sicher Docker. bitte gib uns alle Informationen! callback adresse? alle ports durchgeführt? und was bei so einer komplexen Installation alles sonst noch zu beachten ist.

@bananajoe Hey. Nein, bei Pause bleibt sie an. Muss ich mal testen. Danke

@michael-wahlers Moin. ich würde hier gerne ansetzen... In Labs gibt es den Parameter "Priorisiertes Laden über Solarenergie". Wenn der gesetzt wird wird, Lädt er über AC nur, wenn der SOC unter 20% ist. damit wäre es möglich, die Ecoflow nach dem Entladen nicht weiter als 20% zu laden... Unbekannter Delta2 Set Befehl: {"params":{"pvChangeSet":1},"from":"iOS","lang":"de-de","id":"xxxxxxxx","moduleSn":"xxxxxxxxx","moduleType":1,"operateType":"pvChangePrio","version":"1.0"} Leider ist der Parameter in dem Script nicht unter den Writeables für die D2 hinterlegt. EDIT: Habs im Script hinzugefügt: { id: 0, name: 'pvChangePrio_D2', ValueName: 'pvChangeSet', Typ: 'D2', MT: 1,}, nun ist der Parameter Writeable. Ich werde es mal testen.

@fuxsism Und den Abschnitt "second bot" im README hast du beachtet? https://github.com/iobroker-community-adapters/ioBroker.mihome-vacuum#second-robot

@mariva sagte: Hier geht es um den Stromzähler Dann wird ein M-Bus Master benötigt, entweder von den Wasserwerken oder ein eigener.

@jamakr4 siehe hier: Solax Photovoltaik Portal in ioBroker https://forum.iobroker.net/topic/13152/solax-photovoltaik-portal-in-iobroker/10 evtl. nützt es dir was.

@pvnet Hier gibt es den passenden Thread für dein Problem. Und hier das Wiki dazu. Dort ist auch die Installation beschrieben. Edit: Marc war wieder schneller :blush:

@gornung Danke für Deine Rückmeldung. Nach reiflicher Überlegung und Recherche habe ich mich nun für Homematic IP entschieden. Bin damit bisher super zufrieden, was die Einrichtung usw. angeht. Die erste Heizsaison (sprich Feuerprobe) kommt allerdings erst...

@deralff Hallo, ich habe den vorhandenen VE Adapter gelöscht und über Github neu installiert (https://github.com/derAlff/ioBroker.ve). Das Problem besteht unverändert. Ich möchte nochmal erwähnen, dass das schon mal funktioniert hat, bevor ich meinen BananaPi neu aufgesetzt habe. Meine Konstellation: Multiplus 2 GX 70-50 mit EM24 Zähler und einer DIY Batterie 280Ah mit Seplos 200A BMS. ioBroker ein SolarLog Base (nirgens eingetragen) Schüko SGI10K WR (nur vom SolarLog üser S0 gezählt) SolPlanet ASW3000S-S (nirgens eingetragen) MfG Stefan host.bananapim5 2023-09-01 19:06:43.872 info Restart adapter system.adapter.ve.0 because enabled host.bananapim5 2023-09-01 19:06:43.871 error instance system.adapter.ve.0 terminated with code 6 (UNCAUGHT_EXCEPTION) ve.0 2023-09-01 19:06:43.293 warn Terminated (UNCAUGHT_EXCEPTION): Without reason ve.0 2023-09-01 19:06:43.290 info terminating ve.0 2023-09-01 19:06:43.288 info Unload adapter... ve.0 2023-09-01 19:06:43.282 error Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.281 error Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) ve.0 2023-09-01 19:06:43.280 error unhandled promise rejection: Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.278 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). ve.0 2023-09-01 19:06:43.236 error Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.235 error Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) ve.0 2023-09-01 19:06:43.234 error unhandled promise rejection: Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.233 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). ve.0 2023-09-01 19:06:43.231 error Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.230 error Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) ve.0 2023-09-01 19:06:43.229 error unhandled promise rejection: Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.228 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). ve.0 2023-09-01 19:06:43.226 error Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.225 error Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) ve.0 2023-09-01 19:06:43.224 error unhandled promise rejection: Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.223 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). ve.0 2023-09-01 19:06:43.221 error Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.220 error Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) ve.0 2023-09-01 19:06:43.219 error unhandled promise rejection: Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.218 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). ve.0 2023-09-01 19:06:43.216 error Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.215 error Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) ve.0 2023-09-01 19:06:43.214 error unhandled promise rejection: Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.213 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). ve.0 2023-09-01 19:06:43.211 error Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.210 error Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) ve.0 2023-09-01 19:06:43.209 error unhandled promise rejection: Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.208 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). ve.0 2023-09-01 19:06:43.207 error Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.206 error Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) ve.0 2023-09-01 19:06:43.204 error unhandled promise rejection: Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.203 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). ve.0 2023-09-01 19:06:43.201 error Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.200 error Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) ve.0 2023-09-01 19:06:43.199 error unhandled promise rejection: Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.198 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). ve.0 2023-09-01 19:06:43.196 error Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.195 error Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) ve.0 2023-09-01 19:06:43.193 error unhandled promise rejection: Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.192 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). ve.0 2023-09-01 19:06:43.190 error Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.188 error Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) ve.0 2023-09-01 19:06:43.186 error unhandled promise rejection: Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.184 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). ve.0 2023-09-01 19:06:43.181 error Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.180 error Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) ve.0 2023-09-01 19:06:43.177 error unhandled promise rejection: Modbus exception 10: Unknown error ve.0 2023-09-01 19:06:43.176 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). admin.0 2023-09-01 19:06:42.130 info Adapter rating updated smartmeter.0 2023-09-01 19:06:41.396 info Received 10 values, 3 updated ve.0 2023-09-01 19:06:38.051 info Number of PV-Inverters: 0 ve.0 2023-09-01 19:06:38.049 info config port: 502 ve.0 2023-09-01 19:06:38.048 info config IP: 192.168.178.44 ve.0 2023-09-01 19:06:37.985 info starting. Version 0.3.1 (non-npm: derAlff/ioBroker.ve#584088cddf3318ede48554ed97414f5ff79f460e) in /opt/iobroker/node_modules/iobroker.ve, node: v18.17.1, js-controller: 4.0.24 host.bananapim5 2023-09-01 19:06:35.119 info instance system.adapter.ve.0 started with pid 17719 host.bananapim5 2023-09-01 19:06:32.585 info instance system.adapter.ve.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.bananapim5 2023-09-01 19:06:32.057 info stopInstance system.adapter.ve.0 send kill signal ve.0 2023-09-01 19:06:32.009 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason ve.0 2023-09-01 19:06:32.007 info terminating ve.0 2023-09-01 19:06:32.006 info Unload adapter... ve.0 2023-09-01 19:06:32.002 info Got terminate signal TERMINATE_YOURSELF host.bananapim5 2023-09-01 19:06:31.992 info stopInstance system.adapter.ve.0 (force=false, process=true) smartmeter.0 2023-09-01 19:06:28.044 info Received 10 values, 3 updated smartmeter.0 2023-09-01 19:06:16.866 info Received 10 values, 1 updated smartmeter.0 2023-09-01 19:06:03.515 info Received 10 values, 1 updated ve.0 2023-09-01 19:06:01.882 info Number of PV-Inverters: 0 ve.0 2023-09-01 19:06:01.880 info config port: 502 ve.0 2023-09-01 19:06:01.878 info config IP: ve.0 2023-09-01 19:06:01.812 info starting. Version 0.3.1 (non-npm: derAlff/ioBroker.ve#584088cddf3318ede48554ed97414f5ff79f460e) in /opt/iobroker/node_modules/iobroker.ve, node: v18.17.1, js-controller: 4.0.24 host.bananapim5 2023-09-01 19:05:58.930 info instance system.adapter.ve.0 started with pid 17702 host.bananapim5 2023-09-01 19:05:56.941 info iobroker exit 0

@mickym Danke, mit "ungleich Null" hats geklappt statt "Nicht Null" :) [image: 1693465021119-bildschirmfoto-2023-08-31-um-08.56.05.png]

@womi Deshalb meinte ich ja auch, das das eher die plumpe (oder besser: fehleranfällige) Variante ist. Hätte ja auch einen Rattenschwanz an Dingen , an die man auch denken müsste: Wenn Wert größer als letzter Wert für Akku voll, dann Konditionierungsbetrieb aufgehoben, etc... Ich hab jetzt einen Datenpunkt, den ich von Hand auf true/false setze... So häufig wechselt der Status ja nicht....

@glasfaser du meinst ohne RTU? Da kommt gar nichts. Es kommen nun Werte an, ich habe nur unglaublich viele Timeouts. Ich könnte damit leben, aber würde ungern das log so vollspamen. Komplett deaktivieren kann man das log nicht?