This wiki is for version 1.0.42 onwards

Configuration Local MQTT

The configuration of local MQTT requires multiple steps which makes it difficult to install

Mqtt broker

The easiest choice is the Mosquitto Addon, which does the job very well, and has the advantage that it uses the HA users to autenticate. The Zendure Integration creates these users for all the devices in the integration. If you do not want to use Mosqitto, or allready use another broker, you must make sure that the devices are able to connect, either by anonymous acces, or by adding the credentials manually. Since it might be a security risk, these credentials are not exposed by the integration. If you need them you have to find them yourself. Please check in the logging of your broker if the devices are able to connect.

Mqtt integration

In order to know the address and username/password to connect to the broker, the Zendure Integration uses the MQTT integration

Zendure Integration Configuration

In the configuration of the Zendure Integration, you have to select "Use Local MQTT"

Bluetooth Integration

The home assistant bluetooth integration should be installed, and your zendure devices should be visible

In the Bluetooth configuration, all available devices are visible in the Advertisement monitor.

MQTT connection

Every 5 minutes the integration will try to reconnect to the MQTT server if during that time no message was received. But it is better to do it yourself by using the MQTT Reset as shown below: If the local MQTT is working correctly the connection status will show: Local MQTT, Zendure App and BLE. If all your devices show it, you are ready to go. If NOT all are properly connected, the smart matching mode will not work properly.

So when you switch it will look like this: The Connection Status is BLE, which means that HA can find the bluetooth ID of the device. If your device is not visible, it will dhow "None" as connection state. In that case you have to use a bluetooth amplifier or move your device closer. An working bletooth connection also hase the advantage that in case of a connection failure the connection cab be reset Now in order to start the connection for each device you can press the Mqtt Rest switch. It is better to do it one by one, since HA alows for a limited number of active bluetooth connections. In the connection fails, there will be errors in the HA log like:

2025-05-25 16:52:00.342 ERROR (MainThread) [custom_components.zendure_ha.zenduredevice] Timeout when trying to connect to Zen 66 ZenE1_66 And the Connection Status will show:

There are many reasons for errors, but in my experience moving the device (or computer) closer is often a good way to resolve them. You can push the switch multiple times to retry. Also starting HA agaion might help sometimes.

Zendure App

Once you are using local MQTT, it might still be usefull to use the Zendure App. In order to be able to do that, the integration relays the messages to the cloud if a request from the App comes in. This should enable the possibility to use the app for changing settings and even firmware updates. Allthough I personally use bluetooth for that...