Integration of heatpump as a separate service?

[BeneWilh]

Hi @freakent, thank you for sharing your scrpts for venus os. Would you be able and willing to add some additional devices such as heatpump in your scripts?

For the time beeing I am using a third EVCharger to show the values on VRM... but as values are summed up its not that nice.
Thank you!

[freakent]

Hi,

I'm always happy to discuss and to investigate feasibility. In this case the config for Heat Pumps looks relatively straignt forward.
https://github.com/victronenergy/venus/wiki/dbus#heatpump

As usual it comes down to what 3rd party device you are trying to integrate and whether the data it provides maps to what Victron supports in their dbus interface (see the link above).

You could try adding the following lines to your services.yml file, reboot, then try publishing over mqtt a registration message for a heat pump device. Check the dbus-mqtt-devices log file as per the troubleshooting instructions in the README. If it registers OK, then try sending some data attriibutes using the device id.

# hhttps://github.com/victronenergy/venus/wiki/dbus#heatpump
heatpump:
  ProductId:
    default: 65535 # 0xFFFF
  CustomName:
    default: "My Heat Pump"
    persist: true
  State:
    description: "State of heat pump (enum to be decided later)"
  Temperature:
    description: "Current water temperature (optional if no temperature reading available)"
  TargetTemperature:
    description: "Target water temperature (optional if not available)"
  Ac/Power:
    description: "Power currently consumed"
  Ac/Energy/Forward:
    description: "Total energy consumed"

I am having to guess the the dbus identifier for this is com.victronenergy.heatpump, as Victron have not included it in their documentation.

[freakent]

You mean the hp1? That makes no difference so long as it's unique.

What does the dbus-mqtt-devices log look like?

[BeneWilh]

I mean the fe003

@4000000067683d4f377bba4c INFO:device_manager:Received device status message {'clientId': 'fe003', 'connected': 1, 'version': '1.0', 'services': {'hp1': 'heatpump'}}
@4000000067683d4f37834fb4 INFO:device:**** Registering device: fe003, services: {'hp1': 'heatpump'} ****
@4000000067683d4f378883bc INFO:device:Registering Service heatpump for client fe003
@4000000067683d4f378de2bc INFO:device_service_config:About to open config file
@4000000067683d501b8f2b0c INFO:device_service:Registering service heatpump for client fe003 at path com.victronenergy.heatpump.mqtt_fe003_hp1
@4000000067683d501d1814fc INFO:settingsdevice:Setting /Settings/Devices/mqtt_fe003_hp1/ClassAndVrmInstance does not exist yet or must be adjusted
@4000000067683d50209437b4 WARNING:vedbus:USING OUTDATED REGISTRATION METHOD!
@4000000067683d50209ce274 WARNING:vedbus:Please set register=False, then call the register method after adding all mandatory paths. See https://github.com/victronenergy/venus/wiki/dbus-api
@4000000067683d5020fd3a84 INFO:vedbus:registered ourselves on D-Bus as com.victronenergy.heatpump.mqtt_fe003_hp1
@4000000067683d5021501d44 INFO:device_service:Registered Service com.victronenergy.heatpump.mqtt_fe003_hp1 under DeviceInstance 1
@4000000067683d50217836e4 INFO:device_manager:publish {'portalId': 'd83xxxxxxxxxx', 'deviceInstance': {'hp1': 1}, 'topicPath': {'hp1': {'N': 'N/d83xxxxxxxxxx/heatpump/1', 'R': 'R/d83xxxxxxxxxx/heatpump/1', 'W': 'W/d83xxxxxxxxxx/heatpump/1'}}} to device/fe003/DBus, status is 0

[freakent]

fe03 doesn't have a special meaning, it's just any name you want to call your sensing device. It make's me smile to see people use "fe" as that's the initials of my domain, no more than that.

Log file looks OK.

Now that the device is registered try sending a Temperature value.

[BeneWilh]

so I did, but the data on the platfrom (neither v1 nor v2) do not show the temperature

[freakent]

Can you add Temperature to a custom chart in VRM?

[19grad]

Yes its possible to add custom chart in VRM
With all 4 parameters

At the moment i only use the Ac/Power parameter, and it works fine
But i think the heatpump implementation and documentation from victron is not complet jet

[BeneWilh]

but it's not visible at the main Dashoard

only the 2 Wallboxes...

[freakent]

OK, well it looks like those settings for the driver are correct but that support in Victron's dashboard is lacking. Not much more we can do currently.