Just managed to find KIOSK try this: Click Home and select LIST VIEW
Then select your plant:
and you should see KIOSK
Please note that if you have the installer account it will not display the Kiosk login. My advise is to create another acconunt for example owner privilege.
yes thanks that was what i just found out myself. the company from who i bought the system set it up for me. thats why i can’t see the kiosk button. Thanks
1 Like
Hello, I have set up connection to inverter sun2000_8ktl_m0 via LAN cable connected to Dongle (V100R001C00SPC123).
But in HomeAssistant logs i found a lot of warnings with delay of updating data from inverter.
2021-09-24 10:34:07 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sun2000_8ktl_m0 is taking over 10 seconds
2021-09-24 10:34:37 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sun2000_8ktl_m0 is taking over 10 seconds
2021-09-24 10:35:07 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sun2000_8ktl_m0 is taking over 10 seconds
2021-09-24 10:35:27 WARNING (MainThread) [homeassistant.components.sensor] Updating huawei_solar sensor took longer than the scheduled update interval 0:00:30
2021-09-24 10:36:07 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sun2000_8ktl_m0 is taking over 10 seconds
2021-09-24 10:36:37 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sun2000_8ktl_m0 is taking over 10 seconds
2021-09-24 10:37:07 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sun2000_8ktl_m0 is taking over 10 seconds
2021-09-24 10:37:25 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook c75d220bac1cc8a5a93427af753e7ef95c42c1100880d502d211bd329e4baae4 from 77.65.48.234
2021-09-24 10:37:26 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook c75d220bac1cc8a5a93427af753e7ef95c42c1100880d502d211bd329e4baae4 from 77.65.48.234
2021-09-24 10:37:27 WARNING (MainThread) [homeassistant.components.sensor] Updating huawei_solar sensor took longer than the scheduled update interval 0:00:30
2021-09-24 10:38:07 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sun2000_8ktl_m0 is taking over 10 seconds
2021-09-24 10:38:37 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sun2000_8ktl_m0 is taking over 10 seconds
2021-09-24 10:39:07 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sun2000_8ktl_m0 is taking over 10 seconds
Maybe someone had a similar problem and can help me?
There is a battery in your integration and I want to have the amount of energy produced and I don’t want to show it in the entity list
You want to see how mutch you have charged in one day correct?
- platform: template
sensors:
storage_current_day_charge_capacity:
friendly_name: “luna storage day charge capacity”
#entity_id: sensor.sun2000_6ktl_l1
unit_of_measurement: ‘KW’
icon_template: mdi:solar-power
value_template: “{{ state_attr(‘sensor.sun2000_6ktl_l1’, ‘storage_current_day_charge_capacity’) }}”
I do not have a battery in my installation. I want to add to the energy panel the production items from solar panels
check the posts of yousaf465 user … i was not able yet to make it working either
just add total_yield as a sensor in the energy dashboard.
- configuration
- Scroll down to Customizations
- select your entity
- select device class as “energy”
- select state class as " total increasing"
- Select other
- Attribute name “last_reset”.
8 attribute value “1970-01-01T00:00:00+00:00” - click save
- Now your sensor will show up in energy dashboard.
what values you see in developers tools sensor.sun2000_xxktl_xx?
Energy dashboard has its uses but Grafana is still the king
found the error for daily yield. Fixed.
I had fixed the value of daily yield in sensor customization at 15.6KWh. Now it is free floating. 
Hello…
I have direct Modbus connection with land cable
The connection seems to be very stable.
And I gave full functionality with sensors… And energy too (no battery)
But… Sometimes… Without any regularity…
It shows unavailable…
And I can’t understand why…
My HA log has this error…
Can anyone understand it?
And help me to solve it?
Regards…
Logger: homeassistant.components.modbus.modbus
Source: components/modbus/modbus.py:250
Integration: Modbus (documentation, issues)
First occurred: 23 de setembro de 2021 23:57:54 (15 occurrences)
Last logged: 21:20:03
Pymodbus: Solar: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
Pymodbus: Solar: Exception Response(131, 3, SlaveFailure)
my modbus code
modbus:
- name: Solar
type: tcp
close_comm_on_error: false
host: 192.168.1.76
port: 502
delay: 2
timeout: 15
sensors:
- name: Solar SunPower
slave: 1
address: 32080
unit_of_measurement: W
data_type: int32
count: 2
scale: 1
precision: 0
scan_interval: 1
- name: Solar GridPower
slave: 1
address: 37113
unit_of_measurement: W
data_type: int32
count: 2
scale: 1
precision: 0
scan_interval: 1
- name: Solar Inversor Temperatura
slave: 1
address: 32087
unit_of_measurement: ºC
data_type: int
count: 1
scale: 0.1
precision: 0
scan_interval: 60
- name: Solar Produção do Dia
slave: 1
address: 32114
unit_of_measurement: kWh
data_type: uint32
count: 2
scale: 0.01
precision: 2
scan_interval: 60
- name: Solar Produção Total
slave: 1
address: 32106
unit_of_measurement: kWh
data_type: uint32
count: 2
scale: 0.01
precision: 2
scan_interval: 120
- name: Solar Grid_OUT Total
slave: 1
address: 37119
unit_of_measurement: kWh
data_type: int32
count: 2
scale: 0.01
precision: 2
scan_interval: 120
- name: Solar Grid_IN Total
slave: 1
address: 37121
unit_of_measurement: kWh
data_type: uint32
count: 2
scale: 0.01
precision: 2
scan_interval: 120
Hi guys,
I am new here, Have been playing around with this super awesome integration for a couple day.
May i ask how can i create a sensor for inverter startup and shutdown time with the full format like
Inverter startup time: “2021-09-26T23:16:02+00:00” and add +7hour due to GMT+7 time to
“2021-09-27T06:16:02+00:00” and sorry for my bad English.
P.S. Thanks a lot for you guys hard work! It’s pretty amazing what has been done so far!
if you change state class to
state_class: total_increasing
in /config/customize.yaml file it will be fixed. this is for 2021.9.x and above.
here is my customize.yaml file
sensor.sun2000_10ktl_m1:
device_class: energy
state_class: measurement
sensor.pv_daily_yield:
unit_of_measurement: kWh
device_class: energy
state_class: total_increasing
sensor.pv_active_power:
state_class: measurement
device_class: power
last_reset: '1970-01-01T00:00:00+00:00'
sensor.grid_exported_energy:
device_class: energy
state_class: total_increasing
sensor.pv_total_yield:
device_class: energy
state_class: total_increasing
sensor.energy_used_by_house:
device_class: energy
state_class: total_increasing
Does anyone have a similar reading case, it disrupts my monthly and annual readings, but not the total. It turns out that the error comes from pv_string_01_voltage
- platform: template
sensors:
pv_string_01_power:
friendly_name: "Huawei PV String 01 Power"
unit_of_measurement: "W"
device_class: energy
icon_template: mdi:solar-power
value_template: '{{ (states("sensor.pv_string_01_voltage")|float * states("sensor.pv_string_01_current")|float * 1) | round(0) }}'
Can such readings be avoided? What could it be from?
Calibration of the utility meter helps, but until the next wrong reading
I’m also getting wrong readings, that’s why I stopped using smart dongle and I’m connecting again to internal wifi AP. With internal AP I had never got any wrong readings.
1 Like
It turns out, however, that it remains to return to the topic of the router as a gateway via wifi or use the kiosk option
You can also modify template to accept only values between some range:
pv_strin1_voltage:
friendly_name: "Napiecie string 1"
unit_of_measurement: 'V'
value_template: >
{% if state_attr('sensor.sun2000_8ktl_m0', 'pv_string_01_voltage') | float > 0 and state_attr('sensor.sun2000_8ktl_m0', 'pv_string_01_voltage')|float < 500 %}
{{ state_attr('sensor.sun2000_8ktl_m0', 'pv_string_01_voltage') }}
{% else %}
0
{% endif %}
Piszę z głowy więc nie jestem pewien czy składnia poprawnie.
In a my old configuration I had similar issue on an utility meter sensor based to template. This happened at HA restart.
I am not an expert but maybe it could be caused to the temporary unavailablity values of some sensor included into the template.
@ligeza which values you use in energy dashboard? Energy Management in Home Assistant - #929 by yousaf465
I have highlighted the same issue here.