kellerza
external mqtt server not working after upgrade to 9.xx
Issue related to
Sunsynk / mbusd Home Assistant Add-On
Last Version working is 0.8.2. I am using a separte MQTT Server and it seems to be in newer Version of your Addon uses the default HA mqtt Addon instead of mine separate configurated
A clear and concise description of what the bug is.
Expected behavior A clear and concise description of what you expected to happen.
Your environment
- Home Assistant version: 2025.10.3
- Addon:
- Name: sunsynk-multi
- Version: 2025-01-11
- Inverter:
- Make: Deye
- Model: Sun12k
- Firmware:
- Adaptor details:
- RS485 waveshare IP
You configuration
DRIVER: pymodbus INVERTERS:
- SERIAL_NR: "xxx" HA_PREFIX: deye2025 MODBUS_ID: 1 DONGLE_SERIAL_NUMBER: "0" PORT: tcp://192.168.1.84:502 SENSOR_DEFINITIONS: three-phase SENSORS:
- energy_management
- power_flow_card
- pv2_power
- System_Zero_Export_power
- System Zero Export power SENSORS_FIRST_INVERTER:
- settings MANUFACTURER: Sunsynk READ_ALLOW_GAP: 2 READ_SENSORS_BATCH_SIZE: 20 SCHEDULES:
- KEY: W READ_EVERY: 5 REPORT_EVERY: 5 CHANGE_ANY: false CHANGE_BY: 80 CHANGE_PERCENT: 0
- KEY: A READ_EVERY: 5 REPORT_EVERY: 5 CHANGE_ANY: false CHANGE_BY: 80 CHANGE_PERCENT: 0
- KEY: V READ_EVERY: 5 REPORT_EVERY: 5 CHANGE_ANY: false CHANGE_BY: 80 CHANGE_PERCENT: 0 NUMBER_ENTITY_MODE: auto PROG_TIME_INTERVAL: 15 MQTT_HOST: 192.168.1.51 MQTT_PORT: 1883 MQTT_USERNAME: mqttuser MQTT_PASSWORD: testo
paste config in the block surrounded by 3x backticks
16:44:19] INFO MQTT: Connecting to **addons@core-mosquitto:1883**
[16:44:19] INFO Read every (inverter 1)
+-----+---------------------------------------------------------------------------------+
| s | Sensors |
+-----+---------------------------------------------------------------------------------+
| 5 | battery_restart_capacity, load_l2_voltage, prog1_charge, prog4_capacity, |
| | battery_current, grid_ct_power, grid_current, pv_power, use_timer, pv2_power, |
| | prog1_capacity, prog3_time, system_zero_export_power, pv4_voltage, |
| | grid_l1_power, device_type, load_l1_voltage, grid_power, pv1_power, |
| | prog5_capacity, prog2_charge, pv3_voltage, prog1_power, prog5_time, |
| | battery_low_capacity, pv4_current, rated_power, solar_export, priority_load, |
| | prog3_capacity, prog2_capacity, grid_charge_enabled, prog4_power, pv4_power, |
| | grid_l3_power, battery_voltage, load_l2_power, load_limit, pv1_voltage, |
| | export_limit_power, prog1_time, prog4_charge, prog4_time, load_power, |
| | load_l3_power, prog5_power, pv3_current, prog2_power, load_l1_power, |
| | inverter_power, pv1_current, pv3_power, prog3_charge, pv2_current, prog3_power, |
| | battery_power, prog6_power, battery_shutdown_capacity, load_l3_voltage, |
| | prog6_charge, grid_l2_power, prog5_charge, pv2_voltage, prog2_time, prog6_time, |
| | prog6_capacity |
| 15 | grid_frequency, grid_connected, battery_soc, overall_state, serial, protocol |
| 300 | day_load_energy, total_pv_energy, total_battery_charge, day_grid_export, |
| | day_battery_discharge, day_grid_import, total_grid_export, total_grid_import, |
| | day_battery_charge, day_pv_energy, total_battery_discharge |
+-----+---------------------------------------------------------------------------------+
[16:44:19] INFO Report every (inverter 1)
+-----+----------------------------------------------------------------------------------+
| s | Sensors |
+-----+----------------------------------------------------------------------------------+
| 5 | load_l2_voltage, battery_current, grid_ct_power, grid_current, pv_power, |
| | pv2_power, pv4_voltage, grid_l1_power, load_l1_voltage, grid_power, pv1_power, |
| | pv3_voltage, pv4_current, pv4_power, grid_l3_power, battery_voltage, |
| | load_l2_power, pv1_voltage, load_power, load_l3_power, pv3_current, |
| | load_l1_power, inverter_power, pv1_current, pv3_power, pv2_current, |
| | battery_power, load_l3_voltage, grid_l2_power, pv2_voltage |
| 300 | grid_connected, prog1_charge, prog4_capacity, use_timer, prog1_capacity, |
| | total_grid_export, system_zero_export_power, prog3_time, |
| | total_battery_discharge, prog5_capacity, prog5_time, prog2_charge, |
| | grid_frequency, prog1_power, solar_export, priority_load, day_grid_import, |
| | prog3_capacity, prog2_capacity, grid_charge_enabled, total_grid_import, |
| | day_battery_charge, overall_state, prog4_power, load_limit, total_pv_energy, |
| | battery_soc, total_battery_charge, prog1_time, export_limit_power, prog4_charge, |
| | prog4_time, prog5_power, day_pv_energy, prog2_power, day_load_energy, |
| | prog3_charge, prog3_power, day_grid_export, prog6_power, prog6_charge, |
| | prog5_charge, prog2_time, day_battery_discharge, prog6_time, prog6_capacity |
+-----+----------------------------------------------------------------------------------+
[16:44:19] INFO MQTT: Connected
[16:44:21] INFO MQTT: Payload >20000: 22128 (MQTTExplorer will truncate the message)
[16:44:29] WARNING MQTT: Timeout waiting for Home Assistant. The homeassistant/status topic is empty.
Configure the MQTT integration in Home Assistant to publish a last will & testament (online/offline) with the Retain flag set.
[16:44:29] WARNING MQTT: Your entities will be unavailable if HA restarts
[16:44:29] INFO MQTT: Payload >20000: 22128 (MQTTExplorer will truncate the message)
You should try post to /services/mqtt to set the correct info
More here - https://developers.home-assistant.io/docs/api/supervisor/endpoints/
I added a MQTT_CUSTOM option. Try it on the dev/edge version and let me know
hi kellerza, thanks for your effords I installed the addon dev/edge and it seem to work.
There are some truncate messages from mqttexplorer and a runtime warning. I am not programmer and don't know if you need to do anything more.
The entities are online again :-)
Here is a snipplet of the log file:
local_hass-addon-sunsynk-edge_2025-10-29T13-13-51.342Z.log
[13:58:33] INFO MQTT MIGRATE topic homeassistant/number/2308164252/battery_max_discharge_current/config with payload {'migrate_discovery': True}
[13:58:33] INFO MQTT MIGRATE topic homeassistant/number/2308164252/battery_capacity_current/config with payload {'migrate_discovery': True}
[13:58:33] INFO MQTT MIGRATE topic homeassistant/number/2308164252/battery_shutdown_capacity/config with payload {'migrate_discovery': True}
[13:58:33] INFO MQTT MIGRATE topic homeassistant/number/2308164252/battery_restart_capacity/config with payload {'migrate_discovery': True}
[13:58:33] INFO MQTT MIGRATE topic homeassistant/number/2308164252/battery_low_capacity/config with payload {'migrate_discovery': True}
[13:58:33] INFO MQTT MIGRATE topic homeassistant/text/2308164252/date_time/config with payload {'migrate_discovery': True}
[13:58:33] INFO MQTT MIGRATE topic homeassistant/number/2308164252/ups_delay_time/config with payload {'migrate_discovery': True}
[13:58:33] INFO MQTT MIGRATE topic homeassistant/number/2308164252/battery_resistance/config with payload {'migrate_discovery': True}
[13:58:34] INFO MQTT: Payload >20000: 21985 (MQTTExplorer will truncate the message)
/usr/local/lib/python3.13/asyncio/events.py:89: RuntimeWarning: coroutine 'MQTTClient.monitor_homeassistant_status.
The truncate message is normal.
the _timeout message might indicate that you don't have the homeassistant birth/last will messages set
good to hear. Any info, when you will make a new release with this changes? THANKS FOR ALL!!!