[Twiz O'Meter] MQTT data format questions

Yes that would be good. And would it be possible to only send values that are not empty? Basically, I think it's good if the TOM also sends values when the 12V battery is being charged.

maikt schrieb: And would it be possible to only send values that are not empty?

In the attached archive:
Fw145 for ESP32, with empty value filtered from the Json payload
Fw for LCD display, with WiFi reconnect forced when tapping on tray icon (mqtt or wi-fi).
Just for testing purposes, so no guaranty it will work...

maikt schrieb:

Delvecchio schrieb: After some tests, it seems to me the publishing frequency is correct.
Give a look at the following screenshot

Very strange. I have set 15s refresh interval and I get multiple refreshes per second. But 5s also didn't work. See Screenshot

I found a bug which, occasionally, reset the publishing frequency when the Json payload was active.
I think this was the cause of the problem you reported.
Enclosed the fw fix.

Delvecchio schrieb: Fw145 for ESP32, with empty value filtered from the Json payload
Fw for LCD display, with WiFi reconnect forced when tapping on tray icon (mqtt or wi-fi).

Thanks, I will test/observe it

Delvecchio schrieb: I think this was the cause of the problem you reported.

Yes, your fix resolve this issue, thanks.

Otherwise the json payload is now grouped, this is great. Is this also possible with the binary payload? And can the existing ClientID be used instead of "ToM"?

maikt schrieb: Is this also possible with the binary payload? And can the existing ClientID be used instead of "ToM"?

For the binary payload, symply add "ToM/" (or, if you prefer, the ClientID/) at the beginning of the topic out field.
For sure it's possible to use ClientID (as suggested above), but for now not for the json payload, because its topic isn't configurable at the moment. May be in the future I'll add another field.

(doubled post)

Delvecchio schrieb: For the binary payload, symply add "ToM/" (or, if you prefer, the ClientID/) at the beginning of the topic out field.

It works perfect, thanks.

Delvecchio schrieb: Fw for LCD display, with WiFi reconnect forced when tapping on tray icon (mqtt or wi-fi).

Unfortunately this doesn't work for me. Do I need an update of the display firmware for this?

Delvecchio schrieb: Fw145 for ESP32, with empty value filtered from the Json payload.

It works, but now I have a problem with the new json payload, because in order to read + transform the data in openHAB, all the data elements must always be available. However, empty values is no longer sent. You changed that at my request, but now I've seen that unfortunately it doesn't work. Sorry.

maikt schrieb: Unfortunately this doesn't work for me. Do I need an update of the display firmware for this?

Yes, in the archive I included the LCD fw file for this reason.

maikt schrieb: all the data elements must always be available. However, empty values is no longer sent. You changed that at my request, but now I've seen that unfortunately it doesn't work. Sorry.

No problem, I can restore the full payload (empty values included), as it was before.

Full Json payload restored.

Wie cool ist das denn !!

That's cool !



Readout from toM via Node-RED
Ausgelesen mit Node-RED

One simple question (perhaps I missed somewhere the info).
Eine einfache Frage (vielleicht habe ich die Info übersehen).

How is the string field wise arranged ?
Wie lautet die (Feld-)Zusammensetzung vom String ?

The payload coming from "TopicOut" is in raw format, and it's mainly used by the android app to retrieve values.
It's easier to subscribe to ToM/TopicJson ad use its payload in json format. You need to enable this payload in the Wifi page of the webserver.

Genau, das sieht dann so aus und müsste dann auch selbsterklärend sein: