MQTT Config Topic | Home Assistant | Page 1

kind cargo Mar 25, 2024, 4:18 PM

#

It's beena few hours. Did you get it going yet or still need advice?

#

MQTT Config Topic

lament sorrel Mar 25, 2024, 4:20 PM

#

Nope, still no replies that I'm aware of

kind cargo Mar 25, 2024, 4:21 PM

#

Here's am MQTT config file I use from a python program for raspi. https://github.com/SirGoodenough/ThermoPI/blob/main/ThermoPI.py

#


payloadTconfig = {
    "name": NAMET,
    "stat_t": STATE,
    "avty_t": LWT,
    "pl_avail": "Online",
    "pl_not_avail": "Offline",
    "uniq_id": T_ID,
    "dev": {
        "ids": [
        D_ID,
        DEVICE_ID
        ],
        "name": "ThermoPI",
        'sa': AREA,
        "mf": "SirGoodenough",
        "mdl": "HomeAssistant Discovery for ThermoPI",
        "sw": "https://github.com/SirGoodenough/ThermoPI"
    },
    "unit_of_meas":"°F",
    "dev_cla":"temperature",
    "frc_upd": True,
    "val_tpl": "{{ value_json.temperature }}"
}

lament sorrel Mar 25, 2024, 4:22 PM

#

how many of those params are required?

#

My battery config msg:

    String discoveryTopic = "homeassistant/sensor/" + chip_name + "/battery/config";

    DynamicJsonDocument doc(1024);
    char buffer[512];

    StaticJsonDocument<256> device;
    device["identifiers"] = JsonArray();
    device["identifiers"].add(chip_name);
    device["name"] = "Feather Huzzah Wifi";
    device["manufacturer"] = "Ken";
    device["model"] = "Feather Huzzah ESP8266";

    doc["device"] = device;
    doc["name"] = chip_name + "_battery";
    doc["device_class"] = "battery";
    doc["state_class"] = "measurement";
    doc["unit_of_measurement"] = "%";
    doc["state_topic"]   = stateTopic;
    doc["platform"] = "mqtt";
    doc["value_template"] = "{{ value_json.battery }}";

    size_t n = serializeJson(doc, buffer);

    auto res = client.publish(discoveryTopic.c_str(), buffer, n);
    Serial.println("");
    Serial.print("sendMQTTBatteryDiscoveryMsg = [size="); Serial.print(n); Serial.print("] "); Serial.println(discoveryTopic); Serial.println(buffer);
    Serial.print("Publish Result="); Serial.println(res);

kind cargo Mar 25, 2024, 4:22 PM

#

I know you have yours in a different format but this is easier to see problem so I look at it this way. Also I use the shorted version of the keys, that's in the MATT HA docs somewhere for the list.

lament sorrel Mar 25, 2024, 4:23 PM

#

right, i found the abbreviations file

#

i've started looking at the code because the docs are lacking

#

I don't have these, at least:
"avty_t": LWT,
"pl_avail": "Online",
"pl_not_avail": "Offline",

kind cargo Mar 25, 2024, 4:25 PM

#

You don't have availability or the unique_id, I HIGHLY recommend those be added. Otjherwise if things go well, HA is fine but miss a broker because things happen, and HA gets confused. Vert little of the devide section is 'Needed',but it shown up nice in the device panel in HA.

lament sorrel Mar 25, 2024, 4:26 PM

#

It wasn't until I added the device section that it created a device object. I still haven't been able to get it to create an entity for any of the sensor values though

#

I was attempting battery/temp/humidity with a little battery powered esp8266 with a shell sensor

#

i've been able to make the mqtt device, but yeah, no entities

kind cargo Mar 25, 2024, 4:27 PM

#

kind cargo Mar 25, 2024, 4:28 PM

#

lament sorrel I don't have these, at least: "avty_t": LWT, "pl_avail": "Online", "...

and you need "uniq_id": T_ID,

lament sorrel Mar 25, 2024, 4:29 PM

#

I had tried that as well, with no result before. I assume the unique id is unique per sensor, and not per device

#

i had made unique id's that were "feather_huzzah_01_bat" and such, but i don't believe that had any meaningful results

kind cargo Mar 25, 2024, 4:29 PM

#

unique per sensor

lament sorrel Mar 25, 2024, 4:29 PM

#

i'll try adding some of these and see what happens, sec

#

"avty_t": LWT,
what is LWT here?

kind cargo Mar 25, 2024, 4:30 PM

#

Then, you have mqtt-explorer

#

?

lament sorrel Mar 25, 2024, 4:30 PM

#

nvm
LWT = TOPIC + D_ID + '/lwt'

kind cargo Mar 25, 2024, 4:31 PM

#

lwt last will testament. If the sensor is offline, this tells ha it os offline.

lament sorrel Mar 25, 2024, 4:31 PM

#

gotcha, i was just coming to that conclusion myself, i hadn't seen one implemented till now

kind cargo Mar 25, 2024, 4:31 PM

#

So if the esp is off, it will grey out the values in HA

lament sorrel Mar 25, 2024, 4:33 PM

#

how do you actually get mqtt logs from mosquito? I've only been able to listen on # for everything, but it'd be neat to be able to see why it makes determinations

#

i'm assuming that's what you mean by mqtt-explorer

kind cargo Mar 25, 2024, 4:34 PM

#

I was going to say if you look at the broker in mqtt explorer, you see what the topic actually is. If it shows up in color, the jsom is correcr. If b/w, json needs fixin. You can also dend the topic data to test sdtuff without the esp.

lament sorrel Mar 25, 2024, 4:34 PM

#

After adding the online/offline/unique id, it just created another device

kind cargo Mar 25, 2024, 4:34 PM

#

Troubleshooting MQTT? MQTT-Explorer can help you be successful!
If you have Addons available, try adding this Addon repository to your Addon list. https://github.com/GollumDom/addon-repository.

lament sorrel Mar 25, 2024, 4:34 PM

#

no sensor entity

kind cargo Mar 25, 2024, 4:35 PM

#

That program

lament sorrel Mar 25, 2024, 4:35 PM

#

i hadn't heard of this yet, thanks

kind cargo Mar 25, 2024, 4:35 PM

#

Absolutely required so you can troubleshoot and see what the broker sees

#

I think with that you will likely figure it out. Ping me this thread if you have more questions, but to get as far as you did without a good sample and that program, you will nail this in short order.

lament sorrel Mar 25, 2024, 4:38 PM

#

Thank you!

lament sorrel Mar 25, 2024, 8:47 PM

#

I'm pretty sure it'

#MQTT Config Topic