Hi Peter,
thanks for your fast reply. The listet entities is exactly what I’m missing.
For the sake of clarification here my snip from configuration.yaml:
modbus:
- name: E3DC
type: tcp
host: 192.168.99.70
port: 502
sensors:
- platform: modbus
scan_interval: 10
registers:- name: E3DC_solar_power
slave: 1
unit_of_measurement: W
register: 40068
hub: e3dc
device_class: power - name: E3DC_battery_power
slave: 1
unit_of_measurement: W
register: 40070
hub: e3dc
device_class: power - name: E3DC_battery_soc
slave: 1
unit_of_measurement: ‘%’
register: 40083
data_type: uint
hub: e3dc
device_class: battery - name: E3DC_power_consumption
slave: 1
unit_of_measurement: W
register: 40072
hub: e3dc
device_class: power - name: E3DC_grid_power
slave: 1
unit_of_measurement: W
register: 40074
hub: e3dc
device_class: power - name: E3DC_emergency_power_state
slave: 1
data_type: uint
register: 40084
hub: e3dc - name: E3DC_EMS_state
slave: 1
data_type: uint
register: 40085
hub: e3dc - name: E3DC_autarky_and_consumption
slave: 1
data_type: uint
register: 40082
hub: e3dc
- name: E3DC_solar_power
- platform: template
sensors:
e3dc_autarky:
friendly_name: ‘E3DC Autarky’
unit_of_measurement: ‘%’
value_template: “{{ (states(‘sensor.e3dc_autarky_and_consumption’)|int / 256)|round(0,‘floor’) }}”
e3dc_own_consumption:
friendly_name: ‘E3DC Own Consumption ratio’
unit_of_measurement: ‘%’
value_template: “{{ ((states(‘sensor.e3dc_autarky_and_consumption’)|int / 256 - states(‘sensor.e3dc_autarky’)|int) * 256)|round(0,‘floor’) }}”
binary_sensor:
- platform: template
sensors:
e3dc_emergency_power_available:
friendly_name: “E3DC Emergency Power available”
value_template: “{{ states(‘sensor.e3dc_ems_state’)|int|bitwise_and(4) > 0 }}”
e3dc_battery_loading_blocked:
friendly_name: “E3DC Battery loading blocked”
value_template: “{{ states(‘sensor.e3dc_ems_state’)|int|bitwise_and(1) > 0 }}”
e3dc_battery_unloading_blocked:
friendly_name: “E3DC Battery unloading blocked”
value_template: “{{ states(‘sensor.e3dc_ems_state’)|int|bitwise_and(2) > 0 }}”
e3dc_weather_based_loading:
friendly_name: “E3DC weather based loading limiter”
value_template: “{{ states(‘sensor.e3dc_ems_state’)|int|bitwise_and(8) > 0 }}”
e3dc_power_limiter:
friendly_name: “E3DC power limiter”
value_template: “{{ states(‘sensor.e3dc_ems_state’)|int|bitwise_and(16) > 0 }}”
e3dc_smartcharge_loading_blocked:
friendly_name: “E3DC SmartCharge loading blocked”
value_template: “{{ states(‘sensor.e3dc_ems_state’)|int|bitwise_and(32) > 0 }}”
e3dc_smartcharge_unloading_blocked:
friendly_name: “E3DC SmartCharge unloading blocked”
value_template: “{{ states(‘sensor.e3dc_ems_state’)|int|bitwise_and(64) > 0 }}”
So, pretty much like listet here in the forum. Have tried both the original register addresses as listed above and the ones with -1 offset.
Absolutely no idea, why the register-based entities (sensors) do not show up. Have a likewise config for some of the values in node red (implemented by my more capable son) and there the registers show their values.
What I’d expect/like to see as entities are the usual suspects arising form the sensor definitions in the second section. What would be a bonus add-on are the wallbox values - but that is nice to have. The core stuff is my personal must have as I not only want to visualize and store the values but also want to be able to kick off my washer, dryer etc based on E3/DC states/values.
I am like a small brown coated animal running through the forrest not seing nothing …
Thanks.
