Closed Dinth closed 6 years ago
Same on my turboTEC plus VU 202
did you already check the writable messages with "find -w"? anyway, this is not an ebusd issue but rather ebusd-configuration.
Hi John30. Indeed, it may be a configuration problem, but i believe there are two issues here:
Here's the output of find -w. Actually i found a really weird thing here. If i do "find -w" im getting "no data stored" on all variables, but if i just do "find" ebusctl shows the data stored in a variable.
localhost: find -w
bai AccessoriesOne = no data stored
bai AccessoriesTwo = no data stored
bai AntiCondensValue = no data stored
bai BlockTimeHcMax = no data stored
bai clearerrorhistory = no data stored
bai DSNOffset = no data stored
bai FanSpeedOffsetMax = no data stored
bai FanSpeedOffsetMin = no data stored
bai FlowsetHcMax = no data stored
bai HcPumpMode = no data stored
bai HoursTillService = no data stored
bai HwcTempMax = no data stored
bai OptionalRelais = no data stored
bai PartloadHcKW = no data stored
bai PumpPowerDesired = no data stored
bai ReturnRegulation = no data stored
bai SetFactoryValues = no data stored
bai StorageLoadTimeMax = no data stored
bai WPPostrunTime = no data stored
broadcast id = no data stored
broadcast queryexistence = no data stored
memory eeprom = no data stored
memory ram = no data stored
localhost: find
bai AccessoriesOne = circulationpump
bai AccessoriesTwo = extheatingpump
(...)
I cannot write to a variable which is writable (FlowsetHcMax)
it seems your bai just ignores the write. can't do anything about that I'm afraid. Do you have a controller as well? Then you could try setting the parameter there and watch the bus for corresponding messages in order to correct/adjust the message definition.
Variables which should be writable, are not (HeatingSwitch)
the bai definitions were extracted from a manufacturer DB and that's how it is defined there. Since I don't own all of the devices I can't validate them, so if you're sure the message is writeable, then please issue a corresponding pull request on ebusd-configuration.
it seems your bai just ignores the write. can't do anything about that I'm afraid. Do you have a controller as well?
Unfortunately i dont, ive been hoping that i will be able to control the boiler usingjust an RPi and ebus. Im not a gas enginner, is it just a matter of getting a VCR700 for debugging or i would also need to install a wireless receiver in the boiler?
Since I don't own all of the devices I can't validate them, so if you're sure the message is writeable, then please issue a corresponding pull request on ebusd-configuration.
Fully understand. Is there a way i could confirm if the value is writable before issuing a pull request, or help in any other way to make ebusd better if im not a coder ?
Unfortunately i dont, ive been hoping that i will be able to control the boiler usingjust an RPi and ebus. Im not a gas enginner, is it just a matter of getting a VCR700 for debugging or i would also need to install a wireless receiver in the boiler?
it is for finding out what messages the boiler is willing to answer to. anyway, before spending money, you should probably have a look at the "standard" messages that are understood by most of the heating devices, see here for heating hcmode.inc and here for hot water unit hwcmode.inc.
Is there a way i could confirm if the value is writable before issuing a pull request, or help in any other way to make ebusd better if im not a coder ?
well just set it to writable, write the value and check that the desired effect becomes real.
I created pull request #101 at ebusd-configuration repository which makes HeatingSwitch and HwcSwitch writable. Also i translated the file into english. When i will have some spare time i will also try to check other variables if they can be made r/w
closed in favour of https://github.com/john30/ebusd/issues/101
Hi. Im struggling with figuring out how to use ebusd together with my combi boiler, as most values which normally should be writable are read only (for example HeatingSwitch). Im using ebusd 3.2 and latest config (online). Access level is set to *.
Even the writable values cannot really be modified, as below:
Here's my boiler's code:
And output of ebusctl find -V: