micro-ebusd / MQTT / HA: Just wrote value via MQTT is not set as current value

[Commifreak]

Hi,

I observed this behavior:

Z2OpMode is currently set to day. Now I want it off. I select "Off". MQTT now show the current value being "day" and the "set"-Topic with new value "off".

As I see, the value is immediately written to ebus. But it seems that the value for MQTT is just being updated at next poll interval.

Why? Wouldnt it be better to set the new value when the write-action to ebus was successful?

Running build 20260301.

Thanks

[john30]

these are two different messages, one for read and one for write. so when doing a write, micro-ebusd does not automatically issue a subsequent read. by clicking the reload icon next to the message you should get the updated value

[Commifreak]

Yes. But wouldnt it be a good idea to set the just (successful) written new value to set get topic? Without read. When set was successful, just set this new value.

[Commifreak]

To be honest, I dont know the best practice here. I just see the odd behavior that HA does not show the just set value when refreshing the webpage. Maybe its a HA thing, maybe not. I dont know how basic MQTT best practices are.

[john30]

actually the data of a write is explicitly sent to mqtt as well, just checked it with that message definition. it does not wait for the poll cycle

[Commifreak]

Then why I get this?

The SET value is written and the GET-value changes 5 minutes after the write.

[Commifreak]

Ah, interesting. Switchinbg it a few times back and forth (and wait a bit between this) shows your described behavior, when suddenly the issue hits again: Sometimes it does not get reflected on the GET channel. And sometimes the GET-channel gets immediately the new value, set via SET.

EDIT: That maybe explains the sometimes missing HA log entries "changed due to automation xxx" because the time between set and seeing the new value is too far away? Sometimes it works. Strange.

If I can get you more infos which maybe explains this issue on my side, Iam happy to help. Maybe you are able to reproduce it on your side?

[john30]

are you sure that the mqtt client is not just missing it? maybe have a look at the broker logs

[Commifreak]

No, HA shows the same "In MQTT diagnostics", last x received and last x sent messages:

In a case were it actually works:

SET:

GET:

In a case were it does not work:

SET:

GET:

No errors on the time when it gets SET inside eas logs.

I increased log level and will check again.