ebusd.mqtt2.template: Fragen, Anregungen

[rudolfkoenig]

Wo findet man dazu eine Erklärung/ein Beispiel?

https://fhem.de/commandref_modular.html#jsonMap

Da es möglich ist, dass jemand mehrere ebus-Dämonen betreibt, wäre dann eben der nächste mit "ebuse" oder "ebusf" zu konfigurieren, da kommt der eine Punkt her.

Ok, dann halt (ebus..*?)/, immer noch kuerzer/einfacher lesbar.
Meine Loesung waere: wer mehr als ein ebus Daemon hat (meine Annahme: das ist selten), der soll den Regexp anpassen. Dafuer ist der Normalfall verstaendlich.

[Beta-User]

https://fhem.de/commandref_modular.html#jsonMap

...hätte ich mir eigentlich denken können...

Da wir grade bei commandref-Themen sind: Ich habe in https://fhem.de/commandref_modular.html#MYSENSORS_DEVICE mal einen englischen Text zu attrTemplate reingebaut. Wenn der paßt, könnte man das gerne nach MQTT2_DEVICE entsprechend übertragen; ich kann gerne auch eine deutsche Übersetzung liefern. (Was immer nicht so spaßig ist: den richtigen "level" bei der commandref-Sprache zu treffen, daher nur "notfalls" das Angebot, auch einen patch zu liefern)

Ok, dann halt (ebus..*?)/, immer noch kuerzer/einfacher lesbar.

So wird's gemacht.

Code Auswählen Erweitern

attr MQTT2_ebusd bridgeRegexp (ebus..*?)/(bai|\d+|cc|e7f|ehp|f\d\d|hc|he.|hmu|hwc|mc|mc.\d|omu|omu.\d|pms|rcc|rcc.\d|sc|sdr_p|ui|uih|v\d\d|v81.\d|vd\d|vl\d|vr_\d\d|zeo)/.*:.* "$1_$2"\
(ebus..*?)/(global|broadcast|general|scan([^/]*))/.*:.* "$1"


Meine Loesung waere: wer mehr als ein ebus Daemon hat (meine Annahme: das ist selten), der soll den Regexp anpassen. Dafuer ist der Normalfall verstaendlich.

In dem Zusammenhang: irgendwie hatte ich den Eindruck, dass die seltsamen topic-Pfade, die durch den weiteren ".?" abgefangen werden sollen, auch daher kamen, dass irgendwas im Kreis ging; leider kann ich das nicht konkreter beschreiben, aber es kam vermutlich entweder von dem Punkt im Topic-Pfad, den die scans erzeugen, oder es hatte was damit zu tun, dass auf dem Testsystem in der Ausgangskonfiguration mal ein CLIENT auf einen 2-er-SERVER gehört hatte (das habe ich leider erst später gemerkt).
Wenn das grundsätzlich ausgeschlossen werden kann und nur was mit dem Testsystem zu tun hat: Gerne.

(Das letzte war eigentlich eine Frage @all).

@Rudi ergänzend noch:
Ich betreibe mein Testsystem auch mit CLIENT und höre damit den SERVER auf dem Hauptsystem ab, damit ich Testdevices habe. Führt halt bei beiderseits eingeschaltetem Autocreate dazu, dass dass Hauptsystem wieder auf dem Hauptsystem als Abbild der vom Testsytem her ausgeführten MQTT-Anweisungen angelegt wird; wenn da escapte Sonderzeichen im Topic-Pfad drin sind, gibt das seltsame Ping-Pong-Spiele. Bei Gelegenheit scheibe ich mal was dazu, das ist hier OT, und ich habe dazu auch zu wenig konkretes bzw. selbst gehirnt...
Aber vielleicht kannst du das aus eigener Anschauung auch so verstehen, daher an der Stelle die Bemerkung; ansonsten: Vorerst wieder vergessen .

[Reinhart]

Grade zu den Geräten ohne ReadingList: werden die aktualisiert, wenn du das betreffende Browserfenster einfach offen hältst? (Ich habe sowas ähnliches mit meinen HM-RTs/WTs realisiert, und da werden "externe Daten" (von anderen Kanälen als dem dargestellten) nur dann aktualisiert, wenn sich ein "echtes" Reading des Devices ändert.) Ansonsten muß man die Seite neu laden...

Ja, das funktioniert. Man kann das leicht nachstellen, in einem Browserfenster öffnet man die Ansicht Pumpe mit Ventilator, im 2. Browserfenster erhöhe ich die Heizkurve und nach kurzer Zeit läuft die Pumpe und der Ventilator ( live ) hoch ohne einen Refresh im Browser durchzuführen zu müssen. Getestet mit Chrome Browser. Gleiches gilt wenn ich vom Hauptsystem über ECMD Kommandos losschicke (geht ja auf denselben eBus ), die sind im Testsystem bei offenem Fenster ebenfalls sofort sichtbar. In beiden Fällen, wird ja auch das "echte" Reading geändert. Das "sofort" bezieht sich allerdings nach dem zyklischen Eintreffen der MQTT Strings.

LG

[john30]

/list topic ist eingebaut, siehe wiki

[Beta-User]

/list topic ist eingebaut, siehe wiki

Thx.
Aktualisiertes template für den ebus-Dämon an sich ging eben ins svn (ein noArg füge ich bei Gelegenheit dazu, das ist mir eben auf die Schnelle durchgerutscht). Hoffe, das im Wiki richtig interpretiert zu haben, dass eine Payload an sich sinnvoll ist; bitte um Rückmeldung, wenn jemand da Verbesserungsbedarf sieht.

Code Auswählen Erweitern

attr DEVICE setList getKnown DEV_ID/global/list onlyknown

Da die Online- und Signal-Messages einen last will haben, gibt's dafür jetzt auch Symbole, allerdings wäre ich da auch für "hübschere" Varianten offen, habe halt erst mal genommen, was auf die Schnelle verfügbar war.

global|broadcast|general|scan habe ich jetzt mal dem ebusd-Gerät zugeordnet, da sich bisher keiner mit einer besseren Idee gemeldet hat...

@Reinhart:
Wäre schön, wenn du bei Gelegenheit den ebusd-Dienst auf dem Testsystem auf die letzte Version heben könntest .

[Reinhart]

Danke John, funktioniert!

Ich habe die letzte Version compiliert, beim "bushandler.o" erhalte ich eine Warning:

Code Auswählen Erweitern

  CXX      device.o
  CXX      message.o
  AR       libebus.a
ar: `u' modifier ignored since `D' is the default (see `U')
make[3]: Verzeichnis ,,/home/pi/ebusd/src/lib/ebus" wird verlassen
make[2]: Verzeichnis ,,/home/pi/ebusd/src/lib/ebus" wird verlassen
Making all in src/ebusd
make[2]: Verzeichnis ,,/home/pi/ebusd/src/ebusd" wird betreten
  CXX      bushandler.o
bushandler.cpp: In member function 'void ebusd::BusHandler::formatGrabResult(bool, bool, std::ostringstream*, bool, time_t, time_t) const':
bushandler.cpp:1561:19: warning: suggest parentheses around '&&' within '||' [-W parentheses]
     if (since > 0 && it.second.getLastTime() < since
         ~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  CXX      datahandler.o
  CXX      network.o
  CXX      mainloop.o

Wenn ich nun Abfrage erhalte ich mit:

Code Auswählen Erweitern

set ebusMQTT publish ebusd/bai/list
folgende Liste

Code Auswählen Erweitern

Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/list', ... (0 bytes))
ebusd/bai/list (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/AATemp', ... (0 bytes))
ebusd/bai/AATemp (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/AccessoriesOne', ... (0 bytes))
ebusd/bai/AccessoriesOne (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/AccessoriesOne', ... (0 bytes))
ebusd/bai/AccessoriesOne (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/AccessoriesTwo', ... (0 bytes))
ebusd/bai/AccessoriesTwo (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/AccessoriesTwo', ... (0 bytes))
ebusd/bai/AccessoriesTwo (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ACRoomthermostat', ... (0 bytes))
ebusd/bai/ACRoomthermostat (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/AircontrolOk', ... (0 bytes))
ebusd/bai/AircontrolOk (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/AITemp', ... (0 bytes))
ebusd/bai/AITemp (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/AntiCondensValue', ... (0 bytes))
ebusd/bai/AntiCondensValue (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/AntiCondensValue', ... (0 bytes))
ebusd/bai/AntiCondensValue (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/averageIgnitiontime', ... (0 bytes))
ebusd/bai/averageIgnitiontime (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/BlockTimeHcMax', ... (0 bytes))
ebusd/bai/BlockTimeHcMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/BlockTimeHcMax', ... (0 bytes))
ebusd/bai/BlockTimeHcMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/BoilerType2', ... (0 bytes))
ebusd/bai/BoilerType2 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/BoilerType', ... (0 bytes))
ebusd/bai/BoilerType (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ChangesDSN', ... (0 bytes))
ebusd/bai/ChangesDSN (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/CirPump', ... (0 bytes))
ebusd/bai/CirPump (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/clearerrorhistory', ... (0 bytes))
ebusd/bai/clearerrorhistory (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/CounterStartattempts1', ... (0 bytes))
ebusd/bai/CounterStartattempts1 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/CounterStartattempts2', ... (0 bytes))
ebusd/bai/CounterStartattempts2 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/CounterStartAttempts3', ... (0 bytes))
ebusd/bai/CounterStartAttempts3 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/currenterror', ... (0 bytes))
ebusd/bai/currenterror (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/DateTime', ... (145 bytes))
ebusd/bai/DateTime {
     "dcfstate": {"value": "nosignal"},
     "btime": {"value": "06:33:39"},
     "bdate": {"value": "-.-.-"},
     "temp2": {"value": 12.250}}
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/dcfState', ... (0 bytes))
ebusd/bai/dcfState (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/DCFTimeDate', ... (0 bytes))
ebusd/bai/DCFTimeDate (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/DCRoomthermostat', ... (0 bytes))
ebusd/bai/DCRoomthermostat (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/DeactivationsIFC', ... (0 bytes))
ebusd/bai/DeactivationsIFC (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/DeactivationsTemplimiter', ... (0 bytes))
ebusd/bai/DeactivationsTemplimiter (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/DeltaFlowReturnMax', ... (0 bytes))
ebusd/bai/DeltaFlowReturnMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/DisplayMode', ... (0 bytes))
ebusd/bai/DisplayMode (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/DSN', ... (0 bytes))
ebusd/bai/DSN (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/DSNOffset', ... (0 bytes))
ebusd/bai/DSNOffset (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/DSNOffset', ... (0 bytes))
ebusd/bai/DSNOffset (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/DSNStart', ... (0 bytes))
ebusd/bai/DSNStart (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/EBusHeatcontrol', ... (0 bytes))
ebusd/bai/EBusHeatcontrol (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/EbusSourceOn', ... (0 bytes))
ebusd/bai/EbusSourceOn (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/EbusVoltage', ... (0 bytes))
ebusd/bai/EbusVoltage (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/errorhistory', ... (0 bytes))
ebusd/bai/errorhistory (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ExhaustCurve', ... (0 bytes))
ebusd/bai/ExhaustCurve (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ExhaustCurve', ... (0 bytes))
ebusd/bai/ExhaustCurve (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/exhaustWayBlockCounter', ... (0 bytes))
ebusd/bai/exhaustWayBlockCounter (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/expertlevel_ReturnTemp', ... (0 bytes))
ebusd/bai/expertlevel_ReturnTemp (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ExternalFaultmessage', ... (0 bytes))
ebusd/bai/ExternalFaultmessage (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/externalFlowTempDesired', ... (0 bytes))
ebusd/bai/externalFlowTempDesired (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/externalHwcSwitch', ... (0 bytes))
ebusd/bai/externalHwcSwitch (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ExternGasvalve', ... (0 bytes))
ebusd/bai/ExternGasvalve (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ExtFlowTempDesiredMin', ... (0 bytes))
ebusd/bai/ExtFlowTempDesiredMin (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/extWP', ... (0 bytes))
ebusd/bai/extWP (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FanHours', ... (0 bytes))
ebusd/bai/FanHours (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FanMaxSpeedOperation', ... (0 bytes))
ebusd/bai/FanMaxSpeedOperation (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FanMinSpeedOperation', ... (0 bytes))
ebusd/bai/FanMinSpeedOperation (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FanPWMSum', ... (0 bytes))
ebusd/bai/FanPWMSum (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FanPWMTest', ... (0 bytes))
ebusd/bai/FanPWMTest (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FanSpeed', ... (37 bytes))
ebusd/bai/FanSpeed {
     "0": {"name": "", "value": 0}}
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FanStarts', ... (0 bytes))
ebusd/bai/FanStarts (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/Flame', ... (0 bytes))
ebusd/bai/Flame (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FlameSensingASIC', ... (0 bytes))
ebusd/bai/FlameSensingASIC (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FloorHeatingContact', ... (0 bytes))
ebusd/bai/FloorHeatingContact (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FlowsetHcMax', ... (0 bytes))
ebusd/bai/FlowsetHcMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FlowsetHcMax', ... (0 bytes))
ebusd/bai/FlowsetHcMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FlowsetHwcMax', ... (0 bytes))
ebusd/bai/FlowsetHwcMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FlowsetHwcMax', ... (0 bytes))
ebusd/bai/FlowsetHwcMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FlowSetPotmeter', ... (0 bytes))
ebusd/bai/FlowSetPotmeter (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FlowTemp', ... (64 bytes))
ebusd/bai/FlowTemp {
     "temp": {"value": 30.44},
     "sensor": {"value": "ok"}}
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FlowTempDesired', ... (32 bytes))
ebusd/bai/FlowTempDesired {
     "temp": {"value": 36.50}}
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/Fluegasvalve', ... (0 bytes))
ebusd/bai/Fluegasvalve (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/Gasvalve3UC', ... (0 bytes))
ebusd/bai/Gasvalve3UC (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/Gasvalve', ... (0 bytes))
ebusd/bai/Gasvalve (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/GasvalveASICFeedback', ... (0 bytes))
ebusd/bai/GasvalveASICFeedback (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/GasvalveUC', ... (0 bytes))
ebusd/bai/GasvalveUC (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/GasvalveUCFeedback', ... (0 bytes))
ebusd/bai/GasvalveUCFeedback (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/GVStepOffsetMax', ... (0 bytes))
ebusd/bai/GVStepOffsetMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/GVStepOffsetMax', ... (0 bytes))
ebusd/bai/GVStepOffsetMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/GVStepOffsetMin', ... (0 bytes))
ebusd/bai/GVStepOffsetMin (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/GVStepOffsetMin', ... (0 bytes))
ebusd/bai/GVStepOffsetMin (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HcHours', ... (0 bytes))
ebusd/bai/HcHours (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HcPumpMode', ... (0 bytes))
ebusd/bai/HcPumpMode (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HcPumpMode', ... (0 bytes))
ebusd/bai/HcPumpMode (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HcPumpStarts', ... (0 bytes))
ebusd/bai/HcPumpStarts (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HcStarts', ... (0 bytes))
ebusd/bai/HcStarts (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HcUnderHundredStarts', ... (0 bytes))
ebusd/bai/HcUnderHundredStarts (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HeatingSwitch', ... (0 bytes))
ebusd/bai/HeatingSwitch (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HoursTillService', ... (0 bytes))
ebusd/bai/HoursTillService (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HoursTillService', ... (0 bytes))
ebusd/bai/HoursTillService (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcDemand', ... (0 bytes))
ebusd/bai/HwcDemand (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcHours', ... (0 bytes))
ebusd/bai/HwcHours (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcImpellorSwitch', ... (0 bytes))
ebusd/bai/HwcImpellorSwitch (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcPostrunTime', ... (0 bytes))
ebusd/bai/HwcPostrunTime (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcPostrunTime', ... (0 bytes))
ebusd/bai/HwcPostrunTime (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcSetPotmeter', ... (0 bytes))
ebusd/bai/HwcSetPotmeter (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcStarts', ... (0 bytes))
ebusd/bai/HwcStarts (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcSwitch', ... (0 bytes))
ebusd/bai/HwcSwitch (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcTemp', ... (0 bytes))
ebusd/bai/HwcTemp (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcTempDesired', ... (0 bytes))
ebusd/bai/HwcTempDesired (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcTempMax', ... (0 bytes))
ebusd/bai/HwcTempMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcTempMax', ... (0 bytes))
ebusd/bai/HwcTempMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcTypes', ... (0 bytes))
ebusd/bai/HwcTypes (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcUnderHundredStarts', ... (0 bytes))
ebusd/bai/HwcUnderHundredStarts (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcWaterflow', ... (0 bytes))
ebusd/bai/HwcWaterflow (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcWaterflowMax', ... (0 bytes))
ebusd/bai/HwcWaterflowMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/Ignitor', ... (0 bytes))
ebusd/bai/Ignitor (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/IonisationVoltageLevel', ... (0 bytes))
ebusd/bai/IonisationVoltageLevel (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/maintenancedata_HwcTempMax', ... (0 bytes))
ebusd/bai/maintenancedata_HwcTempMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/maxIgnitiontime', ... (0 bytes))
ebusd/bai/maxIgnitiontime (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/minIgnitiontime', ... (0 bytes))
ebusd/bai/minIgnitiontime (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ModulationTempDesired', ... (0 bytes))
ebusd/bai/ModulationTempDesired (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/OutdoorstempSensor', ... (64 bytes))
ebusd/bai/OutdoorstempSensor {
     "temp": {"value": 12.50},
     "sensor": {"value": "ok"}}
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/OverflowCounter', ... (0 bytes))
ebusd/bai/OverflowCounter (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ParamToken', ... (0 bytes))
ebusd/bai/ParamToken (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PartloadHcKW', ... (0 bytes))
ebusd/bai/PartloadHcKW (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PartloadHcKW', ... (0 bytes))
ebusd/bai/PartloadHcKW (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PartloadHwcKW', ... (0 bytes))
ebusd/bai/PartloadHwcKW (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PartloadHwcKW', ... (0 bytes))
ebusd/bai/PartloadHwcKW (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PartnumberBox', ... (0 bytes))
ebusd/bai/PartnumberBox (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PositionValveSet', ... (0 bytes))
ebusd/bai/PositionValveSet (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PowerValue', ... (0 bytes))
ebusd/bai/PowerValue (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PrAPSCounter', ... (0 bytes))
ebusd/bai/PrAPSCounter (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PrAPSSum', ... (0 bytes))
ebusd/bai/PrAPSSum (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredCombustionDecrementTime', ... (0 bytes))
ebusd/bai/PredCombustionDecrementTime (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredCombustionPredCounter', ... (0 bytes))
ebusd/bai/PredCombustionPredCounter (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredCombustionSwitchingPoint', ... (0 bytes))
ebusd/bai/PredCombustionSwitchingPoint (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredFanPWMDevThreshold', ... (0 bytes))
ebusd/bai/PredFanPWMDevThreshold (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredFanPWMPredCounter', ... (0 bytes))
ebusd/bai/PredFanPWMPredCounter (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredFanPWMRefPWMcounter', ... (0 bytes))
ebusd/bai/PredFanPWMRefPWMcounter (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredFanPWMRefPWMsum', ... (0 bytes))
ebusd/bai/PredFanPWMRefPWMsum (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredFanPWMSwitchingPoint', ... (0 bytes))
ebusd/bai/PredFanPWMSwitchingPoint (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredIgnitionPredCounter', ... (0 bytes))
ebusd/bai/PredIgnitionPredCounter (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredIgnitionSwitchingPoint', ... (0 bytes))
ebusd/bai/PredIgnitionSwitchingPoint (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredSourcePressureDevThreshold', ... (0 bytes))
ebusd/bai/PredSourcePressureDevThreshold (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredSourcePressurePredCounter', ... (0 bytes))
ebusd/bai/PredSourcePressurePredCounter (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredSourcePressureSwitchingPoint', ... (0 bytes))
ebusd/bai/PredSourcePressureSwitchingPoint (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredWaterflowDevThreshold', ... (0 bytes))
ebusd/bai/PredWaterflowDevThreshold (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredWaterflowSwitchingPoint', ... (0 bytes))
ebusd/bai/PredWaterflowSwitchingPoint (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredWaterpressureMaxPressure', ... (0 bytes))
ebusd/bai/PredWaterpressureMaxPressure (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredWaterpressureMinPressure', ... (0 bytes))
ebusd/bai/PredWaterpressureMinPressure (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PredWaterpressureSwitchingPoint', ... (0 bytes))
ebusd/bai/PredWaterpressureSwitchingPoint (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PrEnergyCountHc1', ... (0 bytes))
ebusd/bai/PrEnergyCountHc1 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PrEnergyCountHc2', ... (0 bytes))
ebusd/bai/PrEnergyCountHc2 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PrEnergyCountHc3', ... (0 bytes))
ebusd/bai/PrEnergyCountHc3 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PrEnergyCountHwc1', ... (0 bytes))
ebusd/bai/PrEnergyCountHwc1 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PrEnergyCountHwc2', ... (0 bytes))
ebusd/bai/PrEnergyCountHwc2 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PrEnergyCountHwc3', ... (0 bytes))
ebusd/bai/PrEnergyCountHwc3 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PrEnergySumHc1', ... (0 bytes))
ebusd/bai/PrEnergySumHc1 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PrEnergySumHc2', ... (0 bytes))
ebusd/bai/PrEnergySumHc2 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PrEnergySumHc3', ... (0 bytes))
ebusd/bai/PrEnergySumHc3 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PrEnergySumHwc1', ... (0 bytes))
ebusd/bai/PrEnergySumHwc1 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PrEnergySumHwc2', ... (0 bytes))
ebusd/bai/PrEnergySumHwc2 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PrEnergySumHwc3', ... (0 bytes))
ebusd/bai/PrEnergySumHwc3 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PumpHours', ... (0 bytes))
ebusd/bai/PumpHours (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PumpHwcFlowNumber', ... (0 bytes))
ebusd/bai/PumpHwcFlowNumber (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PumpHwcFlowSum', ... (0 bytes))
ebusd/bai/PumpHwcFlowSum (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ReduceModulationBlocktime', ... (0 bytes))
ebusd/bai/ReduceModulationBlocktime (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ReduceModulationBlocktime', ... (0 bytes))
ebusd/bai/ReduceModulationBlocktime (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/RemainingBoilerblocktime', ... (0 bytes))
ebusd/bai/RemainingBoilerblocktime (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ReturnRegulation', ... (0 bytes))
ebusd/bai/ReturnRegulation (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ReturnRegulation', ... (0 bytes))
ebusd/bai/ReturnRegulation (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ReturnTemp', ... (101 bytes))
ebusd/bai/ReturnTemp {
     "temp": {"value": 30.56},
     "tempmirror": {"value": 65046},
     "sensor": {"value": "ok"}}
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ReturnTempMax', ... (0 bytes))
ebusd/bai/ReturnTempMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/SecondPumpMode', ... (0 bytes))
ebusd/bai/SecondPumpMode (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/SecondPumpMode', ... (0 bytes))
ebusd/bai/SecondPumpMode (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/SerialNumber', ... (0 bytes))
ebusd/bai/SerialNumber (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/SetFactoryValues', ... (0 bytes))
ebusd/bai/SetFactoryValues (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/SetFactoryValues', ... (0 bytes))
ebusd/bai/SetFactoryValues (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/SetMode', ... (384 bytes))
ebusd/bai/SetMode {
     "hcmode": {"value": "auto"},
     "flowtempdesired": {"value": 36.5},
     "hwctempdesired": {"value": null},
     "hwcflowtempdesired": {"value": null},
     "disablehc": {"value": 0},
     "disablehwctapping": {"value": 0},
     "disablehwcload": {"value": 1},
     "remoteControlHcPump": {"value": 0},
     "releaseBackup": {"value": 0},
     "releaseCooling": {"value": 0}}
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/SHEMaxDeltaHwcFlow', ... (0 bytes))
ebusd/bai/SHEMaxDeltaHwcFlow (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/SHEMaxFlowTemp', ... (0 bytes))
ebusd/bai/SHEMaxFlowTemp (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/SolPostHeat', ... (0 bytes))
ebusd/bai/SolPostHeat (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/SpecialAdj', ... (0 bytes))
ebusd/bai/SpecialAdj (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/SpecialAdj', ... (0 bytes))
ebusd/bai/SpecialAdj (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/Statenumber', ... (0 bytes))
ebusd/bai/Statenumber (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/Status01', ... (272 bytes))
ebusd/bai/Status01 {
     "0": {"name": "temp1", "value": 30.0},
     "1": {"name": "temp1", "value": 30.0},
     "2": {"name": "temp2", "value": 12.250},
     "3": {"name": "temp1", "value": 31.0},
     "4": {"name": "temp1", "value": 33.0},
     "5": {"name": "pumpstate", "value": "off"}}
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/Status02', ... (221 bytes))
ebusd/bai/Status02 {
     "0": {"name": "hwcmode", "value": "auto"},
     "1": {"name": "temp0", "value": 60},
     "2": {"name": "temp1", "value": 70.0},
     "3": {"name": "temp0", "value": 70},
     "4": {"name": "temp1", "value": 48.0}}
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/Status16', ... (0 bytes))
ebusd/bai/Status16 (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/Status', ... (0 bytes))
ebusd/bai/Status (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/Storageloadpump', ... (0 bytes))
ebusd/bai/Storageloadpump (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/StorageLoadPumpHours', ... (0 bytes))
ebusd/bai/StorageLoadPumpHours (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/StorageloadPumpStarts', ... (0 bytes))
ebusd/bai/StorageloadPumpStarts (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/StorageLoadTimeMax', ... (0 bytes))
ebusd/bai/StorageLoadTimeMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/StorageLoadTimeMax', ... (0 bytes))
ebusd/bai/StorageLoadTimeMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/StoragereleaseClock', ... (0 bytes))
ebusd/bai/StoragereleaseClock (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/StorageTemp', ... (0 bytes))
ebusd/bai/StorageTemp (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/StorageTempDesired', ... (0 bytes))
ebusd/bai/StorageTempDesired (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/StorageTempMax', ... (0 bytes))
ebusd/bai/StorageTempMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/TargetFanSpeed', ... (0 bytes))
ebusd/bai/TargetFanSpeed (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/TargetFanSpeedOutput', ... (0 bytes))
ebusd/bai/TargetFanSpeedOutput (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/TempDiffBlock', ... (0 bytes))
ebusd/bai/TempDiffBlock (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/TempDiffFailure', ... (0 bytes))
ebusd/bai/TempDiffFailure (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/TempGradientFailure', ... (0 bytes))
ebusd/bai/TempGradientFailure (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/Templimiter', ... (0 bytes))
ebusd/bai/Templimiter (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/TemplimiterWithNTC', ... (0 bytes))
ebusd/bai/TemplimiterWithNTC (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/TempMaxDiffExtTFT', ... (0 bytes))
ebusd/bai/TempMaxDiffExtTFT (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/TimerInputHc', ... (0 bytes))
ebusd/bai/TimerInputHc (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ValveMode', ... (0 bytes))
ebusd/bai/ValveMode (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ValveMode', ... (0 bytes))
ebusd/bai/ValveMode (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ValveStarts', ... (0 bytes))
ebusd/bai/ValveStarts (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/VolatileLockout', ... (0 bytes))
ebusd/bai/VolatileLockout (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WarmstartDemand', ... (0 bytes))
ebusd/bai/WarmstartDemand (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WarmstartOffset', ... (0 bytes))
ebusd/bai/WarmstartOffset (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WaterHcFlowMax', ... (0 bytes))
ebusd/bai/WaterHcFlowMax (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WaterPressure', ... (65 bytes))
ebusd/bai/WaterPressure {
     "press": {"value": 1.550},
     "sensor": {"value": "ok"}}
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WaterpressureBranchControlOff', ... (0 bytes))
ebusd/bai/WaterpressureBranchControlOff (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WaterpressureMeasureCounter', ... (0 bytes))
ebusd/bai/WaterpressureMeasureCounter (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WaterpressureVariantSum', ... (0 bytes))
ebusd/bai/WaterpressureVariantSum (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WP', ... (0 bytes))
ebusd/bai/WP (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WPPostrunTime', ... (0 bytes))
ebusd/bai/WPPostrunTime (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WPPostrunTime', ... (0 bytes))
ebusd/bai/WPPostrunTime (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WPPWMPower', ... (32 bytes))
ebusd/bai/WPPWMPower {
     "percent0": {"value": 0}}
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WPPWMPowerDia', ... (0 bytes))
ebusd/bai/WPPWMPowerDia (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WPPWMPowerDia', ... (0 bytes))
ebusd/bai/WPPWMPowerDia (null)
Client mosqsub/10880-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WPSecondStage', ... (0 bytes))
ebusd/bai/WPSecondStage (null)


@Beta-User

diese Version "ebusd 3.3.v3.3-19-ga3f4999" läuft nun ebenfalls am Testsystem.

LG

[Reinhart]

gleich noch eine Frage an John!

Sehe ich das jetzt richtig, dass mit "list" nur der Cache des Dämon angefragt wird und keine "echte" (forced) Busanfrage stattfindet?

LG

[Beta-User]

@Beta-User

diese Version "ebusd 3.3.v3.3-19-ga3f4999" läuft nun ebenfalls am Testsystem.

LG

Thx. Mit

Code Auswählen Erweitern

attr DEVICE setList getKnown:noArg DEV_ID/global/list onlyknownbzw. Auslösen des set scheint jetzt einiges an Info zu kommen. Ich würde daher mal ein "set DEVICE getknown" ans Ende des template schreiben. Komplett sähe das dann so aus:

Code Auswählen Erweitern

name:E_01a_eBus_daemon_splitter
filter:TYPE=MQTT2_DEVICE
desc:Device containing all status messages from the ebus daemon itself<br>NOTE: acts also as a bridge device to split up the hardware on the bus into different mqtt2_devices<br>NOTE:<br>- for use with MQTT2_CLIENT use a copy of the Device with the same clientId than the IO, delete original's readingList after applying the template!<br>- this might change the devices CID
par:DEVTYPE;Internal TYPE of the device; { InternalVal("DEVICE","TYPE","")}
par:DEV_ID;base topic set ebus;{ AttrVal("DEVICE","readingList","") =~ m,[^:]+:?(ebus[a-zA-Z])[^/]*[/].*:, ? $1 : "ebusd" }
modify DEVICE DEV_ID
attr DEVICE autocreate 1
attr DEVICE bridgeRegexp (ebus..*?)/(bai|\d+|cc|e7f|ehp|f\d\d|hc|he.|hmu|hwc|mc|mc.\d|omu|omu.\d|pms|rcc|rcc.\d|sc|sdr_p|ui|uih|v\d\d|v81.\d|vd\d|vl\d|vr_\d\d|zeo)/.*:.* "$1_$2"\
(ebus..*?)/(global|broadcast|general|scan([^/]*))/.*:.* "$1"
attr DEVICE icon sani_boiler_temp
attr DEVICE userReadings formatedUptime:uptime.* {my $m = ReadingsVal($name,"uptime",0)/60;; return sprintf "0 000 00:%02d", $m if $m < 60;; my $h = $m / 60;; $m %= 60;; return sprintf "0 000 %02d:%02d", $h, $m if $h < 24;; my $d = $h / 24;; $h %= 24;; return sprintf "0 %03d %02d:%02d", $d, $h, $m if $d <365;; my $y = $d / 365;; $d %= 365;; return sprintf "%d %03d %02d:%02d", $y, $d, $h, $m}
attr DEVICE stateFormat Status: \
1:running\
Signal: \
2:signal\
<br>Uptime: formatedUptime
attr DEVICE setList getKnown:noArg DEV_ID/global/list onlyknown
set DEVICE getKnown
attr DEVICE model E_01a_eBus_daemon_splitter
Magst du das file auf dem Testystem mal entsprechend anpassen, die ebus-Devices komplett löschen, save drauf, und dann nochmal schauen, ob das template nach Anwendung auf das dann wieder "nackige" ebusd-MQTT2-Sammel-Device erwartungsgemäß alles sauber sortiert und den ebusd so anpingt, dass wir gleich eine halbwegs komplette Übersicht (also bezogen auf das Testsystem: alle drei die Hardware repräsentierenden Geräte) haben?

[Reinhart]

habe das jetzt gemacht, aber bei "global" kommt gar nichts.

Please note that the global topic prefix is not published again by the /list suffix.

LG

[Beta-User]

habe das jetzt gemacht, aber bei "global" kommt gar nichts.

LG

Hmm,
die global-Dinge landen sauber im ebusd-Gerät selbst; das ist durch die bridgeRegexp so eingestellt.

Aber der "bai" scheint verschwunden zu bleiben?

[Reinhart]

da haben wir uns mißverstanden, dieses "global" funktioniert nicht:

Code Auswählen Erweitern


getKnown:noArg ebusd/global/list onlyknown

so gehts

Code Auswählen Erweitern


getKnown430:noArg ebusd/430/list onlyknown
getKnownBai:noArg ebusd/bai/list onlyknown

Warum die "bai" nicht gekommen sind war der Dämon, er hat alles geliefert nur keine "bai". Ein Restart des Dämon hat das Problem behoben.

LG

[Beta-User]

Hmm, Danke für die Rückmeldung.

Mit dieser spezifischen Form der "list"-Abfrage beißt sich aber die Katze wieder in den Schwanz: wir wollten doch eigentlich eine Abfragefunktionalität haben, mit der man feststellen kann, was am Bus alles so verfügbar ist. So müßen erst wieder die Zielbaugruppen angegeben werden, die "wir" ja noch gar nicht kennen...
Diese spezifische Art der Abfrage würde ich daher eher bei den einzelnen Devices unterbringen wollen (dort dann aber wieder ohne den Zusatz 430 bzw Bai).

Nach den Äußerungen von John30 klang das aber danach, als wäre die globale Abfrage "einen Level höher" angedacht. Oder habe ich schlicht den falschen Pfad erwischt?

Dass "bai" wieder da war, und dann auch das entsprechende Device sauber angelegt wurde, habe ich vorhin gesehen, danke.

[Reinhart]

es geht nur die Topic "global" nicht, das was du suchst, findet man ohne "global".

Code Auswählen Erweitern

set Mosquitto publish ebusd/list onlyknown

Code Auswählen Erweitern

Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/list', ... (9 bytes))
ebusd/list onlyknown
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/430/Date', ... (39 bytes))
ebusd/430/Date {
     "date": {"value": "08.04.2019"}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/430/Hc1HeatCurve', ... (32 bytes))
ebusd/430/Hc1HeatCurve {
     "curve": {"value": 1.00}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/430/HwcTempDesired', ... (32 bytes))
ebusd/430/HwcTempDesired {
     "temp1": {"value": 57.0}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/430/Time', ... (37 bytes))
ebusd/430/Time {
     "time": {"value": "17:16:40"}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/CounterStartattempts1', ... (30 bytes))
ebusd/bai/CounterStartattempts1 {
     "temp0": {"value": 29}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/DateTime', ... (145 bytes))
ebusd/bai/DateTime {
     "dcfstate": {"value": "nosignal"},
     "btime": {"value": "05:44:53"},
     "bdate": {"value": "-.-.-"},
     "temp2": {"value": 17.375}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/DeactivationsIFC', ... (38 bytes))
ebusd/bai/DeactivationsIFC {
     "0": {"name": "", "value": 18}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FanHours', ... (35 bytes))
ebusd/bai/FanHours {
     "hoursum2": {"value": 6378}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FanSpeed', ... (37 bytes))
ebusd/bai/FanSpeed {
     "0": {"name": "", "value": 0}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FlowTemp', ... (64 bytes))
ebusd/bai/FlowTemp {
     "temp": {"value": 25.88},
     "sensor": {"value": "ok"}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FlowTempDesired', ... (32 bytes))
ebusd/bai/FlowTempDesired {
     "temp": {"value": 29.50}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HcHours', ... (35 bytes))
ebusd/bai/HcHours {
     "hoursum2": {"value": 5466}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HcStarts', ... (41 bytes))
ebusd/bai/HcStarts {
     "0": {"name": "", "value": 39800}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcHours', ... (34 bytes))
ebusd/bai/HwcHours {
     "hoursum2": {"value": 686}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcSetPotmeter', ... (32 bytes))
ebusd/bai/HwcSetPotmeter {
     "temp": {"value": 48.94}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcStarts', ... (41 bytes))
ebusd/bai/HwcStarts {
     "0": {"name": "", "value": 88600}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/OutdoorstempSensor', ... (64 bytes))
ebusd/bai/OutdoorstempSensor {
     "temp": {"value": 17.38},
     "sensor": {"value": "ok"}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PartloadHcKW', ... (30 bytes))
ebusd/bai/PartloadHcKW {
     "power": {"value": 18}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/ReturnTemp', ... (101 bytes))
ebusd/bai/ReturnTemp {
     "temp": {"value": 24.38},
     "tempmirror": {"value": 65145},
     "sensor": {"value": "ok"}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/SetMode', ... (384 bytes))
ebusd/bai/SetMode {
     "hcmode": {"value": "auto"},
     "flowtempdesired": {"value": 29.5},
     "hwctempdesired": {"value": null},
     "hwcflowtempdesired": {"value": null},
     "disablehc": {"value": 0},
     "disablehwctapping": {"value": 0},
     "disablehwcload": {"value": 1},
     "remoteControlHcPump": {"value": 0},
     "releaseBackup": {"value": 0},
     "releaseCooling": {"value": 0}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/Status01', ... (272 bytes))
ebusd/bai/Status01 {
     "0": {"name": "temp1", "value": 25.0},
     "1": {"name": "temp1", "value": 24.0},
     "2": {"name": "temp2", "value": 17.375},
     "3": {"name": "temp1", "value": 35.0},
     "4": {"name": "temp1", "value": 36.0},
     "5": {"name": "pumpstate", "value": "off"}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/Status02', ... (221 bytes))
ebusd/bai/Status02 {
     "0": {"name": "hwcmode", "value": "auto"},
     "1": {"name": "temp0", "value": 60},
     "2": {"name": "temp1", "value": 70.0},
     "3": {"name": "temp0", "value": 70},
     "4": {"name": "temp1", "value": 48.0}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WaterPressure', ... (65 bytes))
ebusd/bai/WaterPressure {
     "press": {"value": 1.514},
     "sensor": {"value": "ok"}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WPPWMPower', ... (32 bytes))
ebusd/bai/WPPWMPower {
     "percent0": {"value": 0}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/broadcast/outsidetemp', ... (34 bytes))
ebusd/broadcast/outsidetemp {
     "temp2": {"value": 15.375}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/broadcast/vdatetime', ... (75 bytes))
ebusd/broadcast/vdatetime {
     "time": {"value": "17:16:55"},
     "date": {"value": "08.04.2019"}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/scan.08/', ... (126 bytes))
ebusd/scan.08/ {
     "MF": {"value": "Vaillant"},
     "ID": {"value": "BAI00"},
     "SW": {"value": "0518"},
     "HW": {"value": "7401"}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/scan.08/id', ... (211 bytes))
ebusd/scan.08/id {
     "prefix": {"value": ""},
     "year": {"value": ""},
     "week": {"value": ""},
     "product": {"value": ""},
     "supplier": {"value": ""},
     "counter": {"value": ""},
     "suffix": {"value": ""}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/scan.15/', ... (126 bytes))
ebusd/scan.15/ {
     "MF": {"value": "Vaillant"},
     "ID": {"value": "43000"},
     "SW": {"value": "0215"},
     "HW": {"value": "2002"}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/scan.15/id', ... (239 bytes))
ebusd/scan.15/id {
     "prefix": {"value": "21"},
     "year": {"value": "11"},
     "week": {"value": "09"},
     "product": {"value": "0020028515"},
     "supplier": {"value": "0907"},
     "counter": {"value": "006374"},
     "suffix": {"value": "N5"}}
Client mosqsub/22694-Raspberry received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (5 bytes))
ebusd/global/uptime 81804


hier werden alle Geräte aufgelistet, aber auch nur deshalb weil sie bereits durch autocreate erfasst wurden, also einmal schon Daten abgefragt wurden. Ohne "onlyknown" werden alle Geräte gefunden die per CSV geladen wurden. Die kann ich aber hier nich tposten, weil der Code Tag das nicht packt.

LG

[Beta-User]

Argh, manchmal ist es so einfach...

Die readingList mit den ganzen Einträgen ohne Content wird jetzt zumindest beim 430 auch wieder so lang, dass das nicht optimal ist, oder? Schwierig, da zu sagen, was Sinn macht.
Einfach so ohne Parameter würde ich das also nicht ins template nehmen und aufrufen, wenn dann gibt es eben noch einen zweiten Eintrag "getAll", der dann den publish ohne payload macht?

Bisher hatte ich verstanden, dass sich das auf der ebusd-Seite schon automatisch irgendwann füllen würde, und man dann lediglich den erstmaligen publish veranlassen würde. Das wäre m.E. eigentlich die richtige Vorgehensweise.

[john30]

also die /global Elemente sind so speziell und völlig unabhängig von vom Scan Ergebnis und der Anlagenkonfiguration, dass ich das (fürst Erste) nicht ins /list Result mit aufgenommen habe. Wenn ihr das unbedingt braucht, kann ich es schon noch einbauen.
Genau, /list löst by intention niemals einen Bus Request aus.