Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ebusd Config #427

Open
Bavop opened this issue Aug 10, 2024 · 1 comment
Open

Ebusd Config #427

Bavop opened this issue Aug 10, 2024 · 1 comment

Comments

@Bavop
Copy link

Bavop commented Aug 10, 2024

My grandfather has multiple vaillant systems, and when i attached the ebusd adapter and used the ebusd addon for homeassistant i got this in the mqtt broker :
image
all the recognised items are like the hc with only those 4 items. and all the others aren't recognised. Any idea how i can fix this ?

@JonesGW-MGD
Copy link

JonesGW-MGD commented Aug 15, 2024

Complex set-up!

Personally, I wouldn't start to trouble shoot from MQ, I think you need to start with the logs on start up - that will help you see what configuration files have been matched and loaded, and will also help you see clearly the master/slave address assignments. Or use ebusctl info command etc.

Without that it's hard to diagnose what is happening during the auto-configuration process.

I think though you're going to have to clone the online repository and make local adjustments.

From what I suspect, the 'RC C' devices are Room Zone Controllers - probably VR90/3 or similar? These should be symlinked in the repository for the addresses you have if they are not, you'd need to either copy/rename or better still create a symbolic link for each device.

Looks like there is a bunch of VR60/3 mixers (these should be correctly matched), auroMatics, (Again should get matched at the addresses you have), other solar components (might need to create files for addresses ed. and 12. )- again, there should be files in the repository for these devices, just not expected at the addresses configured in this property so you'll need to match/rename as above.

There are two further heat sources sitting behind VR32 bus extenders. This is done because you can't have multiple devices configured to address 08 which would be how they arrived by default. (It's odd to me though that a VR32 has been assigned address 08 - I would have thought that was unnecessary).

Addressing the VR32s is a bit more complex. You need to work out what device is behind each one, and then find the right file for that device and then rename it to be picked up against the VR32. So for example if there is a gas boiler behind the VR32 at address 18, you would find 08.bai.csv and rename/symlink to 18.v32.csv. There are some posts on this ebusd discussion forum on doing this. (Including changing the latency parameter on start-up)

I think you might be busy....!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants