MQTT connection and topics / data

[isi07]

Hello,
Thanks for this very helpful device.
I have two questions on the MQTT connection of my MBusino Nano.
I have flashed to latest version 1.0.3

1. couple days ago there was a power outage in my area
   the Mbusino was up again faster than my MQTT server.
   In that case it seems that MBusino stops tr to connecting to MQTT server, if it does not find MQTT server at first try.
   Is this the expected behavior?
   I only noticed a few days later and was missing the values in my statistics.
   I had to power off the MBusino and then after restart it connected to MQTT server.
   Is it possible that MBusino checks for MQTT server eveery x minutees or so? And then reconnects.

2. Other question is regarding the values of the meter reading
   it looks like not all values are updated in the MQTT topics.
   I have an Eltako DSZ15DM-3x80A meter.
   The main energy reading is only updated sometimes in the right topic for example.
   But the value/dta is coming in thee JSON part.
   Other values are populated in the topics

Is this intended behavior?
Is there a logic thatt only changed values are updated to the topics? But other topics/values are updated though.

In HA you see the changes to the value are received.

here is the corresponding jsonstring
MBusino-001/MBus/SlaveAddress100/jsonstring

{
  "header": {
    "len": 146,
    "c_field": 8,
    "address": 100,
    "ci_field": 114,
    "id": "23450075",
    "manufacturer": "ELT",
    "version": 1,
    "medium_code": 2,
    "medium": "Electricity",
    "access_counter": 238,
    "status": 0,
    "status_details": {
      "battery_low": false,
      "permanent_error": false,
      "temporary_error": false,
      "app_status": "no_error"
    },
    "signature": 0
  },
  "records": [
    {
      "vif": "0x4",
      "code": 1,
      "value_scaled": 8592040,
      "units": "Wh",
      "name": "energy",
      "tariff": 1
    },
    {
      "vif": "0x4",
      "code": 1,
      "value_scaled": 8484360,
      "units": "Wh",
      "name": "energy",
      "storage": 2,
      "tariff": 1
    },
    {
      "vif": "0x4",
      "code": 1,
      "value_scaled": 0,
      "units": "Wh",
      "name": "energy",
      "tariff": 2
    },
    {
      "vif": "0x4",
      "code": 1,
      "value_scaled": 0,
      "units": "Wh",
      "name": "energy",
      "storage": 2,
      "tariff": 2
    },
    {
      "vif": "0xfd49",
      "code": 57,
      "value_scaled": 232,
      "units": "V",
      "name": "voltage_L1"
    },
    {
      "vif": "0xfd5b",
      "code": 58,
      "value_scaled": 0,
      "units": "A",
      "name": "current_L1"
    },
    {
      "vif": "0x2c",
      "code": 13,
      "value_scaled": 0,
      "units": "W",
      "name": "power_L1"
    },
    {
      "vif": "0x2c",
      "code": 13,
      "value_scaled": 0,
      "units": "W",
      "name": "power_L1",
      "subUnit": 1
    },
    {
      "vif": "0xfd49",
      "code": 57,
      "value_scaled": 232,
      "units": "V",
      "name": "voltage_L2"
    },
    {
      "vif": "0xfd5b",
      "code": 58,
      "value_scaled": 0,
      "units": "A",
      "name": "current_L2"
    },
    {
      "vif": "0x2c",
      "code": 13,
      "value_scaled": 0,
      "units": "W",
      "name": "power_L2"
    },
    {
      "vif": "0x2c",
      "code": 13,
      "value_scaled": 0,
      "units": "W",
      "name": "power_L2",
      "subUnit": 1
    },
    {
      "vif": "0xfd49",
      "code": 57,
      "value_scaled": 233,
      "units": "V",
      "name": "voltage_L3"
    },
    {
      "vif": "0xfd5b",
      "code": 58,
      "value_scaled": 0,
      "units": "A",
      "name": "current_L3"
    },
    {
      "vif": "0x2c",
      "code": 13,
      "value_scaled": 0,
      "units": "W",
      "name": "power_L3"
    },
    {
      "vif": "0x2c",
      "code": 13,
      "value_scaled": 0,
      "units": "W",
      "name": "power_L3",
      "subUnit": 1
    },
    {
      "vif": "0xff68",
      "code": 122,
      "value_scaled": 1,
      "name": "manufactur_specific"
    },
    {
      "vif": "0x2c",
      "code": 13,
      "value_scaled": 0,
      "units": "W",
      "name": "power"
    },
    {
      "vif": "0x2c",
      "code": 13,
      "value_scaled": 0,
      "units": "W",
      "name": "power",
      "subUnit": 1
    },
    {
      "vif": "0xff13",
      "code": 122,
      "value_scaled": 0,
      "name": "manufactur_specific"
    }
  ]
}

[Zeppelin500]

Hi Isi,

1. If the MBusino do not find a broker, he search every couple of seconds for the broker. (and do nothing else). So it should be no problem, if the broker is to late. If the broker is online again, he will connect immediately.
   Is the Nano connected via Ethernet? Are you able to read out USB Serial while the same situation? There are many status messages.

2. It looks like a bug. The line with "vs_xxxx.." should not there. Please share your raw telegram. Activate it at the GUI and copy it from the mqtt explorer.
   Then downgrade to a older version. e.g. 1.0.0 and report if the bug is gone.

Regards

[isi07]

2. I have flashed down to 1.0.0
   the vs_xxxx topics are still theere

689292680864727500452394150102BF0000008C1004539285008C1104858484008C2004000000008C21040000000002FDC9FF01E80002FDDBFF01000002ACFF0100008240ACFF01000002FDC9FF02E90002FDDBFF02000002ACFF0200008240ACFF02000002FDC9FF03E90002FDDBFF03000002ACFF0300008240ACFF03000002FF68010002ACFF0000008240ACFF00000001FF1300561600

[{"vif":"0x4","code":1,"value_scaled":8592530,"units":"Wh","name":"energy","tariff":1},{"vif":"0x4","code":1,"value_scaled":8484850,"units":"Wh","name":"energy","storage":2,"tariff":1},{"vif":"0x4","code":1,"value_scaled":0,"units":"Wh","name":"energy","tariff":2},{"vif":"0x4","code":1,"value_scaled":0,"units":"Wh","name":"energy","storage":2,"tariff":2},{"vif":"0xfd49","code":57,"value_scaled":2.007001e7,"value_string":"2007-00-08","name":"voltage_TimeSt"},{"vif":"0xfd5b","code":58,"value_scaled":2000000,"value_string":"2000-00-00","name":"current_TimeSt"},{"vif":"0x2c","code":13,"value_scaled":2e8,"value_string":"2000-00-00","name":"power_TimeSt"},{"vif":"0x2c","code":13,"value_scaled":2e8,"value_string":"2000-00-00","name":"power_TimeSt","subUnit":1},{"vif":"0xfd49","code":57,"value_scaled":2.0070009e7,"value_string":"2007-00-09","name":"voltage_TimeSt"},{"vif":"0xfd5b","code":58,"value_scaled":2000000,"value_string":"2000-00-00","name":"current_TimeSt"},{"vif":"0x2c","code":13,"value_scaled":2e8,"value_string":"2000-00-00","name":"power_TimeSt"},{"vif":"0x2c","code":13,"value_scaled":2e8,"value_string":"2000-00-00","name":"power_TimeSt","subUnit":1},{"vif":"0xfd49","code":57,"value_scaled":2.0070009e7,"value_string":"2007-00-09","name":"voltage_TimeSt"},{"vif":"0xfd5b","code":58,"value_scaled":2000000,"value_string":"2000-00-00","name":"current_TimeSt"},{"vif":"0x2c","code":13,"value_scaled":2e8,"value_string":"2000-00-00","name":"power_TimeSt"},{"vif":"0x2c","code":13,"value_scaled":2e8,"value_string":"2000-00-00","name":"power_TimeSt","subUnit":1},{"vif":"0xff68","code":122,"value_scaled":1,"name":"manufactur_specific"},{"vif":"0x2c","code":13,"value_scaled":2e8,"value_string":"2000-00-00","name":"power_TimeSt"},{"vif":"0x2c","code":13,"value_scaled":2e8,"value_string":"2000-00-00","name":"power_TimeSt","subUnit":1},{"vif":"0xff13","code":122,"value_scaled":0,"name":"manufactur_specific"}]

[Zeppelin500]

Ok, thank you. I will check your telegram and come back to you next days.

[Zeppelin500]

Mh, I can't reproduce your failure. Are you sure, the raw telegram and your MQTT-Explorer output is the same telegram?
This is my output with your telegram. It looks good.

[isi07]

Thanks for your support in this.
I have updated my MQTT Explorer version to 0.4.0 beta 6 (previously 0.4.0 beta 4)
Now looks good for me as well.

[Zeppelin500]

OK, but MQTT Explorer is absolutely independent of the HA measures.
Let me know if still a problem present.

[isi07]

You are right.
I have tried few times now to reproduce the situation after a power outage by restarting the MQTT server.
In all cases the MBusino has connected again.
For now problem is gone.
Thanks