Code: Select all
/qmf/qml/apps/boilerMonitor
Moderators: marcelr, TheHogNL, Toonz
Code: Select all
/qmf/qml/apps/boilerMonitor
Aren't all available variables not listed in qmf_project.xml?Ierlandfan wrote: As stated probably more values exist depending on your boilertype.
It' s probably a pre-populated list of values based on boiler manufacturer and Boiler (Beta) user input.
I can also see in the strace from happ_thermstat that Toon is actively checking for exisiting ID's and throws a "Not supported" message otherwise.
Yes.Toonz wrote:Another question: my dev toon is not connected to the boiler. Does anyone know if there is an opentherm boiler simulator (via a raspberry for example?) out there which I can connect to the 'keteladapter' ?
This is just the app where you can register your boiler brand/model/type and give consent to Eneco to use these data.Ierlandfan wrote:No idea what it does yet but that's easy to find out.Code: Select all
/qmf/qml/apps/boilerMonitor
You reminded me of a post from januari 2017 where we already saw the OT data being graphed.Aren't all available variables not listed in qmf_project.xml?
Values are also logged and stored in rra databases (see config_hcb_rrd.xml)
Code: Select all
boiler_burner_minutes-10yrdays.csv
boiler_burner_minutes-5yrhours.csv
thermstat_boilerBurnerHours-30days.csv
thermstat_boilerBurnerHours-year.csv
thermstat_boilerChPressure-30days.csv
thermstat_boilerChPressure-year.csv
thermstat_boilerDhwBurnerHours-30days.csv
thermstat_boilerDhwBurnerHours-year.csv
thermstat_boilerFailedBurnerStarts-30days.csv
thermstat_boilerFailedBurnerStarts-year.csv
thermstat_boilerOpMode-30days.csv
thermstat_boilerOpMode-year.csv
thermstat_boilerPumpStarts-30days.csv
thermstat_boilerPumpStarts-year.csv
thermstat_boilerRetTemp-30days.csv
thermstat_boilerRetTemp-year.csv
thermstat_boilerSetpoint-30days.csv
thermstat_boilerSetpoint-year.csv
thermstat_boilerSuccesfulBurnerStarts-30days.csv
thermstat_boilerSuccesfulBurnerStarts-year.csv
thermstat_boilerTemp-30days.csv
thermstat_boilerTemp-year.csv
thermstat_dhwBurnerStarts-30days.csv
thermstat_dhwBurnerStarts-year.csv
thermstat_heatingFactor-30days.csv
thermstat_heatingFactor-year.csv
-thermstat_outsideRate-30days.csv
Had a quick look, it isn't as easy from QML because interaction with bxt is via the built-in module BxtClient which has a defined set of functionality.marcelr wrote:Looking at the reply to the ./bxt query, it shouldn't be too hard to squeeze the queries into a piece of qml code.
Code: Select all
var msg = bxtFactory.newBxtMessage(BxtMessage.ACTION_INVOKE, p.thermstatUuid, "specific1", "GetBoilerBrands");
// Timeout is one second more than the timeout in happ_scsync
bxtClient.doAsyncBxtRequest(msg, parseBoilerBrands, 16);
return requestId;
Code: Select all
[bxt.c]Sending HBXT_QUERY_INVOKE from bxt.c-28534 to 7d8ef81a-b3b6-4c0c-a0f9-272 973bd7497/specific1: n=QueryStateVariable varName=BoilerChPressure
Code: Select all
var msg = bxtFactory.newBxtMessage(BxtMessage.ACTION_INVOKE, p.thermstatUuid, "specific1", "BoilerChPressure");
// Timeout is one second more than the timeout in happ_scsync
bxtClient.doAsyncBxtRequest(msg, BoilerChPressure, 16);
return BoilerChPressure;
Code: Select all
Boxtalk Message to Send:
-------------------------------------------------------------------------------- ------------
<query class="invoke" uuid="set-by-hcom_send" destuuid="7d8ef81a-b3b6-4c0c-a0f9- 272973bd7497" serviceid="urn:hcb-hae-com:serviceId:specific1">
<u:QueryStateVariable xmlns:u="urn:hcb-hae-com:service:specific1:1"><varName >BoilerChPressure</varName>
</u:QueryStateVariable>
</query>