Missing number entity for Hc1HeatCurve in Home Assistant

[Malfed]

Thanks to #1177 I was able to write values from Home Assistant using ebusd to my Vaillant. It's working really well for most of the entities, but I'm missing a number entity for Hc1HeatCurve to change it's value using the UI.

Let's take Hc1MinFlowTempDesired as an example. I've got a number entity for it:

I can change that value using the Home Assistant UI. It's working.

Now, there's Hc1HeatCurve. I've also got an entity for it, but it's a sensor:

Because it's a sensor, I cannot change it's value in Home Assistant UI. Looking at the CSV I'd say both are writable:

When using mqtt I can also change it's value:

So overall I'd say that it's working, but it's only missing the correct entity in Home Assistant to be editable using the UI. I've read through several issues and stumbled upon the discovery messages sent to HA (mosquitto_sub -v -t 'homeassistant/#'), so I took at look at them:

 homeassistant/sensor/ebusd_700_Hc1HeatCurve_0/config {
    "unique_id":"ebusd_700_Hc1HeatCurve_0",
    "name":"ebusd 700 Hc1HeatCurve ",
    "device":{
     "identifiers":"ebusd_700",
     "manufacturer":"ebusd.eu",
     "name":"ebusd 700",
     "via_device":"ebusd",
     "sw_version":"23.2",
     "suggested_area":"Heating"
    },
    "value_template":"{{value_json[\"0\"].value}}",
    "state_topic":"ebusd/700/Hc1HeatCurve"
   }

Comparing this to other messages I noticed that command_topic is missing. For the example Hc1MinFlowTempDesired command_topic exists:

  homeassistant/number/ebusd_700_Hc1MinFlowTempDesired_tempv/config {
    "unique_id":"ebusd_700_Hc1MinFlowTempDesired_tempv",
    "name":"ebusd 700 Hc1MinFlowTempDesired tempv",
    "device":{
     "identifiers":"ebusd_700",
     "manufacturer":"ebusd.eu",
     "name":"ebusd 700",
     "via_device":"ebusd",
     "sw_version":"23.2",
     "suggested_area":"Heating"
    },
    "value_template":"{{value_json[\"tempv\"].value}}",
    "state_topic":"ebusd/700/Hc1MinFlowTempDesired",
    "command_topic":"ebusd/700/Hc1MinFlowTempDesired/set",
    "unit_of_measurement":"┬░C",
    "device_class":"temperature"
   }

This is probably the reason why the entity is not writable from Home Assistant. Now I'm wondering why. Is this a bug? Is this on purpose?

[Koky05]

You can add it by modify file mqrr-hassio.cfg:
Into section type_switch-w-number add:

type_switch-w-number =
    number,heating curve, = curve*%%
    number,heating curve, = Curve*%%

Into section type_switch-number add:

type_switch-number =
    sensor,heating curve,measurement = curve
    sensor,heating curve,measurement = Curve

[Malfed]

Thanks! That changed it from a sensor to a number.

Just out of curiosity - how would I undo this? I added this to the file /etc/ebusd/mqtt-hassio.cfg in the container (though I thought that these changes are not persistent). I restarted the addon and the sensor changed to a number. Now, after restarting Home Assistant and the addon again, the file is reset to default (as I expected), so my added lines are no longer there - but the change is still working?! It's still a number, not a sensor. I even deleted the entity, but it's added as a number again. Overall, that's ok, but I still wonder why that is?

[Koky05]

The definition of value is located in type_switch-**number** if you want to have it as string it should be defined in different part of mqtt-hassio.cfg. If you look into MQTT messages you will find two part one for sensor definition and one with values it self. Only values are refreshed after HA restart. Sensor definition are loaded on eBusd restart when it load all configuration files for eBusd, I can be wrong but these is my observation.

[sebska]

Hi there,

i have one question:
could you give me a 'idiot guide' to: "how can i see my discovery messages?". I have some issues between EBusD an HA.

Within HA I habe the "MQTT Explorer", where I can see all my things I need (with polling) coming in. Other things are #-tagged in the csv as I do not need them (now).

But some of the Topics (like 'EBusD/ctlv2/z1HolidayStartDate') are not in HA at all. Possibly that Time ands Date are not configured in mqtt-hassio.cfg?

Other Topics ( 'EBusD/ctlv2/z1QuickVetoDuration') are visible but not writable.
BUT: With a Putty-Console with tcp-command: w -c ctlv2 z1QuickVetoDuration 1.0 this is possible to write it. But It takes a while to see the change with TCP or within HA (abaout 30 sec.)
Within the csv it is like this:
r1;w,,z1QuickVetoDuration,Duration of Quick Veto mode in Hours Zone 1,,,,2600,,,EXP,,,valid values are 0.5-12 in 0.5 increments (default 3) writing enables quick veto mode

I have switched the mqtt-hassio.cfg to write an with some temperatures it works.

Youd you help me please?

Regards

Sebastian