Closed antez88 closed 2 years ago
This is a well done bug report. Thank you for that.
So when you setup the integration with the combination: 192.168.68.125, port 502 and slave id 1 it correctly sets up the integration for your 8TKL inverter?
In that case I would expect that "1,2" is the correct value to put in the slave id's fields.
If you're still experiencing issues. Please post the full logs (including pymodbus logs) where you first setup the integration with the 8KTL alone, then remove the integration again and try to setup again with the 10KTL included.
Note: I don't have an SDongleA or second inverter in my own installation. I've implemented support just by reading the technical manual, but without being able to test it in practice. I need proper logs of actual owners to understand how the system behaves in all possible configurations.
BIG thanks! Opposite order works, i.e —> “1,2”. Think it´s the only variation I haven`t tried and should have been the most logical to try :)
So at least in my case the Master Inverter (Slave 2) wasn `t the that should be first in order.
THANKS!
System Health details
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4947 Installed Version | 1.25.5 Stage | running Available Repositories | 1119 Downloaded Repositories | 5Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | 1 november 2022 01:00 relayer_connected | true remote_enabled | true remote_connected | true alexa_enabled | true google_enabled | true remote_server | eu-west-2-3.ui.nabu.casa can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 9.0 -- | -- update_channel | stable supervisor_version | supervisor-2022.10.0 agent_version | 1.3.0 docker_version | 20.10.17 disk_total | 56.6 GB disk_used | 6.3 GB healthy | true supported | true board | rpi3 supervisor_api | ok version_api | ok installed_addons | File editor (5.3.3), Terminal & SSH (9.4.0), Home Assistant Google Drive Backup (0.108.2), Node-RED (13.4.0), MariaDB (2.4.0), TellStick (2.1.0), InfluxDB (4.5.0), Grafana (8.0.2)Dashboards
dashboards | 2 -- | -- resources | 0 views | 1 mode | storageNibe Uplink Heat Pumps
api_endpoint_reachable | ok -- | --Recorder
oldest_recorder_run | 3 oktober 2022 18:23 -- | -- current_recorder_run | 12 oktober 2022 20:42 estimated_db_size | 42.71 MiB database_engine | sqlite database_version | 3.38.5Huawei Solar Setup
See attached images.
2 Inverters: SUN2000-10TKL SUN2000-8TKL
Smart Meter 3phase
Huawei Luna 10 kWh battery
SDongle
Describe the issue
When trying to connect through Network via SDongle (double checked IP in my TP Link Deco M5) I get an Error for one of my inverters (the master inverter where my battery and SDongle is connected). When trying to connect just my 8TKL inverter the integration works fine. But as soon as I try with my 10TKL, either isolated or both of them with comma separated slave IDs I get an Error.
Have double checked the slave IDs in each Inverter as seen in the snaps above. SlaveID no 1 = 8TKL Inverter SlaveID no 2 = 10TKL Inverter Have also tried both ports 502, 6607 and also with on/off in all the variations with setting “elevate permissions”. Also triple checked in both Fusion Solar and app in Inverters and Dongle that Modbus is set to Enable Unrestricted.
Lost for ideas now so I`m reaching out for help here :)
Snap with error below:
Relevant debug logs