Enabling MQTT or reboot with MQTT enabled -> deactivte the SM solar system

[Helmut1965]

EMS Version: 3.7.0
Board Profile: BBQKees Gateway E32, V1.5
TX Mode: EMS+, Service Key 0x0B

Devices: GB192, RC310, Solar Module SM100, WaterModule MS100

Problem Description: During the last day I try to change from the IOBroker EMS adapter to an mqtt communication. To do so, I enable MQTT in EMS-ESP. After I enable the MQTT it deactivates a few minutes later the Solar System. Modul is still available.

The entity 'activated' is set to off. I'm not able to enable this in web interface, I have to renable it in the RC310 at the device.
Also in case I reboot the EMS-ESP or I disconnet the ethernet cable, the Solar system will be disabled.
I copied a few log entries which was created during the enablement of the MQTT.
The problem is also there in case I change from ESP+ to ESP.

log.txt

Is there something else what I can provide?
Have a great Day
Helmut

[proddy]

looking at the logs I see something is sending many MQTT commands to EMS-ESP. Do you know what this could be?

[MichaelDvP]

There is no system info, i need to use my foggy crystall ball.
In this i see emsesp-mqtt-options publish-single and publish-to-command are checked and ioBroker adapter is set to publish own states and/or publish on subscribe. So we have a nice publish-command ping-pong-game without winners.

[MichaelDvP]

What ems-esp versio do you use, what ioBroker adapter version?
With actual versions the temperaturesensors are shown without any options checked in the adapter.

[Helmut1965]

@MichaelDvP

1. EMS-ESP: 3.7.0
2. IOBroker Adapter 4.8.0
3. There are no Tempsensors in the Adapter in case I deselect the Dalas checkbox

[MichaelDvP]

Ok, the better temperaturesensor came with Adapter 4.9 see: https://github.com/tp1de/ioBroker.ems-esp/releases/tag/v4.9.0
Ems-esp 3.7.0. has the v2-api bug, that could make it freeze, i can't remember, has the Adapter 4.8 the v2-api option or use it only v3 protocol?
Try update both, you always can go back if you don't like it.

[Helmut1965]

@MichaelDvP , thanks for reply. My target was MQTT and get rid of the EMS-ESP Adapter. The MQTT is faster because it send state changes on his own and not polling. Also it's great, that there is the possibility ton enable or disable the entities in the web interface for the API/MQTT.
There is maybe one small improvement idea, It would be great to enable/disable an entity on change but leave in the status for example every 600s. To give one example. My syspress is send every few seconds because it is between 1.3 and 1.4. So value is update very frequently. In case I disable this for sending - it's not longer there, also away from the status (default cycle). It would be great, if there is the possibility to leave all items on the status every n-seconds.
I hope, I was able to explain my thought here.

[MichaelDvP]

Yes, publish on change can only used with mqtt, API is alwas a response.
There are two possibilities for publish on change, setting publish interval to zero publishes the json of all device values on any change within this json. Checking Publish single values on change publishes additional small messages for each entity seperate. Publish is always when a ems-telegram comes in checking the values for changes and publish. So publish time is given by the bus and we don't have too much publishes at one time. Setting these single values to timing will blow the message queue. Using publish single values and setting interval to zero disables the json publish.
Works with any mqtt-broker like mosquitto, etc., In ioBroker looks like this:

There is another option: Publish to command topic (ioBroker) in mqtt-settings. This can only be used with the ioBroker-mqtt https://github.com/ioBroker/ioBroker.mqtt as mqtt-broker with disabled settings for publish on subscribe and publish on connect.
The ems-esp publishes to to the same topic used for commands, e.g. thermostat/hc1/seltemp instead of thermostat_data/hc1/seltemp. A standalone mqtt-broker as mosquitto will send any message back to to the subscription of ems-esp, so any publish of emsesp results in a write command, that's bad. The ioBroker mqtt just collects the data and sends a command only if you change in the integrated ioBroker-client. These entitiescan be used direct in ioBroker-Vis to change values. Looks like this:

But with publish on subscribe/connect in ioBroker-mqtt or when using mosquitto this leads to unwanted commands like you have with the deactivated solar.