Gunnar Skjold

OBIS codes does not change meaning, no. I could implement a name map for all possible electricity OBIS codes. Seeing that the firmware is already at 94% used flash space...

The idea with this issue was to extract and send any (known or unknown) OBIS to MQTT without wasting any more memory. Storing the data in AmsData class like you...

Agree, move PF values as well to ha4.json. Update your PR with this change and I will conduct some tests during my next work session.

ESP32 version of the firmware can self update. If anyone can provide the necessary JSON to publish on MQTT, I can implement the changes.

Yes, but I've had some issues getting it to work properly. I have not given up though.

I cannot find any specific examples on how this should be published on MQTT. If someone can reference a proper example, I will look into this.

> > @nechry any reason this pull request is being ignored? > > yes, @Fishwaldo initially started reviewing this code and he will finish. Seeing that @Fishwaldo has not contributed...

Could you try this version: [esp32.zip](https://github.com/gskjold/AmsToMqttBridge/files/9640340/esp32.zip)

Currently debugging with RAW full and consistently receiving data for l3. Maybe you are hitting some limits of emqx? https://docs.emqx.com/en/cloud/latest/intro/restriction.html#connected-communications

Good to know!