No writable entities in Homeassistant #1384
Comments
|
check the discovery messages sent to HA using e.g. |
|
Same for me, I have a vaillant that is recognised as bai 08.
|
|
did you add the writable direction to the filter? and was that escaped correctly (as the pipe symbol is special at least on the command line)? |
Hi! I have a 0010019985 Vaillant As soon as I have some free time I would like to try to understand if one of the specific ones for other models is suitable for my boiler Thanks for your project! |
|
You are some steps ahead of me (using a 10021924 ) :) I'm currently at the same point not exactly knowing how to determine infos for creating a special file. |
|
@mansellrace - many us are able to write values even using the default bai file (bai308523.inc) and the associated controller devices - so I suspect it's not an actual 'issue' with the ebusd application or the configuration files, but perhaps your set-up? You might find if you raise a discussion item rather than an issue you get some help - I'd be happy to share my experience for example. (Some of which I documented here to write values as mundane as MaintenanceDate and as useful as HeatCurve using ebusd and HA 'out of the box') |
Seems like there are only sensors and binary sensors, se below. I'm really stuck here, arguments seem to be valid, which is reflected in startup logs I've also cloned config locally and uncommented but still no luck! here is mqtt output |
|
if you're using supervised addon, why do you start ebusd in foreground in the first place? this would interfere with another running instance i guess, so please check that |
This was the logs from supervised addon, so I don't start ebusd by myself anywhere |
|
did you change anything else in the mqtt.cfg file used? maybe just post it here, so we're on the same page |
|
Hello, I have exactly the same situation, tried different things: filter-direction in HA UI, copy and edit mqtt-hassio.cfg nothing helped. Last time I tried in my bai config file for few line change type from "wi" to "w" and that line with "w" type was discovered by HA as writable and writing functionality is working. I need to search more about difference in type definition as I'm completely beginner in ebus. |
|
If change from "wi" to "w" works for you you need to add |
|
My ebusd already have that: and it doesn't work. |
|
maybe HA did not update the discovery info. try to remove a particular entity in HA that is supposed to be wi writable and restart ebusd to force push the defs. maybe also check what is sent to discovery on mqtt to be sure |
|
I did all that already even completely remove ebusd devices from HA and reinstalling ebusd addon. Nothing helps. MQTT Explorer shows that HA showing correctly what MQTT config messages are send by ebusd. In my system config messages for "wi" are created differently than for "w" so I'm trying to understand source code which doing that. |
|
After some investigation it is even more complicated. If i have message defined as "wi" non of them is shown as writable in HA. When I changed 2 the most interesting for me from "wi" to "w" they both shows as writable (based on that were my last comments). But when I change all "wi" to "w" only 2 more become writable (from 11 "w" messages). All are visible in HA but only 4 writable My bai config Writable are HwcTempMax, HeatCurve, FlowsetHcMax, FlowsetHwcMax |
|
It is connected with unit |
|
then your filters in mqtt-hassio.cfg exclude it. when you want to have messages with access level available, you need to set up ACL |
|
About filter in mqtt-hassio.cfg. I assume the problem is with For the comment about ACL. I assume it is about "w" and "wi" difference. I was assuming |
|
did you try with accesslevel "*"? |
|
As above log shows I'm starting it with |
|
I have a smiliar issue with 08.bai - able to see many sensors but no controls. (i have tried variations on the payload such as in a json) ebusd tells me: I followed JonesGW-MGD guide as closely as I could in a docker instance for HA but got nowhere. I appreciate any feedback on this as I cannot seem to get anywhere! TIA Info: docker configebusd: HA configebusd: ebusctl infoversion: ebusd 24.1.24.1 |
|
Hi @AbsurdSyssie - if you take a couple of steps back - have you tried issuing a write command directly from It's a slightly different question but what is your use-case for setting ebusd is an immensely powerful tool but you really want to avoid 'fighting Vaillant' - by which I mean (and it will depend on your particular configuration) - if I tried to do this, I'd be overriding the weather-compensation features - My boiler takes the outside temp, feeds that and the desired room / zone temp to a heat curve and determine the flow temp. I really don't want to be messing with this. Even if you don't have weather comp - your controller will likely be telling the boiler what to set the desired flow temp to. And it will do this all the time - like every so many minutes (opinions vary) by using the 'SetMode' command so if you want to override the controller, you need to 'flood' the ebus more frequently with your settings. Even if your controller is totally 'dumb' like a non-Vaillant control, (Hive / Nest, etc.) that is basically powering the boiler on/off - it's still possible that you'll need to continuously 'instruct' the boiler. |
|
Wow that was fast! Thanks for your response. I have tried: I've tried adding My desire to change flowtempdesired is that it is the value which changes when I change a dial on my boiler, and is the only writable value from 08.bai.csv that I can understand. I can't see any values like 'targetroomtemp' or burner controls etc. My real use case for an ebus shield was to be able to use it as a smart thermostat that I could control through HA - set a desired room temp, use my thermometers around the house to inform the boiler as to when to turn off, set the modulation etc. I currently have a vaillant thermostat attached which is an old style one with little in the way of customisation. I tried capturing the values it sends and replicating those but no joy. I have tested the commands with and without the thermostat attached. |
|
@AbsurdSyssie - when ebusd starts - can you confirm what bai file it loads? (just run - Also do you know the Valliant model number for your thermostat? |
The thermostat is a The boiler is a Edit - turned the shield back on and pinged again |
|
@AbsurdSyssie - so you're loading the boiler message file bai.308523.inc which one could regard as the 'default' file if no other more specific file is discovered based on your boiler product ID, SW and HW versions etc. If I assume, because you are on version 24.1, you are taking your message definitions from the new repository here - https://github.com/eBUS/ebus.github.io/blob/main/en/vaillant/bai.308523.inc Then, line 16 of this file is:
so it's set currently as not writable. ( you now have some options depending on your appetite! (but if you replicate the files locally - set a --configpath to point to these, you can then experiment with making them writeable for example.) (Even so, at some point you may need to disconnect the VRT50 because that is relaying a room temp that the boiler is then translating into a flow temp. Ultimately you will effectively need to emulate a '15 address' (controller) type device from HA - it's possible - and you can search this discussion forum for 'emulate controller' or 'replace controller' for people that have achieved this. To test - you could (assuming you start ebusd with this additional parameter:
Again - not really the purpose of ebusd I suspect people would tell you!) |
|
I see, thanks a lot! I have had a look at bai.308523.inc and I can see a couple of values for AC/DC thermostats. I am assuming I would send an MQTT message /ebusd/bai/DCthermostat payload 1 Will let you know how it goes! I am very appreciative of your help! edit - whilst my wall thermostat is asking for heat; Confusing as this thermostat only gets power from the PCB of the boiler. I will remove it and see if I can write the value to 1. edit 2 These seem innocuous enough to set to write and see what happens. |
|
Thanks for all your help again JonesGW. Could I quickly ask about how one goes about using the setmode command, I can't find any comprehensive guide on it. ebusctl logs look like this when the VRT is on; The MQTT broker sees this; |
Description
I run ebusd as an addon in Supervised HA, and it can discover my Vaillant boiler and bunch of sensors, but there is no writable entities for my boiler, even though I added
to the config
Actual behavior
A lot of sensors are successfully displayed on the main page of HA, however there is nothing I can write to.
Expected behavior
Some writable entities should be presented
ebusd version
current source from git
ebusd arguments
--foreground --mqtthost=192.168.50.87 --mqttport=1883 --mqttuser=ebusd --mqttpass=ebusd --scanconfig --mqttjson --configpath=/config/ebusd-configuration/latest/en/ --mqttint=/config/ebusd-configuration/latest/en/mqtt.cfg --mqtttopic=ebusd --device=enh:192.168.50.106:9999 --log=all:notice --log=main:notice --log=bus:notice --log=update:notice --log=network:notice --log=other:notice --mqttvar=filter-direction=r|u|^w
Operating system
Debian 12 (Bookworm) / Ubuntu 22-23 / Raspberry Pi OS 12 (including lite)
CPU architecture
x64
Dockerized
same as ebusd version
Hardware interface
Adapter Shield v5 via Ethernet
Related integration
MQTT Home Assistant via mqtt-hassio.cfg
Logs
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
The text was updated successfully, but these errors were encountered: