configuration isseu? #1435
Unanswered
dev-wouter
asked this question in
Q&A
Replies: 1 comment
-
It looks like there is no configuration file for your Vaillant heatpump, that's why it doesn't show any data. But it works correctly because it loads global values. try to search in discussion part of these get if someone try it with same heatpump as you. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
hi all,
a few weeks ago i purchased the 'EBUS to WiFi Adapter Module V6.3' to be able to control my Vaillant flexoTherm vwf 57 heatpump.
connection is made and it is connected to my wifi.
i followed the instruction of how to configure everything in Home assistant, but it seems that i cannot get values from my Ebus.
this is the configuration in Yaml for ebusD
scanconfig: true loglevel_all: notice mqtttopic: ebusd mqttint: /etc/ebusd/mqtt-hassio.cfg mqttjson: true mqtthost: core-mosquitto mqttport: 1883 network_device: 192.168.0.202:3335 mqttuser: mqtt_user mqttpass: XXXxxxxXXXXxxxxXXXX accesslevel: "*" mode: enh configpath: /config/ebusd/ebusd-2.1.x/en
this is the logging after i restarted the addon
> ebusd --foreground --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=mqtt_user --mqttpass=xxxxxxxXXXXxxxxx--scanconfig --mqttjson --configpath=/config/ebusd/ebusd-2.1.x/en --accesslevel=* --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=enh:192.168.0.202:3335 --log=all:notice 2025-01-09 18:30:13.771 [device notice] transport opened 2025-01-09 18:30:13.773 [main notice] ebusd 24.1.p20241110 started with broadcast scan on device: 192.168.0.202:3335, TCP, enhanced 2025-01-09 18:30:13.774 [bus notice] bus started with own address 31/36 2025-01-09 18:30:13.780 [device notice] reset 2025-01-09 18:30:13.780 [mqtt notice] connection established 2025-01-09 18:30:13.796 [bus notice] signal acquired 2025-01-09 18:30:23.775 [main notice] starting initial broadcast scan 2025-01-09 18:30:23.905 [update notice] sent write broadcast queryexistence QQ=31: 2025-01-09 18:31:33.907 [main notice] scan completed 1 time(s), check again 2025-01-09 18:32:24.115 [main notice] update check: revision 24.1 available, broadcast.csv: different version available, memory.csv: different version available 2025-01-09 18:32:44.115 [main notice] scan completed 2 time(s), check again 2025-01-09 18:33:54.116 [main notice] scan completed 3 time(s), check again 2025-01-09 18:35:04.117 [main notice] scan completed 4 time(s), check again 2025-01-09 18:36:14.119 [main notice] scan completed 5 time(s), check again 2025-01-09 18:37:24.120 [main notice] scan completed 6 time(s), end 2025-01-09 18:39:36.794 [bus notice] new master 03, master count 2 2025-01-09 19:17:55.001 [bus notice] max. symbols per second: 133 2025-01-09 19:17:56.005 [bus notice] max. symbols per second: 204 2025-01-09 19:17:57.031 [bus notice] max. symbols per second: 224
this is logging from the mosquitto broker
[18:22:45] INFO: Service restart after closing s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped 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 cont-init: info: running /etc/cont-init.d/mosquitto.sh [19:22:51] INFO: SSL is not enabled cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0 cont-init: info: running /etc/cont-init.d/nginx.sh cont-init: info: /etc/cont-init.d/nginx.sh exited 0 s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting services-up: info: copying legacy longrun mosquitto (no readiness notification) services-up: info: copying legacy longrun nginx (no readiness notification) [19:22:51] INFO: Starting NGINX for authentication handling... s6-rc: info: service legacy-services successfully started [19:22:52] INFO: Starting mosquitto MQTT broker... 2025-01-09 19:22:52: Warning: Mosquitto should not be run as root/administrator. 2025-01-09 19:22:52: mosquitto version 2.0.18 starting 2025-01-09 19:22:52: Config loaded from /etc/mosquitto/mosquitto.conf. 2025-01-09 19:22:52: Loading plugin: /usr/share/mosquitto/go-auth.so 2025-01-09 19:22:52: ├── Username/password checking enabled. 2025-01-09 19:22:52: ├── TLS-PSK checking enabled. 2025-01-09 19:22:52: └── Extended authentication not enabled. 2025-01-09 19:22:52: Opening ipv4 listen socket on port 1883. 2025-01-09 19:22:52: Opening ipv6 listen socket on port 1883. 2025-01-09 19:22:52: Opening websockets listen socket on port 1884. 2025-01-09 19:22:52: mosquitto version 2.0.18 running 2025-01-09 19:22:52: New connection from ::1:37526 on port 1883. 2025-01-09 19:22:52: Client <unknown> disconnected due to protocol error. [19:22:52] INFO: Successfully send discovery information to Home Assistant. [19:22:52] INFO: Successfully send service information to the Supervisor. 2025-01-09 19:22:55: New connection from 172.30.32.1:46539 on port 1883. 2025-01-09 19:22:55: New client connected from 172.30.32.1:46539 as 65PC92IJ48gpLhkErgaOkw (p2, c1, k60, u'mqtt_user'). 2025-01-09 19:23:07: New connection from 172.30.33.1:50280 on port 1883. 2025-01-09 19:23:07: New client connected from 172.30.33.1:50280 as ebusd_24.1_279 (p1, c1, k60, u'mqtt_user').
with mqtt explorer i also dont get a lot of data
is there somebody with an idea what i did wrong? i can provide more data if requested.
Beta Was this translation helpful? Give feedback.
All reactions