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 |
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: