-
-
Notifications
You must be signed in to change notification settings - Fork 137
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
MQTT: PrEnergyCountHwc1 and PrEnergyCountHc1 unit of measurement are not sent in definition. #643
Comments
I apologize. In a deeper analysis I discovered the field in configuration files didn't have the unit specified. I updated it and started working :) |
But should it really be Wh? Ive been comparing my PrEnergyCountHc and PrEnergyCountHwc readings with kWh usage readings from my gas meter and the numbers differ considerably. |
At least for my boiler is in Wh. Later on HA energy dashboard are converted to kWh. |
Out of curiosity, which boiler model is that? |
Its a Saunier Duval Semia Condens: address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0705;HW=1303", loaded "vaillant/bai.308523.inc", "vaillant/08.bai.csv" |
Thanks. And how did you fixed this?
|
in the configuration files:
|
@Tugado do you have sensible values? |
That correct values and need to be recalculate to m3.
|
I understand. So the unit is "unusual" and we have to use a converter. It is also not kcal or GJ etc. Maybe this should not be reported as energy by ebusd? Maybe it should be a counter, for example? Entity sensor.ebusd_bai_ebusd_bai_prenergysumhc2 (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'None' which is not a valid unit for the device class ('energy') it is using; expected one of ['kcal', 'kWh', 'Mcal', 'J', 'MWh', 'GJ', 'MJ', 'Gcal', 'kJ', 'cal', 'Wh']; ps. But the first value is definitely wrong - the counter is overclocked - I have to reset it to zero. |
It is energy but multiplicator depends on fuel you use. Most of the time it is shown in invoice from energy company (In my case Gas company, because I use CNG as energy source). |
Do you see "5434.0 " on your invoice? |
It is constant for CNG in my location to convert Energy amount obtained in m3 of it. And that calculated value I use to show consumption of gas in HA. |
If a few people could post their gas caloric value (it is on the gas bill at least here in the uk) and their ratio of PrEnergyCountHc/gas usage then we could figure it out |
But what does "constant for CNG in my location" mean? If the Vaillant shows some number, and we have to find a divisor to calculate one of these values, then it is not energy. It is a counter of "something". And for each Vaillant it is different. In my opinion, all PrEnergy* should be counter (energy, but counter) |
I found also (polish page):
This is totally different fo HC and HWC. And it is not close 5434.0 |
Yes, but it could be our gas company specific that they show it. |
Yeah |
How is that data meant to be used? Ie are any Vailant devices showing gas usage from data on eBus?
|
At least in my case it is the energy in Wh and you can get it to m3 with a conversion factor. This conversion ratio is published in my provider site. |
Lucky You :) I will try check my multiplier. It should be about 250. |
Do you get the same data with the energy count fields? I use the prenergycount instead of the prenergysum to make the comparison. |
PrEnergySum is sensor created by my. It is based on PrEnergyCount ( |
My HWC count is about 11 000 000 |
Description
I changed ebusd configuration to work with default mqtt-hassio.cfg and Home Assistant discovery and realized that PrEnergyCountHwc1 and PrEnergyCountHc have no unit on their definition.
Is there any way to force the unit to be passed in the definition-payload?
Actual behavior
Expected behavior
{
"unique_id": "ebusd_bai_PrEnergyCountHc1_0",
"name": "ebusd bai PrEnergyCountHc1 ",
"device": {
"identifiers": "ebusd_bai",
"manufacturer": "ebusd.eu",
"name": "ebusd bai",
"via_device": "ebusd",
"sw_version": "22.3",
"suggested_area": "Heating"
},
"value_template": "{{value_json["0"].value}}",
"state_topic": "ebusd/bai/PrEnergyCountHc1",
"state_class": "total_increasing",
"device_class": "energy",
"unit_of_measurement": "Wh"
}
ebusd version
22.3
ebusd arguments
EBUSD_OPTS="--scanconfig --configpath=/etc/ebusd/ --mqttport=1883 --mqtthost=192.168.2.1 --mqttuser=user --mqttpass=pw --lograwdatafile=/var/log/ebusd.log --mqttverbose --latency=20000 --accesslevel="*" --mqttjson --mqttint=/etc/ebusd/mqtt-hassio.cfg --pollinterval=2"
Operating system
Debian 11 (Bullseye) / Raspbian 11 / Ubuntu 20-21
CPU architecture
arm64
Dockerized
No response
Hardware interface
adapter 3 USB
Related integration
No response
Logs
type_switch-number =
sensor,temperature,measurement = temp|,°C$
sensor,power_factor,measurement = power*%%
sensor,power,measurement = power|,kW$|,W$
sensor,voltage,measurement = volt|,V$
sensor,current,measurement = current,|,A$
sensor,energy,total_increasing = energy|,Wh$
sensor,yield,total_increasing = total*,Wh$
sensor,,total_increasing = hours|,h$
sensor,,total_increasing = starts*,$
sensor,pressure,measurement = bar$
sensor,gas,measurement = gas*/min$
sensor,humidity,measurement = humid*%%$
sensor,, =
The text was updated successfully, but these errors were encountered: