@chillkroete1206 ich habe es über mqtt gelöst mit der Hilfe von: https://the78mole.de/taking-your-m-bus-online-with-mqtt/
Ich musste im Skript die
\
hier entfernen:
id : .MBusData.SlaveInformation.Id, \
manufacturer: .MBusData.SlaveInformation.Manufacturer, \
medium : .MBusData.SlaveInformation.Medium, \
@tombox der Type ist VWv2 neue Baujahr >=2020, der Fehler ist das erste mal aufgetreten.
Guten Abend,
habe gerade folgende Fehlermeldung bekommen:
vw-connect.0
2022-11-25 20:03:43.139 error Error in OnStateChange: undefined
vw-connect.0
2022-11-25 20:03:43.138 error {"error":{"errorCode":"gw.error.authentication","description":"Malformed request"}}
vw-connect.0
2022-11-25 20:03:43.138 error 401
der Fehler kommt, wenn ich den Datenpunkt:
vw-connect.0.XXXXXXXX.remote.standheizung auf true setze.
Nachdem ich den Adapter neugestartet habe, hat es wieder funktioniert.
Jemand eine Idee woran das liegt?
Vielen Dank.
Hallo zusammen,
ich suche gerade nach einer Lösung um die Standheizung von unserem Passat dynamisch einzuschalten. Hintergrund ist, dass meine Lebensgefährtin Nachtschicht arbeitet immer zu der gleiche Arbeitszeit allerdings an ganz unterschiedlichen Tagen im Monat.
Mein erster Ansatz war über die Abfahrtszeiten die Standheizung zu aktivieren, da dort der Heizbeginn Automatisch gesetzt wird. Leider werden die Werte in den Datenpunkten nicht übernommen bzw. nach kurzer Zeit mit dem alten Wert überschrieben. Ich vermute mir fehlt noch der Befehl für die Synchronisierung, wie es in der We Connect App der fall ist. Dort wird auch der Tag und die Uhrzeit der Abfahrt eingestellt und das ganze über die Taste "Synchronisierung" rechts oben bestätigt - gibt es diesen Datenpunkt?
Ich habe mir jetzt erstmal so geholfen, dass ich die Standheizung direkt zum Zeitpunkt einschalte, die Variable ob Nachtdienst ist oder nicht wird aus einem Kalender generiert (aktuell noch vertauscht (false=es ist Nachtdienst, true=es ist kein Nachtdienst).
Die Hilfsvariable "Standheizung_früh" wird benötigt um in der Früh nach der letzten Nacht die Standheizung zu aktivieren, da zu diesem Zeitpunkt laut Kalender kein Nachtdienst mehr ist.
Vielleicht hat jemand eine bessere Idee oder eine Lösung für um die Abfahrtszeit zu beschreiben.
Vielen Dank.
Hallo zusammen,
ich wollte node-red-contrib-alexa-remote2-applestrudel aktualisieren, leider geht dieser immer auf Fehler. Ich habe jetzt schon alles von der Palette deaktiviert, den Flow gelöscht und die Konfiguration und sogar die UI Datei. Dennoch lässt sich die Palette nicht aktualisieren oder löschen.
Protokoll - Aktualiseren:
2022-10-21T07:58:08.894Z Entfernen : node-red-contrib-alexa-remote2-applestrudel
2022-10-21T07:58:09.084Z npm remove --no-audit --no-update-notifier --no-fund --save node-red-contrib-alexa-remote2-applestrudel
2022-10-21T07:58:18.136Z [err] npm
2022-10-21T07:58:18.137Z [err] ERR! code ERESOLVE
2022-10-21T07:58:18.145Z [err] npm
2022-10-21T07:58:18.146Z [err] ERR! ERESOLVE could not resolve
2022-10-21T07:58:18.146Z [err] npm
2022-10-21T07:58:18.146Z [err] ERR!
2022-10-21T07:58:18.147Z [err]
2022-10-21T07:58:18.147Z [err] npm ERR!
2022-10-21T07:58:18.147Z [err] While resolving: @prescient-devices/node-red-contrib-dashboard-input-persistence@1.1.2
2022-10-21T07:58:18.148Z [err] npm ERR! Found: node-red-dashboard@3.1.2
2022-10-21T07:58:18.148Z [err] npm ERR! node_modules/node-red-dashboard
2022-10-21T07:58:18.148Z [err] npm ERR! peer node-red-dashboard@">=2.23.2" from node-red-contrib-ui-clock@1.0.2
2022-10-21T07:58:18.148Z [err] npm ERR!
2022-10-21T07:58:18.148Z [err] node_modules/node-red-contrib-ui-clock
2022-10-21T07:58:18.148Z [err] npm ERR! node-red-contrib-ui-clock@"~1.0.2" from the root project
2022-10-21T07:58:18.148Z [err] npm ERR! peer node-red-dashboard@">=2.23.2" from node-red-contrib-ui-digital-display@1.0.3
2022-10-21T07:58:18.148Z [err] npm ERR!
2022-10-21T07:58:18.148Z [err] node_modules/node-red-contrib-ui-digital-display
2022-10-21T07:58:18.148Z [err] npm ERR! node-red-contrib-ui-digital-display@"~1.0.3" from the root project
2022-10-21T07:58:18.148Z [err] npm ERR! 5 more (node-red-contrib-ui-led, node-red-node-ui-iframe, ...)
2022-10-21T07:58:18.148Z [err] npm
2022-10-21T07:58:18.149Z [err] ERR!
2022-10-21T07:58:18.149Z [err] npm ERR! Could not resolve dependency:
2022-10-21T07:58:18.149Z [err] npm
2022-10-21T07:58:18.149Z [err] ERR! peer node-red-dashboard@"^2.28.1" from @prescient-devices/node-red-contrib-dashboard-input-persistence@1.1.2
2022-10-21T07:58:18.149Z [err] npm ERR! node_modules/@prescient-devices/node-red-contrib-dashboard-input-persistence
2022-10-21T07:58:18.149Z [err] npm ERR!
2022-10-21T07:58:18.149Z [err] @prescient-devices/node-red-contrib-dashboard-input-persistence@"~1.1.2" from the root project
2022-10-21T07:58:18.149Z [err] npm ERR!
2022-10-21T07:58:18.149Z [err] npm ERR!
2022-10-21T07:58:18.149Z [err] Conflicting peer dependency: node-red-dashboard@2.30.0
2022-10-21T07:58:18.149Z [err] npm ERR! node_modules/node-red-dashboard
2022-10-21T07:58:18.149Z [err] npm ERR!
2022-10-21T07:58:18.149Z [err] peer node-red-dashboard@"^2.28.1" from @prescient-devices/node-red-contrib-dashboard-input-persistence@1.1.2
2022-10-21T07:58:18.149Z [err] npm ERR! node_modules/@prescient-devices/node-red-contrib-dashboard-input-persistence
2022-10-21T07:58:18.149Z [err] npm ERR!
2022-10-21T07:58:18.149Z [err] @prescient-devices/node-red-contrib-dashboard-input-persistence@"~1.1.2" from the root project
2022-10-21T07:58:18.149Z [err] npm ERR!
2022-10-21T07:58:18.149Z [err] npm ERR!
2022-10-21T07:58:18.150Z [err] Fix the upstream dependency conflict, or retry
2022-10-21T07:58:18.150Z [err] npm ERR! this command with --force, or --legacy-peer-deps
2022-10-21T07:58:18.150Z [err] npm
2022-10-21T07:58:18.150Z [err] ERR! to accept an incorrect (and potentially broken) dependency resolution.
2022-10-21T07:58:18.150Z [err] npm ERR!
2022-10-21T07:58:18.150Z [err] npm
2022-10-21T07:58:18.150Z [err] ERR! See /home/iobroker/.npm/eresolve-report.txt for a full report.
2022-10-21T07:58:18.156Z [err]
2022-10-21T07:58:18.156Z [err] npm
2022-10-21T07:58:18.157Z [err] ERR! A complete log of this run can be found in:
2022-10-21T07:58:18.157Z [err] npm ERR! /home/iobroker/.npm/_logs/2022-10-21T07_58_10_191Z-debug-0.log
2022-10-21T07:58:18.171Z rc=1
-----------------------------------------------------------
2022-10-21T08:04:49.271Z Installieren : node-red-contrib-alexa-remote2-applestrudel 5.0.21
2022-10-21T08:04:49.929Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-alexa-remote2-applestrudel@5.0.21
2022-10-21T08:04:51.140Z [err] npm
2022-10-21T08:04:51.141Z [err]
2022-10-21T08:04:51.141Z [err] WARN config production Use `--omit=dev` instead.
2022-10-21T08:04:59.306Z [err] npm
2022-10-21T08:04:59.306Z [err] ERR!
2022-10-21T08:04:59.306Z [err]
2022-10-21T08:04:59.307Z [err] code ERESOLVE
2022-10-21T08:04:59.320Z [err] npm
2022-10-21T08:04:59.321Z [err] ERR!
2022-10-21T08:04:59.321Z [err] ERESOLVE could not resolve
2022-10-21T08:04:59.321Z [err] npm
2022-10-21T08:04:59.322Z [err] ERR!
2022-10-21T08:04:59.322Z [err]
2022-10-21T08:04:59.323Z [err] npm
2022-10-21T08:04:59.323Z [err] ERR! While resolving: @prescient-devices/node-red-contrib-dashboard-input-persistence@1.1.2
2022-10-21T08:04:59.323Z [err] npm ERR! Found: node-red-dashboard@3.1.2
2022-10-21T08:04:59.323Z [err] npm ERR! node_modules/node-red-dashboard
2022-10-21T08:04:59.323Z [err] npm
2022-10-21T08:04:59.323Z [err] ERR! peer node-red-dashboard@">=2.23.2" from node-red-contrib-ui-clock@1.0.2
2022-10-21T08:04:59.323Z [err] npm ERR! node_modules/node-red-contrib-ui-clock
2022-10-21T08:04:59.324Z [err] npm ERR!
2022-10-21T08:04:59.324Z [err] node-red-contrib-ui-clock@"~1.0.2" from the root project
2022-10-21T08:04:59.324Z [err] npm
2022-10-21T08:04:59.324Z [err] ERR! peer node-red-dashboard@">=2.23.2" from node-red-contrib-ui-digital-display@1.0.3
2022-10-21T08:04:59.324Z [err] npm ERR! node_modules/node-red-contrib-ui-digital-display
2022-10-21T08:04:59.324Z [err] npm
2022-10-21T08:04:59.325Z [err] ERR! node-red-contrib-ui-digital-display@"~1.0.3" from the root project
2022-10-21T08:04:59.325Z [err] npm ERR! 5 more (node-red-contrib-ui-led, node-red-node-ui-iframe, ...)
2022-10-21T08:04:59.325Z [err] npm
2022-10-21T08:04:59.325Z [err] ERR!
2022-10-21T08:04:59.325Z [err] npm ERR! Could not resolve dependency:
2022-10-21T08:04:59.325Z [err] npm
2022-10-21T08:04:59.325Z [err] ERR! peer node-red-dashboard@"^2.28.1" from @prescient-devices/node-red-contrib-dashboard-input-persistence@1.1.2
2022-10-21T08:04:59.325Z [err] npm ERR! node_modules/@prescient-devices/node-red-contrib-dashboard-input-persistence
2022-10-21T08:04:59.325Z [err] npm
2022-10-21T08:04:59.325Z [err] ERR! @prescient-devices/node-red-contrib-dashboard-input-persistence@"~1.1.2" from the root project
2022-10-21T08:04:59.325Z [err] npm ERR!
2022-10-21T08:04:59.325Z [err] npm
2022-10-21T08:04:59.332Z [err] ERR! Conflicting peer dependency: node-red-dashboard@2.30.0
2022-10-21T08:04:59.332Z [err] npm ERR! node_modules/node-red-dashboard
2022-10-21T08:04:59.332Z [err] npm ERR! peer node-red-dashboard@"^2.28.1" from @prescient-devices/node-red-contrib-dashboard-input-persistence@1.1.2
2022-10-21T08:04:59.332Z [err] npm ERR! node_modules/@prescient-devices/node-red-contrib-dashboard-input-persistence
2022-10-21T08:04:59.332Z [err] npm ERR! @prescient-devices/node-red-contrib-dashboard-input-persistence@"~1.1.2" from the root project
2022-10-21T08:04:59.332Z [err] npm ERR!
2022-10-21T08:04:59.332Z [err] npm ERR! Fix the upstream dependency conflict, or retry
2022-10-21T08:04:59.332Z [err] npm ERR! this command with --force, or --legacy-peer-deps
2022-10-21T08:04:59.332Z [err] npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
2022-10-21T08:04:59.332Z [err] npm ERR!
2022-10-21T08:04:59.332Z [err] npm ERR! See /home/iobroker/.npm/eresolve-report.txt for a full report.
2022-10-21T08:04:59.335Z [err]
2022-10-21T08:04:59.336Z [err] npm
2022-10-21T08:04:59.336Z [err] ERR! A complete log of this run can be found in:
2022-10-21T08:04:59.336Z [err] npm ERR! /home/iobroker/.npm/_logs/2022-10-21T08_04_51_068Z-debug-0.log
2022-10-21T08:04:59.358Z rc=1
Protokoll Entfernen:
-----------------------------------------------------------
2022-10-21T07:58:08.894Z Entfernen : node-red-contrib-alexa-remote2-applestrudel
2022-10-21T07:58:09.084Z npm remove --no-audit --no-update-notifier --no-fund --save node-red-contrib-alexa-remote2-applestrudel
2022-10-21T07:58:18.136Z [err] npm
2022-10-21T07:58:18.137Z [err] ERR! code ERESOLVE
2022-10-21T07:58:18.145Z [err] npm
2022-10-21T07:58:18.146Z [err] ERR! ERESOLVE could not resolve
2022-10-21T07:58:18.146Z [err] npm
2022-10-21T07:58:18.146Z [err] ERR!
2022-10-21T07:58:18.147Z [err]
2022-10-21T07:58:18.147Z [err] npm ERR!
2022-10-21T07:58:18.147Z [err] While resolving: @prescient-devices/node-red-contrib-dashboard-input-persistence@1.1.2
2022-10-21T07:58:18.148Z [err] npm ERR! Found: node-red-dashboard@3.1.2
2022-10-21T07:58:18.148Z [err] npm ERR! node_modules/node-red-dashboard
2022-10-21T07:58:18.148Z [err] npm ERR! peer node-red-dashboard@">=2.23.2" from node-red-contrib-ui-clock@1.0.2
2022-10-21T07:58:18.148Z [err] npm ERR!
2022-10-21T07:58:18.148Z [err] node_modules/node-red-contrib-ui-clock
2022-10-21T07:58:18.148Z [err] npm ERR! node-red-contrib-ui-clock@"~1.0.2" from the root project
2022-10-21T07:58:18.148Z [err] npm ERR! peer node-red-dashboard@">=2.23.2" from node-red-contrib-ui-digital-display@1.0.3
2022-10-21T07:58:18.148Z [err] npm ERR!
2022-10-21T07:58:18.148Z [err] node_modules/node-red-contrib-ui-digital-display
2022-10-21T07:58:18.148Z [err] npm ERR! node-red-contrib-ui-digital-display@"~1.0.3" from the root project
2022-10-21T07:58:18.148Z [err] npm ERR! 5 more (node-red-contrib-ui-led, node-red-node-ui-iframe, ...)
2022-10-21T07:58:18.148Z [err] npm
2022-10-21T07:58:18.149Z [err] ERR!
2022-10-21T07:58:18.149Z [err] npm ERR! Could not resolve dependency:
2022-10-21T07:58:18.149Z [err] npm
2022-10-21T07:58:18.149Z [err] ERR! peer node-red-dashboard@"^2.28.1" from @prescient-devices/node-red-contrib-dashboard-input-persistence@1.1.2
2022-10-21T07:58:18.149Z [err] npm ERR! node_modules/@prescient-devices/node-red-contrib-dashboard-input-persistence
2022-10-21T07:58:18.149Z [err] npm ERR!
2022-10-21T07:58:18.149Z [err] @prescient-devices/node-red-contrib-dashboard-input-persistence@"~1.1.2" from the root project
2022-10-21T07:58:18.149Z [err] npm ERR!
2022-10-21T07:58:18.149Z [err] npm ERR!
2022-10-21T07:58:18.149Z [err] Conflicting peer dependency: node-red-dashboard@2.30.0
2022-10-21T07:58:18.149Z [err] npm ERR! node_modules/node-red-dashboard
2022-10-21T07:58:18.149Z [err] npm ERR!
2022-10-21T07:58:18.149Z [err] peer node-red-dashboard@"^2.28.1" from @prescient-devices/node-red-contrib-dashboard-input-persistence@1.1.2
2022-10-21T07:58:18.149Z [err] npm ERR! node_modules/@prescient-devices/node-red-contrib-dashboard-input-persistence
2022-10-21T07:58:18.149Z [err] npm ERR!
2022-10-21T07:58:18.149Z [err] @prescient-devices/node-red-contrib-dashboard-input-persistence@"~1.1.2" from the root project
2022-10-21T07:58:18.149Z [err] npm ERR!
2022-10-21T07:58:18.149Z [err] npm ERR!
2022-10-21T07:58:18.150Z [err] Fix the upstream dependency conflict, or retry
2022-10-21T07:58:18.150Z [err] npm ERR! this command with --force, or --legacy-peer-deps
2022-10-21T07:58:18.150Z [err] npm
2022-10-21T07:58:18.150Z [err] ERR! to accept an incorrect (and potentially broken) dependency resolution.
2022-10-21T07:58:18.150Z [err] npm ERR!
2022-10-21T07:58:18.150Z [err] npm
2022-10-21T07:58:18.150Z [err] ERR! See /home/iobroker/.npm/eresolve-report.txt for a full report.
2022-10-21T07:58:18.156Z [err]
2022-10-21T07:58:18.156Z [err] npm
2022-10-21T07:58:18.157Z [err] ERR! A complete log of this run can be found in:
2022-10-21T07:58:18.157Z [err] npm ERR! /home/iobroker/.npm/_logs/2022-10-21T07_58_10_191Z-debug-0.log
2022-10-21T07:58:18.171Z rc=1
-----------------------------------------------------------
2022-10-21T08:04:49.271Z Installieren : node-red-contrib-alexa-remote2-applestrudel 5.0.21
2022-10-21T08:04:49.929Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-alexa-remote2-applestrudel@5.0.21
2022-10-21T08:04:51.140Z [err] npm
2022-10-21T08:04:51.141Z [err]
2022-10-21T08:04:51.141Z [err] WARN config production Use `--omit=dev` instead.
2022-10-21T08:04:59.306Z [err] npm
2022-10-21T08:04:59.306Z [err] ERR!
2022-10-21T08:04:59.306Z [err]
2022-10-21T08:04:59.307Z [err] code ERESOLVE
2022-10-21T08:04:59.320Z [err] npm
2022-10-21T08:04:59.321Z [err] ERR!
2022-10-21T08:04:59.321Z [err] ERESOLVE could not resolve
2022-10-21T08:04:59.321Z [err] npm
2022-10-21T08:04:59.322Z [err] ERR!
2022-10-21T08:04:59.322Z [err]
2022-10-21T08:04:59.323Z [err] npm
2022-10-21T08:04:59.323Z [err] ERR! While resolving: @prescient-devices/node-red-contrib-dashboard-input-persistence@1.1.2
2022-10-21T08:04:59.323Z [err] npm ERR! Found: node-red-dashboard@3.1.2
2022-10-21T08:04:59.323Z [err] npm ERR! node_modules/node-red-dashboard
2022-10-21T08:04:59.323Z [err] npm
2022-10-21T08:04:59.323Z [err] ERR! peer node-red-dashboard@">=2.23.2" from node-red-contrib-ui-clock@1.0.2
2022-10-21T08:04:59.323Z [err] npm ERR! node_modules/node-red-contrib-ui-clock
2022-10-21T08:04:59.324Z [err] npm ERR!
2022-10-21T08:04:59.324Z [err] node-red-contrib-ui-clock@"~1.0.2" from the root project
2022-10-21T08:04:59.324Z [err] npm
2022-10-21T08:04:59.324Z [err] ERR! peer node-red-dashboard@">=2.23.2" from node-red-contrib-ui-digital-display@1.0.3
2022-10-21T08:04:59.324Z [err] npm ERR! node_modules/node-red-contrib-ui-digital-display
2022-10-21T08:04:59.324Z [err] npm
2022-10-21T08:04:59.325Z [err] ERR! node-red-contrib-ui-digital-display@"~1.0.3" from the root project
2022-10-21T08:04:59.325Z [err] npm ERR! 5 more (node-red-contrib-ui-led, node-red-node-ui-iframe, ...)
2022-10-21T08:04:59.325Z [err] npm
2022-10-21T08:04:59.325Z [err] ERR!
2022-10-21T08:04:59.325Z [err] npm ERR! Could not resolve dependency:
2022-10-21T08:04:59.325Z [err] npm
2022-10-21T08:04:59.325Z [err] ERR! peer node-red-dashboard@"^2.28.1" from @prescient-devices/node-red-contrib-dashboard-input-persistence@1.1.2
2022-10-21T08:04:59.325Z [err] npm ERR! node_modules/@prescient-devices/node-red-contrib-dashboard-input-persistence
2022-10-21T08:04:59.325Z [err] npm
2022-10-21T08:04:59.325Z [err] ERR! @prescient-devices/node-red-contrib-dashboard-input-persistence@"~1.1.2" from the root project
2022-10-21T08:04:59.325Z [err] npm ERR!
2022-10-21T08:04:59.325Z [err] npm
2022-10-21T08:04:59.332Z [err] ERR! Conflicting peer dependency: node-red-dashboard@2.30.0
2022-10-21T08:04:59.332Z [err] npm ERR! node_modules/node-red-dashboard
2022-10-21T08:04:59.332Z [err] npm ERR! peer node-red-dashboard@"^2.28.1" from @prescient-devices/node-red-contrib-dashboard-input-persistence@1.1.2
2022-10-21T08:04:59.332Z [err] npm ERR! node_modules/@prescient-devices/node-red-contrib-dashboard-input-persistence
2022-10-21T08:04:59.332Z [err] npm ERR! @prescient-devices/node-red-contrib-dashboard-input-persistence@"~1.1.2" from the root project
2022-10-21T08:04:59.332Z [err] npm ERR!
2022-10-21T08:04:59.332Z [err] npm ERR! Fix the upstream dependency conflict, or retry
2022-10-21T08:04:59.332Z [err] npm ERR! this command with --force, or --legacy-peer-deps
2022-10-21T08:04:59.332Z [err] npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
2022-10-21T08:04:59.332Z [err] npm ERR!
2022-10-21T08:04:59.332Z [err] npm ERR! See /home/iobroker/.npm/eresolve-report.txt for a full report.
2022-10-21T08:04:59.335Z [err]
2022-10-21T08:04:59.336Z [err] npm
2022-10-21T08:04:59.336Z [err] ERR! A complete log of this run can be found in:
2022-10-21T08:04:59.336Z [err] npm ERR! /home/iobroker/.npm/_logs/2022-10-21T08_04_51_068Z-debug-0.log
2022-10-21T08:04:59.358Z rc=1
-----------------------------------------------------------
2022-10-21T08:07:56.753Z Entfernen : node-red-contrib-alexa-remote2-applestrudel
Vielen Dank
Grüße
Michael
habe es geändert, leider ist es nicht besser geworden:
pi@raspberrypi:~ $ service ebusd status
● ebusd.service - LSB: controls ebusd, the daemon for communication with eBUS heating systems.
Loaded: loaded (/etc/init.d/ebusd; generated)
Active: active (running) since Fri 2021-07-02 18:01:03 CEST; 11min ago
Docs: man:systemd-sysv-generator(8)
Process: 7643 ExecStart=/etc/init.d/ebusd start (code=exited, status=0/SUCCESS)
Tasks: 4 (limit: 4915)
CGroup: /system.slice/ebusd.service
└─7650 /usr/bin/ebusd --pidfile /var/run/ebusd.pid -d /dev/ttyUSB0 -p 8888 --latency=10000 --receivetimeout=100000 -l /var/log/ebusd.log --configpath=http://ebusd.eu/config/ --s
Jul 02 18:01:03 raspberrypi systemd[1]: Starting LSB: controls ebusd, the daemon for communication with eBUS heating systems....
Jul 02 18:01:03 raspberrypi ebusd[7643]: Starting ebusd: ebusd.
Jul 02 18:01:03 raspberrypi systemd[1]: Started LSB: controls ebusd, the daemon for communication with eBUS heating systems..
eher schlechter:
pi@raspberrypi:~ $ ebusctl i
version: ebusd 21.2.v21.2
signal: acquired
symbol rate: 23
max symbol rate: 130
min arbitration micros: 629
max arbitration micros: 3956
min symbol latency: 4
max symbol latency: 8
reconnects: 0
masters: 3
messages: 214
conditional: 3
poll: 0
update: 10
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0104;HW=7803", loaded "vaillant/bai.308523.inc", "vaillant/08.bai.csv"
address 10: master #2
address 15: slave #2
address 31: master #8, ebusd
address 36: slave #8, ebusd
address ed: slave, scanned "MF=Vaillant;ID=VMS02;SW=0108;HW=1703"
ist es normal, dass ich nach einer config Änderung die Heizung aus und wieder einschalten muss?
Ich mache immer:
service ebusd stop
nano /etc/default/ebusd - anpassen
service ebbst start
Danach findet er garnichts mehr. Schalte ich die Heizungsanlage aus und danach wieder ein findet er was - siehe oben ebusctl i
Was mir noch aufgefallen ist, bei mir steht bei der Abfrage service ebusd status in Zeile 9 --pidfile /var/run/ebusd.pid```
CGroup: /system.slice/ebusd.service
└─7650 /usr/bin/ebusd --pidfile /var/run/ebusd.pid -d /dev/ttyUSB0 -p 8888 --latency=10000 --receivetimeout=100000 -l /var/log/ebusd.log --configpath=http://ebusd.eu/config/ --s
das habe ich so noch nirgends gesehen, liegt es evtl. daran?wow das ging schnell, für die Abfrage nicht als root?
Bleibt allerdings gleich
Hallo zusammen,
ich bin neu in diesem Thema und dies ist auch mein erster Post, bisher konnte ich alles lösen dank diesem Forum allerdings komme ich jetzt nicht weiter. Versuche seit 1,5Wochen den Ebus Adapter von Esera ans laufen zu bekommen.
Meine Anlage:
Therme - VC266/5-5
VMS 8 - Solarstation
VRC 700/6 Multimatic
meine aktuelle config:
EBUSD_OPTS="-d /dev/ttyUSB0 -p 8888 --latency=10000 --receivetimeout=100000 -l /var/log/ebusd.log --configpath=/etc/ebusd --scanconfig=full --httpport=8889 --htmlpath=/var/ebusd/html"
Ausgabe status:
root@raspberrypi:/home/pi# service ebusd status
● ebusd.service - LSB: controls ebusd, the daemon for communication with eBUS heating systems.
Loaded: loaded (/etc/init.d/ebusd; generated)
Active: active (running) since Fri 2021-07-02 15:09:31 CEST; 23min ago
Docs: man:systemd-sysv-generator(8)
Process: 4395 ExecStart=/etc/init.d/ebusd start (code=exited, status=0/SUCCESS)
Tasks: 4 (limit: 4915)
CGroup: /system.slice/ebusd.service
└─4402 /usr/bin/ebusd --pidfile /var/run/ebusd.pid -d /dev/ttyUSB0 -p 8888 --latency=10000 --receivetimeout=100000 -l /var/log/ebusd.log --configpath=/etc/ebusd --scanconfig=ful
Jul 02 15:09:31 raspberrypi systemd[1]: Starting LSB: controls ebusd, the daemon for communication with eBUS heating systems....
Jul 02 15:09:31 raspberrypi ebusd[4395]: Starting ebusd: ebusd.
Jul 02 15:09:31 raspberrypi systemd[1]: Started LSB: controls ebusd, the daemon for communication with eBUS heating systems..
Ausgabe info:
root@raspberrypi:/home/pi# ebusctl i
version: ebusd 21.2.v21.2
signal: acquired
symbol rate: 38
max symbol rate: 150
min arbitration micros: 622
max arbitration micros: 3982
min symbol latency: 2
max symbol latency: 11
reconnects: 0
masters: 3
messages: 214
conditional: 3
poll: 0
update: 10
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0104;HW=7803", loaded "vaillant/bai.308523.inc", "vaillant/08.bai.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=70000;SW=0613;HW=6903"
address 31: master #8, ebusd
address 36: slave #8, ebusd
address ed: slave, scanned "MF=Vaillant;ID=VMS02;SW=0108;HW=1703"
ich weis nicht wieso er die csv für die Geräte "ID=7000" und "ID=VMS02" nicht lädt. Hoffe es kann mir jemand helfen, habe das forum gefühlt 100 mal durchgelesen.
