nliaudat / esp_canbus Goto Github PK

For hoval, the actual terminator resistor do not works.

https://github.com/nliaudat/esp_canbus/blob/main/esphome/components/toptronic/toptronic.cpp
line 194

uint32_t can_id = 0xF1E40801;

Is your feature request related to a problem? Please describe.
I have a HOVAL VMC with only the basic controller, not the TopTronic E controller. So I use an ESP with this component to control and monitor the VMC.
I would like also to monitor error codes from the VMC.

Describe the solution you'd like
If I understand well at the moment this is not possible because error info are spread across multiple bytes (15) so there isn't a data type that can contains all the information, so even creating a single sensor containing all the values is not possible.

The idea would be having different sensors (maybe a new sensor type?) were is possible to define start byte:

sensor:
- platform: toptronic
  name: Active error 1 appearance timestamp
  device_type: HV
  device_addr: ${TT_HV_addr}
  function_group: 0
  function_number: 0
  datapoint: 29042
  start_byte: 0
  id: HV_0_0_29042
  type: U32
- platform: toptronic
  name: Active error 1 disappear timestamp
  device_type: HV
  device_addr: ${TT_HV_addr}
  function_group: 0
  function_number: 4
  datapoint: 29042
  start_byte: 4
  id: HV_0_0_29042
  type: U32

I was not able to compile the config.

esphome compile config.yaml
INFO Reading configuration config.yaml...
WARNING GPIO4 is a Strapping PIN and should be avoided.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
Failed config

captive_portal: [source wifi.yaml:18]

  This feature is only available with frameworks ['arduino'].
  {}
web_server: [source config.yaml:41]

  This feature is only available with frameworks ['arduino'].
  port: 80
async_tcp: None
  {}
This feature is only available with frameworks ['arduino']

I changed the esp32 section to:

esp32:
  board: nodemcu-32s
  framework:
    type: arduino #arduino #esp-idf  not ready missing json and async_tcp
    version: recommended #latest

Now I was able to compile. Did not test yet if it's working.

Hey!

Thank you for sharing this awesome project.
I'm currently working on adapting it for a heat generator. (https://github.com/abichinger/esp_canbus)

I'm trying to figure out how the can id is composed and thought you might be able to help me with this.
chrishrb/hoval-gateway#11

Find a way to set
internal: true
in sensor if it's already on inputs.

The writable parameter could be the trick.

in sensors_LANG.yaml
the parameter internal: true must be add

- platform: toptronic
  name: Normal ventilation modulation
  device_type: HV
  device_addr: ${TT_HV_addr}
  function_group: 50
  function_number: 0
  datapoint: 40651
  id: HV_50_0_40651
  type: U8
  unit_of_measurement: '%'
  **_internal: true_**

inputs_LANG.yaml for notes

number:
- platform: toptronic
  name: Normal ventilation modulation
  device_type: HV
  device_addr: ${TT_HV_addr}
  function_group: 50
  function_number: 0
  datapoint: 40651
  id: HV_50_0_40651_set
  type: U8
  unit_of_measurement: '%'
  min_value: 15
  max_value: 100
  step: 1
  decimal: 0

What do you think about entity id's with a unique device identifier in it? With the current setup you get not so meaningful entity ids which makes it hard to find them in home assistant during dashboard or automation creation.

For example:

With the use of friendly_name or some other variable it would be easier to identify the sensors afterwards.

Did you already try the hoval_HV.yaml. Do you get data? Is there something I can help?

Trying to figure out how to retrieve U32 based high/low values such as these datapoints for a heat pump:

I know the data is reported to the displays on the unit, but I don't see them going over the CAN bus. I can only see the GET request data going over the wire:

19:22:57	[I]	[tt:230]	
[GET] Data: 0x01400a0159e1

Could it be that the response neither fit the SENSOR nor TEXTSENSOR format? Has anyone successfully read u32 based datapoints in an actual environment?