huawei_solar: [Bug]: Battery wont charge - Caused by Huawei Dongle being present.

System Health details

System Information

version core-2022.8.4
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.10.5
os_name Linux
os_version 5.15.55
arch aarch64
timezone Europe/London
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
GitHub API Calls Remaining 4778
Installed Version 1.26.2
Stage running
Available Repositories 1097
Downloaded Repositories 10
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 8.4
update_channel stable
supervisor_version supervisor-2022.08.3
agent_version 1.2.1
docker_version 20.10.14
disk_total 113.9 GB
disk_used 78.3 GB
healthy true
supported true
board odroid-n2
supervisor_api ok
version_api ok
installed_addons File editor (5.3.3), MariaDB (2.5.1), Let’s Encrypt (4.12.6), Check Home Assistant configuration (3.11.0), Terminal & SSH (9.6.0), Zigbee2MQTT (1.27.0-1), Log Viewer (0.14.0), Mosquitto broker (6.1.2), ESPHome (2022.8.0)
Dashboards
dashboards 1
resources 1
views 7
mode storage
Recorder
oldest_recorder_run 12 July 2022 at 12:41
current_recorder_run 21 August 2022 at 19:01
estimated_db_size 7885.02 MiB
database_engine sqlite
database_version 3.38.5
Sonoff
version 3.1.0 (3871c0b)
cloud_online 43 / 183
local_online 1 / 1

Huawei Solar Setup

SDongle, Network @ 192

Describe the issue

First of, having the option to modify battery charging is amazing, thank you!

  1. When Battery Forcible charge power is changed the Logbook isn’t updated. Is this expected UX? It makes it look as if the inputs aren’t working. Numeric increments also do not update the Logbook. Selects and Checkboxes of other values do update the Logbook.
  2. When Battery Forcible charge power is changed the value doesn’t appear to have any impact on actual charging of the battery.
  3. Thanks again!

Relevant debug logs

Logger: pymodbus.client.asynchronous.async_io
Source: /usr/local/lib/python3.10/site-packages/pymodbus/client/asynchronous/async_io/__init__.py:307
First occurred: 19:04:16 (70 occurrences)
Last logged: 19:16:44

    Failed to connect: Multiple exceptions: [Errno 111] Connect call failed ('::1', 502, 0, 0), [Errno 111] Connect call failed ('127.0.0.1', 502)
    Failed to connect: [Errno 111] Connect call failed ('10.0.0.106', 6607)
    Failed to connect: Multiple exceptions: [Errno 111] Connect call failed ('::1', 6607, 0, 0), [Errno 111] Connect call failed ('127.0.0.1', 6607)
    Failed to connect: [Errno 111] Connect call failed ('10.0.0.182', 6607)
    Failed to connect: Multiple exceptions: [Errno 111] Connect call failed ('10.0.0.134', 6607), [Errno 111] Connect call failed ('fdd2:b8b:5577::9bb', 6607, 0, 0)

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 19 (17 by maintainers)

Commits related to this issue

Most upvoted comments

@dklemm I’m not intimately familiar with what really happens when you start a force charge/discharge. I observed the behavior for a couple of minutes and documented that.

I haven’t been actively using it myself, even though I started developing this integration in the first place because I wanted to actively manipulate my battery. However, preliminary results showed that the constant term of the inverter losses are just too big to bother with it, leading to round trip losses of >40% 😞