For type 243, sub-type 6 is percent, so value should be in range 0-100. Sub-type 7 (fan) should be better.

Happy to heard that! However, syntax is not the right one (so "EnergyMeterMode": "1" is ignored and may be missing in device). This don't make plugin to crash, but is just ignored. Right syntax is: "MQTTsignal": { "topic": "homeassistant/easee/power", "type": "243", "subtype": "29", "switchtype": "0 ...

Thanks for that! I'm still thinking that publishing this kind of data in homeassistant sub-topics will lead to problems at some time, but do as you wish. In all cases, this as no effects on MqttMapper... Concerning payload, float value seems to be the right one, with a decimal point (and not a comma ...

I really need to get the payload you inject into MqttMapper, as I more blond than less..

What I suspect is an illegal content (maybe a float with a "," instead of a ".").

Setting switchType = 1 means "counter is a gas meter", probably not what you wanted. FYI, here are switchtypes for meter : enum _eMeterType { MTYPE_ENERGY = 0, //0 MTYPE_GAS, //1 MTYPE_WATER, //2 MTYPE_COUNTER, //3 MTYPE_ENERGY_GENERATED, //4 MTYPE_TIME, //5 MTYPE_END }; To set "Calculated" mode ...

Could you try with : "MQTTsignal": { "topic": "homeassistant/easee/power", "type": "243", "subtype": "29", "switchtype": "0", "mapping": {"item": "~*;~0","multiplier": 1000} Item syntax `~*` means payload value and `;~0` means `;0`. MqttMapper device will be then loaded with the read value ...

I'm a bit lost... Would it be possible to post here content of MqttMapper.json file? Concerning topics, I'm still thinking that putting running values into a homeassistant sub-topic is a non sense. An I still would like to see what's inside "eas" topic and its sub-topics , as stable values can ...

This happens when you try to set value using some script. In this case, Domoticz ask MqttMapper to update external value, but you don't give /set parameters (which indeed is normal in your case, as we don't normally set a counter). Do you have any script trying to modify "MQQTTsignal" device? FMI ...

Depending on counter type you have chosen, you may have 2 displays : Widget could be daily usage (you have to wait a bit to see it incrementing), and total (located on text line, just under daily value). Total should be equal to value you see in the log, daily is computed from (total - first value ...

I'm something lost... Does the payload contain {"value": 1.52300000190735 or just 1.52300000190735 ? Reading error message, I vote for the second... In this case, try with "MQTTsignal": { "topic": "eas/easee/power", "type": "243", "subtype": "29", "switchtype": "0", "mapping": {"item ...

Let's try with:

Are you sure that you have twice the same "value" item with different content?

Would it be possible to get "eas/easee/power" full content? Concerning the error, it indicates that this kind of device (kWh counter) needs a value, while sent data only contents "" (meaning that value was not found or empty). With "eas/easee/power" content, I'll help finding the right item.

It's possible to dynamically set any icon through a dzVents script : return { on = {devices = "my Device Name"}, execute = function(dz, item) local icons = { [0] = 140, -- Off [10] = 137,-- Auto [20] = 138-- Manual } print('Info: '..item.name..', level '..tostring(item.level)..', icon '..tostring ...

Very strange... Looks like a configuration error, where homeassistant topic was given instead of "real" one (like "eas" or perhaps none)

Giving key name (easee), would it be possible to have a look at "eas" root topic (the one with 4 topics and 134 messages) ?

Could you post here a cut&paste or a screen copy of topic content?

Does anyone know how to get two digits (eg 5.2 kwh or better 5200 watt) from: "MQTTsignal": { "topic": "homeassistant/easee/power", "type": "243", "subtype": "29", "switchtype": "0", "mapping": {"item": "values/current","multiplier": 1000} So I need the output in watts, I have 0 at the moment ...

Anyway, even if this is not the best solution, it's always possible for a plugin to read/store data into a json file in plugin's folder.

Effectively, very strange... I was thinking about and error reported by HTTP, for example when closing URL, but this seems not to be the case...

I mean, does the page return an error (non 200 status) when opened in a browser?