Skip to content

Latest commit

 

History

History
73 lines (54 loc) · 2.35 KB

customization.md

File metadata and controls

73 lines (54 loc) · 2.35 KB
Raw

Customizing

The hart of this component is the parameter-definition file parameters.yaml. By changing the file, the behaviour is totally changed.

It has two sections:

1. Requests

This section defines the requests that should be issued to the logger each time the component does a parameter update. The list below was created for a DEYE 5kW inverter, and could be customized for other models that are not 100% compatible with this inverter.

requests:
  - start: 0x0003
    end:  0x000E
  - start: 0x003B
    end: 0x0070
  - start: 0x0096
    end: 0x00C3
  - start: 0x00f4
    end: 0x00f8

This block specifies that the component should issue three requests to the logger, the first one requesting parameters 0x0003 up to 0x000E, then a second request for parmeters 0x003B up to 0x0070, and the last for parameters 0x000f4 up to 0x00f8.

2. Parameters

This section defines the induvidual parameter definitions. For example:

parameters:
 - group: solar
   items: 
    - name: "PV1 Power"
      class: "power"
      uom: "W"
      scale: 1
      rule: 1
      registers: [0x00BA]
      icon: 'mdi:solar-power'

group

The group just groups parameters that belong together. The induvidual parameter-items has to be placed in a group. The items parameters contains the parameter definitions that belong in the group.

Parameter-item

(see) https://developers.home-assistant.io/docs/core/entity/

field description
name The name field of the home-assistant entity #
class The class field of the home-assistant entity #
uom The unit_of_measurement field of the home-assistant entity #
icon The icon field of the home-assistant entity #
The fields below define how the value from the logger is parsed
scale Scaling factor for the value read from the logger
rule Method to interpret the data from the logger ##
registers Array of register fields that comprises the value. If the value is placed in a number of registers, this array will contain more than one item.
lookup Defines a key-value pair for values where an integer maps to a string field

# (see) https://developers.home-assistant.io/docs/core/entity/

## The rule field specifies how to interpret the binary data.

  1. unsigned 16-bit value
  2. signed 16 bit value
  3. unsigned 32 bit value
  4. signed 32 bit value
  5. ascii value
  6. bit field