-
Notifications
You must be signed in to change notification settings - Fork 301
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
McxFlowTempDesired in HA vr71 #451
Comments
You need to change filter name to include Flow: |
This doesn't help and the filter-direction was already configured on that way. And also |
Changing the message type from 'w' to 'uw' (update-write) works for me (all filters disabled in mqtt-hassio.cfg):
|
What do you mean with |
@chrizzzp points to modify 26.vr_71.csv, because it show that sensors are only for write not for read. |
Message type is defined in the CSV. I use local CSVs and edited |
Should we use those files: |
As far as I understood they apply to ebusd version >24.x where the CSV files are generated from these source files. I haven't really looked into 24.x yet. So I still use ebusd version 23.x with local CSVs. But I'm quite sure this is possible also in version 24.x |
I think I need those generated files: https://ebus.github.io/mapping.html |
Are you sure you also changed the default message type to 'uw'? This is the local
|
WIth local CSVs you have to run ebusd with the option
If you use the HA ebusd addon you can define the local path in the configuration tab of the addon. Local files have to be in a location ebusd can access (important if you run it in a container like the HA ebusd addon does). |
I have the entities finally in HA. Thanks For support. |
I don't see any action to be taken as the mentioned vr71 is already part of the repo. |
A change from message type 'w' to 'uw' is requested for the following definitions of the
Explanation: when the type of the write messages is changed from |
How do I get those sensors in HA with the mqtt-hassio.cfg file?
And especially the McxFlowTempDesired values because the both SensorData sensors are there.
https://github.com/john30/ebusd-configuration/blob/master/ebusd-2.1.x/en/vaillant/26.vr_71.csv
The text was updated successfully, but these errors were encountered: